From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Soeren Sonnenburg <kernel@nn7.de>
Cc: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>,
"David S. Miller" <davem@redhat.com>
Subject: Re: 2.6.6 kernel oops on ifconfig eth0 mtu 1300
Date: Sun, 16 May 2004 19:19:03 +1000 [thread overview]
Message-ID: <1084699142.7777.10.camel@gaston> (raw)
In-Reply-To: <1084693466.4708.18.camel@localhost>
On Sun, 2004-05-16 at 17:44, Soeren Sonnenburg wrote:
> On Sun, 2004-05-16 at 03:05, Benjamin Herrenschmidt wrote:
> > On Sun, 2004-05-16 at 03:50, Soeren Sonnenburg wrote:
> > > Hi.
> > >
> > > When I have some ethernet connection and then do
> > > ifconfig eth0 mtu 1300 I get an immediate kernel panic (kernel 2.6.6)
> > > powerbook g4 15" 1ghz.
> > >
> > > (xmon trace (jpeg) on request)
> >
> > Yes, please, the trace
>
> doesn't it happen when you do ifconfig eth0 mtu 1300 ? anyway here it
> is: use a web-browser to view it (it is a redirect):
> http://www.nn7.de/kernel/mtu1300.jpg
Heh, didn't want to crash the laptop today. I CC'ed David Miller on that
as he is the main author of the driver.
David: the crash is apparently us doing skb_put of ETH_FRAME_LEN + RX_LEN,
so we tune the skb allocator to the MTU ? It's commented out in my bk
snapshot but then, I may be missing something. Should we change sungem to
use the mtu instead of ETH_FRAME_LEN ?
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2004-05-16 9:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-15 17:50 2.6.6 kernel oops on ifconfig eth0 mtu 1300 Soeren Sonnenburg
2004-05-16 1:05 ` Benjamin Herrenschmidt
2004-05-16 7:44 ` Soeren Sonnenburg
2004-05-16 9:19 ` Benjamin Herrenschmidt [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=1084699142.7777.10.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=davem@redhat.com \
--cc=kernel@nn7.de \
--cc=linuxppc-dev@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.