On 2012-05-04 10:20 +0100, Dave Airlie wrote:
> >>
> >> FWIW, for me EDID failure on new kernels is 100% reproducible, and there
> >> are no such checksum errors in the log. ?It's just missing.
> >>
> >> > Just a crazy thought, but didn't we change some timings related to
> >> > EDID retrieval? To
On Wed, 2012-05-02 at 21:31 +1000, Ben Skeggs wrote:
> On Wed, 2012-05-02 at 09:54 +0200, Jean Delvare wrote:
> > Hi Luca, Maarten,
> >
> > On Monday 30 April 2012 01:01:30 pm Luca Tettamanti wrote:
> > > On Mon, Apr 30, 2012 at 11:07 AM, Maarten Maathuis > > gmail.com> wrote:
> > > > On Mon,
>>
>> FWIW, for me EDID failure on new kernels is 100% reproducible, and there
>> are no such checksum errors in the log. ?It's just missing.
>>
>> > Just a crazy thought, but didn't we change some timings related to
>> > EDID retrieval? To make it faster.
>>
>> OK, this time bisecting started off
FWIW, for me EDID failure on new kernels is 100% reproducible, and there
are no such checksum errors in the log. It's just missing.
Just a crazy thought, but didn't we change some timings related to
EDID retrieval? To make it faster.
OK, this time bisecting started off relatively
On Wed, 2012-05-02 at 21:31 +1000, Ben Skeggs wrote:
On Wed, 2012-05-02 at 09:54 +0200, Jean Delvare wrote:
Hi Luca, Maarten,
On Monday 30 April 2012 01:01:30 pm Luca Tettamanti wrote:
On Mon, Apr 30, 2012 at 11:07 AM, Maarten Maathuis madman2...@gmail.com
wrote:
On Mon, Apr 30,
On Wed, 2012-05-02 at 09:54 +0200, Jean Delvare wrote:
> Hi Luca, Maarten,
>
> On Monday 30 April 2012 01:01:30 pm Luca Tettamanti wrote:
> > On Mon, Apr 30, 2012 at 11:07 AM, Maarten Maathuis > gmail.com> wrote:
> > > On Mon, Apr 30, 2012 at 12:37 AM, Dmitry Torokhov
> > >
> > > wrote:
> > >>
Hi Luca, Maarten,
On Monday 30 April 2012 01:01:30 pm Luca Tettamanti wrote:
> On Mon, Apr 30, 2012 at 11:07 AM, Maarten Maathuis
> wrote:
> > On Mon, Apr 30, 2012 at 12:37 AM, Dmitry Torokhov
> >
> > wrote:
> >> On Sat, Apr 28, 2012 at 11:33:50AM -0400, Nick Bowler wrote:
> >>> On 2012-04-28
Hi Luca, Maarten,
On Monday 30 April 2012 01:01:30 pm Luca Tettamanti wrote:
On Mon, Apr 30, 2012 at 11:07 AM, Maarten Maathuis madman2...@gmail.com
wrote:
On Mon, Apr 30, 2012 at 12:37 AM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
On Sat, Apr 28, 2012 at 11:33:50AM -0400, Nick
On Wed, 2012-05-02 at 09:54 +0200, Jean Delvare wrote:
Hi Luca, Maarten,
On Monday 30 April 2012 01:01:30 pm Luca Tettamanti wrote:
On Mon, Apr 30, 2012 at 11:07 AM, Maarten Maathuis madman2...@gmail.com
wrote:
On Mon, Apr 30, 2012 at 12:37 AM, Dmitry Torokhov
(re-adding Ben to the Cc because he was apparently dropped somewhere in
this thread)
On 2012-05-01 09:23 -0400, Nick Bowler wrote:
> On 2012-04-30 11:07 +0200, Maarten Maathuis wrote:
> > On Mon, Apr 30, 2012 at 12:37 AM, Dmitry Torokhov
> > wrote:
> > > On Sat, Apr 28, 2012 at 11:33:50AM -0400,
On Tue, 1 May 2012 11:31:23 -0400
Nick Bowler wrote:
> On 2012-05-01 16:09 +0100, Alan Cox wrote:
> > > OK, this time bisecting started off relatively smoothly (doing the same
> > > "backwards" bisect on the branch-o-reverts as last time), but then my
> > > disk died halfway through... So I'll
> OK, this time bisecting started off relatively smoothly (doing the same
> "backwards" bisect on the branch-o-reverts as last time), but then my
> disk died halfway through... So I'll post the partial bisection results
> now (11 commits left to test), but I clearly have other things to fix
>
On 2012-05-01 16:09 +0100, Alan Cox wrote:
> > OK, this time bisecting started off relatively smoothly (doing the same
> > "backwards" bisect on the branch-o-reverts as last time), but then my
> > disk died halfway through... So I'll post the partial bisection results
> > now (11 commits left to
On 2012-04-30 11:07 +0200, Maarten Maathuis wrote:
> On Mon, Apr 30, 2012 at 12:37 AM, Dmitry Torokhov
> wrote:
> > On Sat, Apr 28, 2012 at 11:33:50AM -0400, Nick Bowler wrote:
> >> On 2012-04-28 02:19 -0400, Alex Deucher wrote:
> >> > On Fri, Apr 27, 2012 at 8:39 PM, Nick Bowler >> >
On 2012-04-30 11:07 +0200, Maarten Maathuis wrote:
On Mon, Apr 30, 2012 at 12:37 AM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
On Sat, Apr 28, 2012 at 11:33:50AM -0400, Nick Bowler wrote:
On 2012-04-28 02:19 -0400, Alex Deucher wrote:
On Fri, Apr 27, 2012 at 8:39 PM, Nick Bowler
OK, this time bisecting started off relatively smoothly (doing the same
backwards bisect on the branch-o-reverts as last time), but then my
disk died halfway through... So I'll post the partial bisection results
now (11 commits left to test), but I clearly have other things to fix
before I
On 2012-05-01 16:09 +0100, Alan Cox wrote:
OK, this time bisecting started off relatively smoothly (doing the same
backwards bisect on the branch-o-reverts as last time), but then my
disk died halfway through... So I'll post the partial bisection results
now (11 commits left to test), but
On Tue, 1 May 2012 11:31:23 -0400
Nick Bowler nbow...@elliptictech.com wrote:
On 2012-05-01 16:09 +0100, Alan Cox wrote:
OK, this time bisecting started off relatively smoothly (doing the same
backwards bisect on the branch-o-reverts as last time), but then my
disk died halfway
(re-adding Ben to the Cc because he was apparently dropped somewhere in
this thread)
On 2012-05-01 09:23 -0400, Nick Bowler wrote:
On 2012-04-30 11:07 +0200, Maarten Maathuis wrote:
On Mon, Apr 30, 2012 at 12:37 AM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
On Sat, Apr 28, 2012 at
On Mon, Apr 30, 2012 at 11:07 AM, Maarten Maathuis
wrote:
> On Mon, Apr 30, 2012 at 12:37 AM, Dmitry Torokhov
> wrote:
>> On Sat, Apr 28, 2012 at 11:33:50AM -0400, Nick Bowler wrote:
>>> On 2012-04-28 02:19 -0400, Alex Deucher wrote:
>>> > On Fri, Apr 27, 2012 at 8:39 PM, Nick Bowler >> >
On Mon, Apr 30, 2012 at 12:37 AM, Dmitry Torokhov
wrote:
> On Sat, Apr 28, 2012 at 11:33:50AM -0400, Nick Bowler wrote:
>> On 2012-04-28 02:19 -0400, Alex Deucher wrote:
>> > On Fri, Apr 27, 2012 at 8:39 PM, Nick Bowler
>> > wrote:
>> > > Hi Ben,
>> > >
>> > > On 2012-04-27 15:20 +1000, Ben
On Sat, Apr 28, 2012 at 11:33:50AM -0400, Nick Bowler wrote:
On 2012-04-28 02:19 -0400, Alex Deucher wrote:
On Fri, Apr 27, 2012 at 8:39 PM, Nick Bowler nbow...@elliptictech.com
wrote:
Hi Ben,
On 2012-04-27 15:20 +1000, Ben Skeggs wrote:
Does this patch help you at all?
On Mon, Apr 30, 2012 at 12:37 AM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
On Sat, Apr 28, 2012 at 11:33:50AM -0400, Nick Bowler wrote:
On 2012-04-28 02:19 -0400, Alex Deucher wrote:
On Fri, Apr 27, 2012 at 8:39 PM, Nick Bowler nbow...@elliptictech.com
wrote:
Hi Ben,
On
On Mon, Apr 30, 2012 at 11:07 AM, Maarten Maathuis madman2...@gmail.com wrote:
On Mon, Apr 30, 2012 at 12:37 AM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
On Sat, Apr 28, 2012 at 11:33:50AM -0400, Nick Bowler wrote:
On 2012-04-28 02:19 -0400, Alex Deucher wrote:
On Fri, Apr 27, 2012
On Sat, Apr 28, 2012 at 11:33:50AM -0400, Nick Bowler wrote:
> On 2012-04-28 02:19 -0400, Alex Deucher wrote:
> > On Fri, Apr 27, 2012 at 8:39 PM, Nick Bowler
> > wrote:
> > > Hi Ben,
> > >
> > > On 2012-04-27 15:20 +1000, Ben Skeggs wrote:
> > >> Does this patch help you at all?
> > >>
> > >>
On 2012-04-28 02:19 -0400, Alex Deucher wrote:
> On Fri, Apr 27, 2012 at 8:39 PM, Nick Bowler
> wrote:
> > Hi Ben,
> >
> > On 2012-04-27 15:20 +1000, Ben Skeggs wrote:
> >> Does this patch help you at all?
> >>
> >>
On Fri, Apr 27, 2012 at 8:39 PM, Nick Bowler
wrote:
> Hi Ben,
>
> On 2012-04-27 15:20 +1000, Ben Skeggs wrote:
>> Does this patch help you at all?
>>
>> http://cgit.freedesktop.org/nouveau/linux-2.6/commit/?id=a3a285f17867f0018de798b5ee85731ec1268305
>
> Yes. ?I cherry-picked this patch on top
On Fri, Apr 27, 2012 at 8:39 PM, Nick Bowler nbow...@elliptictech.com wrote:
Hi Ben,
On 2012-04-27 15:20 +1000, Ben Skeggs wrote:
Does this patch help you at all?
http://cgit.freedesktop.org/nouveau/linux-2.6/commit/?id=a3a285f17867f0018de798b5ee85731ec1268305
Yes. I cherry-picked this
On 2012-04-28 02:19 -0400, Alex Deucher wrote:
On Fri, Apr 27, 2012 at 8:39 PM, Nick Bowler nbow...@elliptictech.com wrote:
Hi Ben,
On 2012-04-27 15:20 +1000, Ben Skeggs wrote:
Does this patch help you at all?
Hi Ben,
On 2012-04-27 15:20 +1000, Ben Skeggs wrote:
> Does this patch help you at all?
>
> http://cgit.freedesktop.org/nouveau/linux-2.6/commit/?id=a3a285f17867f0018de798b5ee85731ec1268305
Yes. I cherry-picked this patch on top of Linus' master (3.4-rc4+) and
this appears to solve the "black
On Wed, 2012-04-25 at 12:56 +1000, Ben Skeggs wrote:
> On Tue, 2012-04-24 at 21:35 -0400, Nick Bowler wrote:
> > On 2012-04-23 21:03 -0400, Nick Bowler wrote:
> > > On 2012-04-22 22:45 -0400, Konrad Rzeszutek Wilk wrote:
> > > > On Sun, Apr 22, 2012 at 08:05:54PM -0400, Nick Bowler wrote:
> > > >
Hi Ben,
On 2012-04-27 15:20 +1000, Ben Skeggs wrote:
Does this patch help you at all?
http://cgit.freedesktop.org/nouveau/linux-2.6/commit/?id=a3a285f17867f0018de798b5ee85731ec1268305
Yes. I cherry-picked this patch on top of Linus' master (3.4-rc4+) and
this appears to solve the black
On Wed, 2012-04-25 at 12:56 +1000, Ben Skeggs wrote:
On Tue, 2012-04-24 at 21:35 -0400, Nick Bowler wrote:
On 2012-04-23 21:03 -0400, Nick Bowler wrote:
On 2012-04-22 22:45 -0400, Konrad Rzeszutek Wilk wrote:
On Sun, Apr 22, 2012 at 08:05:54PM -0400, Nick Bowler wrote:
Following up
On Mon, Apr 23, 2012 at 09:03:45PM -0400, Nick Bowler wrote:
> On 2012-04-22 22:45 -0400, Konrad Rzeszutek Wilk wrote:
> > On Sun, Apr 22, 2012 at 08:05:54PM -0400, Nick Bowler wrote:
> > > Following up on the above, the commit which introduces the panics during
> > > boot is this one:
> > >
> > >
On Mon, Apr 23, 2012 at 09:03:45PM -0400, Nick Bowler wrote:
On 2012-04-22 22:45 -0400, Konrad Rzeszutek Wilk wrote:
On Sun, Apr 22, 2012 at 08:05:54PM -0400, Nick Bowler wrote:
Following up on the above, the commit which introduces the panics during
boot is this one:
commit
On 2012-04-23 21:03 -0400, Nick Bowler wrote:
On 2012-04-22 22:45 -0400, Konrad Rzeszutek Wilk wrote:
On Sun, Apr 22, 2012 at 08:05:54PM -0400, Nick Bowler wrote:
Following up on the above, the commit which introduces the panics during
boot is this one:
commit
On Tue, 2012-04-24 at 21:35 -0400, Nick Bowler wrote:
On 2012-04-23 21:03 -0400, Nick Bowler wrote:
On 2012-04-22 22:45 -0400, Konrad Rzeszutek Wilk wrote:
On Sun, Apr 22, 2012 at 08:05:54PM -0400, Nick Bowler wrote:
Following up on the above, the commit which introduces the panics
On 2012-04-22 22:45 -0400, Konrad Rzeszutek Wilk wrote:
> On Sun, Apr 22, 2012 at 08:05:54PM -0400, Nick Bowler wrote:
> > Following up on the above, the commit which introduces the panics during
> > boot is this one:
> >
> > commit 8e7e70522d760c4ccd4cd370ebfa0ba69e006c6e
> > Author: Jerome
On Sun, 2012-04-22 at 08:26 +0100, Dave Airlie wrote:
> On Sun, Apr 22, 2012 at 5:51 AM, Linus Torvalds
> wrote:
> > David & co, any ideas?
>
> I've been asking Ben about this, I might have to use a bit more pressure,
I unfortunately haven't yet had any ideas which could be useful aside
from
On 2012-04-22 22:45 -0400, Konrad Rzeszutek Wilk wrote:
On Sun, Apr 22, 2012 at 08:05:54PM -0400, Nick Bowler wrote:
Following up on the above, the commit which introduces the panics during
boot is this one:
commit 8e7e70522d760c4ccd4cd370ebfa0ba69e006c6e
Author: Jerome Glisse
On Sun, Apr 22, 2012 at 08:05:54PM -0400, Nick Bowler wrote:
> On 2012-04-22 12:40 -0400, Nick Bowler wrote:
> > On 2012-04-21 21:51 -0700, Linus Torvalds wrote:
> > > Nick, I realize you had trouble with a bisection already, but it might
> > > really be worth trying again. Do a
> > >
> > >
On Sun, Apr 22, 2012 at 18:40, Nick Bowler wrote:
> (Aside: is there a way to run "git bisect skip" without causing a new
> working tree to be immediately checked out? ?When I'm going to be
> picking the next commit manually anyway, having git bisect checkout a
> new tree arbitrarily, potentially
On 2012-04-22 12:40 -0400, Nick Bowler wrote:
> On 2012-04-21 21:51 -0700, Linus Torvalds wrote:
> > Nick, I realize you had trouble with a bisection already, but it might
> > really be worth trying again. Do a
> >
> > git bisect visualize
> >
> > and try to pick a good commit (avoding the
On 2012-04-22 08:26 +0100, Dave Airlie wrote:
> I've been asking Ben about this, I might have to use a bit more pressure,
>
> It would be worth bisecting drivers/gpu/drm only, I doubt its going to
> be outside that area.
Since the original bisection was restricted to drivers/gpu, and there
On 2012-04-21 21:51 -0700, Linus Torvalds wrote:
> Nick, I realize you had trouble with a bisection already, but it might
> really be worth trying again. Do a
>
> git bisect visualize
>
> and try to pick a good commit (avoding the problems you hit) when you
> hit a problem, and then do
>
>
On Sun, Apr 22, 2012 at 5:51 AM, Linus Torvalds
wrote:
> David & co, any ideas?
I've been asking Ben about this, I might have to use a bit more pressure,
It would be worth bisecting drivers/gpu/drm only, I doubt its going to
be outside that area.
Dave.
On Sun, Apr 22, 2012 at 5:51 AM, Linus Torvalds
torva...@linux-foundation.org wrote:
David co, any ideas?
I've been asking Ben about this, I might have to use a bit more pressure,
It would be worth bisecting drivers/gpu/drm only, I doubt its going to
be outside that area.
Dave.
On 2012-04-22 08:26 +0100, Dave Airlie wrote:
I've been asking Ben about this, I might have to use a bit more pressure,
It would be worth bisecting drivers/gpu/drm only, I doubt its going to
be outside that area.
Since the original bisection was restricted to drivers/gpu, and there
appears
On 2012-04-21 21:51 -0700, Linus Torvalds wrote:
Nick, I realize you had trouble with a bisection already, but it might
really be worth trying again. Do a
git bisect visualize
and try to pick a good commit (avoding the problems you hit) when you
hit a problem, and then do
git
On Sun, Apr 22, 2012 at 18:40, Nick Bowler nbow...@elliptictech.com wrote:
(Aside: is there a way to run git bisect skip without causing a new
working tree to be immediately checked out? When I'm going to be
picking the next commit manually anyway, having git bisect checkout a
new tree
On 2012-04-22 12:40 -0400, Nick Bowler wrote:
On 2012-04-21 21:51 -0700, Linus Torvalds wrote:
Nick, I realize you had trouble with a bisection already, but it might
really be worth trying again. Do a
git bisect visualize
and try to pick a good commit (avoding the problems you
On Sun, Apr 22, 2012 at 08:05:54PM -0400, Nick Bowler wrote:
On 2012-04-22 12:40 -0400, Nick Bowler wrote:
On 2012-04-21 21:51 -0700, Linus Torvalds wrote:
Nick, I realize you had trouble with a bisection already, but it might
really be worth trying again. Do a
git bisect
On Sun, 2012-04-22 at 08:26 +0100, Dave Airlie wrote:
On Sun, Apr 22, 2012 at 5:51 AM, Linus Torvalds
torva...@linux-foundation.org wrote:
David co, any ideas?
I've been asking Ben about this, I might have to use a bit more pressure,
I unfortunately haven't yet had any ideas which could be
David & co, any ideas?
There are other reports of problems with 3.3.x kernels, there's a
report from Tim which may be related (also
apparently working in 3.2, broken black screen in all 3.3.x).
Nick, I realize you had trouble with a bisection already, but it might
really be worth trying again.
David co, any ideas?
There are other reports of problems with 3.3.x kernels, there's a
report from Tim timlie...@woh.rr.com which may be related (also
apparently working in 3.2, broken black screen in all 3.3.x).
Nick, I realize you had trouble with a bisection already, but it might
really be
55 matches
Mail list logo
