Skip to contentSkip to conversation

linux-2.6.8-rc4-bk1 - nfsd oops when starting the first client

DISCUSSION Alexander Stohr 2 participants 2 messages Aug 13, 2004

lore
Share & tools
lore
#0 lore raw

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.

Signature · 2 lines
NEU: WLAN-Router für 0,- EUR* - auch für DSL-Wechsler!
GMX DSL = supergünstig & kabellos http://www.gmx.net/de/go/dsl

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  
#1 lore raw
Quoted 16 lines · Alexander Stohr

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.

Quoted 7 lines

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.

This might solve it:

	http://lkml.org/lkml/2004/8/11/264
Signature · 1 line
Peter Zijlstra <[email protected]>