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 13403] New: Random crashes.
Date: Tue, 27 Nov 2007 01:36:09 -0800 (PST)	[thread overview]
Message-ID: <bug-13403-8800@http.bugs.freedesktop.org/> (raw)

http://bugs.freedesktop.org/show_bug.cgi?id=13403

           Summary: Random crashes.
           Product: xorg
           Version: unspecified
          Platform: x86 (IA32)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
        AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
        ReportedBy: xake-ca8b1Tj3MiseIZ0/mPfg9Q@public.gmane.org
         QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org


01:00.0 VGA compatible controller [0300]: nVidia Corporation NV31 [GeForce FX
5600] [10de:0312] (rev a1) (prog-if 00 [VGA controller])

I have random crashes both with and without randr12.
They can appear as I open a window, closes a window, press enter in a terminal,
switch between windows or clicking a link in firefox.
They all gives DMA queue hangs in one form or another, but I have been unable
to find a pattern in what triggers them.

This current one was me opening something in gmplayer.


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

             reply	other threads:[~2007-11-27  9:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-27  9:36 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-13403-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2007-11-27  9:37   ` [Bug 13403] Random crashes bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2007-11-27  9:38   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2007-11-27  9:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2007-11-27  9:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2007-11-27  9:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2007-11-27 11:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2007-11-27 11:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-01-17 14:13   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-01-17 21:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-01-17 22:50   ` 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-13403-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.