From mboxrd@z Thu Jan 1 00:00:00 1970 From: Haren Myneni Subject: Re: [Fastboot] Re: Re: tg3: issue for reboot/kexec Date: Thu, 30 Jun 2005 18:18:21 -0700 Message-ID: <42C499DD.3050009@us.ibm.com> References: <42BC9F09.1060002@us.ibm.com> <20050624174652.159f26ce.rdunlap@xenotime.net> <20050625033328.GC3934@kroah.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============61386528323925238==" Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.osdl.org Errors-To: linux-pm-bounces@lists.osdl.org To: "Eric W. Biederman" Cc: linux-pm@lists.osdl.org, fastboot@lists.osdl.org, netdev@vger.kernel.org List-Id: linux-pm@vger.kernel.org --===============61386528323925238== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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. Thanks Haren --===============61386528323925238== Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --===============61386528323925238==--