From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 26 10:26:48 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B3EAA16A4CE; Thu, 26 Feb 2004 10:26:48 -0800 (PST) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92C0D43D1D; Thu, 26 Feb 2004 10:26:48 -0800 (PST) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([24.7.73.28]) by comcast.net (rwcrmhc12) with ESMTP id <2004022618264801400kd7rre>; Thu, 26 Feb 2004 18:26:48 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id KAA06851; Thu, 26 Feb 2004 10:26:46 -0800 (PST) Date: Thu, 26 Feb 2004 10:26:45 -0800 (PST) From: Julian Elischer To: Eugene Grosbein In-Reply-To: <20040226175423.GA413@grosbein.pp.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: stable@freebsd.org cc: hackers@freebsd.org Subject: Re: Testers needed: Joe's MFC of USB code X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Feb 2004 18:26:48 -0000 On Fri, 27 Feb 2004, Eugene Grosbein wrote: [...] > 'Failed to set value of option mode: Device busy'. > 6. Choose 'File/Exit' menu in this xscanimage window. > > Several seconds later system will lock up. There is nothing to be done > if you are in X, only power down/up cycle will help. > > > Sympthoms of lockup: system does not respond to pings, consoles do not switch. > Ctril-Alt-ESC will work for a few moments after lockup > but if you wait a little, it won't work and lockup will become 'total'. > > Versions: sane-backends-1.0.13_2, sane-frontends-1.0.11_1, gimp-1.2.3_2,1 > > Now what do we have with a patch proposed? Well, instead of lockup > we obtain good old kernel panic (the patch is really usefull). > And crashdump, of course. The panic is 100% repeatable. Here comes gdb > backtrace (kernel compiled with INVARIANTS and debug info): > thankyou! this is exactly the kind of thing we are looking for.. I have a scanner here.. I'll try duplicate it.. looks like it is caused by closing the file descriptor while the device is "busy" in some way.. Julian