On Mon, 2008-05-05 at 10:15 +0200, Michel Dänzer wrote: > On Sun, 2008-05-04 at 21:12 -0400, Miles Lane wrote: > > When I boot this kernel, everything seems okay, but after I leave the > > machine for 30 minutes or so, I come back and find the machine locked > > up. > > Define 'locked up'. Can you ping it? Can you log in via ssh? Is the X > server still alive? Where is it stuck? ... > > > > When I checked my log file after rebooting, I find the log filled with > > "trying to get vblank count for disabled pipe 0". > > [...] > > > May 4 14:40:44 whirligig kernel: [ 47.544109] ALSA > > sound/pci/hda/hda_codec.c:716: hda_codec_setup_stream: NID=0x12, > > stream=0x5, channel=0, format=0x4011 > > May 4 14:40:46 whirligig kernel: [ 48.850489] trying to get vblank count > > for disabled pipe 0 > > May 4 14:40:46 whirligig kernel: [ 48.897990] trying to get vblank count > > for disabled pipe 0 > > May 4 14:40:46 whirligig kernel: [ 48.941691] trying to get vblank count > > for disabled pipe 0 > > May 4 14:40:46 whirligig kernel: [ 49.003556] trying to get vblank count > > for disabled pipe 0 > > May 4 14:40:46 whirligig kernel: [ 49.147880] trying to get vblank count > > for disabled pipe 0 > > May 4 14:40:47 whirligig kernel: [ 50.528654] trying to get vblank count > > for disabled pipe 0 > > [...] > > May 4 15:36:23 whirligig kernel: [ 3404.847515] ALSA > > sound/pci/hda/hda_codec.c:728: hda_codec_cleanup_stream: NID=0xe > > May 4 16:06:53 whirligig kernel: [ 5241.488711] trying to get vblank count > > for disabled pipe 1 > > May 4 16:06:53 whirligig kernel: [ 5241.488748] trying to get vblank count > > for disabled pipe 1 > > May 4 16:06:53 whirligig kernel: [ 5241.496130] trying to get vblank count > > for disabled pipe 1 > > May 4 16:06:53 whirligig kernel: [ 5241.516053] trying to get vblank > > count for disabled pipe 1 > > Note that some of these are for pipe 1 as well as pipe 0. Does the > problem only occur for one of them? Miles isn't alone, I also get 'trying to get vblank count for disabled pipe 0' (GM965). vblank interrupts were previously not working for me, but they are now. I'm not sure what's changed. > > Do you have any GL apps running when this happens? > For me, this happens every time a GL app is run.
I'm also getting occasional lockups. Often it's the window manager (metacity) that locks up when attempting to move a window, restarting the window manager unlocks X but attempting to move a window again results in another lockup. When it's locked up the pointer moves and vt switching works but nothing else. Other times I've had a hard lockup that required a hard reboot, this happens less frequently. ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
