From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oliver Neukum Subject: Re: strange USB storage failure with 2.6.29-rc2 Date: Wed, 28 Jan 2009 22:49:28 +0100 Message-ID: <200901282249.29599.oliver@neukum.org> References: <20090128120129.68d04cd6@infradead.org> <20090128142915.3b6f1949.zaitcev@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20090128142915.3b6f1949.zaitcev-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> Content-Disposition: inline Sender: linux-usb-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Pete Zaitcev Cc: Alan Stern , Dirk Hohndel , James Bottomley , Sarah Sharp , linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Matthew Dharm , linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-scsi@vger.kernel.org Am Wednesday 28 January 2009 22:29:15 schrieb Pete Zaitcev: > On Wed, 28 Jan 2009 16:23:37 -0500 (EST), Alan Stern wrote: > > > > Any recommendations how to best approach debugging this? Attaching > > > strace to some processes before inserting the usb stick? > > > > No really good recommendations. The guilty party is often hal, so you > > can try turning off the haldaemon service before plugging in your > > stick. > > printk current->comm in queuecommand maybe? Code to do just that can be taken from the microtek driver. HTH Oliver -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html