August 2020 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[kernel-bugs] [Bug 1174622] New: System not reconnecting to WLAN after suspend/resume

by bugzilla_noreply＠suse.com

https://bugzilla.suse.com/show_bug.cgi?id=1174622 Bug ID: 1174622 Summary: System not reconnecting to WLAN after suspend/resume Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: holgi(a)suse.com QA Contact: qa-bugs(a)suse.de CC: tiwai(a)suse.com Found By: Development Blocker: --- Created attachment 840122 --> https://bugzilla.suse.com/attachment.cgi?id=840122&action=edit Output of hwinfo --netcard System with NetworkManger is connected to a wifi network. After suspend and resume later, it is not able to reconnect to the same wifi network. After a reboot, system is connecting to the same wifi network without any problems. -- You are receiving this mail because: You are the assignee for the bug.

3 months, 3 weeks

1
25
0 0

[kernel-bugs] [Bug 1173294] New: iwlwifi: TX on unused queue 5 WARNING: tx.c:2346 iwl_trans_pcie_tx+0xa1e/0x1150

by bugzilla_noreply＠suse.com

https://bugzilla.suse.com/show_bug.cgi?id=1173294 Bug ID: 1173294 Summary: iwlwifi: TX on unused queue 5 WARNING: tx.c:2346 iwl_trans_pcie_tx+0xa1e/0x1150 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ddiss(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This looks similar to: https://bugzilla.kernel.org/show_bug.cgi?id=204643 I hit the following WARNING while playing with network manager's new activate hotspot UI functionality and then disabling all radio (nmcli radio wifi off): [ 1157.323257] wlan1: deauthenticating from 34:31:XX:XX:XX:XX by local choice (Reason: 3=DEAUTH_LEAVING) [ 1157.323301] ------------[ cut here ]------------ [ 1157.323302] TX on unused queue 5 [ 1157.323343] WARNING: CPU: 3 PID: 6784 at ../drivers/net/wireless/intel/iwlwifi/pcie/tx.c:2346 iwl_trans_pcie_tx+0xa1e/0x1150 [iwlwifi] [ 1157.323344] Modules linked in: tun ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 ebtable_nat ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptablet [ 1157.323376] snd_hda_core dell_smm_hwmon fat kvm snd_hwdep dell_wmi dell_smbios irqbypass iwlwifi dcdbas joydev snd_pcm snd_timer sparse_keymap mei_me cfg80211 dell_wmi_d] [ 1157.323412] CPU: 3 PID: 6784 Comm: kworker/3:1 Not tainted 5.3.18-lp152.19-default #1 openSUSE Leap 15.2 (unreleased) [ 1157.323413] Hardware name: Dell Inc. Latitude E7450/0YGN55, BIOS A21 05/16/2019 [ 1157.323434] Workqueue: events cfg80211_rfkill_sync_work [cfg80211] [ 1157.323444] RIP: 0010:iwl_trans_pcie_tx+0xa1e/0x1150 [iwlwifi] [ 1157.323447] Code: 80 3d 2b 65 03 00 00 b8 ea ff ff ff 0f 85 25 f8 ff ff 89 ce 48 c7 c7 49 6e d8 c0 89 04 24 c6 05 0d 65 03 00 01 e8 42 94 33 e1 <0f> 0b 8b 04 24 e9 03 f8 c [ 1157.323448] RSP: 0018:ffff9f66404bf7f0 EFLAGS: 00010282 [ 1157.323449] RAX: 0000000000000000 RBX: 0000000000000005 RCX: 0000000000000006 [ 1157.323450] RDX: 0000000000000007 RSI: 0000000000000096 RDI: ffff93915e399a10 [ 1157.323451] RBP: ffff939155e59e28 R08: 000000000000065e R09: 0000000000000001 [ 1157.323452] R10: 0000000000000005 R11: 0000000000000001 R12: ffff9390f1cc4b00 [ 1157.323453] R13: 0000000000000005 R14: 0000000000000037 R15: ffff9391566683e8 [ 1157.323454] FS: 0000000000000000(0000) GS:ffff93915e380000(0000) knlGS:0000000000000000 [ 1157.323455] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 1157.323456] CR2: 00007f8e2af0a000 CR3: 00000002ba00a005 CR4: 00000000003606e0 [ 1157.323457] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 1157.323458] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 1157.323459] Call Trace: [ 1157.323473] ? iwl_mvm_set_tx_cmd+0x1a2/0x480 [iwlmvm] [ 1157.323483] ? iwl_mvm_get_tx_rate.isra.21+0x44/0xe0 [iwlmvm] [ 1157.323491] ? iwl_mvm_get_tx_ant+0x43/0x80 [iwlmvm] [ 1157.323499] ? iwl_mvm_set_tx_params+0x11f/0x4e0 [iwlmvm] [ 1157.323507] iwl_mvm_tx_mpdu+0x207/0x600 [iwlmvm] [ 1157.323516] iwl_mvm_tx_skb_sta+0x1ed/0x480 [iwlmvm] [ 1157.323524] iwl_mvm_tx_skb+0x17/0x40 [iwlmvm] [ 1157.323532] iwl_mvm_mac_itxq_xmit+0x7a/0xf0 [iwlmvm] [ 1157.323559] ieee80211_queue_skb+0x2da/0x420 [mac80211] [ 1157.323582] ieee80211_tx+0xd9/0x130 [mac80211] [ 1157.323604] __ieee80211_tx_skb_tid_band+0x58/0x70 [mac80211] [ 1157.323627] ieee80211_send_deauth_disassoc+0xfd/0x130 [mac80211] [ 1157.323649] ieee80211_set_disassoc+0x3a0/0x5e0 [mac80211] [ 1157.323679] ieee80211_mgd_deauth+0x113/0x230 [mac80211] [ 1157.323701] cfg80211_mlme_deauth+0xaf/0x1c0 [cfg80211] [ 1157.323720] cfg80211_mlme_down+0x7b/0x90 [cfg80211] [ 1157.323739] cfg80211_disconnect+0x11f/0x1d0 [cfg80211] [ 1157.323754] cfg80211_leave+0x26/0x40 [cfg80211] [ 1157.323767] cfg80211_netdev_notifier_call+0x258/0x5b0 [cfg80211] [ 1157.323774] ? iwl_mvm_set_tim+0x50/0x50 [iwlmvm] [ 1157.323794] ? __iterate_interfaces+0x78/0x110 [mac80211] [ 1157.323800] ? iwl_mvm_set_tim+0x50/0x50 [iwlmvm] [ 1157.323817] ? __iterate_interfaces+0x78/0x110 [mac80211] [ 1157.323831] ? ieee80211_iterate_active_interfaces_atomic+0xd/0x10 [mac80211] [ 1157.323838] ? iwl_mvm_recalc_multicast+0x45/0x70 [iwlmvm] [ 1157.323841] ? rtnl_is_locked+0x11/0x20 [ 1157.323843] ? inetdev_event+0x46/0x5c0 [ 1157.323850] ? iwl_mvm_configure_filter+0x61/0x80 [iwlmvm] [ 1157.323853] notifier_call_chain+0x47/0x70 [ 1157.323855] __dev_close_many+0x5f/0x110 [ 1157.323857] dev_close_many+0x7c/0x120 [ 1157.323859] dev_close.part.104+0x3e/0x70 [ 1157.323874] cfg80211_shutdown_all_interfaces+0x6d/0xc0 [cfg80211] [ 1157.323886] cfg80211_rfkill_sync_work+0x29/0x30 [cfg80211] [ 1157.323889] process_one_work+0x1f4/0x3e0 [ 1157.323892] worker_thread+0x2d/0x3e0 [ 1157.323894] ? process_one_work+0x3e0/0x3e0 [ 1157.323895] kthread+0x10d/0x130 [ 1157.323897] ? kthread_park+0xa0/0xa0 [ 1157.323899] ret_from_fork+0x35/0x40 [ 1157.323902] ---[ end trace 3217541a75ee82c3 ]--- I've not been able to reproduce it so far, but will update when/if I get a clear procedure. -- You are receiving this mail because: You are the assignee for the bug.

4 months

1
10
0 0

[kernel-bugs] [Bug 1173819] New: 'BUG: workqueue lockup' on ThunderX2 machines with kernel 4.12.14 in OBS

by bugzilla_noreply＠suse.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1173819 Bug ID: 1173819 Summary: 'BUG: workqueue lockup' on ThunderX2 machines with kernel 4.12.14 in OBS Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de CC: adrian.schroeter(a)suse.com, afaerber(a)suse.com, dmueller(a)suse.com Found By: --- Blocker: --- obs-arm-7, -8 and -9 are often down in OBS these days due to kernel issues. One issue is a workqueue lockup: BUG: workqueue lockup - pool cpus=59 node=0 flags=0x0 nice=0 stuck for 92265s! -- You are receiving this mail because: You are the assignee for the bug.

7 months

1
7
0 0

[kernel-bugs] [Bug 1175105] New: mdadm doesn't except partition for --add because of "dirt" in that partition of a fresh gpt table

by bugzilla_noreply＠suse.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1175105 Bug ID: 1175105 Summary: mdadm doesn't except partition for --add because of "dirt" in that partition of a fresh gpt table Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ralf(a)czekalla.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I'm about to migrate an important central private nextcloud server to 15.2. I'm use RAID1 for all my partitions and benefit from that with easy made clones with the help of mdadm by growing the number of raid-devices and adding a refreshed SSD with a new gpt partition table and cloned partitions descriptions. This worked for most of the six partitions but one. (It's not the first installation I transform with this idea. Did these processes already several times) This faulty one showed weird error messages I couldn't find a real good reason for, like ... ...on console: # mdadm --verbose /dev/md2 --add /dev/sdc5 mdadm: add new device failed for /dev/sdc5 as 4: Invalid argument # mdadm -E /dev/sdc5 /dev/sdc5: Magic : a92b4efc Version : 1.0 Feature Map : 0x9 Array UUID : 94bbbcd3:ad4d1b0b:dcd4d548:1af16050 Name : any:2 Creation Time : Fri Feb 2 20:09:03 2018 Raid Level : raid1 Raid Devices : 3 Avail Dev Size : 83892192 sectors (40.00 GiB 42.95 GB) Array Size : 41945984 KiB (40.00 GiB 42.95 GB) Used Dev Size : 83891968 sectors (40.00 GiB 42.95 GB) Super Offset : 83892208 sectors Unused Space : before=0 sectors, after=224 sectors State : active Device UUID : c9e17312:0069d580:42782958:8817e0f7 Internal Bitmap : -16 sectors from superblock Update Time : Mon Aug 10 18:09:21 2020 Bad Block Log : 512 entries available at offset -8 sectors - bad blocks present. Checksum : 7b5d72a - correct Events : 0 Device Role : spare Array State : AA. ('A' == active, '.' == missing, 'R' == replacing) First I was blinded by the "bad blocks present", but all devices checked out perfectly healthy in smart and also extended device scans didn't show any problems. Took me several hours to get through all this. dmesg: md: sdc5 does not have a valid v1.0 superblock, not importing! md: md_import_device returned -22 Also tried to --zero-superblock the partition of course. No change of behavior and still the above error message in dmesg remained. At the end I found a surprising hint on serverfault.com (https://serverfault.com/questions/696392/how-to-add-disk-back-to-raid-and-r…) from Oct. 2015 with a similar behavior that suggested to clean-up of the partition first with dd writing zeros (dd if=/dev/zero of=/dev/sdc5 status=progress) and try again later to add the last seemingly faulty partition. And long story short, this really worked. Somehow mdadm - and md behind - is choking on some dirt inside of partition blocks from old content before the disk/ssd was wiped with a new gpt partition table. (Of course with SSDs you try to prevent unnecessary writes and wiping every block of a disk first) I'm using md device type 1.0 here (in contrast to the serverfault.com case), where the RAID/md setup data is stored at the end of the partition. I had to wipe exactly this area at the end of the partition to add it afterwards successfully. Of course, no effect when doing this at the beginning of the partition (mentioned in the serverfault.com case) where md type 1.2 stores the md setup data. I think after 5 years this might need a clean up in mdadm or md device management. At least the error message should suggest to clean the partition first instead of this error message in dmesg. Also the --zero-superblock should wipe out the dirt beneath the superblock and not seemingly let some stuff leak here. Thanks Ralf -- You are receiving this mail because: You are the assignee for the bug.

9 months, 3 weeks

1
5
0 0

[kernel-bugs] [Bug 1175646] New: After bios update, some keyboard function keys not recognized.

by bugzilla_noreply＠suse.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1175646 Bug ID: 1175646 Summary: After bios update, some keyboard function keys not recognized. 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: zhonb(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I performed a bios update on a Dell precision 7530, which resolved my issue with the bug reported here: https://bugzilla.opensuse.org/show_bug.cgi?id=1175626 However, the new bios version (1.13.1) does not map the keyboard function keys correctly. Some work (e.g., volume control, keyboard backlight) and some don't (wifi toggle, screen brightness). Is there a way to map the new keyboard configuration in the bios so it works correctly in openSUSE? The keyboard functions correctly in windows. It does not work correctly in LEAP, tumbleweed or the latest fedora release. -- You are receiving this mail because: You are the assignee for the bug.

1 year, 3 months

1
6
0 0

[kernel-bugs] [Bug 1173776] New: media: add support for eyeTV Geniatech T2 lite

by bugzilla_noreply＠suse.com

https://bugzilla.suse.com/show_bug.cgi?id=1173776 Bug ID: 1173776 Summary: media: add support for eyeTV Geniatech T2 lite Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: thomas(a)abiwatch.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Would you consider to pick following patch into your kernel for Leap 15.2? commit 14494583336880640654300c76d0f5df3360d85f media: dvbsky: add support for eyeTV Geniatech T2 lite It went in to v5.5 and later it got automatically added to stable v5.4.y. It should apply cleanly and just work. -- You are receiving this mail because: You are the assignee for the bug.

1 year, 3 months

1
9
0 0

[kernel-bugs] [Bug 1175300] New: AMDGPU Driver Brightness Issue

by bugzilla_noreply＠suse.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1175300 Bug ID: 1175300 Summary: AMDGPU Driver Brightness Issue 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: jshand2013(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- hi, just checked the amdgpu brightness level and it seems to be on 20% -- You are receiving this mail because: You are the assignee for the bug.

1 year, 5 months

1
1
0 0

[kernel-bugs] [Bug 1174868] New: Upgrade to LEAP 15.2 makes Thinkpad 480s sometimes completely freezes, 20°C warmer and journal is trimmed

by bugzilla_noreply＠suse.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1174868 Bug ID: 1174868 Summary: Upgrade to LEAP 15.2 makes Thinkpad 480s sometimes completely freezes, 20°C warmer and journal is trimmed Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: markus.zimmermann(a)symflower.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- One of our machines here a Thinkpad T480s on openSUSE 15.2 kernel 5.3.18-lp152.33-default. In general this machine was upgraded from LEAP 15.1 to 15.2 and then the problems started to show. The CPU is constantly hotter while working. by 20°C. This machine now freezes sometimes completely. The machine is then - not pingable - no keyboard interaction works - lid close/open does nothng - no mouse interaction works - the notebook is really warm - When a freeze happens also a trim of the journal happens... e.g. we loose the whole journal for the day. - We SSH'ed into the machine and watched via "htop", "journal -f" and "sensors". WHen the machine freezes, there is no significant load via htop seeable, there are no interesting logs in journal and sensors shows that it is simply hotter. Interestingly, we upgraded another machine before (also a Thinkpad T480s) and this does not have any problems. We are btw on the latest firmwares using fwupdmgr. What should we try? How can we debug it? -- You are receiving this mail because: You are the assignee for the bug.

1 year, 5 months

1
19
0 0

[kernel-bugs] [Bug 1175589] New: latest kernel update gives backtrace on boot on Huawei TaiShan 2280

by bugzilla_noreply＠suse.com

https://bugzilla.suse.com/show_bug.cgi?id=1175589 Bug ID: 1175589 Summary: latest kernel update gives backtrace on boot on Huawei TaiShan 2280 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: aarch64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ro(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- System Information Manufacturer: Huawei Product Name: TaiShan 2280 Version: V100R001C00 Base Board Information Manufacturer: Huawei Product Name: BC11SPCD Version: VER.A last working kernel: obs-arm-6:~ # uname -a Linux obs-arm-6 5.3.18-lp152.33-default #1 SMP Wed Jul 22 06:32:33 UTC 2020 (e5a8383) aarch64 aarch64 aarch64 GNU/Linux crashing kernel: 5.3.18-lp152.36-default [ 198.659862] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000010 [ 198.678721] Mem abort info: [ 198.681504] ESR = 0x96000004 [ 198.681506] Exception class = DABT (current EL), IL = 32 bits [ 198.681507] SET = 0, FnV = 0 [ 198.681508] EA = 0, S1PTW = 0 [ 198.681508] Data abort info: [ 198.681511] ISV = 0, ISS = 0x00000004 [ 198.684652] audit: type=1400 audit(1598003387.680:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/nagios/plugins/check_ntp_time" pid=6829 comm="apparmor_parser" [ 198.690461] CM = 0, WnR = 0 [ 198.690463] user pgtable: 4k pages, 48-bit VAs, pgdp=0000002fb4588000 [ 198.690464] [0000000000000010] pgd=0000000000000000 [ 198.690468] Internal error: Oops: 96000004 [#1] SMP [ 198.690470] Modules linked in: joydev sbsa_gwdt hns_roce_hw_v1(+) ib_uverbs ipmi_si(+) ib_core ipmi_devintf ipmi_msghandler efivarfs ext4 mbcache jbd2 fuse squashfs lz4_decompress loop brd af_packet ses enclosure sd_mod hid_generic usbhid marvell aes_ce_blk hibmc_drm crypto_simd drm_vram_helper ttm cryptd drm_kms_helper aes_ce_cipher syscopyarea crct10dif_ce ehci_platform ghash_ce sysfillrect ehci_hcd hisi_sas_v2_hw aes_arm64 sysimgblt hisi_sas_main fb_sys_fops sha2_ce libsas sha256_arm64 drm scsi_transport_sas sha1_ce usbcore libata hns_dsaf hns_enet_drv hns_mdio hnae sg nbd dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua scsi_mod [ 198.796596] CPU: 20 PID: 6588 Comm: systemd-udevd Not tainted 5.3.18-lp152.36-default #1 openSUSE Leap 15.2 (unreleased) [ 198.796597] Hardware name: Huawei TaiShan 2280 /BC11SPCD, BIOS 1.27 06/13/2017 [ 198.796600] pstate: 60000005 (nZCv daif -PAN -UAO) [ 198.819443] pc : hns_roce_create_cq+0x2c/0x810 [hns_roce_hw_v1] [ 198.821744] audit: type=1400 audit(1598003387.820:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/nagios/plugins/check_procs" pid=6848 comm="apparmor_parser" [ 198.825353] lr : hns_roce_v1_rsv_lp_qp+0xa8/0x4f8 [hns_roce_hw_v1] [ 198.848701] sp : ffff0000239035c0 [ 198.852001] x29: ffff0000239035c0 x28: ffff802fbad92000 [ 198.857299] x27: 0000000000000010 x26: ffff802f98eee200 [ 198.862597] x25: ffff80203cbd2010 x24: ffff802fb3b71900 [ 198.867895] x23: ffff80203cbd2010 x22: ffff80203cbd2010 [ 198.872967] audit: type=1400 audit(1598003387.870:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/nagios/plugins/check_swap" pid=6858 comm="apparmor_parser" [ 198.873193] x21: ffff000011679000 x20: 0000000000000000 [ 198.895591] x19: ffff000023903708 x18: ffffffffffffffff [ 198.900888] x17: 0000000000000000 x16: ffff802fb4b93d00 [ 198.906186] x15: 00000000000019b8 x14: 000000000000058a [ 198.911483] x13: 0000000000000003 x12: ffffffffffffffff [ 198.916781] x11: 0000000000000040 x10: ffffff7fff7fff7f [ 198.922078] x9 : a6c8de5e8022adff x8 : 0000000000000000 [ 198.927376] x7 : ffffffffffffffff x6 : ffff802fb2b59eb8 [ 198.932673] x5 : ffff802fb2b59eb8 x4 : 0000000000000400 [ 198.937971] x3 : 0000000000000000 x2 : 0000000000000000 [ 198.943268] x1 : ffff000023903708 x0 : ffff0000092ec808 [ 198.948566] Call trace: [ 198.951005] hns_roce_create_cq+0x2c/0x810 [hns_roce_hw_v1] [ 198.956566] hns_roce_v1_rsv_lp_qp+0xa8/0x4f8 [hns_roce_hw_v1] [ 198.962388] hns_roce_v1_init+0x584/0x8b8 [hns_roce_hw_v1] [ 198.967863] hns_roce_init+0x2b4/0xb08 [hns_roce_hw_v1] [ 198.973077] hns_roce_probe+0x328/0x478 [hns_roce_hw_v1] [ 198.978382] platform_drv_probe+0x58/0xa8 [ 198.982378] really_probe+0xdc/0x448 [ 198.985940] driver_probe_device+0x12c/0x148 [ 198.990196] device_driver_attach+0x74/0x98 [ 198.994366] __driver_attach+0x6c/0x168 [ 198.998188] bus_for_each_dev+0x84/0xd8 [ 199.002010] driver_attach+0x30/0x40 [ 199.005572] bus_add_driver+0x170/0x258 [ 199.009394] driver_register+0x64/0x118 [ 199.013217] __platform_driver_register+0x54/0x60 [ 199.017911] hns_roce_driver_init+0x24/0x1000 [hns_roce_hw_v1] [ 199.023731] do_one_initcall+0x54/0x240 [ 199.027554] do_init_module+0x60/0x1f0 [ 199.031289] load_module+0x1614/0x1718 [ 199.035024] __se_sys_finit_module+0xf8/0x110 [ 199.039367] __arm64_sys_finit_module+0x24/0x30 [ 199.043885] el0_svc_common.constprop.0+0xa0/0x1f8 [ 199.048662] el0_svc_handler+0x34/0x90 [ 199.052397] el0_svc+0x10/0x14 [ 199.055442] Code: aa0203f4 aa1e03e0 d503201f b0041c15 (f940037c) [ 199.061522] ---[ end trace 6041bb51aa4731d0 ]--- -- You are receiving this mail because: You are the assignee for the bug.

1 year, 5 months

1
3
0 0

[kernel-bugs] [Bug 1175893] New: question: load insanely high

by bugzilla_noreply＠suse.com

https://bugzilla.suse.com/show_bug.cgi?id=1175893 Bug ID: 1175893 Summary: question: load insanely high Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ro(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- obs-arm-1:~ # uname -a Linux obs-arm-1 5.8.2-1-default #1 SMP Wed Aug 19 09:43:15 UTC 2020 (71b519a) aarch64 aarch64 aarch64 GNU/Linux obs-arm-1:~ # cat /proc/loadavg 848.03 848.11 847.01 8/660 35750 obs-arm-1:~ # ps awux | wc -l 526 obs-arm-1:~ # pstree -apl | wc -l 252 so I have 526 processes and a load of about 850 ... what am I missing here ? top - 13:00:18 up 1 day, 17:02, 1 user, load average: 845.34, 847.11, 846.76 Tasks: 524 total, 1 running, 523 sleeping, 0 stopped, 0 zombie %Cpu(s): 12.8 us, 0.3 sy, 0.0 ni, 86.9 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 257195.5+total, 13658.55+free, 30579.12+used, 212957.8+buff/cache MiB Swap: 1000.066 total, 956.066 free, 44.000 used. 223341.5+avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 18257 qemu 20 0 9553800 4.102g 22944 S 113.2 1.633 1317:44 qemu-system-aar 21778 qemu 20 0 9689056 4.106g 22956 S 107.2 1.635 1328:27 qemu-system-aar 9249 qemu 20 0 9566116 4.106g 23208 S 102.0 1.635 1318:27 qemu-system-aar 23827 qemu 20 0 9424236 4.059g 23048 S 102.0 1.616 23:30.35 qemu-system-aar 18143 qemu 20 0 9560948 4.104g 22880 S 100.7 1.634 1316:43 qemu-system-aar 22072 qemu 20 0 9465680 4.098g 23052 S 100.7 1.631 1329:10 qemu-system-aar 36915 root 20 0 9428 3852 2900 R 1.316 0.001 0:00.16 top 41766 qemu 20 0 9475952 4.099g 22728 S 0.658 1.632 41:10.28 qemu-system-aar 6601 root 20 0 31536 23576 7452 S 0.329 0.009 0:20.33 bs_worker 1 root 20 0 172424 13108 9568 S 0.000 0.005 3:31.34 systemd 2 root 20 0 0 0 0 S 0.000 0.000 0:00.99 kthreadd 3 root 0 -20 0 0 0 I 0.000 0.000 0:00.00 rcu_gp 4 root 0 -20 0 0 0 I 0.000 0.000 0:00.00 rcu_par_gp [... skipping the rest of zeroes ...] 8 VMs with about 24 qemu threads each, so I would not be surprised about a load of ~200 but why are we seeing > 800 now ? -- You are receiving this mail because: You are the assignee for the bug.

1 year, 5 months

1
24
0 0

2022

2021

2020

openSUSE Kernel Bugs August 2020