All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 43835] New: System crashes when radeon firmware blob (R520_cp.bin) is installed
Date: Wed, 14 Dec 2011 09:06:57 +0000	[thread overview]
Message-ID: <bug-43835-502@http.bugs.freedesktop.org/> (raw)

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

             Bug #: 43835
           Summary: System crashes when radeon firmware blob (R520_cp.bin)
                    is installed
    Classification: Unclassified
           Product: DRI
           Version: XOrg CVS
          Platform: Other
               URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=65153
                    2
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Radeon
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: noelamac@gmail.com


Created attachment 54426
  --> https://bugs.freedesktop.org/attachment.cgi?id=54426
Logs ("dmesg" and "xorg.0.log" for kernels 3.2-rc4 and 3.1 with and without the
firmware installed)

1. Steps to reproduce the problem

Running Debian Wheezy, by installing the package "firmware-linux-nonfree" which
contains the firmware to enable 3D acceleration for the ATI card (M56P Radeon
Mobility X1600), when the system starts and user logins, the system crashes (no
specific action triggers the crash, is just about time to get it).

2. Symptoms

The user receives a "kernel oops" (kernel 3.1) or system hangs with a trace
(kernel 3.2-rc4) and system locks.

3. Tested kernels

The user has tested kernel 3.1 (Wheezy's stock kernel) and 3.2-rc4 (from
Debian's experimental branch). Both kernels expose the same result when
firmware is installed. On the other hand, both kernels work fine as soon as the
firmware package is unistalled.

4. Additional information

The crash has been tracked in Debian BTS #651532 (full link available in the
URL field).

5. Attached logs (4 files):

- "dmesg" and "Xorg.0.log" for kernels 3.2-rc4 and 3.1 when firmware is
installed.

- "dmesg" and "Xorg.0.log" for kernels 3.2-rc4 and 3.1 when firmware is not
installed.

6. Other considerations

Please, note that I am opening the this bug on behalf of another person who is
experiencing the crash. For this reason I'm CC'ing to him.

-- 
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:[~2011-12-14 17:06 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-14  9:06 bugzilla-daemon [this message]
2011-12-14 17:19 ` [Bug 43835] System crashes when radeon firmware blob (R520_cp.bin) is installed bugzilla-daemon
2011-12-14 17:22 ` bugzilla-daemon
2011-12-14 17:56 ` bugzilla-daemon
2011-12-15  8:49 ` bugzilla-daemon
2011-12-15 15:29 ` bugzilla-daemon
2011-12-15 15:47 ` bugzilla-daemon
2011-12-15 16:43 ` bugzilla-daemon
2011-12-15 16:44 ` bugzilla-daemon
2011-12-15 21:25 ` bugzilla-daemon
2011-12-15 21:28 ` bugzilla-daemon
2011-12-15 21:37 ` bugzilla-daemon
2011-12-15 21:40 ` bugzilla-daemon
2011-12-16  8:01 ` bugzilla-daemon
2011-12-16  8:17 ` bugzilla-daemon
2011-12-16  9:05 ` bugzilla-daemon
2011-12-16  9:51 ` bugzilla-daemon
2011-12-16 21:23 ` bugzilla-daemon
2011-12-16 22:48 ` bugzilla-daemon
2011-12-17  9:44 ` bugzilla-daemon
2012-01-22 21:46 ` bugzilla-daemon
2012-01-22 21:47 ` bugzilla-daemon
2012-01-22 21:48 ` bugzilla-daemon
2012-01-22 21:49 ` bugzilla-daemon
2012-01-22 21:49 ` bugzilla-daemon
2012-01-22 22:24 ` bugzilla-daemon
2012-01-23 21:21 ` bugzilla-daemon
2012-01-23 21:22 ` bugzilla-daemon
2012-01-23 21:25 ` bugzilla-daemon
2012-01-23 21:25 ` bugzilla-daemon
2012-01-23 21:40 ` bugzilla-daemon
2012-01-24  7:58 ` bugzilla-daemon
2012-01-24  8:00 ` bugzilla-daemon
2012-01-24  9:16 ` bugzilla-daemon
2012-01-25 17:16 ` bugzilla-daemon
2012-01-25 17:17 ` bugzilla-daemon
2012-01-25 17:37 ` bugzilla-daemon
2012-01-25 17:54 ` bugzilla-daemon
2012-01-25 18:10 ` bugzilla-daemon
2012-01-25 18:17 ` bugzilla-daemon
2012-01-25 18:35 ` bugzilla-daemon
2012-01-25 18:41 ` bugzilla-daemon
2012-01-25 18:56 ` bugzilla-daemon
2012-01-25 18:57 ` bugzilla-daemon
2012-01-25 20:39 ` bugzilla-daemon
2012-01-26  7:41 ` bugzilla-daemon
2012-01-26 13:59 ` bugzilla-daemon
2012-01-26 18:18 ` bugzilla-daemon
2012-02-02 12:04 ` bugzilla-daemon
2012-02-02 14:23 ` bugzilla-daemon
2012-02-02 14:36 ` bugzilla-daemon
2012-02-02 14:36 ` bugzilla-daemon
2012-02-02 16:34 ` bugzilla-daemon
2012-02-02 16:57 ` bugzilla-daemon
2012-02-10  1:55 ` bugzilla-daemon
2012-02-12 11:24 ` bugzilla-daemon
2012-02-12 11:26 ` bugzilla-daemon
2012-02-12 11:27 ` bugzilla-daemon
2012-02-12 11:27 ` bugzilla-daemon
2019-11-19  8:24 ` 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-43835-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.