From: David Ford <david+cert@blue-labs.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: USB burps with irq XX: nobody cared. (2.5.70)
Date: Sun, 08 Jun 2003 18:37:35 -0400 [thread overview]
Message-ID: <3EE3BAAF.7000008@blue-labs.org> (raw)
This is one of those systems that has some 150K of dmesg on boot due to
that pesky USB barfing - IRQ XX nobody cared!.
Due to it's size I haven't included it here. Here's a link to it
however - http://blue-labs.org/~david/dmesg.out.2.5.70.bz2
(There are a lot of unknown devices in lspci output, if an interested
party wants, I'll provide as much detail as I can.)
David
# lspci -v|grep -A5 USB
00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev
a3) (prog-if 10 [OHCI])
Subsystem: FIRST INTERNATIONAL Computer Inc: Unknown device 9042
Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 20
Memory at ee087000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [44] Power Management version 2
00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev
a3) (prog-if 10 [OHCI])
Subsystem: FIRST INTERNATIONAL Computer Inc: Unknown device 9042
Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 22
Memory at ee082000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [44] Power Management version 2
00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev
a3) (prog-if 20 [EHCI])
Subsystem: FIRST INTERNATIONAL Computer Inc: Unknown device 9042
Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 20
Memory at ee083000 (32-bit, non-prefetchable) [size=256]
Capabilities: [44] #0a [2080]
Capabilities: [80] Power Management version 2
# grep -i hci /boot/2.5.70/.config
CONFIG_USB_EHCI_HCD=y
CONFIG_USB_OHCI_HCD=y
# CONFIG_USB_UHCI_HCD is not set
next reply other threads:[~2003-06-08 20:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-08 22:37 David Ford [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-09 16:26 USB burps with irq XX: nobody cared. (2.5.70) David Brownell
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=3EE3BAAF.7000008@blue-labs.org \
--to=david+cert@blue-labs.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