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 16:14:33 -0700 [thread overview]
Message-ID: <87k3n1rw6e.fsf@xmission.com> (raw)
In-Reply-To: <CAKw_n9FKo8Uz+pPpC7Qu78H-mE5WJebZ7wJEDK7g6y6=H68yRw@mail.gmail.com> (Dave Lloyd's message of "Tue, 14 May 2013 17:57:26 -0500")
Dave Lloyd <dave@davelloyd.com> writes:
> On Tue, May 14, 2013 at 5:33 PM, Eric W. Biederman
> <ebiederm@xmission.com> wrote:
>> Dave Lloyd <dave@davelloyd.com> writes:
>>
>>> On Tue, May 14, 2013 at 5:01 PM, Eric W. Biederman
>>> <ebiederm@xmission.com> wrote:
>>>
>>>>
>>>> Yes this does seem to be all over the place, and memory corruption
>>>> probably caused by ongoing-dma seems like a reasonable hypothesis.
>>>
>>> Thank goodness it's not just me! :-)
>>
>> It is a classic issue, although I suspect something is unique in your
>> setup because it has (to my knowledge) not been a widespread problem for
>> years.
>
> It could certainly be buggy hardware. Other details include:
>
> Kernel 3.0.29.0 and we are also using infiniband (which I believe I
> found a reference to the Mellanox hardware potentially causing this
> issue unless the driver was unloaded before reboot with kexec). The
> potential issue with unloading the IB drivers doesn't bug me nearly as
> much as not unloading pata_amd and pata_acpi causing the ACPI Error
> messages upon reboot with kexec.
Oh. Yeah. IB definitely sets up memory for ongoing dma. So if it
doesn't have a shutdown method and IB traffic comes in during boot just
about anything cood happen.
> I'm inclined to chalk the ACPI Error mesages up to potentially buggy
> BIOS/hardware from the vendor since pata_amd and pata_acpi are in wide
> use and I would expect to see more issues reported were there truly an
> issue with rebooting with kexec and not unloading pata_amd and
> pata_acpi.
Maybe. Or it might be luck of timing, which memory was stomped when
incomming IB packets stomped on memory.
Eric
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2013-05-14 23:15 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
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 [this message]
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=87k3n1rw6e.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 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.