kern/65428: uscanner(4)-related repeatable kernel panic, 4.10-BETA

[Ceri Davies]

The following reply was made to PR kern/65428; it has been noted by GNATS.

From: Ceri Davies <ceri at FreeBSD.org>
To: FreeBSD Gnats Submit <freebsd-gnats-submit at FreeBSD.org>
Cc:  
Subject: Re: kern/65428: uscanner(4)-related repeatable kernel panic, 4.10-BETA
Date: Tue, 13 Apr 2004 19:21:13 +0100

 Adding to audit trail, from misfiled PR kern/65429:
 
 Date: Sun, 11 Apr 2004 02:31:20 -0700 (PDT)
 To: Eugene Grosbein <eugen at grosbein.pp.ru>
 Message-Id: <Pine.BSF.4.21.0404110227320.82054-100000 at InterJet.elischer.org>
 In-Reply-To: <200404110920.i3B9KVtG000692 at grosbein.pp.ru>
 
  On Sun, 11 Apr 2004, Eugene Grosbein wrote:
  
  > 
  > >Submitter-Id:	current-users
  > >Originator:	Eugene Grosbein
  > >Organization:	Svyaz Service JSC
  > >Confidential:	no
  > >Synopsis:	uscanner(4)-related repeatable kernel panic, 4.10-BETA
  > >Severity:	critical
  > >Priority:	high
  > >Category:	kern
  > >Class:		sw-bug
  > >Release:	FreeBSD 4.10-BETA i386
  > >Environment:
  > System: FreeBSD grosbein.pp.ru 4.10-BETA FreeBSD 4.10-BETA #0: Sun Apr 11 15:43:04 KRAST 2004 eu at grosbein.pp.ru:/usr/local/obj/usr/local/src/sys/DADV i386
  > 	System was updated 10 April using cvsup.
  > 	Ports: sane-backends-1.0.13_2, sane-frontends-1.0.11_1, gimp-1.2.3_2,1
  
  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 will exapine these backtraces for clues but am not very hopeful.
  
  This was already a problem before the MFC right?