public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ford <david@linux.com>
To: Keith Owens <kaos@ocs.com.au>, Greg KH <greg@wirex.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [bug] usb-uhci locks up on boot half the time
Date: Wed, 08 Nov 2000 21:40:43 -0800	[thread overview]
Message-ID: <3A0A38DB.F5D63F6D@linux.com> (raw)
In-Reply-To: <3427.973738139@kao2.melbourne.sgi.com>

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

> The NMI oopser for UP only trips in when the cpu is spinning.  If the
> cpu is in a halt state then NMI does not run.  But in a halt state you
> should be able to activate kdb via the pause key.  The only time you
> cannot get kdb via pause is if interrupts are disabled (but then the
> cpu should be spinning and NMI should kick in) or if the cpu or
> motherboard is totally wedged.

just a quick followup while i'm working at it.  the hardware is totally
hung, nothing gets to it, keyboard, serial, or nmi.

being there are a lot of usb functions, does anyone have some suggested
breakpoints?

-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

       reply	other threads:[~2000-11-09  6:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3427.973738139@kao2.melbourne.sgi.com>
2000-11-09  5:40 ` David Ford [this message]
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
2000-11-11  9:49   ` Harald Nordgård-Hansen
  -- 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=3A0A38DB.F5D63F6D@linux.com \
    --to=david@linux.com \
    --cc=greg@wirex.com \
    --cc=kaos@ocs.com.au \
    --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