All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paulo Marques <pmarques@grupopie.com>
To: werner@guyane.yi.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.35-rc2,3 -- Problem with PS2 keyboard and mouse driver
Date: Fri, 02 Jul 2010 13:05:57 +0100	[thread overview]
Message-ID: <4C2DD625.2030903@grupopie.com> (raw)
In-Reply-To: <1278041650.12788@guyane.yi.org>

werner@guyane.yi.org wrote:
> 2.6.35-rc2,3,3-git1 -- Problem with PS2 keyboard and mouse driver
> 
> That problem continues at -git6 .
> 
> Since 2.6.35-rc2 the USB keyboard driver don't work longer, on
> different mainboards and keyboards.
> 
> On 2.6.35-rc1 things still were (more or less) normal.
> 
> THIS IS AN ERROR WHICH ENTERED BETWEEN 2.6.35 -rc1 and -rc2 !!

The address 07200720 looks like a couple of gray spaces in a vga console
and I've seen that before not long ago.

After a bit of searching, I've found it: it's in the thread that started
with "Linux 2.6.35-rc2", and most importantly in the thread:

BUG kmalloc-4096: Poison overwritten (2.6.35-rc2)

where there is a patch that is supposed to fix this. I thought this was
already applied upstream, though...

For your convenience, the patch in that thread is this one (might be
white space mangled, as I just copy+pasted it, so you might need to
apply it by hand):

---
 drivers/char/vt.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/char/vt.c b/drivers/char/vt.c
index 1296c42..e123958 100644
--- a/drivers/char/vt.c
+++ b/drivers/char/vt.c
@@ -304,8 +304,8 @@ static void scrup(struct vc_data *vc, unsigned int
t, unsigned int b, int nr)
 	d = (unsigned short *)(vc->vc_origin + vc->vc_size_row * t);
 	s = (unsigned short *)(vc->vc_origin + vc->vc_size_row * (t + nr));
 	scr_memmovew(d, s, (b - t - nr) * vc->vc_size_row);
-	scr_memsetw(d + (b - t - nr) * vc->vc_size_row, vc->vc_video_erase_char,
-		    vc->vc_size_row * nr);
+	scr_memsetw((void *)d + (b - t - nr) * vc->vc_size_row,
+			vc->vc_video_erase_char, vc->vc_size_row * nr);
 }

 static void scrdown(struct vc_data *vc, unsigned int t, unsigned int b,
int nr)



  reply	other threads:[~2010-07-02 12:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-02  3:34 2.6.35-rc2,3 -- Problem with PS2 keyboard and mouse driver werner
2010-07-02 12:05 ` Paulo Marques [this message]
2010-07-02 20:41   ` werner
2010-07-03 18:20 ` Maciej Rutecki
  -- strict thread matches above, loose matches on Subject: below --
2010-07-10  2:12 werner
2010-07-11 22:21 ` Randy Dunlap
     [not found] <1278618295.14439@sys-linux.yi.org>
2010-07-08 23:22 ` Dmitry Torokhov
2010-07-09 23:02   ` H. Peter Anvin
2010-07-09 23:24     ` Dmitry Torokhov
2010-07-10  0:25       ` H. Peter Anvin
2010-07-08  4:25 werner
2010-07-08  6:14 ` Dmitry Torokhov
2010-06-29  1:10 werner

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=4C2DD625.2030903@grupopie.com \
    --to=pmarques@grupopie.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=werner@guyane.yi.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.