From: Jes Sorensen <jes@wildopensource.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: netdev@oss.sgi.com
Subject: Re: acenic: Unhandled event 0x24
Date: 30 Jun 2004 01:41:01 -0400 [thread overview]
Message-ID: <yq0eknx4n82.fsf@wildopensource.com> (raw)
In-Reply-To: <20040629154751.20f4772a@dell_ss3.pdx.osdl.net>
>>>>> "Stephen" == Stephen Hemminger <shemminger@osdl.org> writes:
Stephen> When the acenic gigabit ether card is under lots of receive
Stephen> pressure, it generates many (not excessive) console output
Stephen> about Unhandled event 0x24
Stephen> I presume this is because the receive ring is getting over
Stephen> run and packet was dropped.
Weird!
This is another one thats not listed in the programming manual. I have
never seen it spew out event 0x24 messages, no idea what they are
for. If you want to add a patch to rate-limit it I would have no
objections.
Cheers,
Jes
prev parent reply other threads:[~2004-06-30 5:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-29 22:47 acenic: Unhandled event 0x24 Stephen Hemminger
2004-06-30 5:41 ` Jes Sorensen [this message]
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=yq0eknx4n82.fsf@wildopensource.com \
--to=jes@wildopensource.com \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.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;
as well as URLs for NNTP newsgroup(s).