From: "Paul Rolland" <rol@witbe.net>
To: Linux Kernel <linux-kernel@vger.kernel.org>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Cc: rol@witbe.net
Subject: 2.6.23-rc7 - _random_ IRQ23 : nobody cared
Date: Mon, 24 Sep 2007 08:33:36 +0200 [thread overview]
Message-ID: <20070924083336.7a08fd61@tux.DEF.witbe.net> (raw)
Hello,
I already reported kernel 2.6.23-rcX warning about irq X : nobody cared, and
it seemed to have been fixed in 2.6.23-rc6... Unfortunately, just rebooting
with my 2.6.23-rc7, I got it appearing again, though the previous boot was
just fine, and I didn't change/recompile my kernel in between.
So, what changed ? I've compiled two modules : qc-usb-messenger, and
hsf-modem, to make sure all my hardware is fully supported.
And now, I have :
....
scsi 3:0:1:0: Direct-Access ATA ST3500641AS 3.AA PQ: 0 ANSI: 5
sd 3:0:1:0: [sdd] 976773168 512-byte hardware sectors (500108 MB)
sd 3:0:1:0: [sdd] Write Protect is off
sd 3:0:1:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support
DPO or FUA
sd 3:0:1:0: [sdd] 976773168 512-byte hardware sectors (500108 MB)
sd 3:0:1:0: [sdd] Write Protect is off
sd 3:0:1:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support
DPO or FUA
irq 23: nobody cared (try booting with the "irqpoll" option)
Call Trace:
<IRQ> [<ffffffff8105d21b>] __report_bad_irq+0x30/0x72
[<ffffffff8105d46c>] note_interrupt+0x20f/0x253
[<ffffffff8105dd38>] handle_fasteoi_irq+0xa9/0xd1
[<ffffffff8100ec65>] do_IRQ+0xf1/0x160
[<ffffffff8100b25b>] mwait_idle+0x0/0x45
[<ffffffff8100c431>] ret_from_intr+0x0/0xa
<EOI> [<ffffffff8100b29d>] mwait_idle+0x42/0x45
[<ffffffff8100b1f3>] cpu_idle+0xbd/0xe0
[<ffffffff8175ca8e>] start_kernel+0x2bb/0x2c7
[<ffffffff8175c140>] _sinittext+0x140/0x144
handlers:
[<ffffffff81307485>] (ata_interrupt+0x0/0x1d3)
Disabling IRQ #23
sdd:<3>ata4.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata4.01: cmd c8/00:08:00:00:00/00:00:00:00:00/f0 tag 0 cdb 0x0 data 4096 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata4: soft resetting port
ata4.01: qc timeout (cmd 0x27)
ata4.01: ata_hpa_resize 1: hpa sectors (0) is smaller than sectors
(976773168) ata4.00: failed to IDENTIFY (I/O error, err_mask=0x40)
ata4: failed to recover some devices, retrying in 5 secs
ata4: soft resetting port
ata4.01: qc timeout (cmd 0x27)
....
Booting with irqpoll is Ok, and I have :
2 [14:55] rol@donald:~> cat /proc/interrupts
CPU0 CPU1
0: 31263 0 IO-APIC-edge timer
1: 201 0 IO-APIC-edge i8042
4: 219 0 IO-APIC-edge serial
6: 5 0 IO-APIC-edge floppy
8: 1 0 IO-APIC-edge rtc
9: 0 0 IO-APIC-fasteoi acpi
12: 129 1124 IO-APIC-edge i8042
14: 7010 1235 IO-APIC-edge libata
15: 0 0 IO-APIC-edge libata
17: 0 0 IO-APIC-fasteoi uhci_hcd:usb3
18: 0 0 IO-APIC-fasteoi uhci_hcd:usb4
19: 4250 0 IO-APIC-fasteoi uhci_hcd:usb5, HDA Intel
20: 1251 44 IO-APIC-fasteoi ehci_hcd:usb1, uhci_hcd:usb2
21: 422 640 IO-APIC-fasteoi pata_pdc2027x, firewire_ohci
23: 24023 0 IO-APIC-fasteoi libata, hsfpcibasic2
378: 93 108 PCI-MSI-edge eth0
379: 1 0 PCI-MSI-edge eth1
NMI: 0 0
LOC: 31000 30803
ERR: 0
Hell, IRQ 23 is shared between libata and my modem !!!
OK, just reboot, and see what happens.... Cool, now it is booting fine,
no more complaint, even without irqpoll, IRQ 23 still shared...
Another one, and Ok again... So, this looks really random :(
Anything I could do to try to collect usefull traces ?
Paul
next reply other threads:[~2007-09-24 6:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 6:33 Paul Rolland [this message]
2007-09-24 14:26 ` David Newall
2007-09-25 7:00 ` Paul Rolland
2007-09-27 0:55 ` Tejun Heo
2007-09-27 6:05 ` Paul Rolland
2007-09-27 9:04 ` Benjamin Herrenschmidt
2007-09-27 10:05 ` Paul Rolland
2007-09-27 22:27 ` Benjamin Herrenschmidt
2007-09-28 6:30 ` Paul Rolland
2007-09-28 9:55 ` Tejun Heo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070924083336.7a08fd61@tux.DEF.witbe.net \
--to=rol@witbe.net \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome