Hi!
    I have installed 2.4.16 kernel. And now I see that possibly my problem
dealed with loop device work when HIGHMEM enabled.
    I have tested 2 configuration:
       1. HIGHMEM - disable
          loop device compiled in kernel
       2. HIGHMEM - enable
          loop device compiled in kernel

I am using filesystem from a file mounted to /var/log directory during
the boot.File is formated by ext2 filesystem.

like this:  mount /tmp/tmpfs /var/log -o loop

For 1 all is working fine.Loop devices is working and no any unresolved
symbols.

For 2 I loop devices is not used because module ext2 have unresolved
symbols:


/lib/modules/2.4.16-hm/kernel/fs/ext2/ext2.o: unresolved symbol kunmap_high
/lib/modules/2.4.16-hm/kernel/fs/ext2/ext2.o: unresolved symbol
highmem_start_page
/lib/modules/2.4.16-hm/kernel/fs/ext2/ext2.o: unresolved symbol kmap_high
/lib/modules/2.4.16-hm/kernel/fs/ext2/ext2.o: insmod
/lib/modules/2.4.16-hm/kernel/fs/ext2/ext2.o failed
/lib/modules/2.4.16-hm/kernel/fs/ext2/ext2.o: insmod ext2 failed
bash-2.05# modprobe rd
/lib/modules/2.4.16-hm/kernel/drivers/block/rd.o: unresolved symbol
kunmap_high
/lib/modules/2.4.16-hm/kernel/drivers/block/rd.o: unresolved symbol
highmem_start_page
/lib/modules/2.4.16-hm/kernel/drivers/block/rd.o: unresolved symbol
kmap_high
/lib/modules/2.4.16-hm/kernel/drivers/block/rd.o: insmod
/lib/modules/2.4.16-hm/kernel/drivers/block/rd.o
failed/lib/modules/2.4.16-hm/kernel/drivers/block/rd.o: insmod rd failed
bash-2.05# modprobe isofs
/lib/modules/2.4.16-hm/kernel/fs/isofs/isofs.o: unresolved symbol
kunmap_high
/lib/modules/2.4.16-hm/kernel/fs/isofs/isofs.o: unresolved symbol
highmem_start_page
/lib/modules/2.4.16-hm/kernel/fs/isofs/isofs.o: unresolved symbol kmap_high
/lib/modules/2.4.16-hm/kernel/fs/isofs/isofs.o: insmod
/lib/modules/2.4.16-hm/kernel/fs/isofs/isofs.o failed
/lib/modules/2.4.16-hm/kernel/fs/isofs/isofs.o: insmod isofs failed
bash-2.05# modprobe minix
/lib/modules/2.4.16-hm/kernel/fs/minix/minix.o: unresolved symbol
kunmap_high
/lib/modules/2.4.16-hm/kernel/fs/minix/minix.o: unresolved symbol
highmem_start_page
/lib/modules/2.4.16-hm/kernel/fs/minix/minix.o: unresolved symbol kmap_high
/lib/modules/2.4.16-hm/kernel/fs/minix/minix.o: insmod
/lib/modules/2.4.16-hm/kernel/fs/minix/minix.o failed
/lib/modules/2.4.16-hm/kernel/fs/minix/minix.o: insmod minix failed

So without loop devices all is working in HIGHMEM configuration.

Sorry for a little flood.														
						Best regards, pasha.

Previous message content:

     The problem is in kernel freezing after some time after booting if I
am turning on HIGHMEM in kernel configuration.This is behaviour when I
dont run syslog and klog deamons during the booting. Otherwise kernel
freezes right after start syslog daemon and gives oops.Without turned on
HIGHMEM system is working normally.
     My PC configuration:
        HP X4000
        Dual P4 Xeon 1.7GHz
        MB chipset i860
        2G RAM

     I have tested 2.4.14 , 2.4.15 , 2.4.10 , 2.4.9 kernels with the same
configuration. And only 2.4.9 kernel is working normally. As I remeber
in 2.4.10 was included new VM system. May be problem is dealed with it?

In attachment dmesg log with oops, decoded oops and kernel
configuration. All is from 2.4.15 kernel test.
										I can test patches if it will be necessary.					                                                		pasha.

Marcelo Tosatti wrote:

  > Could you please describe whats your problem with HIGHMEM again?
  >
  > I did not read your first report.
  >
  > On Sat, 24 Nov 2001, Pavel Frolov wrote:
  >
  >
  >>Hi, ppl!
  >>   I have tried to use HIGHMEM on 2.4.15 and 2.4.14 as had written
  >>before without success.
  >>   On 2.4.9 kernel HIGHMEM is working.
  >>
  >>    Please check new VM stuff.
  >>
  >>                                                          pasha.
  >>
  >>-
  >>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/
  >>
  >>
  >
  >