mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Patrick Mansfield <patmans@us.ibm.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Pedro Larroy <piotr@member.fsf.org>,
	Matthew Dharm <mdharm-usb@one-eyed-alien.net>,
	USB development list <linux-usb-devel@lists.sourceforge.net>,
	linux-kernel@vger.kernel.org
Subject: Re: aborts in usb-storage in branch 2.6
Date: Mon, 27 Oct 2003 16:01:13 -0800	[thread overview]
Message-ID: <20031027160113.A2582@beaverton.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0310241712140.2594-100000@ida.rowland.org>; from stern@rowland.harvard.edu on Fri, Oct 24, 2003 at 05:15:13PM -0400

On Fri, Oct 24, 2003 at 05:15:13PM -0400, Alan Stern wrote:
> On Thu, 23 Oct 2003, Pedro Larroy wrote:

> > abort.log -> 2.6.0test8
> > devices -> 2.6.0test8
> > kernel.log -> 2.6.0testx  where x < 8
> > 
> > In abort.log, is the paste of the log with kernel 2.6.0test8 in kern.log
> > there is a log from 2.6.0test4 or 2.6.0test4-mm
> > 
> > On previous 2.6.0testx kernels the bug appeared to trigger when ACPI debug
> > statements were printed, notice there are aborts after ACPI printks.
> > 
> > On 2.6.0test8 it seems to be triggered when doing concurrent access to the
> > filesystem.
> > 
> > I would like to help in anyway I can, but ACPI and USB is far beyond my
> > kernel knowledge, so I'm not currently able to fix the bugs myself.

> I looked at your logs, but I can't add much to what you already know.  
> This certainly does appear to be some sort of interrupt sharing/routing
> problem -- the logs don't indicate anything specific to USB.  However
> there's no easy way to tell what the source of that problem is.

The logs look like a SCSI timeout - a 30 second gap, followed by abort,
test unit ready, and a resend of the timed out write. That does not help
much. It could certainly be a lost interrupt.

I did not see any timeout/aborts happening (immediately) after the acpi
messages.

> Maybe someone who knows more about ACPI and interrupt handling can help.

I don't know ACPI, but I thought interrupt problems it might cause
happened more consistently.

-- Patrick Mansfield

  reply	other threads:[~2003-10-28  0:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-23 16:59 Pedro Larroy
2003-10-24 21:15 ` Alan Stern
2003-10-28  0:01   ` Patrick Mansfield [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-10-22  2:10 Pedro Larroy

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=20031027160113.A2582@beaverton.ibm.com \
    --to=patmans@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=mdharm-usb@one-eyed-alien.net \
    --cc=piotr@member.fsf.org \
    --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

Powered by JetHome