Hi,
meanwhile, I convinced Dell that I have a hardware issue (and not a
Linux issue), and Dell has replaced the mainboard of my laptop. After
that, both the USB over-current kernel messages and the kworker
processes with permanent high CPU load are gone. So, this was indeed a
hardware issue!
On Mon 31-08-20 14:37:10, Mathias Nyman wrote:
[...]
> I can't come up with any good solution to this right now.
> Only bad ideas such as
> a. Add a sleep to the over-current case,
>doesn't solve anything else than the ~100% cpu hogging part of the problem
This sounds like a better thing fro
On 29.8.2020 18.59, Alan Stern wrote:
> On Sat, Aug 29, 2020 at 11:50:03AM +0200, Salvatore Bonaccorso wrote:
>> Hi Alan,
>>
>> I'm following up on this thread because a user in Debian (Dirk, Cc'ed)
>> as well encountered the same/similar issue:
>>
>> On Tue, Jul 21, 2020 at 10:33:25AM -0400, Alan
On Sat, Aug 29, 2020 at 11:50:03AM +0200, Salvatore Bonaccorso wrote:
> Hi Alan,
>
> I'm following up on this thread because a user in Debian (Dirk, Cc'ed)
> as well encountered the same/similar issue:
>
> On Tue, Jul 21, 2020 at 10:33:25AM -0400, Alan Stern wrote:
> > On Tue, Jul 21, 2020 at 07:
Hi Alan,
I'm following up on this thread because a user in Debian (Dirk, Cc'ed)
as well encountered the same/similar issue:
On Tue, Jul 21, 2020 at 10:33:25AM -0400, Alan Stern wrote:
> On Tue, Jul 21, 2020 at 07:59:17AM +0200, Michal Hocko wrote:
> > > Sorry, my mistake. The module name needs t
On Tue, Jul 21, 2020 at 06:00:25PM +0200, Michal Hocko wrote:
> On Tue 21-07-20 10:33:25, Alan Stern wrote:
> [...]
>
> Thanks a lot for your analysis. The laptop is slowly dying so this can
> be related.
>
> > So yes, this looks like a hardware design error. Turning off
> > autosuspend by writ
On Tue 21-07-20 10:33:25, Alan Stern wrote:
[...]
Thanks a lot for your analysis. The laptop is slowly dying so this can
be related.
> So yes, this looks like a hardware design error. Turning off
> autosuspend by writing to the sysfs power/control file is probably the
> best way to handle the
On Tue, Jul 21, 2020 at 07:59:17AM +0200, Michal Hocko wrote:
> > Sorry, my mistake. The module name needs to be "xhci_hcd" with an '_'
> > character, not a '-' character -- the same as what shows up in the lsmod
> > output.
>
>
> [14766.973734] xhci_hcd :00:14.0: Get port status 2-1 read:
On Mon 20-07-20 16:02:43, Alan Stern wrote:
> On Mon, Jul 20, 2020 at 08:16:05PM +0200, Michal Hocko wrote:
> > On Mon 20-07-20 13:48:12, Alan Stern wrote:
> > > On Mon, Jul 20, 2020 at 07:45:30PM +0200, Michal Hocko wrote:
> > > > On Mon 20-07-20 13:38:07, Alan Stern wrote:
> > > > > On Mon, Jul 2
On Mon, Jul 20, 2020 at 08:16:05PM +0200, Michal Hocko wrote:
> On Mon 20-07-20 13:48:12, Alan Stern wrote:
> > On Mon, Jul 20, 2020 at 07:45:30PM +0200, Michal Hocko wrote:
> > > On Mon 20-07-20 13:38:07, Alan Stern wrote:
> > > > On Mon, Jul 20, 2020 at 06:33:55PM +0200, Michal Hocko wrote:
> > >
On Mon 20-07-20 13:48:12, Alan Stern wrote:
> On Mon, Jul 20, 2020 at 07:45:30PM +0200, Michal Hocko wrote:
> > On Mon 20-07-20 13:38:07, Alan Stern wrote:
> > > On Mon, Jul 20, 2020 at 06:33:55PM +0200, Michal Hocko wrote:
> > > > On Mon 20-07-20 11:12:55, Alan Stern wrote:
> > > > [...]
> > > > >
On Mon, Jul 20, 2020 at 07:45:30PM +0200, Michal Hocko wrote:
> On Mon 20-07-20 13:38:07, Alan Stern wrote:
> > On Mon, Jul 20, 2020 at 06:33:55PM +0200, Michal Hocko wrote:
> > > On Mon 20-07-20 11:12:55, Alan Stern wrote:
> > > [...]
> > > > sudo echo 'module usbcore =p' >/debug/dynamic_d
On Mon 20-07-20 13:38:07, Alan Stern wrote:
> On Mon, Jul 20, 2020 at 06:33:55PM +0200, Michal Hocko wrote:
> > On Mon 20-07-20 11:12:55, Alan Stern wrote:
> > [...]
> > > sudo echo 'module usbcore =p' >/debug/dynamic_debug/control
> > >
> > > Then wait long enough for some interesting messages
On Mon, Jul 20, 2020 at 06:33:55PM +0200, Michal Hocko wrote:
> On Mon 20-07-20 11:12:55, Alan Stern wrote:
> [...]
> > sudo echo 'module usbcore =p' >/debug/dynamic_debug/control
> >
> > Then wait long enough for some interesting messages to appear in the
> > kernel log (it should only take
On Mon 20-07-20 11:12:55, Alan Stern wrote:
[...]
> sudo echo 'module usbcore =p' >/debug/dynamic_debug/control
>
> Then wait long enough for some interesting messages to appear in the
> kernel log (it should only take a few seconds if the worker thread is as
> busy as you say) and collect
On Mon, Jul 20, 2020 at 04:32:13PM +0200, Michal Hocko wrote:
> On Mon 20-07-20 09:58:57, Alan Stern wrote:
> [...]
> > Can you provide the contents of /sys/kernel/debug/usb/devices and also a
>
> attached.
It looks like you've got just two devices, only one of which is in use,
on bus 1 (the no
On Mon 20-07-20 09:58:57, Alan Stern wrote:
[...]
> Can you provide the contents of /sys/kernel/debug/usb/devices and also a
attached.
> usbmon trace showing a few rounds of this recurring activity?
This is not my area so I will need some help here. I assume I should
look for debug/usb/usbmon w
On Mon, Jul 20, 2020 at 10:39:56AM +0200, Michal Hocko wrote:
> Hi,
> I am not sure when this started happening but at least 5.6, 5.7 and
> 5.8-rc6 all exhibit this problem. Please note that the this is happining
> on a laptop which is not completely healthy. The BIOS complains that the
> Battery c
Hi,
I am not sure when this started happening but at least 5.6, 5.7 and
5.8-rc6 all exhibit this problem. Please note that the this is happining
on a laptop which is not completely healthy. The BIOS complains that the
Battery cannot be charged because the power supply cannot be recognized.
This is
19 matches
Mail list logo
