From owner-freebsd-bugs@FreeBSD.ORG  Fri Apr  9 04:41:26 2004
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
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 9233B16A4CE
	for <freebsd-bugs@freebsd.org>; Fri,  9 Apr 2004 04:41:26 -0700 (PDT)
Received: from osiris.ipform.ru (osiris.itlegion.ru [212.248.52.90])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D82A143D5F
	for <freebsd-bugs@freebsd.org>; Fri,  9 Apr 2004 04:41:25 -0700 (PDT)
	(envelope-from matrix@itlegion.ru)
Received: from artem (artem.office.ipform.ru [192.168.0.12])
	by osiris.ipform.ru (8.12.6/8.12.6) with ESMTP id i39BfNXg062055
	for <freebsd-bugs@freebsd.org>; Fri, 9 Apr 2004 15:41:24 +0400 (MSD)
	(envelope-from matrix@itlegion.ru)
X-AntiVirus: Checked by Dr.Web (http://www.drweb.net)
Message-ID: <003e01c41e27$1f0c8ad0$0c00a8c0@artem>
From: "Artem Koutchine" <matrix@itlegion.ru>
To: <freebsd-bugs@freebsd.org>
Date: Fri, 9 Apr 2004 15:38:00 +0400
Organization: IT Legion
MIME-Version: 1.0
Content-Type: text/plain;
	charset="koi8-r"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Subject: twe driver and 3dm
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Apr 2004 11:41:26 -0000

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. 

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.

What do you think?

Artem