[Bug 1170696] New: Dell Latitude 7490 freezes with 15.2
http://bugzilla.suse.com/show_bug.cgi?id=1170696 Bug ID: 1170696 Summary: Dell Latitude 7490 freezes with 15.2 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-maintainers@forge.provo.novell.com Reporter: adrian.schroeter@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- My standard SUSE company notebook (Dell Latitude 7490) is freezing since 15.2. Since I was unable to get any traces or crash dumps yet, I re-installed 15.1 to verify the hardware is not broken. The problem is back after updating to 15.2 again (just keeping always my /home partition). The freeze happens also a few minutes after booting in runlevel 3. No kernel crash panic LED and of course no dump in systemd. I would try to give more details, but I am bit clueless atm how to get more data. -- 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#c1 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adrian.schroeter@suse.com, | |tiwai@suse.com Flags| |needinfo?(adrian.schroeter@ | |suse.com) --- Comment #1 from Takashi Iwai <tiwai@suse.com> --- 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#c2 --- Comment #2 from Adrian Schröter <adrian.schroeter@suse.com> --- Created attachment 836975 --> http://bugzilla.suse.com/attachment.cgi?id=836975&action=edit hwinfo from Dell Latitude 7490 -- 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 <adrian.schroeter@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(adrian.schroeter@ | |suse.com) | --- Comment #3 from Adrian Schröter <adrian.schroeter@suse.com> --- 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#c4 --- Comment #4 from Takashi Iwai <tiwai@suse.com> --- Thanks. Could you install openSUSE Leap 15.1 kernel and OBS Kernel:stable kernel on top of the existing Leap 15.2 system and see whether they can trigger the similar problem? -- 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 <adrian.schroeter@suse.com> --- 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#c6 --- Comment #6 from Adrian Schröter <adrian.schroeter@suse.com> --- Unable to boot Kernel:stable atm, created a cert.der based on sslcert from Kernel:stable in /boot/efi/ but grub still refuses to load 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 <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sndirsch@suse.com --- Comment #7 from Takashi Iwai <tiwai@suse.com> --- 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 http://bugzilla.suse.com/show_bug.cgi?id=1170696#c8 --- Comment #8 from Stefan Dirsch <sndirsch@suse.com> --- No. I took the Dell Precision 5520 with Intel/nvidia combo. -- 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 <lubos.kocman@suse.com> 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 http://bugzilla.suse.com/show_bug.cgi?id=1170696#c9 --- Comment #9 from Lubos Kocman <lubos.kocman@suse.com> --- Precission with 5530 has no issues, I had some freeze experience with previous Leap kernel, but it got fixed with update. lkocman@linux:~/Workspace/sles/release-notes-sles> uname -r 5.3.18-lp152.11-default -- 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 <lubos.kocman@suse.com> 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#c10 Lubos Kocman <lubos.kocman@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(adrian.schroeter@ | |suse.com) --- Comment #10 from Lubos Kocman <lubos.kocman@suse.com> --- Any update on the issue? Can this still be reproduced? -- 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 <adrian.schroeter@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(adrian.schroeter@ | |suse.com) | --- Comment #11 from Adrian Schröter <adrian.schroeter@suse.com> --- 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#c12 Lubos Kocman <lubos.kocman@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P1 - Urgent |P2 - High --- Comment #12 from Lubos Kocman <lubos.kocman@suse.com> --- Reducing priority to P2 as one of criteria is no P1s and this is the only P1 we have. I can see that this will be a hardware specific issue and not a generic crash. Please make sure to submit fix as a maintenance update to Leap 15.2 Thank you -- 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 <adrian.schroeter@suse.com> --- 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#c14 --- Comment #14 from Takashi Iwai <tiwai@suse.com> --- (In reply to Adrian Schröter from comment #13)
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 :)
Could you try the latest Leap 15.2 kernel in OBS Kernel:openSUSE-15.2 repo? I've backported quite a few i915 patches that caused lockups on other machines, and this supposedly worked on others. If the problem still persists, we might consider taking over the machine. -- 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 <adrian.schroeter@suse.com> --- 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 <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |patrik.jakobsson@suse.com, | |tzimmermann@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 Stefan Dirsch <sndirsch@suse.com> 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 Miroslav Beneš <mbenes@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mbenes@suse.com Assignee|kernel-maintainers@forge.pr |kernel-bugs@opensuse.org |ovo.novell.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 <adrian.schroeter@suse.com> --- 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#c17 --- Comment #17 from Adrian Schröter <adrian.schroeter@suse.com> --- Created attachment 841987 --> https://bugzilla.suse.com/attachment.cgi?id=841987&action=edit picture of ioremap error report. The drawing errors were on screen. -- 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 <adrian.schroeter@suse.com> --- 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#c19 --- Comment #19 from Adrian Schr�ter <adrian.schroeter@suse.com> --- it is our official company notebook model for some time after all ... -- 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 <adrian.schroeter@suse.com> --- 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#c21 --- Comment #21 from Takashi Iwai <tiwai@suse.com> --- Honestly speaking, it's hard to judge because of the lack of the crash information. But this looks indeed like the same problem. Did you try to exclude the firmware as pointed there? You'd need to rebuild initrd after the removal. It's unfortunate that our team (hardware-enablement) hasn't received the recent company-standard laptop for verification at all. The last one we received was some Skylake models in a few years ago. An employee may receive something for the workstation or the laptop for daily works, but not for the evaluation and the debugging purpose for the team. (And of course we're not involved with the decision which model to choose, either.) -- 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 <adrian.schroeter@suse.com> --- 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#c23 --- Comment #23 from Patrik Jakobsson <patrik.jakobsson@suse.com> --- If the DMC is causing issues you can also try the different i915.enable_dc module parameter settings (with the DMC firmware loaded). i915.enable_dc=0 should be equivalent to not loading the firmware (at least regarding the power states). -Patrik -- 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 <adrian.schroeter@suse.com> --- 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 https://bugzilla.suse.com/show_bug.cgi?id=1170696#c25 --- Comment #25 from Adrian Schr�ter <adrian.schroeter@suse.com> --- (with firmware file restored and re-created initrd of course) -- 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 <okurz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |okurz@suse.com -- 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