http://bugzilla.suse.com/show_bug.cgi?id=1010656 http://bugzilla.suse.com/show_bug.cgi?id=1010656#c1 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai@suse.com --- Comment #1 from Takashi Iwai --- A blind shot: could you check booting with nomodeset option? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1010656 http://bugzilla.suse.com/show_bug.cgi?id=1010656#c3 --- Comment #3 from Andreas Schneider --- Graphics card: NVIDIA Corporation GK107 [GeForce GT 640] Driver: nuoveau -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1010656 http://bugzilla.suse.com/show_bug.cgi?id=1010656#c5 --- Comment #5 from Andreas Schneider --- If you can tell me how to get the config file, new entry in grub, etc. then I can do it. I have to check but I think 4.8.6 hangs sometimes at the same position and sometimes it just boots fine. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1010656 http://bugzilla.suse.com/show_bug.cgi?id=1010656#c7 --- Comment #7 from Andreas Schneider --- Hi Takashi, I haven't had the time to bisect yet. However with Kernel 4.8.8 using nomodeset in the kernel commandline successfully boots the system. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1010656 http://bugzilla.suse.com/show_bug.cgi?id=1010656#c9 --- Comment #9 from Takashi Iwai --- (In reply to Andreas Schneider from comment #8)

I'm not a kernel developer, but I tried to bisect.

However after:

make make install grub2-mkconfig -o /boot/grub2/grub.cfg

and reboot I was not able to start that kernel it crashed. Also 'make install' told me I need a initrd ...

So did make make install make modules_install mkinitrd

Now even a normal SUSE kernel doesn't boot anymore. Please provide better instructions. I'm going to try to fix my system now ...

Sorry, I overlooked your inquiry! Too bad that it didn't work easily. I attach below two scripts I often use for myself; the first one is to install a self-made kernel. Just run the script on the kernel tree you built, then it'll include the kernel, System.map and modules, update bootloader, etc. You'd need to pass -f option if the kernel was already installed and you want to just update / re-install the same kernel version. Another one is to remove the installed kernels and modules. Just pass the kernel version-release string, or pass the file name /boot/vmlinuz-4.4.x-xyz, then the script will guess and remove the corresponding ones. Last but not least: don't forget to change CONFIG_LOCALVERSION in your .config after running make localmodconfig. The point is to install a different kernel flavor so that the original kernel is kept intact. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1010656 http://bugzilla.suse.com/show_bug.cgi?id=1010656#c11 --- Comment #11 from Takashi Iwai --- Created attachment 703883 --> http://bugzilla.suse.com/attachment.cgi?id=703883&action=edit remove-kernel script -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1010656 http://bugzilla.suse.com/show_bug.cgi?id=1010656#c13 --- Comment #13 from Andreas Schneider --- I think it has something todo with mounting. With 4.8.10 sometimes the system boots but then my /home is not mounted. /dev/sda3 -> /root /dev/sdb1 + /dev/sdc1 -> /dev/md0 /dev/md0 -> dmcrypt dmcrypt -> /home (xfs) /dev/sdd1 -> /home/asn/storage (btrfs) cat /etc/crypttab cr_home /dev/disk/by-id/md-uuid-bddc3fad:3bec21d2:880d66c3:2d4c587c none discard tail -2 /etc/fstab /dev/mapper/cr_home /home xfs nofail 0 2 UUID=0033c508-6f0e-486e-a4bd-f409db47de17 /home/asn/storage btrfs defaults 0 0 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1010656 http://bugzilla.suse.com/show_bug.cgi?id=1010656#c15 --- Comment #15 from Andreas Schneider --- It is hard to really reproduce because it sometimes works and sometimes doesn't. I normally booted 3 times to see if it fails once. The patch looks correct, but this might trigger something else. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1010656 http://bugzilla.suse.com/show_bug.cgi?id=1010656#c17 --- Comment #17 from Andreas Schneider --- git bisect start # good: [3aed64f6d341cdb62bb2d6232589fb13448ce063] pvclock: introduce seqcount-like API git bisect good 3aed64f6d341cdb62bb2d6232589fb13448ce063 # bad: [61385cc1db42b163c664429ab87d6399ea043c0d] Linux 4.8.8 git bisect bad 61385cc1db42b163c664429ab87d6399ea043c0d # bad: [8509eb19618c050b017a3da7f6dd3180106cdf32] Merge branch 'drm-fixes-4.8' of git://people.freedesktop.org/~agd5f/linux into drm-fixes git bisect bad 8509eb19618c050b017a3da7f6dd3180106cdf32 # bad: [d3f422c8d58b2f0d68a51db88389a715dc10b4d2] Merge branch 'nvmf-4.8-rc' of git://git.infradead.org/nvme-fabrics into for-linus git bisect bad d3f422c8d58b2f0d68a51db88389a715dc10b4d2 # bad: [6c84239d595dc6ffe39f0f03dae2f64ed200db95] Merge tag 'rtc-4.8' of git://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux git bisect bad 6c84239d595dc6ffe39f0f03dae2f64ed200db95 # bad: [0cda611386b2fcbf8bb32e9a5d82bfed4856fc36] Merge tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dledford/rdma git bisect bad 0cda611386b2fcbf8bb32e9a5d82bfed4856fc36 # bad: [d58b0d980f0b1c27204da0e05537b606da45a07f] Merge branch 'for-linus-4.8' of git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs git bisect bad d58b0d980f0b1c27204da0e05537b606da45a07f # bad: [b067c9045af4791a5836042f743d12477131f7b5] Merge branch 'parisc-4.8-1' of git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux git bisect bad b067c9045af4791a5836042f743d12477131f7b5 # good: [fb1b83d3ff78168e10799627f231cf0c05c9d80d] Merge tag 'modules-next-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux git bisect good fb1b83d3ff78168e10799627f231cf0c05c9d80d # good: [472f95f32d5aa07eda96a6b2578b85d7b27c5110] binfmt_flat: allow compressed flat binary format to work on MMU systems git bisect good 472f95f32d5aa07eda96a6b2578b85d7b27c5110 # bad: [cd70c37b5a23eee7aa411205e2b4c74097f52336] [media] staging: add MEDIA_SUPPORT dependency git bisect bad cd70c37b5a23eee7aa411205e2b4c74097f52336 # good: [9f8b333308dcb6af321526a54612cfaa7999a995] [media] vim2m: copy the other colorspace-related fields as well git bisect good 9f8b333308dcb6af321526a54612cfaa7999a995 # bad: [52e37f0a6655158c731a35b79106d3150fd3847c] [media] media: adv7180: Fix broken interrupt register access git bisect bad 52e37f0a6655158c731a35b79106d3150fd3847c # bad: [6cb164f551abfda045326ceb50bb4e5966a990c1] [media] vb2: Fix allocation size of dma_parms git bisect bad 6cb164f551abfda045326ceb50bb4e5966a990c1 # first bad commit: [6cb164f551abfda045326ceb50bb4e5966a990c1] [media] vb2: Fix allocation size of dma_parms I noted the following two commits if I need to redo bisect. bad: 52e37f0a6655158c731a35b79106d3150fd3847c good: 472f95f32d5aa07eda96a6b2578b85d7b27c5110 For those I was sure they were working or broken. The commits in between were racy. So the bad commits sometimes worked. I think the issue involves more than one patch. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1010656 http://bugzilla.suse.com/show_bug.cgi?id=1010656#c19 --- Comment #19 from Andreas Schneider --- I've started with 4.8.6 but then used the wrong command so I reduced the range and didn't start from 4.8.6 again. I kept a 4.7.0-rc3 kernel around as this was a good working version. And iirc it is a build from 472f95f32d5aa07eda96a6b2578b85d7b27c5110 I can redo the bisect between: bad: 52e37f0a6655158c731a35b79106d3150fd3847c good: 472f95f32d5aa07eda96a6b2578b85d7b27c5110 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1010656 http://bugzilla.suse.com/show_bug.cgi?id=1010656#c21 --- Comment #21 from Andreas Schneider --- The first released kernel with the issue is v4.8-rc1 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1010656 http://bugzilla.suse.com/show_bug.cgi?id=1010656#c23 --- Comment #23 from Andreas Schneider --- I was wrong, maybe I mixed the numbers and wanted to write 4.6.8. I always end up in a btrfs merge commit as the bad one and then only get good commits. I hate git-merge -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1010656 http://bugzilla.suse.com/show_bug.cgi?id=1010656#c25 Jiri Slaby changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |jslaby@suse.com Resolution|--- |FIXED --- Comment #25 from Jiri Slaby --- 4.9 is approaching to tumbleweed. So I am closing this as fixed then. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1010656 http://bugzilla.suse.com/show_bug.cgi?id=1010656#c27 Jiri Slaby changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |NORESPONSE --- Comment #27 from Jiri Slaby --- Closing due to lack of response. -- You are receiving this mail because: You are on the CC list for the bug.