To: "Simon White" <s_a_white@email.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Detecting kernel shutdown in a kernel driver
References: <20050210200537.AD4754BE65@ws1-1.us4.outblaze.com>
From: Andi Kleen <ak@muc.de>
Date: Fri, 11 Feb 2005 16:14:47 +0100
In-Reply-To: <20050210200537.AD4754BE65@ws1-1.us4.outblaze.com> (Simon
 White's message of "Thu, 10 Feb 2005 15:05:37 -0500")
Message-ID: <m1fz03uo0o.fsf@muc.de>
User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 944
Lines: 18

"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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/