From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.5 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, T_DKIMWL_WL_HIGH,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2964EC282E1 for ; Thu, 23 May 2019 12:26:30 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id EDEFA20851 for ; Thu, 23 May 2019 12:26:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1558614390; bh=uxY0goRxIH7FVXM1u2k7AIkNk1QNtD/4V0eD23yFcMg=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=1Kk1I8Pwk1Wm8l/VQIZBRa34RPndsiIt52IQNtdb7pcyc+4PIoUJGA24tWJ6Av/iN A+DWFvTeJKqUmqguHqtvaf4c4wSTfUUZ/kHO4IBwDv8Nf9jDeeshYSv9oN2SAc9xVW 5qBv9MW2KoDCvjdYmqyCYrp8B49jkxU/84ZZ+3Gc= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730769AbfEWM03 (ORCPT ); Thu, 23 May 2019 08:26:29 -0400 Received: from mail.kernel.org ([198.145.29.99]:46456 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730763AbfEWM03 (ORCPT ); Thu, 23 May 2019 08:26:29 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 4555C2133D; Thu, 23 May 2019 12:26:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1558614388; bh=uxY0goRxIH7FVXM1u2k7AIkNk1QNtD/4V0eD23yFcMg=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=REav7a8UMvtR1Y70EbCa80zEgVPGHiqEOwjoIGGklvgeKSjAXVKBbGrGHYnSAiLuD UCQ3Ig4sIyWikrO7d8+PrAHHl/c5jTB5I6s7lXiT0sjsi+zZ0mtPDNjKunOVDTUiV7 YOTpFWxSRJHwTm81a9F6y0FViiFmXAte0Y2ZW5lg= Date: Thu, 23 May 2019 14:26:26 +0200 From: Greg KH To: "Schmid, Carsten" Cc: "linux-usb@vger.kernel.org" Subject: Re: Crash/hung task in usb-storage thread Message-ID: <20190523122626.GA26641@kroah.com> References: <20190523120410.GA16571@kroah.com> <3bb81d0da7de4745852aef52802f3b9b@SVR-IES-MBX-03.mgc.mentorg.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3bb81d0da7de4745852aef52802f3b9b@SVR-IES-MBX-03.mgc.mentorg.com> User-Agent: Mutt/1.11.4 (2019-03-13) Sender: linux-usb-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-usb@vger.kernel.org On Thu, May 23, 2019 at 12:16:59PM +0000, 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.102 is still old. > 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 :( good luck! greg k-h