From: Udo van den Heuvel <udovdh@xs4all.nl>
To: linux-kernel@vger.kernel.org
Cc: Arjan van de Ven <arjan@infradead.org>
Subject: Re: Oops / BUG? (2.6.17.2 on VIA Epia CL6000)
Date: Sun, 02 Jul 2006 13:24:34 +0200 [thread overview]
Message-ID: <44A7ACF2.4070304@xs4all.nl> (raw)
In-Reply-To: <1151839268.3111.10.camel@laptopd505.fenrus.org>
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
# CONFIG_KALLSYMS_ALL is not set
# CONFIG_KALLSYMS_EXTRA_PASS is not set
Kind regards,
Udo
next prev parent reply other threads:[~2006-07-02 11:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-02 11:15 Oops / BUG? (2.6.17.2 on VIA Epia CL6000) Udo van den Heuvel
2006-07-02 11:21 ` Arjan van de Ven
2006-07-02 11:24 ` Udo van den Heuvel [this message]
2006-07-02 11:38 ` Arjan van de Ven
2006-07-02 11:46 ` Udo van den Heuvel
2006-07-02 21:15 ` Jan Engelhardt
-- strict thread matches above, loose matches on Subject: below --
2006-07-02 19:51 Chuck Ebbert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44A7ACF2.4070304@xs4all.nl \
--to=udovdh@xs4all.nl \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.