Summary: | [SNB] BUG drm_framebuffer_free_bug | ||||||
---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | mikhail.v.gavrilov | ||||
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
Severity: | normal | ||||||
Priority: | medium | CC: | intel-gfx-bugs, matthew.d.roper, przanoni | ||||
Version: | XOrg git | ||||||
Hardware: | Other | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
i915 platform: | i915 features: | ||||||
Attachments: |
|
Description
mikhail.v.gavrilov
2015-03-20 13:49:18 UTC
Hi What are the steps to reproduce this problem? How reproducible is the bug? Which platform are you using? Please provide the output of "lspci -nn". Is there any way for you to provide us a complete dmesg? Even better if you are able to boot with drm.debug=0xe. When did this start happening? Are you able to bisect this bug? Bisecting is a _really_ good way to help fixing the bug, and since you're running RC Kernels, maybe the bisect interval would be small. Thanks, Paulo > What are the steps to reproduce this problem? How reproducible is the bug?
I turned off the computer and it happened the first time.
# lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:0100] (rev 09)
00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09)
00:16.0 Communication controller [0780]: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04)
00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 05)
00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller [8086:1c20] (rev 05)
00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 [8086:1c10] (rev b5)
00:1c.1 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 [8086:1c12] (rev b5)
00:1d.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 [8086:1c26] (rev 05)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev a5)
00:1f.0 ISA bridge [0601]: Intel Corporation H67 Express Chipset Family LPC Controller [8086:1c4a] (rev 05)
00:1f.2 SATA controller [0106]: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller [8086:1c02] (rev 05)
00:1f.3 SMBus [0c05]: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller [8086:1c22] (rev 05)
01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06)
02:00.0 USB controller [0c03]: NEC Corporation uPD720200 USB 3.0 Host Controller [1033:0194] (rev 04)
Created attachment 114497 [details]
system log
This sounds like it might be fixed by: commit 220dd2bc43e23f72fcdf6cc6ced3107c7023f123 Author: Daniel Vetter <daniel.vetter@ffwll.ch> Date: Fri Feb 27 12:58:13 2015 +0100 drm: Fixup racy refcounting in plane_force_disable which we had in -next, but were missing in -fixes until this morning. Can you try cherry-picking that commit and see if it solves your problem? I have been using kernel 4-rc4 and faced this problem also. I am cherry picking this patch to see if the problem is reproducible. (In reply to Matt Roper from comment #4) > This sounds like it might be fixed by: > > commit 220dd2bc43e23f72fcdf6cc6ced3107c7023f123 > Author: Daniel Vetter <daniel.vetter@ffwll.ch> > Date: Fri Feb 27 12:58:13 2015 +0100 > > drm: Fixup racy refcounting in plane_force_disable > > which we had in -next, but were missing in -fixes until this morning. Can > you try cherry-picking that commit and see if it solves your problem? I can confirm that this commit fixes the problem, cherry-picked it to v3.19.something, tested on a Lenovo X250. And the commit is part of v4.0 (since rc5?), so I think that this bug can be closed. (In reply to Daniel Martin from comment #6) > I can confirm that this commit fixes the problem, cherry-picked it to > v3.19.something, tested on a Lenovo X250. > And the commit is part of v4.0 (since rc5?), so I think that this bug can be > closed. It's also cc: stable so should show up in earlier releases eventually too. Thanks for the report and testing, closing. |
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.