All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Tobias Winter <tobias@linuxdingsda.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel bug report 2.6.24-rc8 on core2quad q6600 with debian unstable amd64
Date: Wed, 23 Jan 2008 17:07:48 -0800	[thread overview]
Message-ID: <20080123170748.36068472@deepthought> (raw)
In-Reply-To: <4797D86B.3060202@linuxdingsda.de>

On Thu, 24 Jan 2008 01:14:35 +0100
Tobias Winter <tobias@linuxdingsda.de> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
> 
> Hi folks, I'm sending the bug report here, since i have no idea where
> else to send it. I hope it is helping.
> 
> 
> [1.] One line summary of the problem:
> The kernel panics under high CPU/IO load, compilers segfault, mdadm
> used to do so, too.
> 
> [2.] Full description of the problem/report:
> I upgraded my system to fairly new hardware and find myself unable to
> compile any kernel source and the system panics under high load e.g.
> resyncing a RAID or building a kernel. Building kernel is 100% sure to
> result in a kernel panic.

Sounds like bad memory. Run memtest for at least 24hrs.

  reply	other threads:[~2008-01-24  1:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-24  0:14 kernel bug report 2.6.24-rc8 on core2quad q6600 with debian unstable amd64 Tobias Winter
2008-01-24  1:07 ` Stephen Hemminger [this message]
2008-01-24 14:45   ` Lennart Sorensen
2008-01-25 10:17     ` [resolved] " Tobias Winter
2008-01-25 14:25       ` Lennart Sorensen
2008-01-25 17:20         ` Valdis.Kletnieks
2008-01-24  1:15 ` Roland Dreier
2008-01-24 11:21   ` Tobias Winter

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=20080123170748.36068472@deepthought \
    --to=shemminger@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tobias@linuxdingsda.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.