September 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1136677] New: Add support for compressed firmware files
by bugzilla_noreply＠novell.com 03 Sep '19

03 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1136677 Bug ID: 1136677 Summary: Add support for compressed firmware files Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: tiwai(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- With the recent patchset to add the support for loading compressed firmware files, we can reduce the package size significantly. Along with kernel patches, we'd need a few more things: - The kernel configuration adjustment - kernel-firmware package to change to the compressed files - dracut to deal with the compressed files - rpm-config-SUSE to deal with the compressed files for provides -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1145529] IPv6 present, although yast network has IPv6 enable unchecked
by bugzilla_noreply＠novell.com 03 Sep '19

03 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1145529 http://bugzilla.suse.com/show_bug.cgi?id=1145529#c10 --- Comment #10 from Michal Filka <mfilka(a)suse.com> --- (In reply to Richard Bos from comment #7) > BTW: the logfile used is: y2log-1.gz It is a rotated logfile. Usually contains e.g. logs from installation or old logs which are not accurate anymore. what we need is at least /var/log/YaST2/y2log or (better) result of save_y2logs command as pointed in Comment#3 - it gathers also some other logs and stores a pieces of configuration state which help us to debug the issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1145529] IPv6 present, although yast network has IPv6 enable unchecked
by bugzilla_noreply＠novell.com 03 Sep '19

03 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1145529 http://bugzilla.suse.com/show_bug.cgi?id=1145529#c9 Michal Filka <mfilka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(mfilka(a)suse.com) |needinfo?(richard.bos@xs4al | |l.nl) --- Comment #9 from Michal Filka <mfilka(a)suse.com> --- (In reply to Richard Bos from comment #6) > When I execute your "sysctl -a | grep disable_ipv6" command: > > My output is: > # sysctl -a | grep disable_ipv6 > net.ipv6.conf.all.disable_ipv6 = 1 > net.ipv6.conf.default.disable_ipv6 = 1 > net.ipv6.conf.eth0.disable_ipv6 = 0 <<<<<< this should be a problem. It overwrites global setup (.all.disable_ipv6) by per interface setup (eth0 in this case). Question is where it comes from because yast do not touch this per interface variables. Could you try a "hotfix": /usr/sbin/sysctl -w net.ipv6.conf.eth0.disable_ipv6=1 and check whether it survives reboot to see if it is configured by some other part of your system? > net.ipv6.conf.lo.disable_ipv6 = 1 > > > I checked my settings again and "enable ipv6" is unchecked. > (and IPv6 is thus present) > > In the log I find: > > 2019-08-14 06:23:35 <3> <system> (6198) [ag_udev_persistent] OPEN_FAILED > opening /etc/udev/rules.d/79-yast2-drivers.rules failed: No such file or > directory > > 2019-08-14 06:23:35 <1> <system>(6159) [Ruby] modules/LanItems.rb:1134 > Ops.get called on nil. > 2019-08-14 06:23:35 <1> <system>(6159) [Ruby] modules/LanItems.rb:1133 Index > 1 is out of array size > 2019-08-14 06:23:35 <1> <system>(6159) [Ruby] modules/LanItems.rb:1131 Index > 1 is out of array size > > The code does not seems to be happy... Usually not a problem. Just info - a bit useless bcs it can be caused by valid check like "if index is not in limit go away" > > > It continues with: > 2019-08-14 06:23:35 <1> <system>(6159) [Ruby] modules/Lan.rb:227 readIPv6: > IPv6 is disabled > > 2019-08-14 06:23:35 <3> <system>(6159) [Interpreter] modules/Routing.rb:273 > File not found /etc/sysconfig/network/ifroute-eth0 > 2019-08-14 06:23:35 <3> s<system>(6159) [Interpreter] modules/Routing.rb:273 > File not found /etc/sysconfig/network/ifroute-lo > > (replace my hostname with <system>) > > Looks like an issue.... > # ls -l /etc/sysconfig/network/ifroute-* > > ls: cannot access '/etc/sysconfig/network/ifroute-*': No such file or > directory > # ls -l /etc/sysconfig/network/if* > -rw------- 1 root root 195 Jul 30 12:17 /etc/sysconfig/network/ifcfg-eth0 > -rw------- 1 root root 147 Apr 11 05:42 /etc/sysconfig/network/ifcfg-lo > -rw-r--r-- 1 root root 21738 Feb 24 2019 > /etc/sysconfig/network/ifcfg.template > > > Is this the issue? No. It just means that you don't use per interface route files. Again just info. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1148500] New: lvm2 2.02.180-327: vgs hangs with "device XXX not intialized in udev data base"
by bugzilla_noreply＠novell.com 03 Sep '19

03 Sep '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1148500 Bug ID: 1148500 Summary: lvm2 2.02.180-327: vgs hangs with "device XXX not intialized in udev data base" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: martin.wilck(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 815982 --> http://bugzilla.opensuse.org/attachment.cgi?id=815982&action=edit log of "vgs -vvvv" OpenQA problem https://openqa.opensuse.org/tests/1018187, installation with openSUSE-Staging:G-Tumbleweed-DVD-x86_64-Build277.1-Media.iso, installing on encrypted LVM. Blocking LVM2 release (https://build.opensuse.org/request/show/725506) ps aux shows system hanging in "vgs", called by dracut: > root 18034 0.0 0.3 4100 3228 tty1 S+ 03:06 0:00 \_ /bin/bash --norc /sbin/mkinitrd > root 18047 0.0 0.4 5520 4644 tty1 S+ 03:06 0:00 \_ /bin/bash -p /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force /boot/initrd-5.2.9-5-default 5.2.9-5-default > root 19895 0.0 0.3 5520 3036 tty1 S+ 03:23 0:00 \_ /bin/bash -p /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force /boot/initrd-5.2.9-5-default 5.2.9-5-default > root 19896 0.1 0.7 10732 7580 tty1 S+ 03:23 0:00 \_ lvm vgs --noheadings -o pv_name system I reproduced this locally. vgs emits hundreds of messages like this: > #device/dev-type.c:1042 Device /dev/loop0 not initialized in udev database (89/100, 8800000 microseconds). strace shows that vgs is trying to access the udev db under /run/udev/data directly by opening files under that directory. This fails because /run is not mounted in the chroot (system being installed). As soon as a bind-mount is created for /run into the chroot, vgs and then the installation proceeds and completes: mount --bind /run /mnt/run I've assigned this to the "installer" component because it can be fixed in a simple way by bind-mounting /run. I don't know how this problem is related to the lvm2 update from sr#725506. -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1148374] LTO: libqt5-qttools build fails on ppc64
by bugzilla_noreply＠novell.com 03 Sep '19

03 Sep '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1148374 http://bugzilla.opensuse.org/show_bug.cgi?id=1148374#c5 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(dimstar@opensuse. | |org) --- Comment #5 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Michel Normand from comment #4) > (In reply to Fabian Vogt from comment #3) > > (In reply to Michel Normand from comment #2) > > > (In reply to Fabian Vogt from comment #1) > > > > Could probably be worked around by disabling LTO for ppc64 in general. > > > > > > how to do that ? > > > > By overriding the optflags in openSUSE:Factory:PowerPC for %ifatch ppc64 > > with some which don't use the %{_lto_cflags} macro. > > Fabian could you do that ? (I do not have maintenance access) Me neither. Dominique? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1147412] bcache-register fails during boot, leaving backing store busy
by bugzilla_noreply＠novell.com 03 Sep '19

03 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1147412 http://bugzilla.suse.com/show_bug.cgi?id=1147412#c4 --- Comment #4 from Coly Li <colyli(a)suse.com> --- (In reply to Coly Li from comment #1) > Can you try the vanilla kernel after Linux v5.3-rc3 ? > There are quite a lot fixes merged into Linux v5.3, we can have a try > whether it is caused by known issue. Stange, I remember I saw a commnet that you were not able to find a 5.3-rc3 to test, but I don't see this commnet here.. The kernel BUG location is line 433, 431 static inline bool bch_cut_back(const struct bkey *where, struct bkey *k) 432 { 433 BUG_ON(bkey_cmp(where, &START_KEY(k)) < 0); 434 return __bch_cut_back(where, k); 435 } Which was an out-of-order bkey items triggered. Recently we have a report for such problem but the fix commit 31b90956b124 ("bcache: fix stack corruption by PRECEDING_KEY()") is merged into Linux v5.2 already. This is the first report I see for bcache with Optane. Myabe this is another new bug hides for long time. Do you use the 16GB Optane as cache device, and the 128GB SSD as backing device ? I am thinking of how to reproduce a similar configuration and see what happens. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1148500] lvm2 2.02.180-327: vgs hangs with "device XXX not intialized in udev data base"
by bugzilla_noreply＠novell.com 03 Sep '19

03 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1148500 http://bugzilla.suse.com/show_bug.cgi?id=1148500#c12 Jiri Srain <jsrain(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.wilck(a)suse.com Flags| |needinfo?(martin.wilck@suse | |.com) --- Comment #12 from Jiri Srain <jsrain(a)suse.com> --- Well, I guess that /run was created as a regular directory - it is part of the filesystem package. YaST does following mounts after partitioning disk: mount_in_target("/dev", "devtmpfs", "-t devtmpfs") mount_in_target("/proc", "proc", "-t proc") mount_in_target("/sys", "sysfs", "-t sysfs") mount_in_target(EFIVARS_PATH, "efivarfs", "-t efivarfs") if File.exist?(EFIVARS_PATH) Can you see anything else missing? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1148374] LTO: libqt5-qttools build fails on ppc64
by bugzilla_noreply＠novell.com 03 Sep '19

03 Sep '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1148374 http://bugzilla.opensuse.org/show_bug.cgi?id=1148374#c4 Michel Normand <normand(a)linux.vnet.ibm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dimstar(a)opensuse.org --- Comment #4 from Michel Normand <normand(a)linux.vnet.ibm.com> --- (In reply to Fabian Vogt from comment #3) > (In reply to Michel Normand from comment #2) > > (In reply to Fabian Vogt from comment #1) > > > Could probably be worked around by disabling LTO for ppc64 in general. > > > > how to do that ? > > By overriding the optflags in openSUSE:Factory:PowerPC for %ifatch ppc64 > with some which don't use the %{_lto_cflags} macro. Fabian could you do that ? (I do not have maintenance access) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1147412] bcache-register fails during boot, leaving backing store busy
by bugzilla_noreply＠novell.com 03 Sep '19

03 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1147412 http://bugzilla.suse.com/show_bug.cgi?id=1147412#c3 --- Comment #3 from Coly Li <colyli(a)suse.com> --- (In reply to Coly Li from comment #2) > (In reply to Coly Li from comment #1) > > Can you try the vanilla kernel after Linux v5.3-rc3 ? > > There are quite a lot fixes merged into Linux v5.3, we can have a try > > whether it is caused by known issue. > > The fix is merged in SLE15 and SLE15-SP1 kernel, it will go into Tumbleweed > very soon. I type into a mismatch bugzilla report, please ignore the above comment. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1147412] bcache-register fails during boot, leaving backing store busy
by bugzilla_noreply＠novell.com 03 Sep '19

03 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1147412 http://bugzilla.suse.com/show_bug.cgi?id=1147412#c2 --- Comment #2 from Coly Li <colyli(a)suse.com> --- (In reply to Coly Li from comment #1) > Can you try the vanilla kernel after Linux v5.3-rc3 ? > There are quite a lot fixes merged into Linux v5.3, we can have a try > whether it is caused by known issue. The fix is merged in SLE15 and SLE15-SP1 kernel, it will go into Tumbleweed very soon. -- You are receiving this mail because: You are on the CC list for the bug.

1 0