From: Ian Pilcher <i.pilcher@comcast.net>
To: linux-kernel@vger.kernel.org, acpi-devel@lists.sourceforge.net
Subject: 2.6.1 - IRQ routing regression on Abit VP6
Date: Tue, 13 Jan 2004 22:42:06 -0600 [thread overview]
Message-ID: <4004C89E.60703@comcast.net> (raw)
2.6.0 works fine on this hardware, including the twitchy built-in USB
controllers.
Loading the uhci-hcd module on 2.6.1 gives me the following:
drivers/usb/core/usb.c: registered new driver usbfs
drivers/usb/core/usb.c: registered new driver hub
drivers/usb/host/uhci-hcd.c: USB Universal Host Controller Interface
driver v2.1
uhci_hcd 0000:00:07.2: UHCI Host Controller
uhci_hcd 0000:00:07.2: irq 225, io base 00009400
uhci_hcd 0000:00:07.2: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
uhci_hcd 0000:00:07.3: UHCI Host Controller
uhci_hcd 0000:00:07.3: irq 225, io base 00009800
uhci_hcd 0000:00:07.3: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
hub 1-0:1.0: new USB device on port 1, assigned address 2
APIC error on CPU1: 00(40)
APIC error on CPU1: 40(40)
APIC error on CPU1: 40(40)
APIC error on CPU1: 40(40)
APIC error on CPU1: 40(40)
APIC error on CPU1: 40(40)
APIC error on CPU1: 40(40)
APIC error on CPU0: 00(40)
APIC error on CPU1: 40(40)
APIC error on CPU1: 40(40)
APIC error on CPU1: 40(40)
APIC error on CPU1: 40(40)
APIC error on CPU0: 40(40)
APIC error on CPU0: 40(40)
APIC error on CPU0: 40(40)
APIC error on CPU0: 40(40)
APIC error on CPU0: 40(40)
APIC error on CPU1: 40(40)
APIC error on CPU1: 40(40)
APIC error on CPU0: 40(40)
APIC error on CPU0: 40(40)
APIC error on CPU1: 40(40)
APIC error on CPU0: 40(40)
APIC error on CPU0: 40(40)
APIC error on CPU0: 40(40)
APIC error on CPU0: 40(40)
APIC error on CPU0: 40(40)
APIC error on CPU0: 40(40)
APIC error on CPU1: 40(40)
irq 177: nobody cared!
Call Trace:
[<c010d74a>] __report_bad_irq+0x2a/0x90
[<c010d840>] note_interrupt+0x70/0xb0
[<c010dc35>] do_IRQ+0x195/0x220
[<c011b7ed>] smp_apic_timer_interrupt+0xdd/0x150
[<c0105000>] rest_init+0x0/0x80
[<c010bc24>] common_interrupt+0x18/0x20
[<c0108ac0>] default_idle+0x0/0xc0
[<c0105000>] rest_init+0x0/0x80
[<c0108a19>] hlt_idle+0x29/0x40
[<c0108bbb>] cpu_idle+0x3b/0x50
[<c03aa4a0>] unknown_bootoption+0x0/0x120
[<c03aa940>] start_kernel+0x1b0/0x200
[<c03aa4a0>] unknown_bootoption+0x0/0x120
handlers:
[<c0263d00>] (ide_intr+0x0/0x2c0)
[<c0263d00>] (ide_intr+0x0/0x2c0)
Disabling IRQ #177
usb 1-1: control timeout on ep0out
uhci_hcd 0000:00:07.2: Unlink after no-IRQ? Different ACPI or APIC
settings may help.
And so on, until I shut down the system.
The 20031203 ACPI patch fixes the problem.
--
========================================================================
Ian Pilcher i.pilcher@comcast.net
========================================================================
reply other threads:[~2004-01-14 4:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4004C89E.60703@comcast.net \
--to=i.pilcher@comcast.net \
--cc=acpi-devel@lists.sourceforge.net \
--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