oops in 2.4.1-pre8

Hello.

I've got a Dell Precision 420 (dual P3/800 w/1gb RDRAM).

I'm consistently getting an oops when accessing any smbfs mount whether running 'ls' inside the smbfs mount or hitting TAB for filename completion of a directory in an smbfs mount. I have another machine (dual P2/300 w/320MB memory) that does not have this problem. The P2 has an eepro100 ethernet card whereas the Dell has the built-in 3c920 (3c905c emulation).

Below is the ksymoops output. The oops screen I manually typed onto my other computer because the /var/log/messages file gets corrupted when this occurs and I don't know how to save the oops screen on the computer itself. SAR-S, SAR-U say they're doing to do their action but do not actually sync or remount the disks. CAD does not reboot the computer. SAR-B does reboot the machine though.

Unable to handle kernel NULL pointer dereference at virtual address 00000000
c012b2fb
*pde = 00000000
Oops: 0000
CPU:    0
EIP:    0010:[<c012b2fb>]

Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010202
eax: 00000001 ebx: 00000000 ecx: c02ea430 edx: 0003ff9e
esi: c2093878 edi: 00000000 ebp: f7e00004 esp: f73b3e18
ds: 0018 es: 0018 ss: 0018
Process ls (pid: 862, stackpage=f73b3000)

Stack: c02ea430 c02ea690 f73b3e4c 00000000 c2093878 f7e00004 f73b3e4c 00000001
     c012e829 c2093878 00000000 00000001 f7300004 c2093878 c019344a 
f7918e9c
     c0000000 00000012 00000000 fe1ec014 0000001a 00000012 c019218b 
00000000
Call Trace: [<c012e829>] [<c019344a>] [<c019218b>] [<f8957a20>] [<f8959188>] [<c018fde6>] [<f8959048>]
     [<f895903c>] [<c0191364>] [<c0192259>] [<c0191569>] [<c014e338>] 
[<c014e140>] [<c0109113>]
Code: 8b 07 ff 47 18 89 70 04 89 06 89 7e 04 89 37 89 7e 08 8b 55

Trace; c012e829 <grab_cache_page+79/a0> Trace; c019344a <smb_trans2_request+18a/1f0> Trace; c019218b <smb_add_to_cache+fb/180> Trace; f8957a20 <__module_using_checksums+3b52/??? Trace; f8959188 <__module_using_checksums+52ba/??? Trace; c018fde6 <smb_proc_readdir_long+456/4d0> Trace; f8959048 <__module_using_checksums+517a/??? Trace; f895903c <__module_using_checksums+516e/??? Trace; c0191364 <smb_proc_readdir+24/40> Trace; c0192259 <smb_refill_dircache+29/70> Trace; c0191569 <smb_readdir+d9/190> Trace; c014e338 <sys_getdents64+b8/170> Trace; c014e140 <filldir64+0/140>
Trace; c0109113 <system_call+33/38>
Code; c012b2fb <add_to_page_cache_unique+bb/120> 00000000 <_EIP>:
Code; c012b2fb <add_to_page_cache_unique+bb/120> <=====
0: 8b 07 mov (%edi),%eax <=====
Code; c012b2fd <add_to_page_cache_unique+bd/120>
2: ff 47 18 incl 0x18(%edi)
Code; c012b300 <add_to_page_cache_unique+c0/120>
5: 89 70 04 mov %esi,0x4(%eax)
Code; c012b303 <add_to_page_cache_unique+c3/120>
8: 89 06 mov %eax,(%esi)
Code; c012b305 <add_to_page_cache_unique+c5/120>
a: 89 7e 04 mov %edi,0x4(%esi)
Code; c012b308 <add_to_page_cache_unique+c8/120>
d: 89 37 mov %esi,(%edi)
Code; c012b30a <add_to_page_cache_unique+ca/120>
f: 89 7e 08 mov %edi,0x8(%esi)
Code; c012b30d <add_to_page_cache_unique+cd/120>
12: 8b 55 00 mov 0x0(%ebp),%edx

Ethernet is compiled into the kernel as is smbfs (not as modules). I've compiled this kernel with 4GB bigmem support (otherwise I only get 8xxMB total).

If anyone needs more please let me know.

--Scott

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/

That other machine is not compiled with bigmem, I assume.

The smbfs cache code in 2.4.0 doesn't work with bigmem. For now disable bigmem or don't use smbfs, it's oopsing all the time.

Rainer Mager reported the same thing yesterday ("Oops with 4GB memory setting in 2.4.0 stable" if you want to read the thread).

I am currently looking into this ... what kind of server are you connecting to? win2k/NT4/9x? It is easier to test with those than the more exotic OS/2 & NetApp.

/Urban

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/

Hi Urban.

I'm connecting to a Win2K server (same share between computers). A slight change in my previous post: my dual P2 w/320MB appears to be running 2.4.0-ac9 instead of 2.4.1-pre8. The bigmem machine (1gb mem) had the oops on 2.4.0-ac9 but before reporting I thought I'd try 2.4.1-pre8 and see if it also had the oops. (This morning the small mem machine had a problem but I'll put that in a separate email.)

Earlier I had tried 2.4.0-test12 but it partially scrambled my root partition so I went back to 2.2.19-pre2. After the oops I tried 2.4.0 straight but when it was booting it decided my root partition had been umounted not-cleanly and decided it needed to do lots of icky things to my root partition. I just rebooted it (without letting it do any changes) and went back into 2.4.1-pre8 and let it clean up the root partition. So I don't know if 2.4.0 straight would do this (apparently it does from other people's reports) since 2.4.0 didn't want to play nice on my machine.

Since I can't do without smbfs I guess I'll have to do without bigmem. Please let me know when you're ready to test some fixes; I would be glad to help testing.

--Scott

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/