On May 06 Daniel Vetter wrote:
> On Thu, May 05, 2016 at 10:45:31PM +0200, Stefan Richter wrote:
[...]
> > Subtest fbc-1p-primscrn-spr-indfb-fullscreen: FAIL (5.876s)
>
> This one failed in both runs. Can you please retest with just that using
>
> # kms_frontbuffer_tracking --run-subtest fbc-1p
On May 08 Stefan Richter wrote:
> On May 05 Zanoni, Paulo R wrote:
> > If you don't want to keep carrying a manual revert, you can just boot
> > with i915.enable_fbc=0 for now (or write a /etc/modprobe.d file). Also,
> > it would be good to know in case you still somehow see the machine
> > hangs e
On May 05 Zanoni, Paulo R wrote:
> If you don't want to keep carrying a manual revert, you can just boot
> with i915.enable_fbc=0 for now (or write a /etc/modprobe.d file). Also,
> it would be good to know in case you still somehow see the machine
> hangs even with FBC disabled.
As expected, i915.
On Thu, May 05, 2016 at 10:45:31PM +0200, Stefan Richter wrote:
> On May 05 Stefan Richter wrote:
> > Quoting the changelog of the commit:
> [...]
> > - Download intel-gpu-tools, compile it, and run:
> >$ sudo ./tests/kms_frontbuffer_tracking --run-subtest '*fbc-*' 2>&1
> > | tee fbc.
On May 05 Daniel Vetter wrote:
> Hm, if it's watermarks then testing with latest drm-intel-nightly would be
> interesting. We finally managed to land atomic watermark updates (should
> all be there in 4.7 too):
>
> https://cgit.freedesktop.org/drm-intel
I will see if I can test this sometime soon
On May 05 Zanoni, Paulo R wrote:
> Em Qui, 2016-05-05 Ã s 19:45 +0200, Stefan Richter escreveu:
> > Â Â Â Â Oh, and in case you - the person reading this commit message - found
> > Â Â Â Â this commit through git bisect, please do the following:
> > Â Â Â Â Â - Check your dmesg and see if there are
Em Sex, 2016-05-06 Ã s 00:54 +0200, Stefan Richter escreveu:
> On May 05 Zanoni, Paulo R wrote:
> >
> > Em Qui, 2016-05-05 Ã s 19:45 +0200, Stefan Richter escreveu:
> > >
> > > Â Â Â Â Oh, and in case you - the person reading this commit message
> > > - found
> > > Â Â Â Â this commit through git
On May 05 Stefan Richter wrote:
> Quoting the changelog of the commit:
[...]
> - Download intel-gpu-tools, compile it, and run:
>$ sudo ./tests/kms_frontbuffer_tracking --run-subtest '*fbc-*' 2>&1 |
> tee fbc.txt
>Then send us the fbc.txt file, especially if you get a failure.
On Thu, May 05, 2016 at 06:50:14PM +, Zanoni, Paulo R wrote:
> Em Qui, 2016-05-05 Ã s 19:45 +0200, Stefan Richter escreveu:
> > On Apr 30 Stefan Richter wrote:
> > >
> > > On Apr 29 Stefan Richter wrote:
> > > >
> > > > On Apr 26 Stefan Richter wrote:Â Â
> > > > >
> > > > > v4.6-rc solidly
On May 05 Stefan Richter wrote:
> Quoting the changelog of the commit:
[...]
> - Boot with drm.debug=0xe, reproduce the problem, then send us the
>dmesg file.
>
> I can try this, but I am skeptical about getting any useful kernel
> messages from before the hang.
I booted 4.6-rc5 with
On Apr 30 Stefan Richter wrote:
> On Apr 29 Stefan Richter wrote:
> > On Apr 26 Stefan Richter wrote:
> > > v4.6-rc solidly hangs after a short while after boot, login to X11, and
> > > doing nothing much remarkable on the just brought up X desktop.
> > >
> > > Hardware: x86-64, E3-1245 v3 (Hasw
Em Qui, 2016-05-05 Ã s 19:45 +0200, Stefan Richter escreveu:
> On Apr 30 Stefan Richter wrote:
> >
> > On Apr 29 Stefan Richter wrote:
> > >
> > > On Apr 26 Stefan Richter wrote:Â Â
> > > >
> > > > v4.6-rc solidly hangs after a short while after boot, login to
> > > > X11, and
> > > > doing not
12 matches
Mail list logo
