February 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1162471] [Build 20200131] Kernel 5.5/btrfs 'eats' disk space
by bugzilla_noreply＠novell.com 03 Feb '20

03 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1162471 http://bugzilla.suse.com/show_bug.cgi?id=1162471#c7 --- Comment #7 from David Sterba <dsterba(a)suse.com> --- Branch with fix submitted for merge to master. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1160096] After Update, WIFI don't Work
by bugzilla_noreply＠novell.com 03 Feb '20

03 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1160096 http://bugzilla.suse.com/show_bug.cgi?id=1160096#c6 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Flags|needinfo?(pam82(a)web.de) | --- Comment #6 from Takashi Iwai <tiwai(a)suse.com> --- OK, it's good to hear that the latest system works. So let's close now. Feel free to reopen if you encounter the same problem again. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1162511] Flooded with messages dev_pm_opp_set_rate: failed to find current OPP for freq on Raspberry Pi 4B
by bugzilla_noreply＠novell.com 03 Feb '20

03 Feb '20

1 0

[Bug 1162511] New: Flooded with messages dev_pm_opp_set_rate: failed to find current OPP for freq on Raspberry Pi 4B
by bugzilla_noreply＠novell.com 03 Feb '20

03 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1162511 Bug ID: 1162511 Summary: Flooded with messages dev_pm_opp_set_rate: failed to find current OPP for freq on Raspberry Pi 4B Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Factory Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: freek(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 828929 --> http://bugzilla.opensuse.org/attachment.cgi?id=828929&action=edit kernel.log Attached is a full log created by "journalctl -b > kernel.log". -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1162471] [Build 20200131] Kernel 5.5/btrfs 'eats' disk space
by bugzilla_noreply＠novell.com 03 Feb '20

03 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1162471 http://bugzilla.suse.com/show_bug.cgi?id=1162471#c6 --- Comment #6 from David Sterba <dsterba(a)suse.com> --- The patch can be safely added to tumbleweed now, it's on the way to master and then stable https://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git/commit/?h=f… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1162479] Failure to create RAID0 or LVM when installing on two disks
by bugzilla_noreply＠novell.com 03 Feb '20

03 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1162479 http://bugzilla.suse.com/show_bug.cgi?id=1162479#c4 Arvin Schnell <aschnell(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|YaST2 |Basesystem Assignee|yast2-maintainers(a)suse.de |nfbrown(a)suse.com QA Contact|jsrain(a)suse.com |qa-bugs(a)suse.de --- Comment #4 from Arvin Schnell <aschnell(a)suse.com> --- The error message is not clear to me but looks like a problem of mdadm. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1162479] Failure to create RAID0 or LVM when installing on two disks
by bugzilla_noreply＠novell.com 03 Feb '20

03 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1162479 http://bugzilla.suse.com/show_bug.cgi?id=1162479#c3 --- Comment #3 from Arvin Schnell <aschnell(a)suse.com> --- This bug deals with the RAID problem, bug #1162506 deals with the LVM problem. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1162479] Failure to create RAID0 or LVM when installing on two disks
by bugzilla_noreply＠novell.com 03 Feb '20

03 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1162479 Arvin Schnell <aschnell(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aschnell(a)suse.com See Also| |http://bugzilla.suse.com/sh | |ow_bug.cgi?id=1162506 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1162479] Failure to create RAID0 or LVM when installing on two disks
by bugzilla_noreply＠novell.com 03 Feb '20

03 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1162479 Arvin Schnell <aschnell(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1162506 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1162472] New: systemd in rescue image tries to mount / with MS_SLAVE, but it fails -- logind does not start
by bugzilla_noreply＠novell.com 03 Feb '20

03 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1162472 Bug ID: 1162472 Summary: systemd in rescue image tries to mount / with MS_SLAVE, but it fails -- logind does not start Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: systemd-maintainers(a)suse.de Reporter: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Start rescue system from Tumbleweed cd and see logind failing: > # systemctl status systemd-logind.service > ● systemd-logind.service - Login Service > Loaded: loaded (/mounts/mp_0000/usr/lib/systemd/system/systemd-logind.service; static; vendor preset: disabled) > Drop-In: /mounts/mp_0000/usr/lib/systemd/system/systemd-logind.service.d > └─nosandbox.conf > Active: failed (Result: exit-code) since Mon 2020-02-03 09:25:20 UTC; 4min 48s ago > Docs: man:systemd-logind.service(8) > man:logind.conf(5) > https://www.freedesktop.org/wiki/Software/systemd/logind > https://www.freedesktop.org/wiki/Software/systemd/multiseat > Process: 2926 ExecStartPre=/sbin/modprobe -abq drm (code=exited, status=226/NAMESPACE) > Process: 2927 ExecStart=/usr/lib/systemd/systemd-logind (code=exited, status=226/NAMESPACE) > Main PID: 2927 (code=exited, status=226/NAMESPACE) > > Feb 03 09:25:20 rescue systemd[1]: systemd-logind.service: Scheduled restart job, restart counter is at 5. > Feb 03 09:25:20 rescue systemd[1]: Stopped Login Service. > Feb 03 09:25:20 rescue systemd[1]: systemd-logind.service: Start request repeated too quickly. > Feb 03 09:25:20 rescue systemd[1]: systemd-logind.service: Failed with result 'exit-code'. > Feb 03 09:25:20 rescue systemd[1]: Failed to start Login Service. When you try to log in as root, it needs to timeout first and only then you get a shell: > Feb 03 09:25:20 rescue systemd[2927]: systemd-logind.service: Failed to set up mount namespacing: Invalid argument > Feb 03 09:25:20 rescue systemd[2927]: systemd-logind.service: Failed at step NAMESPACE spawning /usr/lib/systemd/systemd-logind: Invalid argument > Feb 03 09:25:20 rescue systemd[1]: systemd-logind.service: Main process exited, code=exited, status=226/NAMESPACE > Feb 03 09:25:20 rescue systemd[1]: systemd-logind.service: Failed with result 'exit-code'. > Feb 03 09:25:20 rescue systemd[1]: Failed to start Login Service. > Feb 03 09:25:20 rescue systemd[1]: systemd-logind.service: Scheduled restart job, restart counter is at 5. > Feb 03 09:25:20 rescue systemd[1]: Stopped Login Service. > Feb 03 09:25:20 rescue systemd[1]: systemd-logind.service: Start request repeated too quickly. > Feb 03 09:25:20 rescue systemd[1]: systemd-logind.service: Failed with result 'exit-code'. > Feb 03 09:25:20 rescue systemd[1]: Failed to start Login Service. > Feb 03 09:25:45 rescue dbus-daemon[2408]: [system] Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms) > Feb 03 09:25:45 rescue login[2835]: pam_systemd(login:session): Failed to create Leap 15.2 is OK. My first suspect would be: https://github.com/openSUSE/systemd/commit/9b68367b3a076c168c9f0e8659d01222… The behaviour of the 15.2 and TW kernels is the same: # mount --make-rslave / mount.bin: /: not mount point or bad option. -- You are receiving this mail because: You are on the CC list for the bug.

1 1