November 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 09 Nov '21

09 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c9 --- Comment #9 from Martin Wilck <martin.wilck(a)suse.com> --- Suggested by Takashi in chat: for the Live CD image, it might be worthwhile to try including the *uncompressed* modules, because they can be compressed much better during image creation. That would have the additional benefit that the result would be independent of whether or not the modules were shiped xz or zstd-compressed. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192476] CONFIG_FORTIFY_SOURCE isn't enabled on TW kernels
by bugzilla_noreply＠suse.com 09 Nov '21

09 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192476 https://bugzilla.suse.com/show_bug.cgi?id=1192476#c2 --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- Submitted to my master/for-next branch. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 09 Nov '21

09 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c8 --- Comment #8 from Martin Wilck <martin.wilck(a)suse.com> --- (In reply to Michal Suchanek from comment #7) > Isn't rescue CD recompressed anyway? > > Does recomressing the zstd compressed data with xz (squashfs, initrd) > recover the space? Probably not. Compressing already-compressed payloads is inefficient. See https://mwilck.github.io/labsconf2021/#/1/5 for example. The _rpm_ size is smallest if the the payload (the modules) are uncompressed. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 09 Nov '21

09 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c7 --- Comment #7 from Michal Suchanek <msuchanek(a)suse.com> --- Isn't rescue CD recompressed anyway? Does recomressing the zstd compressed data with xz (squashfs, initrd) recover the space? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192375] Bose Revolve+ SoundLink USB speaker bad dB
by bugzilla_noreply＠suse.com 09 Nov '21

09 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192375 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |tiwai(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 09 Nov '21

09 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c6 --- Comment #6 from Martin Wilck <martin.wilck(a)suse.com> --- I made a note in SUSE Jira (PM-2971) about this to inform PM. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192457] ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 09 Nov '21

09 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c5 --- Comment #5 from Martin Wilck <martin.wilck(a)suse.com> --- Understood. There's obviously a trade-off which needs to be considered. I believe there are strong arguments in favor of zstd, mainly speed. But if it's prohibitive in other areas, we must reconsider the decision. One obvious possiblility would be to split off kernel-default-extra like we do in Leap, reducing the install size of the kernel base package. But that's yet another trade-off, and doing it would cost substantial effort. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189791] btrfs filesystem corruptions with HyperPAV
by bugzilla_noreply＠suse.com 08 Nov '21

08 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1189791 https://bugzilla.suse.com/show_bug.cgi?id=1189791#c13 --- Comment #13 from Berthold Gunreben <azouhr(a)opensuse.org> --- (In reply to LTC BugProxy from comment #12) > ------- Comment From stefan.haberland(a)de.ibm.com 2021-11-08 10:27 EDT------- > Hi, currently there are only btrfs error messages shared. > Are there any DASD related error messages? I did not see any. > What I see in the workflow: > > > 2.3 Use yast to activate and format disk then create raw partition > > Could you please explain a little more in detail what this exactly looks > like and what exactly is meant by "raw partition"? > > Is the disk that is added to btrfs a partition created by fsdasd or the base > blockdevice (e.g. /dev/dasdx1 vs /dev/dasdx). It is /dev/dasdx1 (as you can see from the btrfs device stats as well) The lowlevel dasdfmt has been done with yast, since I was unsure about how to accomplish this correctly with keeping the disk devices thin provisioned. After this, the single partition was created in the partitioner dialog. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188428] New: udev: failed to get device info: could not read 'authorized': No such file or directory
by bugzilla_noreply＠suse.com 08 Nov '21

08 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1188428 Bug ID: 1188428 Summary: udev: failed to get device info: could not read 'authorized': No such file or directory Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Starting with kernel 5.13.0-1 (Jul 09) on boot I always get an error message (see subject) from boltd regarding device cd010000-0060-XPS 9370. All messages from boltd: boltd[1189]: bolt 0.9.1 starting up. boltd[1189]: manager: initializing store boltd[1189]: store: located at: /var/lib/boltd boltd[1189]: config: loading user config boltd[1189]: bouncer: initializing polkit boltd[1189]: watchdog: enabled [pulse: 90s] boltd[1189]: udev: initializing udev boltd[1189]: store: loading domains boltd[1189]: [cd010000-0060-domain? ] store: loading domain boltd[1189]: journal: opened for 'cd010000-0060'; size: 0 bytes boltd[1189]: [cd010000-0060-domain? ] domain: registered (bootacl: 16/16) boltd[1189]: store: loading devices boltd[1189]: [00cd30c8-3205 ] store: loading device boltd[1189]: [cd010000-0060 ] store: loading device boltd[1189]: global 'generation' set to '3' boltd[1189]: [da010000-0070 ] store: loading device boltd[1189]: power: state located at: /run/boltd/power boltd[1189]: power: force power support: yes boltd[1189]: udev: found 1 domain boltd[1189]: udev: enumerating devices boltd[1189]: probing: adding /sys/devices/pci0000:00/0000:00:1c.4/0000:03:00.0 to roots boltd[1189]: [cd010000-0060-domain0 ] bootacl: synchronizing journal boltd[1189]: security level set to 'user' boltd[1189]: [cd010000-0060-domain0 ] connected: as domain0 [user] (/sys/devices/pci0000:00/0000:00:1c.4/0000:03:00.0/0000:04:00.0/0000:05:00.0/domain0) boltd[1189]: [cd010000-0060-XPS 9370 ] udev: failed to get device info: could not read 'authorized': No such file or directory boltd[1189]: [cd010000-0060-XPS 9370 ] parent is (null)... boltd[1189]: [cd010000-0060-XPS 9370 ] store: updating device boltd[1189]: [cd010000-0060-XPS 9370 ] connected: unknown (/sys/devices/pci0000:00/0000:00:1c.4/0000:03:00.0/0000:04:00.0/0000:05:00.0/domain0/0-0) boltd[1189]: [00cd30c8-3205-TS3 Plus ] parent is cd010000-0060... boltd[1189]: [00cd30c8-3205-TS3 Plus ] connected: authorized (/sys/devices/pci0000:00/0000:00:1c.4/0000:03:00.0/0000:04:00.0/0000:05:00.0/domain0/0-0/0-3) boltd[1189]: [cd010000-0060-domain0 ] dbus: exported domain at /org/freedesktop/bolt/domains/cd010000_0060_6d18_a364_e809ccc32820 boltd[1189]: [00cd30c8-3205-TS3 Plus ] dbus: exported device at /org/freedesktop/bolt/devices/00cd30c8_3205... boltd[1189]: [cd010000-0060-XPS 9370 ] dbus: exported device at /org/freedesktop/bolt/devices/cd010000_0060... boltd[1189]: [da010000-0070-XPS 13 9370 ] dbus: exported device at /org/freedesktop/bolt/devices/da010000_0070... boltd[1189]: probing: started [1000] boltd[1189]: [00cd30c8-3205-TS3 Plus ] udev: device changed: authorized -> authorized boltd[1189]: probing: timeout, done: [2974874] (2000000) System info: Operating System: openSUSE Tumbleweed 20210715 KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 Kernel Version: 5.13.1-1-default (64-bit) Graphics Platform: X11 Processors: 8 �� Intel�� Core�� i7-8550U CPU @ 1.80GHz Memory: 15,0 GiB of RAM Graphics Processor: Mesa DRI Intel�� UHD Graphics 620 This is a DELL XPS 9370 notebook. -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 1189791] btrfs filesystem corruptions with HyperPAV
by bugzilla_noreply＠suse.com 08 Nov '21

08 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1189791 https://bugzilla.suse.com/show_bug.cgi?id=1189791#c12 --- Comment #12 from LTC BugProxy <bugproxy(a)us.ibm.com> --- ------- Comment From stefan.haberland(a)de.ibm.com 2021-11-08 10:27 EDT------- Hi, currently there are only btrfs error messages shared. Are there any DASD related error messages? What I see in the workflow: > 2.3 Use yast to activate and format disk then create raw partition Could you please explain a little more in detail what this exactly looks like and what exactly is meant by "raw partition"? Is the disk that is added to btrfs a partition created by fsdasd or the base blockdevice (e.g. /dev/dasdx1 vs /dev/dasdx). -- You are receiving this mail because: You are the assignee for the bug.

1 0