From: Andi Kleen <ak@muc.de>
To: "Simon White" <s_a_white@email.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Detecting kernel shutdown in a kernel driver
Date: Fri, 11 Feb 2005 16:14:47 +0100 [thread overview]
Message-ID: <m1fz03uo0o.fsf@muc.de> (raw)
In-Reply-To: <20050210200537.AD4754BE65@ws1-1.us4.outblaze.com> (Simon White's message of "Thu, 10 Feb 2005 15:05:37 -0500")
"Simon White" <s_a_white@email.com> writes:
> Hi,
>
> I've been writing a device driver for a piece of hardware that we recently found the pci bridge has an issue on software reset (kernel 2.6.8.1, hardware reset is fine). The bridge appears to corrupt the subvendor/device ids on next boot. We have found a software work around in that I can write to the bridge on module exit and it will always detect correctly next boot (through module_exit when rmmod'd).
>
> However on shutting down a machine with the module loaded it never works next time, so is module_exit actually called?
It's only called when the module is explicitely unloaded.
You can use register_reboot_notifier() though.
-Andi
prev parent reply other threads:[~2005-02-11 15:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 20:05 Detecting kernel shutdown in a kernel driver Simon White
2005-02-10 21:48 ` Stephen Hemminger
2005-02-11 15:14 ` Andi Kleen [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=m1fz03uo0o.fsf@muc.de \
--to=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=s_a_white@email.com \
/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