Date: Mon, 28 Jul 2008 21:50:19 +0200 From: Kris Kennaway <kris@FreeBSD.org> To: stevefranks@ieee.org Cc: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: 'stray irq7's cause hang? Message-ID: <488E22FB.60203@FreeBSD.org> In-Reply-To: <539c60b90807280935i50041623pe54b6ad65d5b89b8@mail.gmail.com> References: <539c60b90807280935i50041623pe54b6ad65d5b89b8@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Steve Franks wrote: > I've got a new system that hangs after about 2 hours - no > ctrl-alt-esc, not ctrl-alt-Fn, no ctrl-alt-delete. > > I tried hints.0.apic.disabled="YES" (that's apic, not acpi) (or > whatever the correct syntax from the handbook is), but I still get the > hang, and the stray irq 7's. As far as I can see, there's no other > dmesg output related. The stray interrupts may be a red herring. "Stray" means that no driver is handling them, and so there is no driver to screw up :) I see straq irq 7's on a HP proliant blade system, and also the hard hangs (it doesn't even reply to a NMI; this means it is almost certainly a hardware error). However I am now fairly certain the hangs are associated to disk failure. Several of the blades that were hanging went on to develop DMA errors from ATA, and after I validated the remaining systems with smartctl and took offline yet more blades that failed the self-tests, I have not had the problem recur. Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?488E22FB.60203>