From owner-freebsd-bugs Sun Jan 3 08:40:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA10621 for freebsd-bugs-outgoing; Sun, 3 Jan 1999 08:40:09 -0800 (PST) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA10615 for ; Sun, 3 Jan 1999 08:40:08 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.8/8.8.5) id IAA28423; Sun, 3 Jan 1999 08:40:01 -0800 (PST) Date: Sun, 3 Jan 1999 08:40:01 -0800 (PST) Message-Id: <199901031640.IAA28423@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.ORG From: Skumle Subject: Re: i386/8894: Rebooting accidently because of missing floppy Reply-To: Skumle Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR i386/8894; it has been noted by GNATS. From: Skumle To: freebsd-gnats-submit@freebsd.org Cc: skumles@yahoo.com Subject: Re: i386/8894: Rebooting accidently because of missing floppy Date: Sun, 3 Jan 1999 08:40:58 -0800 (PST) _maybe_ is more a kern category type bug? If agreable, a change priority from high to low. Severity?? The problem was enabling CPU_WT_ALLOC kernel option. options CPU_WT_ALLOC At the time, I did not include this in the bug report, personal audit or *shrug* audit repost. IMHO close this bug. If it matters, hanging happens when I try enabling in FreeBSD 2.2.8-RELEASE of kernel config file again. #options CPU_WT_ALLOC if I _comment_ hanging is _not_ happening, for me now.. Problem happened again in XFree86 3.3.3, when I reported the audit followup, I made a mistake: I was not, Running FreeBSD 2.2.8-RELEASE i386, XFree86 3.3.2. I was, Running FreeBSD 2.2.7-RELEASE i386, XFree86 3.3.2 (when I did bug follow audit, I did use 2.2.8. When I send the first bug report 2.2.7. My __BAD__ error) It happens FYI when I try to find out what happened under FreeBSD 2.2.8-RELEASE i386, XFree86 3.3.3. Maybe my CPU does not work correct, I have Pentium MMX, an incompatible? # CPU_WT_ALLOC enables write-through allocation. Other ways How to repeat? cron (find jobs); gqmpeg (mp3) I try to be less careless in the new year and after.. Thanks for making FreeBSD great. I ordered WC 2.2.8 cds. _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message