DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:date:from:to:cc:subject:message-id:references:mime-version:content-type:content-disposition:in-reply-to:user-agent;
        b=OzQgEELvgyu4TOTNwzVH7zdEOZuSc3eL7X+LkQfRmavSjB9e9o38iNpoXAQk8pSinaOt6MZ4fxGW8/oWlPtAGI4JEoxUyewsD/xfj1T9ggfRbdkOjtZAoEZZoVd/8lNmojWUNUM4IdLPVQt/ubr2gT3LI8PGYV52WwJ7jq4HXkw=
Date: Wed, 11 Jan 2006 18:38:22 +0300
From: Alexey Dobriyan <adobriyan@gmail.com>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.15-$SHA1: VT <-> X sometimes odd
Message-ID: <20060111153822.GA7879@mipter.zuzino.mipt.ru>
References: <20060110162305.GA7886@mipter.zuzino.mipt.ru> <43C4F114.9070308@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <43C4F114.9070308@gmail.com>
User-Agent: Mutt/1.5.11
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2290
Lines: 53

On Wed, Jan 11, 2006 at 07:50:44PM +0800, Antonino A. Daplas wrote:
> Alexey Dobriyan wrote:
> > Approximate sequence of event:
> >
> > 1. script which builds allmodconfig on 11 targets is left on otherwise
> >    idle machine. Logged in on VT1. Logged of X.
> > 2. After 5 hours I return, ensure script behaves OK, switch to X and see
> >    black screen.
> > 3. Now, trying to switch between VTs and X gives nothing but black
> >    screen.
> > 4. Alt+SysRq+K. After several seconds black screen switches to black
> >    screen with text cursor in the upper-left corner.
> > 5. Futher attempts to switch and SysRq+Ki'ing gave nothing.
> > 6. In a minute or so X login prompt reappeared. Mouse os OK. Keyboard is
> >    not. In particular, typing username doesn't work.
> > 7. By some miracle, typing became OK (probably after I hit Ctrl, not
> >    sure). I login to X successfully and fire up mutt to mail bugreport.
> > 8. Devil turned me to switch to VT again...
> > 9. goto #5.
> > 10. Cold reboot.
>
> Can you reproduce this with another X driver, for example, vesa or
> fbdev, and/or with another console driver? Maybe you can also try with
> DRI enabled and disabled?

OK, I'll try.

> > The overall feeling is that X left without human interaction starts to
> > reacts slooowly (probably after blanking kicks in?).
>
> That's also what I'm thinking, console blanking, X blanking, or power
> management. You might want to shorten the console blanking interval with:
>
> setterm -blank 1.

Strange freezing continues, probably blanking should be left alone:

1. while reading random patches with gitk with nothing more running. gitk
   already read all patch headers from the whole Linux git archive.

   gitk stops reacting on mouse clicks
   "Ctrl+Alt+1" (switching to virtual desktop #1 in evilwm) -- OK
   "Ctrl+Alt+2" (back) -- gitk shows its window but without actual
   content as if something can't get a timeslice for redraw.

2. Two allmodconfig builds in parallel. mutt downloading email, /me
   lazily browsing with Firefox.

-
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/