All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ford <david@linux.com>
To: Greg KH <greg@wirex.com>
Cc: linux-kernel@vger.kernel.org, Keith Owens <kaos@ocs.com.au>
Subject: Re: [bug] usb-uhci locks up on boot half the time
Date: Wed, 08 Nov 2000 23:39:36 -0800	[thread overview]
Message-ID: <3A0A54B8.66A66AAB@linux.com> (raw)
In-Reply-To: <3A09F158.910C925@linux.com> <14857.62696.393621.795132@somanetworks.com> <3A09FD81.E7DA9352@linux.com> <20001108200844.A13446@wirex.com> <3A0A25C1.C46E392B@linux.com> <20001108215901.A13572@wirex.com>

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

Sigh.  That's not the real hang position.  I needed to step slower.

kdb> ss
0xc01100f8 pci_conf1_write_config_word+0x40:   outw   %ax,(%dx)
SS trap at 0xc01100fa (pci_conf1_write_config_word+0x42)
0xc01100fa pci_conf1_write_config_word+0x42:   popl   %ebx
kdb> ss
0xc01100fa pci_conf1_write_config_word+0x42:   popl   %ebx
SS trap at 0xc01100fb (pci_conf1_write_config_word+0x43)
0xc01100fb pci_conf1_write_config_word+0x43:   xorl   %eax,%eax
kdb> ss
0xc01100fb pci_conf1_write_config_word+0x43:   xorl   %eax,%eax
SS trap at 0xc01100fd (pci_conf1_write_config_word+0x45)
0xc01100fd pci_conf1_write_config_word+0x45:   popl   %esi
kdb> ss
0xc01100fd pci_conf1_write_config_word+0x45:   popl   %esi
SS trap at 0xc01100fe (pci_conf1_write_config_word+0x46)
0xc01100fe pci_conf1_write_config_word+0x46:   movl   %ebp,%esp
kdb> ss
0xc01100fe pci_conf1_write_config_word+0x46:   movl   %ebp,%esp
SS trap at 0xc0110100 (pci_conf1_write_config_word+0x48)
0xc0110100 pci_conf1_write_config_word+0x48:   popl   %ebp
kdb> ss
0xc0110100 pci_conf1_write_config_word+0x48:   popl   %ebp
SS trap at 0xc0110101 (pci_conf1_write_config_word+0x49)
0xc0110101 pci_conf1_write_config_word+0x49:   ret
kdb> ss
0xc0110101 pci_conf1_write_config_word+0x49:   ret
SS trap at 0xc020c7af (pci_write_config_word+0x2b)
0xc020c7af pci_write_config_word+0x2b:   pushl  %ebx
kdb> ss
0xc020c7af pci_write_config_word+0x2b:   pushl  %ebx
SS trap at 0xc020c7b0 (pci_write_config_word+0x2c)
0xc020c7b0 pci_write_config_word+0x2c:   popf
kdb> ss
0xc020c7b0 pci_write_config_word+0x2c:   popf

Here is where it hung this time.  Register dump below.

usb-uhci.c: $Revision: 1.242 $ time 20:13:32 Nov  8 2000
usb-uhci.c: High bandwidth mode enabled
Instruction(i) breakpoint #0 at 0xc03f5a8c (adjusted)
0xc03f5a8c start_uhci:   pushl  %ebp

Entering kdb (current=0xcfff4000, pid 1) due to Breakpoint @ 0xc03f5a8c
kdb> bp pci_write_config_word+0x2c
Instruction(i) BP #1 at 0xc020c7b0 (pci_write_config_word+0x2c)
    is enabled globally adjust 1
kdb> g
Instruction(i) breakpoint #1 at 0xc020c7b0 (adjusted)
0xc020c7b0 pci_write_config_word+0x2c:   popf

Entering kdb (current=0xcfff4000, pid 1) due to Breakpoint @ 0xc020c7b0
kdb> rd
eax = 0x00000000 ebx = 0x00000256 ecx = 0x000000c0 edx = 0x00000cfc
esi = 0x000000c0 edi = 0xc144c800 esp = 0xcfff5f74 eip = 0xc020c7b0
ebp = 0xcfff5f90 xss = 0x00000018 xcs = 0x00000010 eflags = 0x00000046
xds = 0xc1440018 xes = 0x00000018 origeax = 0xffffffff &regs = 0xcfff5f40



0xc020c7aa pci_write_config_word+0x26:   movl   0x10(%edx),%eax
0xc020c7ad pci_write_config_word+0x29:   call   *%eax
0xc020c7af pci_write_config_word+0x2b:   pushl  %ebx
0xc020c7b0 pci_write_config_word+0x2c:   popf
0xc020c7b1 pci_write_config_word+0x2d:   jmp    0xc020c7bc
pci_write_config_word+0x38
0xc020c7b3 pci_write_config_word+0x2f:   nop
0xc020c7b4 pci_write_config_word+0x30:   movl   $0x87,%eax
0xc020c7b9 pci_write_config_word+0x35:   leal   0x0(%esi),%esi
0xc020c7bc pci_write_config_word+0x38:   leal   0xfffffff4(%ebp),%esp

I'm going to have to drop this debug shortly and return to my regular work :(

-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  7:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-09  0:35 [bug] usb-uhci locks up on boot half the time 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 [this message]
2000-11-09  1:12 ` Keith Owens
     [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 17:06 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

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=3A0A54B8.66A66AAB@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 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.