[opensuse-factory] BZ cannot search "DWARF2 unwinder stuck"
This is merely the latest instance where I try to search BZ and wait and wait and wait and wait only to have the search silently fail. In the instant case, I deselected everything, put "DWARF2 unwinder stuck" in the comments box, and put 5y in the upper change history between box before clicking to proceed (search button). A blank page displays straight away, and stays that way for several minutes, with status bar initially displaying "Transferring data from bugzilla.opensuse.org...", then switching to "Done", without producing any change in the all white viewport. What can I do differently, without imposing unwanted restrictions, to nudge BZ into doing something useful searching for such a string? TW/4.6.3 dmesg excerpt: [ 16.041803] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in has_audio (expected 1, found 0) [ 16.041805] ------------[ cut here ]------------ [ 16.041826] WARNING: CPU: 0 PID: 66 at ../drivers/gpu/drm/i915/intel_display.c:12802 intel_modeset_check_state+0x67e/0x870 [i915]() [ 16.041827] pipe state doesn't match! [ 16.041849] Modules linked in: snd_hda_codec i915 snd_hda_core snd_hwdep snd_pcm snd_timer drm_kms_helper e1000e ptp gpio_ich snd drm fb_sys_fops dm_mod pps_core iTCO_wdt iTCO_vendor_support syscopyarea coretemp sysfillrect lpc_ich mei_me dell_wmi soundcore kvm_intel sparse_keymap video sysimgblt mfd_core i2c_i801 mei ppdev parport_pc parport shpchp i2c_algo_bit wmi kvm acpi_cpufreq dcdbas button 8250_fintek pcspkr tpm_tis tpm irqbypass hid_generic usbhid ehci_pci uhci_hcd ehci_hcd sr_mod cdrom ata_generic serio_raw usbcore usb_common sg [ 16.041851] CPU: 0 PID: 66 Comm: kworker/u16:5 Not tainted 4.4.2-1-default #1 [ 16.041852] Hardware name: Dell Inc. OptiPlex 780 /03NVJ6, BIOS A14 08/21/2012 [ 16.041856] Workqueue: events_unbound async_run_entry_fn [ 16.041858] ffffffffa04e5f00 ffff8800d7a878a0 ffffffff8137eb99 ffff8800d7a878e8 [ 16.041859] ffff8800d7a878d8 ffffffff8107c552 ffff880037803400 ffff880112b59000 [ 16.041860] ffff8800d903c400 ffff8800d4475800 ffff8800d67d8348 ffff8800d7a87938 [ 16.041861] Call Trace: [ 16.041868] [<ffffffff8101a095>] try_stack_unwind+0x175/0x190 [ 16.041872] [<ffffffff81018fe9>] dump_trace+0x69/0x3a0 [ 16.041874] [<ffffffff8101a0fb>] show_trace_log_lvl+0x4b/0x60 [ 16.041876] [<ffffffff8101942c>] show_stack_log_lvl+0x10c/0x180 [ 16.041878] [<ffffffff8101a195>] show_stack+0x25/0x50 [ 16.041881] [<ffffffff8137eb99>] dump_stack+0x4b/0x72 [ 16.041884] [<ffffffff8107c552>] warn_slowpath_common+0x82/0xc0 [ 16.041887] [<ffffffff8107c5dc>] warn_slowpath_fmt+0x4c/0x50 [ 16.041908] [<ffffffffa0478c5e>] intel_modeset_check_state+0x67e/0x870 [i915] [ 16.041937] [<ffffffffa0483fef>] intel_atomic_commit+0x4af/0x6d0 [i915] [ 16.041956] [<ffffffffa0331107>] drm_atomic_commit+0x37/0x60 [drm] [ 16.041964] [<ffffffffa03bda6f>] restore_fbdev_mode+0x22f/0x260 [drm_kms_helper] [ 16.041971] [<ffffffffa03bfc33>] drm_fb_helper_restore_fbdev_mode_unlocked+0x33/0x80 [drm_kms_helper] [ 16.041976] [<ffffffffa03bfcad>] drm_fb_helper_set_par+0x2d/0x50 [drm_kms_helper] [ 16.041998] [<ffffffffa049897a>] intel_fbdev_set_par+0x1a/0x60 [i915] [ 16.042002] [<ffffffff813ef8f0>] fbcon_init+0x570/0x5f0 [ 16.042006] [<ffffffff8147faaa>] visual_init+0xca/0x130 [ 16.042008] [<ffffffff814818e1>] do_bind_con_driver+0x1c1/0x3a0 [ 16.042011] [<ffffffff81481df9>] do_take_over_console+0x149/0x1a0 [ 16.042014] [<ffffffff813eb827>] do_fbcon_takeover+0x57/0xb0 [ 16.042015] [<ffffffff813f0368>] fbcon_event_notify+0x658/0x750 [ 16.042018] [<ffffffff8109afba>] notifier_call_chain+0x4a/0x70 [ 16.042021] [<ffffffff8109b337>] __blocking_notifier_call_chain+0x47/0x60 [ 16.042023] [<ffffffff8109b366>] blocking_notifier_call_chain+0x16/0x20 [ 16.042025] [<ffffffff813f5b0b>] fb_notifier_call_chain+0x1b/0x20 [ 16.042027] [<ffffffff813f7c50>] register_framebuffer+0x200/0x330 [ 16.042033] [<ffffffffa03bff2d>] drm_fb_helper_initial_config+0x25d/0x3f0 [drm_kms_helper] [ 16.042055] [<ffffffffa049948b>] intel_fbdev_initial_config+0x1b/0x20 [i915] [ 16.042057] [<ffffffff8109cab8>] async_run_entry_fn+0x48/0x150 [ 16.042060] [<ffffffff81094309>] process_one_work+0x159/0x470 [ 16.042063] [<ffffffff81094668>] worker_thread+0x48/0x4a0 [ 16.042065] [<ffffffff8109a2c9>] kthread+0xc9/0xe0 [ 16.042068] [<ffffffff816a9a8f>] ret_from_fork+0x3f/0x70 [ 16.043685] DWARF2 unwinder stuck at ret_from_fork+0x3f/0x70 [ 16.043686] Leftover inexact backtrace: [ 16.043688] [<ffffffff8109a200>] ? kthread_worker_fn+0x170/0x170 [ 16.043689] ---[ end trace f20d2d0e68470c43 ]--- [ 16.113027] Console: switching to colour frame buffer device 180x56 Entire dmesg from TW/kernel 4.6.3: http://fm.no-ip.com/Tmp/SUSE/Factory/dmsg-gx780-tw20160710-k4631.txt BTW, "DWARF2 unwinder stuck" is near the tail of the Call Trace that occurs on every 13.2, 42.1 and TW boot on Intel video host gx780. The search intent was to find some kind of clue to making these oopses stop happening, but I'm having no luck figuring out where to start. An old SUSE forum thread indicated a solution had been found once upon a time, but without clues to access useful additional info: https://forums.suse.com/showthread.php?1913-Kernel-error-DWARF2-unwinder-stu... -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On pátek 15. července 2016 4:17 Felix Miata wrote:
BTW, "DWARF2 unwinder stuck" is near the tail of the Call Trace that occurs on every 13.2, 42.1 and TW boot on Intel video host gx780. The search intent was to find some kind of clue to making these oopses stop happening, but I'm having no luck figuring out where to start.
The "unwinder stuck" message has nothing to do with the WARN_ON check you are hitting. Unwinder is the code that tries to present your kernel stack in a human readable form _after_ the problem happened. The message means it has trouble to follow the call chain. As it happened this high on the stack, it's not really a problem and it doesn't hinder investigating the bug at all. The interesting parts of the log would rather be
[ 16.041826] WARNING: CPU: 0 PID: 66 at ../drivers/gpu/drm/i915/intel_display.c:12802 intel_modeset_check_state+0x67e/0x870 [i915]() [ 16.041827] pipe state doesn't match!
and
[ 16.041908] [<ffffffffa0478c5e>] intel_modeset_check_state+0x67e/0x870 [i915] [ 16.041937] [<ffffffffa0483fef>] intel_atomic_commit+0x4af/0x6d0 [i915] [ 16.041956] [<ffffffffa0331107>] drm_atomic_commit+0x37/0x60 [drm] [ 16.041964] [<ffffffffa03bda6f>] restore_fbdev_mode+0x22f/0x260 [drm_kms_helper] [ 16.041971] [<ffffffffa03bfc33>] drm_fb_helper_restore_fbdev_mode_unlocked+0x33/0x80 [drm_kms_helper] [ 16.041976] [<ffffffffa03bfcad>] drm_fb_helper_set_par+0x2d/0x50 [drm_kms_helper] [ 16.041998] [<ffffffffa049897a>] intel_fbdev_set_par+0x1a/0x60 [i915] [ 16.042002] [<ffffffff813ef8f0>] fbcon_init+0x570/0x5f0
I would suggest to google for "i915 pipe state doesn't match". Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Michal Kubecek composed on 2016-07-15 10:42 (UTC+0200):
The interesting parts of the log would rather be
[ 16.041826] WARNING: CPU: 0 PID: 66 at ../drivers/gpu/drm/i915/intel_display.c:12802 intel_modeset_check_state+0x67e/0x870 [i915]() [ 16.041827] pipe state doesn't match!
and
[ 16.041908] [<ffffffffa0478c5e>] intel_modeset_check_state+0x67e/0x870 [i915] [ 16.041937] [<ffffffffa0483fef>] intel_atomic_commit+0x4af/0x6d0 [i915] [ 16.041956] [<ffffffffa0331107>] drm_atomic_commit+0x37/0x60 [drm] [ 16.041964] [<ffffffffa03bda6f>] restore_fbdev_mode+0x22f/0x260 [drm_kms_helper] [ 16.041971] [<ffffffffa03bfc33>] drm_fb_helper_restore_fbdev_mode_unlocked+0x33/0x80 [drm_kms_helper] [ 16.041976] [<ffffffffa03bfcad>] drm_fb_helper_set_par+0x2d/0x50 [drm_kms_helper] [ 16.041998] [<ffffffffa049897a>] intel_fbdev_set_par+0x1a/0x60 [i915] [ 16.042002] [<ffffffff813ef8f0>] fbcon_init+0x570/0x5f0
I would suggest to google for "i915 pipe state doesn't match".
No luck finding an apparently matching open bug on https://bugs.freedesktop.org/query.cgi so I started a thread on the intel-gfx mailing list: https://lists.freedesktop.org/archives/intel-gfx/2016-July/100711.html It also happens in Knoppix 7.6.1 / kernel 4.2.6. https://software.opensuse.org/search is broken, so I don't know how to find whatever BS repo might hold newer libdrm* that might be fixed. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2016-07-15 12:30, Felix Miata wrote:
https://software.opensuse.org/search is broken, so I don't know how to find whatever BS repo might hold newer libdrm* that might be fixed.
Try webpin instead. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
participants (3)
-
Carlos E. R.
-
Felix Miata
-
Michal Kubecek