From: "Andreas Möller" <andreas-moeller@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: Re: -aa VM splitup
Date: Wed, 03 Apr 2002 02:37:53 +0200 [thread overview]
Message-ID: <3CAA4EE1.1060502@gmx.net> (raw)
Hello,
I have patched a stock 2.4.19-pre5 kernel with Andrew Morton's -aa
VM splitup [1], Ingo Molnar's O(1) scheduler [2], Andrew Morton's read
latency [3] and IDE lockup patches [4] and the mini low latency patch
[5] plus fixes for it [6] (in this order). When running ps or top under
this kernel, I get following error messages:
{vmalloc_to_page} {GPLONLY_vmalloc_to_page}
Warning: /boot/System.map does not match kernel data.
I made sure that I didn't forget to copy the new System.map. Perhaps
some symbol needs to be exported?
Andreas
--
[1] http://www.zip.com.au/~akpm/linux/patches/2.4/2.4.19-pre5/aa1/
[2]
http://people.redhat.com/~mingo/O(1)-scheduler/sched-O1-2.4.18-pre8-K3.patch
[3]
http://www.zip.com.au/~akpm/linux/patches/2.4/2.4.19-pre5/read-latency2.patch
[4]
http://www.zip.com.au/~akpm/linux/patches/2.4/2.4.19-pre5/ide-lockup.patch
[5]
http://giga.cps.unizar.es/~magallon/linux/kernel/2.4.19-pre5-jam2/23-lowlatency-mini.gz
[6]
http://giga.cps.unizar.es/~magallon/linux/kernel/2.4.19-pre5-jam2/24-lowlatency-fixes-5.gz
next reply other threads:[~2002-04-03 0:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-03 0:37 Andreas Möller [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-20 3:53 -aa VM splitup Andrew Morton
2002-03-31 12:26 ` Mike Galbraith
2002-04-01 1:02 ` Andrea Arcangeli
2002-04-01 1:52 ` Andrew Morton
2002-04-01 2:29 ` Andrea Arcangeli
2002-04-01 12:07 ` Mike Galbraith
2002-04-01 18:02 ` Andrea Arcangeli
2002-04-01 19:02 ` Mike Galbraith
2002-04-01 23:25 ` Marcelo Tosatti
2002-04-02 4:06 ` Mike Galbraith
2002-04-02 7:28 ` Mike Galbraith
2002-04-02 19:25 ` Andrea Arcangeli
2002-04-03 5:28 ` Mike Galbraith
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=3CAA4EE1.1060502@gmx.net \
--to=andreas-moeller@gmx.net \
--cc=linux-kernel@vger.kernel.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.