From: Bernhard Walle <bwalle@suse.de>
To: kexec@lists.infradead.org, jlan@sgi.com
Subject: Re: kdump broken on Altix 350
Date: Wed, 10 Sep 2008 13:48:05 +0200 [thread overview]
Message-ID: <20080910134805.488b43f9@kepler.site> (raw)
In-Reply-To: <57C9024A16AD2D4C97DC78E552063EA30A0067D6@orsmsx505.amr.corp.intel.com>
* "Luck, Tony" <tony.luck@intel.com> [2008-08-29]:
> > your commit
> >
> > commit 10617bbe84628eb18ab5f723d3ba35005adde143
> > Author: Tony Luck <tony.luck@intel.com>
> > Date: Tue Aug 12 10:34:20 2008 -0700
> >
> > [IA64] Ensure cpu0 can access per-cpu variables in early boot
> > code
> >
> > broke kdump on our Altix 350. I get following early crash in kdump
> > kernel
>
> Sorry about that. I'll try to reproduce it here.
I had some discussion about that with Jay Lan that he could not
reproduce that on his machine. We thought it was different config, but
now I can verify that the problem is reproducible here with the default
configuration (plus CONFIG_SATA_VITESSE).
Bernhard
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Bernhard Walle <bwalle@suse.de> (by way of Bernhard Walle
To: kexec@lists.infradead.org, jlan@sgi.com
Subject: Re: kdump broken on Altix 350
Date: Wed, 10 Sep 2008 11:48:05 +0000 [thread overview]
Message-ID: <20080910134805.488b43f9@kepler.site> (raw)
In-Reply-To: <57C9024A16AD2D4C97DC78E552063EA30A0067D6@orsmsx505.amr.corp.intel.com>
* "Luck, Tony" <tony.luck@intel.com> [2008-08-29]:
> > your commit
> >
> > commit 10617bbe84628eb18ab5f723d3ba35005adde143
> > Author: Tony Luck <tony.luck@intel.com>
> > Date: Tue Aug 12 10:34:20 2008 -0700
> >
> > [IA64] Ensure cpu0 can access per-cpu variables in early boot
> > code
> >
> > broke kdump on our Altix 350. I get following early crash in kdump
> > kernel
>
> Sorry about that. I'll try to reproduce it here.
I had some discussion about that with Jay Lan that he could not
reproduce that on his machine. We thought it was different config, but
now I can verify that the problem is reproducible here with the default
configuration (plus CONFIG_SATA_VITESSE).
Bernhard
next prev parent reply other threads:[~2008-09-10 11:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-29 16:03 kdump broken on Altix 350 Bernhard Walle
2008-08-29 16:03 ` Bernhard Walle
2008-08-29 16:05 ` Bernhard Walle
2008-08-29 16:05 ` Bernhard Walle
2008-08-29 20:42 ` Luck, Tony
2008-08-29 20:42 ` Luck, Tony
2008-08-29 20:48 ` Bernhard Walle
2008-08-29 20:48 ` Bernhard Walle
2008-09-10 11:48 ` Bernhard Walle [this message]
2008-09-10 11:48 ` Bernhard Walle
2008-09-10 20:21 ` Jay Lan
2008-09-10 20:21 ` Jay Lan
2008-09-27 1:00 ` Jay Lan
2008-09-27 1:00 ` Jay Lan
2008-09-29 20:55 ` Luck, Tony
2008-09-29 20:55 ` Luck, Tony
2008-09-29 23:42 ` Luck, Tony
2008-09-29 23:42 ` Luck, Tony
2008-09-30 0:30 ` Jay Lan
2008-09-30 0:30 ` Jay Lan
2008-10-02 5:13 ` Simon Horman
2008-10-02 5:13 ` Simon Horman
2008-10-02 17:04 ` Jay Lan
2008-10-02 17:04 ` Jay Lan
2008-09-10 12:19 ` Bernhard Walle
2008-09-10 12:19 ` Bernhard Walle
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=20080910134805.488b43f9@kepler.site \
--to=bwalle@suse.de \
--cc=jlan@sgi.com \
--cc=kexec@lists.infradead.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 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.