From: Bernhard Walle <bwalle@suse.de>
To: Tony Luck <tony.luck@intel.com>
Cc: jlan@sgi.com, linux-ia64@vger.kernel.org, kexec@lists.infradead.org
Subject: Re: kdump broken on Altix 350
Date: Fri, 29 Aug 2008 16:05:31 +0000 [thread overview]
Message-ID: <20080829180531.0524a1e4@halley.suse.de> (raw)
In-Reply-To: <20080829180302.6e67c26e@halley.suse.de>
* Bernhard Walle [2008-08-29 18:03]:
>
> 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:
Ah, and the kexec call was
/sbin/kexec -p /boot/vmlinuz-2.6.27-rc2-default --append="
root=/dev/disk/by-id/scsi-SATA_HDS722580VLSA80_VNRB3KC2CZY0RL-part4
kdb=on sysrq=1 console=tty1 console=ttySG0,38400 thash_entries 97152
elevatorfiadline sysrq=1 reset_devices irqpoll maxcpus=1 "
--initrd=/boot/initrd-2.6.27-rc2-default-kdump --noio
The interesting thing should be the kernel command line here.
Bernhard
--
Bernhard Walle, SUSE Linux Products GmbH, Architecture Development
--
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-08-29 16:05 UTC|newest]
Thread overview: 13+ 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:05 ` Bernhard Walle [this message]
2008-08-29 20:42 ` Luck, Tony
2008-08-29 20:48 ` Bernhard Walle
2008-09-10 11:48 ` Bernhard Walle
2008-09-10 20:21 ` Jay Lan
2008-09-27 1:00 ` Jay Lan
2008-09-29 20:55 ` Luck, Tony
2008-09-10 12:19 ` Bernhard Walle
2008-09-29 23:42 ` Luck, Tony
2008-09-30 0:30 ` Jay Lan
2008-10-02 5:13 ` Simon Horman
2008-10-02 17:04 ` Jay Lan
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=20080829180531.0524a1e4@halley.suse.de \
--to=bwalle@suse.de \
--cc=jlan@sgi.com \
--cc=kexec@lists.infradead.org \
--cc=linux-ia64@vger.kernel.org \
--cc=tony.luck@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox