On Mon, 16 Feb 2015, Paul Bolle pebo...@tiscali.nl wrote:
I still see this on v3.19. I booted with drm.debug=0x4. The almost 2K
lines in dmesg containing either [drm or this WARNING are pasted
below. I really know nothing about all this, but I do note that only the
WARNINGS are preceded by:
On Mon, 23 Feb 2015, Jani Nikula jani.nik...@linux.intel.com wrote:
On Mon, 16 Feb 2015, Paul Bolle pebo...@tiscali.nl wrote:
I still see this on v3.19. I booted with drm.debug=0x4. The almost 2K
lines in dmesg containing either [drm or this WARNING are pasted
below. I really know nothing
On Wed, Feb 04, 2015 at 01:32:14PM +0100, Paul Bolle wrote:
Andrey Skvortsov schreef op zo 01-02-2015 om 00:16 [+0300]:
this warning exist in v3.19-rc6 and does not in v3.18. Bisection
points to the commit 51e31d49c890552 drm/i915: Use generic vblank wait.
I have two machines with
Andrey Skvortsov schreef op zo 01-02-2015 om 00:16 [+0300]:
this warning exist in v3.19-rc6 and does not in v3.18. Bisection
points to the commit 51e31d49c890552 drm/i915: Use generic vblank wait.
I have two machines with integrated Intel graphics and the problem
happens only on the old one
Hi,
this warning exist in v3.19-rc6 and does not in v3.18. Bisection
points to the commit 51e31d49c890552 drm/i915: Use generic vblank wait.
I have two machines with integrated Intel graphics and the problem
happens only on the old one with GM965 chipset and X3100 integrated graphics.
backtrace
