From: Chuck Ebbert <cebbert@redhat.com>
To: Auke Kok <auke-jan.h.kok@intel.com>
Cc: Netdev <netdev@vger.kernel.org>
Subject: e1000: assertion hit in e1000_clean(), kernel 2.6.21.1
Date: Fri, 18 May 2007 18:33:44 -0400 [thread overview]
Message-ID: <464E29C8.9090905@redhat.com> (raw)
We have several reports now of hitting this assertion in
netif_rx_complete(), inlined in e1000_clean():
BUG_ON(!test_bit(__LINK_STATE_RX_SCHED, &dev->state));
[<c0431162>] __queue_work+0x51/0x5e
[<c059eea1>] et_rx_action+0x94/0x185
[<c042837d>] __do_softirq+0x5d/0xba
[<c0407837>] do_softirq+0x59/0xb1
[<c04281e9>] local_bh_enable_ip+0x35/0x40
[<c059e46b>] dev_open+0x44/0x62
[<c059ce8c>] dev_change_flags+0x46/0xe3
[<c05d9e09>] devinet_ioctl+0x250/0x56a
The second function is "net_rx_action", corrupted
by the serial connection.
The source file has four extra lines at the top because of a
trivial wireless patch, so 898 in that code is really 894 in
the stock kernel.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=240339
next reply other threads:[~2007-05-18 22:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 22:33 Chuck Ebbert [this message]
2007-05-18 23:03 ` e1000: assertion hit in e1000_clean(), kernel 2.6.21.1 Kok, Auke
2007-05-18 23:18 ` Curtis Doty
2007-05-20 10:55 ` Herbert Xu
2007-05-20 19:03 ` Kok, Auke
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=464E29C8.9090905@redhat.com \
--to=cebbert@redhat.com \
--cc=auke-jan.h.kok@intel.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).