mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kai Ruhnau <kai@tragetaschen.dyndns.org>
To: LKML <linux-kernel@vger.kernel.org>
Subject: System hang in quirk_usb_handoff_ohci
Date: Mon, 29 Dec 2008 21:32:22 +0100	[thread overview]
Message-ID: <495933D6.1020409@tragetaschen.dyndns.org> (raw)

Hi,

Some days ago, I reported a reproducible hang during boot. The
information around was quite vague and so I took the liberty to further
dig into the the call stack of pci_init and found the exact place where
the initialization locks.
But first the symptoms (those are improved as well):

If I turn on or restart my computer and try to boot without my
intervention, the system always hangs during boot, the last output being
the io scheduler registration. However, if I press a key at any time
after the BIOS (for example manual choosing  the grub entry or during
the kernel messages) the system happily boots normally.

After a little printk debugging, it turns out, that
quirk_usb_handoff_ohci will hang when applied to my first USB OHCI pci
device. I have marked the offending line in the following snippet (line
186 in the original---the second writel)

============ (startint at line 182 inn pci-quirks.c)
[...]
    u32 control = readl(base + OHCI_CONTROL);
    if (control & OHCI_CTRL_IR) {
        int wait_time = 500; /* arbitrary; 5 seconds */
        writel(OHCI_INTR_OC, base + OHCI_INTRENABLE);

       // The next line might hang

        writel(OHCI_OCR, base + OHCI_CMDSTATUS);
        while (wait_time > 0 &&
                readl(base + OHCI_CONTROL) & OHCI_CTRL_IR) {
            wait_time -= 10;
            msleep(10);
        }
[...]
=========

The lspci output for the device is

00:13.0 0c03: 1002:4387 (prog-if 10 [OHCI])
        Subsystem: 1462:7326              
        Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 16
        Memory at fdffe000 (32-bit, non-prefetchable) [size=4K]   
        Kernel driver in use: ohci_hcd                            
        Kernel modules: ohci-hcd                                  

My system is a

Linux  2.6.28-gentoo #12 SMP PREEMPT Mon Dec 29 21:01:04 CET 2008 x86_64
Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz GenuineIntel GNU/Linux

Thanks for your time.

Best regards
Kai

-- 
This signature is left as an exercise for the reader.


             reply	other threads:[~2008-12-29 20:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-29 20:32 Kai Ruhnau [this message]
2008-12-29 21:09 ` Robert Hancock
2008-12-30  0:30   ` Kai Ruhnau

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=495933D6.1020409@tragetaschen.dyndns.org \
    --to=kai@tragetaschen.dyndns.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®