March 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1177624] watchdog: BUG: soft lockup - CPU#16 stuck for 23s! [qemu-system-aar:4554]
by bugzilla_noreply＠suse.com 08 Mar '22

08 Mar '22

https://bugzilla.suse.com/show_bug.cgi?id=1177624 https://bugzilla.suse.com/show_bug.cgi?id=1177624#c5 Oliver Kurz <okurz(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX |--- --- Comment #5 from Oliver Kurz <okurz(a)suse.com> --- As you reported yourself this is still appearing, see https://progress.opensuse.org/issues/107980 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1195464] intel: screenlocker does not wake up after sleep
by bugzilla_noreply＠suse.com 08 Mar '22

08 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1195464 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|X.Org |Kernel Assignee|gfx-bugs(a)suse.de |kernel-bugs(a)opensuse.org QA Contact|gfx-bugs(a)suse.de |qa-bugs(a)suse.de -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196802] Iwlwifi Fails to Probe Intel Wireless CNVi
by bugzilla_noreply＠suse.com 08 Mar '22

08 Mar '22

https://bugzilla.suse.com/show_bug.cgi?id=1196802 https://bugzilla.suse.com/show_bug.cgi?id=1196802#c6 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(onur@delipenguen. | |net) --- Comment #6 from Takashi Iwai <tiwai(a)suse.com> --- Thanks. It turned out that this is a pretty new device and the iwlwifi driver supports this since 5.17 (still in rc), as it seems. I backported the patches to SLE15-SP4, and the test kernel is being built in home:tiwai:bsc1196802 repo. Once after the build finishes (will take an hour or so), it'll be available at http://download.opensuse.org/repositories/home:/tiwai:/bsc1196802/pool/ Could you give it a try later? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189808] New: udp datagrams received out-of-order with kernel 5.3.18-lp152.72.1 onwards
by bugzilla_noreply＠suse.com 08 Mar '22

08 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1189808 Bug ID: 1189808 Summary: udp datagrams received out-of-order with kernel 5.3.18-lp152.72.1 onwards Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: simonalogan(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36 Build Identifier: Hi folks, We have observed that Leap 15.2 kernels 5.3.18-lp152.72.1 onwards frequently deliver UDP packets out of order. The issue is 100% reproducable on Haswell hardware, for example an Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz machine. I know UDP makes no guarantee of packet delivery order, but previous kernels always seemed to deliver packets in order. Did something change in 72.1 that would affect this? We noticed this affecting video streaming, but it is easily reproducable using iperf. Please see steps below. Thanks, Simon Reproducible: Always Steps to Reproduce: - Run an iperf server on the Haswell box. iperf3 -s - Now run a set of 10 tests, asking a remote client to receive 300Mbit blocks of UDP data. for iter in 0 1 2 3 4 5 6 7 8 9; do echo "iter: $iter"; iperf3 -c 192.168.1.10 -u -b 300M -R | grep "datagrams received out-of-order"; done Using kernel 5.3.18-lp152.60 I see no out-of-order datagrams. Using kernel 5.3.18-lp152.87 I see > 10k out-of-order datagrams on each run. Actual Results: Using the 5.3.18-lp152.87 kernel: iter: 0 [SUM] 0.0-10.0 sec 22283 datagrams received out-of-order iter: 1 [SUM] 0.0-10.0 sec 23910 datagrams received out-of-order iter: 2 [SUM] 0.0-10.0 sec 20661 datagrams received out-of-order iter: 3 [SUM] 0.0-10.0 sec 20182 datagrams received out-of-order iter: 4 [SUM] 0.0-10.0 sec 18224 datagrams received out-of-order iter: 5 [SUM] 0.0-10.0 sec 19448 datagrams received out-of-order iter: 6 [SUM] 0.0-10.0 sec 27404 datagrams received out-of-order iter: 7 [SUM] 0.0-10.0 sec 17781 datagrams received out-of-order iter: 8 [SUM] 0.0-10.0 sec 11182 datagrams received out-of-order iter: 9 [SUM] 0.0-10.0 sec 25676 datagrams received out-of-order Here's the full output from one run: [ 5] local 192.168.1.8 port 53594 connected to 192.168.1.10 port 5201 [ ID] Interval Transfer Bitrate Jitter Lost/Total Datagrams [ 5] 0.00-1.00 sec 35.8 MBytes 300 Mbits/sec 0.010 ms 0/25904 (0%) [ 5] 1.00-2.00 sec 35.7 MBytes 300 Mbits/sec 0.024 ms 0/25888 (0%) [ 5] 2.00-3.00 sec 35.8 MBytes 300 Mbits/sec 0.027 ms 0/25897 (0%) [ 5] 3.00-4.00 sec 35.8 MBytes 300 Mbits/sec 0.012 ms 1/25908 (0.0039%) [ 5] 4.00-5.00 sec 35.8 MBytes 300 Mbits/sec 0.021 ms -1/25897 (-0.0039%) [ 5] 5.00-6.00 sec 35.8 MBytes 300 Mbits/sec 0.017 ms 0/25897 (0%) [ 5] 6.00-7.00 sec 35.7 MBytes 300 Mbits/sec 0.032 ms 0/25887 (0%) [ 5] 7.00-8.00 sec 35.8 MBytes 300 Mbits/sec 0.012 ms 0/25909 (0%) [ 5] 8.00-9.00 sec 35.8 MBytes 300 Mbits/sec 0.009 ms 0/25899 (0%) [ 5] 9.00-10.00 sec 35.8 MBytes 300 Mbits/sec 0.015 ms 0/25897 (0%) - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Jitter Lost/Total Datagrams [ 5] 0.00-10.00 sec 358 MBytes 300 Mbits/sec 0.000 ms 0/259008 (0%) sender [SUM] 0.0-10.0 sec 22745 datagrams received out-of-order [ 5] 0.00-10.00 sec 358 MBytes 300 Mbits/sec 0.015 ms 0/258983 (0%) receiver Going the other way simon@localhost:~> iperf3 -c 192.168.1.10 -u -b 300M Connecting to host 192.168.1.10, port 5201 [ 5] local 192.168.1.8 port 56004 connected to 192.168.1.10 port 5201 [ ID] Interval Transfer Bitrate Total Datagrams [ 5] 0.00-1.00 sec 35.7 MBytes 300 Mbits/sec 25878 [ 5] 1.00-2.00 sec 35.8 MBytes 300 Mbits/sec 25898 [ 5] 2.00-3.00 sec 35.8 MBytes 300 Mbits/sec 25900 [ 5] 3.00-4.00 sec 35.8 MBytes 300 Mbits/sec 25910 [ 5] 4.00-5.00 sec 35.7 MBytes 300 Mbits/sec 25878 [ 5] 5.00-6.00 sec 35.8 MBytes 300 Mbits/sec 25919 [ 5] 6.00-7.00 sec 35.7 MBytes 300 Mbits/sec 25882 [ 5] 7.00-8.00 sec 35.8 MBytes 300 Mbits/sec 25897 [ 5] 8.00-9.00 sec 35.8 MBytes 300 Mbits/sec 25898 [ 5] 9.00-10.00 sec 35.8 MBytes 300 Mbits/sec 25898 - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Jitter Lost/Total Datagrams [ 5] 0.00-10.00 sec 358 MBytes 300 Mbits/sec 0.000 ms 0/258958 (0%) sender [ 5] 0.00-10.00 sec 358 MBytes 300 Mbits/sec 0.013 ms 6/258958 (0.0023%) receiver Expected Results: Based on kernel 5.3.18-lp152.60, I expect no out-of-order datagrams. -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 1196855] New: [RPi4] vc4_hdmi driver is crashing when 4K monitor is connected
by bugzilla_noreply＠suse.com 08 Mar '22

08 Mar '22

https://bugzilla.suse.com/show_bug.cgi?id=1196855 Bug ID: 1196855 Summary: [RPi4] vc4_hdmi driver is crashing when 4K monitor is connected Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ivan.ivanov(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I am seeing following driver crash when boot with 4K monitor attached or when I plug it later: [ 87.272347][ T687] Unable to handle kernel read from unreadable memory at virtual address 0000000000000348 [ 87.282260][ T687] Mem abort info: [ 87.285796][ T687] ESR = 0x96000004 [ 87.289597][ T687] EC = 0x25: DABT (current EL), IL = 32 bits [ 87.295723][ T687] SET = 0, FnV = 0 [ 87.299525][ T687] EA = 0, S1PTW = 0 [ 87.303428][ T687] FSC = 0x04: level 0 translation fault [ 87.309082][ T687] Data abort info: [ 87.312713][ T687] ISV = 0, ISS = 0x00000004 [ 87.317307][ T687] CM = 0, WnR = 0 [ 87.321018][ T687] user pgtable: 4k pages, 48-bit VAs, pgdp=0000000103aef000 [ 87.328268][ T687] [0000000000000348] pgd=0000000000000000, p4d=0000000000000000 [ 87.335882][ T687] Internal error: Oops: 96000004 [#1] SMP [ 87.341537][ T687] Modules linked in: af_packet(E) algif_hash(E) aes_neon_bs(E) aes_neon_blk(E) algif_skcipher(E) af_alg(E) bnep(E) cpufreq_dt(E) snd_soc_hdmi_codec(E) btsdio(E) hci_uart(E) btqca(E) btrtl(E) btbcm(E) brcmfmac(E) btintel(E) bluetooth(E) brcmutil(E) cfg80211(E) ecdh_generic(E) rfkill(E) raspberrypi_cpufreq(E) vc4(E) drm_kms_helper(E) broadcom(E) cec(E) bcm2711_thermal(E) rc_core(E) snd_soc_core(E) bcm_phy_lib(E) snd_compress(E) iproc_rng200(E) ac97_bus(E) snd_pcm_dmaengine(E) snd_pcm(E) snd_timer(E) snd(E) genet(E) mdio_bcm_unimac(E) soundcore(E) syscopyarea(E) sysfillrect(E) sysimgblt(E) nvmem_rmem(E) fb_sys_fops(E) leds_gpio(E) uio_pdrv_genirq(E) uio(E) efi_pstore(E) nls_iso8859_1(E) nls_cp437(E) vfat(E) fat(E) drm(E) fuse(E) ip_tables(E) x_tables(E) ext4(E) mbcache(E) jbd2(E) mmc_block(E) xhci_pci(E) xhci_pci_renesas(E) xhci_hcd(E) usbcore(E) usb_common(E) crct10dif_ce(E) raspberrypi_hwmon(E) clk_raspberrypi(E) gpio_raspberrypi_exp(E) i2c_brcmstb(E) [ 87.341795][ T687] clk_bcm2711_dvp(E) bcm2835_wdt(E) bcm2835_dma(E) virt_dma(E) gpio_regulator(E) pcie_brcmstb(E) phy_generic(E) sdhci_iproc(E) sdhci_pltfm(E) sdhci(E) mmc_core(E) fixed(E) sg(E) efivarfs(E) [ 87.447616][ T687] CPU: 3 PID: 687 Comm: irq/56-vc4 hdmi Tainted: G E 5.16.12-0.gc83ed31-default #1 openSUSE Tumbleweed (unreleased) df4e1cac08e5b2a7fb15702129d12fa8f60d0542 [ 87.464734][ T687] Hardware name: raspberrypi rpi/rpi, BIOS 2022.01 01/01/2022 [ 87.472147][ T687] pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 87.479917][ T687] pc : vc4_hdmi_enable_scrambling+0x44/0x270 [vc4] [ 87.486425][ T687] lr : vc4_hdmi_connector_detect+0x70/0x250 [vc4] [ 87.492829][ T687] sp : ffff800008b4bc10 [ 87.496892][ T687] x29: ffff800008b4bc10 x28: 0000000000000000 x27: 0000000000000000 [ 87.504847][ T687] x26: ffffb0874123ea70 x25: ffffb0874123eb50 x24: ffff4ada87284400 [ 87.512800][ T687] x23: ffff4ada825c8000 x22: 0000000000000001 x21: ffff4ada9c960e00 [ 87.520752][ T687] x20: ffff4ada830585d8 x19: ffff4ada83058528 x18: 0000000000000000 [ 87.528702][ T687] x17: 58b0805a70f23000 x16: ffffb0874147b1f0 x15: 5029a0a0a0005e56 [ 87.536654][ T687] x14: 005a60010706e603 x13: 005a60010706e603 x12: 0fe200c005e30180 [ 87.544605][ T687] x11: d6001a00002188b9 x10: 003a203040133880 x9 : ffffb086f98ee700 [ 87.552555][ T687] x8 : ffff800008b4bbc8 x7 : 0000000000000031 x6 : 0000000000000000 [ 87.560506][ T687] x5 : 0000000000000000 x4 : ffff4adb7efb0800 x3 : 0000000000001d84 [ 87.568455][ T687] x2 : 00000000000003e8 x1 : 000000001443fd00 x0 : 0000000000000000 [ 87.576407][ T687] Call trace: [ 87.579589][ T687] vc4_hdmi_enable_scrambling+0x44/0x270 [vc4 f9f81cc6c18ada14f57f48953a862b790f775310] [ 87.589345][ T687] vc4_hdmi_connector_detect+0x70/0x250 [vc4 f9f81cc6c18ada14f57f48953a862b790f775310] [ 87.599009][ T687] drm_helper_probe_detect_ctx+0x9c/0x120 [drm_kms_helper f15a3342071364205456da259f114c585fb81c6e] [ 87.609875][ T687] check_connector_changed+0x50/0x1ec [drm_kms_helper f15a3342071364205456da259f114c585fb81c6e] [ 87.620379][ T687] drm_connector_helper_hpd_irq_event+0x3c/0xd0 [drm_kms_helper f15a3342071364205456da259f114c585fb81c6e] [ 87.631765][ T687] vc4_hdmi_hpd_irq_thread+0x38/0x50 [vc4 f9f81cc6c18ada14f57f48953a862b790f775310] [ 87.641167][ T687] irq_thread_fn+0x38/0xb0 [ 87.645509][ T687] irq_thread+0x1b0/0x400 [ 87.649754][ T687] kthread+0x154/0x160 [ 87.653731][ T687] ret_from_fork+0x10/0x20 [ 87.658070][ T687] Code: f9402a60 52807d02 529fa001 72a28861 (f941a400) [ 87.664957][ T687] ---[ end trace 3923d3f635d7a9ff ]--- # cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20220301" -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1196837] Is kernel 5.17 rc 7 stable
by bugzilla_noreply＠suse.com 07 Mar '22

07 Mar '22

https://bugzilla.suse.com/show_bug.cgi?id=1196837 https://bugzilla.suse.com/show_bug.cgi?id=1196837#c2 Petr Tesa��k <ptesarik(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED Assignee|kernel-bugs(a)opensuse.org |ptesarik(a)suse.com --- Comment #2 from Petr Tesa��k <ptesarik(a)suse.com> --- Oops, something must have gone wrong with the recent script update... -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196802] New: Iwlwifi Fails to Probe Intel Wireless CNVi
by bugzilla_noreply＠suse.com 07 Mar '22

07 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196802 Bug ID: 1196802 Summary: Iwlwifi Fails to Probe Intel Wireless CNVi Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: onur(a)delipenguen.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0 Build Identifier: Observing on an MSI GS66 12UHS 049TR computer with Leap 15.4 Beta. Kernel version is 5.14.21-150400.10-default. Wireless device is not even created as iwlwifi fails to probe the device. [Sun Mar 6 11:33:52 2022] Intel(R) Wireless WiFi driver for Linux [Sun Mar 6 11:33:52 2022] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002) [Sun Mar 6 11:33:52 2022] i801_smbus 0000:00:1f.4: enabling device (0000 -> 0003) [Sun Mar 6 11:33:52 2022] i801_smbus 0000:00:1f.4: SPD Write Disable is set [Sun Mar 6 11:33:52 2022] i801_smbus 0000:00:1f.4: SMBus using PCI interrupt [Sun Mar 6 11:33:52 2022] iwlwifi: No config found for PCI dev 51f0/1672, rev=0x370, rfid=0x2010d000 [Sun Mar 6 11:33:52 2022] iwlwifi: probe of 0000:00:14.3 failed with error -22 00:14.3 Network controller [0280]: Intel Corporation Alder Lake-P PCH CNVi WiFi [8086:51f0] (rev 01) No wireless device created, not visible in output of commands like ip, iw etc. Tried Leap 15.3 but neither ethernet nor wireless worked there, with Leap 15.4 Beta ethernet is working. Reproducible: Always Steps to Reproduce: 1.Just booting the computer 2. 3. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1196837] New: Is kernel 5.17 rc 7 stable
by bugzilla_noreply＠suse.com 07 Mar '22

07 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196837 Bug ID: 1196837 Summary: Is kernel 5.17 rc 7 stable Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: Sauerlandlinux(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- kernel 5.17 rc7 is now in kernel:stable and kernel:stable:backport. Is this right? Or an error? Stephan -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1196779] New: Bluetooth adapter with ID not included in modul btusb
by bugzilla_noreply＠suse.com 07 Mar '22

07 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196779 Bug ID: 1196779 Summary: Bluetooth adapter with ID not included in modul btusb Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: RMurr(a)t-online.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The bluetooth adapter with ID 04f2:b49f from Chicony Electronics Co., Ltd Bluetooth Radio (Realtek RTL8723BE) is not included in Kernel modul btusb.c. Although the modul btusb is loaded automatically there is neither any device recognized nor the adapter is discoverable. Root cause: the line with following entry is missing in btusb.c { USB_DEVICE(0x04f2, 0xb49f), .driver_info = BTUSB_REALTEK }, As soon as the line is inserted all devices in range are recognized and are pairable. (Tested with Kernel 5.4.0 on Linux Mint distribution) I could not find any kernel version where the entry in btusb.c is included. -- You are receiving this mail because: You are the assignee for the bug.

1 19

[Bug 1196835] New: [riscv64][Unmatched] CPU#0 stuck forever while trying to reboot the board.
by bugzilla_noreply＠suse.com 07 Mar '22

07 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196835 Bug ID: 1196835 Summary: [riscv64][Unmatched] CPU#0 stuck forever while trying to reboot the board. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: RISC-V OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: chester.lin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 856812 --> http://bugzilla.opensuse.org/attachment.cgi?id=856812&action=edit reboot log Image: openSUSE-Tumbleweed-RISC-V-JeOS-hifiveunmatched.riscv64-2022.03.03-Build1.5.raw The CPU#0 always gets stuck when trying to run the "reboot" command. The full log is attached. However, the shutdown command works fine. Symptom ======= [ OK ] Reached target System Reboot. [ 946.451940][ T1] reboot: Restarting system [ 972.949373][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 26s! [systemd-shutdow:1] [ 972.956785][ C0] Modules linked in: af_packet iwlmvm mac80211 libarc4 btusb mscc macsec btrtl btbcm macb btintel iwlwifi phylink bluetooth of_mdio fixed_phy fwnode_m [ 973.016111][ C0] CPU: 0 PID: 1 Comm: systemd-shutdow Not tainted 5.16.11-1-default #1 openSUSE Tumbleweed 6860fdcc9bf06bdf6df5c525bc26813c2d19712e [ 973.029484][ C0] Hardware name: SiFive HiFive Unmatched A00 (DT) [ 973.035739][ C0] epc : machine_restart+0xc/0xe [ 973.040428][ C0] ra : machine_restart+0xc/0xe [ 973.045119][ C0] epc : ffffffff80003a4a ra : ffffffff80003a4a sp : ffffffd00400bd70 [ 973.053023][ C0] gp : ffffffff81771220 tp : ffffffe07fe79c00 t0 : ffffffff8178052f [ 973.060927][ C0] t1 : ffffffff81780518 t2 : 0000000000000000 s0 : ffffffd00400bd80 [ 973.068831][ C0] s1 : 0000000001234567 a0 : 0000000000000000 a1 : 0000000000000000 [ 973.076734][ C0] a2 : 0000000000000000 a3 : 0000000000000231 a4 : 0000000000000000 [ 973.084639][ C0] a5 : 0000000000000000 a6 : c0000000ffffdfff a7 : ffffffffffffffff [ 973.092543][ C0] s2 : ffffffffffffffea s3 : ffffffff81619118 s4 : fffffffffee1dead [ 973.100447][ C0] s5 : d38c929a8bffd198 s6 : 0000000000000000 s7 : 0000000000000000 [ 973.108351][ C0] s8 : 0000000000000000 s9 : 0000003fc7360d08 s10: 0000000000080080 [ 973.116255][ C0] s11: 0000000000000000 t3 : 0000000000000072 t4 : ffffffffffffffff [ 973.124159][ C0] t5 : ffffffff81618fd0 t6 : ffffffd00400bae8 [ 973.130152][ C0] status: 0000000200000120 badaddr: 0000000000000000 cause: 8000000000000005 [ 973.138753][ C0] [<ffffffff80031470>] __do_sys_reboot+0x176/0x226 [ 973.145092][ C0] [<ffffffff80031532>] sys_reboot+0x12/0x1a [ 973.150824][ C0] [<ffffffff80003024>] ret_from_syscall+0x0/0x2 [ 982.539352][ C0] BUG: workqueue lockup - pool cpus=0 node=0 flags=0x0 nice=0 stuck for 34s! [ 1006.459281][ C0] rcu: INFO: rcu_sched self-detected stall on CPU [ 1006.464780][ C0] rcu: 0-....: (5979 ticks this GP) idle=ccb/1/0x4000000000000002 softirq=6008/6008 fqs=2972 [ 1006.474941][ C0] (t=6001 jiffies g=7405 q=80) -- You are receiving this mail because: You are the assignee for the bug.

1 0