All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105481] New: radeon driver lockup since 3.9.*
Date: Mon, 05 Oct 2015 00:50:07 +0000	[thread overview]
Message-ID: <bug-105481-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=105481

            Bug ID: 105481
           Summary: radeon driver lockup since 3.9.*
           Product: Drivers
           Version: 2.5
    Kernel Version: 4.2.2-1
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: droidlove@ya.ru
        Regression: No

Created attachment 189451
  --> https://bugzilla.kernel.org/attachment.cgi?id=189451&action=edit
dmesg output

Since the Kernel 3.9.*(don't remember the last number of the version; maybe all
of them) i get rare lockups of the radeon  driver. The probability of a lockup
is higher the more load on a graphic card. But this is not necessary. This time
the driver hung while watching a video in SMPlayer. 

I can't reproduce the bug on purpose, it just happens from time to time,
resulting in switched off monitors. Sometimes the kernel is trying to restore
the driver but this never happens, resulting in endless switching on and off
the monitors. 

Hardware:
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape
Verde PRO [Radeon HD 7750/8740 / R7 250E]


Thanks!

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

                 reply	other threads:[~2015-10-05  0:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-105481-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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.