All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
* MPC8xx Interrupt vectors
@ 1999-06-21 14:02 kd
  0 siblings, 0 replies; only message in thread
From: kd @ 1999-06-21 14:02 UTC (permalink / raw
  To: linuxppc-dev


Hello,

Two problems:

1) When I make an application do a page_fault (segmentation fault) the
kernel crasses insted of just the application crassing.
Needless to say I do not have an secondary storage or an swap device, but I
am running rootfs from /dev/nfs. System has
only 4MB of ram.
2)When the system crasses it goes into the "Rebootting in 180 s" prompt,
but fails to reboot, i.e. it goes into endless loop, like:
Rebooting in 180 seconds..<0>Kernel panic: Kernel Mode Software FPU
Emulation
Rebooting in 180 seconds..<0>Kernel panic: Kernel Mode Software FPU
Emulation
Rebooting in 180 seconds..

In the reset vector there are probably some corrupted data that looks like
FPU instuction that triggers the FPU trap.

This makes me think that the Interrupt vectors are somehow screwed.

Do you guys recognise this behaviour?

System is embedded 2.2.5 with mpc 823 CPU  4MB of Ram.

Thanks,

K.D.



[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~1999-06-21 14:02 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
1999-06-21 14:02 MPC8xx Interrupt vectors kd

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.