From: Andrew Morton <akpm@digeo.com>
To: Alexander Hoogerhuis <alexh@ihatent.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.64-mm6
Date: Fri, 14 Mar 2003 03:55:32 -0800 [thread overview]
Message-ID: <20030314035532.3fb6e351.akpm@digeo.com> (raw)
In-Reply-To: <87bs0eqors.fsf@lapper.ihatent.com>
Alexander Hoogerhuis <alexh@ihatent.com> wrote:
>
> I've used tried the -mm-kernels since they've actually made
> 2.5-kernels usable on my laptop lately (Compaq Evo800c), but
> 2.5.64-mm2 and onwards doesnt work with X anymore. I run 4.3.0-r1 from
> the Gentoo unstable "branch".
>
> with -mm1 I X coming up just nicely, and now the screen just goes
> black after trying to start X, and it seems related to DRM.
I have a radeon card here. Just tried it. The X server starts up OK but as
soon as I run tuxracer, some ioctl down in the radeon driver keeps on timing
out waiting for the FIFO, spins for ten milliseconds in-kernel and the X
server immediately calls the ioctl again. The whole thing is bust. I went
all the way back to 2.5.39, where it is still bust. 2.4.21-pre5 is OK
though.
So it looks like my breakage is different from yours.
Could you please try just 2.5.64 plus
http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.64/2.5.64-mm6/broken-out/linus.patch
That will tell us if it is a -mm bug or a -linus bug.
It it is the latter, and if you're feeling really keen then could you search through the patches at
http://www.zip.com.au/~akpm/linux/patches/2.5/badari/
and work out exactly which one introduced the problem?
Each of those patches is against 2.5.64. The chronological order is:
cset-1.1085-to-1.1085.txt.gz
cset-1.1085-to-1.1086.txt.gz
cset-1.1085-to-1.1089.txt.gz
cset-1.1085-to-1.1090.txt.gz
cset-1.1085-to-1.1091.txt.gz
cset-1.1085-to-1.1094.txt.gz
cset-1.1068.1.17-to-1.1075.txt.gz
cset-1.1068.1.17-to-1.1077.txt.gz
cset-1.1068.1.17-to-1.1106.txt.gz
cset-1.1068.1.17-to-1.1107.txt.gz
cset-1.1068.1.17-to-1.1110.txt.gz
cset-1.1068.1.17-to-1.1122.txt.gz
cset-1.1068.1.17-to-1.1123.txt.gz
cset-1.1068.1.17-to-1.1124.txt.gz
cset-1.1068.1.17-to-1.1125.txt.gz
cset-1.1068.1.17-to-1.1127.txt.gz
cset-1.1068.1.17-to-1.1131.txt.gz
cset-1.1068.1.17-to-1.1137.txt.gz
cset-1.1068.1.17-to-1.1160.txt.gz
cset-1.1068.1.17-to-1.1166.txt.gz
cset-1.1068.1.17-to-1.1168.txt.gz
cset-1.1068.1.17-to-1.1171.txt.gz
cset-1.1068.1.17-to-1.1173.txt.gz
cset-1.1068.1.17-to-1.1174.txt.gz
cset-1.1068.1.17-to-1.1175.txt.gz
cset-1.1068.1.17-to-1.1177.txt.gz
cset-1.1068.1.17-to-1.1101.txt.gz
cset-1.1068.1.17-to-1.1113.txt.gz
cset-1.1068.1.17-to-1.1119.txt.gz
cset-1.1068.1.17-to-1.1147.txt.gz
cset-1.1068.1.17-to-1.1154.txt.gz
cset-1.1068.1.17-to-1.1157.txt.gz
Thanks.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
next prev parent reply other threads:[~2003-03-14 11:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-13 11:26 2.5.64-mm6 Andrew Morton
2003-03-13 16:23 ` 2.5.64-mm6 Jeremy Fitzhardinge
2003-03-13 19:34 ` 2.5.64-mm6 Andrew Morton
2003-03-13 20:07 ` 2.5.64-mm6 Roger Larsson
2003-03-14 3:04 ` 2.5.64-mm6 Steven Cole
2003-03-14 3:28 ` 2.5.64-mm6 Andrew Morton
2003-03-14 3:46 ` 2.5.64-mm6 Shawn
2003-03-14 3:51 ` 2.5.64-mm6 Andrew Morton
2003-03-14 3:56 ` 2.5.64-mm6 Robert Love
2003-03-13 20:35 ` 2.5.64-mm6 Thomas Molina
2003-03-14 9:29 ` 2.5.64-mm6 Alexander Hoogerhuis
2003-03-14 11:55 ` Andrew Morton [this message]
2003-03-15 8:38 ` 2.5.64-mm6 Alexander Hoogerhuis
2003-03-14 12:01 ` 2.5.64-mm6 Helge Hafting
2003-03-14 12:14 ` 2.5.64-mm6 Andrew Morton
2003-03-14 20:38 ` 2.5.64-mm6 Eli Carter
2003-03-14 20:53 ` 2.5.64-mm6 Andrew Morton
2003-03-14 22:01 ` 2.5.64-mm6 Eli Carter
2003-03-14 22:21 ` 2.5.64-mm6 Andrew Morton
2003-03-13 13:42 2.5.64-mm6 Felipe Alfaro Solana
2003-03-13 21:49 2.5.64-mm6 Felipe Alfaro Solana
2003-03-14 0:23 ` 2.5.64-mm6 Thomas Molina
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=20030314035532.3fb6e351.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=alexh@ihatent.com \
--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