From owner-freebsd-hackers Fri Dec 21 8: 6:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from scanner.secnap.net (scanner.secnap.net [216.241.67.74]) by hub.freebsd.org (Postfix) with ESMTP id E30A137B419 for ; Fri, 21 Dec 2001 08:06:07 -0800 (PST) Received: from MIKELT ([10.1.1.40]) by scanner.secnap.net (8.11.3/8.11.5) with SMTP id fBLG62s00404 for ; Fri, 21 Dec 2001 11:06:02 -0500 (EST) (envelope-from scheidell@secnap.net) Message-ID: <005d01c18a39$534cb6f0$2801010a@MIKELT> From: "Michael Scheidell" To: References: Subject: Re: userland program panics freebsd 4.3 Date: Fri, 21 Dec 2001 11:05:34 -0500 Organization: Secnap Network Security, LLC. MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ----- Original Message ----- From: "Paul Halliday" To: "Kris Kennaway" Cc: Sent: Thursday, December 20, 2001 10:08 PM Subject: Re: userland program panics freebsd 4.3 > > On Thu, 20 Dec 2001, Kris Kennaway wrote: > > > On Thu, Dec 20, 2001 at 12:45:51PM -0500, Michael Scheidell wrote: > > > > > > > > I'm not aware of any services that broke between 4.3 and 4.4. Care to > > > > elaborate? > > > > > > scan through freebsd-questions, freebsd-mobile and freebsd-ports > > > > That's completely non-helpful. I read -questions and -ports, and > > don't recall complaints of massive breakage in 4.4. Perhaps you'd > > care to be more specific so we can actually address the problems, if > > they exist? > > Because there are dozens or even hundreds of kernel bugs fixed since > > 4.3, so there's a very good chance yours was one of them. I guess I forgot a couple of things: #1, this IS a free operating system and noone is being paid to fix my problems #2, you probably get a lot of 'its broke please fix it' posts to these newsgroups #3, when I am frustrated I get a little testy. I would like to thank those who have assisted me in trying to find this problem and fix it. Nick Hilliard for his original pointer to FBSD handbook and the dumpdev section. Matthew Dillon for his offer to look at the vmcore (I know someone asked for more information, but beyond the gdb kernel traces and the description of the hardware, I don't think posting a 256MB core here would be a good idea) I also forgot that those of you who do try to help fix problems might also get frustrated at the lack of information given during the initial posts. Sorry, I did the best I could. I described the hardware and the environment and thought I pointed to the section in the kernel that had the problem. I was hoping that the given environment would trigger some suggestions, other than going to a new version. I like FBSD, It is faster and easier to use than Linux (for my application). I like the ports section. It is very easy to use, easy to update, and it contains most of what I would need. FBSD has been very stable except for this one thing. I expect that eventually we will find why it is happening and find some small, obscure 'feature' in the os that is causing this. It will get fixed quickly and help future generations of FBSD users who aren't so lucky as to be able to reproduce the panic at will. Again, I thank those who helped, even those who I did not mention and when I find the problem, I will post the resolution. -- Michael Scheidell Secnap Network Security, LLC scheidell@secnap.net 1+(561) 368-9561 See updated IT Security News at http://www.fdma.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message