From: Markus Rechberger <linuxusb.ml@sundtek.de>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-usb@vger.kernel.org
Subject: Re: USB Autosuspend
Date: Wed, 18 Dec 2024 18:13:35 +0800 [thread overview]
Message-ID: <4e5403bfeaa656a42f145c217ccc7e58c993bca6.camel@sundtek.de> (raw)
In-Reply-To: <3e9d6d03-eed7-4f46-9926-4d395c0bc46d@rowland.harvard.edu>
On Mon, 2024-11-18 at 22:11 -0500, Alan Stern wrote:
> On Mon, Nov 18, 2024 at 04:13:29PM +0800, Markus Rechberger wrote:
> > Hi,
> >
> > we repeatedly received issues from customers with usb autosuspend,
> > our
> > devices are randomly disconnected on some systems, it did not
> > happen
> > many times but if more than 4-5 customers report this there's
> > usually
> > some real issue behind that.
> >
> > I'm asking here because the Libreelec distribution recently got my
> > attention that they seem to set usb autosuspend to -1 during boot
> > time
> > so they probably figured that out much earlier with other devices.
> > I have never experienced that issue on an Ivy or Haswell based
> > system.
> >
> > Were there some issues with particular kernel versions in the past
> > or
> > are there any issues known in general with USB autosuspend?
>
> I'm not aware of any such issues.
>
> Do you think you can get kernel debugging logs from your customers
> showing examples of these disconnections?
>
one customer just replied his problem is gone since he disabled auto
suspend (that was the latest one). He tested it since the last mail to
the mailing list.
Do you want any particular logfiles / logging from him?
Best Regards,
Markus
> Alan Stern
>
next prev parent reply other threads:[~2024-12-18 10:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 8:13 USB Autosuspend Markus Rechberger
2024-11-19 3:11 ` Alan Stern
2024-11-21 16:27 ` Markus Rechberger
2024-12-18 10:13 ` Markus Rechberger [this message]
2024-12-18 16:09 ` Alan Stern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4e5403bfeaa656a42f145c217ccc7e58c993bca6.camel@sundtek.de \
--to=linuxusb.ml@sundtek.de \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox