Problem with Kernel

Problem with Kernel

[Timothy M. Totten]

Hello,

	I am currently running Kernel 2.4.5 on my machine, and I
tried to install 2.4.18 and got a kernel panic. So I thought
I'de just make a new compile of 2.4.5 with only one change,
I set the High Memory support to 4GB instead of None.

	Right when the kernel should have been setting up the swap
space, instead it gave me the following message:

BUG IN DYNAMIC LINKER ld.so: rtld.c: 621: dl_main: Assertion `_dl_rtld_map.l_libname` failed!
Kernel panic: Attempted to kill init!

This is a different message than I was getting in 2.4.18
but happens at the same time in bootup.

The thing is, when I boot the original 2.4.5 it works fine.

They are both the same version from the same directory, and
only the High Memory support option has changed.

I'de like to get it working as having only 890 megs out of
1.75GB of RAM is kinda sucky since I just bought the RAM.

The machine is a Compaq Proliant 6000 "Quad Pentium Pro 200".

Thanks!

Timothy M. Totten

Re: Problem with Kernel

[Robert Claeson]

Timothy M. Totten wrote:

 >    I am currently running Kernel 2.4.5 on my machine, and I
 >tried to install 2.4.18 and got a kernel panic. So I thought
 >I'de just make a new compile of 2.4.5 with only one change,
 >I set the High Memory support to 4GB instead of None.
 >
 >    Right when the kernel should have been setting up the swap
 >space, instead it gave me the following message:
 >
 >BUG IN DYNAMIC LINKER ld.so: rtld.c: 621: dl_main: Assertion 
 >`_dl_rtld_map.l_libname` failed!
 >Kernel panic: Attempted to kill init!
 >
 >This is a different message than I was getting in 2.4.18
 >but happens at the same time in bootup.
 >
 >The thing is, when I boot the original 2.4.5 it works fine.

Are you sure you did get exactly the same drivers and file system 
modules included as with your original 2.4.5 kernel? The reason I ask is 
that I've just spent two entire days trying (and finally suceeding) to 
get 2.4.18 working on a Compaq DL380 server (and no, not evern Red Hat's 
"original" kernels worked with these systems starting with 2.4.9-21).

I didn't get the same results as you did, but various other kinds of 
kernel panics either when it tried to mount the root file system or 
setting up swap. I'm not sure exactly how I did manage to get it to 
work, but I believe I finally figured that I needed to compile the 
cpqarray driver as a module and not as a static driver, and various 
other drivers static, especially those pertaining to file systems and 
such. Mkinitrd didn't pick them up correctly, and using --preload or 
--with to mkinitrd didn't help either. IOW, I fixed the problem with my 
systems by T&E. I know too little about your system to tell whether the 
problem is the same, or even similar.

/Robert

PROBLEM with kernel

[Andrej Hocevar]

I got this right after resuming from hibernation. Unfortunatelly, I
don't have the kernel-sources anymore as I've actually upgraded to
2.6.25.4. 



Buffer I/O error on device sda1, logical block 0
lost page write due to I/O error on sda1
scsi 1:0:0:0: Direct-Access     WD       5000AAKS Externa 106a PQ: 0
ANSI: 4
sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 11 00 00 00
sd 1:0:0:0: [sdb] Assuming drive cache: write through
sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 11 00 00 00
sd 1:0:0:0: [sdb] Assuming drive cache: write through
 sdb: sdb1 sdb2 sdb3
 sd 1:0:0:0: [sdb] Attached SCSI disk
usb-storage: device scan complete
------------[ cut here ]------------
WARNING: at fs/buffer.c:1183 mark_buffer_dirty+0x20/0x6a()
Modules linked in: xt_state xt_tcpudp iptable_filter ip_tables x_tables
nf_nat_ftp nf_nat nf_conntrack_ipv4 nf_conntrack_ftp nf_conntrack ppdev
lp cpufreq_stats fuse sr_mod sbp2 sd_mod parport_pc parport
snd_intel8x0 snd_ac97_codec rtc ac97_bus snd_pcm_oss snd_mixer_oss
snd_pcm 8250_pci snd_timer 8250 serial_core snd_page_alloc rng_core
video output evdev ide_cd_mod cdrom ide_disk usb_storage usbhid
scsi_mod ohci1394 piix ieee1394 ide_core ehci_hcd uhci_hcd usbcore unix
[last unloaded: firmware_class]
Pid: 7364, comm: umount Not tainted 2.6.25.3summer #1
[<c011767f>] warn_on_slowpath+0x40/0x4f
[<c013c6d5>] generic_writepages+0x1a/0x21
[<c014dd56>] check_bytes_and_report+0x25/0x98
[<c014dd56>] check_bytes_and_report+0x25/0x98
[<c014e046>] check_object+0x114/0x19f
[<c0192fdf>] journal_destroy+0x11e/0x125
[<c014e561>] __slab_free+0x1be/0x1ed
[<c0192fdf>] journal_destroy+0x11e/0x125
[<c014eb91>] kfree+0x79/0x81
[<c0192fdf>] journal_destroy+0x11e/0x125
[<c0192fdf>] journal_destroy+0x11e/0x125
[<c0124ac8>] autoremove_wake_function+0x0/0x2d
[<c016a436>] mark_buffer_dirty+0x20/0x6a
[<c018a729>] ext3_put_super+0x41/0x137
[<c0153257>] generic_shutdown_super+0x4a/0xad
[<c01532c6>] kill_block_super+0xc/0x1b
[<c0153334>] deactivate_super+0x2c/0x3f
[<c01620bf>] sys_umount+0x231/0x269
[<c014e561>] __slab_free+0x1be/0x1ed
[<c01543ef>] sys_stat64+0xf/0x23
[<c01440c0>] remove_vma+0x36/0x3b
[<c0144938>] do_munmap+0x181/0x19b
[<c0162102>] sys_oldumount+0xb/0xe
[<c010393e>] syscall_call+0x7/0xb
=======================
---[ end trace 02c95bee20be13a0 ]---


	Andrej

--
www.ljudmila.org/ludliteratura