[Bug 1170344] New: Btrfsprogs 5.6 bug: kernel booting stop at "BTRFS info" output
http://bugzilla.opensuse.org/show_bug.cgi?id=1170344 Bug ID: 1170344 Summary: Btrfsprogs 5.6 bug: kernel booting stop at "BTRFS info" output Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs@suse.de Reporter: hillwoodroc@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I Updated My PC and laptop to Tumbleweed 20200417, then these two systems could not boot, and there is not any error on screen. I tried to chroot to get the dmesg log, I got many BTRFS notices at the end. I find Btrfsprogs was updated before 10 days ago in Factory. I guess this is a bug for Btrfsprogs. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1170344
http://bugzilla.opensuse.org/show_bug.cgi?id=1170344#c1
--- Comment #1 from Hillwood Yang
http://bugzilla.opensuse.org/show_bug.cgi?id=1170344
Hillwood Yang
http://bugzilla.opensuse.org/show_bug.cgi?id=1170344
http://bugzilla.opensuse.org/show_bug.cgi?id=1170344#c2
--- Comment #2 from Hillwood Yang
http://bugzilla.opensuse.org/show_bug.cgi?id=1170344
Hillwood Yang
http://bugzilla.opensuse.org/show_bug.cgi?id=1170344
http://bugzilla.opensuse.org/show_bug.cgi?id=1170344#c3
--- Comment #3 from Hillwood Yang
http://bugzilla.opensuse.org/show_bug.cgi?id=1170344
http://bugzilla.opensuse.org/show_bug.cgi?id=1170344#c4
--- Comment #4 from Hillwood Yang
http://bugzilla.opensuse.org/show_bug.cgi?id=1170344
http://bugzilla.opensuse.org/show_bug.cgi?id=1170344#c6
--- Comment #6 from Hillwood Yang
http://bugzilla.opensuse.org/show_bug.cgi?id=1170344
http://bugzilla.opensuse.org/show_bug.cgi?id=1170344#c7
--- Comment #7 from Hillwood Yang
Created attachment 836858 [details] dmesg for my laptop
This time it stop at "rfkill: input handler disabled"
s/stop/stopped -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1170344
http://bugzilla.opensuse.org/show_bug.cgi?id=1170344#c9
--- Comment #9 from Hillwood Yang
Supposing it's a kernel regression, can you rollback and check whether the old kernel works?
I don't think this is a kernel bug, because it works fine after just updating kernel to 5.6.4. And also the system can work after rollbacking to the version before 20200417. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1170344
Hillwood Yang
http://bugzilla.opensuse.org/show_bug.cgi?id=1170344
Hillwood Yang
http://bugzilla.opensuse.org/show_bug.cgi?id=1170344
http://bugzilla.opensuse.org/show_bug.cgi?id=1170344#c10
--- Comment #10 from Hillwood Yang
Supposing it's a kernel regression, can you rollback and check whether the old kernel works?
Confirm this is a LUKS issue. After I format the home partition without LUKS, the system works fine. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1170344
http://bugzilla.opensuse.org/show_bug.cgi?id=1170344#c11
Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=1170344
http://bugzilla.opensuse.org/show_bug.cgi?id=1170344#c12
--- Comment #12 from Hillwood Yang
Then it might be the plymouth problem that was recently mentioned on opensuse-factory ML.
You are right. Removing plymouth can workaround this issue. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1170344
Hillwood Yang
http://bugzilla.opensuse.org/show_bug.cgi?id=1170344
http://bugzilla.opensuse.org/show_bug.cgi?id=1170344#c13
Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=1170344
http://bugzilla.opensuse.org/show_bug.cgi?id=1170344#c14
--- Comment #14 from Cliff Zhao
http://bugzilla.opensuse.org/show_bug.cgi?id=1170344
http://bugzilla.opensuse.org/show_bug.cgi?id=1170344#c15
Cliff Zhao
please rewrite the detailed reproduction steps, and upload the support-log please.
Could not reproduce in recent distros. -- You are receiving this mail because: You are on the CC list for the bug.
participants (2)
-
bugzilla_noreply@novell.com
-
bugzilla_noreply@suse.com