mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Sven Lauritzen <the-pulse@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] at mm/slab.c:1235! (Version 2.6.15)
Date: Wed, 18 Jan 2006 14:22:19 +0200	[thread overview]
Message-ID: <84144f020601180422q78ecdf37mb8b8e9d1f40039d1@mail.gmail.com> (raw)
In-Reply-To: <1137582956.1774.15.camel@berlin.slsd>

Hi,

On 1/18/06, Sven Lauritzen <the-pulse@gmx.net> wrote:
> Last night my machine crashed and I found this report in the syslog.
> Kernel version is 2.6.15 vanilla. I've pasted .config and lspci -vvv
> output. Please let me know if you need more information. I hope this is
> the right place to drop the report.

Try enabling CONFIG_DEBUG_SLAB and CONFIG_DEBUG_PAGEALLOC to see if
they pick up anything.

On 1/18/06, Sven Lauritzen <the-pulse@gmx.net> wrote:
> Jan 18 06:27:16 berlin kernel: kernel BUG at mm/slab.c:1235!
> Jan 18 06:27:16 berlin kernel: invalid operand: 0000 [#1]
> Jan 18 06:27:16 berlin kernel: PREEMPT
> Jan 18 06:27:16 berlin kernel: Modules linked in: snd_ens1371
> snd_ac97_codec snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi
> snd_seq_midi_event snd_seq snd_seq_device snd_ac97_bus
> Jan 18 06:27:16 berlin kernel: CPU:    0
> Jan 18 06:27:16 berlin kernel: EIP:    0060:[<c013f4bd>]    Not tainted
> VLI
> Jan 18 06:27:16 berlin kernel: EFLAGS: 00010046   (2.6.15)
> Jan 18 06:27:16 berlin kernel: EIP is at kmem_freepages+0x3d/0xa0

I don't quite see how this could happen. Is the box otherwise stable?
Have you run memtest86 on it?

                             Pekka

  reply	other threads:[~2006-01-18 12:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-18 11:15 Sven Lauritzen
2006-01-18 12:22 ` Pekka Enberg [this message]
2006-01-18 13:41   ` Sven Lauritzen
2006-01-18 13:54     ` Pekka J Enberg
2006-01-21 13:20       ` Sven Lauritzen

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=84144f020601180422q78ecdf37mb8b8e9d1f40039d1@mail.gmail.com \
    --to=penberg@cs.helsinki.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=the-pulse@gmx.net \
    /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®