Here are a two more bugfixes for USB issues that were recently
discovered with 2.6.18-rc6
They do:
- fix a leak on /proc/tty/drivers/usb-serial
- fix a oops when unloading the yealink driver
Please pull from:
master.kernel.org:/pub/scm/linux/kernel/git/gregkh/usb-2.6.git/
From: Matthias Urlichs <[EMAIL PROTECTED]>
A sufficiently-large number of USB serial devices causes a reference leak
when /proc/tty/drivers/usbserial is read.
Signed-Off-By: Matthias Urlichs <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
---
drivers/usb/serial/usb-seri
From: Henk Vergonet <[EMAIL PROTECTED]>
This patch fixes a memory leak and a kernel oops when trying to unload
the driver, due to an unbalanced cleanup.
Thanks Ivar Jensen for spotting my mistake.
Signed-off-by: Henk Vergonet <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED
On Tue, 12 Sep 2006, Rafael J. Wysocki wrote:
> Now I have another symtom: during the _second_ suspend the suspending of
> USB controllers fails with messages like this:
>
> usb_hcd_pci_suspend(): ehci_pci_suspend+0x0/0xab [ehci_hcd]() returns -22
> pci_device_suspend(): usb_hcd_pci_suspend+0x0/0
On Mon, 11 Sep 2006, Vivek Dharmadhikari wrote:
> Hello Alan
>
> > Is the failure to ACK the problem you're worried about?
>
> Yes and the other issue(I/O error) as well. The real problem is that
> when we use this USB stick with out host controller, the driver takes
> long time to report "Attac
On Mon, 11 Sep 2006, Iñaky Pérez-González wrote:
> On Friday 08 September 2006 07:30, Alan Stern wrote:
> > On Thu, 7 Sep 2006, Iñaky Pérez-González wrote:
> > > usb: introduce usb_reenumerate_device()
> > >
> >
> > I don't understand the point of this patch. Is it simply to export an
> > interfa
> Pete Zaitcev <[EMAIL PROTECTED]> writes:
>>> Holding a reference
>>>to a struct pid avoid that problem, and paves the way
>>>for implementing a pid namespace.
>>
>>That may be useful.
>>
>>The patch itself seems straightforward if we can trust your struct
>>pid thingies. If OpenVZ people approve
您好：本公司发票代开范围:(商品销售、广告、运输发票、其它服务、租赁、建筑安装、
餐饮定额,增值发票等).贵公司在做帐或进销存方面如需用到的话，我司可提供
全方面的服务。可根据所做数量额度的大小来衡量优惠的点数。欢迎来电来邮。
郑重承诺!所用票据均可上网查询验证！
联系电话：13926556422 刘先生， 邮箱: [EMAIL PROTECTED]
-
Using Tomcat but need to d
On Tue, Sep 12, 2006 at 10:28:27AM -0400, Alan Stern wrote:
> On Tue, 12 Sep 2006, Rafael J. Wysocki wrote:
>
> > Now I have another symtom: during the _second_ suspend the suspending of
> > USB controllers fails with messages like this:
> >
> > usb_hcd_pci_suspend(): ehci_pci_suspend+0x0/0xab [e
On Tue, Sep 12, 2006 at 07:22:11PM +0200, Mattia Dongili wrote:
> On Tue, Sep 12, 2006 at 10:28:27AM -0400, Alan Stern wrote:
[...]
> > I was just going to send in a patch to fix the problem. I haven't had
> > much of a chance to try it out yet. The patch is included below, so you
> > can test it
On Monday 11 September 2006 20:18, Greg KH wrote:
> On Mon, Sep 11, 2006 at 06:44:43PM -0700, I?aky P?rez-Gonz?lez wrote:
> > Greg, would you please hold out that patch until we clarify the issue
> > further?
>
> Sure, I'll just drop it for now. Is that ok?
Perfect, thx
-
On Tuesday 12 September 2006 07:44, Alan Stern wrote:
> On Mon, 11 Sep 2006, Iñaky Pérez-González wrote:
> > On Friday 08 September 2006 07:30, Alan Stern wrote:
> > Yep, the initial reset that brings the device back to default state/addr0
> > always happens. However, it seems like that is not aff
Hello Alan
> The drive's firmware fails to respond to MODE SENSE commands.
> The same thing should happen on the PC. It would be
> possible to prevent those commands from being sent by adding
> an entry to the blacklist table, if you want.
How to add MODE_SENSE in the blacklist table ? Are
On Tue, 12 Sep 2006, Vivek Dharmadhikari wrote:
> Hello Alan
>
> > The drive's firmware fails to respond to MODE SENSE commands.
> > The same thing should happen on the PC. It would be
> > possible to prevent those commands from being sent by adding
> > an entry to the blacklist table, if y
Alan
The drive do responds to MODE SENSE when plugged into Linux PC.
I used the USB analyzer and I see following commands on the wire.
1. Inquiry message - Device responds with 36 bytes of data and returns
success in CSW
2. Test Unit Ready - Device returns error(0x1) in CSW
3. Request Sense -
On Tue, 12 Sep 2006, Mattia Dongili wrote:
> No luck here. I'll give -mm2 a run just to
>
> full dmesg
> with patch applied[1]:
> http://oioio.altervista.org/linux/dmesg-2.6.18-rc6-mm1-fail-S3-2
>
> without it (it's almost identical :)):
> http://oioio.altervista.org/linux/dmesg-2.6.18-rc6-mm1-
On Tue, 12 Sep 2006, Vivek Dharmadhikari wrote:
> Alan
>
> The drive do responds to MODE SENSE when plugged into Linux PC.
>
> I used the USB analyzer and I see following commands on the wire.
>
> 1. Inquiry message - Device responds with 36 bytes of data and returns
> success in CSW
> 2. Test
Alan
> The bytes of the two CBW packets are otherwise identical?
Yes the CBW packets are identicle except the value of Tag field. The
difference in the value of Tag field do not bother me because it can
vary.
> > Is it possible that the large gap of 12ms confuses the device ?
>
> It should not
> First of all, at91_udc activates the pullup in ..._register_driver(), so
> even if I don't load any gadget module, the host starts enumeration.
I don't follow. If you (successfully) register a gadget driver
and don't usb_gadget_disconnect() in the gadget driver bind()
method, it's *required* to
19 matches
Mail list logo
