From owner-freebsd-current Fri Mar 24 18: 4:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id B3C1337B7C7 for ; Fri, 24 Mar 2000 18:04:41 -0800 (PST) (envelope-from cdf.lists@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1016) id ADCF99B17; Fri, 24 Mar 2000 21:04:40 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id A450ABA1D; Fri, 24 Mar 2000 21:04:40 -0500 (EST) Date: Fri, 24 Mar 2000 21:04:40 -0500 (EST) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: Alan Clegg Cc: freebsd-current@FreeBSD.ORG Subject: Re: reproducable system crash in 4.0-STABLE In-Reply-To: <20000324205658.A320@ecto.greenpeas.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 24 Mar 2000, Alan Clegg wrote: > I know this is not "current", but it was last week, so give me a break. > > On a dual PII system, access to /dev/smb0 (system management bus) by > wmhm (/usr/ports/sysutils/wmhm) or gkrellm (/usr/ports/sysutils/gkrellm) > causes an immediate system panic. > > I have the following in dmesg: > > smbus0: on bti2c0 > smb0: on smbus0 > > and I have system dumps available to whoever wants. > I got similiar panics when I was working on my {wm}lmmon ports. You need: device intpm in your kernel config (or use the /dev/io method). I reported this when I found it a few months ago, but no one seemed to care. The system shouldn't panic if the device isn't present in the kernel, but... ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message