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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id BAC1FE8FDC7 for ; Wed, 4 Oct 2023 04:45:00 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241046AbjJDEpB (ORCPT ); Wed, 4 Oct 2023 00:45:01 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43614 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229896AbjJDEpA (ORCPT ); Wed, 4 Oct 2023 00:45:00 -0400 Received: from wp530.webpack.hosteurope.de (wp530.webpack.hosteurope.de [80.237.130.52]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4A24690; Tue, 3 Oct 2023 21:44:56 -0700 (PDT) Received: from [2a02:8108:8980:2478:8cde:aa2c:f324:937e]; authenticated by wp530.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1qntkk-0007Y7-3n; Wed, 04 Oct 2023 06:44:54 +0200 Message-ID: Date: Wed, 4 Oct 2023 06:44:52 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: rt8000usb driver issue (maybe interaction with other drivers) Content-Language: en-US, de-DE To: enc0der , Stanislaw Gruszka Cc: Bagas Sanjaya , Linux Regressions , Linux Kernel Mailing List , Linux Wireless References: <20231002185053.GB402943@wp.pl> From: "Linux regression tracking (Thorsten Leemhuis)" Reply-To: Linux regressions mailing list In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-bounce-key: webpack.hosteurope.de;regressions@leemhuis.info;1696394696;201ff504; X-HE-SMSGID: 1qntkk-0007Y7-3n Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04.10.23 03:34, enc0der wrote: > > [ 1542.248686] CPU: 3 PID: 29 Comm: ksoftirqd/3 Tainted: G W > OE 5.10.120-tegra #1 FWIW, 5.10.120 is ancient from the upstream perspective. And I assume that "-tegra" indicates that this is a vendor kernel that most likely is heavily patched -- and those changes might be the reason for the problem. Therefore you should report this to your vendor. See "Make sure you're using the upstream Linux kernel" in https://docs.kernel.org/admin-guide/reporting-issues.html for details. If you want help from the upstream Linux kernel developers, please reproduce the problem with latest mainline. Ciao, Thorsten