From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: [bug] usb-uhci locks up on boot half the time
Date: 9 Nov 2000 14:54:34 -0800 [thread overview]
Message-ID: <8uf9va$hi8$1@penguin.transmeta.com> (raw)
In-Reply-To: <D5E932F578EBD111AC3F00A0C96B1E6F07DBDC82@orsmsx31.jf.intel.com> <3A0B27E3.7D10AB64@linux.com>
In article <3A0B27E3.7D10AB64@linux.com>, David Ford <david@linux.com> wrote:
>
>The oddity is that kdb shows the machine to lock up on the popf in
>pci_conf_write_word()+0x2c. I never did get around to digging up this
>routine and looking at the code, but I suspect this is a final return
>from the routine. I'm rather confused however, I have no idea why a
>flags pop would hang the hardware.
Educated guess: it enables interrupts, after it has done something to
the hardware that causes an infinite stream of them.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-09 22:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-09 17:06 [bug] usb-uhci locks up on boot half the time Dunlap, Randy
2000-11-09 17:15 ` Greg KH
2000-11-09 22:40 ` David Ford
2000-11-09 22:54 ` Linus Torvalds [this message]
2000-11-11 9:49 ` Harald Nordgård-Hansen
[not found] <3427.973738139@kao2.melbourne.sgi.com>
2000-11-09 5:40 ` David Ford
-- strict thread matches above, loose matches on Subject: below --
2000-11-09 0:35 David Ford
2000-11-09 0:50 ` Georg Nikodym
2000-11-09 1:27 ` David Ford
2000-11-09 4:08 ` Greg KH
2000-11-09 4:19 ` David Ford
2000-11-09 5:59 ` Greg KH
2000-11-09 6:55 ` David Ford
2000-11-09 7:05 ` David Ford
2000-11-09 7:39 ` David Ford
2000-11-09 1:12 ` Keith Owens
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='8uf9va$hi8$1@penguin.transmeta.com' \
--to=torvalds@transmeta.com \
--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 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.