http://bugzilla.suse.com/show_bug.cgi?id=1017783 http://bugzilla.suse.com/show_bug.cgi?id=1017783#c1 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bpetkov@suse.com, | |tiwai@suse.com --- Comment #1 from Takashi Iwai --- Boris, do you know of any known breakage in this regard? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1017783 http://bugzilla.suse.com/show_bug.cgi?id=1017783#c2 Emanuel Castelo changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |emanuel.castelo@gmail.com --- Comment #2 from Emanuel Castelo --- System: Host: linux-s4s1 Kernel: 4.8.14-1-default x86_64 (64 bit) Desktop: Cinnamon 3.2.7 Distro: openSUSE Tumbleweed Machine: Device: laptop System: TOSHIBA product: Satellite L555 v: PSLN0U-00T00E Mobo: TOSHIBA model: KTWAA v: 1.00 BIOS: TOSHIBA v: V1.90 date: 12/18/2009 i was able to boot thru kernel shown without issues, i have not been able to boot 4.9 kernel, boot process goes from grub screen to bios screen in endless loop, otherwise every update has installed without issue, as a workaround i have added lock to 'kernel-default' and un-installed 4.9 kernel. there was mention of relation to wifi chip, mine is Intel WiFi Link 5100 driver: iwlwifi -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1017783 http://bugzilla.suse.com/show_bug.cgi?id=1017783#c5 --- Comment #5 from Robert Pretki --- Created attachment 708606 --> http://bugzilla.suse.com/attachment.cgi?id=708606&action=edit dmesg dmesg -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1017783 http://bugzilla.suse.com/show_bug.cgi?id=1017783#c7 Borislav Petkov changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(tiwai@suse.com) --- Comment #7 from Borislav Petkov --- Hmm, Takashi, do we have any of those laptops somewhere to try to repro? The forums.opensuse.org thread has a couple more toshiba models and even a thinkpad. One other thing I can think of is bisecting it, if anyone of you people who can reproduce, are willing to give it a try. If you have questions what to do exactly, feel free to ask. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1017783 http://bugzilla.suse.com/show_bug.cgi?id=1017783#c9 Borislav Petkov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |r.pretki@gmail.com Flags| |needinfo?(r.pretki@gmail.co | |m) --- Comment #9 from Borislav Petkov --- Hmm, ok, so I guess we need to start poking to try to pinpoint the issue. Robert, can you please start the box and press "e" at the grub boot prompt with the 4.9 kernel and remove the line starting with "initrd ..." and then press F10 to boot. It still won't boot all the way but I want to see whether the initrd is the culprit. Also, on the "linux" line, remove "quiet" and add "log_buf_len=16M ignore_loglevel initcall_debug" so that we can at least try to see some messages. You can make a video of the boot and upload it somewhere so that I can take a look at what exactly happens. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1017783 http://bugzilla.suse.com/show_bug.cgi?id=1017783#c11 --- Comment #11 from Guy Dawson --- Created attachment 708747 --> http://bugzilla.suse.com/attachment.cgi?id=708747&action=edit dmesg output from affected HP DL360 G4p server -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1017783 http://bugzilla.suse.com/show_bug.cgi?id=1017783#c13 --- Comment #13 from Guy Dawson --- I need to dig around the big box of cables (tm) to find a null modem cable to make the connection. I'll post what I can get when I get it. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1017783 http://bugzilla.suse.com/show_bug.cgi?id=1017783#c16 --- Comment #16 from Borislav Petkov --- (In reply to Robert Pretki from comment #14)

I have just sent to your e-mail address a link to the video (MKV, x264), which includes: (1) boot with the default settings; (2) boot without "quiet"; (3) boot with "dis_ucode_ldr" (instead of "quiet"); (4) boot without "initrd" line;

Thanks for doing that. It doesn't tell us much but at least it doesn't look like the initrd changes anything so it must be something happening very early causing the machine to triple-fault. The nasty thing is that debugging such an issue on a laptop is always a PITA as we can't log serial console. One thing I could think of is to try booting with "nosmp nomodeset" so that we init only one CPU and thus avoid a whole lot of init code and see whether that works. The "nomodeset" should switch off the gfx modesetting so that we can maybe see more output from the kernel. Before you reboot though, edit /etc/default/grub and change GRUB_TERMINAL to "console": GRUB_TERMINAL="console" Then do: # grub2-mkconfig -o /boot/grub2/grub.cfg and reboot. When you're back in the grub menu, remove "quiet" and add "nosmp nomodeset ignore_loglevel" and then press F10. And upload the video again. Hopefully, we'll be able to see more output. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1017783 http://bugzilla.suse.com/show_bug.cgi?id=1017783#c18 --- Comment #18 from Emanuel Castelo --- tried openSUSE Tumbleweed 20170104 as suggested above; System: Host: linux-s4s1 Kernel: 4.8.14-1-default x86_64 (64 bit) Desktop: Cinnamon 3.2.7 Distro: openSUSE Tumbleweed 20170104 Machine: Device: laptop System: TOSHIBA product: Satellite L555 v: PSLN0U-00T00E Mobo: TOSHIBA model: KTWAA v: 1.00 BIOS: TOSHIBA v: V1.90 date: 12/18/2009 removed kernel 4.9.2.x previously installed, and installed latest kernel https://gist.github.com/anonymous/ab11ffa621c8cdbdeec174b4ad56f2f7 still broke kernel. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1017783 Joey Lee changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jlee@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1017783 Dominique Leuenberger changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High Severity|Normal |Major -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1017783 http://bugzilla.suse.com/show_bug.cgi?id=1017783#c21 --- Comment #21 from Dominique Leuenberger --- possible related upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=192111 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1017783 http://bugzilla.suse.com/show_bug.cgi?id=1017783#c23 --- Comment #23 from Joey Lee --- (In reply to Dominique Leuenberger from comment #21)

possible related upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=192111

In bko#192111, Ivan bisected out that the bad patch is 8b355e3bc. The result is possible because acpi/osl.c uses synchronize_rcu_expedited to speed up grace period in acpi_os_map_cleanup() since v3.19: 74b51ee152b ACPI / osl: speedup grace period in acpi_os_map_cleanup The detail of 8b355e3bc needs RCU expert's comment. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1017783 Borislav Petkov changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED Assignee|kernel-maintainers@forge.pr |jlee@suse.com |ovo.novell.com | Flags|needinfo?(jlee@suse.com) | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1017783 http://bugzilla.suse.com/show_bug.cgi?id=1017783#c27 Bruno Pesavento changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bpesavento@infinito.it --- Comment #27 from Bruno Pesavento --- (In reply to Joey Lee from comment #26)

Could you please help to test it?

FYI, successfully booted that kernel on Leap 42.2 on ASUS N551 (i7-4720HQ+GTX960M), everything apparently fine so far. Previously it was impossible to boot kernel 4.9.0-4.g1af4b0f-default from Kernel:/stable/standard/. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1017783 http://bugzilla.suse.com/show_bug.cgi?id=1017783#c29 --- Comment #29 from Emanuel Castelo --- http://download.opensuse.org/repositories/home:/joeyli:/branches:/openSUSE:/... installed and booted without issue. System: Host: linux-s4s1 Kernel: 4.9.2-1.g2d3c294-default x86_64 (64 bit gcc: 6.2.1) Desktop: Cinnamon 3.2.8 Distro: openSUSE Tumbleweed Machine: Device: laptop System: TOSHIBA product: Satellite L555 v: PSLN0U-00T00E Mobo: TOSHIBA model: KTWAA v: 1.00 BIOS: TOSHIBA v: V1.90 date: 12/18/2009 Thank you and great job to all who made this happen, this is why i stick with Opensuse. If there is log info needed i will be happy to provide. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1017783 http://bugzilla.suse.com/show_bug.cgi?id=1017783#c33 --- Comment #33 from Stan Kain --- The release candidate for the kernel resolved my issue with my Toshiba C50A laptop computer. I have completed a fresh install of Tumbleweed using this kernel and my system boots without issue. Thank you! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1017783 http://bugzilla.suse.com/show_bug.cgi?id=1017783#c35 --- Comment #35 from Stan Kain --- No objection in the least. Please feel free to do so. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1017783 http://bugzilla.suse.com/show_bug.cgi?id=1017783#c37 --- Comment #37 from Bruno Pesavento --- http://beta.suse.com/private/bpetkov/ tested, and works here on ASUS N551 Leap 42.2. Boots fine from what I can tell; lots of ACPI harmless "Errors" typical of 4.9 kernels. Couldn't test HW thoroughly because of lack of a matching kernel-devel. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1017783 http://bugzilla.suse.com/show_bug.cgi?id=1017783#c39 --- Comment #39 from Borislav Petkov --- Ok, here's a test 4.9 with the final fix: http://download.opensuse.org/repositories/home:/bpetkov:/tw-rcu2/standard/ and with all kernel flavors. Thanks for testing. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1017783 http://bugzilla.suse.com/show_bug.cgi?id=1017783#c41 --- Comment #41 from Bruno Pesavento --- bruno@LT_B:~> uname -r 4.9.2-1.gc693a29-default bruno@LT_B:~> Works as expected here, including building of extra kernel modules. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1017783 http://bugzilla.suse.com/show_bug.cgi?id=1017783#c44 --- Comment #44 from Borislav Petkov --- (In reply to Dainius Masiliunas from comment #43)

I'm not sure if it's the same problem,

Well, "freezes at boot" is not the same as "RCU stalls".

but with kernel 4.9.0-2 I can boot fine, but after a few minutes I start getting RCU stalls. That makes processes hang and rebooting impossible (systemd shows that it's waiting for services to turn off, but never kills them, and pressing ctrl+alt+del makes it hang too). This is a desktop system with i5-3470.

Workaround is to install kernel 4.9.3 from the Kernel:stable repo.

Sounds like the fix for your issue went into 4.9.3 and you're good to go. Or what is the problem? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1017783 http://bugzilla.suse.com/show_bug.cgi?id=1017783#c46 --- Comment #46 from Borislav Petkov --- (In reply to Dainius Masiliunas from comment #45)

Well, it's not in base Tumbleweed repository yet. And I'm not sure if the fix for this issue is in base Tumbleweed yet either (I see references to 4.9.2 here).

You just have to be patient - they will all land in 4.9.x sooner rather than later. Also, there's nothing wrong with running 4.9.3 from Kernel:stable as long as your machine works fine with it. Actually, Kernel:stable is what is going to land in tumbleweed later so you're previewing it :-) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1017783 http://bugzilla.suse.com/show_bug.cgi?id=1017783#c48 Borislav Petkov changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #48 from Borislav Petkov --- Did you read the previous message before posting? You need to be a little bit more patient - fixes like that need to be tested on everything else so as to make sure they don't break other machines. And this needs a couple of days at least. So run 4.8.x until then - it would hardly be any difference. In any case, the fix will land in 4.9.6, most probably. Greg just picked it up: https://lkml.kernel.org/r/148518123623074@kroah.com -- You are receiving this mail because: You are on the CC list for the bug.