From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dmitry Torokhov Subject: Re: [Bug #14388] keyboard under X with 2.6.31 Date: Mon, 12 Oct 2009 16:46:41 -0700 Message-ID: <20091012234641.GF8345@core.coreip.homeip.net> References: <56acieJJ2fF.A.nEB.Hzl0KB@chimera> <87ljjgfcbu.fsf@spindle.srvr.nix> <20091013003841.6c2988d0@lxorguk.ukuu.org.uk> Mime-Version: 1.0 Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject :message-id:references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=ERrg5BJv3nf4weOYzZpno3E/pH11B6oPKMrP5MJR1wI=; b=wMvSfbDcSIgxbcT/qNB48A3LR7Bm6GVR1kUMx4ZzN1TNUIQoy/lxt1LbMRE3xs7DDn aXLwgFfZ9PoVgILLvVM43Dwa/mSMZZPH3vUmKHvwDXOcxjXppL9IdHAftsRo4BmAwN+/ gh/vXsmh39A1mLp2gD953Z5951TsH13MharHs= Content-Disposition: inline In-Reply-To: <20091013003841.6c2988d0-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org> Sender: kernel-testers-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Alan Cox Cc: Nix , "Justin P. Mattock" , "Rafael J. Wysocki" , Linux Kernel Mailing List , Kernel Testers List , Boyan , Ed Tomlinson , =?iso-8859-1?B?RnLpZOlyaWMgTC4gVy4=?= Meunier , Linus Torvalds , OGAWA Hirofumi On Tue, Oct 13, 2009 at 12:38:41AM +0100, Alan Cox wrote: > > So it seems likely to me that this is a kernel bug, somewhere, and the > > TTY layer seems like a good place to look (OK, a horrible place, but a > > *likely* place). > > Somewhere around 2.6.29-30 various things went funny in the keyboard > layer for me - notably characters "bleeding" across console switches. > What do you mean by "bleeding"? Are you sure it is not autorepeat kicking in? > > > > I'm about to try reverting the suggested commit and will report back. I > > see this failure about once a day, so I'll give it three days to go > > wrong and then (if it doesn't) will presume it works and so inform you. > > > > > > (Of course with this commit reverted Emacsen start dropping data from > > their ptys, and as bad luck would have it I live in (X)Emacs, but that's > > on a different machine! so I can have my compile buffer data *and* not > > destroy X ;} ) > > X doesn't touch the pty layer. It touches vt (extensively) and the input > layers. It's vt/kbd access is also very raw so bypasses much of that > layer. That isn't to say tty isn't the cause but look for input layer > changes too. -- Dmitry