[Intel-gfx] i915 ERRORs and WARN_ON()s

Hi, > I fully understand your frustration with all this - you have a bug and > it's annoying and creating bugzilla accounts all over the internet is > indeed not a good way to do things. Unfortunately bugzilla is the > standard, and we don't have the manpower to write our own, nor do the > freedes

[Intel-gfx] i915 ERRORs and WARN_ON()s

Hi, > > Hu? I don't quite get it. Communicating via email is an unscalable > > inconvenience? So, if I asked you to create an account with my todo tracker > > instead, would that be more scalable and convenient? Using everyone's > > software of choice instead of my own most certainly is neither sc

[Intel-gfx] i915 ERRORs and WARN_ON()s

Hi, > The Bugzilla at https://bugs.freedesktop.org is our tool of choice for > tracking bugs in drm/i915. It's your choice to not create an account > there, but please, don't expect us to work as a proxy between you and > bugzilla either. It's a much bigger and unscalable inconvenience for us > th

[Intel-gfx] i951 ERRORs and WARN_ON()s (was: blank screen on boot with i915/DRM_FBDEV_EMULATION)

Hi, > Florian, if you're using drm-intel-nigthly submit a bug at > https://bugs.freedesktop.org/enter_bug.cgi?product=DRI, with DRM/intel > as component. This way we can track some kind of progress/regress. The FIFO Gee ... is there any way without "creating an account"? Having to create accounts

i951 Xv playback uneven

Hi, with the drm-intel-nightly I am currently running, I am also seeing some quite noticable stuttering in Xv playback. It's particularly obvious in stuff like rolling credits. It's not directly a performance problem, as the effect can be seen even in "stop motion" (i.e., frame by frame) playback:

i951 ERRORs and WARN_ON()s (was: blank screen on boot with i915/DRM_FBDEV_EMULATION)

Hi, > > We've fixed piles of those in recent kernels, but didn't backport all the > > fixes (since usually it's a silent failure, but it can correlate with > > black screens). > > Not quite completely, it seems ... > > I have built drm-intel-nightly (f261f82359), and I'm getting this: [...] pin

i951 ERRORs and WARN_ON()s (was: blank screen on boot with i915/DRM_FBDEV_EMULATION)

Hi, > We've fixed piles of those in recent kernels, but didn't backport all the > fixes (since usually it's a silent failure, but it can correlate with > black screens). Not quite completely, it seems ... I have built drm-intel-nightly (f261f82359), and I'm getting this: | [ 15.855007] [drm:i

blank screen on boot with i915/DRM_FBDEV_EMULATION

Hi, > FBDEV_EMULATION vs. I915_FBDEV is probably a read herring, more likely is > that for some odd reason the very first modeset fails. Once X has > resurrect the screen, can you then switch to fbcon? Also please check in > /sys/class/vtconsole whether the fbdev driver is loaded and bound (check

blank screen on boot with i915/DRM_FBDEV_EMULATION

Hi, I just compiled a new kernel version 4.4.5, replacing a previous 4.1.9 for my thinkpad x40, which replaced CONFIG_DRM_I915_FBDEV with CONFIG_DRM_FBDEV_EMULATION--now, when the i915 and fbcon modules get loaded during boot, the screen goes blank (with backlight still on), which didn't happen wi

[PATCH] drm/savage: re-add busmaster enable, regression fix

466e69b8b03b8c1987367912782bc12988ad8794 dropped busmaster enable from the global drm code and moved it to the individual drivers, but missed the savage driver. So, this re-adds busmaster enable to the savage driver, fixing the regression. Signed-off-by: Florian Zumbiehl diff --git a/drivers

[PATCH] drm/savage: re-add busmaster enable, regression fix

466e69b8b03b8c1987367912782bc12988ad8794 dropped busmaster enable from the global drm code and moved it to the individual drivers, but missed the savage driver. So, this re-adds busmaster enable to the savage driver, fixing the regression. Signed-off-by: Florian Zumbiehl diff --git a/drivers