From: Nix <nix@esperi.org.uk>
To: Greg KH <greg@kroah.com>
Cc: 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: Sun, 17 Feb 2019 19:13:52 +0000 [thread overview]
Message-ID: <877edytehb.fsf@esperi.org.uk> (raw)
In-Reply-To: <20190216194758.GA10756@kroah.com> (Greg KH's message of "Sat, 16 Feb 2019 20:47:58 +0100")
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.
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.
next prev parent reply other threads:[~2019-02-17 19:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-16 16:26 Nix
2019-02-16 19:47 ` Greg KH
2019-02-17 19:13 ` Nix [this message]
2019-02-18 7:58 ` Johan Hovold
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=877edytehb.fsf@esperi.org.uk \
--to=nix@esperi.org.uk \
--cc=greg@kroah.com \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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
Powered by JetHome