Error on booting

Error on booting

Post by John J. Budd II » Sat, 17 Oct 1998 04:00:00

For reasons that are unclear to me I have been having difficulty
gettting past this error on booting and wondered if perhaps someone
might be able to shed a bit of light on the matter.  First of all it
will occur whether I try to boot off a floppy with zlilo, a kernel image
of any type, or from loadlin.  Occasionally the machine will get past
the boot and continue seemingly without difficulty unless I shut it down
for any reason.  I am using Slackware 2.0.34 but  I noted it to occur
with 2.0.35 as well on a brand new system install.  Any ideas?  Here is
the message:

Unable to handle kernel paging request at virtual address c3c2c2c0
current->tss.cr3 = 00101000, %cr3 = 00101000
*pde = 00000000
Oops: 0002
CPU:    0
EIP:    0010:[<01e1601f>]
EFLAGS: 00010203
eax: 01e16160   ebx: 0039d954   ecx: 00000000   edx: 00000000
esi: 01e16018   edi: 00000050   ebp: 001e9c30   esp: 001e9c14
ds: 0018   es: 0018   fs: 002b   gs: 0010   ss: 0018
Process swapper (pid: 0, process nr: 0, stackpage=001e7cf8)
Stack: 00112875 0039d954 00000001 ffffffff 00000001 00000001 001e9c4c
       00118137 001e9c4c 001e9cd4 00000000 00009000 0010a85b 0039d94a
       001ea4ac 001e9cd4 00000000 00009000 00000005 00000018 00000018
Call Trace: [<00112875>] [<00118137>] [<0010a85b>] [<00109904>]
[<0010a8d5>] [<001094fc>] [<001092b9>]
Code: 00 14 00 00 00 00 20 00 00 00 20 00 00 00 00 00 00 00 00 00
Aiee, killing interrupt handler
kfree of non-kmalloced memory: 001e9d40, next= 00000000, order=0
kfree of non-kmalloced memory: 001e9d30, next= 00000000, order=0
kfree of non-kmalloced memory: 001ea244, next= 00000000, order=0
idle task may not sleep
idle task may not sleep
idle task may not sleep
idle task may not sleep
idle task may not sleep

I might add that the error will more frequently occur after tesing the
hlt command.


1. diskless boot hit error while booting kernel, cannot find boot device, dhcp problem?

Hi people, wonder if you could help me on this:

i have two redhat 7.1 machine, one trying to boot off the other
through etherboot. Everythign goes fine, the client boots, retreat the
kernel off the server through tftp, and starting the kernel. Then it
stopped with error messages:
VFS: Cannot open root device "nfs" or 00:ff
please append a correct "root=" boot option
Kernel panic:VFS: Unable to mount root fs on 00:ff

kdb >
Where do I append a "root=" option? is it a dhcp problem? in
/etc/dhcpd.conf, i did put in

 option root-path "/boothome";

along with the other options. also, when tagging the kernel image, i
also have rootdir option:
mknbi-linux zImage --output=kernel --rootdir=/boothome

nfs export is correct, i have no idea where i did wrong.

any clue?

thanks in advance.
Paul G

2. Looking for X11R5 for Linux

3. 1.2.8: boot error: hda: DRDY error: status=0x01 { Error }

4. problem: e4500, controllers, disk arrays (5200) and Volume Manager

5. Boot issues (will Windows 95 boot from the 2nd drive withBootEasy???; strange error message with wd0)

6. Boot disk to resolve raid problem ?

7. FreeBSD 4.2 won't boot - 'read error' on boot after install

8. My ping won't pong (hardware config probably)

9. Won't boot from boot disk - "crc error"

10. /etc/boot.conf error on boot (i386) 3.1

11. Intel Boot Disc error - Boot failure

12. Booting from SLS1.03 -> crc error, from HLU boot/root is ok?

13. mount errors when booting from HD, ok booting from diskette