Benches Mac desktops

4

smbfs throws Kernel Panic when accessing Window...

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

I've found a few other discussions that list the same issue but no solutions. The basic problem is that I have a Mac Pro running 10.5.2 and Quark 7.3.1. The system is bound to AD using Apple's plugin. The machine is connecting to a number of file servers, all but one is a NAS box. When Quark attempts to navigate the network share on the NAS devices in order to place or update a linked image, the machine kernel panics. This is 100% reproducible on this workstation but not on the 5 G5 Towers that were cloned from this Mac Pro. The KPs are always the same, detailing com.apple.smbfs framework as the problem. The cpu core will change but otherwise all panics looks much like below.

As mentioned, this does not occur on the G5 systems in the environment which are clones of the Mac Pro. I do not have another Intel based system to confirm that it is a platform issue but I am working on providing that.

My basic question is can anyone suggest a possible solution other than cleaning the caches, doing an archive and install (machine was installed on Wednesday, was put into service Monday, showed the symptom immediately. The machine did not have a chance to damage itself.

Any suggestions appreciated.

------

Mon May 12 11:50:17 2008
panic(cpu 6 caller 0x001A8C8A): Kernel trap at 0x5e7ae24a, type 14=page fault, registers:
CR0: 0x80010033, CR2: 0x00000010, CR3: 0x00f50000, CR4: 0x00000660
EAX: 0x00000800, EBX: 0x00000800, ECX: 0x00000f80, EDX: 0x00000000
CR2: 0x00000010, EBP: 0x652ef558, ESI: 0x00000000, EDI: 0x652ef780
EFL: 0x00010206, EIP: 0x5e7ae24a, CS: 0x00000008, DS: 0x652e0010
Error code: 0x00000000

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x652ef2a8 : 0x12b0f7 (0x4581f4 0x652ef2dc 0x133230 0x0)
0x652ef2f8 : 0x1a8c8a (0x461720 0x5e7ae24a 0xe 0x460ed0)
0x652ef3d8 : 0x19ece5 (0x652ef3f0 0x652ef458 0x652ef558 0x5e7ae24a)
0x652ef3e8 : 0x5e7ae24a (0xe 0x48 0x652e0070 0x1a0010)
0x652ef558 : 0x5e7b0036 (0x9d92830 0x1 0x0 0x0)
0x652ef578 : 0x1f2707 (0x652ef59c 0x0 0x652ef5a8 0x6e71330)
0x652ef5c8 : 0x1f51dd (0x9d92830 0x652ef780 0x8b3b624 0x386184)
0x652ef628 : 0x1dc413 (0x9d92830 0x652ef780 0x8b3b624 0x0)
0x652ef8c8 : 0x357df8 (0x6e71330 0x0 0x80000008 0x8b3b624)
0x652ef908 : 0x1d894d (0x6eba604 0x6e71330 0x80000008 0x8b3b624)
0x652ef958 : 0x1c5d49 (0x9d92830 0x0 0x80000008 0x8b3b624)
0x652eff78 : 0x3dcf13 (0x77037b0 0x8b3b520 0x8b3b564 0x0)
0x652effc8 : 0x19f1c3 (0x89f7b40 0x0 0x1a20b5 0x89f7b40)
No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb046b328
Kernel loadable modules in backtrace (with dependencies):
com.apple.filesystems.smbfs(1.4.2)@0x5e798000->0x5e7c7fff

BSD process name corresponding to current thread: QuarkXPress

Mac OS version:
9C7010

Kernel version:
Darwin Kernel Version 9.2.2: Tue Mar 4 21:17:34 PST 2008; root:xnu-1228.4.31~1/RELEASE_I386
System model name: MacPro3,1 (Mac-F42C88C8)

4 replies

Sign in or join Beachball Help to reply.

  1. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I've got 3 iMac7,1 in the same environment (AD domain, using every moment smb shares) and every single iMac from time to time raises kernel panicks.
    So, this is clearly something related to Leopard being in a AD domain.

    Here it is an example:

    panic(cpu 1 caller 0x001A8C8A): Kernel trap at 0x00c9e24a, type 14=page fault, registers:
    CR0: 0x8001003b, CR2: 0x00000010, CR3: 0x01139000, CR4: 0x00000660
    EAX: 0x00000800, EBX: 0x00000800, ECX: 0x00000f80, EDX: 0x00000000
    CR2: 0x00000010, EBP: 0x2e90b558, ESI: 0x00000000, EDI: 0x2e90b780
    EFL: 0x00010206, EIP: 0x00c9e24a, CS: 0x00000008, DS: 0x2e900010
    Error code: 0x00000000

    Backtrace, Format - Frame : Return Address (4 potential args on stack)
    0x2e90b2a8 : 0x12b0e1 (0x457024 0x2e90b2dc 0x13321a 0x0)
    0x2e90b2f8 : 0x1a8c8a (0x460550 0xc9e24a 0xe 0x45fd00)
    0x2e90b3d8 : 0x19eb67 (0x2e90b3f0 0x2e90b458 0x2e90b558 0xc9e24a)
    0x2e90b3e8 : 0xc9e24a (0xe 0x48 0x2e900070 0x1a0010)
    0x2e90b558 : 0xca0036 (0x61f8cb0 0x1 0x2e90b5a8 0xca4448)
    0x2e90b578 : 0x1f1707 (0x2e90b59c 0x216 0x2e90b5d8 0x38723e)
    0x2e90b5c8 : 0x1f41dd (0x61f8cb0 0x2e90b780 0xa9967c4 0x385118)
    0x2e90b628 : 0x1db413 (0x61f8cb0 0x2e90b780 0xa9967c4 0x13073d)
    0x2e90b8c8 : 0x356d8c (0x4145880 0x0 0x80000064 0xa9967c4)
    0x2e90b908 : 0x1d794d (0x419fa04 0x4145880 0x80000064 0xa9967c4)
    0x2e90b958 : 0x1c4c77 (0x61f8cb0 0x0 0x80000064 0xa9967c4)
    0x2e90bf78 : 0x3dbe77 (0x43972e0 0xa9966c0 0xa996704 0x3303)
    0x2e90bfc8 : 0x19f084 (0xa8be480 0x0 0x1a20b5 0xa9097d8)
    No mapping exists for frame pointer
    Backtrace terminated-invalid frame pointer 0xb0d42348
    Kernel loadable modules in backtrace (with dependencies):
    com.apple.filesystems.smbfs(1.4.2)@0xc88000->0xcb7fff

    BSD process name corresponding to current thread: Adobe Illustrato

    Mac OS version:
    9C31

    Kernel version:
    Darwin Kernel Version 9.2.0: Tue Feb 5 16:13:22 PST 2008; root:xnu-1228.3.13~1/RELEASE_I386
    System model name: iMac7,1 (Mac-F42386C8)

  2. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I am getting the exact same results, I am trying to access a NAS device on a network, but the network is not in an AD Domain. The Nas is running smb shares and is causing a kernel panic nearly every time. This started at the beginning of May.

  3. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Does the NAS support AFP?

  4. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    AFP is not a solution based on environment. As all Windows servers, the NAS had Services for Macintosh. But that is so antiquated that it would be a worse resolution for the environment. ExtremeZ is also not going to happen. In this and other situations, we are bound to using SMB/CIFS shares.

    Additionally, changing the file sharing protocol to resolve a problem with a specific hardware and software combination is not the answer. I've made some progress on this and will provide my findings shortly.