> >Michel,
> >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.
> # cat /proc/interrupts - 2.4:
> 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
>
One difference between the above and the 2.6 one you sent before is that
you don't seem to have rtc employed on 2.6:
CPU0
0: 626375 IO-APIC-edge timer
1: 1599 IO-APIC-edge i8042
2: 0 XT-PIC cascade
4: 1708 IO-APIC-edge serial
7: 2 IO-APIC-edge parport0
14: 19858 IO-APIC-edge ide2
15: 5220 IO-APIC-edge ide3
16: 30711 IO-APIC-level nvidia
18: 1799 IO-APIC-level eth0, eth1
19: 103365 IO-APIC-level ide0, ide1, ehci_hcd:usb4, aic7xxx
21: 47273 IO-APIC-level uhci_hcd:usb1, uhci_hcd:usb2,
uhci_hcd:usb3
22: 2782 IO-APIC-level VIA8233
I don't expect this to be of any significance, but as Alan said you
never know... Another thing is that you are getting large number of
interrupts on the VIA device, whereas there is no any on 2.4. Does the
chipset get enabled differently? I wish I new VIA chipset, or had it,
will probably have to finally get some documentation on it.
> 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
Here I see that no fixups were applied to the chipset, and it seemed to
work just fine without them. I would experiment and turn fixups off, but
since this is a production system... Hmmm.
Your previous trace for 2.6 with fixups:
USB Universal Host Controller Interface driver v2.2
PCI: Via IRQ fixup for 0000:00:10.0, from 10 to 5 uhci_hcd 0000:00:10.0:
VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller uhci_hcd
0000:00:10.0: new USB bus registered, assigned bus number 1 uhci_hcd
0000:00:10.0: irq 21, io base 0x0000cc00 hub 1-0:1.0: USB hub found hub
1-0:1.0: 2 ports detected
PCI: Via IRQ fixup for 0000:00:10.1, from 10 to 5 uhci_hcd 0000:00:10.1:
VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (#2) uhci_hcd
0000:00:10.1: new USB bus registered, assigned bus number 2 uhci_hcd
0000:00:10.1: irq 21, io base 0x0000d000 hub 2-0:1.0: USB hub found hub
2-0:1.0: 2 ports detected
PCI: Via IRQ fixup for 0000:00:10.2, from 10 to 5 uhci_hcd 0000:00:10.2:
VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (#3) usb 1-1:
new low speed USB device using uhci_hcd and address 2 uhci_hcd
0000:00:10.2: new USB bus registered, assigned bus number 3 uhci_hcd
0000:00:10.2: irq 21, io base 0x0000d400 hub 3-0:1.0: USB hub found hub
3-0:1.0: 2 ports detected
PCI: Via IRQ fixup for 0000:00:10.3, from 11 to 3 ehci_hcd 0000:00:10.3:
VIA Technologies, Inc. USB 2.0 ehci_hcd 0000:00:10.3: new USB bus
registered, assigned bus number 4 ehci_hcd 0000:00:10.3: irq 19, io mem
0xe3009000 ehci_hcd 0000:00:10.3: USB 2.0 initialized, EHCI 1.00, driver
10 Dec 2004
usbcore: registered new driver hiddev
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 6 ports detected
usbhid: probe of 1-1:1.0 failed with error -5
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.01:USB HID core driver irq 21: nobody
cared!
Seeing actual IO-APIC setup in both cases would help, the ones you get
with apic=verbose, and you might have to provide full traces (as
attachment for example). It is somewhat comforting for me to know that
my patch is not affecting the outcome. But it is important to crack this
case of course. I think we need higher authority here, such as Bjorn, or
Alan...
Cheers,
--Natalie
> --
> Michel Bouissou <[EMAIL PROTECTED]> OpenPGP ID 0xDDE8AC6E
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
