[TheSaint]

Just a big problem:

If i want run halt, reboot or init x comes "****: couldnt find kmalloc()"

and if i run "ps x" to view the running PIDs --> nothing to see!

OS: SuSE Linux 8.1 i386 Prof

HELP PLEASE, is a good install, dont want new one!!!


THX

[lynch]

What ,if anything,has changed on this system before the problems started?
kmalloc is for memory allocation;have you increased the amount of ram you have recently?Did this just start happening all of a sudden or has it been intermittent?
I run SuSE 8.1 but have never experienced this problem before.
lynch

[TheSaint]

after a system failure, i think. nothing gone go, and i must reboot. After that i had this problem.

My file systems are
raiserfs (ext3) "/home"
ext2 "/"

how can i manuel make a filecheck on this file systems??? maybe its a file problem, or can i reinstall kmalloc (ii it a kernel source?)

its my router for home lan:
http://icebox.kicks-***.net/Sysinfo/ *** -> a s s

[TheSaint]

Thats the message from console if i want reboot:


The system is going down for reboot NOW!
/dev/null
RK_Init: idt=0xc035f000, sct[]=0xc02faa34, ****: Can't find kmalloc()!


i hope it can help you

[codejockey]

kmalloc is an internal kernel memory allocation function and should always be available. I'd definitely check the filesystems (/ is most likely). Since your root filesystem is ext2, you can check it easily with fsck.

Boot from a floppy (or the installation CD) and login as root. Use the mount command to verify that your root filesystem on the hard drive is not mounted. Run fsck on your hard drive's / filesystem using a command such as: fsck /dev/hda1 and review the results. Note that you will need to know the partition for your root filesystem. I recommend answering 'n' (no) to any request fsck makes to correct a problem it has found. By answering 'n', you will be able to get a feel for the extent of any problems. After fsck finishes, you can re-run it and have it fix problems.

Hope this helps.