Fw: throttling kernel messages: KERNEL: assertion (flags & MSG_PEEK) failed at net/ipv4/tcp.c (1282)

Fw: throttling kernel messages: KERNEL: assertion (flags & MSG_PEEK) failed at net/ipv4/tcp.c (1282)

[Randy.Dunlap]

FYI.


Begin forwarded message:

Date: Tue, 12 Apr 2005 11:41:48 +0200
From: "Ulrich Windl" <ulrich.windl@rz.uni-regensburg.de>
To: linux-kernel@vger.kernel.org
Subject: throttling kernel messages: KERNEL: assertion (flags & MSG_PEEK) failed at net/ipv4/tcp.c (1282)


Hi,

I'm affected by the (in)famous bug:
Apr 12 07:03:02 mailgate kernel: recvmsg bug: copied D640F0D1 seq D640F679
Apr 12 07:03:02 mailgate kernel: KERNEL: assertion (flags & MSG_PEEK) failed at 
net/ipv4/tcp.c (1282)
Apr 12 07:03:02 mailgate kernel: recvmsg bug: copied D640F0D1 seq D640F679
Apr 12 07:03:02 mailgate kernel: KERNEL: assertion (flags & MSG_PEEK) failed at 
net/ipv4/tcp.c (1282)

(Kernel of SuSE Linux 9.2, 2.6.8-24.13-default #1 Fri Mar 18 10:19:42 UTC 2005 
i686 i686 i386 GNU/Linux)

The kernel spits out hundreds to thousand messages per second, making klogd and 
syslogd quite busy, and my messages file stopped growing at 2GB.

I'd suggest to enable throttling for this message, or trigger a panic/reboot, or 
maybe even fix the bug or message. ;-)

Regards,
Ulrich

-

Re: Fw: throttling kernel messages: KERNEL: assertion (flags & MSG_PEEK) failed at net/ipv4/tcp.c (1282)

[David S. Miller]

On Tue, 12 Apr 2005 11:41:48 -0700
"Randy.Dunlap" <rddunlap@osdl.org> wrote:

> 
> FYI.

2.6.8, he needs to upgrade :-)

Re: Fw: throttling kernel messages: KERNEL: assertion (flags & MSG_PEEK) failed at net/ipv4/tcp.c (1282)

[KOVACS Krisztian]

  Hi,

On Tue, 2005-04-12 at 11:41 -0700, Randy.Dunlap wrote:
> I'm affected by the (in)famous bug:
> Apr 12 07:03:02 mailgate kernel: recvmsg bug: copied D640F0D1 seq D640F679
> Apr 12 07:03:02 mailgate kernel: KERNEL: assertion (flags & MSG_PEEK) failed at 
> net/ipv4/tcp.c (1282)
> Apr 12 07:03:02 mailgate kernel: recvmsg bug: copied D640F0D1 seq D640F679
> Apr 12 07:03:02 mailgate kernel: KERNEL: assertion (flags & MSG_PEEK) failed at 
> net/ipv4/tcp.c (1282)
> 
> (Kernel of SuSE Linux 9.2, 2.6.8-24.13-default #1 Fri Mar 18 10:19:42 UTC 2005 
> i686 i686 i386 GNU/Linux)
> 
> The kernel spits out hundreds to thousand messages per second, making klogd and 
> syslogd quite busy, and my messages file stopped growing at 2GB.
> 
> I'd suggest to enable throttling for this message, or trigger a panic/reboot, or 
> maybe even fix the bug or message. ;-)

  I also hit these assertions today. In my case it was probably because
of a slab corruption problem caused by the e100 driver. (I had
CONFIG_DEBUG_SLAB enabled, so a lot of slab corruption messages appeared
right before these assertion errors.)

  After applying e100-napi-fixes.patch from 2.6.11-mm4 the problem semms
to be gone.

-- 
  Krisztian Kovacs

Re: Fw: throttling kernel messages: KERNEL: assertion (flags & MSG_PEEK) failed at net/ipv4/tcp.c (1282)

[Olaf Kirch]

On Tue, Apr 12, 2005 at 10:18:50PM +0200, KOVACS Krisztian wrote:
>   I also hit these assertions today. In my case it was probably because
> of a slab corruption problem caused by the e100 driver. (I had
> CONFIG_DEBUG_SLAB enabled, so a lot of slab corruption messages appeared
> right before these assertion errors.)

Yes, we've seen these symptoms in various bug reports in various 2.6
versions, and after some debugging narrowed it down to an e100 driver
issue. It went away with 2.6.11 final.

>   After applying e100-napi-fixes.patch from 2.6.11-mm4 the problem semms
> to be gone.

Ah, I'll look into that one. Thanks for the pointer!

Olaf
-- 
Olaf Kirch   |  --- o --- Nous sommes du soleil we love when we play
okir@suse.de |    / | \   sol.dhoop.naytheet.ah kin.ir.samse.qurax

Re: Fw: throttling kernel messages: KERNEL: assertion (flags & MSG_PEEK) failed at net/ipv4/tcp.c (1282)

[KOVACS Krisztian]

  Hi,

2005-04-12, k keltezéssel 22.39-kor Olaf Kirch ezt írta:
> >   I also hit these assertions today. In my case it was probably because
> > of a slab corruption problem caused by the e100 driver. (I had
> > CONFIG_DEBUG_SLAB enabled, so a lot of slab corruption messages appeared
> > right before these assertion errors.)
> 
> Yes, we've seen these symptoms in various bug reports in various 2.6
> versions, and after some debugging narrowed it down to an e100 driver
> issue. It went away with 2.6.11 final.

  For me it definitely did not go away with 2.6.11. However, as soo as I
applied e100-napi-fixes.patch the problem magically disappeared. So I
suspect this NAPI state machine problem might have been the culprit.

-- 
 Regards,
  Krisztian Kovacs

RE: Fw: throttling kernel messages: KERNEL: assertion (flags &MSG_PEEK) failed at net/ipv4/tcp.c (1282)

[Brandeburg, Jesse]

>From: netdev-bounce@oss.sgi.com [mailto:netdev-bounce@oss.sgi.com] On
>Behalf Of KOVACS Krisztian
>2005-04-12, k keltezéssel 22.39-kor Olaf Kirch ezt írta:
>> >   I also hit these assertions today. In my case it was probably because
>> > of a slab corruption problem caused by the e100 driver. (I had
>> > CONFIG_DEBUG_SLAB enabled, so a lot of slab corruption messages
>appeared
>> > right before these assertion errors.)
>>
>> Yes, we've seen these symptoms in various bug reports in various 2.6
>> versions, and after some debugging narrowed it down to an e100 driver
>> issue. It went away with 2.6.11 final.
>
>  For me it definitely did not go away with 2.6.11. However, as soo as I
>applied e100-napi-fixes.patch the problem magically disappeared. So I
>suspect this NAPI state machine problem might have been the culprit.
>

This was the exact failure mode of this e100 bug.  It would exhibit with slab corruption, only when in NAPI mode.  Glad it fixed your issue as well.

Jesse