All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 76286] New: Kernel v3.13 hang during boot now that dpm is enabled for radeon driver - Radeon HD4870
Date: Mon, 17 Mar 2014 18:32:46 +0000	[thread overview]
Message-ID: <bug-76286-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 76286
          Assignee: dri-devel@lists.freedesktop.org
           Summary: Kernel v3.13 hang during boot now that dpm is enabled
                    for radeon driver - Radeon HD4870
          Severity: major
    Classification: Unclassified
                OS: Linux (All)
          Reporter: OmegaPhil+FreeDesktop.BugTracker@gmail.com
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: unspecified
         Component: DRM/Radeon
           Product: DRI

Created attachment 95961
  --> https://bugs.freedesktop.org/attachment.cgi?id=95961&action=edit
Kernel log for session with manual radeon module loading with modesetting
enabled

Flagged as major as this prevents kernel boot if the user doesnt know how to
disable the functionality with the kernel boot parameters.

Originally reported in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741619
, Debian kernel v3.13 enables dpm by default - partway through the boot process
(when cryptsetup is opening encrypted disks), the kernel hangs (confirmed with
no response to ping).

The kernel boots fine with radeon.dpm=0.

Following instructions
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741485#10) I booted with
radeon.modeset=0, made sure X wasn't running and radeon was unloaded, then
modprobe'd radeon modeset=1 - after a small delay everything hung.

I have attached kern.log (REISUB FTW this time it seems?), there is an X log
but that simply gave up after finding no modesetting support, before the point
where I reloaded radeon.

kern.log is verbose as I always boot with full debugging information, but in
this case its useless as nothing appears to be logged associated with the
radeon load (and I'm assuming the magic sync worked).

In terms of fighting the issue, I have C and C++ experience but no real kernel
debugging EXP and certainly nothing todo with the graphical stack.


===============================

uname -a: Linux omega1 3.13-1-amd64 #1 SMP Debian 3.13.5-1 (2014-03-04) x86_64
GNU/Linux
Debian Testing
X server: 1.15.0
Radeon: 7.3.0

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

[-- Attachment #1.2: Type: text/html, Size: 3949 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:[~2014-03-17 18:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-17 18:32 bugzilla-daemon [this message]
2014-03-17 20:00 ` [Bug 76286] Kernel v3.13 hang during boot now that dpm is enabled for radeon driver - Radeon HD4870 bugzilla-daemon
2014-03-17 21:10 ` bugzilla-daemon
2014-03-17 21:13 ` bugzilla-daemon
2014-03-17 21:18 ` bugzilla-daemon
2014-03-21  6:06 ` bugzilla-daemon
2014-03-21  6:21 ` bugzilla-daemon
2014-03-21  6:41 ` bugzilla-daemon
2014-03-21  7:13 ` bugzilla-daemon
2014-03-21  7:37 ` bugzilla-daemon
2014-03-21 14:45 ` bugzilla-daemon
2014-03-21 17:48 ` bugzilla-daemon
2014-03-21 18:11 ` bugzilla-daemon
2014-03-21 18:32 ` bugzilla-daemon
2014-03-29 21:22 ` bugzilla-daemon
2014-05-22 13:48 ` bugzilla-daemon
2014-05-22 14:02 ` bugzilla-daemon
2014-05-22 14:58 ` bugzilla-daemon
2014-05-26  7:36 ` bugzilla-daemon
2014-05-27  7:06 ` bugzilla-daemon
2019-11-19  8:46 ` 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-76286-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.