Date: Fri, 24 Mar 2000 21:04:40 -0500 (EST) From: "Chris D. Faulhaber" <jedgar@fxp.org> To: Alan Clegg <abc@bsdi.com> Cc: freebsd-current@FreeBSD.ORG Subject: Re: reproducable system crash in 4.0-STABLE Message-ID: <Pine.BSF.4.10.10003242101270.14291-100000@pawn.primelocation.net> In-Reply-To: <20000324205658.A320@ecto.greenpeas.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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: <System Management Bus> on bti2c0
> smb0: <SMBus general purpose I/O> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.10003242101270.14291-100000>