From: Russell King <rmk@arm.linux.org.uk>
To: Alex Romosan <romosan@sycorax.lbl.gov>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at drivers/serial/core.c:1067 with 2.5.44
Date: Sun, 27 Oct 2002 17:12:53 +0000 [thread overview]
Message-ID: <20021027171253.B9553@flint.arm.linux.org.uk> (raw)
In-Reply-To: <87adkzde90.fsf@sycorax.lbl.gov>; from romosan@sycorax.lbl.gov on Sun, Oct 27, 2002 at 08:43:07AM -0800
On Sun, Oct 27, 2002 at 08:43:07AM -0800, Alex Romosan wrote:
> i am not sure what this means. i am running debian unstable. i just
> realized i ran ksymoops with the -x option (if it makes any difference
> i can resend the oops without -x).
Firstly, you need klogd running with -x so the numbers within [< and >]
are preserved. It is a shame that these distributions still run klogd
without -x.
> > 2. your ksymoops doesn't seem to know what modules are loaded.
>
> isn't this the list of modules loaded at the time?
>
> Oct 27 07:39:54 trinculo kernel: 3c574_cs irtty irda autofs4 microcode
> ppp_async uhci-hcd ohci-hcd usbcore nls_cp437 vfat snd-pcm-oss
> snd-mixer-oss snd-ymfpci snd-pcm snd-mpu401-uart snd-rawmidi
> snd-ac97-codec snd-opl3-lib snd-timer snd-hwdep snd-seq-device
> snd soundcore
This is a line from the kernel which ksymoops can't interpret.
ksymoops needs to know which modules are loaded, and where they
are loaded so it can give accurate call trace information.
BTW, an even better option would be to enable CONFIG_KALLSYMS.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-10-27 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-27 16:25 kernel BUG at drivers/serial/core.c:1067 with 2.5.44 Alex Romosan
2002-10-27 16:33 ` Russell King
2002-10-27 16:43 ` Alex Romosan
2002-10-27 17:12 ` Russell King [this message]
2002-10-27 19:12 ` Alex Romosan
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=20021027171253.B9553@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=romosan@sycorax.lbl.gov \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox