Bug 227551

Summary: usb not working in 10.2 - regresion from 10.1
Product: [openSUSE] openSUSE 10.2 Reporter: Pavel Nemec <pnemec>
Component: KernelAssignee: Thomas Renninger <trenn>
Status: RESOLVED WONTFIX QA Contact: E-mail List <qa-bugs>
Severity: Major    
Priority: P5 - None    
Version: RC 5   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: boot messages
hwinfo output
/proc/interrupts and dmes on SL 10.1

Description Pavel Nemec 2006-12-11 07:35:12 UTC
I have Asus k8n4-e Mainboard. Everything work flavlesly on 10.1
On 10.2 no usb device work (or show up in logs).

logs will follow
Comment 1 Pavel Nemec 2006-12-11 07:36:45 UTC
Created attachment 109079 [details]
boot messages
Comment 2 Pavel Nemec 2006-12-11 07:44:16 UTC
Created attachment 109082 [details]
hwinfo output
Comment 3 Greg Kroah-Hartman 2006-12-14 20:11:22 UTC
Looks like an acpi interrupt routing issue :(
Comment 4 Thomas Renninger 2007-01-03 16:54:30 UTC
Again an NFORCE chipset, this is probably a duplicate?
Can you try:
acpi_use_timer_override
and (if above does not help):
nomsi
and (if above two do not help):
noapic
boot parameters please.
Comment 5 Pavel Nemec 2007-01-04 07:42:47 UTC
I will try it today.

I already tried noapic. It did not help.

Comment 6 Pavel Nemec 2007-01-05 15:33:12 UTC
i tried boath command (acpi_use_timer_oveerride and nomsi) non of them works.
Comment 7 Thomas Renninger 2007-01-05 16:09:40 UTC
whatabout:
pci=noacpi
and
pci=routeirq
Does one of them help?

Hmm, better check for a BIOS update before.
If you still have the 10.1 installed, can you post /proc/insterrupts of both and also attach dmesg output of 10.1 with this machine, pls.
Comment 8 Pavel Nemec 2007-01-08 09:37:42 UTC
I already tried pci=noacpi (no help), i will try pci=routeirq today.

I already download newer bios (no information about changes in irq/usb/apm), but it is little hard to update it without Win ;) I will do it now.
I will also gather all logs you asked.
Comment 9 Pavel Nemec 2007-01-09 16:10:42 UTC
Created attachment 112030 [details]
/proc/interrupts and dmes on SL 10.1
Comment 11 Pavel Nemec 2007-01-10 09:39:03 UTC
on 10.2
cat /proc/interrupts v
           CPU0       
  0:     205779    IO-APIC-edge  timer
  1:        176    IO-APIC-edge  i8042
  6:          5    IO-APIC-edge  floppy
  7:          1    IO-APIC-edge  parport0
  8:          2    IO-APIC-edge  rtc
  9:          0   IO-APIC-level  acpi
 10:          0    IO-APIC-edge  MPU401 UART
 14:      26115    IO-APIC-edge  ide0
 15:       8518    IO-APIC-edge  ide1
NMI:          0 
LOC:     205679 
ERR:          0
MIS:          0
Comment 12 Thomas Renninger 2007-01-11 11:39:15 UTC
Is this a x86_64 system? If yes this is probably a duplicate.

*** This bug has been marked as a duplicate of bug 232013 ***
Comment 13 Pavel Nemec 2007-01-11 12:25:17 UTC
I am not sure if this is duplicate.
This is x86_64 computer, but system is i586
I never have problems with installing. Just USB device do not work.
Also this is not dual core system.

I can try load new kernel, but i do not know which one.
Comment 14 Thomas Renninger 2007-01-11 13:27:21 UTC
It's still worth to try whether this got fixed in 2.6.20 kernel, best try the same kernel flavor i586/x86_64 that failed.
Comment 15 Pavel Nemec 2007-01-12 08:47:27 UTC
I tested new 2.6.20 kernel. It did not help. Same results, no usb.

I am not kernel expert, but i think this is not duplicate of bug 232013. I do not have problem with booting or installing (which is also booting kernel), and i also do not have dualcore system.

Hence i am reopening this bug.

Comment 16 Thomas Renninger 2007-01-13 12:31:04 UTC
Something seems to go wrong with USB and the forcedeath network card IRQ assignment...:

<7>PCI: Setting latency timer of device 0000:00:0a.0 to 64
<6>forcedeth: Couldn't find register window for device 0000:00:0a.0.
<6>ACPI: PCI interrupt for device 0000:00:0a.0 disabled
<4>forcedeth: probe of 0000:00:0a.0 failed with error -22
<6>ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [APCH] -> GSI 23 (level, low) -> IRQ 217
<7>PCI: Setting latency timer of device 0000:00:0a.0 to 64
<6>forcedeth: Couldn't find register window for device 0000:00:0a.0.
<6>ACPI: PCI interrupt for device 0000:00:0a.0 disabled
<4>forcedeth: probe of 0000:00:0a.0 failed with error -22
<6>usbcore: registered new driver usbfs
<6>usbcore: registered new driver hub
<7>ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
<4>ACPI: PCI Interrupt Link [APCF] disabled and referenced, BIOS bug
<4>ACPI: PCI Interrupt Link [APCF] BIOS reported IRQ 0, using IRQ 22
<4>ACPI: PCI Interrupt Link [APCF] enabled at IRQ 22
<6>ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [APCF] -> GSI 22 (level, low) -> IRQ 225
<6>ACPI: PCI interrupt for device 0000:00:02.0 disabled
<3>ohci_hcd 0000:00:02.0: init 0000:00:02.0 fail, -16
<4>ohci_hcd: probe of 0000:00:02.0 failed with error -16
<4>ACPI: PCI Interrupt Link [APCL] disabled and referenced, BIOS bug
<4>ACPI: PCI Interrupt Link [APCL] BIOS reported IRQ 0, using IRQ 21
<4>ACPI: PCI Interrupt Link [APCL] enabled at IRQ 21
<6>ACPI: PCI Interrupt 0000:00:02.1[B] -> Link [APCL] -> GSI 21 (level, low) -> IRQ 233
<6>ACPI: PCI interrupt for device 0000:00:02.1 disabled
<3>ehci_hcd 0000:00:02.1: init 0000:00:02.1 fail, -16
<4>ehci_hcd: probe of 0000:00:02.1 failed with error -16
<4>Emu10k1_gameport: probe of 0000:05:08.1 failed with error -16

Can you also attach acpidump output which contains ACPI IRQ routing information, pls. If you still have 10.1 installed a dmesg of this booted could also help a lot. I hope to be able to find something then...
Comment 17 Thomas Renninger 2007-03-05 18:33:15 UTC
bug #232013 also affects i586 machines and is about wrong IRQ routing.
Can you please check if:
maxcpus=0
(eventually also add noapic)
helps?
Comment 18 Pavel Nemec 2007-03-06 08:16:14 UTC
No, i get rid of that machine.