From: James Bottomley <James.Bottomley@SteelEye.com>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Boot failure with 2.6.9-rc2-bk latest in usb/hid-core.c
Date: 21 Sep 2004 10:47:02 -0400 [thread overview]
Message-ID: <1095778029.2467.45.camel@mulgrave> (raw)
In-Reply-To: <20040921081047.GA10757@ucw.cz>
On Tue, 2004-09-21 at 04:10, Vojtech Pavlik wrote:
> There were changes in the function that prints the above message,
> however they were indentation only. I really doubt it could be the HID
> changes I did.
Well, I verified that it works before this merge
torvalds@ppc970.osdl.org|ChangeSet|20040916140404|15905
and doesn't with it (this was Linus pulling in your input tree).
> It looks like there is either a problem with ACPI IRQ routing that when
> enabling the EHCI controller IRQ does something bad to the OHCI
> controllers, or the EHCI driver itself does something bad to the OHCI
> controllers. (Afte all, the controllers share their ports.)
>
> Try disabling EHCI in your config to confirm my theory.
Yes, disabling EHCI in the config allows boot.
This is what lspci says about the USB controller:
0000:a0:01.0 USB Controller: NEC Corporation USB (rev 41) (prog-if 10
[OHCI])
Subsystem: NEC Corporation USB
Flags: bus master, medium devsel, latency 128, IRQ 57
Memory at 00000000d0022000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [40] Power Management version 2
0000:a0:01.1 USB Controller: NEC Corporation USB (rev 41) (prog-if 10
[OHCI])
Subsystem: NEC Corporation USB
Flags: bus master, medium devsel, latency 128, IRQ 58
Memory at 00000000d0021000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [40] Power Management version 2
0000:a0:01.2 USB Controller: NEC Corporation USB 2.0 (rev 02) (prog-if
20 [EHCI])
Subsystem: NEC Corporation USB 2.0
Flags: bus master, medium devsel, latency 128, IRQ 59
Memory at 00000000d0020000 (32-bit, non-prefetchable) [size=256]
Capabilities: [40] Power Management version 2
So it looks like ACPI is routing the IRQ's corectly. Just to confirm,
here's the ACPI routing probe from boot:
ACPI: PCI interrupt 0000:a0:01.0[A] -> GSI 38 (level, low) -> IRQ 57
GSI 39 (level, low) -> CPU 0 (0x0000) vector 58
ACPI: PCI interrupt 0000:a0:01.1[B] -> GSI 39 (level, low) -> IRQ 58
GSI 40 (level, low) -> CPU 0 (0x0000) vector 59
ACPI: PCI interrupt 0000:a0:01.2[C] -> GSI 40 (level, low) -> IRQ 59
Anything else you need?
James
prev parent reply other threads:[~2004-09-21 14:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-19 16:08 Boot failure with 2.6.9-rc2-bk latest in usb/hid-core.c James Bottomley
2004-09-21 8:10 ` Vojtech Pavlik
2004-09-21 14:47 ` James Bottomley [this message]
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=1095778029.2467.45.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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