public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Parag Warudkar <kernel-stuff@comcast.net>
To: David Brownell <david-b@pacbell.net>
Cc: linux-usb-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] 2.6.12-rc5 : repeatable modprobe usb-storage hang
Date: Sat, 4 Jun 2005 15:32:17 -0400	[thread overview]
Message-ID: <200506041532.17710.kernel-stuff@comcast.net> (raw)
In-Reply-To: <200506041212.04476.david-b@pacbell.net>

On Saturday 04 June 2005 15:12, David Brownell wrote:
> On Friday 03 June 2005 10:41 am, Parag Warudkar wrote:
> > Also interesting is this line -
> > [   40.586298] ohci_hcd 0000:00:02.0: Unlink after no-IRQ?  Controller is
> > probably using the wrong IRQ.
>
> So did you investigate these IRQ setup problem, or just ignore
> that pointed diagnostic?
>
Adding to the weirdness is that it happens infrequently - most of the times it 
works fine and I see no such error messages. I have ignored it till now. I 
will see if acpi=noirq helps.

> Controllers are not expected to behave if their drivers aren't given
> the correct IRQ.  In particular, when software needs to wait until
> the hardware reports it's finished with something, and the hardware
> never reports that (== never issues the IRQ) then things may hang.
>
The ohci-hcd hang problem might  be related to this. (Load of ohci-hcd with a 
storage device attached to the controller always hangs machine for 2 minutes 
- hang occurs in pci_enable_device()) 

> Also this earlier line already identified a potential root cause:
> > [   38.927690] ACPI: PCI Interrupt 0000:00:02.0[P]: no GSI - using IRQ 11
>
> This could be a problem in either the tables BIOS provided, or in the
> way ACPI is interpreting them, or something else ... I'm not an ACPI guru.
>

Most likely this is  a ACPI oddity - If BIOS was wrong it would have happened 
all the times. The above "no GSI" thing happens only some times and looks 
like that's when things won't work.

> You should be experimenting with ways to get the right IRQ assigned to this
> controller; such problems are common enough that there are probably half a
> dozen boot options affecting what happens.  Or maybe look at BIOS options
> that affect that controller; you might need to update your board's BIOS
> firmware.
>
> - Dave
Thanks for all the pointers. I will start with acpi=noirq and see.  My BIOS 
firmware is up2date.

Parag

-- 
Mac Beer: At first, came only a 16-oz. can, but now comes in a 32-oz. 
can. Considered by many to be a "light" beer. All the cans look 
identical. When you take one from the fridge, it opens itself. The 
ingredients list is not on the can. If you call to ask about the 
ingredients, you are told that "you don't need to know." A notice on the 
side reminds you to drag your empties to the trashcan.

      reply	other threads:[~2005-06-04 19:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-03 17:41 2.6.12-rc5 : repeatable modprobe usb-storage hang Parag Warudkar
2005-06-03 23:28 ` Andrew Morton
2005-06-03 23:44   ` Parag Warudkar
2005-06-04 19:12 ` [linux-usb-devel] " David Brownell
2005-06-04 19:32   ` Parag Warudkar [this message]

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=200506041532.17710.kernel-stuff@comcast.net \
    --to=kernel-stuff@comcast.net \
    --cc=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /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