From: Greg KH <greg@kroah.com>
To: Marcin Slusarz <marcin.slusarz@gmail.com>
Cc: "Frédéric L. W. Meunier" <fredlwm@gmail.com>,
"Linux Kernel" <linux-kernel@vger.kernel.org>,
edt@aei.ca, hirofumi@mail.parknet.co.jp, alan@linux.intel.com,
"Greg Kroah-Hartman" <gregkh@suse.de>
Subject: Re: keyboard under X with 2.6.31
Date: Thu, 15 Oct 2009 11:31:54 -0700 [thread overview]
Message-ID: <20091015183154.GC3921@kroah.com> (raw)
In-Reply-To: <4AD37E05.5010504@gmail.com>
On Mon, Oct 12, 2009 at 09:05:41PM +0200, Marcin Slusarz wrote:
> Frédéric L. W. Meunier wrote:
> > On Sun, 11 Oct 2009, Boyan wrote:
> >
> >> (sending again, sorry about last reply, wrong subject...)
> >> On Sat, 10 Oct 2009 21:00:05 -0400, Ed Tomlinson wrote:
> >>> You are not alone with keyboard problems in 31 in X. In my case I
> >>> blamed a new wireless setup.
> >>> I am building with the the above commit reverted.
> >>
> >> Not sure why, but after reverting
> >> e043e42bdb66885b3ac10d27a01ccb9972e2b0a3 (pty: avoid forcing
> >> 'low_latency' tty flag) my analog tv tuner stopped working after booting
> >> for the first time. It has TV and FM radio, but only radio worked when
> >> reverted this patch. I saw some EIO errors with strace. Then added again
> >> the patch and on top of it I've added commit:
> >>
> >> 3a54297478e6578f96fd54bf4daa1751130aca86
> >> pty: quickfix for the pty ENXIO timing problems
> >>
> >> Everything was ok.
> >> Today I've tried to reproduce this and reverted both patches. Recompiled
> >> and everything is ok. Not sure what happened yesterday.
> >> So to summarize 2.6.31.3 with reverted commit
> >> e043e42bdb66885b3ac10d27a01ccb9972e2b0a3 (pty: avoid forcing
> >> 'low_latency' tty flag) works for me.
> >
> > Reverting the commit also works for me. Thanks.
> >
> > The direct link, for those not using git:
> >
> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=e043e42bdb66885b3ac10d27a01ccb9972e2b0a3
>
> CC'ing Greg K-H
I've now queued up 3a54297478e6578f96fd54bf4daa1751130aca86 for the next
.31-stable release.
thanks for letting me know.
greg k-h
next prev parent reply other threads:[~2009-10-15 18:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-11 6:34 keyboard under X with 2.6.31 Boyan
2009-10-11 20:39 ` Frédéric L. W. Meunier
2009-10-12 19:05 ` Marcin Slusarz
2009-10-15 18:31 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-10-10 20:18 Boyan
2009-10-11 1:00 ` Ed Tomlinson
2009-10-07 20:19 Frédéric L. W. Meunier
2009-10-09 2:38 ` Dmitry Torokhov
2009-10-09 2:55 ` Frédéric L. W. Meunier
2009-10-09 3:19 ` Justin P. Mattock
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091015183154.GC3921@kroah.com \
--to=greg@kroah.com \
--cc=alan@linux.intel.com \
--cc=edt@aei.ca \
--cc=fredlwm@gmail.com \
--cc=gregkh@suse.de \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin.slusarz@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox