From owner-freebsd-current Tue Mar 20 16:19: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from fw.mccons.net (adsl-65-64-105-41.dsl.kscymo.swbell.net [65.64.105.41]) by hub.freebsd.org (Postfix) with ESMTP id 435F237B718 for ; Tue, 20 Mar 2001 16:19:04 -0800 (PST) (envelope-from root@mccons.maxbaud.net) Received: from localhost (root@localhost) by fw.mccons.net (8.11.1/8.11.2) with SMTP id f2L0J3094913 for ; Tue, 20 Mar 2001 18:19:03 -0600 (CST) (envelope-from root@mccons.maxbaud.net) Date: Tue, 20 Mar 2001 18:19:03 -0600 (CST) From: Wm Brian McCane X-Sender: root@fw.mccons.net To: freebsd-current@FreeBSD.ORG Subject: Re: CURRENT instability In-Reply-To: <20010319121606.A89188@enst.fr> 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 Mon, 19 Mar 2001, Pierre Beyssac wrote: > On Mon, Mar 19, 2001 at 08:30:12AM +0100, Pascal Hofstee wrote: > > AMD K6-2 350 > > > > I noticed the vague stack smashes posting earlier ... and i think it's very > > likely this is the same bug > > Same here, random crashes -- AMD K6-2 300; no panic, no crash dump, > just a complete system freeze if you happen to use too much CPU. > I had to temporarily revert to an older kernel. Another "data point". It was happening here as well on a Pentium 200/MMX. The crash occurred, almost everytime, in a bcopy called from vm_fault according to the kernel debugger (on the rare occassions I could still use it). Whenever I couldn't use the debugger, the Instruction pointer was usually 08:ffffffff. I stuck an old P-III 800MHz/PC133 machine in its place and everything has worked flawlessly since. - brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message