All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 73445] New: [NV4E] regression with 3.13 -rcX: glxgears etc. hard lockup/freezes machine, on 3.12 everything works
Date: Thu, 09 Jan 2014 19:25:48 +0000	[thread overview]
Message-ID: <bug-73445-8800@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1810 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=73445

          Priority: medium
            Bug ID: 73445
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
           Summary: [NV4E] regression with 3.13 -rcX: glxgears etc. hard
                    lockup/freezes machine, on 3.12 everything works
          Severity: critical
    Classification: Unclassified
                OS: Linux (All)
          Reporter: christian.niemeyer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: 10.0
         Component: Drivers/DRI/nouveau
           Product: Mesa

This seems to be a regression.

Running ubuntu 14.04 development branch. On an old HP G6000 notebook with
GeForce Go 6000, this is NV4E according to my /var/log/Xorg.0.log

With 3.12.0-7-generic everything runs fine. Even basic acceleration in Firefox
and playing games in Steam (like World of Goo or Snuggle Truck - those run
flawlessly). I have OpenGL 2.1 support and Shader Language 1.20 according to
glxinfo

I runs fine on 3.12-x with Mesa 10.0 and also fine with xorg-edergs PPA with
Mesa 10.1.0-devel

However in both cases booting any 3.13 kernel and running the first GL
application like glxgears or starting a game, my system entirely freezes.
Whether I use stock repository or xorg-edgers. So to me this doesn't seem to be
directly Mesa related, there is some problem with kernel 3.13 definitely. It
freezes reproduceable 100%. No problems with 3.12.

Once I could reat a VT after a while, but it didn't react anymore.

3.13 is going to be the kernel for ubuntu 14.04 LTS. 

Sorry, this is my first bug report, please be kind. I'm not able to get any log
files after reboot.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3089 bytes --]

[-- Attachment #2: Type: text/plain, Size: 181 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

             reply	other threads:[~2014-01-09 19:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-09 19:25 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-73445-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-01-09 19:28   ` [Bug 73445] [NV4E] regression with 3.13 -rcX: glxgears etc. hard lockup/freezes machine, on 3.12 everything works bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-09 19:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-09 19:38   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-09-11 23:38   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-73445-8800@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.