From: Andi Kleen <ak@suse.de>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: linux-kernel@vger.kernel.org, Vivek Goyal <vgoyal@in.ibm.com>
Subject: Re: Crash with SMP on post 2.6.15 -git kernel
Date: Thu, 12 Jan 2006 00:36:25 +0100 [thread overview]
Message-ID: <200601120036.26026.ak@suse.de> (raw)
In-Reply-To: <20060111145704.2cfbd44a@dxpl.pdx.osdl.net>
On Wednesday 11 January 2006 23:57, Stephen Hemminger wrote:
> On Wed, 11 Jan 2006 02:27:30 +0100
> Andi Kleen <ak@suse.de> wrote:
>
> > On Wednesday 11 January 2006 01:54, Stephen Hemminger wrote:
> > 6
> > > [ 37.047264] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)[ 37.070722] CPU: L2 Cache: 1024K (64 bytes/line)
> > > [ 37.085894] mtrr: v2.0 (20020519)
> > > [ 37.350186] Using local APIC timer interrupts.
> > > [ 37.414873] Detected 12.464 MHz APIC timer.
> > > [ 37.428717] Booting processor 1/2 APIC 0x1
> > >
> > > Machine then goes blank and reboots...
> >
> > Don't know what it could be - I didn't merge anything. Maybe revert the kexec patches?
> > Does the -git6 snapshot still work? Possibly do a binary search to narrow
> > it down.
> >
> > -Andi
> That was not the bad config. It turns out the problem is the new code
> for kdump. If CONFIG_KDUMP is turned on it crashes.
Ok thanks. I took a quick look and didn't saw anything obvious
below arch/x86_64 that could cause it. Maybe will try later again in a simulator
or Vivek will probably fix it when he wakes up again.
-Andi
next prev parent reply other threads:[~2006-01-11 23:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 0:54 Crash with SMP on post 2.6.15 -git kernel Stephen Hemminger
2006-01-11 1:27 ` Andi Kleen
2006-01-11 2:49 ` Stephen Hemminger
2006-01-11 9:32 ` Vivek Goyal
2006-01-11 11:12 ` Andi Kleen
2006-01-11 13:42 ` Vivek Goyal
2006-01-11 13:50 ` Andi Kleen
2006-01-11 14:03 ` Vivek Goyal
2006-01-12 0:05 ` Stephen Hemminger
2006-01-12 0:12 ` Andi Kleen
2006-01-11 22:57 ` Stephen Hemminger
2006-01-11 23:36 ` Andi Kleen [this message]
2006-01-11 23:44 ` Stephen Hemminger
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=200601120036.26026.ak@suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=shemminger@osdl.org \
--cc=vgoyal@in.ibm.com \
/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.