On Mon, Nov 26, 2012 at 8:28 PM, Marcin Slusarz
wrote:
> On Mon, Nov 26, 2012 at 08:16:17PM +0100, Maarten Maathuis wrote:
>> On Mon, Nov 26, 2012 at 7:04 PM, Marcin Slusarz
>> wrote:
>> > On Sun, Nov 25, 2012 at 11:50:50PM +0100, Maarten Maathuis wrote:
>> >> Hi everyone,
>> >>
>> >> I was wonde
On Mon, Nov 26, 2012 at 08:16:17PM +0100, Maarten Maathuis wrote:
> On Mon, Nov 26, 2012 at 7:04 PM, Marcin Slusarz
> wrote:
> > On Sun, Nov 25, 2012 at 11:50:50PM +0100, Maarten Maathuis wrote:
> >> Hi everyone,
> >>
> >> I was wondering what to do to dig into this problem further.The kernel
> >>
On Mon, Nov 26, 2012 at 7:04 PM, Marcin Slusarz
wrote:
> On Sun, Nov 25, 2012 at 11:50:50PM +0100, Maarten Maathuis wrote:
>> Hi everyone,
>>
>> I was wondering what to do to dig into this problem further.The kernel
>> is several weeks old (nouveau tree), it's at commit
>> 000463f13fba6b2f94a5bfcb
On Sun, Nov 25, 2012 at 11:50:50PM +0100, Maarten Maathuis wrote:
> Hi everyone,
>
> I was wondering what to do to dig into this problem further.The kernel
> is several weeks old (nouveau tree), it's at commit
> 000463f13fba6b2f94a5bfcb0d615751ae9c34a0.
>
> As you can see from the mesages below t
Hi everyone,
I was wondering what to do to dig into this problem further.The kernel
is several weeks old (nouveau tree), it's at commit
000463f13fba6b2f94a5bfcb0d615751ae9c34a0.
As you can see from the mesages below the problem is reproducable to
the point of getting exactly the same error.
Nov