lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <9f12c322-fb62-26f0-46d1-61936a419468@gmail.com>
Date: Fri, 2 Jun 2023 09:27:48 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
 Linux Regressions <regressions@...ts.linux.dev>,
 Linux Kernel Network Developers <netdev@...r.kernel.org>,
 Linux Real Time <linux-rt-users@...r.kernel.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
 Paolo Abeni <pabeni@...hat.com>, SamW <proaudiomanuk@...il.com>
Subject: Fwd: commit 6e98b09da931a00bf4e0477d0fa52748bf28fcce suspect causing
 full system lockup

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ