Re: 4.20.7: pl2303 not working (post-4.19 regression) (limited info so far, not yet bisected)

2019-02-18 Thread Nix
On 18 Feb 2019, Johan Hovold stated: > On Sun, Feb 17, 2019 at 07:13:52PM +0000, Nix wrote: >> 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&#

Re: 4.20.7: pl2303 not working (post-4.19 regression) (limited info so far, not yet bisected)

2019-02-17 Thread Nix
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. >

4.20.7: pl2303 not working (post-4.19 regression) (limited info so far, not yet bisected)

2019-02-16 Thread Nix
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

Re: [3.16.1 BISECTED REGRESSION]: Simtec Entropy Key (cdc-acm) broken in 3.16

2014-11-06 Thread Nix
On 6 Nov 2014, Johan Hovold said: > On Thu, Nov 06, 2014 at 01:49:13PM +0000, Nix wrote: >> On 5 Nov 2014, Johan Hovold told this: >> > On Wed, Nov 05, 2014 at 03:14:49PM +, Nix wrote: > >> > Could you try two more things (too make sure line control is really

Re: [3.16.1 BISECTED REGRESSION]: Simtec Entropy Key (cdc-acm) broken in 3.16

2014-11-06 Thread Nix
On 5 Nov 2014, Johan Hovold told this: > On Wed, Nov 05, 2014 at 03:14:49PM +0000, Nix wrote: >> >> > What if you >> >> > physically disconnect and reconnect the device instead, or simply >> >> >

Re: [3.16.1 BISECTED REGRESSION]: Simtec Entropy Key (cdc-acm) broken in 3.16

2014-11-05 Thread Nix
On 5 Nov 2014, Johan Hovold stated: > On Fri, Oct 31, 2014 at 04:44:46PM +0000, Nix wrote: >> Sorry for the delay: illness and work-related release time flurries. >> >> On 24 Oct 2014, Johan Hovold told this: >> >> > [ +CC: linux-usb ] >> > >&

Re: [3.16.1 BISECTED REGRESSION]: Simtec Entropy Key (cdc-acm) broken in 3.16

2014-10-31 Thread Nix
Sorry for the delay: illness and work-related release time flurries. On 24 Oct 2014, Johan Hovold told this: > [ +CC: linux-usb ] > > On Wed, Oct 22, 2014 at 04:36:59PM +0100, Nix wrote: >> On 22 Oct 2014, Johan Hovold outgrape: >> >> > On Wed, Oct 22, 2014

Re: [3.16.1 BISECTED REGRESSION]: Simtec Entropy Key (cdc-acm) broken in 3.16

2014-10-24 Thread Nix
On 24 Oct 2014, Johan Hovold told this: > [ +CC: linux-usb ] > On Wed, Oct 22, 2014 at 04:36:59PM +0100, Nix wrote: >> On 22 Oct 2014, Johan Hovold outgrape: >> >> > On Wed, Oct 22, 2014 at 10:31:17AM +0100, Nix wrote: >> >> On 14 Oct 2014, Johan Hovold ve

Re: Looks like a broken hub? (was Re: 3.16.2: 2TiB Seagate Expansion Desk apparently still broken with both USB mass storage *and* UAS: some debugging output)

2014-09-07 Thread Nix
[linux-scsi dropped, this is not a scsi or uas problem.] On 7 Sep 2014, n...@esperi.org.uk stated: > And... now it works, at least well enough to get a device file. So it's > not the disk that's at fault: it's the no-name hub! (Which is, I think, > USB ID 2109:0811 -- at least two instances of thi

Looks like a broken hub? (was Re: 3.16.2: 2TiB Seagate Expansion Desk apparently still broken with both USB mass storage *and* UAS: some debugging output)

2014-09-07 Thread Nix
On 7 Sep 2014, Alan Stern spake thusly: > On Sun, 7 Sep 2014, Nix wrote: > >> I have a brand new Seagate Expansion Desk drive attached to my x86-64 >> desktop. (I also have a 4TiB model of the same drive, but I haven't even >> unboxed it: there seems little poin

3.16.2: 2TiB Seagate Expansion Desk apparently still broken with both USB mass storage *and* UAS: some debugging output

2014-09-07 Thread Nix
I have a brand new Seagate Expansion Desk drive attached to my x86-64 desktop. (I also have a 4TiB model of the same drive, but I haven't even unboxed it: there seems little point as long as the 2TiB version doesn't work.) I am seeing apparently the same problem as Alexandre Oliva reported in