Re: usb-storage & btusb regression = usb storage crash

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Apr 12, 2012 at 09:27:02AM +0200, Tomasz Miś wrote:
> Dnia 11-04-2012 o godz. 17:27 Greg KH napisał(a):
> > On Wed, Apr 11, 2012 at 11:35:03AM +0200, Tomasz Miś wrote:
> > > I re-submit a bug in usb-storage module and btusb and perhaps the
> > > driver option1. Confusion about which I wrote - visible in the
> > > attached dmesg, appears when the USB dongle is plugged into a USB port
> > > and is connected to another computer for example. If during a call we
> > > unlink this device (physically) from the port, or disable (for
> > > example, under KDE), you get an error appears in dmesg and the result
> > > will be total "crash" usb-storage. This error occurs from version 3.3
> > > to 3.3.1-rcx ... the
> > > 3.4.-RCX is only detect a bluetooth device on the USB port, but the
> > > system does not proceed at all data to and from the device.
> > 
> > Can you reproduce this on a "clean" kernel.org kernel?  Yours has a
> > number of other unknown patches, as well as the closed-source ati driver
> > in it.
> > 
> > And I don't see the usb-storage driver crashing, I see the bluetooth
> > driver causing problems, have you asked the bluetooth developers about
> > this?
> > 
> > thanks,
> > 
> > greg k-h
> 
> Hi, but my kernel is practically "pure vanilla". The only patches
> which I put on the kernel is AppArmor patch 2.4 compatibility patches
> [0001-0003]. Described by me problem occurs both in the Catalyst
> [tested at 12.1-12.3] and the open driver - does not matter.

Ok, can we see the crash with the "clean" kernel please?

> No I did not report this error to the list of bluetooth... Perhaps
> that the major problem is a [btusb], but certainly there are
> usb-storage crash too. After the "crash" btusb, followed by a
> usb-storage crash = any device using it, no longer will be work.
> Tested with 5 pandive, 2 GSM modems. Only a mouse hooked up to
> usb-wifi earlier works.

I would work on solving the bluetooth problem first, that looks like the
issue here.  Try emailing linux-bluetooth@xxxxxxxxxxxxxxx about this
issue.

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux