All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 88464] booting with radeon.test=1 with radeon3850hd and lockdep validation causes lock-up
Date: Sun, 01 Feb 2015 04:27:12 +0000	[thread overview]
Message-ID: <bug-88464-502-Ja6yMFld8n@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-88464-502@http.bugs.freedesktop.org/>


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

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

--- Comment #5 from Arthur Marsh <arthur.marsh@internode.on.net> ---
Created attachment 113009
  --> https://bugs.freedesktop.org/attachment.cgi?id=113009&action=edit
dmesg after patches applied and with radeon.test=1

After applying the patches and rebuilding the kernel and booting with
radeon.test=1 I had the problems shown in the dmesg output and video output not
working until I rebooted again.

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

[-- Attachment #1.2: Type: text/html, Size: 1563 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

  parent reply	other threads:[~2015-02-01  4:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-15 15:26 [Bug 88464] booting with radeon.test=1 with radeon3850hd and lockdep validation causes lock-up bugzilla-daemon
2015-01-15 15:27 ` bugzilla-daemon
2015-01-18 14:55 ` bugzilla-daemon
2015-01-18 14:56 ` bugzilla-daemon
2015-01-30 15:06 ` bugzilla-daemon
2015-02-01  4:27 ` bugzilla-daemon [this message]
2015-02-07  9:15 ` bugzilla-daemon
2015-02-09  7:24 ` bugzilla-daemon
2015-02-09  7:29 ` bugzilla-daemon
2015-02-17  9:18 ` bugzilla-daemon
2019-11-19  9:00 ` 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-88464-502-Ja6yMFld8n@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.