When KMS is enable on a dual-monitor configuration (either DVI or DP) plymouthd aborts after kernel oops in drm module.
Platform is a Dell Latitude E6500 laptop with Ubuntu 11.04 alpha1, alpha2, beta1, and beta2 builds.
If I disable KMS at boot time with nomodeset, the problem goes away but then again so does xrandr support for the dual-monitors.
Screenshots of kernel oops:
The usual question is which kernel is that? Can you produce with the kernel from the mainline repository (or even one from xorg-edgers)?
Created attachment 45723 [details] [review]
Defend against a NULL crtc
So this looks to be the most likely explanation. But first you need to get a mainline (or equivalent) so that you can patch and test. :)
This is a difficult proposition. My laptop is currently running Ubuntu 10.10--which is working mostly well for my daily work. I found this bug by using the Ubuntu 11.04 Live alpha and beta discs to see if 11.04 is viable (which at this point it is not because of this bug). I cannot simply wipe out my laptop to install 11.04 with the prospect of it not working as it would affect my ability to work. I am open to ideas though. Please let me know what you think.
Build the kernel for your normal installation and remove it afterwards. It should hit the same bug as it looks to be before userspace starts.
I compiled the vanilla 188.8.131.52 kernel and ran into this problem on my existing system. I will apply the patch an compile again tonight or tomorrow and see if that remedies it.
I am able to use the vanilla 184.108.40.206 kernel on my dual DVI configuration at home while I get the kernel oops at work (with the two DP monitors). When I boot from the Live CDs I have the problem whether it is DVI or DP. Does that make sense to you?
Regardless, I will try patching the kernel, recompiling, and testing on my DP configuration tomorrow.
Yeah, AIUI, the OOPS requires the DP to be activated by the BIOS on the second pipe and then we try to disable it without setting it up (and so deref a NULL pointer).
Booted with no oops on DP this morning with the patched kernel. Looks like this solves the problem. Need to get the Ubuntu team to pick up this patch before they GM. Do you have contacts to do that?
With your positive feedback from testing, I've earmarked the patch for stable, so it should feed quickly into the distributions.
On Wed, Apr 20, 2011 at 10:43 AM, <email@example.com> wrote:
> --- Comment #10 from Chris Wilson <firstname.lastname@example.org> 2011-04-20
> 08:43:49 PDT ---
> With your positive feedback from testing, I've earmarked the patch for
> so it should feed quickly into the distributions.
> Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug.
> You reported the bug.
The patch (rather a variant thereof) is now upstream, closing.