linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Regressions <regressions@lists.linux.dev>,
	Linux Kernel Network Developers <netdev@vger.kernel.org>,
	Linux Real Time <linux-rt-users@vger.kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Paolo Abeni <pabeni@redhat.com>, SamW <proaudiomanuk@gmail.com>
Subject: Fwd: commit 6e98b09da931a00bf4e0477d0fa52748bf28fcce suspect causing full system lockup
Date: Fri, 2 Jun 2023 09:27:48 +0700	[thread overview]
Message-ID: <9f12c322-fb62-26f0-46d1-61936a419468@gmail.com> (raw)

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

             reply	other threads:[~2023-06-02  2:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-02  2:27 Bagas Sanjaya [this message]
2023-06-06  1:35 ` Fwd: commit 6e98b09da931a00bf4e0477d0fa52748bf28fcce suspect causing full system lockup Bagas Sanjaya

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=9f12c322-fb62-26f0-46d1-61936a419468@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=proaudiomanuk@gmail.com \
    --cc=regressions@lists.linux.dev \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).