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.
YB
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...
--
Boris B. Zhmurov
mailto: [email protected]
"wget http://kernelpanic.ru/bb_public_key.pgp -O - | gpg --import"
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 <[email protected]> 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...
>
>
> --
> Boris B. Zhmurov
> mailto: [email protected]
> "wget http://kernelpanic.ru/bb_public_key.pgp -O - | gpg --import"
>
>
this should be on netdev (cc'd), i included some of the thread here.
On 2/7/06, Yoseph Basri <[email protected]> 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 <[email protected]> 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 <[email protected]> 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
From: Jesse Brandeburg <[email protected]>
Date: Wed, 8 Feb 2006 12:07:14 -0800
> this should be on netdev (cc'd), i included some of the thread here.
...
> 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)
What are the changeset IDs so I can fix this?
Thanks.
On 2/8/06, David S. Miller <[email protected]> wrote:
> From: Jesse Brandeburg <[email protected]>
> Date: Wed, 8 Feb 2006 12:07:14 -0800
>
> > this should be on netdev (cc'd), i included some of the thread here.
> ...
> > 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)
>
> What are the changeset IDs so I can fix this?
I think the commit id that is missing from 2.6.14.X is
fb5f5e6e0cebd574be737334671d1aa8f170d5f3
but here is the web link if i gave the wrong info
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=fb5f5e6e0cebd574be737334671d1aa8f170d5f3
Hello, Jesse Brandeburg.
On 08.02.2006 23:07 you said the following:
> whats the relevance of e1000?
>
> I though Herbert had fixed these
Nope :( I had this messages on 2.6.14.2 and now I have it on 2.6.15.3.
--
Boris B. Zhmurov
mailto: [email protected]
"wget http://kernelpanic.ru/bb_public_key.pgp -O - | gpg --import"
On 2/10/06, Boris B. Zhmurov <[email protected]> wrote:
> Hello, Jesse Brandeburg.
>
> On 08.02.2006 23:07 you said the following:
>
> > whats the relevance of e1000?
> >
> > I though Herbert had fixed these
>
> Nope :( I had this messages on 2.6.14.2 and now I have it on 2.6.15.3.
>
For what it's worth I had these messages for a while and they got
fixed 2 or 3 weeks ago from memory in Dave's 2.6.16 net tree or net2.6
tree.
Is it possible for you to download 2.6.16-rc2 or similar and see if it
goes away?
Ian
--
Ian McDonald
http://wand.net.nz/~iam4
WAND Network Research Group
University of Waikato
New Zealand
Hello, Ian McDonald.
On 09.02.2006 22:25 you said the following:
> Is it possible for you to download 2.6.16-rc2 or similar and see if it
> goes away?
It'll be better, if I get only patch fixs that problem, not all 2.6.16-rc2.
--
Boris B. Zhmurov
mailto: [email protected]
"wget http://kernelpanic.ru/bb_public_key.pgp -O - | gpg --import"
On 2/10/06, Boris B. Zhmurov <[email protected]> wrote:
> Hello, Ian McDonald.
>
> On 09.02.2006 22:25 you said the following:
>
> > Is it possible for you to download 2.6.16-rc2 or similar and see if it
> > goes away?
>
> It'll be better, if I get only patch fixs that problem, not all 2.6.16-rc2.
>
Oops I didn't read Jesse's message earlier properly.
That patch which probably fixed it is (from his message):
I think the commit id that is missing from 2.6.14.X is
fb5f5e6e0cebd574be737334671d1aa8f170d5f3
but here is the web link if i gave the wrong info
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=fb5f5e6e0cebd574be737334671d1aa8f170d5f3
--
Ian McDonald
http://wand.net.nz/~iam4
WAND Network Research Group
University of Waikato
New Zealand
On 2006-02-09, Boris B. Zhmurov <[email protected]> wrote:
>
>> Is it possible for you to download 2.6.16-rc2 or similar and see if it
>> goes away?
>
> It'll be better, if I get only patch fixs that problem, not all 2.6.16-rc2.
I just got this same warning on a system running 2.6.14.5. It's been
up for 50 days, quite heavily loaded, and I've seen this only once.
Should i be conserned ? Could someone tell me what it means ?
# uname -a
Linux mail 2.6.14.5 #1 SMP Tue Dec 27 14:39:55 CET 2005 i686 i686 i386 GNU/Linux
# dmesg|grep KERNEL
KERNEL: assertion (!sk->sk_forward_alloc) failed at net/core/stream.c (279)
KERNEL: assertion (!sk->sk_forward_alloc) failed at net/ipv4/af_inet.c (148)
# ethtool -k eth0
Offload parameters for eth0:
rx-checksumming: on
tx-checksumming: on
scatter-gather: on
tcp segmentation offload: on
# ethtool -k eth1
Offload parameters for eth1:
rx-checksumming: on
tx-checksumming: on
scatter-gather: on
tcp segmentation offload: on
-jf
I have the same problem.
Upgraded to 2.6.16-rc5, the problem does not go away.
I also have intel nics and the e1000 driver. Upgraded to the latest
driver via intel website, that didn't fix it either.
The only fix is to turn "tcp segmentation offload" off. Not a good
solution.
Anyone got any idea? Is there a patch somewhere I can apply that
should fix this?
Regards,
Johan
From: Ian McDonald <[email protected]>
Date: Fri, 10 Feb 2006 08:37:48 +1300
> On 2/10/06, Boris B. Zhmurov <[email protected]> wrote:
> > Hello, Ian McDonald.
> >
> > On 09.02.2006 22:25 you said the following:
> >
> > > Is it possible for you to download 2.6.16-rc2 or similar and see if it
> > > goes away?
> >
> > It'll be better, if I get only patch fixs that problem, not all 2.6.16-rc2.
>
> Oops I didn't read Jesse's message earlier properly.
>
> That patch which probably fixed it is (from his message):
> I think the commit id that is missing from 2.6.14.X is
> fb5f5e6e0cebd574be737334671d1aa8f170d5f3
This patch is in the linux-2.6.14 stable tree, I just
verified this.
From: Jesse Brandeburg <[email protected]>
Date: Wed, 8 Feb 2006 18:10:21 -0800
> I think the commit id that is missing from 2.6.14.X is
> fb5f5e6e0cebd574be737334671d1aa8f170d5f3
It's in 2.6.14.x I just double checked.
On Fri, 10 Mar 2006, David S. Miller wrote:
> From: Ian McDonald <[email protected]>
> Date: Fri, 10 Feb 2006 08:37:48 +1300
>
>> On 2/10/06, Boris B. Zhmurov <[email protected]> wrote:
>>> Hello, Ian McDonald.
>>>
>>> On 09.02.2006 22:25 you said the following:
>>>
>>>> Is it possible for you to download 2.6.16-rc2 or similar and see if it
>>>> goes away?
>>>
>>> It'll be better, if I get only patch fixs that problem, not all 2.6.16-rc2.
>>
>> Oops I didn't read Jesse's message earlier properly.
>>
>> That patch which probably fixed it is (from his message):
>> I think the commit id that is missing from 2.6.14.X is
>> fb5f5e6e0cebd574be737334671d1aa8f170d5f3
>
> This patch is in the linux-2.6.14 stable tree, I just
> verified this.
So it must be another problem: I had this message with 2.6.15.2:
KERNEL: assertion (!sk->sk_forward_alloc) failed at net/core/stream.c (279)
KERNEL: assertion (!sk->sk_forward_alloc) failed at net/ipv4/af_inet.c (148)
Best regards,
Krzysztof Ol?dzki
> So it must be another problem: I had this message with 2.6.15.2:
>
> KERNEL: assertion (!sk->sk_forward_alloc) failed at net/core/stream.c (279)
> KERNEL: assertion (!sk->sk_forward_alloc) failed at net/ipv4/af_inet.c (148)
>
Confirmed in 2.6.15.6. Exactly the same assertion in kern.log from time to time
on all my boxes with this kernel. Previous posts mentioned possible relevance
with e1000 ethernet card. Well, all these boxes has e1000 too, which probably
means nothing.
--
Michal Feix