I'm seeing a consistent oops with usbserial under 2.6.0-test5, which
occurs when I try to sync my pda using pilot-link. The module seems to
load (via hotplug) without any difficulty, and the sync itself works
fine... the oops occurs when the module is unloaded. Once this
happens, it requires a reboot to get usb working again.
I've attached the decoded oops, along with my kernel .config. If I
need to provide any additional information, please let me know.
On Wed, Sep 10, 2003 at 10:30:55PM -0500, Greg Norris wrote:
> I'm seeing a consistent oops with usbserial under 2.6.0-test5, which
> occurs when I try to sync my pda using pilot-link. The module seems to
> load (via hotplug) without any difficulty, and the sync itself works
> fine... the oops occurs when the module is unloaded. Once this
> happens, it requires a reboot to get usb working again.
>
> I've attached the decoded oops, along with my kernel .config. If I
> need to provide any additional information, please let me know.
Can you load both the usbserial and visor modules with "debug=1":
modprobe usbserial debug=1
modprobe visor debug=1
and then sync and remove the visor driver?
I'd be very interested in the kernel debug log right up to the kernel
oops.
thanks,
greg k-h
On Thu, Sep 11, 2003 at 07:45:15PM +0200, Jindrich Makovicka wrote:
> Hello,
>
> I have a similar problem, here is the syslog with debug=1 set for visor
> and usbserial. This occured after using a ppp connection. I am running
> 2.4.0test5 with v4l2 patch from http://bytesex.org/v4l/.
Hm, can you try the following patch and let me know if it fixes the
problem for you?
thanks,
greg k-h
--- a/drivers/usb/serial/usb-serial.c Wed Sep 3 08:47:22 2003
+++ b/drivers/usb/serial/usb-serial.c Thu Sep 11 11:01:55 2003
@@ -871,8 +871,10 @@
/* the ports are cleaned up and released in port_release() */
for (i = 0; i < serial->num_ports; ++i)
- if (serial->port[i]->dev.parent != NULL)
+ if (serial->port[i]->dev.parent != NULL) {
device_unregister(&serial->port[i]->dev);
+ serial->port[i] = NULL;
+ }
/* If this is a "fake" port, we have to clean it up here, as it will
* not get cleaned up in port_release() as it was never registered with
On Thu, Sep 11, 2003 at 10:57:56AM -0700, Greg KH wrote:
> Hm, can you try the following patch and let me know if it fixes the
> problem for you?
>
> thanks,
>
> greg k-h
I'm still getting an (apparently) identical oops. I've attached the
ksymoops output (your patch was applied for this one), along with the
debugging messages you requested previously. Let me know if I can
provide any additional info.
Thanx!
> On Wed, Sep 10, 2003 at 10:30:55PM -0500, Greg Norris wrote:
> > I'm seeing a consistent oops with usbserial under 2.6.0-test5, which
> > occurs when I try to sync my pda using pilot-link. The module seems to
> > load (via hotplug) without any difficulty, and the sync itself works
> > fine... the oops occurs when the module is unloaded. Once this
> > happens, it requires a reboot to get usb working again.
> >
> > I've attached the decoded oops, along with my kernel .config. If I
> > need to provide any additional information, please let me know.
>
> Can you load both the usbserial and visor modules with "debug=1":
> modprobe usbserial debug=1
> modprobe visor debug=1
>
> and then sync and remove the visor driver?
> I'd be very interested in the kernel debug log right up to the kernel
> oops.
I am also seeing an oops, 2.6.0-test5-mm1, Sony CLIE PDA.
I'll try to get you the kernel debug tonight.
cliffw
>
> thanks,
>
> greg k-h
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
On Thu, Sep 11, 2003 at 05:32:24PM -0500, Greg Norris wrote:
> On Thu, Sep 11, 2003 at 10:57:56AM -0700, Greg KH wrote:
> > Hm, can you try the following patch and let me know if it fixes the
> > problem for you?
> >
> > thanks,
> >
> > greg k-h
>
> I'm still getting an (apparently) identical oops. I've attached the
> ksymoops output (your patch was applied for this one), along with the
> debugging messages you requested previously. Let me know if I can
> provide any additional info.
Does this happen on 2.6.0-test5-bk3?
thanks,
greg k-h
On Wed, Sep 17, 2003 at 09:09:55PM -0700, Greg KH wrote:
> > I'm still getting an (apparently) identical oops. I've attached the
> > ksymoops output (your patch was applied for this one), along with the
> > debugging messages you requested previously. Let me know if I can
> > provide any additional info.
>
> Does this happen on 2.6.0-test5-bk3?
I can confirm that this is still an issue on 2.6.0-test5-bk5... I
didn't test -bk3 explicitly (although I certainly will if you like), as
I assume that any relevant changes will be in -bk5 as well. The oops
appears to be essentially identical, so I'm omitting it and the debug
output in order to conserve bandwidth. If you want to see it anyway,
just let me know.
Thanx!