From: Jesse Brandeburg <jesse.brandeburg@gmail.com>
To: Miquel van Smoorenburg <miquels@cistron.nl>, nipsy@bitgnome.net
Cc: linux-kernel@vger.kernel.org,
Kernel Netdev Mailing List <netdev@vger.kernel.org>
Subject: Re: KERNEL: assertion (!sk->sk_forward_alloc) failed
Date: Mon, 28 Nov 2005 08:44:05 -0800 [thread overview]
Message-ID: <4807377b0511280844w5ab2cb95y9955a62c0efe2f9d@mail.gmail.com> (raw)
In-Reply-To: <dmf1kn$t2s$1@news.cistron.nl>
This should really be on netdev, so I copied it.
On 11/28/05, Miquel van Smoorenburg <miquels@cistron.nl> wrote:
> In article <20051128123601.GA32346@king.bitgnome.net>,
> Mark Nipper <nipsy@bitgnome.net> wrote:
> > I received the following in my system logs recently:
> >---
> >Nov 27 22:56:20 king kernel: KERNEL: assertion (!sk->sk_forward_alloc)
> >failed at net/core/stream.c (279)
> >Nov 27 22:56:20 king kernel: KERNEL: assertion (!sk->sk_forward_alloc)
> >failed at net/ipv4/af_inet.c (151)
> >
> > All I could find related to this was some potential bugs
> >mentioned in 2.6.9 and in particular with relation to TSO.
> >However, I'm running a vanilla 2.6.13.4 at the moment. But, I do
> >have an e1000 and checking ethtool does show TSO on.
>
> I'm seeing the same on 2.6.14.2, also with e1000. It wasn't there on
> 2.6.11.12 which I was running previously.
I don't believe this is related to e1000 because we don't mess with
the sock (sk) struct. Did you try disabling TSO? I bet the netdev
guys can help.
next prev parent reply other threads:[~2005-11-28 16:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-28 12:36 Mark Nipper
2005-11-28 13:44 ` Miquel van Smoorenburg
2005-11-28 16:44 ` Jesse Brandeburg [this message]
2006-02-07 9:46 Yoseph Basri
2006-02-07 10:32 ` Boris B. Zhmurov
2006-02-08 3:02 ` Yoseph Basri
2006-02-08 20:07 ` Jesse Brandeburg
2006-02-08 22:12 ` David S. Miller
2006-02-09 2:10 ` Jesse Brandeburg
2006-03-10 10:59 ` David S. Miller
2006-02-09 19:17 ` Boris B. Zhmurov
2006-02-09 19:25 ` Ian McDonald
2006-02-09 19:32 ` Boris B. Zhmurov
2006-02-09 19:37 ` Ian McDonald
2006-03-10 10:59 ` David S. Miller
2006-03-10 15:51 ` Krzysztof Oledzki
2006-03-12 10:30 ` Michal Feix
2006-02-16 21:02 ` Jan-Frode Myklebust
2006-03-03 6:12 Johan Lundgren
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=4807377b0511280844w5ab2cb95y9955a62c0efe2f9d@mail.gmail.com \
--to=jesse.brandeburg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miquels@cistron.nl \
--cc=netdev@vger.kernel.org \
--cc=nipsy@bitgnome.net \
/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
all inboxes | Powered by JetHome®