Re: libata sata_sil broken on 2.6.13.1

[Jeff Garzik <jgarzik@pobox.com>]

izvekov@lps.ele.puc-rio.br wrote:
> I managed to get a serial cable. Now follows the dmesg, from where libata
> starts until it dies.
>
> ata1: SATA max UDMA/100 cmd 0xF881E080 ctl 0xF881E08A bmdma 0xF881E000 irq 11
> ata2: SATA max UDMA/100 cmd 0xF881E0C0 ctl 0xF881E0CA bmdma 0xF881E008 irq 11
> ata1: dev 0 ATA, max UDMA/133, 234441648 sectors: lba48
> ata1(0): applying Seagate errata fix
> ata1: dev 0 configured for UDMA/100
> scsi0 : sata_sil
> irq 11: nobody cared (try booting with the "irqpoll" option)


This one is related to libata.  Known problem:
    http://bugzilla.kernel.org/show_bug.cgi?id=3880

Silicon Image 311x throws interrupts after we told the hardware to 
disable interrupts, but only for a few certain devices and/or PATA 
bridges.  I only have theories as to the solution.

I made a failed attempt to solve it here:
    http://search.luky.org/linux-kernel.2005/msg14830.html

This patch from Albert Lee might solve it, but the patch itself needs 
bug fixes:
    http://marc.theaimsgroup.com/?t=112628285200005&r=1&w=2

Also, defining ATA_IRQ_TRAP in include/linux/libata.h may work around 
the problem.

Plenty more info available on request.  Nothing changed in this area 
with regards to 2.6.12/2.6.13, so I presume that ACPI has simply exposed 
the existing problem for you.  :(

    Jeff


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