[Bug 975824] New: freezes at boot with 4.1.20-11
http://bugzilla.opensuse.org/show_bug.cgi?id=975824 Bug ID: 975824 Summary: freezes at boot with 4.1.20-11 Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-maintainers@forge.provo.novell.com Reporter: lathanderjk@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- HW: Zbook 14 ( 4200u, HD4400, M4100, 1x 8GB RAM, Intel SSD) Complete system freezes at boot(during login to KDE) a also tested with 4.1.20-11 vanila same result. 4.5.1/4.5.0 from repo http://download.opensuse.org/repositories/Kernel:/stable/standard/ works withou problem also 4.1.15-8 and 4.1.13-5 or old 3.16.7-35 too. I also use repo http://download.opensuse.org/repositories/X11:/XOrg/openSUSE_Leap_42.1/ http://download.opensuse.org/repositories/Emulators/openSUSE_Leap_42.1/ and official VLC repo nothing else. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=975824
http://bugzilla.opensuse.org/show_bug.cgi?id=975824#c1
--- Comment #1 from Jozef Kovac
http://bugzilla.opensuse.org/show_bug.cgi?id=975824
http://bugzilla.opensuse.org/show_bug.cgi?id=975824#c2
Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=975824
http://bugzilla.opensuse.org/show_bug.cgi?id=975824#c3
--- Comment #3 from Jozef Kovac
http://bugzilla.opensuse.org/show_bug.cgi?id=975824
http://bugzilla.opensuse.org/show_bug.cgi?id=975824#c4
--- Comment #4 from Jozef Kovac
http://bugzilla.opensuse.org/show_bug.cgi?id=975824
http://bugzilla.opensuse.org/show_bug.cgi?id=975824#c5
--- Comment #5 from Jozef Kovac
http://bugzilla.opensuse.org/show_bug.cgi?id=975824
http://bugzilla.opensuse.org/show_bug.cgi?id=975824#c6
--- Comment #6 from Jozef Kovac
http://bugzilla.opensuse.org/show_bug.cgi?id=975824
Jozef Kovac
http://bugzilla.opensuse.org/show_bug.cgi?id=975824
http://bugzilla.opensuse.org/show_bug.cgi?id=975824#c7
--- Comment #7 from Jozef Kovac
http://bugzilla.opensuse.org/show_bug.cgi?id=975824
http://bugzilla.opensuse.org/show_bug.cgi?id=975824#c8
--- Comment #8 from Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=975824
http://bugzilla.opensuse.org/show_bug.cgi?id=975824#c9
--- Comment #9 from Takashi Iwai
Install it. Run "make install" as root, and it'll copy the files to /boot. Then update grub.conf. % su
Here, one important step I forgot: install modules at first, then install the rest. # make modules_install # make install And usually the step below is superfluous. Do it only if the new entry doesn't appear in GRUB menu. # /usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=975824
http://bugzilla.opensuse.org/show_bug.cgi?id=975824#c10
--- Comment #10 from Jozef Kovac
http://bugzilla.opensuse.org/show_bug.cgi?id=975824
http://bugzilla.opensuse.org/show_bug.cgi?id=975824#c11
--- Comment #11 from Jozef Kovac
http://bugzilla.opensuse.org/show_bug.cgi?id=975824
http://bugzilla.opensuse.org/show_bug.cgi?id=975824#c12
--- Comment #12 from Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=975824
http://bugzilla.opensuse.org/show_bug.cgi?id=975824#c13
--- Comment #13 from Jozef Kovac
http://bugzilla.opensuse.org/show_bug.cgi?id=975824
http://bugzilla.opensuse.org/show_bug.cgi?id=975824#c14
--- Comment #14 from Jozef Kovac
http://bugzilla.opensuse.org/show_bug.cgi?id=975824
http://bugzilla.opensuse.org/show_bug.cgi?id=975824#c15
--- Comment #15 from Takashi Iwai
After first ( 4.1.17-test+) same bug, but i accidentally run git bisect bad instead of git commit bad What now?
You mean "git bisect good" for one of the above? :) Just restart bisection. Save the log once: % git bisect log > bisect.log Then reset, restart and set good/bad. % git bisect reset % git bisect start % git bisect good v4.1.17 % git bisect bad v4.1.18 And look at the previous bisect.log. Answer "git bisect good" or "git bisect bad" just like the previous run until the wrong point. You don't have to build and test for these, because you already know the result. Just go with good/bad. (Actually the first call of "git bisect good v4.1.17" and "... bad v4.1.18" can be replaced with the last good and bad commits in the log.) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=975824
http://bugzilla.opensuse.org/show_bug.cgi?id=975824#c16
--- Comment #16 from Takashi Iwai
in bisect_log i found
bad: [3a1e81ad84e4d880b00ecf7ad8d03b9b772ddfa7] crypto: algif_hash - Fix race condition in hash_check_key git bisect bad 3a1e81ad84e4d880b00ecf7ad8d03b9b772ddfa7
After the whole bisection, git bisect will tell you "the first bad commit". That is the commit we're interested in. Is the commit above such one? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=975824
http://bugzilla.opensuse.org/show_bug.cgi?id=975824#c17
--- Comment #17 from Jozef Kovac
http://bugzilla.opensuse.org/show_bug.cgi?id=975824
http://bugzilla.opensuse.org/show_bug.cgi?id=975824#c18
--- Comment #18 from Jozef Kovac
http://bugzilla.opensuse.org/show_bug.cgi?id=975824
http://bugzilla.opensuse.org/show_bug.cgi?id=975824#c19
--- Comment #19 from Takashi Iwai
polo@polo:~> cd linux-stable polo@polo:~/linux-stable> git commit bad error: pathspec 'bad' did not match any file(s) known to git.
Not "git commit bad" but "git bisect bad". It's a sub-command of git-bisect. Also "git bisect good" as well for a good commit. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=975824
http://bugzilla.opensuse.org/show_bug.cgi?id=975824#c20
--- Comment #20 from Takashi Iwai
i star again but i think first is same.
how can i remove installed kernels(this way) ? just delete all related file in /boot and /lib/modules ?
Yes, remove the corresponding /boot/vmlinuz*, and /lib/modules/$VERSION, /boot/System.map*. Then update grub config via /usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=975824
http://bugzilla.opensuse.org/show_bug.cgi?id=975824#c21
--- Comment #21 from Jozef Kovac
(In reply to Jozef Kovac from comment #18)
polo@polo:~> cd linux-stable polo@polo:~/linux-stable> git commit bad error: pathspec 'bad' did not match any file(s) known to git.
Not "git commit bad" but "git bisect bad". It's a sub-command of git-bisect. Also "git bisect good" as well for a good commit.
well it means: git bisect start # good: [2d5f6b0413359df065fd02d695c08bbc7d998bbd] Linux 4.1.17 git bisect good 2d5f6b0413359df065fd02d695c08bbc7d998bbd # bad: [83fdace666f72dbfc4a7681a04e3689b61dae3b9] Linux 4.1.18 git bisect bad 83fdace666f72dbfc4a7681a04e3689b61dae3b9 # bad: [3a1e81ad84e4d880b00ecf7ad8d03b9b772ddfa7] crypto: algif_hash - Fix race condition in hash_check_key git bisect bad 3a1e81ad84e4d880b00ecf7ad8d03b9b772ddfa7 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=975824
Jozef Kovac
http://bugzilla.opensuse.org/show_bug.cgi?id=975824
http://bugzilla.opensuse.org/show_bug.cgi?id=975824#c22
--- Comment #22 from Takashi Iwai
(In reply to Takashi Iwai from comment #19)
(In reply to Jozef Kovac from comment #18)
polo@polo:~> cd linux-stable polo@polo:~/linux-stable> git commit bad error: pathspec 'bad' did not match any file(s) known to git.
Not "git commit bad" but "git bisect bad". It's a sub-command of git-bisect. Also "git bisect good" as well for a good commit.
well it means:
git bisect start # good: [2d5f6b0413359df065fd02d695c08bbc7d998bbd] Linux 4.1.17 git bisect good 2d5f6b0413359df065fd02d695c08bbc7d998bbd # bad: [83fdace666f72dbfc4a7681a04e3689b61dae3b9] Linux 4.1.18 git bisect bad 83fdace666f72dbfc4a7681a04e3689b61dae3b9 # bad: [3a1e81ad84e4d880b00ecf7ad8d03b9b772ddfa7] crypto: algif_hash - Fix race condition in hash_check_key git bisect bad 3a1e81ad84e4d880b00ecf7ad8d03b9b772ddfa7
No, no, this isn't the first bad commit. This is merely the first check. Now git bisect is pointing to the next commit to test. Just build at this state as is, install and retest. Then give either "git bisect good" or "git bisect bad" again depending on the result. Then git-bisect points to yet another point to test. Repeat this procedure for many times (git suggests how many left) until git shows that you reach to the first bad commit. This is the goal. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=975824
http://bugzilla.opensuse.org/show_bug.cgi?id=975824#c23
--- Comment #23 from Jozef Kovac
http://bugzilla.opensuse.org/show_bug.cgi?id=975824
http://bugzilla.opensuse.org/show_bug.cgi?id=975824#c24
--- Comment #24 from Jozef Kovac
http://bugzilla.opensuse.org/show_bug.cgi?id=975824
http://bugzilla.opensuse.org/show_bug.cgi?id=975824#c25
--- Comment #25 from Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=975824
http://bugzilla.opensuse.org/show_bug.cgi?id=975824#c26
--- Comment #26 from Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=975824
Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=975824
http://bugzilla.opensuse.org/show_bug.cgi?id=975824#c27
--- Comment #27 from Jozef Kovac
http://bugzilla.opensuse.org/show_bug.cgi?id=975824
http://bugzilla.opensuse.org/show_bug.cgi?id=975824#c28
Takashi Iwai
participants (1)
-
bugzilla_noreply@novell.com