Date: Fri, 26 Dec 2003 22:12:41 -0700 (MST) From: "M. Warner Losh" <imp@bsdimp.com> To: dhee@myrealbox.com Cc: freebsd-current@freebsd.org Subject: Re: Serial driver problems with 5.2-current Message-ID: <20031226.221241.38712391.imp@bsdimp.com> In-Reply-To: <1072413406.b4920de0dhee@myrealbox.com>
index | next in thread | previous in thread | raw e-mail
In message: <1072413406.b4920de0dhee@myrealbox.com>
"Dheeraj" <dhee@myrealbox.com> writes:
: db> break siointr
: db> c
: Breakpoint at siointr: pushl %ebp
: db> trace
: siointr(c28e9800,2,fd,c27c6580,4) at siointr
: pccard_intr(c284cb00,4,685f676e,1,c27bbd80) at pccard_intr+0x48
: cbb_intr(c27a9800,1,5f676e09,2e696368,c10f9c80) at cbb_intr+0x158
: ithread_loop(c10f5800,cd963d48,20,3,5f676e08) at ithread_loop+0x178
: fork_exit(c04d94e0,c10f5800,cd963d48) at fork_exit+0x6c
: fork_trampoline() at fork_trampoline+0x8
: --- trap 0x1, eip = 0, esp = 0xcd963d7c, ebp = 0 ---
: db> c
: and then it hangs.
: I just ran out of ideas there after.
: I can probably try somemore stupidity of mine early tommorow.
Hmmm, can you break into the debugger after it hangs? This is
smelling like an interrupt problem a little, or a pci bus hang
although I usually have only seen those with experimental/development
pci hardware, or pci hardware that was a little too reliant on the
host to not do bad things (or such bad things were too wasy for my
driver to do).
Warner
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031226.221241.38712391.imp>