From owner-freebsd-current@FreeBSD.ORG Sat Dec 27 05:08:13 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 2119516A4CE for ; Sat, 27 Dec 2003 05:08:13 -0800 (PST) Received: from smtp-send.myrealbox.com (smtp-send.myrealbox.com [192.108.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id D390043D39 for ; Sat, 27 Dec 2003 05:08:11 -0800 (PST) (envelope-from dhee@myrealbox.com) Received: from dhee [24.99.34.159] by myrealbox.com with NetMail ModWeb Module; Sat, 27 Dec 2003 08:08:11 -0500 From: "Dheeraj" To: imp@bsdimp.com Date: Sat, 27 Dec 2003 08:08:11 -0500 X-Mailer: NetMail ModWeb Module X-Sender: dhee MIME-Version: 1.0 Message-ID: <1072530491.b36949c0dhee@myrealbox.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable cc: freebsd-current@freebsd.org Subject: Re: Re: Serial driver problems with 5.2-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: dhee@myrealbox.com 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 13:08:13 -0000 Hello Warner. I got a little further ahead or maybe not. i just put in a bunch of printf's and noticed that it goes into an infinite= loop. in srs/sys/dev/sio.c siointr1(struct com_s com)=20 { in the 2nd while loop while(line_status & LSR_RCV_MASK) { /*break/unattached error bits or real input?*/ ---- --- } } so it never comes out of this loop and the machine just hangs. i could al= so point to some more details if i were able to see the 'printfs' properl= y, right now i can see the scrreen scroll so fast that i can't make anyth= ing out of it. and as i said earlier i cannot break into the debugger. (i= know only two ways of it, ctrl-alt-esc and sysctl, if there is anything = else i can try out i shall try) dheeraj PS: Of course I am clueless about how to go about it but i hope you can pro= bably make some sense out of it. I do not understand why an interrupt routine is called even though i have n= o serial devices connected to it -----Original Message----- From: "M. Warner Losh" To: dhee@myrealbox.com Date: Fri, 26 Dec 2003 22:12:41 -0700 (MST) Subject: Re: Serial driver problems with 5.2-current 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 =3D 0, esp =3D 0xcd963d7c, ebp =3D 0 --- : db> c : and then it hangs.=20 : I just ran out of ideas there after.=20 : 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