On Sun, 2008-05-04 at 21:12 -0400, Miles Lane wrote:
quoted text
> 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? ...


quoted text
> When I checked my log file after rebooting, I find the log filled with "trying to get vblank count for disabled pipe 0".

[...]

quoted text
> 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?

Do you have any GL apps running when this happens?


-- 
Earthling Michel Dänzer           |          http://tungstengraphics.com
Libre software enthusiast         |          Debian, X and DRI developer

--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/