On Sun, 2006-07-02 at 13:24 +0200, Udo van den Heuvel wrote:
> Arjan van de Ven wrote:
> > On Sun, 2006-07-02 at 13:15 +0200, Udo van den Heuvel wrote:
> >> Hello,
> >>
> >> On my otherwise stable Via EPIA CL6000 I experienced an OOPS.
> >> Hardware should be OK. I was unable to reproduce the event, so far.
> >> In what part of the kernel did things go wrong?
> >> What can I do to help fix the bug? (if it is indeed a bug)
> >
> > Hi,
> >
> > something really bad happened (the processor jumped into hyperspace);
> > however it looks like automatic symbol resolving isn't working;
> > could you check if CONFIG_KALLSYMS is enabled in your kernel config?
> > With that enabled, debugability tends to go up bigtime since at least
> > the backtrace becomes human readable...
>
> I have:
>
> CONFIG_KALLSYMS=y
Hoi,
hmmmmm then something really bad happened, so bad that even the
backtrace is corrupted ;(
I'm sorry to say but unless you already have a suspect, those are really
really hard to diagnose or fix. One thing you can do is remove all
modules you don't actually use (just from a statistical pov that reduces
the risk of it repeating)... and hope maybe a next backtrace does
provide more information.
Greetings,
Arjan van de Ven
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
