On 08 Sep 2000 01:40:55 +0200,
"Juan J. Quintela" <firstname.lastname@example.org> wrote:
>>>>>> "kenneth" == Kenneth Johansson <email@example.com> writes:
> I only can guess that you are using a wrong System.map for
> doing the ksymoops. __mon_yday is an array, not a function,
> the backtrace don't make sense.
>Later, Juan "waiting for a nice backtrace" :)))
>kenneth> Sep 7 17:39:50 ken1 kernel: Call Trace: [__mon_yday+6234/22368] [__mon_yday+6978/22368] [blk_get_queue+50/64] [generic_make_request+257/272] [ll_rw_block+337/448] [flush_dirty_buffers+130/180] [tvecs+15418/54628]
That is caused by klogd assuming it knows where the System.map is and
blindly using the wrong one. Sorry folks but klogd as distributed is
broken. Either start klogd with "-x" or apply
and use ksymoops to get a real back trace.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Sep 07 2000 - 21:00:32 EST