kern/51352: panic: malloc(M_WAITOK) in interrupt context
Bruce M. Simpson
bms at FreeBSD.org
Fri Sep 29 07:30:27 PDT 2006
The following reply was made to PR kern/51352; it has been noted by GNATS.
From: "Bruce M. Simpson" <bms at FreeBSD.org>
To: freebsd-gnats-submit at FreeBSD.org
Cc:
Subject: Re: kern/51352: panic: malloc(M_WAITOK) in interrupt context
Date: Fri, 29 Sep 2006 15:22:38 +0100
This is a multi-part message in MIME format.
--------------030807050903010704040901
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Ccing this to GNATS
--------------030807050903010704040901
Content-Type: message/rfc822;
name*0="Re: kern/51352: panic: malloc(M_WAITOK) in interrupt context"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename*0="Re: kern/51352: panic: malloc(M_WAITOK) in interrupt context"
Received: from mx4.internal (mx4.internal [10.202.2.203])
by store23m.internal (Cyrus v2.3.7-fmsvn9412) with LMTPA;
Fri, 29 Sep 2006 09:48:35 -0400
X-Sieve: CMU Sieve 2.3
X-Spam-score: 0.0
X-Delivered-to: bms at fastmail.net
Received: from mx2.freebsd.org (mx2.freebsd.org [216.136.204.119])
by mx4.messagingengine.com (Postfix) with ESMTP id 040EB15171A
for <bms at fastmail.net>; Fri, 29 Sep 2006 09:48:31 -0400 (EDT)
Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18])
by mx2.freebsd.org (Postfix) with ESMTP id 74940D0BD7
for <bms at fastmail.net>; Fri, 29 Sep 2006 13:47:31 +0000 (GMT)
(envelope-from dada at sbox.tugraz.at)
Received: by hub.freebsd.org (Postfix)
id CDC2416A5AA; Fri, 29 Sep 2006 13:47:14 +0000 (UTC)
Delivered-To: bms at freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id CA71C16A4D8;
Fri, 29 Sep 2006 13:47:13 +0000 (UTC)
(envelope-from dada at sbox.tugraz.at)
Received: from mailrelay2.tugraz.at (mailrelay.tu-graz.ac.at [129.27.2.202])
by mx1.FreeBSD.org (Postfix) with ESMTP id D59F043D55;
Fri, 29 Sep 2006 13:44:54 +0000 (GMT)
(envelope-from dada at sbox.tugraz.at)
Received: from webmail.tugraz.at (webmail.tu-graz.ac.at [129.27.2.204])
by mailrelay2.tugraz.at (8.13.8/8.13.8) with ESMTP id k8TDip16000358;
Fri, 29 Sep 2006 15:44:52 +0200 (CEST)
Received: from NWP254.kfunigraz.ac.at (NWP254.kfunigraz.ac.at
[143.50.80.54]) by webmail.tugraz.at (Horde MIME library) with HTTP; Fri,
29 Sep 2006 15:44:49 +0200
Message-ID: <20060929154449.xwuy9ut74csgk048 at webmail.tugraz.at>
X-Priority: 3 (Normal)
Date: Fri, 29 Sep 2006 15:44:49 +0200
From: Martin Kammerhofer <dada at sbox.tugraz.at>
To: "Bruce M. Simpson" <bms at FreeBSD.org>
Cc: freebsd-bugs at FreeBSD.org
Subject: Re: kern/51352: panic: malloc(M_WAITOK) in interrupt context
References: <200609251022.k8PAM67C084712 at freefall.freebsd.org>
<20060929095229.tc5i1cf6oggckwcs at webmail.tugraz.at>
<451CE252.8060307 at FreeBSD.org>
In-Reply-To: <451CE252.8060307 at FreeBSD.org>
MIME-Version: 1.0
Content-Type: text/plain;
charset=ISO-8859-1;
DelSp="Yes";
format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.2-cvs)
X-Organization: Graz University of Technology
X-Originating-IP: 143.50.80.54
X-Remote-Browser: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1;
.NET CLR 1.1.4322; .NET CLR 1.0.3705; .NET CLR 2.0.50727; InfoPath.1)
X-Scanned-By: MIMEDefang 2.56 on 129.27.10.19
Zitat von "Bruce M. Simpson" <bms at 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...
--------------030807050903010704040901--
More information about the freebsd-bugs
mailing list