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 DD7FDC77B7A for ; Fri, 2 Jun 2023 02:28:20 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233559AbjFBC2R (ORCPT ); Thu, 1 Jun 2023 22:28:17 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46132 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233462AbjFBC2P (ORCPT ); Thu, 1 Jun 2023 22:28:15 -0400 Received: from mail-pl1-x62a.google.com (mail-pl1-x62a.google.com [IPv6:2607:f8b0:4864:20::62a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CB99119B; Thu, 1 Jun 2023 19:28:12 -0700 (PDT) Received: by mail-pl1-x62a.google.com with SMTP id d9443c01a7336-1b038064d97so22502925ad.0; Thu, 01 Jun 2023 19:28:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1685672892; x=1688264892; h=content-transfer-encoding:subject:from:cc:to:content-language :user-agent:mime-version:date:message-id:from:to:cc:subject:date :message-id:reply-to; bh=iH1ysj30mF85sJI8Hu+UweQ/IViEKpx4ySqfGsRzxAs=; b=n9hmECaPd+ti6J6O3CLn/hnZa9po4lvtqeG9t7fTWbd6d+18sta9hEaL45qSB+zkh5 8ZA/GPZH2HTvbxXe0YEj8500pOBEml8Zp3HSPng4Oj7Pl59f6GLyb55gLV4ao6wzfqT3 tnMcUM2jZiArcSWQGP1seAeIOhtbmO7k1SHOl4kZm2AcTmBnjQMqWv4MqBFcBeEp/NkL 01ymX7ULoR8wtEItTDxzxIV1jrplntVc/AKf87k4fN2AOOMY+9tUWRzvyNWwIzejLCVy jXpBwL287rwNs0q7Uog2OFXH9ZB8Ksd3mgLBjHPGE+p/d6oaRRnGQILxkKYZtg9/vJ9l Rwwg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685672892; x=1688264892; h=content-transfer-encoding:subject:from:cc:to:content-language :user-agent:mime-version:date:message-id:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=iH1ysj30mF85sJI8Hu+UweQ/IViEKpx4ySqfGsRzxAs=; b=S8irZSA61SUHiyYV7LHQBxznHmkG5fbcjdmbobQD5bNO0/GhYgyo0QtSdr4qBAHVyc jS7czVdaUCd1IBkT8l5sGQxhIR2tSCBapamEjUvka8T19F94EhxjmewZBdVECjxMrqZO ldF5p5Dsn4uZKnFQhSAc1ct40A97Dl51/TbQ4gNga7OFlvNWQdV3oBFUsN+LaqPoXa1V fGCgL1ebNccnsV7gG8eUgMYUxBeFl1m2PSamFxvJ23IB++X5mnRANJeXavOkGi5vYrp4 6eaCYI9/xfGdT82plX4LqKUUBDaMT3o/sJ09agKHN4msUXkBuAiHpa49VphgEkBgsDfH pZhg== X-Gm-Message-State: AC+VfDym6yzNdSors8W7ZDLK+2CBfYW48ZIIezQLGvSl5EuFrXEmeSIG oezdcrGEF9TTLnRNEpBK2wNbP+zGYP0= X-Google-Smtp-Source: ACHHUZ4e6+vRjrIpsaHlh4EAancrsEHwVNsQVko2QUD7knU+Nwo4iXkRehTnlgoYJZYQRmAB6kY9Vw== X-Received: by 2002:a17:902:d2c5:b0:1b1:76c2:2966 with SMTP id n5-20020a170902d2c500b001b176c22966mr850675plc.20.1685672891925; Thu, 01 Jun 2023 19:28:11 -0700 (PDT) Received: from [192.168.43.80] (subs28-116-206-12-49.three.co.id. [116.206.12.49]) by smtp.gmail.com with ESMTPSA id t21-20020a170902b21500b001ac45598b59sm76827plr.163.2023.06.01.19.28.09 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 01 Jun 2023 19:28:11 -0700 (PDT) Message-ID: <9f12c322-fb62-26f0-46d1-61936a419468@gmail.com> Date: Fri, 2 Jun 2023 09:27:48 +0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Content-Language: en-US To: Linux Kernel Mailing List , Linux Regressions , Linux Kernel Network Developers , Linux Real Time Cc: Linus Torvalds , Paolo Abeni , SamW From: Bagas Sanjaya Subject: Fwd: commit 6e98b09da931a00bf4e0477d0fa52748bf28fcce suspect causing full system lockup Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, I notice a regression report on Bugzilla [1]. Quoting from it: > 6e98b09da931a00bf4e0477d0fa52748bf28fcce > OS slackware64-current fully upto date, on an AMD 990fx motherboard with a > Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 09). > Linux-rt-devel-rc2-rt1 and linux-rt-devel-6.4-rc3-rt2 had same issue, previous linux-rt-devel-6.3.3-rt15 worked with no issue. > > Hello I suspect this series of commits is causing the full system lock im having when using the r8169 driver with linux-rt-devel-6.4-rc3-rt2. With the driver enabled my system locks up with a few mins of booting and logging into desktop. I have to use power off button and reboot to older kernel. With the r8169 driver blacklisted the kernel works perfectly. > My syslog attachment shows the driver errors and after looking at commits I saw the above numbered as being the most likly cause. > A member of oftc linux-rt irc channel looked and gave the comment posted below. > "tell the driver maintainers they must not enable the irq in the napi poll function" > He said it looked like that could be causing the errors and then full system lockup. > please contact me if any further information is required. > > My fix has been blacklist r8169 and use the r8168 driver from relatek with a patch to enable builfing with the 6.4 kernel. > Thank you for your time > SamW See Bugzilla for the full thread and attached syslog. Anyway, I'm adding it to regzbot: #regzbot introduced: 6e98b09da931a0 https://bugzilla.kernel.org/show_bug.cgi?id=217519 #regzbot title: Networking pull for v6.4 causes full system lockup on RTL8111/8168/8411 Thanks. [1]: https://bugzilla.kernel.org/show_bug.cgi?id=217519 -- An old man doll... just what I always wanted! - Clara