Bug 94571 - Random stack traces on Ironlake since 3.19.1
Summary: Random stack traces on Ironlake since 3.19.1
Status: RESOLVED MOVED
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - Intel) (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: intel-gfx-bugs@lists.freedesktop.org
URL: https://bugs.freedesktop.org/show_bug...
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-09 01:57 UTC by Coacher
Modified: 2015-03-10 08:10 UTC (History)
1 user (show)

See Also:
Kernel Version: 3.19.1
Subsystem:
Regression: No
Bisected commit-id:


Attachments
lspci -k -vvv (23.37 KB, application/octet-stream)
2015-03-09 01:57 UTC, Coacher
Details
dmesg output with stack traces examples (87.53 KB, text/plain)
2015-03-09 01:58 UTC, Coacher
Details

Description Coacher 2015-03-09 01:57:13 UTC
Created attachment 169921 [details]
lspci -k -vvv

Hello.

After kernel upgrade from 3.18.7 to 3.19.1 I occasionally get stack traces related to drm_wait_one_vblank() in my dmesg. I haven't figured out the exact conditions for these traces to appear, but they tend to appear more often while browsing in Firefox or running VirtualBox. I had no such problems on 3.18.7. When these traces appear everything seems to run as usual, except for VirtualBox, which becomes very very slow.

My OS is Gentoo amd64 with vanilla kernel 3.19.1. If you need any additional info I am ready to provide it.
Comment 1 Coacher 2015-03-09 01:58:19 UTC
Created attachment 169931 [details]
dmesg output with stack traces examples
Comment 2 Jani Nikula 2015-03-09 09:06:05 UTC
Can't dupe a bug on another bugzilla, but it's this one:
https://bugs.freedesktop.org/show_bug.cgi?id=89108

Hopefully will be backported to v3.19.y.
Comment 3 Coacher 2015-03-10 08:10:56 UTC
(In reply to Jani Nikula from comment #2)
> Can't dupe a bug on another bugzilla, but it's this one:
> https://bugs.freedesktop.org/show_bug.cgi?id=89108
> 
> Hopefully will be backported to v3.19.y.

Thank you very much for your quick and useful response.

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