netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: randy_dunlap <rdunlap@xenotime.net>
Cc: netdev@vger.kernel.org, fastboot@lists.osdl.org,
	Haren Myneni <haren@us.ibm.com>,
	linux-pm@lists.osdl.org
Subject: Re: Re: tg3: issue for reboot/kexec
Date: Fri, 24 Jun 2005 20:33:28 -0700	[thread overview]
Message-ID: <20050625033328.GC3934@kroah.com> (raw)
In-Reply-To: <20050624174652.159f26ce.rdunlap@xenotime.net>

[-- Attachment #1: Type: text/plain, Size: 1751 bytes --]

On Fri, Jun 24, 2005 at 05:46:52PM -0700, randy_dunlap wrote:
> On Fri, 24 Jun 2005 17:02:17 -0700 Haren Myneni wrote:
> 
> | 
> | Hello,
> |     The kexec boot on power blade (JS20) is not successfull without 
> | doing 'ifdown <ethernet device>'.  Based on my initial look in tg3 code, 
> | the driver does not have shutdown nor reboot notifier code unlike in 
> | other drivers. Hence, I added the the following patch (based on e1000) 
> | and it is working. Is it OK to include this patch? If not, any help to 
> | track down the issue would be appreciated.
> | 
> | My system is having the following cards:
> | 0000:11:01.0 Ethernet controller: Broadcom Corporation NetXtreme 
> | BCM5704S Gigabit Ethernet (rev 03)
> | 0000:11:01.1 Ethernet controller: Broadcom Corporation NetXtreme 
> | BCM5704S Gigabit Ethernet (rev 03)
> | 
> | lspci -n -s 0000:11:01
> | 0000:11:01.0 Class 0200: 14e4:16a8 (rev 03)
> | 0000:11:01.1 Class 0200: 14e4:16a8 (rev 03)
> 
> [adding fastboot & linux-pm mailing lists]
> 
> There was just a SCSI driver patch that tried to use a reboot
> notifier on shutdown and the patch got this comment:
> 
> Subject: Re: [PATCH] 2.6 aacraid: shutdown notification
> Message-ID: <42BC6D6F.5090402@us.ibm.com>
> From:	Mark Haverkamp <markh@osdl.org>
> 
> and reply From:	Brian King <brking@us.ibm.com>:
> | The pci_driver->shutdown method should be used instead of registering
> | a reboot notifier.
> 
> so is there a good reason that network drivers should use the
> reboot notifier instead of pci_driver->shutdown,
> or should we be converting drivers to use pci_driver->shutdown
> instead?
> My quick look favors pci_driver->shutdown.

Yes, don't add a reboot notifier, use the shutdown function instead.

thanks,

greg k-h

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2005-06-25  3:33 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 [this message]
2005-06-30 23:21     ` [Fastboot] Re: " 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

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=20050625033328.GC3934@kroah.com \
    --to=greg@kroah.com \
    --cc=fastboot@lists.osdl.org \
    --cc=haren@us.ibm.com \
    --cc=linux-pm@lists.osdl.org \
    --cc=netdev@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    /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;
as well as URLs for NNTP newsgroup(s).