On Fri, 25 Apr 2014, Pavel Machek wrote:
>> On Thu, Apr 24, 2014 at 09:40:38PM +0200, Pavel Machek wrote:
>> > Hi!
>> >
>> > > And if you can indeed reliably reproduce this a bisect could be really
>> > > useful.
>> >
>> > And we have a winner here :-)
>> >
>> > Ok, it was not as painfull as
On Fri, 25 Apr 2014, Pavel Machek wrote:
> > > And we have a winner here :-)
> > >
> > > Ok, it was not as painfull as I feared.
> > >
> > > It does not revert cleanly, but doing it by hand was not that bad.
> >
> > Oh my. That is bizarre, can you check whether you have
> >
> > commit
> On Thu, Apr 24, 2014 at 09:40:38PM +0200, Pavel Machek wrote:
> > Hi!
> >
> > > And if you can indeed reliably reproduce this a bisect could be really
> > > useful.
> >
> > And we have a winner here :-)
> >
> > Ok, it was not as painfull as I feared.
> >
> > It does not revert cleanly, but
Hi!
> > > And if you can indeed reliably reproduce this a bisect could be really
> > > useful.
> >
> > And we have a winner here :-)
> >
> > Ok, it was not as painfull as I feared.
> >
> > It does not revert cleanly, but doing it by hand was not that bad.
>
> Oh my. That is bizarre, can you
Hi!
> And if you can indeed reliably reproduce this a bisect could be really useful.
And we have a winner here :-)
Ok, it was not as painfull as I feared.
It does not revert cleanly, but doing it by hand was not that bad.
Best regards,
Hi!
> And if you can indeed reliably reproduce this a bisect could be
> really useful
It seems reliable, yes. So far I got:
Pavel
git bisect start
# good: [455c6fdbd219161bd09b1165f11699d6d73de11c] Linux 3.14
git bisect good
On Thu, Apr 24, 2014 at 09:40:38PM +0200, Pavel Machek wrote:
> Hi!
>
> > And if you can indeed reliably reproduce this a bisect could be really
> > useful.
>
> And we have a winner here :-)
>
> Ok, it was not as painfull as I feared.
>
> It does not revert cleanly, but doing it by hand was
On Thu, Apr 24, 2014 at 03:43:45PM +0200, Pavel Machek wrote:
> Hi!
>
> > Like Chris said please test latest drm-intel-nighlty from
> > http://cgit.freedesktop.org/drm-intel to make sure that the recently
> > merged mitigation measures work properly. But those won't get your gpu
> > back, only
On Thu, 24 Apr 2014, Pavel Machek wrote:
> > > [drm:init_ring_common] *ERROR* render ring initialization failed ctl
> > > 0001f001 head 2034 tail start 0012f000
> > >
> > > Jiri has been seeing a similar issue creep in during resume, but it is
> > > not reliable enough to bisect. Is
Hi!
> Like Chris said please test latest drm-intel-nighlty from
> http://cgit.freedesktop.org/drm-intel to make sure that the recently
> merged mitigation measures work properly. But those won't get your gpu
> back, only the display and it's only for 3.16. We're still hunting a
What does it
On Thu 2014-04-24 08:03:04, Daniel Vetter wrote:
> On Thu, Apr 24, 2014 at 7:50 AM, Chris Wilson
> wrote:
> > That says that i915.ko failed to initialise the GPU (or rather the GPU
> > wasn't responding) and bailed during module load. The key line here is
> >
> > [drm:init_ring_common] *ERROR*
On Thu, 24 Apr 2014, Pavel Machek wrote:
> > That says that i915.ko failed to initialise the GPU (or rather the GPU
> > wasn't responding) and bailed during module load. The key line here is
>
> > [drm:init_ring_common] *ERROR* render ring initialization failed ctl
> > 0001f001 head 2034
Hi!
> > > > After update to 3.15-rc2, only top 20% of screen works on X.
> > > >
> > > > 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset
> > > > Integrated Graphics Controller (rev 03)
> > > >
> > > > 00:02.1 Display controller: Intel Corporation 4 Series Chipset
> > > >
On Thu, Apr 24, 2014 at 7:50 AM, Chris Wilson
wrote:
> That says that i915.ko failed to initialise the GPU (or rather the GPU
> wasn't responding) and bailed during module load. The key line here is
>
> [drm:init_ring_common] *ERROR* render ring initialization failed ctl
> 0001f001 head 2034
On Thu, Apr 24, 2014 at 12:09:52AM +0200, Pavel Machek wrote:
> Hi!
>
> > > After update to 3.15-rc2, only top 20% of screen works on X.
> > >
> > > 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset
> > > Integrated Graphics Controller (rev 03)
> > >
> > > 00:02.1 Display
Hi!
> > After update to 3.15-rc2, only top 20% of screen works on X.
> >
> > 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset
> > Integrated Graphics Controller (rev 03)
> >
> > 00:02.1 Display controller: Intel Corporation 4 Series Chipset
> > Integrated Graphics Controller
On Wed 2014-04-23 23:09:45, Daniel Vetter wrote:
> On Wed, Apr 23, 2014 at 10:22 PM, Pavel Machek wrote:
> > After update to 3.15-rc2, only top 20% of screen works on X.
> >
> > 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset
> > Integrated Graphics Controller (rev 03)
> >
>
On Wed, Apr 23, 2014 at 10:22 PM, Pavel Machek wrote:
> After update to 3.15-rc2, only top 20% of screen works on X.
>
> 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset
> Integrated Graphics Controller (rev 03)
>
> 00:02.1 Display controller: Intel Corporation 4 Series
Hi!
After update to 3.15-rc2, only top 20% of screen works on X.
00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset
Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation 4 Series Chipset
Integrated Graphics Controller (rev 03)
19 matches
Mail list logo
