lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a649395b-0b91-a0d2-c510-ea8ec4aef917@linux.intel.com>
Date:   Fri, 3 Dec 2021 12:57:38 +0200
From:   Mathias Nyman <mathias.nyman@...ux.intel.com>
To:     Robert Munteanu <rombert@...che.org>,
        Mathias Nyman <mathias.nyman@...el.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     tiwai@...e.com, regressions@...ts.linux.dev,
        linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Regression: plugging in USB scanner breaks all USB functionality

On 2.12.2021 16.55, Robert Munteanu wrote:
> Hi,
> 
> After updating from kernel 5.14.11 to 5.14.14 I am seeing the following
> problem:
> 
> When plugging in an USB scanner ( Brother DSMobile DS-740D ) to my
> Lenovo P52 laptop I lose connection to all USB devices. Not only are
> the devices no longer available on the host, but no power is drawn by
> them. Only a reboot fixes the problem.
> 
> The scanner is the only device that triggers the problem, even when it
> is the only device plugged in. I have a host of other devices,
> connected either directly or via a USB hub in my monitor:
> 

There is one xhci patch in that range that has caused other issues:
ff0e50d3564f xhci: Fix command ring pointer corruption while aborting a command

That patch has a fix that is not yet applied, fix can be found here:
https://lore.kernel.org/linux-usb/20211126122340.1193239-2-mathias.nyman@linux.intel.com/
or
https://git.kernel.org/pub/scm/linux/kernel/git/mnyman/xhci.git/commit/?h=for-usb-linus&id=385b5b09c3546c87cfb730b76abe5f8d73c579a2

Does reverting the original patch, or applying the fix help?

Thanks
-Mathias


 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ