netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: Francois Romieu <romieu@fr.zoreil.com>, netdev@oss.sgi.com
Subject: Re: r8169: panic on 2.6.11
Date: Fri, 04 Mar 2005 16:37:39 -0500	[thread overview]
Message-ID: <4228D523.2070703@pobox.com> (raw)
In-Reply-To: <20050304132804.270cf05b@dxpl.pdx.osdl.net>

Stephen Hemminger wrote:
> I was intentionally over stressing r8169 without NAPI to test out
> an alternative version of netif_rx, and discovered the following bug.
> Looks like a problem in r8169. I was using pktgen to overwhelm the r8169
> from a fast machine.

Does 2.6.10 fail in a similar manner?


> eth0: Too much work at interrupt!
> eth0: Too much work at interrupt!
> ------------[ cut here ]------------
> kernel BUG at net/core/skbuff.c:91!

Any idea what this BUG actually means?  Since it's in skb_over_panic(), 
a function designed to do nothing but BUG(), that doesn't tell us a 
whole lot about the callsite.

	Jeff

  reply	other threads:[~2005-03-04 21:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-04 21:28 r8169: panic on 2.6.11 Stephen Hemminger
2005-03-04 21:37 ` Jeff Garzik [this message]
2005-03-04 21:50   ` Francois Romieu
     [not found]     ` <20050304135922.0b0a3911@dxpl.pdx.osdl.net>
     [not found]       ` <20050304221826.GA1028@electric-eye.fr.zoreil.com>
2005-03-04 22:53         ` Stephen Hemminger
2005-03-04 23:02           ` Francois Romieu
2005-03-04 23:28             ` Jon Mason
2005-03-04 23:49               ` Stephen Hemminger
2005-03-05  0:37                 ` Francois Romieu
2005-03-05  5:03                   ` Jon Mason
2005-03-05  6:34                     ` Stephen Hemminger
2005-03-07 18:59                   ` Stephen Hemminger
2005-03-04 23:58               ` Francois Romieu
2005-03-04 21:39 ` Francois Romieu

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=4228D523.2070703@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=netdev@oss.sgi.com \
    --cc=romieu@fr.zoreil.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).