dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 66714] Mobility Radeon HD 5650 doesn't boot with kernel 3.10 (and newer) when using radeon.audio=1
Date: Sun, 14 Jul 2013 10:10:10 +0000	[thread overview]
Message-ID: <bug-66714-502-5omGHKHdqD@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-66714-502@http.bugs.freedesktop.org/>


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

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

Marco Trevisan (Treviño) <mail@3v1n0.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

--- Comment #4 from Marco Trevisan (Treviño) <mail@3v1n0.net> ---
So, I've tried the patch on a 3.10 kernel that was affected and... Great, it
Works! :)
FYI, I've also added a couple of error logs in the code to see where exactly
the failure was and this was the result:

[    2.073137] [drm] fb mappable at 0xC035F000
[    2.073139] [drm] vram apper at 0xC0000000
[    2.073140] [drm] size 8294400
[    2.073141] [drm] fb depth is 24
[    2.073142] [drm]    pitch is 7680
[    2.073252] fbcon: radeondrmfb (fb0) is primary device
[    2.073323] [drm:evergreen_hdmi_enable] *ERROR* Invalid DIG (dig:
ffff880229d0fc00, dig->afmt: (null))
/home/marco/Dev/debs/linux-3.10.0/drivers/gpu/drm/radeon/evergreen_hdmi.c:298
[    2.573589] [drm:evergreen_hdmi_enable] *ERROR* Invalid DIG (dig:
ffff880229d0fc00, dig->afmt: (null))
/home/marco/Dev/debs/linux-3.10.0/drivers/gpu/drm/radeon/evergreen_hdmi.c:298
[    2.607449] Console: switching to colour frame buffer device 170x48
[    2.610160] radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device
[    2.610162] radeon 0000:01:00.0: registered panic notifier
[    2.610237] [drm] Initialized radeon 2.33.0 20080528 for 0000:01:00.0 on
minor 0

Full dmesg at http://pastebin.ubuntu.com/5873667/
I don't know if this may be only the side effect of another issue (wrong
initialization order?).

One more thing I discovered in the past days, is that the kernel crash was not
happening in case that the HDMI was plugged after that ligthtdm was running
(attaching it anytime before was leading to a freeze).

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

[-- Attachment #1.2: Type: text/html, Size: 3515 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:[~2013-07-14 10:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-08 22:02 [Bug 66714] New: Mobility Radeon HD 5650 doesn't boot with kernel 3.10 (and newer) when using radeon.audio=1 bugzilla-daemon
2013-07-08 22:02 ` [Bug 66714] " bugzilla-daemon
2013-07-08 22:10 ` bugzilla-daemon
2013-07-08 22:19 ` bugzilla-daemon
2013-07-08 23:15 ` bugzilla-daemon
2013-07-14 10:10 ` bugzilla-daemon [this message]
2013-07-14 10:10 ` bugzilla-daemon
2013-07-14 12:18 ` bugzilla-daemon
2013-07-31  3:27 ` bugzilla-daemon
2013-07-31 13:08 ` 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-66714-502-5omGHKHdqD@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).