lkml.org 
[lkml]   [2005]   [Jan]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: 2.4.29, e100 and a WOL packet causes keventd going mad


    Michael Gernoth wrote:

    > Hi,
    >
    > we have about 70 P4 uniprocessor machines (some with Hyperthreading
    > capable CPUs) running linux 2.4.29, which are woken up on the weekdays
    > by sending a WOL packet to them. The machines all have a E100 nic with
    > WOL enabled in the bios. The E100 driver is compiled into the kernel
    > and not loaded as a module.
    >
    > If the machine which should be woken up is already running (because
    > someone switched it on by hand), the WOL packet causes keventd to go
    > mad and "use" 100% CPU:
    >
    > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
    > 2 root 15 0 0 0 0 R 99.9 0.0 140:50.94 keventd
    >
    > This can be reproduced on any of the 70 machines by simply sending a WOL
    > packet to it, when it's already running... No entry is made in the
    > kernel log.
    >
    > The dmesg of an affected machine can be found at:
    > http://wwwcip.informatik.uni-erlangen.de/~simigern/cip-dmesg
    > Our kernel-config is at:
    > http://wwwcip.informatik.uni-erlangen.de/~simigern/cip-generic-config
    > lspci -vvv is at:
    > http://wwwcip.informatik.uni-erlangen.de/~simigern/cip-lspci
    >
    > We are using a kernel.org linux 2.4.29 kernel patched with the current
    > autofs patch and ACL support.
    >
    > Regards,
    > Michael
    > -
    > 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/

    Do you know the official NIC product name e.g Pro/100B. I need to identify the LAN Controller. There are differences between 557 (not sure if 557 can do WOL), 558 and 559 how they ASSERT the PME# signal. Even the same chip have differences between steppings.

    I suspect that PME# is not being DEASSERT after the Wake-up packet is received
    -
    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:09    [W:0.022 / U:118.980 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site