smbfs Oops with Linux 2.6.3

From: Adam Sampson (azz_at_us-lot.org)
Date: 03/10/04

  • Next message: Stefan Smietanowski: "Re: Kernel 2.6.3 patch for Intel Compiler 8.0" 
    Date:	Wed, 10 Mar 2004 01:39:33 +0000
To: urban@teststation.com

    Hiya.

    I use smbfs on my x86 Linux 2.6.3 machine to mount filesystems from a
    (Debian) Samba 3.0.0beta2 server. This has worked fine with both this
    kernel and previous ones for the last few months, but I've just had an
    Oops message while trying to open a directory with ROX-Filer. The
    filesystem in question is automounted (using autofs4), and this would
    have been the first operation upon it after being mounted.

    My kernel config is at <http://offog.org/stuff/config-2.6.3>. Here's the
    ksymoops output:

    ksymoops 2.4.9 on i686 2.6.3. Options used
         -v /src/linux-2.6.3/vmlinux (specified)
         -k /proc/ksyms (default)
         -l /proc/modules (default)
         -o /lib/modules/2.6.3/ (default)
         -m /src/linux-2.6.3/System.map (specified)

    Error (regular_file): read_ksyms stat /proc/ksyms failed
    No modules in ksyms, skipping objects
    No ksyms, skipping lsmod
    Unable to handle kernel NULL pointer dereference at virtual address 00000000
    00000000
    *pde = 00000000
    Oops: 0000 [#1]
    CPU: 0
    EIP: 0060:[<00000000>] Not tainted
    Using defaults from ksymoops -t elf32-i386 -a i386
    EFLAGS: 00210246
    eax: ee433c40 ebx: 00000002 ecx: c5107840 edx: cf84bfa0
    esi: c0165560 edi: c1750080 ebp: cf84bf68 esp: cf84bef8
    ds: 007b es: 007b ss: 0068
    Stack: c01dbbfb c5107840 cf84bfa0 c0165560 cf84bf2c 00000000 00000002 00000004
           d4ea7ee4 00000000 eecd0000 c40520c0 d0a0c980 00000000 5e50af11 00000000
           00000000 00000000 eecd0000 00000002 00000000 00000000 00000001 00000004
    Call Trace:
     [<c01dbbfb>] smb_readdir+0x4fb/0x6e0
     [<c0165560>] filldir64+0x0/0x130
     [<c016524a>] vfs_readdir+0x8a/0x90
     [<c0165560>] filldir64+0x0/0x130
     [<c01656fd>] sys_getdents64+0x6d/0xa6
     [<c0165560>] filldir64+0x0/0x130
     [<c010adff>] syscall_call+0x7/0xb
    Code: Bad EIP value.

    >>EIP; 00000000 Before first symbol

    >>eax; ee433c40 <_end+2dc7cad8/3f846e98>
    >>ecx; c5107840 <_end+49506d8/3f846e98>
    >>edx; cf84bfa0 <_end+f094e38/3f846e98>
    >>esi; c0165560 <filldir64+0/130>
    >>edi; c1750080 <_end+f98f18/3f846e98>
    >>ebp; cf84bf68 <_end+f094e00/3f846e98>
    >>esp; cf84bef8 <_end+f094d90/3f846e98>

    Trace; c01dbbfb <smb_readdir+4fb/6e0>
    Trace; c0165560 <filldir64+0/130>
    Trace; c016524a <vfs_readdir+8a/90>
    Trace; c0165560 <filldir64+0/130>
    Trace; c01656fd <sys_getdents64+6d/a6>
    Trace; c0165560 <filldir64+0/130>
    Trace; c010adff <syscall_call+7/b>

    1 error issued. Results may not be reliable.

    And here's the raw Oops:

    Unable to handle kernel NULL pointer dereference at virtual address 00000000
     printing eip:
    00000000
    *pde = 00000000
    Oops: 0000 [#1]
    CPU: 0
    EIP: 0060:[<00000000>] Not tainted
    EFLAGS: 00210246
    EIP is at 0x0
    eax: ee433c40 ebx: 00000002 ecx: c5107840 edx: cf84bfa0
    esi: c0165560 edi: c1750080 ebp: cf84bf68 esp: cf84bef8
    ds: 007b es: 007b ss: 0068
    Process ROX-Filer (pid: 19894, threadinfo=cf84a000 task=d0b93320)
    Stack: c01dbbfb c5107840 cf84bfa0 c0165560 cf84bf2c 00000000 00000002 00000004
           d4ea7ee4 00000000 eecd0000 c40520c0 d0a0c980 00000000 5e50af11 00000000
           00000000 00000000 eecd0000 00000002 00000000 00000000 00000001 00000004
    Call Trace:
     [<c01dbbfb>] smb_readdir+0x4fb/0x6e0
     [<c0165560>] filldir64+0x0/0x130
     [<c016524a>] vfs_readdir+0x8a/0x90
     [<c0165560>] filldir64+0x0/0x130
     [<c01656fd>] sys_getdents64+0x6d/0xa6
     [<c0165560>] filldir64+0x0/0x130
     [<c010adff>] syscall_call+0x7/0xb

    Code: Bad EIP value.

    If there's any other information that'd be useful, please let me know.

    Thanks, 

    -- 
Adam Sampson <azz@us-lot.org>                        <http://offog.org/>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
  • Next message: Stefan Smietanowski: "Re: Kernel 2.6.3 patch for Intel Compiler 8.0"

    Relevant Pages

    • OOPS: KDE making my kernel flake out?
      ... The Oops actually came from the system just after the Oops occured. ... I think the kernel may have been 2.6.7. ... EIP is at wait_for_completion+0xdc/0x252 ... Inc. VT82xxxxx UHCI USB 1.1 ...
      (Linux-Kernel)
    • RE: Kernel oops in mm/rmap.c in 2.6.11rc4-bk9
      ... Fresher trace of my oops captured over a serial tty link (kernel now ... Oops: invalid operand ...
      (Linux-Kernel)
    • Re: 2.6.0-test8-mm1
      ... > Btw. a similar Oops at the same place occours when the uhci-hcd module is ... > The attached patch prevents the kernel from Oopsing, ... WARN_ONso we'd get a stack trace in addition to the printk). ... Unable to handle kernel NULL pointer dereference at virtual address ...
      (Linux-Kernel)
    • kernel oops on ia64 (2.6.6 + 0521 ia64 patch)
      ... The box is a HP rx2600 with a single processor, kernel is compiled in UP ... I could oops the machine by running a configure script two times so far. ... Call Trace: ... Unable to handle kernel NULL pointer dereference ...
      (Linux-Kernel)
    • Re: ieee1394 and fbdev oops in 2.6.3rc2
      ... > PowerMac motherboard: PowerMac G4 AGP Graphics ... > Call trace: ... mount version older than kernel ... EIP is at 0xffedba55 ...
      (Linux-Kernel)