From: Andrew Morton <akpm@digeo.com>
To: Andi Kleen <ak@muc.de>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix kallsyms crashes in 2.5.54
Date: Thu, 02 Jan 2003 03:52:29 -0800 [thread overview]
Message-ID: <3E1427FD.16A7B021@digeo.com> (raw)
In-Reply-To: 20030102091325.GA24352@averell
Andi Kleen wrote:
>
> The kernel symbol stem compression patch included in 2.5.54 unfortunately
> had a few problems, triggered by various circumstances.
>
With your patch I am still seeing an instant oops when running top(1):
connect(6, {sin_family=AF_UNIX, path="/var/run/.nscd_socket"}, 110) = -1 ENOENT (No such file or directory)
close(6) = 0
open("/etc/group", O_RDONLY) = 6
fcntl64(0x6, 0x1, 0, 0x1) = 0
fcntl64(0x6, 0x2, 0x1, 0x1) = 0
fstat64(6, {st_mode=S_IFREG|0644, st_size=720, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40023000
read(6, "root:x:0:root\nbin:x:1:root,bin,d"..., 4096) = 720
close(6) = 0
munmap(0x40023000, 4096) = 0
open("/proc/1/cmdline", O_RDONLY) = 6
read(6, "init [3]\0\0\0\0\0\0\0\0\0\0\0", 2047) = 19
close(6) = 0
open("/proc/1/wchan", O_RDONLY) = 6
read(6,
The oops isn't very informative. EIP is 0x00000000, call trace
is just "scheduling_functions_start_here+0x3dd/0x4a8"
Using procps from http://surriel.com/procps/
next prev parent reply other threads:[~2003-01-02 11:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-02 9:13 [PATCH] Fix kallsyms crashes in 2.5.54 Andi Kleen
2003-01-02 11:52 ` Andrew Morton [this message]
2003-01-02 12:00 ` Andi Kleen
2003-01-02 12:16 ` Andrew Morton
2003-01-02 13:06 ` One-way Gigabit Ethernet TCP performance with Jumbo frames Steffen Persvold
2003-01-03 13:25 ` Robert Olsson
2003-01-02 18:02 ` [PATCH] Fix kallsyms crashes in 2.5.54 Rudmer van Dijk
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=3E1427FD.16A7B021@digeo.com \
--to=akpm@digeo.com \
--cc=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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