> A more detailed look through the email archives and git log finds the
> following two commits, either of which might be relevant:
>
> 511833acfc06 ("SCSI: fix regression in scsi_send_eh_cmnd()")
> f45681f9beca ("USB: Add quirk to support DJI CineSSD")
>
> For the second commit, it m
On Fri, 24 May 2019, Schmid, Carsten wrote:
> > On Thu, 23 May 2019, Schmid, Carsten wrote:
> >
> > > Hi USB maintainers,
> > >
> > > we recently have seen a problem with usb-storage when trying to read
> > from a device.
> > > This happened on a 4.14.86 kernel.
> > >
> > > The kernel's dmesg sho
On Fri, May 24, 2019 at 01:33:14PM +, Schmid, Carsten wrote:
> > On Thu, 23 May 2019, Schmid, Carsten wrote:
> >
> > > Hi USB maintainers,
> > >
> > > we recently have seen a problem with usb-storage when trying to read
> > from a device.
> > > This happened on a 4.14.86 kernel.
> > >
> > > Th
> On Thu, 23 May 2019, Schmid, Carsten wrote:
>
> > Hi USB maintainers,
> >
> > we recently have seen a problem with usb-storage when trying to read
> from a device.
> > This happened on a 4.14.86 kernel.
> >
> > The kernel's dmesg shows: (log has been submitted via DLT)
> > 1200.862250 kernel: us
On Thu, May 23, 2019 at 01:16:12PM +, Schmid, Carsten wrote:
> > > >
> > > > 4.14.102 is still old.
> > > I agree
> > >
> > > > > Porting a 5.1 will take a lot of effort.
> > > >
> > > > Then that implies you have an SoC with a few million lines of code added
> > > > to the kernel, right? Noth
On Thu, 23 May 2019, Schmid, Carsten wrote:
> Hi USB maintainers,
>
> we recently have seen a problem with usb-storage when trying to read from a
> device.
> This happened on a 4.14.86 kernel.
>
> The kernel's dmesg shows: (log has been submitted via DLT)
> 1200.862250 kernel: usb 1-3.1: reset
> > >
> > > 4.14.102 is still old.
> > I agree
> >
> > > > Porting a 5.1 will take a lot of effort.
> > >
> > > Then that implies you have an SoC with a few million lines of code added
> > > to the kernel, right? Nothing we can do here about that mess, you need
> > > to go ask for support from the
On Thu, May 23, 2019 at 12:30:06PM +, Schmid, Carsten wrote:
> > > > Wow that's an old kernel.
> > > Indeed. Long running project.
> > >
> > > > Can you reproduce this on a "clean" 5.1 kernel release?
> > > As this is an automotive embedded target, we currently have 4.14.102 as
> > > the newe
> > > Wow that's an old kernel.
> > Indeed. Long running project.
> >
> > > Can you reproduce this on a "clean" 5.1 kernel release?
> > As this is an automotive embedded target, we currently have 4.14.102 as the
> > newest custom kernel.
>
> 4.14.102 is still old.
I agree
> > Porting a 5.1 will
On Thu, May 23, 2019 at 12:16:59PM +, Schmid, Carsten wrote:
> > Wow that's an old kernel.
> Indeed. Long running project.
>
> > Can you reproduce this on a "clean" 5.1 kernel release?
> As this is an automotive embedded target, we currently have 4.14.102 as the
> newest custom kernel.
4.14.
> Wow that's an old kernel.
Indeed. Long running project.
> Can you reproduce this on a "clean" 5.1 kernel release?
As this is an automotive embedded target, we currently have 4.14.102 as the
newest custom kernel.
Porting a 5.1 will take a lot of effort.
Anyway, thanks for quick response.
I'll c
On Thu, May 23, 2019 at 11:57:06AM +, Schmid, Carsten wrote:
> Hi USB maintainers,
>
> we recently have seen a problem with usb-storage when trying to read from a
> device.
> This happened on a 4.14.86 kernel.
Wow that's an old kernel.
>
> The kernel's dmesg shows: (log has been submitted
Hi USB maintainers,
we recently have seen a problem with usb-storage when trying to read from a
device.
This happened on a 4.14.86 kernel.
The kernel's dmesg shows: (log has been submitted via DLT)
1200.862250 kernel: usb 1-3.1: reset high-speed USB device number 10 using
xhci_hcd
1285.466289 k
13 matches
Mail list logo
