From: Christian <evil@g-house.de>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.67 alpha compile failure (solved but nfsd Oopses now)
Date: Mon, 14 Apr 2003 00:50:13 +0200 [thread overview]
Message-ID: <3E99E9A5.7090302@g-house.de> (raw)
In-Reply-To: <yw1xllyfv6yf.fsf@zaphod.guide>
Måns Rullgård schrieb:
> See my message with subject "[PATCH] Fix cond_syscall macro on Alpha".
yes, indees. the patch applied (with an error when using patch
--verbose) and 2.5.67 compiled perfectly. i sa w the thread about this
thing on the redhat-AXP list, but i don't know anything about the deeper
interactions between kernel and glibc, sorry.
from a user's point of view i could say: "yes, let it go in 2.5.68" :-)
besides:
now i have a kernel oops when starting the kernel-nfs-server:
------------
lila:~# /etc/init.d/nfs-kernel-server start
Apr 14 00:31:08 lila kernel: Unable to handle kernel paging request at
virtual address 2834362d657a6973
Apr 14 00:31:08 lila kernel: rpc.nfsd(22279): Oops 0
Apr 14 00:31:08 lila kernel: pc = [<fffffc0000314748>] ra =
[<fffffc0000312ec0>] ps = 0007 Not tainted
Apr 14 00:31:08 lila kernel: v0 = 0000000000000000 t0 =
0000000000000000 t1 = fffffc0000314744
Apr 14 00:31:08 lila kernel: t2 = fffffc0000560848 t3 =
fffffc000055fba0 t4 = 0000000000000001
Apr 14 00:31:08 lila kernel: t5 = 2834362d657a6973 t6 =
000000000000001c t7 = fffffc00031f8000
Apr 14 00:31:08 lila kernel: s0 = 0000000000000000 s1 =
fffffc000034e0d0 s2 = 0000000000000000
Apr 14 00:31:08 lila kernel: s3 = 000000011ffff3e4 s4 =
0000000000000000 s5 = fffffc0003840000
Apr 14 00:31:08 lila kernel: s6 = 0000000000000801
Apr 14 00:31:08 lila kernel: a0 = 2834362d657a6973 a1 =
0000000000000028 a2 = 0000000000000001
Apr 14 00:31:08 lila kernel: a3 = 0000000000000028 a4 =
0000000000000001 a5 = 0000000000000000
Apr 14 00:31:08 lila kernel: t8 = 0000000000000000 t9 =
fffffc0000540848 t10= fffffc0003ff31c8
Apr 14 00:31:08 lila kernel: t11= fffffc00005c3010 pv =
fffffc0000314300 at = fffffffc002e6b84
Apr 14 00:31:08 lila kernel: gp = fffffc0000560848 sp = fffffc00031fbcd8
Apr 14 00:31:08 lila kernel: Trace:fffffc0000312ec0 fffffc0000379408
fffffc000034e050 fffffc0000379b78 fffffc000034e0d4 fffffc0000397e3c
fffffc0000313134 fffffc0000313090
Apr 14 00:31:08 lila kernel: Code: 3c900001 3cb00000 47f60401
e43fff1d c3ffff21 47ff0401 <2cb00000> 2cf00003
Starting NFS kernel daemon: nfsd/etc/init.d/nfs-kernel-server: line 79:
22279 Segmentation fault start-stop-daemon --start --quiet --exec
$PREFIX/sbin/rpc.nfsd -- $RPCNFSDCOUNT
mountd.
lila:~#
--------------
(could be that the order is a bit messed up, i copied the kernel oops
from /var/log/messages between "start" and "segfault".)
Thank you very much,
Christian.
next prev parent reply other threads:[~2003-04-13 22:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-12 13:45 2.5.67 alpha compile failure T. Weyergraf
2003-04-12 19:42 ` Måns Rullgård
2003-04-13 22:50 ` Christian [this message]
2003-04-14 11:37 ` nfs-kernel-server Oopses with 2.5.67 Christian
2003-04-14 11:54 ` Måns Rullgård
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=3E99E9A5.7090302@g-house.de \
--to=evil@g-house.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox