Re: [Nouveau] Fwd: [bisected] nouveau failure with 3.9-rc1 and ongoing

2013-03-14 Thread Marcin Slusarz
On Thu, Mar 14, 2013 at 07:56:03PM +0100, Sune Mølgaard wrote:
> Marcin Slusarz wrote:
> > I think it may be already fixed by commit 
> > 94f54f5336aac6801f2a14dcb12467e41b35456a
> > "drm/nv50: encoder creation failure doesn't mean full init failure" (post 
> > 3.9-rc2)
> 
> With the latest 3.9-rc2+ git, I got past the KMS init blackout and into 
> X, but I got a panic shortly after.
> 
> Unfortunately, the trace was too lengthy to see in which module, and 
> since it wasn't captured /var/log/syslog, I have no idea whether it has 
> anything to do with nouveau or something else.
> 
> tl;dr: It would seem that the commit fixes the specific bug I reported, 
> but my system isn't functional.

If you have another machine in the same network, you could try to catch this
panic with netconsole. See
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/networking/netconsole.txt

Marcin
___
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau


Re: [Nouveau] Fwd: [bisected] nouveau failure with 3.9-rc1 and ongoing

2013-03-14 Thread Sune Mølgaard

Marcin Slusarz wrote:

I think it may be already fixed by commit 
94f54f5336aac6801f2a14dcb12467e41b35456a
"drm/nv50: encoder creation failure doesn't mean full init failure" (post 
3.9-rc2)


With the latest 3.9-rc2+ git, I got past the KMS init blackout and into 
X, but I got a panic shortly after.


Unfortunately, the trace was too lengthy to see in which module, and 
since it wasn't captured /var/log/syslog, I have no idea whether it has 
anything to do with nouveau or something else.


tl;dr: It would seem that the commit fixes the specific bug I reported, 
but my system isn't functional.


Thank you so far anyway,

Sune Mølgaard

--
Nothing exists except atoms and empty space; everything else is
opinion.
- Democritus
___
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau


Re: [Nouveau] Fwd: [bisected] nouveau failure with 3.9-rc1 and ongoing

2013-03-13 Thread Marcin Slusarz
On Wed, Mar 13, 2013 at 06:22:38PM +0100, Sune Mølgaard wrote:
> Hiya,
> 
> I sent the enclosed email to linux-kernel before realizing that it 
> would, perhaps, be more proper to send it here, which I hereby do.
> 
> I shall be happy to try out any and all patches.
> 
> Best regards,
> 
> Sune Mølgaard
> 
>  Original Message 
> Subject: [bisected] nouveau failure with 3.9-rc1 and ongoing
> Date: Tue, 12 Mar 2013 19:57:55 +0100
> From: Sune Mølgaard 
> To: linux-ker...@vger.kernel.org
> 
> Hiya,
> 
> Between 3.8 and 3.9-rc1, the following occurs:
> 
> Upon boot, when KMS kicks in, I get a blank screen. Keyboard responds
> correctly to "Num Lock" on/off, but machine is unreachable on the network.
> 
> Git bisection says:
> 
> eb6313add6dddf07ea3e50c4caa33a9c3b2379f1 is the first bad commit
> commit eb6313add6dddf07ea3e50c4caa33a9c3b2379f1
> Author: Ben Skeggs 
> Date:   Mon Feb 11 09:52:58 2013 +1000
> 
>  drm/nv50: initial kms support for off-chip TMDS/DP encoders
> 
>  Signed-off-by: Ben Skeggs 
> 
> :04 04 41f69d26a80082e19d3c76e6556ad5ef9eb2677d
> 216d501e053e9d05136929593e90259c2e59dff0 Mdrivers

I think it may be already fixed by commit 
94f54f5336aac6801f2a14dcb12467e41b35456a
"drm/nv50: encoder creation failure doesn't mean full init failure" (post 
3.9-rc2)

> But even though I marked that last bisection kernel good (since it
> didn't cause a black-out), it does have problems, namely that GTK themes
> are reset, and xrandr seems non-functional, inasmuch as my left-ward,
> secondary screen now seems to be treated as being situated to the right.
> No previous kernel in the bisection exercise caused anything of the like.

Not sure about this one...


Marcin
___
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau


[Nouveau] Fwd: [bisected] nouveau failure with 3.9-rc1 and ongoing

2013-03-13 Thread Sune Mølgaard

Hiya,

I sent the enclosed email to linux-kernel before realizing that it 
would, perhaps, be more proper to send it here, which I hereby do.


I shall be happy to try out any and all patches.

Best regards,

Sune Mølgaard

 Original Message 
Subject: [bisected] nouveau failure with 3.9-rc1 and ongoing
Date: Tue, 12 Mar 2013 19:57:55 +0100
From: Sune Mølgaard 
To: linux-ker...@vger.kernel.org

Hiya,

Between 3.8 and 3.9-rc1, the following occurs:

Upon boot, when KMS kicks in, I get a blank screen. Keyboard responds
correctly to "Num Lock" on/off, but machine is unreachable on the network.

Git bisection says:

eb6313add6dddf07ea3e50c4caa33a9c3b2379f1 is the first bad commit
commit eb6313add6dddf07ea3e50c4caa33a9c3b2379f1
Author: Ben Skeggs 
Date:   Mon Feb 11 09:52:58 2013 +1000

drm/nv50: initial kms support for off-chip TMDS/DP encoders

Signed-off-by: Ben Skeggs 

:04 04 41f69d26a80082e19d3c76e6556ad5ef9eb2677d
216d501e053e9d05136929593e90259c2e59dff0 M  drivers

But even though I marked that last bisection kernel good (since it
didn't cause a black-out), it does have problems, namely that GTK themes
are reset, and xrandr seems non-functional, inasmuch as my left-ward,
secondary screen now seems to be treated as being situated to the right.
No previous kernel in the bisection exercise caused anything of the like.

I'd be happy to try out any and all patches proposed, and as for the
physical card, this is the relevant part:

02:00.0 VGA compatible controller: NVIDIA Corporation G92 [GeForce 9800
GT] (rev a2)

Please let me know if there is anything else I can do to help resolve this!

Best regards,

Sune Mølgaard

--
What a gorgeous day. What effulgent sunshine. It was a day of this
sort the McGillicuddy brothers murdered their mother with an axe.
- W. C. Fields
___
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau