All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: "Satyam Sharma" <satyam.sharma@gmail.com>
Cc: "Timo Lindemann" <tlindemann@arcor.de>, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: kernel hang in ohci init
Date: Thu, 12 Jul 2007 20:40:36 -0700	[thread overview]
Message-ID: <200707122040.36800.david-b@pacbell.net> (raw)
In-Reply-To: <a781481a0707122015q48fd8a06m5d0e54b109708757@mail.gmail.com>

On Thursday 12 July 2007, Satyam Sharma wrote:
> 
> > [2.] The version 2.6.22 of the linux kernel hangs when initializing the
> > integrated ohci controller of the nvidia MCP51 chipset (pci device ids
> > vendor:product == 10de:26d). I have traced through various printks that
> > pci_init calls pci_fixup_device, later on in quirk_usb_ohci_handoff
> > (file linux/drivers/usb/host/pci-quirks.c) kernel freezes in this
> > section:

Note that hangs in that file almost always mean "your BIOS is goofy".
Hunt for BIOS settings related to USB, and change them.  As a rule, if
you tell your BIOS to ignore USB devices (mostly keyboards and disks),
it will have even less of an excuse to break like that.


> > ...
> > if (control & OHCI_CTRL_IR) {
> >         int wait_time = 500;
> >         writel(OHCI_INTR_OC, base + OHCI_INTRENABLE);
> >         writel(OHCI_ORC, base + OHCI_CMDSTATUS); // this never returns
> > ...
> > after this, kernel apparently goes into busy waiting (fans gradually
> > turn louder) and hangs indefinitely. I have also made sure that writel
> > (in linux/include/asm/io.h) really is entered, but never returns.

Does the current kernel.org GIT tree do the same thing?  A bunch
of USB patches were recently merged, including ISTR one in that
area ...


> > I can only guess that it might
> > have to do with the patch
> > "commit 4302a595cd9c6363b495460497ecbda49fa16858
> > Author: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> > Date:   Fri Dec 15 06:53:55 2006 +1100
> > USB: Rework the OHCI quirk mecanism as suggested by David
> > "
> > but I don't really have a clue, so this might be groundless suspicion.

Should be unrelated.  That patch related to how vendor-specific
implementation differences get detected and handled ... basically
just switching to a table-driven approach that can even handle
board-specific wiring braindamage, rather than the original scheme
which was just a big if/then/else looking only at chip vendors.

- Dave

  reply	other threads:[~2007-07-13  3:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-12  8:53 PROBLEM: kernel hang in ohci init Timo Lindemann
2007-07-13  3:15 ` Satyam Sharma
2007-07-13  3:40   ` David Brownell [this message]
2007-07-15 10:41     ` Timo Lindemann
2007-07-15 11:18       ` Satyam Sharma
2007-07-15 11:29         ` Satyam Sharma
2007-07-15 11:49           ` Timo Lindemann
2007-09-16 10:43             ` Satyam Sharma
2007-09-16 10:47               ` Satyam Sharma
2007-09-16 13:19                 ` Satyam Sharma
2007-07-16  5:06         ` David Brownell

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=200707122040.36800.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=satyam.sharma@gmail.com \
    --cc=tlindemann@arcor.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.