On Mon, May 5, 2008 at 4:15 AM, Michel Dänzer
<[EMAIL PROTECTED]> 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? ...
I don't know if I can ping the machine. I can work on finding that
out. I don't have an ssh server running, but can try that. I can't
tell if X is running. The screen remains black.
> > 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?
I just checked my dmesg output and found this:
[ 7196.890661] trying to get vblank count for disabled pipe 0
[ 7258.233274] trying to get vblank count for disabled pipe 1
[ 7258.233963] trying to get vblank count for disabled pipe 1
[ 7261.219671] trying to get vblank count for disabled pipe 0
[ 7261.234483] trying to get vblank count for disabled pipe 0
So, since I am still using this boot session and haven't noticed
anything lock up, it seems that getting either of these messages is
not necessarily the indicator of what is keeping my screen black after
the display has gone to sleep. I have not let the display go to sleep
yet during this boot session, so I don't know what will happen when it
does. I suspicion is that this is the trigger condition.
Miles
-------------------------------------------------------------------------
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
