Date: Wed, 18 Mar 1998 21:47:58 -0600 From: dannyman <dannyman@sasquatch.dannyland.org> To: Karl Denninger <karl@mcs.net> Cc: dyson@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: A reminder of toxic -current ** READ THIS ** Message-ID: <19980318214758.38114@arh0300.urh.uiuc.edu> In-Reply-To: <19980318212757.30801@mcs.net>; from Karl Denninger on Wed, Mar 18, 1998 at 09:27:57PM -0600 References: <199803190257.VAA06394@dyson.iquest.net> <199803190307.WAA23964@dyson.iquest.net> <19980318211402.23977@arh0300.urh.uiuc.edu> <19980318212757.30801@mcs.net>
next in thread | previous in thread | raw e-mail | index | archive | help
First off, thanks to Karl, John and Steve for dire warnings, advice, education, tackling the problem, etc. :) On Wed, Mar 18, 1998 at 09:27:57PM -0600, Karl Denninger wrote: > Kernels built from 3/12 <appear> to not contain the bug. At least, so far > they appear not to contain the bug. Give me until tomorrow morning and I'll > know for sure - I'm running a full regression test on the 3/12 extract right > now, and will post something here if/when it either fails or runs to > completion. What is a "full regression test" ... outta curiousity? :) > If you're not aware that you're seeing the problem, then you probably are in > one of two camps: > > 1) You're slowly having your data destroyed and don't know it, and by > the time you DO know it you'll be completely screwed and need to > essentially reformat the disk :-) Hmmm ... fair enough. I'm not sure if mpg123 is just picky or maybe my entire mp3 collection is going funny. ;) > 2) You are not tripping the condition that is causing the destruction. > This *IS* possible; I have two machines in particular uses which do > NOT cause the problem, but I don't know why. Are there any commonalities in chipsets, and the like? Particular drivers? My system seems to be working perfectly normally, though to be honest, its normal operation is not perfect. ;) A shuttle motherboard, Intel chips, WDC drives .... K5. *shrug* > HOWEVER, be aware that even in case (2), the problematic kernel has > problems with lock-ups and other bad behavior (like unsolicited resets > without core dump or even a panic message, along with hard wedges which > don't respond to anything short of a RESET switch) which may be related. > I can readily reproduce the wedge problem on a busy webserver (which has > a boot disk that never gets written to, and thus is "safe" to use the bad > kernel on otherwise). Bahhh, Karl, I get lockups even on STABLE sometimes. I think I have flakey hardware somewheres. ;) > If you're either unable or unwilling to actually help find this and take the > concurrent risk that comes with doing so, you're best off reverting as above > so you don't become a victim. If someone wants to observe from my machine ... nahh, I'm reverting/rebuilding coz I'm gonna have to move the system soon anyways. Thanks. -dan -- //Dan -=- This message brought to you by djhoward@uiuc.edu -=- \\/yori -=- Information - http://www.uiuc.edu/ph/www/djhoward/ -=- aiokomete -=- Our Honored Symbol deserves an Honorable Retirement 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?19980318214758.38114>