From: Michel Bouissou <michel@bouissou.net>
To: "Protasevich, Natalie" <Natalie.Protasevich@UNISYS.com>
Cc: "Alan Stern" <stern@rowland.harvard.edu>, linux-kernel@vger.kernel.org
Subject: Re: [NOT solved] Kernel 2.6.12 + IO-APIC + uhci_hcd = Trouble
Date: Tue, 12 Jul 2005 00:01:16 +0200 [thread overview]
Message-ID: <200507120001.16803@totor.bouissou.net> (raw)
In-Reply-To: <19D0D50E9B1D0A40A9F0323DBFA04ACCE04C4A@USRV-EXCH4.na.uis.unisys.com>
Le Lundi 11 Juillet 2005 23:25, Protasevich, Natalie a écrit :
> When you get chance, maybe you could boot the OS that used to work for you
> (you mentioned 2.4) and provide the boot trace and /proc/interrupts for
> comparison.
Here it goes. Kernel is a somewhat custom ;-) 2.4.28:
# uname -r
2.4.28-0.rc1.1.1MiBevmsmdkc5
# cat /proc/interrupts
CPU0
0: 32095 IO-APIC-edge timer
1: 968 IO-APIC-edge keyboard
2: 0 XT-PIC cascade
4: 890 IO-APIC-edge serial
7: 2 IO-APIC-edge parport0
8: 1 IO-APIC-edge rtc
14: 10 IO-APIC-edge ide4
15: 42 IO-APIC-edge ide5
18: 1714 IO-APIC-level eth0, eth1
19: 13108 IO-APIC-level ide0, ide1, ide2, ide3, ehci_hcd
21: 751 IO-APIC-level usb-uhci, usb-uhci, usb-uhci
22: 0 IO-APIC-level VIA8233
NMI: 0
LOC: 32049
ERR: 0
MIS: 33
And what should be relevant to USB in the boot log...:
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.275 $ time 11:23:26 Jan 2 2005
usb-uhci.c: High bandwidth mode enabled
usb-uhci.c: USB UHCI at I/O 0xcc00, IRQ 21
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: USB UHCI at I/O 0xd000, IRQ 21
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: USB UHCI at I/O 0xd400, IRQ 21
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 3
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
ehci_hcd 00:10.3: VIA Technologies, Inc. USB 2.0
ehci_hcd 00:10.3: irq 19, pci mem f8b32000
usb.c: new USB bus registered, assigned bus number 4
ehci_hcd 00:10.3: USB 2.0 enabled, EHCI 1.00, driver 2003-Dec-29/2.4
hub.c: USB hub found
hub.c: 6 ports detected
usbdevfs: remount parameter error
usb.c: registered new driver hiddev
usb.c: registered new driver hid
hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vojtech@suse.cz>
hid-core.c: USB HID support drivers
mice: PS/2 mouse device common for all mice
[...]
hub.c: connect-debounce failed, port 1 disabled
[...]
hub.c: new USB device 00:10.2-2, assigned address 2
usb.c: USB device 2 (vend/prod 0x5d8/0x4002) is not claimed by any active
driver.
hub.c: new USB device 00:10.0-1, assigned address 2
input: USB HID v1.10 Mouse [Logitech USB Receiver] on usb1:2.0
usb.c: registered new driver usbscanner
scanner.c: USB scanner device (0x05d8/0x4002) now attached to scanner0
scanner.c: 0.4.16:USB Scanner Driver
usb.c: registered new driver usbmouse
usbmouse.c: v1.6:USB HID Boot Protocol mouse driver
Hope this may help...?
Cheers.
--
Michel Bouissou <michel@bouissou.net> OpenPGP ID 0xDDE8AC6E
next prev parent reply other threads:[~2005-07-11 22:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 21:25 [NOT solved] Kernel 2.6.12 + IO-APIC + uhci_hcd = Trouble Protasevich, Natalie
2005-07-11 22:01 ` Michel Bouissou [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-11 23:41 Protasevich, Natalie
2005-07-12 7:52 ` Michel Bouissou
2005-07-11 20:16 [SOLVED ??] " Alan Stern
2005-07-11 20:46 ` Michel Bouissou
2005-07-11 20:58 ` Michel Bouissou
2005-07-11 21:21 ` [NOT solved] " Michel Bouissou
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=200507120001.16803@totor.bouissou.net \
--to=michel@bouissou.net \
--cc=Natalie.Protasevich@UNISYS.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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;
as well as URLs for NNTP newsgroup(s).