All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Schmid, Carsten" <Carsten_Schmid@mentor.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: AW: Crash/hung task in usb-storage thread
Date: Thu, 23 May 2019 12:30:06 +0000	[thread overview]
Message-ID: <4412d0ddd08e41009d46c018d50ce5c3@SVR-IES-MBX-03.mgc.mentorg.com> (raw)
In-Reply-To: <20190523122626.GA26641@kroah.com>

> > > 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 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 vendor that is forcing you to use that
> kernel, sorry :(
>

Well its at least an x86-64 based SoC.
I'll contact the vendor for sure.

> good luck!
Thanks. Will need it. ;-)

Carsten

  reply	other threads:[~2019-05-23 12:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-23 11:57 Crash/hung task in usb-storage thread Schmid, Carsten
2019-05-23 12:04 ` Greg KH
2019-05-23 12:16   ` AW: " Schmid, Carsten
2019-05-23 12:26     ` Greg KH
2019-05-23 12:30       ` Schmid, Carsten [this message]
2019-05-23 12:35         ` Greg KH
2019-05-23 13:16           ` AW: " Schmid, Carsten
2019-05-23 18:05             ` Greg KH
2019-05-23 16:50 ` Alan Stern
2019-05-24 13:33   ` AW: " Schmid, Carsten
2019-05-24 14:59     ` Greg KH
2019-05-24 15:24     ` AW: " Alan Stern
2019-05-24 15:47       ` AW: " Schmid, Carsten

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=4412d0ddd08e41009d46c018d50ce5c3@SVR-IES-MBX-03.mgc.mentorg.com \
    --to=carsten_schmid@mentor.com \
    --cc=gregkh@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.