Hi,
Just had a nice juicy kernel panic while editing with TextMate. Haven't seen one of these in years!
FWIW the report below.
Gerd
panic(cpu 0 caller 0x000E4488): vnode_rele_ext: vp 3bd0bdc usecount - ve : -1 Latest stack backtrace for cpu 0: Backtrace: 0x00095544 0x00095A5C 0x0002683C 0x000E4488 0x000F67B0 0x000F588C 0x000F4BB0 0x000F188C 0x002A7A94 0x000ABCB0 0x0329200B Proceeding back via exception chain: Exception state (sv=0x38402A00) PC=0x90088DAC; MSR=0x0000D030; DAR=0x06DAF000; DSISR=0x42000000; LR=0x00024074; R1=0xBFFFECE0; XCP=0x00000030 (0xC00 - System call)
Kernel version: Darwin Kernel Version 8.2.0: Fri Jun 24 17:46:54 PDT 2005; root:xnu-792.2.4.obj~3/RELEASE_PPCModel: PowerMac3,5, BootROM 4.2.5f1, 2 processors, PowerPC G4 (2.1), 800 MHz, 1.5 GB Graphics: NVIDIA GeForce2 MX with TwinView, GeForce2 TwinView, AGP, 64 MB Graphics: ATY,Rage6, ATY,Rage6, PCI, 32 MB Memory Module: DIMM0/J21, 512 MB, SDRAM, PC133-333 Memory Module: DIMM1/J22, 512 MB, SDRAM, PC133-333 Memory Module: DIMM2/J23, 512 MB, SDRAM, PC133-333 Network Service: Built-in Ethernet, Ethernet, en0 PCI Card: ATY,Rage6, Display, SLOT-2 Parallel ATA Device: ST330013A, 27.96 GB Parallel ATA Device: PIONEER DVD-RW DVR-103, USB Device: Hub, , Up to 12 Mb/sec, 500 mA USB Device: SoundSticks, harman/kardon, Up to 12 Mb/sec, 500 mA USB Device: Hub in Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/ sec, 500 mA USB Device: Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 250 mA USB Device: Studio Display, , Up to 1.5 Mb/sec, 500 mA USB Device: Hub, , Up to 12 Mb/sec, 500 mA USB Device: Studio Display, , Up to 1.5 Mb/sec, 500 mA USB Device: Hub, , Up to 12 Mb/sec, 500 mA USB Device: USB Receiver, Logitech, Up to 1.5 Mb/sec, 100 mA USB Device: USB2.0 MFP, EPSON, Up to 12 Mb/sec, 100 mA FireWire Device: iSight, Apple Computer, Inc., Up to 400 Mb/sec
On 03/09/2005, at 1.07, Gerd Knops wrote:
Just had a nice juicy kernel panic while editing with TextMate. Haven't seen one of these in years!
Was that while saving a file over a network mounted drive?
When I started to use setxattr() for metadata I got a lot of reports of kernel panics when saving to AFP mnted volumes -- turns out the fs driver is buggy. I introduced a workaround for that, but since then I've had two reports of kernel panics from setxattr(), so it seems my workaround wasn't a complete fix.
To disable the use of setxattr() execute (while TM is not running):
defaults write com.macromates.textmate OakDocumentDisableFSMetaData -bool true
I'll look into having TM disable metadata automatically only for drives that look like network mounts.
On Sep 3, 2005, at 5:33, Allan Odgaard wrote:
On 03/09/2005, at 1.07, Gerd Knops wrote:
Just had a nice juicy kernel panic while editing with TextMate. Haven't seen one of these in years!
Was that while saving a file over a network mounted drive?
My home directory including most files I work on (including the one before the panic) are NFS mounted from a FreeBSD box.
When I started to use setxattr() for metadata I got a lot of reports of kernel panics when saving to AFP mnted volumes -- turns out the fs driver is buggy. I introduced a workaround for that, but since then I've had two reports of kernel panics from setxattr(), so it seems my workaround wasn't a complete fix.
To disable the use of setxattr() execute (while TM is not running):
defaults write com.macromates.textmate OakDocumentDisableFSMetaData -bool true
I'll look into having TM disable metadata automatically only for drives that look like network mounts.
Should it panic again I'll try that. Worked all day today with TM and no problems other than occasional slow-down in performance.
Gerd