Re: Re: Serial driver problems with 5.2-current

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) 
{

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 also point to some more details if i were able to see the 'printfs' properly, right now i can see the scrreen scroll so fast that i can't make anything 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 probably make some sense out of it.
I do not understand why an interrupt routine is called even though i have no serial devices connected to it

-----Original Message-----
From: "M. Warner Losh" <imp_at_bsdimp.com>
To: dhee_at_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_at_myrealbox.com>
            "Dheeraj" <dhee_at_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