Re: Wish for 2006 to Alan Cox and Jeff Garzik: A functional Driver for PDC202XX

[Mike Snitzer]

On 6/21/06, Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> wrote:
> Ar Mer, 2006-06-21 am 09:34 -0400, ysgrifennodd Mike Snitzer:
> > I have a PDC20267 and tried out 2.6.17 + linux-2.6.17-ide1.gz  The
> > resulting pata_pdc202xx_old module didn't initialize the controller on
> > boot (via initrd).  Is there some other CONFIG option or linux cmdline
> > that should be used?
>
> No it should find it as soon as you load the module. If the device is
> not the primary IDE controller (hda-hdd) you can set CONFIG_IDE = y,
> include drivers for your other controller and get some debug info.
>
> Usually "it didnt initialize" reports are from people with mixed old/new
> IDE in their kernel or initrd, or initrds missing the required modules.
>
> Stick a printk in pdc_init before the pci_register_driver call and
> you'll know for sure if the module is getting loaded. If it is then send
> me an lspci and I'll have a deeper look

The PDC20267 is the primary controller, I do not have CONFIG_IDE set.
The issue with my initrd was mkinitrd --with=pata_pdc202xx_old didn't
include sd_mod; setting scsi_hostadapter accordingly in modprobe.conf
took care of this.

Once the kernel booted the system was seemingly starting without any
problems until various services tried to write files to the root
filesystem.  Each write attempt resulted in a "Read-only filesystem"
error yet all filesystems were mounted read-write.

The kernel had a ton of errors:

Buffer I/O error on device sda3, logical block 4869508
lost page write due to I/O error on sda3
ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: error=0x84 { DriveStatusError BadCRC }
ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: error=0x84 { DriveStatusError BadCRC }
ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: error=0x84 { DriveStatusError BadCRC }
ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: error=0x84 { DriveStatusError BadCRC }
ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: error=0x84 { DriveStatusError BadCRC }
ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: error=0x84 { DriveStatusError BadCRC }
sd 0:0:0:0: SCSI error: return code = 0x8000002
sda: Current: sense key: Aborted Command
   Additional sense: Scsi parity error
Info fld=0x27a3f9b

lspci output is:

00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM
Controller/Host-Hub Interface (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated
Graphics Controller (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB
UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB
UHCI Controller #2 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB
UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2
EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2)
00:1f.0 ISA bridge: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC
Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE
Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801EB/ER (ICH5/ICH5R) SMBus
Controller (rev 02)
00:1f.5 Multimedia audio controller: Intel Corporation 82801EB/ER
(ICH5/ICH5R) AC'97 Audio Controller (rev 02)
01:01.0 Unknown mass storage controller: Promise Technology, Inc.
PDC20267 (FastTrak100/Ultra100) (rev 02)
01:08.0 Ethernet controller: Intel Corporation 82562EZ 10/100 Ethernet
Controller (rev 02)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/