> Thanks for reply.
>
> I am sorry to say that it still resulted in a panic.
No. It resulted in oops.
> I compiled the program as
>
> gcc -Wall -DMODULE -D__KERNEL__ -DLINUX -O2 -c force_oops.c
> insmod force_oops.o
>
> This created an entry /proc/force_oops.
>
> cat > /proc/force_oops
> resulted in panic.
>
> Unable to handle kernel NULL pointer dereferance at virtual address 00000000
> current->tss.cr3=005ed000, %cr3=005ed000
> *pde=00000000
> Entering kdb due to panic @ 0xc2810059
Kdb called it panic. That's kdb's fault. It is oops, really. Try go.
> .
> kdb> bt
> cannot determine function for eip=0xc2810059
>
> Looks like there is something seriously wrong with my system. Any idea
> what it might be?
I'd tell you but you would not like that answer :-)))).
Pavel
-- I'm really pavel@ucw.cz. Look at http://195.113.31.123/~pavel. Pavel Hi! I'm a .signature virus! Copy me into your ~/.signature, please!- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/