Re: Updated libata PATA patch

Alan Cox
2006-05-10T16:27:51Z

On Mer, 2006-05-10 at 12:05 -0400, Kevin Radloff wrote:
> > ae.irq_flags = SA_SHIRQ ?
>
> Another new and exciting oops :)

Yay, so that one was the PCMCIA code being broken.

> pcmcia: registering new device pcmcia1.0
> ata3: PATA max PIO0 cmd 0x3100 ctl 0x310E bmdma 0x0 irq 11
> ata3: dev 0 cfg 49:0200 82:0000 83:0000 84:0000 85:0000 86:0000 87:0000 88:0000
> ata3: dev 0 ATA-10, max PIO4, 2001888 sectors: LBA
> ata3: dev 0 configured for PIO0

This is all good. Its a PIO0 device (PCMCIA is ISA cycles which are PIO0
cycles)

> scsi2 : pata_pcmcia
> Vendor: ATA Model: SanDisk SDCFH-10 Rev: HDX
> Type: Direct-Access ANSI SCSI revision: 05
> SCSI device sdb: 2001888 512-byte hdwr sectors (1025 MB)

The disk was found and the indentify data came out correctly.

> sdb: Write Protect is off
> sdb: Mode Sense: 00 3a 00 00
> SCSI device sdb: drive cache: write through
> SCSI device sdb: 2001888 512-byte hdwr sectors (1025 MB)
> sdb: Write Protect is off
> sdb: Mode Sense: 00 3a 00 00
> SCSI device sdb: drive cache: write through

The drive was sized, the cache checked properly.

> sdb:<1>BUG: unable to handle kernel NULL pointer dereference at
> virtual address 00000000

Awww.. how to ruin a good day 8)

At this point its trying to read the partition table. It has translated
the command into a SCSI command block and into ATA,. It has queued it,
and it has just set out to issue it when it went boom

I'll do some more digging, but putting printks into ata_qc_issue_prot to
see where it explodes is the next step I suspect.