On Fri, 1 Jul 2005, Lee Revell wrote: > On Fri, 2005-07-01 at 18:46 -0700, William Weston wrote: > > FWIW, I'm still seeing the SMT scheduling? meltdown issues with > > -50-42. > > Running two instances of 'dd if=/dev/zero of=/dev/null bs=65536' > > instead > > of 'burnP6' results in the same behavior. Here's a quick recap: > > > > - Start (or login to ) X. > > - Start an X app that constantly updates the screen, like wmcube, or > > vlc. > > Which video driver is X using? What nice value is the X server running > at?
Hardware is Intel 82865G (integrated) with DRM i915 1.1.0 20040405 and xorg-3.8.2 i810 driver, running at nice 0, priority 15. Should I bump the priority up? To realtime? > Does adding: > > Option "NoAccel" > > to the Device section of your X config file make any difference? Disabling the dri and drm modules didn't help. I'll turn on NoAccel when I'm back in the office on Tuesday. > (on most systems X is the only thing besides the kernel that can access > hardware directly, which can cause problems) So would running X through the framebuffer device be the way to go for stability under realtime? It's been a couple years since I've used fb. --ww - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/