Bug 73841 - Audio broken on HDMI (ATI)
Summary: Audio broken on HDMI (ATI)
Status: RESOLVED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_video-dri
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-11 15:57 UTC by v0k3
Modified: 2014-09-12 11:14 UTC (History)
2 users (show)

See Also:
Kernel Version: 3.14-4
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments
dmesg with debug (91.41 KB, text/plain)
2014-04-29 13:40 UTC, v0k3
Details

Description v0k3 2014-04-11 15:57:53 UTC
After the last update to the kernel version 3.14.0.4 I get this error on boot:

"drm:I915_stolen_to_physical"

and my HDMI's sound doesn't work anymore..
I just downgraded the kernel to 3.13.8-1 and it works (no errors).
I'm on Arch Linux x86-x64 with an intel's CPU i7 (2600 or 2700) and as vga I have a Radeon HD 7770.
Sorry for bad english.
Comment 1 v0k3 2014-04-18 08:54:39 UTC
audio now works (3.14.1-1) but i still get the error.
Comment 2 Jani Nikula 2014-04-22 18:44:10 UTC
Please attach dmesg showing the problem.
Comment 3 v0k3 2014-04-27 18:32:52 UTC
here there is my last boot dmesg: http://pastebin.com/W9EPz5Ni
Comment 4 Jani Nikula 2014-04-28 10:25:57 UTC
(In reply to v0k3 from comment #3)
> here there is my last boot dmesg: http://pastebin.com/W9EPz5Ni

Apologies, I forgot to ask for dmesg with drm.debug=0xe module parameter set. Also, please always attach ("Add an attachment" above) the logs instead of using pastebin. Thanks.
Comment 5 v0k3 2014-04-28 17:30:28 UTC
(In reply to Jani Nikula from comment #4)
> (In reply to v0k3 from comment #3)
> > here there is my last boot dmesg: http://pastebin.com/W9EPz5Ni
> 
> Apologies, I forgot to ask for dmesg with drm.debug=0xe module parameter
> set. Also, please always attach ("Add an attachment" above) the logs instead
> of using pastebin. Thanks.

Oh sorry, I will do it right now.
Anyway how do I set the drm.debug parameter?
Do I have to start with 'drm.debug=0xe' by the bootloader?
Sorry again, v0k3.
Comment 6 Jani Nikula 2014-04-29 09:03:22 UTC
(In reply to v0k3 from comment #5)
> Anyway how do I set the drm.debug parameter?
> Do I have to start with 'drm.debug=0xe' by the bootloader?

That's correct. Usually you can do that at boot time, without making persistent changes, e.g. by pressing 'e' in grub/syslinux.
Comment 7 v0k3 2014-04-29 13:40:22 UTC
Created attachment 134211 [details]
dmesg with debug
Comment 8 v0k3 2014-04-29 13:40:51 UTC
(In reply to Jani Nikula from comment #6)
> (In reply to v0k3 from comment #5)
> > Anyway how do I set the drm.debug parameter?
> > Do I have to start with 'drm.debug=0xe' by the bootloader?
> 
> That's correct. Usually you can do that at boot time, without making
> persistent changes, e.g. by pressing 'e' in grub/syslinux.

I've done it
Comment 9 Jani Nikula 2014-08-14 08:32:15 UTC
Sorry it seems we've ignored this bug a bit. Does the problem persist with recent kernels, say 3.16?
Comment 10 Jani Nikula 2014-09-12 10:09:45 UTC
Oops, we've totally failed to notice the HDMI is connected to the discrete GPU. Reassigning.
Comment 11 Christian König 2014-09-12 10:38:44 UTC
(In reply to Jani Nikula from comment #10)
> Oops, we've totally failed to notice the HDMI is connected to the discrete
> GPU. Reassigning.

But audio now works for the user again:
> audio now works (3.14.1-1) but i still get the error.

What he still complains about is: "drm:I915_stolen_to_physical" If that isn't critical or already fixed I think we can close the bug now.
Comment 12 Jani Nikula 2014-09-12 11:14:04 UTC
(In reply to Christian König from comment #11)
> What he still complains about is: "drm:I915_stolen_to_physical" If that
> isn't critical or already fixed I think we can close the bug now.

Right. Sorry for the noise.

Thanks for the report anyway. Please file a new bug against DRM/Intel at https://bugs.freedesktop.org/enter_bug.cgi?product=DRI if the problem with drm:I915_stolen_to_physical persists with recent kernels.

Note You need to log in before you can comment on or make changes to this bug.