From: ebiederm@xmission.com (Eric W. Biederman)
To: Greg KH <greg@kroah.com>
Cc: netdev@vger.kernel.org, fastboot@lists.osdl.org, linux-pm@lists.osdl.org
Subject: Re: [Fastboot] Re: Re: tg3: issue for reboot/kexec
Date: Thu, 30 Jun 2005 17:52:55 -0600 [thread overview]
Message-ID: <m1vf3vjtbc.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20050630233354.GA22287@kroah.com> (Greg KH's message of "Thu, 30 Jun 2005 16:33:55 -0700")
[-- Attachment #1: Type: text/plain, Size: 2031 bytes --]
Greg KH <greg@kroah.com> writes:
> On Thu, Jun 30, 2005 at 05:21:45PM -0600, Eric W. Biederman wrote:
>> However I have gotten feedback a couple of times that
>> driver writers tend to prefer using reboot notifiers. In part
>> because shutdown functions don't exist for non-pci devices.
>
> That's a very lame excuse. All busses should have shutdown functions.
> And any device that is just bypassing all of the existing bus logic is
> still tying into the driver core directly (which is a bad thing by
> itself, but that's a different matter.) And there's a shutdown method
> there too.
>
> So there is no excuse to not use it. Please, if they complain, point
> them to me :)
Ok.
Then there is still my complaint and device_shutdown doesn't get called
on module removal which means it really doesn't get implemented. Perhaps
with kexec now being in the mainline kernel this will get better.
Currently I have the following patch outstanding against the e1000
driver because on reboot on some boxes it card revisions
it places the card into a sleep state the driver initialization
routing cannot get the card out of.
And yes the e1000 is bad and is using a reboot_notifier.
Eric
e1000_main.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff -uNr linux-2.4.29-kexec-apic-virtwire-on-shutdownx86_64/drivers/net/e1000/e1000_main.c linux-2.4.29-e1000-no-poweroff-on-reboot/drivers/net/e1000/e1000_main.c
--- linux-2.4.29-kexec-apic-virtwire-on-shutdownx86_64/drivers/net/e1000/e1000_main.c Tue Feb 15 14:17:09 2005
+++ linux-2.4.29-e1000-no-poweroff-on-reboot/drivers/net/e1000/e1000_main.c Wed Feb 16 05:49:00 2005
@@ -2777,7 +2777,7 @@
case SYS_POWER_OFF:
while((pdev = pci_find_device(PCI_ANY_ID, PCI_ANY_ID, pdev))) {
if(pci_dev_driver(pdev) == &e1000_driver)
- e1000_suspend(pdev, 3);
+ e1000_suspend(pdev, (event == SYS_DOWN)?0:3);
}
}
return NOTIFY_DONE;
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2005-06-30 23:52 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 [this message]
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=m1vf3vjtbc.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=fastboot@lists.osdl.org \
--cc=greg@kroah.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;
as well as URLs for NNTP newsgroup(s).