| Summary: | Regression: Can't boot on 4.0.5 and later but can boot on 4.0.4 (on iMac) | ||
|---|---|---|---|
| Product: | DRI | Reporter: | Andreas Tunek <andreas.tunek> |
| Component: | DRM/Radeon | Assignee: | Default DRI bug account <dri-devel> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | critical | ||
| Priority: | medium | CC: | bradfirj |
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | Linux (All) | ||
| See Also: | https://bugzilla.kernel.org/show_bug.cgi?id=101131 | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Andreas Tunek
2015-07-07 08:34:32 UTC
Please include the relevant information here directly. Price question: Can you bisect? If 4.0.5 is bad and 4.0.4 still works that should be pretty much straight forward. Do you know any guide on how to bisect while using Fedora? 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 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 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 I applied the patch you emailed me, should I try this one as well? Yes, I suggest you try it just to confirm that the issue doesn't reappear with the new audio detect code in place. The linked patch works as well. Should I change the status of this bug? |
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.