public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Buehler <abuehler.kernel@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Oliver Pinter <oliver.pntr@gmail.com>,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Greg KH <greg@kroah.com>,
	linux-scsi@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: USB regression (and other failures) in 2.6.2[45]*
Date: Sat, 16 Feb 2008 11:46:42 -0500	[thread overview]
Message-ID: <47B71372.5050804@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0802161013190.3769-100000@iolanthe.rowland.org>

(Note: I consider it blatantly incorrect to send a reply both to a
mailing list and directly to the address of someone who is subscribed to
that list unless you have reason to believe that that someone will not
see the message otherwise, but in this case I am doing so anyway because
I see no way to avoid it and still make sure all relevant people receive
the message.)

On 2/16/2008 10:20 AM, Alan Stern wrote:

> On Sat, 16 Feb 2008, Oliver Pinter wrote:
> 
>> On 2/15/08, Andrew Buehler <abuehler.kernel@gmail.com> wrote:
>>> In my workplace, I use a customized version of Novell's ZENworks
>>> imaging boot CD, which is based off of Linux. I have one
>>> particular model of laptop - the IBM/Lenovo R61 - on which three
>>> different things fail completely in current kernels (tested with
>>> 2.6.24.2 and 2.6.25-rc1): USB, AHCI (and thus access to the SATA
>>> drive), and networking. As a consequence of all three failing in
>>> parallel, I have no practical way to get logs and other
>>> information off of the machine to help with tracking down the
>>> bugs.
> 
> ...
> 
> To make a long story short, the USB symptoms you describe indicate a
> problem with interrupt routing.  This could well explain the other
> difficulties too.  There are various kernel parameters you can try
> putting on the boot command line to work around it:  acpi=noirq or
> acpi=off or pci=noacpi or a few others.

I have now tried all three of these, with no apparent effect; the USB
drive is still not detected when plugged in after boot. A naive search
on Google provides no indication of other possible parameters to try;
the only list I have found of ACPI-related kernel parameters includes no
others which seem likely to be helpful without more knowledge of the
specifics of the situation (and the subsystem) than I have.

What would the next step be?

-- 
    Andrew Buehler

  reply	other threads:[~2008-02-16 16:47 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-15 21:45 USB regression (and other failures) in 2.6.2[45]* Andrew Buehler
2008-02-16 14:32 ` Oliver Pinter
2008-02-16 15:20   ` Alan Stern
2008-02-16 16:46     ` Andrew Buehler [this message]
2008-02-16 17:16       ` Alan Stern
2008-02-16 21:33         ` Andrew Buehler
2008-02-16 23:11           ` Alan Stern
2008-02-17  1:12             ` Andrew Buehler
2008-02-17  3:35               ` Alan Stern
2008-02-17 16:21                 ` Andrew Buehler
2008-02-19 20:35                 ` USB regression (and other failures) in 2.6.2[45]* - mostly resolved Andrew Buehler
2008-02-20 15:50                   ` Alan Stern
2008-02-20 17:06                     ` Andrew Buehler
2008-02-20 17:15                       ` Alan Stern
2008-02-20 18:27                         ` Andrew Buehler
2008-02-20 19:29                           ` Alan Stern
2008-02-21 16:05                             ` Andrew Buehler
2008-02-21 16:36                               ` Alan Stern
2008-02-21 17:17                                 ` Greg KH
2008-02-21 19:43                                   ` Andrew Buehler
2008-02-21 20:02                                     ` Alan Stern
2008-02-17  4:10               ` [OT] GMail (was USB regression (and other failures)...) Joseph Fannin
2008-02-17 10:55           ` USB regression (and other failures) in 2.6.2[45]* Sergey Vlasov
2008-02-17  7:20       ` Paul Jackson
2008-02-17 16:17         ` Andrew Buehler
2008-02-17 16:20           ` Paul Jackson

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=47B71372.5050804@gmail.com \
    --to=abuehler.kernel@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oliver.pntr@gmail.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