From: Tachino Nobuhiro <tachino@open.nm.fujitsu.co.jp>
To: David Ford <david@blue-labs.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at slab.c:1244! (and slab.c:580)
Date: Thu, 12 Jul 2001 11:00:11 +0900 [thread overview]
Message-ID: <ofqqsy8k.wl@nisaaru.open.nm.fujitsu.co.jp> (raw)
In-Reply-To: <3B4C810A.8070500@blue-labs.org>
In-Reply-To: <3B4C810A.8070500@blue-labs.org>
Hello,
At Wed, 11 Jul 2001 12:38:34 -0400,
David Ford wrote:
>
> Hrm. Third time I've reported this, it's happened since the early 2.4
> kernels and I can get at least one every day or so. The odd thing is
> that the first oops normally happens within a couple hours after boot
> but it may take weeks before another oops will happen. The oops always
> has a trace similar to below. The second oops is new to me, it happened
> last night and I haven't seen it before, culled from syslog.
>
> # uname -r
> 2.4.5-ac15
2.4.5-ac19 fixes the minor tty layer bug which modifies the memory after
kfree() was called and it causes Oops if memory allocations debugging is enabled.
So, upgrading to newer kernel may fix your problem.
prev parent reply other threads:[~2001-07-12 2:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-11 16:38 David Ford
2001-07-12 2:00 ` Tachino Nobuhiro [this message]
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=ofqqsy8k.wl@nisaaru.open.nm.fujitsu.co.jp \
--to=tachino@open.nm.fujitsu.co.jp \
--cc=david@blue-labs.org \
--cc=linux-kernel@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®