From owner-freebsd-current@FreeBSD.ORG Fri Dec 26 21:13:01 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C81F16A4CE for ; Fri, 26 Dec 2003 21:13:01 -0800 (PST) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A73543D2D for ; Fri, 26 Dec 2003 21:13:00 -0800 (PST) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.10/8.12.9) with ESMTP id hBR5CkAS090567; Fri, 26 Dec 2003 22:12:52 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Fri, 26 Dec 2003 22:12:41 -0700 (MST) Message-Id: <20031226.221241.38712391.imp@bsdimp.com> To: dhee@myrealbox.com From: "M. Warner Losh" In-Reply-To: <1072413406.b4920de0dhee@myrealbox.com> References: <1072413406.b4920de0dhee@myrealbox.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: Serial driver problems with 5.2-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Dec 2003 05:13:01 -0000 In message: <1072413406.b4920de0dhee@myrealbox.com> "Dheeraj" 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