* Tejun Heo | 2010-04-07 06:56:10 [+0900]: >On 04/06/2010 07:00 PM, Sergei Shtylyov wrote: >>> ata_sff_check_status() does not report ATA_DRQ set so I don't know why >>> the interrupt is comming. >> >> Perhaps the drive incorrectly triggers interrupt on setting the nIEN >> bit -- some drives are known to do this; there is a blacklist of such >> drives in the IDE core so that it avoids setting nIEN bit for them. > >Arghh.... that stinks. Maybe we should port the list over? What is >the ATA device in question here? [ 1.257000] ata1.00: ATA-6: WDC WD1600PB-98FBA0, 15.05R15, max UDMA/100 [ 1.264000] ata1.00: 312581808 sectors, multi 0: LBA48 [ 1.269000] ata1.01: ATAPI: HL-DT-ST DVDRAM GSA-4081B, A100, max UDMA/33 [ 1.335000] scsi 0:0:0:0: Direct-Access ATA WDC WD1600PB-98F 15.0 PQ: 0 ANSI: 5 [ 1.387000] scsi 0:0:1:0: CD-ROM HL-DT-ST DVDRAM GSA-4081B A100 PQ: 0 ANSI: 5 I try to unplug them later and see if the problem goes away once there is no device. I'm not really convinced that this the fault of the device. I just booted the kernel that worked yesterday and I ended up in "no body carred" irq storm. Hard reset, the same kernel and it worked. Two reboots later and I had the "nobody cared" again. So I guess that the irq line is active in every case but if the device (or the CPU) is fast enough then I don't notice it. Later (after the first command or so) it seems to get normal and issue the interrupt only if required. Sebastian -- 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
