Re: hang booting onboard HPT 366 with libata (PATA)

[Ricardo Lugo <ricardolugo@gmail.com>]

On Dec 2, 2006, at 8:03 AM, Alan wrote:

> On Sat, 2 Dec 2006 11:19:28 +0000
> Alan <alan@lxorguk.ukuu.org.uk> wrote:
>
> > > ACPI: PCI Interrup 0000:00:13.1[B] -> GSI 18 (level, low) -> IRQ 16
> > > ata5: PATA max UDMA/66 cmd 0xE400 ctl 0xE802 bmdma 0xEC00 irq 16
> > > ata6: PATA max UDMA/66 cmd 0x0 ctl 0x2 bmdma 0xEC08 irq 16
> >
> > Ok so the underlying problem seems to be that the second channel  
> > of the
> > card had no I/O resource assigned to it, presumably because it  
> > wasn't in
> > use. We check various other "not in use" things but not that one.
> >
> > I'll fix that up. I think it just needs another check in libata-sff.
>
> Try the following

That certainly sped up the bootup process, but still hangs at the  
same place. Interestingly, if I append "nosmp" to kernel params, it  
hangs earlier and I get a different error. Specifics below:

ACPI: PCI Interrupt 0000:00:13.0[A] -> GSI 18 (level, low) -> IRQ 16
ata3: PATA max UDMA/66 cmd 0xD800 ctl 0xDC02 bmdma 0xE000 irq 16
scsi2: pata_hpt366
ATA: abnormal status 0x8 on port 0xD807
ACPI: PCI Interrupt 0000:00:13.1[B] -> GSI 18 (level, low) -> IRQ 16
ata4: PATA max UDMA/66 cmd 0xE400 ctl 0xE802 bmdma 0xEC00 irq 16
scsi3: pata_hpt366
ata4.00: ATA-6, max UDMA/100, 156301488 sectors: LBA48
ata4.00: configured for UDMA/33
scsi 3:0:0:0: Direct-Access     ATA       ST380011A 3.06 PQ: 0 ANSI: 5
SCSI device sda: 156301488 512-byte hdrwr sectors (80026 MB)
sda: Write Protect is off
SCSI device sda: drive cache: write back
SCSI device sda: 156301488 512-byte hdrwr sectors (80026 MB)
sda: Write Protect is off
SCSI device sda: drive cache: write back
sda:_

--- nosmp ---
...
ACPI: PCI Interrupt 0000:00:13.1[B] -> GSI 18 (level, low) -> IRQ 16
ata4: PATA max UDMA/66 cmd 0xE400 ctl 0xE802 bmdma 0xEC00 irq 16
scsi3: pata_hpt366
ata4.00: qc timeout (cmd 0xec)
ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4)

- Rick
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/