On Wed, 22 Jul 2009 20:43:56 +0200 Alberto Gonzalez <alberto6674@xxxxxxxxx> wrote: > On Wednesday 22 July 2009 19:12:51 Jesse Barnes wrote: > > Ah I must have been looking at the wrong register. This one makes > > it look like one of your HDMI hotplug bits is getting stuck (HDMIC > > in particular). This might not even be wired up on your platform... > > Yes, I don't use HDMI, my screen is attached via VGA > > > > This test hack should prevent us from responding to those > > interrupts... > > I've been hitting it hard for over an hour with all the usual tricks > to trigger it (and a few reboots) and I've been unable to reproduce > the problem with this patch. Before I could trigger it reliably in a > few minutes, so I'm pretty sure this patch fixes it. If something new > comes up, I'll let you know anyway. Hm, so this type of interrupt problem is *supposed* to be handled by setting of the PEG_BAND_GAP_DATA reg (low bits set to 0xd). Do you have that in your tree? Does git master have this problem? Maybe we need to add a patch to 2.6.30.x to set PEG_BAND_GAP_DATA as a workaround (git master already has code to do this properly for HDMI and DP outputs afaict). -- Jesse Barnes, Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
