From: "David S. Miller" <davem@davemloft.net>
To: kloczek@rudy.mif.pg.gda.pl
Cc: linux-kernel@vger.kernel.org, davem@redhat.com,
sparclinux@vger.kernel.org,
aurora-sparc-devel@lists.auroralinux.org
Subject: Re: [2.6.13-rc6-git13/sparc64]: Slab corruption (possible stack or buffer-cache corruption)
Date: Tue, 13 Sep 2005 13:08:42 -0700 (PDT) [thread overview]
Message-ID: <20050913.130842.52078742.davem@davemloft.net> (raw)
In-Reply-To: <Pine.BSO.4.62.0509131148020.5000@rudy.mif.pg.gda.pl>
From: Tomasz Kłoczko <kloczek@rudy.mif.pg.gda.pl>
Date: Tue, 13 Sep 2005 12:12:22 +0200 (CEST)
> # grep "^Sep 12" /var/log/messages | grep kernel: | uniq | cut -d " " -f 6- | sort | uniq -c | sort -n | tail -n 2
> 509 svc: bad direction 268435456, dropping request
> 653 eth0: Happy Meal out of receive descriptors, packet dropped.
>
> As you see one of this two messagess occures avarange one time per ~two
> minutes.
> Second looks like some error in sunhme.c. eth0 it is:
It's not a bug, per se, your system is simply receiving more
network traffic than the kernel can receive. So the network
adapter runs out of receive descriptors in which to receive
new packets, and starts dropping them until the kernel catches
up again. That's what that message means.
The "svc: " one I've seen before, it looks like something is
clobbering the sunrpc message, for example a freed up buffer is having
some bit set in one of it's words. This 268435456 value is
"0x10000000" hexadecimal. The code expects the value zero, and we
have a stray bit being set in there, bit 28 to be exact. This would
actually be expected after you trigger something like that
destroy_inode() bug as a buffer is being free'd up twice.
next prev parent reply other threads:[~2005-09-13 20:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-12 14:37 Tomasz Kłoczko
2005-09-12 14:45 ` [Aurora-sparc-devel] " Tom 'spot' Callaway
2005-09-12 15:39 ` Tomasz Kłoczko
2005-09-12 20:41 ` David S. Miller
2005-09-12 20:45 ` Tom 'spot' Callaway
2005-09-12 23:13 ` David S. Miller
2005-09-13 10:12 ` Tomasz Kłoczko
2005-09-13 20:08 ` David S. Miller [this message]
2005-09-14 11:16 ` Tomasz Kłoczko
2005-09-14 11:40 ` Tomasz Kłoczko
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=20050913.130842.52078742.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=aurora-sparc-devel@lists.auroralinux.org \
--cc=davem@redhat.com \
--cc=kloczek@rudy.mif.pg.gda.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.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
all inboxes | Powered by JetHome®