I've been building kernels since 2.2.15 or something, and I've never
had problems before, so bear with me.
Where is "deacivate_page" defined? Because, right at the end, I'm
getting:
ld -m elf_i386 -T /usr/src/linux-2.4.14/linux/arch/i386/vmlinux.lds -e stext arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/main.o init/version.o \
--start-group \
arch/i386/kernel/kernel.o arch/i386/mm/mm.o kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o \
drivers/char/char.o drivers/block/block.o drivers/misc/misc.o drivers/net/net.o drivers/media/media.o drivers/ide/idedriver.o drivers/cdrom/driver.o drivers/sound/sounddrivers.o drivers/pci/driver.o drivers/video/video.o arch/i386/math-emu/math.o \
net/network.o \
/usr/src/linux-2.4.14/linux/arch/i386/lib/lib.a /usr/src/linux-2.4.14/linux/lib/lib.a /usr/src/linux-2.4.14/linux/arch/i386/lib/lib.a \
--end-group \
-o vmlinux
drivers/block/block.o: In function `lo_send':
drivers/block/block.o(.text+0xa8ad): undefined reference to `deactivate_page'
drivers/block/block.o(.text+0xa8f9): undefined reference to `deactivate_page'
make: *** [vmlinux] Error 1
So I'm kinda stuck.
--
Tony Reed
<[email protected]>
My "vendor"?. If I wanna _buy_ an OS, I'll buy an Mac.
On Fri, Nov 16, 2001 at 08:58:51PM -0500, Tony Reed wrote:
> I've been building kernels since 2.2.15 or something, and I've never
> had problems before, so bear with me.
>
> Where is "deacivate_page" defined? Because, right at the end, I'm
> getting:
>
> ld -m elf_i386 -T /usr/src/linux-2.4.14/linux/arch/i386/vmlinux.lds -e stext arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/main.o init/version.o \
> --start-group \
> arch/i386/kernel/kernel.o arch/i386/mm/mm.o kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o \
> drivers/char/char.o drivers/block/block.o drivers/misc/misc.o drivers/net/net.o drivers/media/media.o drivers/ide/idedriver.o drivers/cdrom/driver.o drivers/sound/sounddrivers.o drivers/pci/driver.o drivers/video/video.o arch/i386/math-emu/math.o \
> net/network.o \
> /usr/src/linux-2.4.14/linux/arch/i386/lib/lib.a /usr/src/linux-2.4.14/linux/lib/lib.a /usr/src/linux-2.4.14/linux/arch/i386/lib/lib.a \
> --end-group \
> -o vmlinux
> drivers/block/block.o: In function `lo_send':
> drivers/block/block.o(.text+0xa8ad): undefined reference to `deactivate_page'
> drivers/block/block.o(.text+0xa8f9): undefined reference to `deactivate_page'
> make: *** [vmlinux] Error 1
>
>
> So I'm kinda stuck.
There is a problem in loop.c that references deactivate_page. This is
probably related.
deactivate_page by linus in 2.4.14, while it was in 2.4.14-pre8, the last
pre for 2.4.14.... :(
Mike
--- linux-2.4.14/drivers/block/loop.c Thu Oct 25 13:58:34 2001
+++ linux-2.4.14-loop/drivers/block/loop.c Mon Nov 5 17:06:08 2001
@@ -207,7 +207,6 @@
index++;
pos += size;
UnlockPage(page);
- deactivate_page(page);
page_cache_release(page);
}
return 0;
@@ -218,7 +217,6 @@
kunmap(page);
unlock:
UnlockPage(page);
- deactivate_page(page);
page_cache_release(page);
fail:
return -1;
Tony Reed wrote:
> Where is "deacivate_page" defined?
See the discussions on this list for a patch -
or better yet, get the 2.4.15-pre5 patch, which
has fixes for that and several other issues.
>
> My "vendor"?. If I wanna _buy_ an OS, I'll buy an Mac.
If you got your kernels from a Linux vendor,
you would not be having these issues!
cu
jjs
Em Fri, Nov 16, 2001 at 08:58:51PM -0500, Tony Reed escreveu:
> I've been building kernels since 2.2.15 or something, and I've never
> had problems before, so bear with me.
>
> Where is "deacivate_page" defined? Because, right at the end, I'm
> getting:
two options: delete the references to deactivate_page in
drivers/block/loop.c and rebuild your kernel or get the latest 2.4.15
prepatch that has this fixed.
- Arnaldo
On
Tony Reed <[email protected]> wrote:
:I've been building kernels since 2.2.15 or something, and I've never
:had problems before, so bear with me.
Got it. Thanks guys, for your patience and hard work.
$ uname -a
Linux kubrick 2.4.15-pre5 #1 Sat Nov 17 10:28:20 EST 2001 i586 unknown
--
Tony Reed
<[email protected]>