From owner-freebsd-bugs@FreeBSD.ORG Tue Apr 13 11:30:36 2004 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7735B16A4CE for ; Tue, 13 Apr 2004 11:30:36 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F84243D3F for ; Tue, 13 Apr 2004 11:30:36 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i3DIUabv053016 for ; Tue, 13 Apr 2004 11:30:36 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i3DIUaB9053015; Tue, 13 Apr 2004 11:30:36 -0700 (PDT) (envelope-from gnats) Date: Tue, 13 Apr 2004 11:30:36 -0700 (PDT) Message-Id: <200404131830.i3DIUaB9053015@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Ceri Davies Subject: Re: kern/65428: uscanner(4)-related repeatable kernel panic, 4.10-BETA X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Ceri Davies List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Apr 2004 18:30:36 -0000 The following reply was made to PR kern/65428; it has been noted by GNATS. From: Ceri Davies To: FreeBSD Gnats Submit Cc: Subject: Re: kern/65428: uscanner(4)-related repeatable kernel panic, 4.10-BETA Date: Tue, 13 Apr 2004 19:23:03 +0100 Adding to audit trail, from misfiled PR kern/65431: Date: Sun, 11 Apr 2004 17:41:14 +0800 From: Eugene Grosbein Message-Id: <20040411094114.GB732@grosbein.pp.ru> References: <200404110920.i3B9KVtG000692@grosbein.pp.ru> On Sun, Apr 11, 2004 at 02:31:20AM -0700, Julian Elischer wrote: > I have tried several times to duplicate this but it appears that > the fact that I have a different model of scanner (hp_6500C from memory) > means that SANE acts differently. > I have been completely unable to make my scanner fail in any way. I want to note once more, it does not panices using serial console and uscanner debug messages differ, a message about uscannerclose is not written when I close GUI dialog. Eugene