Re: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)

[Vegard Nossum]

On Sat, Feb 23, 2008 at 7:31 PM, Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> wrote:
> O> I don't see the connection between (no-)smp and ata. Something with
>
> > interrupt routing/IPI, missing irq ack? Booting another !SMP kernel
>  > works fine. The problem also exists in 2.6.24-rc2.
>
>  Almost certainly interrupt routing try smp but with noapic and see if it
>  fails as well ?

Just a quick follow-up. On regular bootups, I get this message:

ata1: SATA max UDMA/133 cmd 0xf8850100 ctl 0x00000000 bmdma 0x00000000 irq 218
ata2: SATA max UDMA/133 cmd 0xf8850180 ctl 0x00000000 bmdma 0x00000000 irq 218

while the nosmp one gets this (the screenshot cut the irq part):

ata1: SATA max UDMA/133 abar m2048@0x9b304000 port 0x9b304100 irq 223
ata2: SATA max UDMA/133 abar m2048@0x9b304000 port 0x9b304100 irq 223

Don't know if the irq # change is significant or not. Will try noapic now.


Vegard
--
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/