kernel panic loop 1
coll...@surfeu.de
I've developed a program for Caldera Linux Openserver 3.11
This is somehow causing a total crash of the machine and when the machine
reboots I see:
"Kernel
panic: loop 1".
"Unable to handle kernel NULL pointer dereference at virtual address
00000010
*pde=06c86001
*pte=00000000
Oops: 0000
CPU: 0
EIP: 0010: [<c0149604>] Not tainted
EFLAGS: 00010283
eax: 00000000 ebx: cabcf640 ecx: 00000001 edx: c5ca6000
esi: cfbfe5c0 edi: c5ca6fff ebp: c5ca6ffe esp: c6ad1f14
ds: 0018 es: 0018 ss: 0018
Process hotdird (pid: 2089, stackpage=c6ad1000)
Stack: ...
Call Trace: ...
Code: ...
Can anybody give me a hint as to what might be causing this?
It's difficult to get to the bottom of this because of the fact that the
machine goes completely dead - no access via the keyboard or via the
network (telnet etc.)
Thanks for any tips,
Martin.
Craig
> I've developed a program for Caldera Linux Openserver 3.11
> This is somehow causing a total crash of the machine and when the machine
> reboots I see:
Caldera is still around? Haven't heard anyone here uses Caldera!
--
Craig
Matt Schalit
>coll...@surfeu.de wrote:
>
>> I've developed a program for Caldera Linux Openserver 3.11
>> This is somehow causing a total crash of the machine and when the machine
>> reboots I see:
>
>Caldera is still around? Haven't heard anyone here uses Caldera!
What the hell are you trying to say? This person posted
a perfectly legitimate question about a difficult problem,
and you follow up with poor grammer and unintelligible
fragments. You have some nerve. What you sow, so shall
you reap.
Regards,
Matthew
Matt Schalit
Martin, I saw you post in the other ng also, and I was hoping someone
with a lot of Linux experience would help you out by now.
Do you have any idea what "Process hotdird (pid: 2089" refers to?
Is there any way for you to boot into single user mode?
Do you have emergency boot disks? Can you boot of them and fix it?
Can you put your hard drive into another linux box, mount the drive,
and remove the crap out of rc2.d or wherever it is?
Good Luck,
Matthew
Roger Leigh
Try running the panic output through ksymoops. I'm not sure if it's
possible, since it's meant for oopses instead of a panic, but worth a
try, since it'll tell you what went wrong.
Check what options you compile into your kernel, and what modules are
being used--are you using any experimental stuff?
I have never seen a panic in five years of running Linux (except from
failure to mount the root partition--a setup issue). It's possibly a
hardware problem, but probably worth trying the latest kernel to see
if it's a bug that's been fixed.
--
Roger Leigh
** Registration Number: 151826, http://counter.li.org **
Need Epson Stylus Utilities? http://gimp-print.sourceforge.net/
GPG Public Key: 0x25BFB848 available on public keyservers
Bill Hay
>Hi,
>
>I've developed a program for Caldera Linux Openserver 3.11
>This is somehow causing a total crash of the machine and when the machine
>reboots I see:
>
>"Kernel
>panic: loop 1".
like you are saying after but the oops reports a process called hotdird
with a pid of 2089 which is unlikely in a machine that is just starting up.
The first step is to find out what the kernel is doing at the time. Have a look
at the relevant System.map file to find out what c0149604 is. Do the
same for the various entries in the call trace.
Is this program running as root? Regular user programs shouldn't be able
to crash the system. If the program runs as a regular user then this
indicates a kernel bug and should probably be reported to the linux kernel
mailing list. If the process is running as root then you should check your
program out first to see what it is doing to cause the problem. If the stack
trace doesn't give you enough info to figure out what is going on you might
want to try running it under user-mode linux.
>
>"Unable to handle kernel NULL pointer dereference at virtual address
>00000010
>*pde=06c86001
>*pte=00000000
>Oops: 0000
>CPU: 0
>EIP: 0010: [<c0149604>] Not tainted
>EFLAGS: 00010283
>eax: 00000000 ebx: cabcf640 ecx: 00000001 edx: c5ca6000
>esi: cfbfe5c0 edi: c5ca6fff ebp: c5ca6ffe esp: c6ad1f14
>ds: 0018 es: 0018 ss: 0018
>Process hotdird (pid: 2089, stackpage=c6ad1000)
>Stack: ...
>Call Trace: ...
>Code: ...
>
>
>
>Can anybody give me a hint as to what might be causing this?
>It's difficult to get to the bottom of this because of the fact that the
>machine goes completely dead - no access via the keyboard or via the
>network (telnet etc.)
>
>Thanks for any tips,
>
>Martin.
>
>
>
--
TANSTAAFM
coll...@surfeu.de
to provide more information:
the process hotdird is my program. It's a daemon which is started as one of
the very last in the boot process. It reads through the /proc directory
tree to get information about particular open user files. As far as I can
ascertain the system crashes during this phase. I would put it down to a
hardware problem if it weren't for the fact that the machine only crashes
when my program is running. The strange thins is, this problem only occurrs
on one machine and so far on no other machine.
This machine belongs to the test department which is why I have a serious
problem and have to find the solution.
One hint is perhaps that the machine which crashes is the only one with a
dual processor motherboard, but with only one processor.
Thanks for all suggestions,
Martin.