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 30213] New: ION2 (NV50) locks up with infinite loop
Date: Wed, 15 Sep 2010 07:39:54 -0700 (PDT)	[thread overview]
Message-ID: <bug-30213-8800@http.bugs.freedesktop.org/> (raw)

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

           Summary: ION2 (NV50) locks up with infinite loop
           Product: xorg
           Version: 7.5
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: Driver/nouveau
        AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
        ReportedBy: jeffm-IBi9RG/b67k@public.gmane.org
         QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org


Created an attachment (id=38722)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=38722)
Xorg.0.log

Under normal operation, the display locks up. The keyboard becomes
nonresponsive, but the mouse (and cursor movement) still works. The display
stays coherent but is just frozen in time.

Attached are both the kernel log and Xorg.0.log, as well as the hwinfo
(openSUSE tool) that describes the hardware in detail. The kernel log changes
and I've seen this hang appear without any entry in the kernel log.

On my system, this issue is reproduced trivially by playing video with totem.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2010-09-15 14:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-15 14:39 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-30213-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2010-09-15 14:40   ` [Bug 30213] ION2 (NV50) locks up with infinite loop bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-15 14:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-15 15:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-15 15:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-15 15:48   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-15 16:01   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-12-05 20:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-18 18:09   ` 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-30213-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.