June 2020 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[kernel-bugs] [Bug 1172670] New: kdump: fails to create dump as dump-capture kernel boots into systemd emergency mode
by bugzilla_noreply＠suse.com 08 Jun '20

08 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1172670 Bug ID: 1172670 Summary: kdump: fails to create dump as dump-capture kernel boots into systemd emergency mode 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: shung-hsi.yu(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 838585 --> http://bugzilla.opensuse.org/attachment.cgi?id=838585&action=edit journalctl output (colored) The system is configured to capture core dump on crash with `yast2 kdump`. This is confirmed by looking at /proc/cmdline (contains ' crashkernel=256M,high crashkernel=72M,low'), output of `dmesg`, and the status of kdump.service. Triggering a crash dump manually with `echo c >/proc/sysrq-trigger` shows the stacktrace, but fails to correctly boot up the dump-capturing kernel. Below is an excerpt of the output of `journalctl` before the emergency shell was started. Jun 08 14:13:35 localhost systemd[1]: Starting Switch Root... Jun 08 14:13:35 localhost systemctl[377]: Failed to switch root: Specified switch root path '/sysroot' does not seem to be an OS tree. os-release file is missing. Jun 08 14:13:35 localhost systemd[1]: initrd-switch-root.service: Main process exited, code=exited, status=1/FAILURE Jun 08 14:13:35 localhost systemd[1]: initrd-switch-root.service: Failed with result 'exit-code'. Jun 08 14:13:35 localhost systemd[1]: Failed to start Switch Root. Jun 08 14:13:35 localhost systemd[1]: initrd-switch-root.service: Triggering OnFailure= d ependencies. Jun 08 14:13:35 localhost systemd[1]: Starting Setup Virtual Console... Jun 08 14:13:35 localhost systemd[1]: Finished Setup Virtual Console. Jun 08 14:13:35 localhost systemd[1]: Started Emergency Shell. Jun 08 14:13:35 localhost systemd[1]: Reached target Emergency Mode. This issue looks a bit similar to https://bugzilla.redhat.com/show_bug.cgi?id=1812393 but I'm not too sure. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[kernel-bugs] [Bug 1172541] Mysterious crashes with kernel 5.6.14
by bugzilla_noreply＠suse.com 08 Jun '20

08 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1172541 http://bugzilla.suse.com/show_bug.cgi?id=1172541#c3 --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- OK, then let's wait until 5.7 kernel gets merged to TW snapshot. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1171677] USB-C external hub randomly stops working
by bugzilla_noreply＠suse.com 08 Jun '20

08 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1171677 http://bugzilla.suse.com/show_bug.cgi?id=1171677#c7 Lubos Kocman <lubos.kocman(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium CC| |lubos.kocman(a)suse.com Component|GNOME |Kernel Assignee|gnome-bugs(a)suse.de |kernel-bugs(a)opensuse.org --- Comment #7 from Lubos Kocman <lubos.kocman(a)suse.com> --- Switching from GNOME desktop to kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] Your Bugzilla bug list needs attention.
by bugzilla_noreply＠suse.com 07 Jun '20

07 Jun '20

[This e-mail has been automatically generated.] You have one or more bugs assigned to you in the Bugzilla bug tracking system (http://bugzilla.suse.com/) that require attention. All of these bugs are in either the CONFIRMED, NEW, or REOPENED state, and have not been touched in 7 days or more. You need to take a look at them, and decide on an initial action. Generally, this means one of three things: (1) You decide this bug is really quick to deal with (like, it's INVALID), and so you get rid of it immediately. (2) You decide the bug doesn't belong to you, and you reassign it to someone else. (Hint: if you don't know who to reassign it to, make sure that the Component field seems reasonable, and then use the "Reset Assignee to default" option.) (3) You decide the bug belongs to you, but you can't solve it this moment. Ignore this email until you are actively working on this bug, when you should set the status to IN_PROGRESS. To get a list of all affected bugs, you can use this URL (bookmark it if you like!): http://bugzilla.suse.com/buglist.cgi?bug_status=CONFIRMED&bug_status=NEW&bu… Or, you can use the general query page, at http://bugzilla.suse.com/query.cgi Appended below are the individual URLs to get to all of your affected bugs that haven't been touched for 7 days or more. You will get this message once a week until you've dealt with these bugs! test bug for assignee change -> http://bugzilla.suse.com/show_bug.cgi?id=1172181 -- To unsubscribe, e-mail: kernel-bugs+unsubscribe(a)opensuse.org To contact the owner, e-mail: kernel-bugs+owner(a)opensuse.org

1 0

[kernel-bugs] [Bug 1172541] Mysterious crashes with kernel 5.6.14
by bugzilla_noreply＠suse.com 05 Jun '20

05 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1172541 http://bugzilla.suse.com/show_bug.cgi?id=1172541#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Unfortunately it's very hard to guess what's going on there only from that. We already moved to 5.7 kernel now, and the update is on its way to TW. Could you try 5.7 kernel from OBS Kernel:stable repo and see whether the issue persists? If a crash happens, it'd be great if you can get a trace of Oops or whatever. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172322] usb message shown on console even with "quiet splash=silent"
by bugzilla_noreply＠suse.com 04 Jun '20

04 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1172322 http://bugzilla.suse.com/show_bug.cgi?id=1172322#c3 Frank Krüger <fkrueger(a)mailbox.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fkrueger(a)mailbox.org --- Comment #3 from Frank Krüger <fkrueger(a)mailbox.org> --- Using current TW and Kernel:stable, my webcam does not work from time to time (using uvcvideo driver), and in this case I am also seeing the above-mentioned messages. Does your webcam work? What is the output of 'lsusb -t' and 'lsusb -v | grep -i port1'? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172292] Support for 64-bot processors on motherboards with 32-bit UEFI
by bugzilla_noreply＠suse.com 04 Jun '20

04 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1172292 http://bugzilla.suse.com/show_bug.cgi?id=1172292#c2 --- Comment #2 from Gary Ching-Pang Lin <glin(a)suse.com> --- It's so called UEFI Mixed mode, and it would need support both from bootloader and kernel. CONFIG_EFI_MIXED is already enabled in kernel, so the question would be how to detect mixed mode and install the proper UEFI bootloader. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172322] usb message shown on console even with "quiet splash=silent"
by bugzilla_noreply＠suse.com 04 Jun '20

04 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1172322 http://bugzilla.suse.com/show_bug.cgi?id=1172322#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mrueckert(a)suse.com Flags| |needinfo?(mrueckert(a)suse.co | |m) --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- The changes between v5.6.12..v5.6.14 wrt drivers/usb are mostly for gadget and other device-specific fixes, so it's not obvious what may break. In anyway, please give the detailed hardware information as well as hwinfo output, and the whole dmesg outputs on both working and non-working cases. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1166342] Harmonize kernel modules in JeOS leap 15.1 with TW and leap 15.2
by bugzilla_noreply＠suse.com 03 Jun '20

03 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1166342 Alynx Zhou <alynx.zhou(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alynx.zhou(a)suse.com Component|Other |Kernel Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172366] btrfs balance in endless loop and couldn't be canceled
by bugzilla_noreply＠suse.com 02 Jun '20

02 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1172366 Goldwyn Rodrigues <rgoldwyn(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |wqu(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172378] New: oopsing in dm_mirror during pvmove
by bugzilla_noreply＠suse.com 02 Jun '20

02 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1172378 Bug ID: 1172378 Summary: oopsing in dm_mirror during pvmove 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: ro(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I've seen a few of these now trying to migrate pontifex (download.opensuse.org) away from an old storage. It is probably triggered by a read error on the underlying device. kernel: 4.12.14-lp151.28.48-default, x86_64 most recent: -- 100:pontifex2 -- time-stamp -- Jun/02/20 2:49:09 -- [68935.390120] invalid opcode: 0000 [#1] SMP NOPTI [68935.404194] CPU: 2 PID: 26557 Comm: kworker/2:0 Not tainted 4.12.14-lp151.28.48-default #1 openSUSE Leap 15.1 [68935.406277] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.11.0-0-g63451fc-prebuilt.qemu-project.org 04/01/2014 [68935.408703] Workqueue: kmirrord do_mirror [dm_mirror] [68935.409680] task: ffff8801ea3d0080 task.stack: ffffc900148c4000 [68935.410863] RIP: 0010:clone_endio+0x5e/0x150 [dm_mod] [68935.411948] RSP: 0018:ffffc900148c7d48 EFLAGS: 00010296 [68935.412957] RAX: 0000000000000040 RBX: ffff88005a28c0b0 RCX: 0000000000000006 [68935.414326] RDX: 0000000000000007 RSI: 0000000000000096 RDI: ffff88183fc97a60 [68935.415690] RBP: ffffffffa02ea280 R08: 0000000000000241 R09: 0000000000000001 [68935.417088] R10: ffffc90014c5fc20 R11: 0000000000000001 R12: ffff88005a28c040 [68935.418463] R13: ffffffffa02ea410 R14: ffff880333ea2128 R15: 0000000000000000 [68935.419968] FS: 0000000000000000(0000) GS:ffff88183fc80000(0000) knlGS:0000000000000000 [68935.421504] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [68935.422608] CR2: 000055e713b82e58 CR3: 000000028f0e0000 CR4: 00000000000406e0 [68935.424047] Call Trace: [68935.424541] do_reads+0x17a/0x1c0 [dm_mirror] [68935.425385] ? dm_rh_update_states+0x2f9/0x310 [dm_region_hash] [68935.426527] ? down_trylock+0x25/0x30 [68935.427262] ? dm_rh_recovery_prepare+0x9d/0x120 [dm_region_hash] [68935.428483] do_mirror+0x102/0x66e [dm_mirror] [68935.429360] ? __switch_to_asm+0x34/0x70 [68935.430134] ? __switch_to_asm+0x40/0x70 [68935.430905] ? __switch_to_asm+0x34/0x70 [68935.431774] ? __switch_to_asm+0x34/0x70 [68935.432608] ? finish_task_switch+0x76/0x230 [68935.433509] process_one_work+0x1da/0x400 [68935.434320] worker_thread+0x2b/0x3f0 [68935.435091] ? process_one_work+0x400/0x400 [68935.435921] kthread+0x10d/0x130 [68935.436562] ? kthread_create_worker_on_cpu+0x50/0x50 [68935.437623] ret_from_fork+0x22/0x40 [68935.438372] Code: 7b e0 48 8d 54 24 07 48 89 de e8 2e 41 5a e1 83 f8 01 74 39 83 f8 02 74 14 85 c0 74 15 89 c6 48 c7 c7 30 df 46 a0 e8 f2 16 d6 e0 <0f> 0b c6 44 24 07 0b 80 7b f8 00 75 08 48 89 df e8 fd 9e f7 e0 [68935.442895] Modules linked in: ip6table_raw xt_comment iptable_raw xt_CT nfnetlink_cthelper nfnetlink af_packet iscsi_ibft iscsi_boot_sysfs ip6 t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT xt_pkttype xt_tcpudp iptable_filter ip6table_mangle nf_conntrack_netbios_ns nf_conntrack_broa dcast nf_conntrack_ipv4 nf_defrag_ipv4 ip_tables xt_conntrack nf_conntrack ip6table_filter ip6_tables x_tables edac_mce_amd kvm_amd ccp xfs kvm ir qbypass libcrc32c dm_mirror crc32_pclmul cirrus dm_region_hash crc32c_intel dm_log ghash_clmulni_intel ttm pcbc drm_kms_helper dm_mod aesni_intel drm virtio_net aes_x86_64 crypto_simd glue_helper net_failover drm_panel_orientation_quirks cryptd failover virtio_balloon fb_sys_fops syscopyarea sysfillrect sysimgblt i2c_piix4 pcspkr qemu_fw_cfg button ata_generic ata_piix [68935.459497] ahci uhci_hcd libahci ehci_hcd serio_raw usbcore virtio_blk floppy sg [68935.461356] ---[ end trace 2f37a9f791364259 ]--- [68935.462345] RIP: 0010:clone_endio+0x5e/0x150 [dm_mod] [68935.462347] RSP: 0018:ffffc900148c7d48 EFLAGS: 00010296 [68935.462349] RAX: 0000000000000040 RBX: ffff88005a28c0b0 RCX: 0000000000000006 [68935.462350] RDX: 0000000000000007 RSI: 0000000000000096 RDI: ffff88183fc97a60 [68935.462351] RBP: ffffffffa02ea280 R08: 0000000000000241 R09: 0000000000000001 [68935.462357] R10: ffffc90014c5fc20 R11: 0000000000000001 R12: ffff88005a28c040 [68935.471992] R13: ffffffffa02ea410 R14: ffff880333ea2128 R15: 0000000000000000 [68935.471995] FS: 0000000000000000(0000) GS:ffff88183fc80000(0000) knlGS:0000000000000000 [68935.471996] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [68935.471997] CR2: 000055e713b82e58 CR3: 000000028f0e0000 CR4: 00000000000406e0 -- 100:pontifex2 -- time-stamp -- Jun/02/20 2:51:02 -- one before: -- 100:pontifex2 -- time-stamp -- Jun/01/20 6:05:10 -- [60441.972610] invalid opcode: 0000 [#1] SMP NOPTI [60441.973885] CPU: 5 PID: 30125 Comm: kworker/5:1 Not tainted 4.12.14-lp151.28.48-default #1 openSUSE Leap 15.1 [60441.975765] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.11.0-0-g63451fc-prebuilt.qemu-project.org 04/01/2014 [60441.977969] Workqueue: kmirrord do_mirror [dm_mirror] [60441.979186] task: ffff88029f9d8180 task.stack: ffffc9000e5d4000 [60441.981195] RIP: 0010:clone_endio+0x5e/0x150 [dm_mod] [60441.982803] RSP: 0018:ffffc9000e5d7d48 EFLAGS: 00010296 [60441.984530] RAX: 0000000000000040 RBX: ffff88012c518870 RCX: 0000000000000006 [60441.986931] RDX: 0000000000000007 RSI: 0000000000000096 RDI: ffff88183fd57a60 [60441.988503] RBP: ffffffffa0153280 R08: 000000000000024a R09: 0000000000000001 [60441.989878] R10: ffffc9000752f7f8 R11: 0000000000000001 R12: ffff88012c518800 [60441.991239] R13: ffffffffa0153410 R14: ffff8817db49f928 R15: 0000000000000000 [60441.992661] FS: 0000000000000000(0000) GS:ffff88183fd40000(0000) knlGS:0000000000000000 [60441.995364] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [60441.996482] CR2: 00007f20a09d3000 CR3: 0000000308c96000 CR4: 00000000000406e0 [60441.997927] Call Trace: [60441.998417] do_reads+0x17a/0x1c0 [dm_mirror] [60441.999249] ? dm_rh_update_states+0x2f9/0x310 [dm_region_hash] [60442.000352] ? down_trylock+0x25/0x30 [60442.001033] ? dm_rh_recovery_prepare+0x9d/0x120 [dm_region_hash] [60442.002188] do_mirror+0x102/0x66e [dm_mirror] [60442.003036] ? __switch_to_asm+0x34/0x70 [60442.003724] ? __switch_to_asm+0x40/0x70 [60442.004385] ? __switch_to_asm+0x34/0x70 [60442.005301] ? __switch_to_asm+0x34/0x70 [60442.006079] ? finish_task_switch+0x76/0x230 [60442.007175] process_one_work+0x1da/0x400 [60442.007959] worker_thread+0x2b/0x3f0 [60442.008664] ? process_one_work+0x400/0x400 [60442.009497] kthread+0x10d/0x130 [60442.010111] ? kthread_create_worker_on_cpu+0x50/0x50 [60442.011171] ret_from_fork+0x22/0x40 [60442.011867] Code: 7b e0 48 8d 54 24 07 48 89 de e8 2e e1 7a e1 83 f8 01 74 39 83 f8 02 74 14 85 c0 74 15 89 c6 48 c7 c7 30 3f 26 a0 e8 f2 b6 f6 e0 <0f> 0b c6 44 24 07 0b 80 7b f8 00 75 08 48 89 df e8 fd 3e 18 e1 [60442.015764] Modules linked in: ip6table_raw xt_comment iptable_raw xt_CT nfnetlink_cthelper nfnetlink af_packet iscsi_ibft iscsi_boot_sysfs ip6 t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT xt_pkttype xt_tcpudp iptable_filter ip6table_mangle nf_conntrack_netbios_ns nf_conntrack_broa dcast nf_conntrack_ipv4 nf_defrag_ipv4 ip_tables xt_conntrack nf_conntrack ip6table_filter ip6_tables x_tables edac_mce_amd kvm_amd xfs ccp dm_mir ror kvm cirrus libcrc32c dm_region_hash ttm irqbypass drm_kms_helper crc32_pclmul dm_log crc32c_intel dm_mod ghash_clmulni_intel drm pcbc drm_pane l_orientation_quirks virtio_net fb_sys_fops aesni_intel syscopyarea sysfillrect net_failover aes_x86_64 sysimgblt failover crypto_simd glue_helper virtio_balloon pcspkr cryptd i2c_piix4 qemu_fw_cfg button ata_generic ata_piix [60442.029932] ahci libahci uhci_hcd ehci_hcd serio_raw virtio_blk usbcore floppy sg [60442.031558] ---[ end trace aead3917ec7f1b83 ]--- [60442.032626] RIP: 0010:clone_endio+0x5e/0x150 [dm_mod] [60442.032627] RSP: 0018:ffffc9000e5d7d48 EFLAGS: 00010296 [60442.032628] RAX: 0000000000000040 RBX: ffff88012c518870 RCX: 0000000000000006 [60442.032629] RDX: 0000000000000007 RSI: 0000000000000096 RDI: ffff88183fd57a60 [60442.032630] RBP: ffffffffa0153280 R08: 000000000000024a R09: 0000000000000001 [60442.032631] R10: ffffc9000752f7f8 R11: 0000000000000001 R12: ffff88012c518800 [60442.032631] R13: ffffffffa0153410 R14: ffff8817db49f928 R15: 0000000000000000 [60442.032634] FS: 0000000000000000(0000) GS:ffff88183fd40000(0000) knlGS:0000000000000000 [60442.032635] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [60442.032636] CR2: 00007f20a09d3000 CR3: 0000000308c96000 CR4: 00000000000406e0 -- 100:pontifex2 -- time-stamp -- Jun/01/20 6:07:09 -- -- You are receiving this mail because: You are the assignee for the bug.

1 1

[kernel-bugs] [Bug 1172366] New: btrfs balance in endless loop and couldn't be canceled
by bugzilla_noreply＠suse.com 01 Jun '20

01 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1172366 Bug ID: 1172366 Summary: btrfs balance in endless loop and couldn't be canceled 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.koelmel(a)kit.edu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have had a endless running btrfs balance with the kernel 4.12.14-lp151.28.48-default. The balance was triggered from the btrfsmaintenance balance timer. I have no kernel stack trace, only the same following trace during 15h: "kernel: [.......] BTRFS info (device dm-0): found 2087 extents" The btrfs filesystem was in the following situation: " Total devices 1 FS bytes used 30.81GiB devid 1 size 45.00GiB used 45.00GiB path /dev/mapper/system-root2 " I've tried to free some space through deletion of old snaphots during this situation, but the btrfs balance was running without change. Also canceling of the btrfs balance had no effect. After these tries i have rebooted the system with skip_balance option in the fstab. Manually started btrfs balance in several steps (with argument -musage beginning from 10 to 80, then with argument -dusage from 10 to 80) were running without problem, but the used size (second line) was a little smaller than 45.00 GiB at the start of the balance runs. A scrub of this filesystem shows no errors. There are some other bug reports describing the same or a similar problem (e.g. https://bugzilla.opensuse.org/show_bug.cgi?id=1160947) but for me it is not clear, if this kernel, which has quite a lot btrfs related changes, should have a bugfix for this problem. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172292] Support for 64-bot processors on motherboards with 32-bit UEFI
by bugzilla_noreply＠suse.com 01 Jun '20

01 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1172292 http://bugzilla.suse.com/show_bug.cgi?id=1172292#c1 Michal Filka <mfilka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Installation |Kernel Assignee|yast2-maintainers(a)suse.de |kernel-bugs(a)opensuse.org QA Contact|jsrain(a)suse.com |qa-bugs(a)suse.de --- Comment #1 from Michal Filka <mfilka(a)suse.com> --- Nothing for yast. Kernel team might help with that (?) -- You are receiving this mail because: You are the assignee for the bug.

1 0