[Bug 1082725] New: drm report a bug system hang cause by kernel update
http://bugzilla.suse.com/show_bug.cgi?id=1082725 Bug ID: 1082725 Summary: drm report a bug system hang cause by kernel update Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-maintainers@forge.provo.novell.com Reporter: jnwang@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Hi Sir, My old laptop, Thinkpad R61i, when I install the latest kernel of leap 42.3. When I open a application, system will hang. screen flicker. and hard to switch to alt+f1 console. but， I success do that 1 time. I will upload the screenshot. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1082725 James Wang <jnwang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai@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=1082725 http://bugzilla.suse.com/show_bug.cgi?id=1082725#c1 --- Comment #1 from James Wang <jnwang@suse.com> --- Created attachment 761610 --> http://bugzilla.suse.com/attachment.cgi?id=761610&action=edit 4.4.114-42-default on thinkpad R61i -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1082725 http://bugzilla.suse.com/show_bug.cgi?id=1082725#c2 --- Comment #2 from James Wang <jnwang@suse.com> --- my thinkpad x250 doesn't report this issue. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1082725 http://bugzilla.suse.com/show_bug.cgi?id=1082725#c3 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jnwang@suse.com Flags| |needinfo?(jnwang@suse.com) --- Comment #3 from Takashi Iwai <tiwai@suse.com> --- First off, try to boot both on working (the previous one) and broken (4.4.114) kernels, and check the output of "modinfo i915 | grep file" in both cases. If both point to */weak-updates/* path, it's OK. If only one of them show the different path (*/kernel/drivers/...), it's the problem. Or if both show */kernel/drivers/*, it's also OK. Once after that, try to boot 4.4.114 kernel with drm.debug=0x0e boot option. Give the kernel journal log at the crash. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1082725 http://bugzilla.suse.com/show_bug.cgi?id=1082725#c4 --- Comment #4 from Takashi Iwai <tiwai@suse.com> --- In anyway, it's an old machine, and if you have drm-kmp-default installed, try to uninstall and retest. The 4.9.x based i915 driver that is provided by drm-kmp seems buggy for old Intel chips, unfortunately. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1082725 http://bugzilla.suse.com/show_bug.cgi?id=1082725#c5 James Wang <jnwang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jnwang@suse.com) | --- Comment #5 from James Wang <jnwang@suse.com> --- (In reply to Takashi Iwai from comment #4)
In anyway, it's an old machine, and if you have drm-kmp-default installed, try to uninstall and retest. The 4.9.x based i915 driver that is provided by drm-kmp seems buggy for old Intel chips, unfortunately.
copy that. I'm thinking of it how to reproduce, because when it hangs, it doesn't response input. OK, Let me try remove drp-kmp package. I left it home, so I have to test after work. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1082725 http://bugzilla.suse.com/show_bug.cgi?id=1082725#c6 --- Comment #6 from James Wang <jnwang@suse.com> --- (In reply to Takashi Iwai from comment #3)
First off, try to boot both on working (the previous one) and broken (4.4.114) kernels, and check the output of "modinfo i915 | grep file" in both cases.
If both point to */weak-updates/* path, it's OK. If only one of them show the different path (*/kernel/drivers/...), it's the problem. Or if both They are different, In 4.4.104-39, it's */weak-updates/*, In 4.4.114-42, it's /lib/modules/4.4.114-42-default/updates/drivers/gpu/drm/i915/i915.ko
show */kernel/drivers/*, it's also OK.
Once after that, try to boot 4.4.114 kernel with drm.debug=0x0e boot option. Give the kernel journal log at the crash.
attachment -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1082725 http://bugzilla.suse.com/show_bug.cgi?id=1082725#c7 --- Comment #7 from James Wang <jnwang@suse.com> --- Created attachment 761809 --> http://bugzilla.suse.com/attachment.cgi?id=761809&action=edit sys.class.drm.card0.error -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1082725 http://bugzilla.suse.com/show_bug.cgi?id=1082725#c8 --- Comment #8 from James Wang <jnwang@suse.com> --- Created attachment 761810 --> http://bugzilla.suse.com/attachment.cgi?id=761810&action=edit dmesg -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1082725 http://bugzilla.suse.com/show_bug.cgi?id=1082725#c9 --- Comment #9 from James Wang <jnwang@suse.com> --- If I run 'gedit', i could switch to console. If I run 'terminal', I never could switch to console. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1082725 http://bugzilla.suse.com/show_bug.cgi?id=1082725#c10 --- Comment #10 from James Wang <jnwang@suse.com> --- https://build.opensuse.org/package/show/home%3Atiwai%3Atest%3Aleap-42.3-drm/... seems like no help. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1082725 James Wang <jnwang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xwang@suse.com, | |yfjiang@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=1082725 http://bugzilla.suse.com/show_bug.cgi?id=1082725#c11 --- Comment #11 from James Wang <jnwang@suse.com> --- after remove all drm-kmp-default packages, it works. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1082725 http://bugzilla.suse.com/show_bug.cgi?id=1082725#c12 --- Comment #12 from Takashi Iwai <tiwai@suse.com> --- OK, if the system works better without drm-kmp, just keep it excluded by zypper lock: zypper al drm-kmp-default In the next update of drm-kmp, there will be no longer hardware supplements matching with the old Intel chips, so it won't be drug automatically. But the lock is surer. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1082725 http://bugzilla.suse.com/show_bug.cgi?id=1082725#c13 --- Comment #13 from Takashi Iwai <tiwai@suse.com> --- And I think this is the general breakage due to the recent updates. We may need to refresh the whole KMPs... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1082725 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FEATURE -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com