Bug 96721 - i915: black screen with kms enabled on baytrail system
Summary: i915: black screen with kms enabled on baytrail system
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-29 11:04 UTC by sassmann
Modified: 2017-01-03 10:04 UTC (History)
2 users (show)

See Also:
i915 platform: BYT
i915 features: display/atomic


Attachments
dmesg-4.7-rc5-modeset-broken.txt (166.30 KB, text/plain)
2016-06-29 11:04 UTC, sassmann
no flags Details

Description sassmann 2016-06-29 11:04:30 UTC
Created attachment 124776 [details]
dmesg-4.7-rc5-modeset-broken.txt

When booting with nomodeset X gets displayed correctly, with KMS enabled the screen stays black. Fedora 24.

[root@wintab8 debug]# uname -m
i686
[root@wintab8 debug]# uname -r
4.7.0-rc5+

[    8.685785] [drm:pwm_setup_backlight [i915]] *ERROR* Failed to own the pwm chip
[...]
[   10.646434] WARNING: CPU: 3 PID: 96 at drivers/gpu/drm/i915/intel_display.c:13556 intel_atomic_commit+0x11e2/0x12a0 [i915]
[   10.646438] pipe A vblank wait timed out
[   10.646481] Modules linked in: mmc_block crc32c_intel i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm fjes video i2c_hid sdhci_acpi sdhci mmc_core
[   10.646494] CPU: 3 PID: 96 Comm: kworker/3:2 Not tainted 4.7.0-rc5+ #5
[   10.646499] Hardware name: AXDIA International GmbH Wintab Gen 8/Type2 - Board Product Name, BIOS AD890.1.02.022 09/25/2014
[   10.646545] Workqueue: events output_poll_execute [drm_kms_helper]
[   10.646568]  c0dd5967 ac3bedee 00000286 e4555d38 c0742137 e4555d7c f87810e4 e4555d68
[   10.646588]  c0461cba f87848b0 e4555d9c 00000060 f87810e4 000034f4 f870d4b2 000034f4
[   10.646607]  00000000 00000000 00000000 e4555d88 c0461d26 00000009 00000000 e4555d7c
[   10.646609] Call Trace:
[   10.646632]  [<c0742137>] dump_stack+0x58/0x81
[   10.646648]  [<c0461cba>] __warn+0xea/0x110
[   10.646899]  [<f870d4b2>] ? intel_atomic_commit+0x11e2/0x12a0 [i915]
[   10.646913]  [<c0461d26>] warn_slowpath_fmt+0x46/0x60
[   10.647162]  [<f870d4b2>] intel_atomic_commit+0x11e2/0x12a0 [i915]
[   10.647178]  [<c04a0df0>] ? prepare_to_wait_event+0xd0/0xd0
[   10.647283]  [<f84ee232>] drm_atomic_commit+0x32/0x60 [drm]
[   10.647331]  [<f84839e3>] restore_fbdev_mode+0x263/0x290 [drm_kms_helper]
[   10.647431]  [<f84ecd94>] ? drm_modeset_lock_all_ctx+0xa4/0xb0 [drm]
[   10.647480]  [<f8485c57>] drm_fb_helper_restore_fbdev_mode_unlocked+0x27/0x70 [drm_kms_helper]
[   10.647527]  [<f8485ccd>] drm_fb_helper_set_par+0x2d/0x60 [drm_kms_helper]
[   10.647574]  [<f8485bdc>] drm_fb_helper_hotplug_event+0xcc/0x120 [drm_kms_helper]
[   10.647823]  [<f872820a>] intel_fbdev_output_poll_changed+0x1a/0x20 [i915]
[   10.647863]  [<f8478701>] drm_kms_helper_hotplug_event+0x21/0x30 [drm_kms_helper]
[   10.647903]  [<f84788f8>] output_poll_execute+0x188/0x1c0 [drm_kms_helper]
[   10.647919]  [<c0478b5f>] process_one_work+0x13f/0x3a0
[   10.647932]  [<c0478df9>] worker_thread+0x39/0x460
[   10.647944]  [<c0478dc0>] ? process_one_work+0x3a0/0x3a0
[   10.647954]  [<c047de26>] kthread+0xa6/0xc0
[   10.647970]  [<c0b0cda2>] ret_from_kernel_thread+0xe/0x24
[   10.647980]  [<c047dd80>] ? kthread_worker_fn+0x140/0x140
[   10.648064] ---[ end trace 2526b8c9602ba815 ]---
Comment 1 Jani Nikula 2016-06-29 13:37:24 UTC
Seems like there are other problems there as well. What machine is this?

Did this ever work? If yes, can you bisect?
Comment 2 sassmann 2016-06-29 13:52:34 UTC
Yes, there's also a problem with hardware buttons and audio, separate issues though.
Modesetting never worked for me, until now I've always used nomodeset.

Intel Baytrail tablet PC.
# lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register [8086:0f00] (rev 0f)
00:02.0 VGA compatible controller [0300]: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0f)
00:14.0 USB controller [0c03]: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI [8086:0f35] (rev 0f)
00:1a.0 Encryption controller [1080]: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine [8086:0f18] (rev 0f)
00:1f.0 ISA bridge [0601]: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit [8086:0f1c] (rev 0f)

Let me know what other info you'd like to see.
Comment 3 Ville Syrjala 2016-12-22 15:15:42 UTC
Hans probably fixed the dead pipe with these:

commit 2b8208ac93be2783edc627fc02d9ca50cc479923
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Fri Dec 2 16:01:28 2016 +0100

    drm/i915/dsi: Fix swapping of MIPI_SEQ_DEASSERT_RESET / MIPI_SEQ_ASSERT_RESET

commit 721d484563e1a51ada760089c490cbc47e909756
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Fri Dec 2 15:29:04 2016 +0100

    drm/i915/dsi: Do not clear DPOUNIT_CLOCK_GATE_DISABLE from vlv_init_display_clock_gating

So please re-test with the latest drm-tip.
Comment 4 sassmann 2017-01-03 07:53:27 UTC
With 4.10-rc1 from drm-tip the problem goes away. Checking dmesg the only i915 error remaining is
[   14.962833] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
[   14.964726] [drm:pwm_setup_backlight [i915]] *ERROR* Failed to own the pwm chip
not sure if this is something to worry about?

However with that kernel the touchscreen no longer works because the hid device fails to probe
[   35.152943] i2c_hid: probe of i2c-FTSC1000:00 failed with error -121
but that's probably a separate issue.
Comment 5 Jani Nikula 2017-01-03 09:40:18 UTC
(In reply to sassmann from comment #4)
> With 4.10-rc1 from drm-tip the problem goes away. Checking dmesg the only
> i915 error remaining is
> [   14.962833] i915 0000:00:02.0: vgaarb: changed VGA decodes:
> olddecodes=io+mem,decodes=io+mem:owns=io+mem
> [   14.964726] [drm:pwm_setup_backlight [i915]] *ERROR* Failed to own the
> pwm chip
> not sure if this is something to worry about?

Related to backlight control. You may need to worry about it, but it's another bug. See bug 96571.

> However with that kernel the touchscreen no longer works because the hid
> device fails to probe
> [   35.152943] i2c_hid: probe of i2c-FTSC1000:00 failed with error -121
> but that's probably a separate issue.

Unrelated to graphics.

Sorry it's not all rosy, but I'm closing this particular bug fixed. Thanks for the report, and thanks to Hans for the fixes.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.