On Thu, 8 Jun 2000, Petko Manolov wrote:
> Jason Sharpee wrote:
> >
> > Alrighty, I stuck DEBUG into the usb-ohci and pegasus driver code and here
> > is the kernel and messages slightly before and after the driver crash.
>
> Hm, I am pretty sure DEBUG in my driver is used only to display dbg()
> messages.
>
> > This is virgin 2.4.0tac8 kernel code running on my Cyrix MediaGX 180 with
> > OHCI HC.
>
>
> Can you try with defining DEBUG just in the beginning of pegasus.c not
> on usb-ohci.
Does this alter the way in which the driver works? I thought it just
kicks out extra messages. It seems to crash at about the same time and in
the same manner with or without the DEBUG define. Ill recompile and test
tonight though to make positively sure.
This seems to be the snippet where it exactly stopped responding.
--------
Jun 8 07:29:58 ws1 kernel: usb-ohci.c: data(74/1536): 00 e0 98 75 46 51
00 80 c8 68 c0 56 08 00 45 00... stat:0 // xmitted data
Jun 8 07:29:58 ws1 kernel: 0(ffffff92) // Dont know what this is? Looks
like indication of the cause.
Jun 8 07:29:58 ws1 kernel: usb-ohci.c: data(0/1536): stat:-110 // The
-110 error that gets handed down the urb.
Jun 8 07:29:58 ws1 kernel: OHCI FREE: 5: c0ac1060
Jun 8 07:29:58 ws1 kernel: pegasus.c: eth0: RX status -110
Jun 8 07:29:58 ws1 kernel: usb-ohci.c: SUB URB:[ 173] dev: 2,ep:
1-I,type:BULK,flags: 0,len:0/1536,stat:-110(ffffff92)
Jun 8 07:29:58 ws1 kernel: OHCI ALLO: 6: c0ac1060
Jun 8 07:29:58 ws1 kernel: usb-ohci.c: USB-error/status: 5 : c0ac12e0
Jun 8 07:29:58 ws1 kernel: usb-ohci.c: RET URB:[ 174] dev: 2,ep:
1-I,type:BULK,flags: 0,len:0/1536,stat:-110(ffffff92)
Jun 8 07:29:58 ws1 kernel: usb-ohci.c: data(0/1536): stat:-110 // repeats
-----
-Jason
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
