From owner-freebsd-stable Tue May 25 1: 1:33 1999 Delivered-To: freebsd-stable@freebsd.org Received: from anon.lcs.mit.edu (anon.lcs.mit.edu [18.26.0.254]) by hub.freebsd.org (Postfix) with SMTP id 03F4A155E7 for ; Tue, 25 May 1999 01:01:30 -0700 (PDT) (envelope-from serge69@nym.alias.net) Date: 25 May 1999 08:01:29 -0000 Message-ID: <19990525080129.24577.qmail@nym.alias.net> From: Sergey Subject: Re: [Q] How stable is FreeBSD 3.X ? To: "Mike Smith" Cc: References: <199905250635.XAA00767@dingo.cdrom.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [1] > If you only complain about a months-old release, nobody is going to be > able to help you. Do you understand this? No. I've think that your interesed in PR about any "supported" release, i.e. 3.0-3.2 for now. Ok, now I understand if my OS isn't stable - I can go to hell. Please WRITE this with RED

font in Handbook. And you'll get 50 times less problem reports. I don't catch this before your flame - thanks. I swear NEVER report a problem if my OS isn't stable. Sorry for you time, Sergey. P.S.: Let's close this meaningless discussion. I ack, I was wrong ... P.P.S.: I've wrote my tech PR again before read [1]. You are free to ignore it, because 3.1R is too old to carry. > If you have nothing more scientific than "it crashes eventually", how > can you claim that this is the "same instability"? It's same instability, because it gives same panic message in same context. panic: lockmgr: locking against myself. This doesn't depend on running processes or system load. This happens on exiting from '[','date'. One time in 'syncer'. This happens randomly - so long time I was sure that this is hardware problems. Once per 1-3 days. I've got it when using softupdates (tunefs -n enable) and when not using (tunefs -n disable). > No. You should be including the details in your initial report. Why > should we have to drag them out of you? I do, but it was ignored. [ my advocacy ] Ok, I agree my last claim (about RELEASES instability) in this thread is out-of-context. A little prehistory... I've sent technical description in my early messages (before this thread). Got only ONE reply, checked solution - it doesn't work, I notify this person (@FreeBSD.ORG), but he ignores me... I was not satisfied with results, but I have NO new info to raise problem technically again... To be honest 3.1 instability is not problem for me - I have great 2.2.8 server! My target was notify you about problems and hear that this is known and solved (or work in progress at least). In this thread I want get only statistics and personal's opinion - NOT solution for 3.1R problem. But get almost NOTHING. Actually this looks like as no one cares about stability ... Why? So I've got new info at last - problem is NOT hardware dependent. But, If so why, no one cares about my previous technical PR? Does this mean that all similar reports ignored? This why I downgrade my message to emotional level ;) It worked! [ end of advocacy ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message