From: "Randy.Dunlap" <rddunlap@osdl.org>
To: netdev <netdev@oss.sgi.com>
Subject: Fw: throttling kernel messages: KERNEL: assertion (flags & MSG_PEEK) failed at net/ipv4/tcp.c (1282)
Date: Tue, 12 Apr 2005 11:41:48 -0700 [thread overview]
Message-ID: <20050412114148.66283c58.rddunlap@osdl.org> (raw)
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
-
next reply other threads:[~2005-04-12 18:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 18:41 Randy.Dunlap [this message]
2005-04-12 19:35 ` Fw: throttling kernel messages: KERNEL: assertion (flags & MSG_PEEK) failed at net/ipv4/tcp.c (1282) David S. Miller
2005-04-12 20:18 ` KOVACS Krisztian
2005-04-12 20:39 ` Olaf Kirch
2005-04-13 7:50 ` KOVACS Krisztian
-- strict thread matches above, loose matches on Subject: below --
2005-04-13 16:06 Fw: throttling kernel messages: KERNEL: assertion (flags &MSG_PEEK) " Brandeburg, Jesse
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=20050412114148.66283c58.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).