Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp1667081imj; Sun, 17 Feb 2019 11:16:06 -0800 (PST) X-Google-Smtp-Source: AHgI3IaTH9wIcUp6BA4lJY0U94MMaY9yEQ1cau1v9l2f59resws3dIMiUSyxKzjy80xSbjlheBtr X-Received: by 2002:a17:902:9885:: with SMTP id s5mr21635799plp.52.1550430966395; Sun, 17 Feb 2019 11:16:06 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550430966; cv=none; d=google.com; s=arc-20160816; b=cbHnehjNDEatfuvVRg/MDQc0BNFYnACua79NImQEdbv+ELqDy7fugLHQJfeBbGs/H6 8e9wtpo28ODuNccyTAkGnnge8+1FQHqvchle+LIpvmD3eRHDYesNYl0ly0i6fQmnk7CA s99dlFjsY6cADSF8NoVOeY/kIXhWTpMDxVk2pI9hKQp4FAJHfu8khAbhNFt0p2VlwzOf 5abeLNWygKeMLgbMzbinhgfhZtrlqiGIlFNr1LUA78YCpV9slh75LMXsPzwiisCRSph9 SOa7rgHXiX1GgUgVIjARTpDScW697XfZALg9nyl1nItsbP3XGWzXMRn2W9+cBNbC00i3 g4cw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:message-id :in-reply-to:date:emacs:references:subject:cc:to:from; bh=sphp/wDWzF2hMP6TsF5T7mBlbgXUWpUlgvgtr7hd02k=; b=jop81V1B1Zlm+r0mGKMd/KcxHRTiaEjlphzQt0glm3KJ7cBcpzZF6R9JssHQm0lgj8 Gn9Rv3yxojCiCLgjJr1nm00Fo0v1B0XmY8DMjbLe1nmKAMfI+zC2aej2fiuAZE/HnKpC HFxjl9wVG19FSQta5kQRUkhdGBP3f0R8dkc6jR4W7ZcWvFmYvtqmusRhN0TQwTeFuGKJ tySgk64PU9vM9WxZZF09su7rBvScsIKgA4V+H39PsHlQ6B2U9kFRlIemata+aygTbLt/ 7VarcChpvvVAIKsZlkKlOInl41TemuTd8axwsB95+nc5G66CLYMOqfmmhrVA4Xb1cg/l IYyw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f20si11760205plr.419.2019.02.17.11.15.49; Sun, 17 Feb 2019 11:16:06 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726262AbfBQTOA (ORCPT + 99 others); Sun, 17 Feb 2019 14:14:00 -0500 Received: from icebox.esperi.org.uk ([81.187.191.129]:47430 "EHLO mail.esperi.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725798AbfBQTOA (ORCPT ); Sun, 17 Feb 2019 14:14:00 -0500 Received: from loom (nix@sidle.srvr.nix [192.168.14.8]) by mail.esperi.org.uk (8.15.2/8.15.2) with ESMTP id x1HJD3U6014430; Sun, 17 Feb 2019 19:13:03 GMT From: Nix To: Greg KH 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) References: <87o97bu2bt.fsf@esperi.org.uk> <20190216194758.GA10756@kroah.com> Emacs: a real time environment for simulating molasses-based life forms. Date: Sun, 17 Feb 2019 19:13:52 +0000 In-Reply-To: <20190216194758.GA10756@kroah.com> (Greg KH's message of "Sat, 16 Feb 2019 20:47:58 +0100") Message-ID: <877edytehb.fsf@esperi.org.uk> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-DCC-wuwien-Metrics: loom 1290; Body=4 Fuz1=4 Fuz2=4 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.