public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ford <david@linux.com>
To: "Dunlap, Randy" <randy.dunlap@intel.com>
Cc: Greg KH <greg@wirex.com>, linux-kernel@vger.kernel.org
Subject: Re: [bug] usb-uhci locks up on boot half the time
Date: Thu, 09 Nov 2000 14:40:36 -0800	[thread overview]
Message-ID: <3A0B27E3.7D10AB64@linux.com> (raw)
In-Reply-To: <D5E932F578EBD111AC3F00A0C96B1E6F07DBDC82@orsmsx31.jf.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1243 bytes --]

"Dunlap, Randy" wrote:

> > Either.  Currently bus (self) powered.  This hub has worked
> > fine on my other
> > computers without any adverse affect.
>
> Bus-powered != self-powered.

It had been a long day.  I really do know the distinction :)

It is currently bus powered and I've only once had it self powered
several months ago.  It is an SIIG 4 port hub, I hadn't seen any
complaints about it doing a web search when I looked, so I purchased it.

I have found that after unplug/plug the mouse and reboot, If I unplug
the hub then the boot will continue fine, if I unplug the just the mouse
(which is plugged into the hub), the machine will indeed hang.  If I
reset the power on the hub and plug it back in it will still hang.
I must reset the power on the motherboard.

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.

-d

--
"The difference between 'involvement' and 'commitment' is like an
eggs-and-ham breakfast: the chicken was 'involved' - the pig was
'committed'."



[-- Attachment #2: Card for David Ford --]
[-- Type: text/x-vcard, Size: 176 bytes --]

begin:vcard 
n:Ford;David
x-mozilla-html:TRUE
adr:;;;;;;
version:2.1
email;internet:david@kalifornia.com
title:Blue Labs Developer
x-mozilla-cpt:;14688
fn:David Ford
end:vcard

  parent reply	other threads:[~2000-11-09 22:41 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 [this message]
2000-11-09 22:54   ` Linus Torvalds
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=3A0B27E3.7D10AB64@linux.com \
    --to=david@linux.com \
    --cc=greg@wirex.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@intel.com \
    /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