Panic on C2D Macbook Pro (repeatable)
 

I've tried a total of five times to do a full backup of my 15" MacBook Pro (new model with Core 2 Duo Processor). Four of the tries resulted in a Kernel Panic.

I'm backing up to a sparseimage file that is residing on an AFP file share. The server is running OSX Server v.10.4.8. (MBP is also 10.4.8). Connection is 1000bt/full duplex on both MBP and Server. This is the paid version of SuperDuper.

I've tried repairing permissions and running Disk Repair. All seems good.

Only once did the backup complete successfully. The panic info is below. Any ideas? (Note - no other apps were running during any backup attempt.)

panic(cpu 1 caller 0x001D07CB): vnode_put(5967d68): iocount < 1
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x36493b18 : 0x128d08 (0x3c9afc 0x36493b3c 0x131de5 0x0)
0x36493b58 : 0x1d07cb (0x3d2208 0x5967d68 0x36493d48 0x34405c)
0x36493b88 : 0x1d0881 (0x5967d68 0x4b6b1a0 0x0 0x36493d48)
0x36493ba8 : 0x1becdb (0x5967d68 0x36493f28 0x1 0x5967d68)
0x36493f58 : 0x3787be (0x53d29c4 0x55554d0 0x5555514 0x0)
0x36493fc8 : 0x19acde (0x54b2f20 0x0 0x19d0b5 0x4cd343c) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbffff208

Kernel version:
Darwin Kernel Version 8.8.2: Thu Sep 28 20:43:26 PDT 2006; root:xnu-792.14.14.obj~1/RELEASE_I386

Model: MacBookPro2,2, BootROM MBP22.00A5.B00, 2 processors, Intel Core 2 Duo, 2.33 GHz, 3 GB
Graphics: ATI Radeon X1600, ATY,RadeonX1600, PCIe, 256 MB
Memory Module: BANK 0/DIMM0, 2 GB, DDR2 SDRAM, 667 MHz
Memory Module: BANK 1/DIMM1, 1 GB, DDR2 SDRAM, 667 MHz
AirPort: AirPort Extreme, 1.0.27p1
Bluetooth: Version 1.7.11f14, 2 service, 0 devices, 1 incoming serial ports
Network Service: Built-in Ethernet, Ethernet, en0
Network Service: Parallels Host-Guest, Ethernet, en2
Network Service: Parallels NAT, Ethernet, en3
Serial ATA Device: FUJITSU MHW2120BH, 111.79 GB
Parallel ATA Device: MATSHITADVD-R UJ-857D
USB Device: Built-in iSight, Micron, Up to 480 Mb/sec, 500 mA
USB Device: Apple Internal Keyboard / Trackpad, Apple Computer, Up to 12 Mb/sec, 500 mA
USB Device: USB 1.1 2port downstream low power hub, Lite-On Technology, Up to 12 Mb/sec, 500 mA
USB Device: USB-PS/2 Optical Mouse, Logitech, Up to 1.5 Mb/sec, 100 mA
USB Device: USB Productivity Option Keyboard( has the hub in # 1 ), Lite-On Technology, Up to 12 Mb/sec, 200 mA
USB Device: IR Receiver, Apple Computer, Inc., Up to 12 Mb/sec, 500 mA
USB Device: Bluetooth HCI, Up to 12 Mb/sec, 500 mA

Well, vnode_put -- as far as I know -- indicates a low-level disk corruption problem. It could be on the destination image.

This could indicate network problems, memory problems... there are a lot of reasons -- all of it basically very, very low-level (and none "caused" by SuperDuper itself).

Have you tried repairing the image, or the source?

Thanks for the info - I'm now digging deep into the disk subsystems on both the server and the MBP.

I have run both permissions repair and disk repair on the source (it was OK). I ran disk repair on the destination and all was OK. The destination is a RAID 1 array using Softraid.

(Also, on each attempt I'm creating a new image file - never the same file twice - to try and keep the tests consistent.)

Just to be thorough, I ran Tech Tools Pro on the source (all tests OK), and did a review of the server's disk configuration.

I'm running several additional tests to see what may cause it to fail. I'll send another note telling my findings.

Thanks.

OK -- let me know what you find.

Orig problem may be fixed, but new ones emerge?
 

Well, here's an update:

A review of the server's RAID array concluded that we had SATA II drives on SATA I controllers. The drives *should* autoconfigure to accept the slower speed, however there was also a jumper to force the drives into SATA I mode. I set the jumpers, ran disk repair (just in case - still said OK) and then re-attempted some backups.

I performed the following backups with the following results:

Full backup to new sparseimage on the server: Backup ran fine. SD was all green, but I got the Spinning Beachball of Death on the SD app. Other apps and the OS seemed fine. Had to reboot to kill SD, since a force quit or Kill -9 on the processes didn't work. Reboot also hung, had to hard power off.

Smart Update backup to the previously created image: Flawless. SD even quit clean after the backup.

Ran another full backup to the server - this time a new/different image file. Ran for a while then the SD app crashed 1/3 the way through. (Note this is the first time I've ever seen the app itself crash.) Crashdump below.

I'm now re-running a full backup again just for giggles. It seems that the original problem is fixed (with the SATA/RAID config change) but other problems have surfaced. Are these new issues the same as the thread about 10.4.8 on Intel not being compatible with SD 2.1.3? (Note I have a new MBP, so downgrading to 10.4.7 is not an option.)

Thanks for all your help.

(Beginning of crashdump)
**********

Host Name: dlcmbp02
Date/Time: 2006-11-12 00:55:01.249 -0500
OS Version: 10.4.8 (Build 8N1037)
Report Version: 4

Command: SuperDuper!
Path: /Applications/SuperDuper!.app/Contents/MacOS/SuperDuper!
Parent: WindowServer [55]

Version: 2.1.3 (80)
Build Version: 2
Project Name: SuperDuper!
Source Version: 573

PID: 560
Thread: 7

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0xe171c360

Thread 0:
0 libSystem.B.dylib 0x90024427 semaphore_wait_signal_trap + 7
1 com.apple.AppKit 0x9327684d -[NSViewHierarchyLock lockForWriting] + 338
2 com.apple.AppKit 0x932d92ba -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVi sibleRectForView:] + 355
3 com.apple.AppKit 0x932d8c8e -[NSView displayIfNeeded] + 439
4 com.apple.AppKit 0x932d8a32 -[NSWindow displayIfNeeded] + 168
5 com.apple.AppKit 0x93328d6c _handleWindowNeedsDisplay + 206
6 com.apple.CoreFoundation 0x9082adae __CFRunLoopDoObservers + 342
7 com.apple.CoreFoundation 0x90829e50 CFRunLoopRunSpecific + 827
8 com.apple.CoreFoundation 0x90829b0e CFRunLoopRunInMode + 61
9 com.apple.HIToolbox 0x92dd8bef RunCurrentEventLoopInMode + 285
10 com.apple.HIToolbox 0x92dd82fd ReceiveNextEventCommon + 385
11 com.apple.HIToolbox 0x92dd8154 BlockUntilNextEventMatchingListInMode + 81
12 com.apple.AppKit 0x9325d465 _DPSNextEvent + 572
13 com.apple.AppKit 0x9325d056 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 137
14 com.apple.AppKit 0x93256ddb -[NSApplication run] + 512
15 com.apple.AppKit 0x9324ad2f NSApplicationMain + 573
16 com.blacey.SuperDuper! 0x0000270a 0x1000 + 5898
17 com.blacey.SuperDuper! 0x00002625 0x1000 + 5669

Thread 1:
0 libSystem.B.dylib 0x90009857 mach_msg_trap + 7
1 com.apple.CoreFoundation 0x9082a2f3 CFRunLoopRunSpecific + 2014
2 com.apple.CoreFoundation 0x90829b0e CFRunLoopRunInMode + 61
3 com.apple.audio.CoreAudio 0x9146441e HALRunLoop::OwnThread(void*) + 158
4 com.apple.audio.CoreAudio 0x91464239 CAPThread::Entry(CAPThread*) + 93
5 libSystem.B.dylib 0x90023d87 _pthread_body + 84

Thread 2:
0 libSystem.B.dylib 0x90009857 mach_msg_trap + 7
1 com.apple.CoreFoundation 0x9082a2f3 CFRunLoopRunSpecific + 2014
2 com.apple.CoreFoundation 0x90829b0e CFRunLoopRunInMode + 61
3 com.apple.Foundation 0x9262ba9b +[NSURLConnection(NSURLConnectionInternal) _resourceLoadLoop:] + 259
4 com.apple.Foundation 0x925f636c forkThreadForFunction + 123
5 libSystem.B.dylib 0x90023d87 _pthread_body + 84

Thread 3:
0 libSystem.B.dylib 0x90019d3c select + 12
1 libSystem.B.dylib 0x90023d87 _pthread_body + 84

Thread 4:
0 libSystem.B.dylib 0x90009857 mach_msg_trap + 7
1 com.apple.CoreFoundation 0x9082a2f3 CFRunLoopRunSpecific + 2014
2 com.apple.CoreFoundation 0x90829b0e CFRunLoopRunInMode + 61
3 com.apple.Foundation 0x92652c4e +[NSURLCache _diskCacheSyncLoop:] + 206
4 com.apple.Foundation 0x925f636c forkThreadForFunction + 123
5 libSystem.B.dylib 0x90023d87 _pthread_body + 84

Thread 5:
0 libSystem.B.dylib 0x900268bc kevent + 12
1 ...ple.CoreServices.CarbonCore 0x90cb4f84 PrivateMPEntryPoint + 51
2 libSystem.B.dylib 0x90023d87 _pthread_body + 84

Thread 6:
0 libSystem.B.dylib 0x90024427 semaphore_wait_signal_trap + 7
1 ...ple.CoreServices.CarbonCore 0x90cb5129 MPWaitOnQueue + 198
2 com.apple.DesktopServices 0x9251db5b TNodeSyncTask::SyncTaskProc(void*) + 143
3 ...ple.CoreServices.CarbonCore 0x90cb4f84 PrivateMPEntryPoint + 51
4 libSystem.B.dylib 0x90023d87 _pthread_body + 84

Thread 7 Crashed:
0 libSystem.B.dylib 0x90000f80 pthread_mutex_lock + 9
1 com.apple.CoreGraphics 0x903321f6 CGClipStackAddRect + 710
2 com.apple.CoreGraphics 0x9033352a CGGStateClipToRect + 323
3 com.apple.CoreGraphics 0x903333ca CGContextClipToRect + 97
4 com.apple.AppKit 0x932a3a72 NSRectClip + 106
5 com.apple.AppKit 0x932a3970 -[NSFocusState flush] + 166
6 com.apple.AppKit 0x932a2627 -[NSView _focusFromView:withContext:] + 436
7 com.apple.AppKit 0x932a21eb -[NSView lockFocusIfCanDraw] + 726
8 com.apple.AppKit 0x932a1d62 -[NSView lockFocus] + 35
9 com.apple.AppKit 0x933e9af1 -[NSUIHeartBeat lockFocusForView:inRect:needsTranslation:] + 1540
10 com.apple.AppKit 0x9342e31b -[NSProgressIndicator heartBeat:] + 1376
11 com.apple.AppKit 0x93334572 -[NSUIHeartBeat _heartBeatThread:] + 1147
12 com.apple.Foundation 0x925f636c forkThreadForFunction + 123
13 libSystem.B.dylib 0x90023d87 _pthread_body + 84

Thread 8:
0 libSystem.B.dylib 0x9000fb5c read + 12
1 libSystem.B.dylib 0x90023d87 _pthread_body + 84

Thread 9:
0 libSystem.B.dylib 0x9000fb5c read + 12
1 libSystem.B.dylib 0x90023d87 _pthread_body + 84

Thread 7 crashed with X86 Thread State (32-bit):
eax: 0xa031c360 ebx: 0x9032e663 ecx: 0x42c80000 edx: 0x41400000
edi: 0x00000010 esi: 0xa033808c ebp: 0xb02b18f8 esp: 0xb02b18bc
ss: 0x0000001f efl: 0x00010a86 eip: 0x90000f80 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037

That crash is the 10.4.8 crash, no question.

I don't know what might have caused your hang, but if it's beachballing and won't force quit, it's likely stuck in the kernel somewhere. But if everything's "green" then everything should have been completed. If this happens again, please sample SuperDuper! so we can see where it is.

Dave,

Thanks for all your help. I appreciate that we located a problem with my server before it caused any other issues.

I'll follow the other thread for a solution for the 10.4.8 problem. The way I understand the thread, it looks like the problem is with changes Apple made affecting the application. Is it the GUI Portion of the app that is impacted? In that case, any thought to making a command line or "stripped down UI" version to work around this problem?

I for one would be happy with an "ugly" interface as long as it was functional. Something I could reference from Cron or a shell script would be awesome.

thanks again

We've not (seriously) considered making SD! a command-line tool, no -- certainly not to work around this particular issue. I'm hoping Apple will fix it....

Core 2 Duo 2.33 GHz backup problems
 

I tried to back up from the new intel mac laptop to a removeable SATA drive. The backup crashed when trying to boot from it and my data on the laptop was also partially corrupted.

I corresponded with Dave Nanian at Shirt Pocket tech support who said the problem is with OS 10.4.8 and "Some intel macs".

I hope this gets straightened out soon. Not having a backup is not good.

barry

There is no reason for the data on the laptop to be corrupted, Barry: the crash is completely localized to the application that crashed. If you're experiencing corruption, you have another -- more serious -- issue.