http://bugzilla.suse.com/show_bug.cgi?id=1170696 http://bugzilla.suse.com/show_bug.cgi?id=1170696#c1 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adrian.schroeter@suse.com, | |tiwai@suse.com Flags| |needinfo?(adrian.schroeter@ | |suse.com) --- Comment #1 from Takashi Iwai --- No ssh access available after it freezes, too? Could you give hwinfo output? Our team hasn't received this company standard laptop, so we have no idea what hardware it is at all. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1170696 http://bugzilla.suse.com/show_bug.cgi?id=1170696#c3 Adrian Schröter changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(adrian.schroeter@ | |suse.com) | --- Comment #3 from Adrian Schröter --- No ssh, no ping and even the cursor stops blinking on the linux console. I see this crash either seconds or 2 minutes after booting or sometimes it can take 1 hour. No idea how to trigger it. For some time I suspected the wireless card, so I removed it and used an USB wireless adapter, but it remains crashing. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1170696 http://bugzilla.suse.com/show_bug.cgi?id=1170696#c5 --- Comment #5 from Adrian Schröter --- Leap 15.1 (Kernel 4.12.14-lp151.28.48) seems to be stable at first glance. But I keep waiting a bit more ... Btw, I do test it atm by not touching the notebook because it looks relative reproducible via that. So any kind of suspend handling might have an influence. But I remember the freezes also while actively working on it. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1170696 http://bugzilla.suse.com/show_bug.cgi?id=1170696#c7 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sndirsch@suse.com --- Comment #7 from Takashi Iwai --- Hrm, you can try the official TW kernel instead of Kernel:stable, then. Looking at hwinfo, it's a Kabylake. Stefan, is it the machine you took? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1170696 Lubos Kocman changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High CC| |lubos.kocman@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=1170696 Lubos Kocman changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 - High |P1 - Urgent -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1170696 http://bugzilla.suse.com/show_bug.cgi?id=1170696#c11 Adrian Schröter changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(adrian.schroeter@ | |suse.com) | --- Comment #11 from Adrian Schröter --- yes, still freezing with that kernel. Leap 15.1 kernel still stable. So no change for me. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1170696 https://bugzilla.suse.com/show_bug.cgi?id=1170696#c13 --- Comment #13 from Adrian Schröter --- Would it be helpfull if I give you my notebook? I can not really using it anyway atm .... (or only with 15.1 kernel, but that causes some other problems). I would also exchange it permanently against a comparable if wanted :) -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1170696 https://bugzilla.suse.com/show_bug.cgi?id=1170696#c15 --- Comment #15 from Adrian Schröter --- Using kernel-default-5.3.18-lp152.100.1.g74fea2c.x86_64 from there still running into a freeze a few seconds after boot. Still trying to get a trace using this kernel, but little hope ... -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1170696 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- CC|sndirsch@suse.com | -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1170696 https://bugzilla.suse.com/show_bug.cgi?id=1170696#c16 --- Comment #16 from Adrian Schröter --- plenty of crashes later on 5.9.0-rc2-2.g4229f31-default I saw once a screen with a partly ioremap error dump. A "screenshot" is attached. Note, the system runs stable sometimes, but suddenly is crashing for some time. The system is nearly unable to boot then for a longer time. switching it off and removing power plug for 10 minutes helps often. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1170696 https://bugzilla.suse.com/show_bug.cgi?id=1170696#c18 --- Comment #18 from Adrian Schr�ter --- kernel-default-5.10.rc3-1.1.ge72caa5.x86_64 from Kernel:Head project changed the behaviour slightly in the way the crash/freeze happens earlier. I also updated the BIOS firmware to latest version from last month btw. I boot the system in runlevel 3 meanwhile for testing. It is crashing immediatly after initializing the framebuffer now (last line is i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device (typed manually, but checked for typos). Afterwards the crash LED is blinking for a few seconds until it stops and the entire system keeps frozen. I did not found any way yet to get a kernel trace in this situation. Can you suggest any way? The linux kernel 4.x from openSUSE 15.1 is still stable on that 15.2 installation. (except that it seems to have suspend issues with that system and I need to boot first a 5.x kernel after power off, wait for the crash before I boot the 4.x one. Otherwise the wlan has a high chance of not being initialized). I would really appreciate in any help to get my main workstation notebook in a usable state. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1170696 https://bugzilla.suse.com/show_bug.cgi?id=1170696#c20 --- Comment #20 from Adrian Schr�ter --- after some more googling, can you confirm that this is most likely a long standing issue with intel firmware? Unlikely to get solved? I would request new hardware then... https://linuxreviews.org/Linux_Kernel_5.5_Will_Not_Fix_The_Frequent_Intel_GP... -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1170696 https://bugzilla.suse.com/show_bug.cgi?id=1170696#c22 --- Comment #22 from Adrian Schr�ter --- removing i915/kbl_dmc_ver1_04.bin and recreating the firmware is indeed solving the issue. At least I was able to reach even this web browser window. Let's see if anything else breaks over time. (/me is punishing himself for not trying that before ... thought the screen will stay black without firmware) -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1170696 https://bugzilla.suse.com/show_bug.cgi?id=1170696#c24 --- Comment #24 from Adrian Schr�ter --- that parameter seems to help also. At least stable for almost one minute already :) -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1170696 Oliver Kurz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |okurz@suse.com -- You are receiving this mail because: You are on the CC list for the bug.