From: Johan Hovold <johan@kernel.org>
To: Nix <nix@esperi.org.uk>
Cc: Greg KH <greg@kroah.com>,
johan@kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: 4.20.7: pl2303 not working (post-4.19 regression) (limited info so far, not yet bisected)
Date: Mon, 18 Feb 2019 08:58:51 +0100 [thread overview]
Message-ID: <20190218075851.GA4072@localhost> (raw)
In-Reply-To: <877edytehb.fsf@esperi.org.uk>
On Sun, Feb 17, 2019 at 07:13:52PM +0000, Nix wrote:
> On 16 Feb 2019, Greg KH told this:
>
> > On Sat, Feb 16, 2019 at 04:26:30PM +0000, Nix wrote:
> >> So I just tried to connect up to my ancient Soekris firewall's serial
> >> console to try to bisect a problem where it stopped booting in 4.20, and
> >> found I couldn't.
> >>
> >> minicom says:
> >>
> >> minicom: cannot open /dev/ttyUSB0: Input/output error
> >>
> >> and in the dmesg we see
> >>
> >> [705576.028170] pl2303 ttyUSB0: failed to submit interrupt urb: -28
> >>
> >> Booting to 4.19, everything works fine. (A random GalliumOS Chromebook
> [...]
> >
> > bisection would be great, thanks!
>
> Rrrg. This is going to be harder than I thought. Rebooting, everything
> works fine! So this is something that kicks in after something less than
> eight days uptime, consistently on every box I own, but is fine on
> reboot.
Tough one.
> I'm still fairly sure this is a regression -- my machines are often up
> for a lot longer than that and I've never seen this before I upgraded to
> 4.20.x -- but I don't think I'm going to identify it by mindless
> bisection. I might have to actually *think* about it.
I doubt it's a regression in usb-serial as essentially nothing changed
with respect to pl2303 or core since 4.19.
The -ENOSPC you're seeing is returned by the host controller to
indicate:
This request would overcommit the usb bandwidth reserved for
periodic transfers (interrupt, isochronous).
but if you're saying you can reproduce this on "every box" it may not be
related to any particular host-controller driver (or USB topology).
Johan
next prev parent reply other threads:[~2019-02-18 7:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-16 16:26 4.20.7: pl2303 not working (post-4.19 regression) (limited info so far, not yet bisected) Nix
2019-02-16 19:47 ` Greg KH
2019-02-17 19:13 ` Nix
2019-02-18 7:58 ` Johan Hovold [this message]
2019-02-18 10:32 ` Nix
2019-02-20 9:29 ` Johan Hovold
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=20190218075851.GA4072@localhost \
--to=johan@kernel.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nix@esperi.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).