On Sat, 29 Jul 2000, Alan Pearson wrote:
> 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).
Yep, thanks Richard and you for information, now im a little piece
further and traced the following with ksymoops:
Using `/System.map' to map addresses to symbols.
Trace: 15bc00 <ax25_timer>
Trace: 15bd68 <ax25_timer+168/264>
Trace: 112f2d <timer_bh+2ed/334>
Trace: 1188a7 <do_bottom_half+3b/60>
Trace: 10a8db <handle_bottom_half+b/20>
Trace: 109994 <sys_idle+5c/70>
Trace: 10a955 <system_call+55/80>
Code:
Guess now it is not any longer off topic?
Using ax25-utils-2.1.42a
Maybe one of the ax25 authors can pick up this and start
to investigate for the problem? Any help would be very
appreciated.
73 Stephan, DK8LV
--
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]
