[2.1.16] Strange crash...
Chris Austin (myrdraal@alpha.pulsar.net)
Sun, 22 Dec 1996 06:44:29 -0500 (EST)
Hi...
Little background information:
I'm running 2.1.16 (no patches to it) on a 486dx2/66 with 12MB of memory,
no SCSI or anything like that...
Anyhow, the system had been running for 18 or so hours and I was playing
with X-DOSEMU. I was in a textmode VC running IRC and I got these messages
on my log:
-----
Dec 22 06:15:01 Jackal kernel: Bad pmd in pte_alloc: 04406700
Dec 22 06:15:01 Jackal kernel:
Dec 22 06:15:01 Jackal kernel: Out of memory for sh.
Dec 22 06:15:01 Jackal kernel: zap_pte_range: bad pmd (25a06700)
Dec 22 06:15:01 Jackal kernel: zap_pte_range: bad pmd (9da06700)
Dec 22 06:16:18 Jackal kernel: change_pte_range: bad pmd (3ba06700)
Dec 22 06:16:19 Jackal kernel: Bad pmd in pte_alloc: 3ad06700
Dec 22 06:16:19 Jackal kernel:
Dec 22 06:16:19 Jackal kernel: Out of memory for top.
Dec 22 06:16:19 Jackal kernel: zap_pte_range: bad pmd (50670000)
Dec 22 06:16:19 Jackal kernel: zap_pte_range: bad pmd (40670000)
Dec 22 06:16:19 Jackal kernel: free_one_pmd: bad directory entry 0000eceb
Dec 22 06:16:19 Jackal kernel: free_one_pmd: bad directory entry 0000003b
Dec 22 06:16:28 Jackal kernel: zap_pte_range: bad pmd (b0670000)
Dec 22 06:16:28 Jackal kernel: zap_pte_range: bad pmd (c0670000)
Dec 22 06:16:28 Jackal kernel: zap_pte_range: bad pmd (30670000)
Dec 22 06:16:28 Jackal kernel: free_one_pmd: bad directory entry 00000070
Dec 22 06:16:28 Jackal kernel: free_one_pmd: bad directory entry 00000076
----
Shortly after that, everything stopped COMPLETELY. The only thing I was
able to do was switch VCs... Just wondering what the signif. of that was?
(BTW I wasn't able to reboot either - Had to reset the machine.)
Bye...