From owner-freebsd-hackers Thu Dec 20 9:46: 4 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 A429037B417 for ; Thu, 20 Dec 2001 09:45:57 -0800 (PST) Received: (from scheidell@localhost) by scanner.secnap.net (8.11.3/8.11.5) id fBKHjp400550 for freebsd-hackers@freebsd.org; Thu, 20 Dec 2001 12:45:51 -0500 (EST) (envelope-from scheidell) Message-Id: <200112201745.fBKHjp400550@scanner.secnap.net> Subject: Re: userland program panics freebsd 4.3 In-Reply-To: <20011220122030.B22881@espresso.q9media.com> To: freebsd-hackers@freebsd.org Date: Thu, 20 Dec 2001 12:45:51 -0500 (EST) From: Michael Scheidell X-Loop: scheidell@secnap.net X-Mailer: ELM [version 2.4ME+ PL92 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII 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 > > 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 as for moving to fbsd 4.4 for a 'maybe' fix of something that might still show up in 4.4 (according to other posts) this seems to be in the kernel anyway, so why would moving from a known to an unknown be a good thing? I did what everyone said, enable dumpdev and send in results. Its not hardware (too consistant, same spot, two different pieces of hardware) its a userland program and should not panic the kernel -- 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