From owner-freebsd-questions Mon Apr 2 13:59:40 2001 Delivered-To: freebsd-questions@freebsd.org Received: from sherline.com (sherline.net [216.120.87.2]) by hub.freebsd.org (Postfix) with SMTP id 0CF0F37B71F for ; Mon, 2 Apr 2001 13:59:36 -0700 (PDT) (envelope-from jgowdy@home.com) Received: (qmail 16370 invoked from network); 2 Apr 2001 20:59:32 -0000 Received: from unknown (HELO server2) (basharteg@216.120.87.3) by 216.120.87.2 with SMTP; 2 Apr 2001 20:59:32 -0000 Message-ID: <006b01c0bbb7$baed3150$035778d8@sherline.net> From: "Jeremiah Gowdy" To: "Matthew H. North" , References: Subject: Re: Reproducible kernel panics, 4.2-STABLE, various hardware Date: Mon, 2 Apr 2001 13:58:55 -0700 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.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yet the panics persist. I need to comment at this point that user software > (in this case squid) should never be able to trigger kernel panics. This > said, I'm getting to the point where I must conclude one of the following: That's not true though. Userland programs running as root can cause kernel panics and hard lockups. :) Have you tried CVSUPing to 4.3-RC and seeing if it does it there? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message