[~bash $]

I think my Mac Pro just underwent a kernel panic. Here's the panic.log:
--

Tue Oct 23 15:06:51 2007
panic(cpu 3 caller 0x001D2919): vnode_put(95244a4): iocount < 1
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x47e8b628 : 0x128d08 (0x3cc0a4 0x47e8b64c 0x131de5 0x0)
0x47e8b668 : 0x1d2919 (0x3d4f30 0x95244a4 0x47e8b6b8 0x1c4cea)
0x47e8b698 : 0x1d29cf (0x95244a4 0x297 0x47e8b6f8 0x95244a4)
0x47e8b6b8 : 0x1f61a7 (0x95244a4 0x47e8b7e8 0x679f9c0 0x47e8bf34)
0x47e8b808 : 0x1f645b (0x47e8bf34 0x47e8b884 0xa 0x13bdec)
0x47e8b8a8 : 0x1e5038 (0x47e8b8c8 0x47e8b8dc 0x47e8bf34 0x0)
0x47e8b8f8 : 0x1ccc89 (0x6805f78 0x47e8bac4 0x47e8bbd8 0x47e8bf34)
0x47e8b968 : 0x1cd4af (0x47e8baac 0x100 0x47e8bacc 0x0)
0x47e8ba18 : 0x1bdf09 (0x47e8baac 0x7177e00 0x0 0x0)
0x47e8bf58 : 0x37ad83 (0x6de5dac 0x6e08e70 0x6e08eb4 0x0)
0x47e8bfc8 : 0x19b28e (0x6b3eee0 0x0 0x19e0b5 0x6eb02c0) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb0119538

Kernel version:
Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386


*********
It was during a simple 'mv' within a particular (non-primary) internal hard disk. I'm just wondering, is there a chance that the drive is going bad?

Thanks ...



I know this is somewhat of a hardware question, but kernel events are Mac OS X software ... please move if deemed necessary.

[~bash $]

uh oh ... it happened again, this time on a different physical disk but in terminal.app during a similar 'mv' operation. I am bothered by the fact that it reported the same cpu3 ... could this core have gone bad somehow???

[seanc]

Could be the CPU, more likely to be RAM though.
Surely this should be in the Mac Pro forum?

[~bash $]

Originally Posted by seanc 

Could be the CPU, more likely to be RAM though.
Surely this should be in the Mac Pro forum?

While I did upgrade my RAM recently, it's been several weeks with no issue. Both times it was during an 'mv' command in Terminal.app, an app which I don't normally use for any kind of heavy lifting. One time (log above) was on a non-primary disk, the second time was on a primary disk.

Here's the second part of the log file, from the second event:

*********

Tue Oct 23 17:52:51 2007
panic(cpu 3 caller 0x001D2919): vnode_put(8429e70): iocount < 1
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x47c3b628 : 0x128d08 (0x3cc0a4 0x47c3b64c 0x131de5 0x0)
0x47c3b668 : 0x1d2919 (0x3d4f30 0x8429e70 0x47c3b6b8 0x1c4cea)
0x47c3b698 : 0x1d29cf (0x8429e70 0x297 0x47c3b6f8 0x8429e70)
0x47c3b6b8 : 0x1f61a7 (0x8429e70 0x47c3b7e8 0x67c7bd0 0x47c3bf34)
0x47c3b808 : 0x1f645b (0x47c3bf34 0x47c3b884 0xa 0x13bdec)
0x47c3b8a8 : 0x1e5038 (0x47c3b8c8 0x47c3b8dc 0x47c3bf34 0x0)
0x47c3b8f8 : 0x1ccc89 (0x680ff78 0x47c3bac4 0x47c3bbd8 0x47c3bf34)
0x47c3b968 : 0x1cd4af (0x47c3baac 0x100 0x47c3bacc 0x0)
0x47c3ba18 : 0x1bdf09 (0x47c3baac 0x7806300 0x0 0x0)
0x47c3bf58 : 0x37ad83 (0x6b7e3e8 0x6e238a8 0x6e238ec 0x0)
0x47c3bfc8 : 0x19b28e (0x6b84a80 0x0 0x19e0b5 0x6b347a0) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb0119178

Kernel version:
Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386


*********

[seanc]

Try taking out the RAM you put in and doing the same commands again, RAM doesn't have to be bad straight away, problems can surface days, months, years later.