From: Harry McGregor <hmcgregor@espri.arizona.edu>
To: linux-kernel@vger.kernel.org
Subject: Strange issue with 2.6.0-test11 and magic packets
Date: Sun, 14 Dec 2003 17:03:19 -0700 [thread overview]
Message-ID: <1071446598.30538.6.camel@Sony> (raw)
Hi,
We have been having a strange issue while testing 2.6.0-test in one of
our computer labs (actually, it's a Debian GNU/Linux based lab in an
Elementary School!). The lab uses ether-wake to boot the computers,
which is of course a bios level thing, and works quite nicely.
The problem comes into play that when a computer happens to already be
booted when a magic packet is sent to it's MAC address, CPU load goes to
100%. top shows the usages as being [events]. We did not experience
this result of sending a magic packet while running 2.4.x kernels.
Hardware is Intel i815e motherboards in Compaq Deskpro systems. Intel
e100 driver built into the kernel.
If anyone can shed some light on where we should start looking, or any
tests you would like to see done, either follow up this post, or respond
to me directly.
Harry
reply other threads:[~2003-12-15 0:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1071446598.30538.6.camel@Sony \
--to=hmcgregor@espri.arizona.edu \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox