Bug 1592214 - [abrt] finish_wait: WARNING: CPU: 0 PID: 103 at drivers/gpu/drm/drm_vblank.c:1073 drm_wait_one_vblank+0x166/0x180 [drm]
Summary: [abrt] finish_wait: WARNING: CPU: 0 PID: 103 at drivers/gpu/drm/drm_vblank.c:...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 28
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:688e4f2324ef14ae53f79ac29e6...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-18 08:06 UTC by Justin Clift
Modified: 2019-02-21 21:12 UTC (History)
21 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-02-21 21:12:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: dmesg (93.71 KB, text/plain)
2018-06-18 08:06 UTC, Justin Clift
no flags Details

Description Justin Clift 2018-06-18 08:06:01 UTC
Description of problem:
Interestingly, this crash happens on every boot now on this ancient MacBook.

Abrt pops up a notification about it after logging in (Fedora 28 using Xfce) and the desktop has loaded.

No other interaction with the system has happened by this time, so it seems to be something triggered during the boot process.

The system itself *appears* to work ok after getting past the abrt notification.  Eg graphical windowing works, applications work, etc.

Additional info:
reporter:       libreport-2.9.5
WARNING: CPU: 0 PID: 103 at drivers/gpu/drm/drm_vblank.c:1073 drm_wait_one_vblank+0x166/0x180 [drm]
Modules linked in: i915 firewire_ohci ata_generic pata_acpi firewire_core crc_itu_t i2c_algo_bit drm_kms_helper sky2 drm video hid_appleir
CPU: 0 PID: 103 Comm: kworker/u4:4 Not tainted 4.16.15-300.fc28.x86_64 #1
Hardware name: Apple Inc. MacBook3,1/Mac-F22788C8, BIOS     MB31.88Z.008E.B02.0803051832 03/05/08
Workqueue: events_unbound async_run_entry_fn
RIP: 0010:drm_wait_one_vblank+0x166/0x180 [drm]
RSP: 0018:ffffb34200a07ac8 EFLAGS: 00010282
RAX: 0000000000000000 RBX: ffff887574a30000 RCX: 0000000000000006
RDX: 0000000000000007 RSI: 0000000000000092 RDI: ffff88757fc16930
RBP: 0000000000000000 R08: 0000000000000030 R09: 00000000000003ec
R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000000
R13: 0000000001000001 R14: ffff88757561cc08 R15: ffff887575ef4800
FS:  0000000000000000(0000) GS:ffff88757fc00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb428540020 CR3: 000000007d20a000 CR4: 00000000000006f0
Call Trace:
 ? finish_wait+0x80/0x80
 intel_get_load_detect_pipe+0x395/0x3d0 [i915]
 intel_tv_detect+0x134/0x4d0 [i915]
 drm_helper_probe_single_connector_modes+0xda/0x6d0 [drm_kms_helper]
 drm_setup_crtcs+0x148/0xaa0 [drm_kms_helper]
 ? sched_clock+0x5/0x10
 ? sched_clock_local+0x12/0x80
 __drm_fb_helper_initial_config_and_unlock+0x3d/0x420 [drm_kms_helper]
 ? _cond_resched+0x15/0x30
 intel_fbdev_initial_config+0x14/0x30 [i915]
 async_run_entry_fn+0x39/0x160
 process_one_work+0x187/0x340
 worker_thread+0x2e/0x380
 ? pwq_unbound_release_workfn+0xd0/0xd0
 kthread+0x112/0x130
 ? kthread_create_worker_on_cpu+0x70/0x70
 ret_from_fork+0x35/0x40
Code: f8 cd 0f 0b e9 2d ff ff ff 48 89 e6 4c 89 f7 e8 d1 d6 fc cd 45 85 e4 0f 85 0f ff ff ff 89 ee 48 c7 c7 40 e0 13 c0 e8 b4 93 f8 cd <0f> 0b e9 fa fe ff ff e8 3e 91 f8 cd 0f 1f 40 00 66 2e 0f 1f 84

Comment 1 Justin Clift 2018-06-18 08:06:17 UTC
Created attachment 1452545 [details]
File: dmesg

Comment 2 serenade 2018-07-23 12:11:07 UTC
Description of problem:
I don't know. I believe that I've installed the modules tto fast. And the problem repeat continuosly during the session, i don't know. I think also I've intalled the software too fast due to an fatal error in fedora system, and as I have to continue my work, then ....

Version-Release number of selected component:
kernel-core-4.17.6-200.fc28

Additional info:
reporter:       libreport-2.9.5
cmdline:        BOOT_IMAGE=/vmlinuz-4.17.6-200.fc28.x86_64 root=UUID=88788f7f-4bcf-4847-8adc-98bf44cfa846 ro rootflags=subvol=root resume=UUID=96ea938e-b0b6-4900-b644-537652e7718c rhgb quiet LANG=es_ES.UTF-8
crash_function: finish_wait
kernel:         4.17.6-200.fc28.x86_64
runlevel:       N 5
type:           Kerneloops

Truncated backtrace:
WARNING: CPU: 0 PID: 104 at drivers/gpu/drm/drm_vblank.c:1084 drm_wait_one_vblank+0x166/0x180 [drm]
Modules linked in: btrfs xor zstd_decompress zstd_compress xxhash raid6_pq libcrc32c i915 i2c_algo_bit drm_kms_helper drm serio_raw uas 8139too usb_storage ata_generic 8139cp pata_acpi mii video
CPU: 0 PID: 104 Comm: kworker/u4:5 Not tainted 4.17.6-200.fc28.x86_64 #1
Hardware name: Hewlett-Packard Compaq Presario C700 Notebook PC/30D9, BIOS F.35 03/29/2010
Workqueue: events_unbound async_run_entry_fn
RIP: 0010:drm_wait_one_vblank+0x166/0x180 [drm]
RSP: 0018:ffffa4e440d57ac0 EFLAGS: 00010282
RAX: 0000000000000000 RBX: ffff96e936868000 RCX: 0000000000000006
RDX: 0000000000000007 RSI: 0000000000000086 RDI: ffff96e93f216930
RBP: 0000000000000000 R08: 0000000000000030 R09: 000000000000028d
R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000000
R13: 0000000001000001 R14: ffff96e8b6996c08 R15: ffff96e8b69ae400
FS:  0000000000000000(0000) GS:ffff96e93f200000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055a463e2fab8 CR3: 000000009520a000 CR4: 00000000000006f0
Call Trace:
 ? finish_wait+0x80/0x80
 intel_get_load_detect_pipe+0x370/0x390 [i915]
 intel_tv_detect+0x12d/0x4a0 [i915]
 drm_helper_probe_single_connector_modes+0xd3/0x6b0 [drm_kms_helper]
 drm_setup_crtcs+0x146/0xa20 [drm_kms_helper]
 ? set_next_entity+0x96/0x1c0
 __drm_fb_helper_initial_config_and_unlock+0x3d/0x420 [drm_kms_helper]
 ? dequeue_task_fair+0x3e/0x6d0
 ? _cond_resched+0x15/0x30
 intel_fbdev_initial_config+0x14/0x30 [i915]
 async_run_entry_fn+0x39/0x160
 process_one_work+0x187/0x340
 worker_thread+0x2e/0x380
 ? pwq_unbound_release_workfn+0xd0/0xd0
 kthread+0x112/0x130
 ? kthread_create_worker_on_cpu+0x70/0x70
 ret_from_fork+0x35/0x40
Code: e3 c5 0f 0b e9 2d ff ff ff 48 89 e6 4c 89 f7 e8 41 d3 e7 c5 45 85 e4 0f 85 0f ff ff ff 89 ee 48 c7 c7 40 63 29 c0 e8 d4 4c e3 c5 <0f> 0b e9 fa fe ff ff e8 5e 4a e3 c5 0f 1f 40 00 66 2e 0f 1f 84

Comment 3 Laura Abbott 2018-10-01 21:33:45 UTC
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs.
 
Fedora 28 has now been rebased to 4.18.10-300.fc28.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 29, and are still experiencing this issue, please change the version to Fedora 29.
 
If you experience different issues, please open a new bug report for those.

Comment 4 Antonios 2018-10-13 23:00:23 UTC
Description of problem:
Just see this message every time my computer boots

Version-Release number of selected component:
kernel-core-4.18.12-200.fc28

Additional info:
reporter:       libreport-2.9.5
cmdline:        BOOT_IMAGE=/vmlinuz-4.18.12-200.fc28.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap rhgb quiet LANG=en_US.UTF-8
crash_function: finish_wait
kernel:         4.18.12-200.fc28.x86_64
runlevel:       unknown
type:           Kerneloops

Truncated backtrace:
WARNING: CPU: 0 PID: 108 at drivers/gpu/drm/drm_vblank.c:1084 drm_wait_one_vblank+0x161/0x170 [drm]
Modules linked in: pata_pcmcia mmc_block i915 sdhci_pci cqhci sdhci e1000e mmc_core serio_raw firewire_ohci i2c_algo_bit drm_kms_helper firewire_core crc_itu_t yenta_socket drm ata_generic pata_acpi video
CPU: 0 PID: 108 Comm: kworker/u4:3 Not tainted 4.18.12-200.fc28.x86_64 #1
Hardware name: Hewlett-Packard HP Compaq 6910p/30BE, BIOS 68MCU Ver. F.16 08/18/2008
Workqueue: events_unbound async_run_entry_fn
RIP: 0010:drm_wait_one_vblank+0x161/0x170 [drm]
Code: da 0f 0b e9 32 ff ff ff 48 89 e6 4c 89 f7 e8 e6 84 d5 da 45 85 e4 0f 85 14 ff ff ff 89 ee 48 c7 c7 48 fa 3b c0 e8 89 f6 d0 da <0f> 0b e9 ff fe ff ff e8 13 f4 d0 da 0f 1f 00 66 66 66 66 90 8b b7 
RSP: 0018:ffffbb7a40defab0 EFLAGS: 00010282
RAX: 0000000000000000 RBX: ffffa0a12fd38000 RCX: 0000000000000006
RDX: 0000000000000007 RSI: 0000000000000082 RDI: ffffa0a13bc16930
RBP: 0000000000000000 R08: 0000000000000030 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000000
R13: 0000000001000001 R14: ffffa0a131b1c008 R15: ffffa0a13198e000
FS:  0000000000000000(0000) GS:ffffa0a13bc00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f5ae0469000 CR3: 0000000131e82000 CR4: 00000000000006f0
Call Trace:
 ? finish_wait+0x80/0x80
 intel_get_load_detect_pipe+0x381/0x3a0 [i915]
 intel_tv_detect+0x12d/0x4a0 [i915]
 ? gmbus_xfer+0x5a/0xa0 [i915]
 drm_helper_probe_single_connector_modes+0xd3/0x6b0 [drm_kms_helper]
 drm_setup_crtcs+0x151/0xa30 [drm_kms_helper]
 ? __switch_to_asm+0x40/0x70
 ? __switch_to_asm+0x34/0x70
 ? __switch_to_asm+0x40/0x70
 ? __switch_to_asm+0x34/0x70
 ? __switch_to_asm+0x40/0x70
 ? __switch_to_asm+0x34/0x70
 __drm_fb_helper_initial_config_and_unlock+0x3d/0x420 [drm_kms_helper]
 ? __switch_to_asm+0x34/0x70
 ? _cond_resched+0x15/0x30
 intel_fbdev_initial_config+0x14/0x30 [i915]
 async_run_entry_fn+0x39/0x160
 process_one_work+0x1a1/0x350
 worker_thread+0x30/0x380
 ? pwq_unbound_release_workfn+0xd0/0xd0
 kthread+0x112/0x130
 ? kthread_create_worker_on_cpu+0x70/0x70
 ret_from_fork+0x35/0x40

Comment 5 Justin Clift 2018-10-15 12:14:24 UTC
As per Antonios's comment above, this is still happening with the newer kernels.  eg kernel-core-4.18.12-200.fc28

Personally I've changed laptops, so this issue isn't something I'm able to diagnose personally any more. ;)

Comment 6 Justin M. Forbes 2019-01-29 16:27:00 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs.

Fedora 28 has now been rebased to 4.20.5-100.fc28.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 29, and are still experiencing this issue, please change the version to Fedora 29.

If you experience different issues, please open a new bug report for those.

Comment 7 Justin M. Forbes 2019-02-21 21:12:39 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.


Note You need to log in before you can comment on or make changes to this bug.