From: "Alexander Stohr" <Alexander.Stohr@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: linux-2.6.8-rc4-bk1 - nfsd oops when starting the first client
Date: Fri, 13 Aug 2004 09:59:46 +0200 (MEST) [thread overview]
Message-ID: <21288.1092383986@www20.gmx.net> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="us-ascii", Size: 870 bytes --]
Hello,
i am getting reproducible kernel oopses in a test environment
when booting the first diskless client (2.0.40-rc6)
for a dual (=SMP) AMD Athlon(tm) MP 1900+ that
is running a recent linux 2.6 bitkeeper kernel.
the oops exactly happens when the (trough bootp provided)
kernel on the client has fully started and wants
to access one of the first files on the server
by means of an nfs access.
see the system messages in the attachment.
the problem was never seen in kernel 2.6.7
for that or any other server.
is this problem known to the audience?
is there a patch to test for this problem?
-Alex. (i am not subscribed to this list, please CC me)
PS: due to sheduled two weeks absence i will not be able
to check my e-mail regularily.
--
NEU: WLAN-Router für 0,- EUR* - auch für DSL-Wechsler!
GMX DSL = supergünstig & kabellos http://www.gmx.net/de/go/dsl
[-- Attachment #2: nfs-oops.txt --]
[-- Type: text/plain, Size: 1608 bytes --]
linux-2.6.8-rc4-bk1
kernel: VFS: Mounted root (ext3 filesystem) readonly.
kernel: 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
ntpd[102]: no IPv6 interfaces found
kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000
kernel: printing eip:
kernel: c014629b
kernel: *pde = 376c4001
kernel: Oops: 0000 [#1]
kernel: PREEMPT SMP
kernel: Modules linked in: 3c59x
kernel: CPU: 0
kernel: EIP: 0060:[page_address+11/176] Not tainted
kernel: EFLAGS: 00010286 (2.6.8-rc4-bk1)
kernel: EIP is at page_address+0xb/0xb0
kernel: eax: 00000000 ebx: 00000000 ecx: 0000000a edx: 0000000a
kernel: esi: f7e9f200 edi: ffff7400 ebp: 00000009 esp: f7715f18
kernel: ds: 007b es: 007b ss: 0068
kernel: Process nfsd (pid: 74, threadinfo=f7715000 task=f77391f0)
kernel: Stack: c032b0dc c2341000 f7e9f200 ffff7400 00000009 c01ddffc 00000000 c2130e84
kernel: 00000020 f7e9f200 c03bbd38 f77178ec f7728014 c01d43ec f7e9f200 c2130eb0
kernel: c2341000 f7e9f264 f7e9f200 f77178ec c03bbd38 c032a362 f7e9f200 f7728014
kernel: Call Trace:
kernel: [svc_udp_recvfrom+236/640] svc_udp_recvfrom+0xec/0x280
kernel: [nfssvc_decode_readargs+204/288] nfssvc_decode_readargs+0xcc/0x120
kernel: [nfsd_dispatch+108/512] nfsd_dispatch+0x6c/0x200
kernel: [svc_process+1170/1515] svc_process+0x492/0x5eb
kernel: [nfsd+566/1120] nfsd+0x236/0x460
kernel: [nfsd+0/1120] nfsd+0x0/0x460
kernel: [kernel_thread_helper+5/20] kernel_thread_helper+0x5/0x14
kernel: Code: 8b 03 f6 c4 01 75 1e 2b 1d 10 02 4a c0 c1 fb 05 c1 e3 0c 8d
next reply other threads:[~2004-08-13 7:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-13 7:59 Alexander Stohr [this message]
2004-08-13 8:49 ` linux-2.6.8-rc4-bk1 - nfsd oops when starting the first client Peter Zijlstra
-- strict thread matches above, loose matches on Subject: below --
2004-08-13 8:44 Jani Averbach
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=21288.1092383986@www20.gmx.net \
--to=alexander.stohr@gmx.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