Date: Fri, 29 Sep 2006 15:44:49 +0200 From: Martin Kammerhofer <dada@sbox.tugraz.at> To: "Bruce M. Simpson" <bms@FreeBSD.org> Cc: freebsd-bugs@FreeBSD.org Subject: Re: kern/51352: panic: malloc(M_WAITOK) in interrupt context Message-ID: <20060929154449.xwuy9ut74csgk048@webmail.tugraz.at> In-Reply-To: <451CE252.8060307@FreeBSD.org> References: <200609251022.k8PAM67C084712@freefall.freebsd.org> <20060929095229.tc5i1cf6oggckwcs@webmail.tugraz.at> <451CE252.8060307@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Zitat von "Bruce M. Simpson" <bms@FreeBSD.org>: > Is the original panic still present, or is this new behaviour? > > Can you tell us more about what kind of hardware you have? > > APM is the common factor in both conditions you describe so it's > important we know how APM is being entered, what kind of BIOS you > have, etc. It's the same hardware (except now larger IDE disks) that produced the original panic. An Intel BX440 based motherboard, the Asus P2B-S. The BIOS is the latest 1013. ACPI does not work with this board, Linux automatically disables it at boot with a message like "P2B-S Rev. 0 motherboards have a known PCI interrupt routing problem". However APM works fine (except with a FreeBSD kernel with INVARIANTS). Btw running a kernel without INVARIANTS on this box is no problem for me ;-). HTH, Martin P.S.: Haven't seen the malloc panic with 6.x, but I did only 2 panics...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060929154449.xwuy9ut74csgk048>