From: Keith Owens <kaos@ocs.com.au>
To: David Won <phlegm@home.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel newby help.... What's causing my Oops
Date: Sat, 28 Oct 2000 15:47:36 +1100 [thread overview]
Message-ID: <6010.972708456@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Fri, 27 Oct 2000 02:26:10 EDT." <00102702261003.01068@phlegmish.com>
On Fri, 27 Oct 2000 02:26:10 -0400,
David Won <phlegm@home.com> wrote:
>Oct 22 22:37:20 phlegmish kernel: Unable to handle kernel paging request at
>virtual address 00018486
>Oct 22 22:37:20 phlegmish kernel: EIP:
>0010:[smbfs:__insmod_smbfs_O/lib/modules/2.4.0-test8/kernel/fs/smbfs/sm+-234781/96]
>Oct 22 22:37:20 phlegmish kernel: Call Trace:
>[smbfs:__insmod_smbfs_O/lib/modules/2.4.0-test8/kernel/fs/smbfs/sm+-220073/96]
>[smbfs:__insmod_smbfs_O/lib/modules/2.4.0-test8/kernel/fs/smbfs/sm+-237584/96]
>[smbfs:__insmod_smbfs_O/lib/modules/2.4.0-test8/kernel/fs/smbfs/sm+-245443/96]
>[__fput+35/144] [_fput+17/64] [fput+18/24] [filp_close+82/92]
>Oct 22 22:37:20 phlegmish kernel: Code: 0f b7 aa 84 40 00 00 89 ef 83 c7 04
>89 4c 24 1c 83 c6 04 8b
>Using defaults from ksymoops -t elf32-i386 -a i386
You did everything right, alas the data was corrupted in the log files
before you even saw it. klogd tries to converts oops itself and far to
often it gets it wrong, yielding gibberish. Edit /etc/rc.d/init.d/syslog
(assuming you use SysV init), change
daemon klogd
to
daemon klogd -x
then /etc/rc.d/init.d/syslog restart. Any new oops will be left alone
so you will have clean data to feed to ksymoops. When you get a clean
oops, feed it to ksymoops and mail the result to linux-kernel.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-10-28 4:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-27 6:26 kernel newby help.... What's causing my Oops David Won
2000-10-27 7:04 ` Urban Widmark
2000-10-28 4:47 ` Keith Owens [this message]
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=6010.972708456@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=phlegm@home.com \
/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