Date: Thu, 07 Nov 2002 16:48:39 -0800 From: "Joel M. Baldwin" <qumqats@outel.org> To: current@FreeBSD.ORG Subject: Re: dnet causes Hard Lock on SMP kernel? ( was 'Why is my -current system Hard Locking?' ) Message-ID: <168637067.1036687709@[192.168.1.20]> In-Reply-To: <7mwunphrlk.wl@black.imgsrc.co.jp> References: <161351601.1036680423@192.168.1.20> <7mwunphrlk.wl@black.imgsrc.co.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
--On Friday, November 08, 2002 8:45 AM +0900 Jun Kuriyama <kuriyama@imgsrc.co.jp> wrote: > At Thu, 7 Nov 2002 22:55:56 +0000 (UTC), > Joel M. Baldwin <qumqats@outel.org> wrote: >> I'm still pursuing the cause of the Hard Locks on my system. >> >> 1.) I have a serial console hooked up. Nothing appears on >> the console when a Hard Lock happens. No panic. >> 2.) Shorting IOCHK to ground on the ISA connector doesn't work >> on a ABIT BP6, so I can't force myself into ddb. >> >> The BIG thing is that I now have a sure fire way of forcing >> a Hard Lock. Every time I run the distributed.net client >> 'dnet' the system hard locks. BUT ONLY ON A SMP KERNEL! >> I have a non SMP kernel running and things so far >> seem stable. Running the system with only 1 CPU is slow, >> so it'll take a while for me to be sure. > > I got same result on my box. Only solution I have is deinstall > dnetc. :-) > > -- > Jun Kuriyama <kuriyama@imgsrc.co.jp> // IMG SRC, Inc. What motherboard/CPU is this on? Have you tried a nonSMP kernel? 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?168637067.1036687709>