[Kernel-packages] [Bug 1931001] Re: Soft lockup due to interrupt storm from smbus

2021-12-17 Thread paul janssen
** Summary changed: - kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! + Soft lockup due to interrupt storm from smbus -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1931

[Kernel-packages] [Bug 1931001] Re: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s!

2021-12-03 Thread paul janssen
Believed to be fixed in the kernel by two commits. See: https://bugzilla.kernel.org/show_bug.cgi?id=177311#c65 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1931001 Title: kern

[Kernel-packages] [Bug 1931001] Re: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s!

2021-11-07 Thread paul janssen
New best workaround, instead of blacklisting i2c-i801 keep it but disable interrupts and use polling instead. Step 1 Temporary and to be able to boot for step 2). a. To able to boot enter the grub menu (press ESC once during boot) b. select the (Ubuntu)Linux entry you want to boot and press "e" to

[Kernel-packages] [Bug 1931001] Re: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s!

2021-11-04 Thread paul janssen
I started kernel bisecting in an attempt to find the commit that causes this issue. Painfull process. I found another workaround (not a solution) on stackoverflow (which has been deleted from stackoverflow by now). The workaround was to disable virtualization in the BIOS: Intel VTX -> disabled ,

[Kernel-packages] [Bug 1931001] Re: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s!

2021-10-11 Thread paul janssen
I also tied blacklisting only "i801_smbus" but that gave the same issue. Only blacklisting "i2c_i801" is currently the best workaround. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bu

[Kernel-packages] [Bug 1931001] Re: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s!

2021-10-11 Thread paul janssen
** Bug watch added: Red Hat Bugzilla #2009977 https://bugzilla.redhat.com/show_bug.cgi?id=2009977 ** Also affects: fedora via https://bugzilla.redhat.com/show_bug.cgi?id=2009977 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of

[Kernel-packages] [Bug 1931001] Re: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s!

2021-10-08 Thread paul janssen
Possible work around (not a fix), blacklist module i2c_i801. It works for me ... Since I noticed a high amount of CPU time spent in interrupt handling I looked at /proc/interrupts (right after the slow boot and slow login): $ cat /proc/interrupts CPU0 CPU1 0:

[Kernel-packages] [Bug 1931001] Re: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s!

2021-10-07 Thread paul janssen
Also tried kernel parameter watchdog_thresh=20, same problem -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1931001 Title: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 2

[Kernel-packages] [Bug 1931001] Re: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s!

2021-10-07 Thread paul janssen
Since I was not to use "Also affects distribution/package" functionality, I add the following links of very simular bugreports in distro's other than Ubuntu: * https://bugs.archlinux.org/task/71575 * https://bugs.archlinux.org/task/70236 * https://bbs.archlinux.org/viewtopic.php?id=264127 * https:

[Kernel-packages] [Bug 1931001] Re: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s!

2021-10-07 Thread paul janssen
Same same, after upgrade from 5.8 to 5.11. Soft lockups during boot, long boot time, and after that a very slow machine. My machine is also Intel Celeron based, like the previous reports. After login into the desktop environment, the "atop" program shows that almost all cpu time is spent in irq,