Date: Fri, 14 May 2010 07:32:59 -0700 From: Jeremy Chadwick <freebsd@jdc.parodius.com> To: Terry Kennedy <TERRY@tmk.com> Cc: freebsd-stable@FreeBSD.org, John Baldwin <jhb@FreeBSD.org>, Matthew Fleming <matthew.fleming@isilon.com> Subject: Re: Crash dump problem - sleeping thread owns a non-sleepable lock during crash dump write Message-ID: <20100514143259.GA1259@icarus.home.lan> In-Reply-To: <01NN3PQCOFHE006UN1@tmk.com> References: <01NN32EOXMYC006UN1@tmk.com> <4BED3912.9080509@FreeBSD.org> <01NN3PQCOFHE006UN1@tmk.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, May 14, 2010 at 09:56:47AM -0400, Terry Kennedy wrote: > As an aside, this is a quad-core in one package CPU (an X3363). On both > this box and a similar one with an X5470, console messages continue to > print out after "the system has been halted - press any key to reboot" - > in particular, the shutdown makes a bunch of the "behind the scenes" man- > agement stuff like the virtual keyboard and monitor appear. Plugging or > unplugging USB devices will go through the whole deal of detecting and > making their service available. > > I know the other CPUs are considered to still be running (hence the > "halting other CPUs" when you press a key to reboot), but this is the > first time I've seen device detection, attachment, etc. show up on the > console after a shutdown. > > Is this behavior to be expected, or is it as unexpected as it was to > me? Systems are Dell Poweredge R300's, 8-STABLE amd64. I've seen this behaviour before (on non-Dell hardware). I'm under the impression there's an interrupt handler that isn't being unloaded, and that the driver framework within the kernel does not "unload" on FreeBSD. What exactly does FreeBSD do on a system halt? I'm under the impression the OS should be unloading its interrupt handlers and then execute the HLT opcode on each processor/core. I don't have a tendency to halt my Supermicro systems, but shutdown -r now or shutdown -p now is pretty common. I've noticed an overall improvement with regards to the shutdown procedure and how long things take during the final phases (after filesystems are unmounted, etc.) with the below sysctl set (in /etc/sysctl.conf, but you can set it in real-time via command-line). hw.acpi.handle_reboot=1 -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100514143259.GA1259>