Axel Uhl writes: > Here's what /var/log/dmesg contains: ... > Tejun Heo wrote: > > Hello, > > > > On 02/12/2010 05:46 PM, Axel Uhl wrote: > >> I don't have a /var/log/boot.msg, only a /var/log/boot. Its contents: > > > > Then please attach output of dmesg after boot. Judging from your initial message and this one, it appears that the problematic disk is driven by sata_via, but sata_via shares IRQ with an awful lot of other junk. Suggestions: 1. Enable IO/APIC support in the kernel. According to your previous lspci the chipset does have one. This should reduce IRQ sharing and make IRQ handling generally better. If there's still some sharing going on, try moving PCI cards to other slots. 2. Move the problematic disk around to e.g. the Promise controller. Do the stray exceptions persist? If so, then it's the disk that's at fault. As long as the libata's error handling recovers, things should work anyway. 3. (Unrelated but...) Why use Old IDE to drive the VIA PATA controller? Just use pata_via for that one, enable SCSI SR+SG support, and disable IDE. -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
