From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tejun Heo Subject: Re: [git patches] libata fixes Date: Mon, 19 Mar 2007 13:37:17 +0900 Message-ID: <45FE137D.8000300@gmail.com> References: <00f401c7694d$81a80920$2101a8c0@donald> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from py-out-1112.google.com ([64.233.166.177]:19937 "EHLO py-out-1112.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752797AbXCSEhX (ORCPT ); Mon, 19 Mar 2007 00:37:23 -0400 Received: by py-out-1112.google.com with SMTP id a29so237354pyi for ; Sun, 18 Mar 2007 21:37:23 -0700 (PDT) In-Reply-To: <00f401c7694d$81a80920$2101a8c0@donald> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: rol@as2917.net Cc: 'Linus Torvalds' , 'Jeff Garzik' , 'Alan Cox' , 'Andrew Morton' , linux-ide@vger.kernel.org, 'LKML' , "'Eric D. Mudama'" Paul Rolland wrote: > Doh ! Got that : > > .... > ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 23 (level, low) -> IRQ 23 > ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode > ahci 0000:00:1f.2: flags: 64bit ncq led clo pio slum part > ata1: SATA max UDMA/133 cmd 0xffffc2000008e900 ctl 0x0000000000000000 bmdma > 0x0000000000000000 irq 504 > ata2: SATA max UDMA/133 cmd 0xffffc2000008e980 ctl 0x0000000000000000 bmdma > 0x0000000000000000 irq 504 > ata3: SATA max UDMA/133 cmd 0xffffc2000008ea00 ctl 0x0000000000000000 bmdma > 0x0000000000000000 irq 504 > ata4: SATA max UDMA/133 cmd 0xffffc2000008ea80 ctl 0x0000000000000000 bmdma > 0x0000000000000000 irq 504 > ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > ata2.00: ATA-6: External Disk 0, RGL10364, max UDMA/133 > ata2.00: 1 sectors, multi 1: LBA48 > ata2.00: configured for UDMA/133 [--snip--] > scsi 1:0:0:0: Direct-Access ATA External Disk 0 RGL1 PQ: 0 ANSI: 5 > SCSI device sdb: 1 512-byte hdwr sectors (0 MB) > sdb: Write Protect is off > SCSI device sdb: write cache: enabled, read cache: enabled, doesn't support > DPO or FUA > SCSI device sdb: 1 512-byte hdwr sectors (0 MB) > sdb: Write Protect is off > SCSI device sdb: write cache: enabled, read cache: enabled, doesn't support > DPO or FUA > sdb:<3>irq 504: nobody cared (try booting with the "irqpoll" option) > > Call Trace: > [] __report_bad_irq+0x35/0x90 > [] note_interrupt+0x21a/0x270 > [] handle_edge_irq+0x10f/0x150 > [] do_IRQ+0x7b/0xf0 > [] mwait_idle+0x0/0x50 > [] ret_from_intr+0x0/0xa > [] vgacon_cursor+0x0/0x1d0 > [] mwait_idle+0x46/0x50 > [] cpu_idle+0x5c/0xa0 > [] start_kernel+0x2aa/0x2c0 > [] _sinittext+0x176/0x180 > > handlers: > [] (ahci_interrupt+0x0/0x590) > Disabling IRQ #504 > unknown partition table > sd 1:0:0:0: Attached scsi disk sdb > sd 1:0:0:0: Attached scsi generic sg1 type 0 > scsi 2:0:0:0: Direct-Access ATA Maxtor 6L250S0 BANC PQ: 0 ANSI: 5 > SCSI device sdc: 490234752 512-byte hdwr sectors (251000 MB) > sdc: Write Protect is off > > > and though it said : > sdb:<3>irq 504: nobody cared (try booting with the "irqpoll" option) > I _am_ booting with the irqpoll option ! Oh... that's just weird. It seems you'll have to continue boot with the timeouts for the time being. Sorry about that. -- tejun