Hi,
This is whats called a kernel oops message.
When something bad happens with a program (or indeed the kernel, you will get
this message).
There is a document on oops tracing in /usr/src/linux/Documentation/oops.txt
which will show you how to find out what caused this (normally a dodgy app, or
a development kernel).
When the machine locks up, the only way (except for a serail console or
something) is to write down all the info on the screen, and reboot, typing it
into a file.
Feed this to a program call ksymoops which will tell you roughly what went
wrong.
You could try upgrading your kernel to 2.2.16, which I find pretty stable, but
be sure this is to blame first.
Hope this helps,
(and as for the silly arguments regarding off-topic posts, if the guy is a ham
(or even x25 cber, I'll do my best to answer and help, stuff all the arogant
assholes on this list with the post elsewhere questions. Hams used to help each
other, no matter if the problem is Ham related or not)
Alanp
On Sat, 29 Jul 2000, Stephan Loges wrote:
> Hi there,
> since i run a gateway for 1 1/2 year now, i have a major
> problem with my machine. From time to time, usually every 5-10
> days the machine stops working with following message seen at
> the screen:
> Oops: 0000
> CPU: 0
> EIP: 0010:[<0015b132>]
> EFLAGAS: 00010006
> eax: 398180ec ebx: 0361c30c ecx: 00000246 edx: 398180ec
> esi: 0361c374 edi: 00000001 ebp: 001c1ab4 esp: 001c1a84
> ds: 0018 es: 0018 fs: 002b gs: 0018 ss: 0018
> Process swapper (pid: 0, process nr: 0, stackpage=001bfb7c)
> Stack: 0361c30c 0015bc00 0015bd68 0361c30c 0361c30c 00112f3d 0361c30c
> 00000001
> ffffffff 00000001 00000001 001c1ad0 001e8ad0 001188a7 001c1ad0
> 001c1b58
> 00000000 00009000 0010a8db 028733e8 fffffc18 001c2330 001c1b58
> 00000000
> Call Trace: [<0015bc00>] [<0015bd68>] [<00112f2d>] [<001188a7>]
> [<0010a8db>] [<00109994>] [<0010a955>]
> [0010968c>] [<00109519>]
> Code: 8b 02 ff 4b 70 89 70 04 89 43 68 c7 02 00 00 00 00 c7 42 04
> Aiee, killing interrupt handler
>
> The message is produced from the kernel exit code, but as i am
> not a programmer, you can imagine how magic these lines are
> looking to me :)
>
> That's it, and there is no way to get the machine up remotely. Only
> a power off/on helps and of course, no syslog entries...
> Formerly the pc was a old Pentium 75 with 24 megs of RAM, i thought
> that a hardware upgrade help, but it doesn't. Now the pc is a
> Pentium 200 with 64 megs, a new harddisk etc. etc.
> The ethernet card is a AT-1700 fibre optic.
> System is SuSE 5.1, with kernel patched to 2.0.38
> AX.25 stuff works fine, installed and working services are
> linuxnode 0.25, netrom, htpp 1.20, ipip tunneling. IP services
> are ftp, telnet, http, smtp.
> Maybe there is someone out here who can give me a little advice
> where to search for the problem.
> I am really lost with it. If you need further info, please give me
> a note.
>
> 73 Stephan, DK8LV
>
> p.s. Gateway is db0fhf.ampr.org [44.130.127.111/193.175.189.174]
> >From today on the machine reboots every night at 2355UTC to
> prevent a possible system exit.
> --
> Join http://www.dk0wcy.de/magneto/magnet.htm or
> http://db0fhf.ampr.org (44.130.127.111) for realtime Magnetometer,
> our Aurora Warning Beacon Project !
>
> [] dk8lv@db0hes.#slh.deu.eu
> [] [EMAIL PROTECTED]
> [] [EMAIL PROTECTED]
> [] [EMAIL PROTECTED]
--
Alanp
