From owner-freebsd-bugs@FreeBSD.ORG Fri Apr 9 18:27:33 2004 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE66516A4CF for ; Fri, 9 Apr 2004 18:27:33 -0700 (PDT) Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6ED543D3F for ; Fri, 9 Apr 2004 18:27:33 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (53530b6c1fb0105090e3f98bc0194b3c@adsl-67-115-73-128.dsl.lsan03.pacbell.net [67.115.73.128])i3A1RVWh014576; Fri, 9 Apr 2004 20:27:32 -0500 (CDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 38E6553504; Fri, 9 Apr 2004 18:27:31 -0700 (PDT) Date: Fri, 9 Apr 2004 18:27:31 -0700 From: Kris Kennaway To: Artem Koutchine Message-ID: <20040410012731.GA64574@xor.obsecurity.org> References: <003e01c41e27$1f0c8ad0$0c00a8c0@artem> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jI8keyz6grp/JLjh" Content-Disposition: inline In-Reply-To: <003e01c41e27$1f0c8ad0$0c00a8c0@artem> User-Agent: Mutt/1.4.2.1i cc: freebsd-bugs@freebsd.org Subject: Re: twe driver and 3dm X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Apr 2004 01:27:34 -0000 --jI8keyz6grp/JLjh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Apr 09, 2004 at 03:38:00PM +0400, Artem Koutchine wrote: > Well, during discussion in other thread we have figured that > twe driver is actually pretty harmless and does not cause kernel > panic.And I also figured that accessing extended error log of 3dm > via web interface causes kernel to panic when the link is clicked > very fast several times.=20 >=20 > Here is what i think. 3DM is only an application and IMHO > error in an application must not cause kernel panic but such > applications must be terminated w/o futher consiquences to > the OS running.So, the problem with kernel panic > when using extended error log in 3dm , again IMHO, > is cause by either buggy kernel or buggy driver. I mean, 3dm > passes some data to the driver which makes do bad things or > 3dm passes some data to the kernel syscall which make kernel > panic. Either way, *IMHO*, the part that must be fixed first is > not 3dm, because it is just an external process relative to the kernel. >=20 > What do you think? I think you need to stop self-diagnosing problems and concentrate on accurately reporting the symptoms. http://www.catb.org/~esr/faqs/smart-questions.html#symptoms Kris --jI8keyz6grp/JLjh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAd02CWry0BWjoQKURApT7AJ4p8/Of/n1QfulKbxjrAMQ7LPFZSwCdHLX2 Pcq1a80AP5li9L2Yy3P4GGE= =8bBM -----END PGP SIGNATURE----- --jI8keyz6grp/JLjh--