lkml.org 
[lkml]   [2004]   [Oct]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 2.6.9-mm1: NForce3 problem (IRQ sharing issue?)
On Sat, 23 Oct 2004, Rafael J. Wysocki wrote:

> > Beats me. Does the interrupt count stop increasing?
>
> Yes, it does.
>
> Moreover, 2.6.10-rc1 has this problem too, but here the network adapter
> stopped working along with the USB (as you can see above, it shares an IRQ
> with the USB too). Also, this time I was able to reload the ohci-hcd module
> (it didn't help) and I got these messages:
>
> Oct 23 18:32:23 albercik kernel: ohci_hcd 0000:00:02.0: remove, state 1
> Oct 23 18:32:23 albercik kernel: usb usb2: USB disconnect, address 1
> Oct 23 18:32:23 albercik kernel: usb 2-2: USB disconnect, address 2
> Oct 23 18:32:24 albercik kernel: ohci_hcd 0000:00:02.0: IRQ INTR_SF lossage
> Oct 23 18:32:24 albercik kernel: ohci_hcd 0000:00:02.0: USB bus 2 deregistered
> Oct 23 18:32:24 albercik kernel: ohci_hcd 0000:00:02.1: remove, state 1
> Oct 23 18:32:24 albercik kernel: usb usb3: USB disconnect, address 1
> Oct 23 18:32:24 albercik kernel: ohci_hcd 0000:00:02.1: USB bus 3 deregistered
> Oct 23 18:32:41 albercik kernel: ohci_hcd: 2004 Feb 02 USB 1.1 'Open' Host
> Controller (OHCI) Driver (PCI)
> Oct 23 18:32:41 albercik kernel: ACPI: PCI interrupt 0000:00:02.0[A] -> GSI 11
> (level, low) -> IRQ 11
> Oct 23 18:32:41 albercik kernel: ohci_hcd 0000:00:02.0: nVidia Corporation
> nForce3 USB 1.1
> Oct 23 18:32:41 albercik kernel: PCI: Setting latency timer of device
> 0000:00:02.0 to 64
> Oct 23 18:32:41 albercik kernel: ohci_hcd 0000:00:02.0: irq 11, pci mem
> 0xfebfb000
> Oct 23 18:32:41 albercik kernel: ohci_hcd 0000:00:02.0: new USB bus
> registered, assigned bus number 2
> Oct 23 18:32:41 albercik kernel: hub 2-0:1.0: USB hub found
> Oct 23 18:32:41 albercik kernel: hub 2-0:1.0: 3 ports detected
> Oct 23 18:32:41 albercik kernel: ACPI: PCI interrupt 0000:00:02.1[B] -> GSI 5
> (level, low) -> IRQ 5
> Oct 23 18:32:41 albercik kernel: ohci_hcd 0000:00:02.1: nVidia Corporation
> nForce3 USB 1.1 (#2)
> Oct 23 18:32:41 albercik kernel: PCI: Setting latency timer of device
> 0000:00:02.1 to 64
> Oct 23 18:32:41 albercik kernel: ohci_hcd 0000:00:02.1: irq 5, pci mem
> 0xfebfc000
> Oct 23 18:32:41 albercik kernel: ohci_hcd 0000:00:02.1: new USB bus
> registered, assigned bus number 3
> ct 23 18:32:41 albercik kernel: hub 3-0:1.0: USB hub found
> Oct 23 18:32:41 albercik kernel: hub 3-0:1.0: 3 ports detected
> Oct 23 18:32:41 albercik kernel: usb 2-2: new low speed USB device using
> address 2
> Oct 23 18:32:46 albercik kernel: usb 2-2: control timeout on ep0out
> Oct 23 18:32:46 albercik kernel: ohci_hcd 0000:00:02.0: Unlink after no-IRQ?
> Different ACPI or APIC settings may help.
> Oct 23 18:36:04 albercik kernel: Losing some ticks... checking if CPU
> frequency changed.
> Oct 23 18:37:28 albercik kernel: eth0: network connection down
> Oct 23 18:37:40 albercik kernel: eth0: no IPv6 routers present
> Oct 23 18:42:45 albercik kernel: Intel ICH 0000:00:06.0: Device was removed
> without properly calling pci_disable_device(). This may need fixing.
>
> The "control timeout on ep0out" and "Unlink after no-IRQ?" messages are
> puzzling, but the last one is just ridiculous as the box has _nothing_ to do
> with Intel.

That's probably the nforce3 audio device which is an intel part.

>
> The .config for 2.6.10-rc1 is available at:
> http://www.sisk.pl/kernel/041023/2.6.10-rc1.config
> The .config for 2.6.9-mm1 is available at:
> http://www.sisk.pl/kernel/041023/2.6.9-mm1.config
>
> The outputs of dmesg and lspci requested by Zwane will follow in a couple of
> minutes.

Thanks,
Zwane
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:07    [W:0.101 / U:3.700 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site