From: ebiederm@xmission.com (Eric W. Biederman)
To: Haren Myneni <haren@us.ibm.com>
Cc: linux-pm@lists.osdl.org, fastboot@lists.osdl.org, netdev@vger.kernel.org
Subject: Re: [Fastboot] Re: Re: tg3: issue for reboot/kexec
Date: Thu, 30 Jun 2005 19:27:51 -0600 [thread overview]
Message-ID: <m1r7ejjox4.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <42C499DD.3050009@us.ibm.com> (Haren Myneni's message of "Thu, 30 Jun 2005 18:18:21 -0700")
[-- Attachment #1: Type: text/plain, Size: 797 bytes --]
Haren Myneni <haren@us.ibm.com> writes:
> Eric W. Biederman wrote:
>
>>A couple stray bits of feedback. Downing the interface is generally
>>a user space requirement like unmounting filesystems.
>>/sbin/kexec and /sbin/reboot both perform this operation so I don't
>>see how this bug was hit.
>>
>>
>>
> Thanks for your feedback. We are still working on kexec tools for PPC64. In the
> mean time, I was using a temporary tool which does not do ifdown. I was in the
> impression that the kexec boot will be successful since the normal kexec code
> path (kernel/sys.c) contains device_shutdown/reboot notifier. It turns out I am
> wrong.
Buggy drivers will do that to you as well. But not doing a clean shutdown
(downing interfaces, and unmounting the filesystems) doesn't help things :)
Eric
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2005-07-01 1:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <42BC9F09.1060002@us.ibm.com>
2005-06-25 0:46 ` tg3: issue for reboot/kexec randy_dunlap
2005-06-25 3:33 ` Greg KH
2005-06-30 23:21 ` [Fastboot] " Eric W. Biederman
2005-06-30 23:33 ` Greg KH
2005-06-30 23:52 ` Eric W. Biederman
2005-08-18 18:30 ` Khalid Aziz
2005-08-18 18:35 ` Khalid Aziz
2005-08-18 18:42 ` Eric W. Biederman
2005-08-18 19:06 ` Khalid Aziz
2005-07-01 1:18 ` Haren Myneni
2005-07-01 1:27 ` Eric W. Biederman [this message]
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=m1r7ejjox4.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=fastboot@lists.osdl.org \
--cc=haren@us.ibm.com \
--cc=linux-pm@lists.osdl.org \
--cc=netdev@vger.kernel.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