From: Thomas Schlichter <schlicht@uni-mannheim.de>
To: Helge Hafting <helgehaf@aitel.hist.no>,
James Simmons <jsimmons@infradead.org>
Cc: Andrew Morton <akpm@osdl.org>,
Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: 2.6.0-test8-mm1
Date: Tue, 21 Oct 2003 22:36:29 +0200 [thread overview]
Message-ID: <200310212236.41476.schlicht@uni-mannheim.de> (raw)
In-Reply-To: <20031021202310.GA14993@hh.idb.hist.no>
[-- Attachment #1: Type: text/plain, Size: 1042 bytes --]
On Tuesday 21 October 2003 22:23, Helge Hafting wrote:
> On Tue, Oct 21, 2003 at 06:47:41PM +0100, James Simmons wrote:
> > Okay I see people are having alot of problems in the -mm tree. I don't
> > have any problems but I'm working against Linus tree. Could people try
> > the patch against 2.6.0-test8 and tell me if they still have the same
> > results.
>
> This patch was fine. 2.6.0-test8 with this patch booted and
> looked no different from plain 2.6.0-test8. I am using it for
> writing this. The problems must be in mm1 somehow.
>
> Helge Hafting
Well here I've got same problems for -test8 + fbdev-patch as with -test8-mm1.
I've compiled the kernel with most DEBUG_* options enabled (all but
DEBUG_INFO and KGDB) and see the same cursor and image corruption as with
-mm1 and the same options enabled.
Should I try compiling this kernel without the DEBUG_* options and watch if I
get the invalidate_list Oops again?
I use vesafb on a Nvidia GeForce 2 MX 440 with 64MB Video-RAM.
Regards
Thomas
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-10-21 20:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-20 9:05 2.6.0-test8-mm1 Andrew Morton
2003-10-20 11:18 ` 2.6.0-test8-mm1 Thomas Schlichter
2003-10-20 15:32 ` 2.6.0-test8-mm1 John Cherry
2003-10-20 16:11 ` 2.6.0-test8-mm1 Thomas Schlichter
2003-10-20 21:48 ` 2.6.0-test8-mm1 Andrew Morton
2003-10-20 22:01 ` 2.6.0-test8-mm1 Thomas Schlichter
2003-10-20 22:17 ` 2.6.0-test8-mm1 Andrew Morton
2003-10-20 22:30 ` 2.6.0-test8-mm1 Thomas Schlichter
2003-10-21 0:43 ` 2.6.0-test8-mm1 Thomas Schlichter
2003-10-21 0:14 ` 2.6.0-test8-mm1 Valdis.Kletnieks
2003-10-21 0:27 ` 2.6.0-test8-mm1 Andrew Morton
2003-10-21 0:46 ` 2.6.0-test8-mm1 Valdis.Kletnieks
2003-10-21 1:56 ` 2.6.0-test8-mm1 Andrew Morton
2003-10-21 2:54 ` 2.6.0-test8-mm1 Valdis.Kletnieks
2003-10-21 3:49 ` 2.6.0-test8-mm1 Jeremy Fitzhardinge
2003-10-21 8:39 ` 2.6.0-test8-mm1 Thomas Schlichter
2003-10-21 17:47 ` 2.6.0-test8-mm1 James Simmons
2003-10-21 20:23 ` 2.6.0-test8-mm1 Helge Hafting
2003-10-21 20:36 ` Thomas Schlichter [this message]
2003-10-21 20:42 ` 2.6.0-test8-mm1 James Simmons
2003-10-21 22:53 ` 2.6.0-test8-mm1 Thomas Schlichter
2003-10-21 23:27 ` 2.6.0-test8-mm1 Robert Love
2003-10-22 2:46 ` 2.6.0-test8-mm1 Valdis.Kletnieks
2003-10-20 19:21 ` [BUG] 2.6.0-test8-mm1 Ramón Rey Vicente
2003-10-20 20:10 ` Andrew Morton
2003-10-20 21:53 ` Ramón Rey Vicente
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=200310212236.41476.schlicht@uni-mannheim.de \
--to=schlicht@uni-mannheim.de \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@osdl.org \
--cc=helgehaf@aitel.hist.no \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox