public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: Dirk Hohndel <hohndel@infradead.org>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	Alan Stern <stern@rowland.harvard.edu>,
	Sarah Sharp <sarah.a.sharp@linux.intel.com>,
	linux-usb@vger.kernel.org,
	Matthew Dharm <mdharm-usb@one-eyed-alien.net>,
	linux-scsi@vger.kernel.org
Subject: Re: strange USB storage failure with 2.6.29-rc2
Date: Wed, 28 Jan 2009 14:13:29 -0700	[thread overview]
Message-ID: <20090128141329.f427232b.zaitcev@redhat.com> (raw)
In-Reply-To: <20090128120129.68d04cd6@infradead.org>

On Wed, 28 Jan 2009 12:01:29 -0800, Dirk Hohndel <hohndel@infradead.org> wrote:

> Any recommendations how to best approach debugging this? Attaching
> strace to some processes before inserting the usb stick?

I would try add some dump_stack() to ->queuecommand, to see if this
is SG_IO or other source. Finding who sends the commands is the key.
Another trick is to printk the completion handlers (w/ lookup_symbol).

-- Pete

  reply	other threads:[~2009-01-28 21:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090127122641.1564fc46@infradead.org>
     [not found] ` <Pine.LNX.4.44L0.0901271548370.2286-100000@iolanthe.rowland.org>
     [not found]   ` <Pine.LNX.4.44L0.0901271548370.2286-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2009-01-28  4:06     ` strange USB storage failure with 2.6.29-rc2 Dirk Hohndel
     [not found]       ` <20090127200607.369a1693-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2009-01-28 16:54         ` Alan Stern
2009-01-28 17:14           ` Dirk Hohndel
2009-01-28 17:47             ` Alan Stern
2009-01-28 19:59               ` Dirk Hohndel
2009-01-28 20:14                 ` Alan Stern
     [not found]             ` <20090128091406.316a80fc-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2009-01-28 17:59               ` James Bottomley
2009-01-28 20:01                 ` Dirk Hohndel
2009-01-28 21:13                   ` Pete Zaitcev [this message]
2009-01-28 21:23                   ` Alan Stern
2009-01-28 21:29                     ` Pete Zaitcev
     [not found]                       ` <20090128142915.3b6f1949.zaitcev-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-01-28 21:41                         ` Alan Stern
2009-01-28 21:49                         ` Oliver Neukum
     [not found]                     ` <Pine.LNX.4.44L0.0901281622210.2231-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2009-01-28 22:39                       ` Dirk Hohndel
2009-01-28 21:10         ` Pete Zaitcev
     [not found]           ` <20090128141035.3a26ea60.zaitcev-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-01-28 21:21             ` Alan Stern
2009-01-28 21:22           ` Dirk Hohndel
     [not found]             ` <20090128132228.3f1e2f8a-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2009-01-28 21:27               ` Pete Zaitcev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090128141329.f427232b.zaitcev@redhat.com \
    --to=zaitcev@redhat.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=hohndel@infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mdharm-usb@one-eyed-alien.net \
    --cc=sarah.a.sharp@linux.intel.com \
    --cc=stern@rowland.harvard.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox