public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Morten Helgesen <admin@nextframe.net>
To: Terje Dalen <t.dalen@no.parkairsystems.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM:  Kernel link problem (block.o)
Date: Tue, 20 Nov 2001 10:57:55 +0100	[thread overview]
Message-ID: <20011120105755.V8184@sexything> (raw)
In-Reply-To: <766E81E1DE3AD411BAD400508B6B830B09DD46@mailserver.parkairsystems.net>
In-Reply-To: <766E81E1DE3AD411BAD400508B6B830B09DD46@mailserver.parkairsystems.net>

Hey, Terje!

Just remove the two references to deactivate_page. 

== Morten

On Tue, Nov 20, 2001 at 09:19:49AM +0100, Terje Dalen wrote:
> Hi, 
> 
> I have upgraded the kernel from 2.4.8 to 2.4.14 due freezing problems
> with 2.4.8 (I think there must have been a deadlock with the memory/swap
> handling. It only worked for 10 minutes to 6 hours). 
> 
> My link problem started when I recompiled the kernel with
> 
> CONFIG_BLK_DEV_LOOP = y
> 
> and get the following problem:
> 
> ld -m elf_i386 -T /usr/src/linux-2.4.14/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/char/drm/drm.o
> drivers/net/fc/fc.o drivers/net/appletalk/appletalk.o
> drivers/net/tokenring/tr.o drivers/net/wan/wan.o drivers/atm/atm.o
> drivers/ide/idedriver.o drivers/cdrom/driver.o drivers/pci/driver.o
> drivers/net/wireless/wireless_net.o drivers/pnp/pnp.o drivers/video/video.o
> drivers/net/hamradio/hamradio.o drivers/md/mddev.o \
>         net/network.o \
>         /usr/src/linux-2.4.14/arch/i386/lib/lib.a
> /usr/src/linux-2.4.14/lib/lib.a /usr/src/linux-2.4.14/arch/i386/lib/lib.a \
>         --end-group \
>         -o vmlinux
> drivers/block/block.o: In function `lo_send':
> drivers/block/block.o(.text+0xb2e9): undefined reference to
> `deactivate_page'
> drivers/block/block.o(.text+0xb325): undefined reference to
> `deactivate_page'
> 
> 
> I can see from in the changelog that the swap.h have been changed and the 
> deactivate_page function has been removed. I guess someone forgot to update
> the loop.c file. Is there a patch available for the correction of loop.c?
> 
> When I compiled the kernel as a module I was able to install and run the
> kernel
> and actually my system have been stable for the last 14 hours.
> 
> Best regards
> Terje
> 
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
mvh
Morten Helgesen 
UNIX System Administrator & C Developer 
Nextframe AS
admin@nextframe.net / 93445641
http://www.nextframe.net

      parent reply	other threads:[~2001-11-20  9:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-20  8:19 PROBLEM: Kernel link problem (block.o) Terje Dalen
2001-11-20  9:45 ` Adrian Bunk
2001-11-20  9:57 ` Morten Helgesen [this message]

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=20011120105755.V8184@sexything \
    --to=admin@nextframe.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=t.dalen@no.parkairsystems.com \
    /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