mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ethan Joffe <ethan@toolfoundry.com>
To: linux-kernel@vger.kernel.org
Subject: 2.4.19 unresolved symbols
Date: Tue, 22 Oct 2002 19:17:41 -0700	[thread overview]
Message-ID: <5.1.0.14.0.20021022190139.0375b698@mail.toolfoundry.com> (raw)


I have a dual P3 box with 2Gigs RAM booting off onboard scsi, and I am 
unable to get the latest v2.4.19 kernel to support the hardware fully. I 
can get the kernel working if I do not have it configured for 4G support, 
in which case it only sees 900Megs or so of RAM, but everything works and 
boots properly.
When I config for 4Gig however, the system fails to boot, giving a bunch of 
errors like the following:

/lib/ext3.0: unresolved symbol highmem_start_page
/lib/ext3.0: unresolved symbol journal_blocks_per_page_Rsmp_6082191c
/lib/ext3.0: unresolved symbol kmap_high
/lib/ext3.0: unresolved symbol journal_forget_Rsmp_678417a8
...
ERROR: /bin/insmod exited abnormally

I have compiled from scratch multiple times using make menuconfig, from 
freshly untarred sources just downloaded from kernel.org .
All of the system.map and initrd type stuff is setup properly in the boot 
dir by the 2.4.19 make files.

To restate the situation... if I boot from floppy and build the kernel with 
4G support it does not work, then if I reboot from floppy and flip 4G 
support off and rebuild, everything works fine except only 900Megs seen.

I am configuring to boot from onboard scsi (module sym53c8xx) , so maybe it 
is related to that and/or smp support?

Any idea what this means and how I can go about getting this fixed?

Thanks
Ethan


                 reply	other threads:[~2002-10-23  2:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5.1.0.14.0.20021022190139.0375b698@mail.toolfoundry.com \
    --to=ethan@toolfoundry.com \
    --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
all inboxes | Powered by JetHome®