2.4.18 mount.smbfs oops

2.4.18 mount.smbfs oops

Post by Sandino Araico Sánche » Fri, 05 Apr 2002 10:00:16



1. mount -t smbfs -o uid=500,gid=500 //blue/shared-dir /mnt/smb
    The smbmount asked me for a password, I pressed enter
2. df
    Nothing strange happens
3. ls /mnt/smb
    The Oops happens.

The Windows machine is Windows Xp, the ksymoops output attached.

--
Sandino Araico Snchez

Quote:>drop table internet;

OK, 135454265363565609860398636678346496 rows affected.
"oh *" --fluxrad

[ Oops-2002-04-03-smbfs.ksymoops 3K ]
ksymoops 2.3.4 on i686 2.4.18.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.4.18/ (default)
     -m /usr/src/linux/System.map (default)

Warning: You did not tell me where to find symbol information.  I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc.  ksymoops -h explains the options.

Warning (compare_maps): ksyms_base symbol acpi_fadt_R__ver_acpi_fadt not found in System.map.  Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol acpi_gbl_FADT_R__ver_acpi_gbl_FADT not found in System.map.  Ignoring ksyms_base entry
Unable to handle kernel paging request at virtual address e0000000
e0de895c
*pde = 00000000
Oops: 0000
CPU:    0
EIP:    0010:[<e0de895c>]    Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010282
eax: 7848f5e4   ebx: e0000000   ecx: f2ebe3fd   edx: 180e9794
esi: 08a0835c   edi: d8199e30   ebp: d8199ec8   esp: d8199de0
ds: 0018   es: 0018   ss: 0018
Process ls (pid: 1445, stackpage=d8199000)
Stack: c0143914 d8199e98 e0df913c 00000000 00000000 00000000 00000000 cfbe0280
       d1a921e0 00000000 0ecad52d 00000000 00000000 00000000 ce54b000 00000022
       00000000 00000000 00000001 00000024 e0de71c9 d089c7a0 d8199fb0 c0143914
Call Trace: [<c0143914>] [<e0de71c9>] [<c0143914>] [<c0143914>] [<e0de7258>]
   [<c0143914>] [<e0de80fb>] [<c0143914>] [<c0143546>] [<c0143914>] [<c0143abf>]
   [<c0143914>] [<c0126377>] [<c0106e23>]
Code: 0f b6 03 43 89 c2 c1 e2 04 01 f2 c1 e8 04 01 c2 8d 04 92 8d

Quote:>>EIP; e0de895c <END_OF_CODE+1bc15d/????>   <=====

Trace; c0143914 <filldir64+0/15c>
Trace; e0de71c9 <END_OF_CODE+1ba9ca/????>
Trace; c0143914 <filldir64+0/15c>
Trace; c0143914 <filldir64+0/15c>
Trace; e0de7258 <END_OF_CODE+1baa59/????>
Trace; c0143914 <filldir64+0/15c>
Trace; e0de80fb <END_OF_CODE+1bb8fc/????>
Trace; c0143914 <filldir64+0/15c>
Trace; c0143546 <vfs_readdir+8e/d4>
Trace; c0143914 <filldir64+0/15c>
Trace; c0143abf <sys_getdents64+4f/103>
Trace; c0143914 <filldir64+0/15c>
Trace; c0126377 <sys_brk+bf/ec>
Trace; c0106e23 <system_call+33/38>
Code;  e0de895c <END_OF_CODE+1bc15d/????>
00000000 <_EIP>:
Code;  e0de895c <END_OF_CODE+1bc15d/????>   <=====
   0:   0f b6 03                  movzbl (%ebx),%eax   <=====
Code;  e0de895f <END_OF_CODE+1bc160/????>
   3:   43                        inc    %ebx
Code;  e0de8960 <END_OF_CODE+1bc161/????>
   4:   89 c2                     mov    %eax,%edx
Code;  e0de8962 <END_OF_CODE+1bc163/????>
   6:   c1 e2 04                  shl    $0x4,%edx
Code;  e0de8965 <END_OF_CODE+1bc166/????>
   9:   01 f2                     add    %esi,%edx
Code;  e0de8967 <END_OF_CODE+1bc168/????>
   b:   c1 e8 04                  shr    $0x4,%eax
Code;  e0de896a <END_OF_CODE+1bc16b/????>
   e:   01 c2                     add    %eax,%edx
Code;  e0de896c <END_OF_CODE+1bc16d/????>
  10:   8d 04 92                  lea    (%edx,%edx,4),%eax
Code;  e0de896f <END_OF_CODE+1bc170/????>
  13:   8d 00                     lea    (%eax),%eax

3 warnings issued.  Results may not be reliable.

 
 
 

2.4.18 mount.smbfs oops

Post by Adrian Bun » Fri, 05 Apr 2002 18:10:08



> 1. mount -t smbfs -o uid=500,gid=500 //blue/shared-dir /mnt/smb
>     The smbmount asked me for a password, I pressed enter
> 2. df
>     Nothing strange happens
> 3. ls /mnt/smb
>     The Oops happens.

> The Windows machine is Windows Xp, the ksymoops output attached.

This sounds like the nls bug. In this case a patch is at
  http://www.hojdpunkten.ac.se/054/samba/00-smbfs-2.4.18-codepage.patch.gz

Quote:> Sandino Araico Snchez

cu
Adrian

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

1. sorry mistake: [2.4.18] another oops in smbfs

Sorry,

I used the wrong system.map

The call trace is now very similar to the one of Cyrille
Chepelov.
Just ignore my previous message.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

2. zones +default gateway

3. SMBFS related oops in 2.4.18

4. open source development questions

5. Linux Kernel Crash - Vanilla 2.4.18/Redhat 2.4.18-5

6. Compiling Pine 3.91 (Solaris 2.5)

7. Linux Kernel Crash - Vanilla 2.4.18/Redhat 2.4.18-5 (2nd try =) )

8. asking for comments on a script

9. what is the difference between 2.4.18-14 and 2.4.18-17.8.0

10. Very High Load on Disk Activity in 2.4.18 (and 2.4.18-pre8)

11. smbfs codepage fixes for 2.4.18

12. file listing problem in smbfs, kernel 2.4.18

13. Anyone else seen VM related oops on 2.4.18?