From: "François Cami" <stilgar2k@wanadoo.fr>
To: bredroll@atari.org
Cc: linux-kernel@vger.kernel.org, axboe@suse.de
Subject: Re: Kernel 2.4.14 compile fail (block.o)
Date: Tue, 13 Nov 2001 04:05:43 +0100 [thread overview]
Message-ID: <3BF08E07.3010003@wanadoo.fr> (raw)
In-Reply-To: <20011112160632.A11922@earth.dsh.org.uk>
Known bug - patch is in 2.4.15pre1
Beware, in pre1 and pre2 netfilter (iptables)
doesn't work.
François
Ian Norton wrote:
> Hi :-),
>
> -- One Liner: make dep is fine but block.o fails to compile
>
> --Problem:
> Make menuconfig for a pretty standard kernel, set for no driver modules, make
> bzImage fails at block.o,
>
> # drivers/block/block.o: In function `lo_send':
> # drivers/block/block.o(.text+0x895f): undefined reference to `deactivate_page'
> # drivers/block/block.o(.text+0x89a9): undefined reference to `deactivate_page'
>
> The currently running system is going along just fine with 2.4.2 no problems
> at all, good uptime,
> Ive built plenty of kernels easily before, ive re created this problem on three
> machines with very different linux setups (kernel, distro, gcc version..)
>
> (menuconfigs saved and attached as bloc.o-fail.gz)
>
> --- /proc/version
> Linux version 2.4.2 (root@orion.dsh.org.uk) (gcc version 2.95.3 19991030
> (prerelease)) #8 Thu Oct 4 15:59:45 BST 2001
>
> --- ver_linux
> linux orion.dsh.org.uk 2.4.2 #8 Thu Oct 4 15:59:45 BST 2001 i686 unknown
> Gnu C 2.95.3
> Gnu make 3.79.1
> binutils 2.10.0.24
> util-linux 2.10b
> mount 2.11b
> modutils 2.4.3
> e2fsprogs 1.19
> PPP 2.3.10
> Linux C Library 2.2.2
> Dynamic linker (ldd) 2.2.2
> Procps 2.0.7
> Net-tools 1.59
> Console-tools 0.2.2
> Sh-utils 2.0
> Modules Loaded
>
> --- host info
> Machine Spec
> CPU : 1x AMD Duron 800Mhz
> RAM : 128Mb PC133
> M/B : GIGABYTE (VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 3))
>
> --- /proc/cpuinfo
> processor : 0
> vendor_id : AuthenticAMD
> cpu family : 6
> model : 3
> model name : AMD Duron(tm) Processor
> stepping : 1
> cpu MHz : 800.042
> cache size : 64 KB
> fdiv_bug : no
> hlt_bug : no
> f00f_bug : no
> coma_bug : no
> fpu : yes
> fpu_exception : yes
> cpuid level : 1
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
> pat pse36 mmx fxsr syscall mmxext 3dnowext 3dnow
> bogomips : 1595.80
>
> --- lspci -vvv included as gzip
> --- no scsi in system
> --- no modules loaded at all (ever)
>
> Hope this has been a helpful bug report
>
> Ian Norton
>
next prev parent reply other threads:[~2001-11-13 14:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-12 16:06 Kernel 2.4.14 compile fail (block.o) Ian Norton
2001-11-13 3:05 ` François Cami [this message]
2001-11-14 22:50 ` Adrian Bunk
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=3BF08E07.3010003@wanadoo.fr \
--to=stilgar2k@wanadoo.fr \
--cc=axboe@suse.de \
--cc=bredroll@atari.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox