Re: Panics on a new MacPro
Re: Panics on a new MacPro
- Subject: Re: Panics on a new MacPro
- From: "Brian Bechtel" <email@hidden>
- Date: Tue, 25 Nov 2008 13:20:12 -0800
On Tue, Nov 25, 2008 at 11:53 AM, George Plymale
<email@hidden> wrote:
> I just purchased a refurbished MacPro and am quite concerned and was hopeful
> for perhaps some additional enlightenment on the following panics that seem
> fairly disjointed.
The two panics are pretty different.
> Obviously I'm rather concerned with the issue as I fear
> perhaps a processor may be at fault. Googling the first panic has lead me
> to wonder if it is tied to Parallels and the second is fairly nebulous to me
> at the moment. Please advise as to what you may see is going on here:
>
> Sat Nov 22 13:22:49 2008
> panic(cpu 7 caller 0x00193077): "pmap_flush_tlbs() timeout: " "cpu(s)
> failing to respond to interrupts, pmap=0x536500
> cpus_to_respond=0x4"@/SourceCache/xnu/xnu-1228.7.58/osfmk/i386/pmap.c:4580
CPU 3 held off interrupts too long (the cpus_to_respond is a mask)
This panic is a message from the core which noticed the problem, so
the backtrace is useless. 10.5.5 has some new code to report the
unresponsive processor, but not all cases can be covered. I would
tend to think this is a software issue, not a hardware issue.
> Tue Nov 25 13:16:03 2008
> panic(cpu 0 caller 0x001A8CEC): Kernel trap at 0x001924c7, type 14=page
> fault, registers:
> CR0: 0x8001003b, CR2: 0x767bc000, CR3: 0x00d44000, CR4: 0x00000660
> EAX: 0x767bc000, EBX: 0x91d8d000, ECX: 0x1114832c, EDX: 0x00000000
> CR2: 0x767bc000, EBP: 0x8825bdd8, ESI: 0x1114832c, EDI: 0x1114832c
> EFL: 0x00010206, EIP: 0x001924c7, CS: 0x00000008, DS: 0x00000010
> Error code: 0x00000000
>
> Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
> 0x8825bbc8 : 0x12b0fa (0x459234 0x8825bbfc 0x133243 0x0)
> 0x8825bc18 : 0x1a8cec (0x4627a0 0x1924c7 0xe 0x461f50)
> 0x8825bcf8 : 0x19eed5 (0x8825bd10 0xa 0x8825bdd8 0x1924c7)
> 0x8825bd08 : 0x1924c7 (0xe 0x48 0x10 0x10)
> 0x8825bdd8 : 0x19273b (0x1114832c 0x91d8d000 0x0 0x193796)
> 0x8825be38 : 0x193796 (0x1114832c 0x91d8d000 0x0 0x0)
> 0x8825be98 : 0x193b91 (0x1114832c 0x91d8d000 0x0 0x53c88d4)
> 0x8825bed8 : 0x193c04 (0x46e20 0x60 0x0 0x3d065ac)
> 0x8825bef8 : 0x17c2c0 (0x46e20 0x8825bf7c 0x12c 0xf4240)
> 0x8825bf98 : 0x17c67d (0x0 0x0 0x8825bfc8 0x12fa2410)
> 0x8825bfc8 : 0x19eccc (0x0 0x0 0x1a20b5 0x23bb79e0)
> Backtrace terminated-invalid frame pointer 0
This panic has the following backtrace:
0x12b0fa <panic+422>
0x1a8cec <kernel_trap+1450>
0x19eed5 <trap_from_kernel+26>
0x1924c7 <pmap64_pdpt+92>
0x19273b <pmap64_pde+79>
0x193796 <pmap_pte+82>
0x193b91 <phys_attribute_test+193>
0x193c04 <pmap_get_refmod+25>
0x17c2c0 <vm_pageout_scan+3578>
0x17c67d <vm_pageout_continue+58>
0x19eccc <call_continuation+28>
a corruption of kernel data structures is the simple way to describe
this. The pmap data structures are damaged somehow. This is most
commonly software, but I suppose it could conceivably be hardware...
First suspect Parallels. It's a common reason. Upgrade to the latest
version available, or remove it altogether and see if the panics stop.
Next suspect other hack-ish software which tries to modify system behavior.
It's remotely possible it's the hardware. Use the hardware
diagnostics which came with the machine, or get them from
http://www.info.apple.com/discimages/index.html and if you find a
problem, contact Apple and ask for a replacement.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden