From: ebiederm@xmission.com (Eric W. Biederman)
To: Dave Lloyd <dave@davelloyd.com>
Cc: kexec@lists.infradead.org
Subject: Re: Kernel panics when using kexec for rebooting
Date: Tue, 14 May 2013 15:01:06 -0700 [thread overview]
Message-ID: <87k3n1w7a5.fsf@xmission.com> (raw)
In-Reply-To: <CAKw_n9E=Hf0=ao1+tjbarHhQoJUdw70xhTUFaY_s4g3OARpdMg@mail.gmail.com> (Dave Lloyd's message of "Mon, 13 May 2013 10:40:09 -0500")
Dave Lloyd <dave@davelloyd.com> writes:
> All:
>
> I seem to be able to relatively reliably panic a system when using
> kexec to reboot. This does not happen during a normal boot sequence.
> Unfortunately, the stack trace I get for the panic is not consistent.
> I've included a few here. Mostly they seem to center on what smells
> like some sort of memory corruption to me. I'm kind of banging my head
> against the wall with this, so any help would be greatly appreciated.
Yes this does seem to be all over the place, and memory corruption
probably caused by ongoing-dma seems like a reasonable hypothesis.
The easy first thing to try is to remove all of your kernel modules
before you reboot with kexec. Not infrequently the module remove path
is better tested than the device shutdown path.
Eric
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2013-05-14 22:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 15:40 Kernel panics when using kexec for rebooting Dave Lloyd
2013-05-14 22:01 ` Eric W. Biederman [this message]
2013-05-14 22:25 ` Dave Lloyd
2013-05-14 22:33 ` Eric W. Biederman
2013-05-14 22:57 ` Dave Lloyd
2013-05-14 23:14 ` Eric W. Biederman
2013-05-15 15:50 ` Dave Lloyd
2013-05-15 16:53 ` Eric W. Biederman
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=87k3n1w7a5.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=dave@davelloyd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox