Bug 95358 - Tonga no hdmi audio on DAL 4.7 works on DAL 4.6
Summary: Tonga no hdmi audio on DAL 4.7 works on DAL 4.6
Status: RESOLVED INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/AMDgpu (show other bugs)
Version: DRI git
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-11 23:33 UTC by Andy Furniss
Modified: 2016-09-03 11:06 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Andy Furniss 2016-05-11 23:33:58 UTC
I have lost HDMI audio with adg5f drm-next-4.7-wip-dal

It worked with 4.6 dal branch.

I can't bisect 4.7 as I can't find a working - if I go too far back I die on boot and need hard reset or get no display.
Comment 1 Andy Furniss 2016-05-14 10:37:18 UTC
FWIW I found an old build of 4.7-dal that did have sound - though it was early, 23rd March and I don't have any builds in between.

I see if I git reset --hard 4.5.0-rc7-g629edea (the version of that build)
I can get a new working build and seemingly git history from that time.

If I had more builds I guess I could narrow it down like that - but I don't and I don't know how get the historic head versions from git - is that possible?
Comment 2 Felix Schwarz 2016-05-14 12:59:05 UTC
(In reply to Andy Furniss from comment #1)
> If I had more builds I guess I could narrow it down like that - but I don't
> and I don't know how get the historic head versions from git - is that
> possible?

Maybe I completely misunderstood your question but did you try "git checkout <COMMIT>"? As far as I can see the main challenge might be to get these commit ids as the DAL branches are rebased regularly, right? "git reflog" might be an option but it might be a bit tedious to search through the big amount of commits.
Comment 3 Andy Furniss 2016-05-14 14:54:40 UTC
(In reply to Felix Schwarz from comment #2)
> (In reply to Andy Furniss from comment #1)
> > If I had more builds I guess I could narrow it down like that - but I don't
> > and I don't know how get the historic head versions from git - is that
> > possible?
> 
> Maybe I completely misunderstood your question but did you try "git checkout
> <COMMIT>"? As far as I can see the main challenge might be to get these
> commit ids as the DAL branches are rebased regularly, right?

Yea, I mainly test the non dal branch so it is the commit hashes I am missing.

I would need to be able to checkout based on date really I think.

>"git reflog"
> might be an option but it might be a bit tedious to search through the big
> amount of commits.

Thanks, I've never used that before, it seems to be just a history of what I did, which doesn't really help as I wasn't on the dal branch mostly, but is useful to know for the future as its now worth me just switching around various branches even if I know I don't have time to build and test every one.

Saying that it looks like I did switch to it but didn't build, so I do have something else to try.
Comment 4 Andy Furniss 2016-05-14 21:03:00 UTC
Possible progress with the git aspect - while reading about reflog I saw a comment which lead me to doing - 

git log --walk-reflogs origin/drm-next-4.7-wip-dal

which apparently gets me a sha for every time I did git fetch origin and dal got updated.

Looks promising, but I haven't had time to test it out yet.
Comment 5 Andy Furniss 2016-05-16 11:52:49 UTC
After more testing with older versions of drm-next-4.7-wip-dal

it seems that this stopped working after the rebase on top of 4.6.

I can't be sure of course, but I can't so far find a working on anything after a version that was based on 4.5.0-rc7, the next I can test is on top of 4.6.0-rc2
and even if I set its history to look much like the working it doesn't work.
Comment 6 Andy Furniss 2016-09-03 11:06:44 UTC
I guess DAL work is all happening in the staging branches now and with current amd-staging-4.7 HDMI sound is working OK for me.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.