kworker / deactivated network interface

Hello

I encounter a new phenomenon on my openSUSE 11.4 x86_64:
A process called kworker makes the system almost unresponsive due to excessive cpu usage.
Moreover, the network interface is disabled. Quote from /var/log/NetworkManager:


eth0: device state change: 1->2 (reason 2)
eth0: bringing up device.
eth0: preparing device.
eth0: deactivating device (reason 2)

Any hint is appreciated! Many thanks in advance (had to type this on my ipod since my machine does not work…)

On 07/05/2011 01:36 PM, checkfrogger wrote:
>
> Hello
>
> I encounter a new phenomenon on my openSUSE 11.4 x86_64:
> A process called kworker makes the system almost unresponsive due to
> excessive cpu usage.
> Moreover, the network interface is disabled. Quote from
> /var/log/NetworkManager:
>
> Code:
> --------------------
>
> eth0: device state change: 1->2 (reason 2)
> eth0: bringing up device.
> eth0: preparing device.
> eth0: deactivating device (reason 2)
>
> --------------------
>
> Any hint is appreciated! Many thanks in advance (had to type this on my
> ipod since my machine does not work…)

Process kworker is the kernel thread - it does things for drivers that do not
need to be done at interrupt priority.

What hardware do you have for your ethernet device? The appropriate two lines
from ‘/sbin/lspci -nnk’ should suffice. If you note the kernel driver in use,
does your system work better when you ‘sudo /sbin/modprobe -r <driver_name>’. If
so, that isolates the problem to the driver/card. If not, whatever is the real
problem is harming the operation of eth0.

Does the output of ‘dmesg’ show anything in the way of oops output?

Thanks for your answer. My ethernet adapter is


00:19.0 ethernet controller [0200]: intel corporation 82566MM gigabit network connection [8086:1049] (rev 03)
Subsystem: Lenovo Thinkpad T61 [17aa:20b9]
kernel driver in use: e1000e

so I stopped this driver and indeed it makes the system responsive again…
Is there another driver I could try?
dmesg doesn’t show any oops stuff…
Thanks!

On 07/05/2011 04:06 PM, checkfrogger wrote:
>
> Thanks for your answer. My ethernet adapter is
>
> Code:
> --------------------
>
> 00:19.0 ethernet controller [0200]: intel corporation 82566MM gigabit network connection [8086:1049] (rev 03)
> Subsystem: Lenovo Thinkpad T61 [17aa:20b9]
> kernel driver in use: e1000e
>
> --------------------
>
> so I stopped this driver and indeed it makes the system responsive
> again…
> Is there another driver I could try?
> dmesg doesn’t show any oops stuff…
> Thanks!

If you reload the driver again, I am assuming that the problem returns.

Please check if extra interrupts are being generated. ‘cat /proc/interripts’
will give that info. You should also check that the cable is properly seated,
and you should try another port on your router if that is possible.

If none of these help, I think you need to consider that your hardware has failed.

Reloading the driver or choosing a different router port did not help…
The list of interrupts follows:

           CPU0       CPU1       
  0:     153168     154513   IO-APIC-edge      timer
  1:         35         28   IO-APIC-edge      i8042
  8:          1          3   IO-APIC-edge      rtc0
  9:        593        342   IO-APIC-fasteoi   acpi
 12:       2921       2807   IO-APIC-edge      i8042
 14:        675        316   IO-APIC-edge      ata_piix
 15:          0          0   IO-APIC-edge      ata_piix
 16:        358         76   IO-APIC-fasteoi   uhci_hcd:usb5, yenta, nvidia
 17:          2          6   IO-APIC-fasteoi   uhci_hcd:usb6, firewire_ohci
 18:          0          0   IO-APIC-fasteoi   uhci_hcd:usb7, r852, mmc0
 19:         31         32   IO-APIC-fasteoi   ehci_hcd:usb2
 20:         17         18   IO-APIC-fasteoi   uhci_hcd:usb3
 21:          0          0   IO-APIC-fasteoi   uhci_hcd:usb4
 22:          0          2   IO-APIC-fasteoi   ehci_hcd:usb1
 40:          0          0   PCI-MSI-edge      PCIe PME
 41:          0          0   PCI-MSI-edge      PCIe PME
 42:          0          0   PCI-MSI-edge      PCIe PME
 43:          0          0   PCI-MSI-edge      PCIe PME
 44:          0          0   PCI-MSI-edge      PCIe PME
 45:          0          0   PCI-MSI-edge      PCIe PME
 46:       6025       3786   PCI-MSI-edge      ahci
 47:         83          9   PCI-MSI-edge      eth0
 48:        550        192   PCI-MSI-edge      hda_intel
 49:          0          0   PCI-MSI-edge      iwlagn
NMI:        111         33   Non-maskable interrupts
LOC:     233900     147293   Local timer interrupts
SPU:          0          0   Spurious interrupts
PMI:        111         33   Performance monitoring interrupts
IWI:          0          0   IRQ work interrupts
RES:       1292       1333   Rescheduling interrupts
CAL:        155        208   Function call interrupts
TLB:        476        545   TLB shootdowns
TRM:          0          0   Thermal event interrupts
THR:          0          0   Threshold APIC interrupts
MCE:          0          0   Machine check exceptions
MCP:          2          2   Machine check polls
ERR:          1
MIS:          0

Looks normal to me, doesn’t it? Thanks!

Hi, I’m wondering if you solved this and if so how??

The ‘kworker load up’ issue crops up quite regularly but no solution seems to have been found for it

Hi, this is a good question. Actually, the problem suddenly disappeared. I have absolutely no explanation, it suddenly came up and magically disappeared again after like a week…
I am also curious what this might have been…

…to cut a very very long story short the first thing I now do is check user group membership - especially after an update.

if root runs fine or if the problem manifests itself* ‘on the road’ *then group membership might be too restrictive.

I ran into this recently and twigged only when all else failed - many hours later
[RIGHT]:shame:
[/RIGHT]