All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 60555] New: [r300g] RADEON_NO_TCL=1 hardlock
Date: Sat, 09 Feb 2013 18:07:15 +0000	[thread overview]
Message-ID: <bug-60555-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: lowest
            Bug ID: 60555
          Assignee: dri-devel@lists.freedesktop.org
           Summary: [r300g] RADEON_NO_TCL=1 hardlock
          Severity: trivial
    Classification: Unclassified
                OS: All
          Reporter: pavel.ondracka@email.cz
          Hardware: Other
            Status: NEW
           Version: git
         Component: Drivers/DRI/r300
           Product: Mesa

This is not really a bug as normal user will never encounter this, just some
nuisance I discovered when I tried to investigate bug 60552 a little bit.

When RADEON_NO_TCL=1 is used (which is useful in diagnosing compiler bugs), the
whole machine sometimes hardlocks. App from bug 60552 is a good way to
reproduce this.

This debug option should be either fixed, or if it no longer considered useful,
then it should be removed. 

BTW this was working not a year ago, so I can probably run a bisect if needed.

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

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

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

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2013-02-09 18:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-09 18:07 bugzilla-daemon [this message]
2013-02-09 18:09 ` [Bug 60555] [r300g] RADEON_NO_TCL=1 hardlock bugzilla-daemon
2013-02-10  1:56 ` bugzilla-daemon
2019-09-18 18:51 ` bugzilla-daemon

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-60555-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.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.