Date: Tue, 16 Aug 2005 21:50:31 +0300 From: Maxim Sobolev <sobomax@portaone.com> To: hackers@FreeBSD.org, bms@FreeBSD.org, drosih@rpi.edu, Bill Paul <wpaul@FreeBSD.org>, John Baldwin <jhb@FreeBSD.org>, Alexander Timoshenko <gonzo@portaone.com>, bug-followup@FreeBSD.org, Alexander Timoshenko <gonzo@portaone.com> Subject: Network interrupt after shutdown method has been called [kern/62889] Message-ID: <43023577.6080108@portaone.com>
next in thread | raw e-mail | index | archive | help
Folks, We experience a 100% reproducible panic on one of our machines during shutdown+power off. We have found that it's caused by the interrupt which happens in re(4) after re_shutdown() method has been called. Quick googling reveals that we are not alone who experience this problem and such condition sometimes happens as a result of interaction with the particular ACPI implementation on shutdown+power off. Some FreeBSD network drivers have been patched to workaround for the problem (i.e. vr(4), see kern/62889), but quick browsing through sources suggests that majority still can be affected by the exactly the same problem. Hence the question: Who is "guilty"? Can the network driver make an assumption that no interrupt will happen after its foo_shutdown() has been called? Or such assumption cannot be made? In the former case most of the network drivers have to be fixed (usually by turning foo_shutdown() into a wrapper to foo_detach() as with vr(4)), while in the latter the reason of this stray irq should be investigated further and fixed where appropriate. Any comments/ideas? -Maxim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43023577.6080108>