Bug 91253 - Regression: Can't boot on 4.0.5 and later but can boot on 4.0.4 (on iMac)
Summary: Regression: Can't boot on 4.0.5 and later but can boot on 4.0.4 (on iMac)
Status: RESOLVED DUPLICATE of bug 91041
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: unspecified
Hardware: Other Linux (All)
: medium critical
Assignee: Default DRI bug account
QA Contact:
Depends on:
Reported: 2015-07-07 08:34 UTC by Andreas Tunek
Modified: 2015-07-30 13:52 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Description Andreas Tunek 2015-07-07 08:34:32 UTC
Using the Fedora Linux I can't boot with Linux from 4.0.5 and up. 4.0.4 still works.

Here is a link to the fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=1236423

and to the linux bug here: https://bugzilla.kernel.org/show_bug.cgi?id=101131

Any more info I should add?
Comment 1 Michel Dänzer 2015-07-07 09:01:03 UTC
Please include the relevant information here directly.
Comment 2 Christian König 2015-07-07 10:16:06 UTC
Price question: Can you bisect?

If 4.0.5 is bad and 4.0.4 still works that should be pretty much straight forward.
Comment 3 Andreas Tunek 2015-07-07 14:30:30 UTC
Do you know any guide on how to bisect while using Fedora?
Comment 4 Alex Deucher 2015-07-07 15:17:18 UTC
There are tons of git bisect howtos.  You will need to checkout the stable kernel git tree, build and install it.  Here are the basics:

# 1. clone the git tree
git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
cd linux-stable
# 2. copy the config from your currently running kernel
cp /boot/config-4.0.4-<whatever> .config
# 3. start the bisect
git bisect start
git bisect good v4.0.4
git bisect bad v4.0.5
# 4. build and install the kernel
make modules_install
make install
# 5. reboot and test of the kernel is working
# 6a. if so mark the commit as good
git bisect good
# 6b. else mark it as bad
git bisect bad
# 7. repeat steps 4-6 until git has identified the problematic commit
Comment 5 Richard Bradfield 2015-07-27 20:43:43 UTC
I believe that the patch proposed in 91041 [1,2] will resolve this.

This bug seems to be caused by an early attempt to access the afmt property of the encoder before it has been initialised. The audio detection rework in [2] looks like it should avoid this corner case.

Andreas, can you try the patch linked as [2]?

[1] https://bugs.freedesktop.org/show_bug.cgi?id=91041
[2] https://bugs.freedesktop.org/attachment.cgi?id=117395
Comment 6 Andreas Tunek 2015-07-28 09:54:52 UTC
I applied the patch you emailed me, should I try this one as well?
Comment 7 Richard Bradfield 2015-07-28 09:57:38 UTC
Yes, I suggest you try it just to confirm that the issue doesn't reappear with the new audio detect code in place.
Comment 8 Andreas Tunek 2015-07-30 11:23:49 UTC
The linked patch works as well. Should I change the status of this bug?
Comment 9 Alex Deucher 2015-07-30 13:52:16 UTC

*** This bug has been marked as a duplicate of bug 91041 ***

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.