From: Jesse Brandeburg <jesse.brandeburg@gmail.com>
To: Yoseph Basri <yoseph.basri@gmail.com>,
"Boris B. Zhmurov" <bb@kernelpanic.ru>
Cc: linux-kernel@vger.kernel.org, NetDEV list <netdev@vger.kernel.org>
Subject: Re: KERNEL: assertion (!sk->sk_forward_alloc) failed
Date: Wed, 8 Feb 2006 12:07:14 -0800 [thread overview]
Message-ID: <4807377b0602081207s7604eceahb8bf4af6715a6534@mail.gmail.com> (raw)
In-Reply-To: <e282236e0602070146p1ed3fdb6k74aa75e15bbc37a3@mail.gmail.com>
this should be on netdev (cc'd), i included some of the thread here.
On 2/7/06, Yoseph Basri <yoseph.basri@gmail.com> wrote:
> Hello kernel maillist,
>
> I'm new member maillist.
>
> Currently, I receive the warning log from my kernel.
>
> Since update to
> Linux 2.6.14.3 #1 SMP Fri Nov 25 20:20:05 SGT 2005 i686 GNU/Linux from 2.4,
>
> I am getting the warning log:
>
> kernel: KERNEL: assertion (!sk->sk_forward_alloc) failed at
> net/core/stream.c (279)
> kernel: KERNEL: assertion (!sk->sk_forward_alloc) failed at
> net/ipv4/af_inet.c (148)
>
> Any information about this issue, and how to solve this problem ?
>
> Another server that i rolled back from 2.6.14 to 2.4 kernel and has no
> warning again. is this bug from 2.6 kernel?
>
> Thanks for your info.
On 2/7/06, Yoseph Basri <yoseph.basri@gmail.com> wrote:
> Hi Boris,
>
> I think so, here is from the dmeg info:
>
> Intel(R) PRO/1000 Network Driver - version 6.0.60-k2
> Copyright (c) 1999-2005 Intel Corporation.
> ACPI: PCI Interrupt 0000:06:08.0[A] -> GSI 29 (level, low) -> IRQ 16
> e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
> ACPI: PCI Interrupt 0000:06:08.1[B] -> GSI 30 (level, low) -> IRQ 17
> e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection
> e100: Intel(R) PRO/100 Network Driver, 3.4.14-k2-NAPI
> e100: Copyright(c) 1999-2005 Intel Corporation
>
> any info regarding this warning?
>
> YB
>
> On 2/7/06, Boris B. Zhmurov <bb@kernelpanic.ru> wrote:
> > Hello, Yoseph Basri.
> >
> > On 07.02.2006 12:46 you said the following:
> >
> > > I am getting the warning log:
> > >
> > > kernel: KERNEL: assertion (!sk->sk_forward_alloc) failed at
> > > net/core/stream.c (279)
> > > kernel: KERNEL: assertion (!sk->sk_forward_alloc) failed at
> > > net/ipv4/af_inet.c (148)
> >
> >
> > Do you have Intel Pro 1000 network card? Same here...
whats the relevance of e1000?
I though Herbert had fixed these, and it looks like half the patches
got into 2.6.14.3, but not the fix to the fix committed on 9-6 (not in
2.6.14.* at all)
Jesse
next prev parent reply other threads:[~2006-02-08 20:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2006-03-03 6:12 Johan Lundgren
2005-11-28 12:36 Mark Nipper
2005-11-28 13:44 ` Miquel van Smoorenburg
2005-11-28 16:44 ` Jesse Brandeburg
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=4807377b0602081207s7604eceahb8bf4af6715a6534@mail.gmail.com \
--to=jesse.brandeburg@gmail.com \
--cc=bb@kernelpanic.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yoseph.basri@gmail.com \
/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®