netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Kirch <okir@suse.de>
To: KOVACS Krisztian <hidden@balabit.hu>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>, netdev <netdev@oss.sgi.com>
Subject: Re: Fw: throttling kernel messages: KERNEL: assertion (flags & MSG_PEEK) failed at net/ipv4/tcp.c (1282)
Date: Tue, 12 Apr 2005 22:39:50 +0200	[thread overview]
Message-ID: <20050412203950.GA9964@suse.de> (raw)
In-Reply-To: <1113337130.3004.14.camel@krak.odu>

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

  reply	other threads:[~2005-04-12 20:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-12 18:41 Fw: throttling kernel messages: KERNEL: assertion (flags & MSG_PEEK) failed at net/ipv4/tcp.c (1282) Randy.Dunlap
2005-04-12 19:35 ` David S. Miller
2005-04-12 20:18 ` KOVACS Krisztian
2005-04-12 20:39   ` Olaf Kirch [this message]
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=20050412203950.GA9964@suse.de \
    --to=okir@suse.de \
    --cc=hidden@balabit.hu \
    --cc=netdev@oss.sgi.com \
    --cc=rddunlap@osdl.org \
    /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).