Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Status
Not open for further replies.

JohnD

macrumors regular
Jun 2, 2005
150
97
Los Angeles, California
Look familiar? Clone of my Big Sur 11.4 VM, running on my 5,1 11.2.3 host, upgraded to the Monterey public beta. Came back to this. Could be Parallels not ready for Monterey, but perhaps could be related to our issue? I'm having too much deja-vu...

1625412066861.png


Code:
panic(cpu 0 caller 0xffffff7fa8905e4d): "hitting assertion" @AppleParavirtDisplayPipe.cpp:428
Panicked task 0xffffff8688fef7d8: 11 threads: pid 441: WindowServer
Backtrace (CPU 0), panicked thread: 0xffffff868b175690, Frame : Return Address
0xffffffe051672f00 : 0xffffff80104a94ed mach_kernel : _handle_debugger_trap + 0x41d
0xffffffe051672f50 : 0xffffff80105ffd55 mach_kernel : _kdp_i386_trap + 0x145
0xffffffe051672f90 : 0xffffff80105ef723 mach_kernel : _kernel_trap + 0x533
0xffffffe051672fe0 : 0xffffff8010448a60 mach_kernel : _return_from_trap + 0xe0
0xffffffe051673000 : 0xffffff80104a98bd mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffe051673120 : 0xffffff80104a9076 mach_kernel : _panic_trap_to_debugger + 0x2b6
0xffffffe051673180 : 0xffffff8010d1c679 mach_kernel : _panic + 0x54
0xffffffe0516731f0 : 0xffffff7fa8905e4d com.apple.driver.AppleParavirtGPU : __ZNK27AppleParavirtVirtualChannel8hasFaultEv + 0xdd9
0xffffffe051673210 : 0xffffff7fa88ff92b com.apple.driver.AppleParavirtGPU : __ZN24AppleParavirtDisplayPipe17submitTransactionEP30IOAccelDisplayPipeTransaction2 + 0x2cb
0xffffffe0516736b0 : 0xffffff7fa8c3cc21 com.apple.iokit.IOAcceleratorFamily2 : __ZN18IOAccelDisplayPipe23transaction_queue_gatedEP30IOAccelDisplayPipeTransaction2 + 0x3b
0xffffffe0516736d0 : 0xffffff8010c64140 mach_kernel : __ZN13IOCommandGate9runActionEPFiP8OSObjectPvS2_S2_S2_ES2_S2_S2_S2_ + 0xb0
0xffffffe051673730 : 0xffffff7fa8c3a403 com.apple.iokit.IOAcceleratorFamily2 : __ZN18IOAccelDisplayPipe17wsaaWillExitDeferEi + 0x11d
0xffffffe0516737a0 : 0xffffff7fa8bfdb53 com.apple.iokit.IOAcceleratorFamily2 : __ZN21IOAccelDisplayMachine20wsaa_will_exit_deferEji + 0x81
0xffffffe0516737e0 : 0xffffff7fa8c3933e com.apple.iokit.IOAcceleratorFamily2 : __ZN18IOAccelDisplayPipe22display_change_handlerEPvP13IOFramebufferiS0_ + 0x2ba
0xffffffe051673820 : 0xffffff7fa8d9bc42 com.apple.iokit.IOGraphicsFamily : __ZN13IOFramebuffer24deliverGroupNotificationEijbiPv + 0x356
0xffffffe051673960 : 0xffffff7fa8d8625d com.apple.iokit.IOGraphicsFamily : __ZN13IOFramebuffer30deliverFramebufferNotificationEiPv + 0x193
0xffffffe0516739f0 : 0xffffff7fa8d98db8 com.apple.iokit.IOGraphicsFamily : __ZN13IOFramebuffer16setWSAAAttributeEjj + 0x1f8
0xffffffe051673a90 : 0xffffff7fa8d99aff com.apple.iokit.IOGraphicsFamily : __ZN13IOFramebuffer15extSetAttributeEP8OSObjectPvP25IOExternalMethodArguments + 0x153
0xffffffe051673ad0 : 0xffffff8010c9350e mach_kernel : __ZN12IOUserClient14externalMethodEjP25IOExternalMethodArgumentsP24IOExternalMethodDispatchP8OSObjectPv + 0x1de
0xffffffe051673b20 : 0xffffff7fa8da00ee com.apple.iokit.IOGraphicsFamily : __ZN23IOFramebufferUserClient14externalMethodEjP25IOExternalMethodArgumentsP24IOExternalMethodDispatchP8OSObjectPv + 0x82
0xffffffe051673b70 : 0xffffff8010c9d93b mach_kernel : _is_io_connect_method + 0x3db
0xffffffe051673cd0 : 0xffffff80105a99f4 mach_kernel : _iokit_server_routine + 0x4e84
0xffffffe051673de0 : 0xffffff8010484149 mach_kernel : _ipc_kmsg_send + 0x439
0xffffffe051673e70 : 0xffffff801049b15b mach_kernel : _mach_msg_overwrite_trap + 0x2db
0xffffffe051673ef0 : 0xffffff80105d4c6c mach_kernel : _mach_call_munger64 + 0x24c
0xffffffe051673fa0 : 0xffffff8010449246 mach_kernel : _hndl_mach_scall64 + 0x16
      Kernel Extensions in backtrace:
         com.apple.iokit.IOGraphicsFamily(589.0)[9A88AD9A-6547-33D4-BBBD-1C40B788E7D1]@0xffffff7fa8d7b000->0xffffff7fa8da9fff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[42B10E6F-C0FE-3F93-A427-B065BCB4E07A]@0xffffff8012f85000->0xffffff8012faefff
         com.apple.iokit.IOAcceleratorFamily2(462.0)[2733B51B-3D16-3705-AC3D-9A15E8D8AB2C]@0xffffff7fa8bef000->0xffffff7fa8c58fff
            dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[DFBB3251-6FEF-39D4-B164-8EC5F0DA2353]@0xffffff8011b32000->0xffffff8011b53fff
            dependency: com.apple.iokit.IOGraphicsFamily(589)[9A88AD9A-6547-33D4-BBBD-1C40B788E7D1]@0xffffff7fa8d7b000->0xffffff7fa8da9fff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[42B10E6F-C0FE-3F93-A427-B065BCB4E07A]@0xffffff8012f85000->0xffffff8012faefff
            dependency: com.apple.iokit.IOReportFamily(47)[CE4DA638-ECDF-3B24-AF3B-A2F3B6D176CD]@0xffffff8012fc0000->0xffffff8012fc2fff
            dependency: com.apple.iokit.IOSurface(302.7)[CBB74EFC-81CC-398B-92C7-2E7EC3EC40C4]@0xffffff80130f4000->0xffffff8013110fff
         com.apple.driver.AppleParavirtGPU(1.0)[61BADD19-AFFB-3AEF-8963-75CC7DFB196A]@0xffffff7fa88f4000->0xffffff7fa8909fff
            dependency: com.apple.AppleGraphicsDeviceControl(6.4.6)[8149087A-01E5-3CB2-AC04-7977C67080C9]@0xffffff7fa74c7000->0xffffff7fa74cafff
            dependency: com.apple.iokit.IOAcceleratorFamily2(462)[2733B51B-3D16-3705-AC3D-9A15E8D8AB2C]@0xffffff7fa8bef000->0xffffff7fa8c58fff
            dependency: com.apple.iokit.IOGraphicsFamily(589)[9A88AD9A-6547-33D4-BBBD-1C40B788E7D1]@0xffffff7fa8d7b000->0xffffff7fa8da9fff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[42B10E6F-C0FE-3F93-A427-B065BCB4E07A]@0xffffff8012f85000->0xffffff8012faefff
            dependency: com.apple.iokit.IOSurface(302.7)[CBB74EFC-81CC-398B-92C7-2E7EC3EC40C4]@0xffffff80130f4000->0xffffff8013110fff

Process name corresponding to current thread (0xffffff868b175690): WindowServer
Boot args: keepsyms=1 -serial=0x2

Mac OS version:
21A5268h

Kernel version:
Darwin Kernel Version 21.0.0: Sun Jun 20 18:43:49 PDT 2021; root:xnu-8011.0.0.121.4~2/RELEASE_X86_64
Kernel UUID: 024FF9EB-1119-3151-B84A-5C863000168D
KernelCache slide: 0x0000000010200000
KernelCache base:  0xffffff8010400000
Kernel slide:      0x0000000010210000
Kernel text base:  0xffffff8010410000
__HIB  text base: 0xffffff8010300000
System model name: Parallels16,1 (Parallels Virtual Platform)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 51843138916
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x0000000c1217883b
  Sleep   : 0x0000000000000000 0x0000000000000000 0x0000000000000000
  Wake    : 0x0000000000000000 0x00000001bc5610e7 0x0000000000000000
last started kext at 46829063815: >AudioAUUC    1.70 (addr 0xffffff7fa8a4a000, size 12288)
loaded kexts:
>AudioAUUC    1.70
@filesystems.smbfs    3.5
@filesystems.autofs    3.0
@fileutil    20.036.15
>!AUpstreamUserClient    3.6.8
>!AMCCSControl    1.14
>!AGraphicsDevicePolicy    6.4.6
@AGDCPluginDisplayMetrics    6.4.6
>pmtelemetry    1
|IOUserEthernet    1.0.1
>usb.!UUserHCI    1
>!AHDAHardwareConfigDriver    283.15
>!AHDA    283.15
>!AHV    1
>!ADiskImages2    116
>!A!ISlowAdaptiveClocking    4.0.0
>ACPI_SMC_PlatformPlugin    1.0.0
>!AParavirtGPU    1
>!AFIVRDriver    4.1.0
>!APVPanic    1
|SCSITaskUserClient    450
>!AFileSystemDriver    3.0.1
@filesystems.tmpfs    1
@filesystems.lifs    1
@filesystems.hfs.kext    578
@BootCache    40
@!AFSCompression.!AFSCompressionTypeZlib    1.0.0
@!AFSCompression.!AFSCompressionTypeDataless    1.0.0d1
@filesystems.apfs    1933.0.26
>!AAHCIPort    348
>!A!I8254XEthernet    3.1.5
@private.KextAudit    1.0
>!AACPIButtons    6.1
>!AHPET    1.8
>!ARTC    2.0.1
>!ASMBIOS    2.1
>!AAPIC    1.7
@!ASystemPolicy    2.0.0
@nke.applicationfirewall    402
|IOKitRegistryCompatibility    1
|EndpointSecurity    1
@Dont_Steal_Mac_OS_X    7.0.0
@kec.!AEncryptedArchive    1
@kext.triggers    1.0
>!AHIDKeyboard    224
>!ASMBus!C    1.0.18d1
|IOSMBus!F    1.1
>!AGraphicsControl    6.4.6
|IO!BSerialManager    9.0.0
|IO!BPacketLogger    9.0.0
|IO!BHost!CUSBTransport    9.0.0
|IO!BHost!CUARTTransport    9.0.0
|IO!BHost!CTransport    9.0.0
>DspFuncLib    283.15
@kext.OSvKernDSPLib    529
>IO!BHost!CPCIeTransport    9.0.0
|IOAVB!F    1000.6
@plugin.IOgPTPPlugin    1000.9
|IOEthernetAVB!C    1.1.0
|CSR!BHost!CUSBTransport    9.0.0
|Broadcom!BHost!CUSBTransport    9.0.0
|Broadcom!B20703USBTransport    9.0.0
>!AIPAppender    1.0
|IOSkywalk!F    1.0
>mDNSOffloadUserClient    1.0.1b8
@!AGPUWrangler    6.4.6
|IONDRVSupport    589
|IOSlowAdaptiveClocking!F    1.0.0
>!ASMBusPCI    1.0.14d1
>IOPlatformPluginLegacy    1.0.0
>IOPlatformPlugin!F    6.0.0d8
|IOAccelerator!F2    462
@!AGraphicsDeviceControl    6.4.6
>!AHDA!C    283.15
|IOHDA!F    283.15
|IOGraphics!F    589
|IOAudio!F    300.9
@vecLib.kext    1.2.0
>usb.IOUSBHostHIDDevice    1.2
>usb.cdc    5.0.0
>usb.networking    5.0.0
>usb.!UHostCompositeDevice    1.2
|IOSCSIMultimediaCommandsDevice    450
|IOBD!S!F    1.8
|IODVD!S!F    1.8
|IOCD!S!F    1.8
>!ABSDKextStarter    3
|IOSurface    302.7
@filesystems.hfs.encodings.kext    1
>!AXsanScheme    3
|IOAHCISerialATAPI    268
|IOAHCIBlock!S    333
>usb.!UXHCIPCI    1.2
>usb.!UXHCI    1.2
>usb.!UEHCIPCI    1.2
>!AVirtIO    132
|IOSerial!F    11
|IOAHCI!F    295
>usb.!UUHCIPCI    1.2
>usb.!UUHCI    1.2
>usb.!UEHCI    1.2
>usb.!UHostPacketFilter    1.0
|IOUSB!F    900.4.2
>!AEFINVRAM    2.1
>!AEFIRuntime    2.1
|IOHID!F    2.0.0
$!AImage4    3.0.0
|IOTimeSync!F    1000.9
|IONetworking!F    3.4
>DiskImages    493.0.0
|IO!B!F    9.0.0
|IOReport!F    47
$quarantine    4
$sandbox    300.0
@kext.!AMatch    1.0.0d1
|CoreAnalytics!F    1
>!ASSE    1.0
>!AKeyStore    2
>!UTDM    531
|IOUSBMass!SDriver    206
|IOSCSIBlockCommandsDevice    450
|IO!S!F    2.1
|IOSCSIArchitectureModel!F    450
>!AMobileFileIntegrity    1.0.5
@kext.CoreTrust    1
>!AFDEKeyStore    28.30
>!AEffaceable!S    1.0
>!ACredentialManager    1.0
>KernelRelayHost    1
|IOUSBHost!F    1.2
>!UHostMergeProperties    1.2
>usb.!UCommon    1.0
>!ABusPower!C    1.0
>!ASEPManager    1.0.1
>IOSlaveProcessor    1
>!AACPIPlatform    6.1
>!ASMC    3.1.9
|IOPCI!F    2.9
|IOACPI!F    1.4
>watchdog    1
@kec.pthread    1
@kec.Libm    1
@kec.corecrypto    11.1

** In Memory Panic Stackshot Succeeded ** Bytes Traced 136446 (Uncompressed 322192) **
Writing local cores...

Beginning dump of kernel stackshot
100..
100..Recorded panic stackshot in corefile at offset 0xa000, compressed to 158958 bytes

Beginning coredump of kernel
12..
28..
41..
63..
73..
94..
100..Done
Coredump complete of kernel, dumped 790 segments (739569664 bytes), 1 threads (184 bytes) overall uncompressed file length 739627048 bytes. Compressed file length is 170393008 bytes

EDIT to add code. Windowserver, huh. I've had both Big Sur 11.3+ and now Monterey VM's crash often during install/upgrade/boot, but never 11.2.3 or earlier builds.
 
Last edited:

PeterHolbrook

macrumors 68000
Sep 23, 2009
1,625
441
Look familiar? Clone of my Big Sur 11.4 VM, running on my 5,1 11.2.3 host, upgraded to the Monterey public beta. Came back to this. Could be Parallels not ready for Monterey, but perhaps could be related to our issue? I'm having too much deja-vu...
I mentioned something similar, weeks ago, related to difficulties I encountered in updating a virtual 11.2.3 to 11.3 (Parallels Desktop on a Mac Pro 5,1), but the consensus opinion was that the virtual hardware of Parallels had no bearing on the issues we're experiencing on our cMPs when trying to boot the latest releases of Big Sur and, now, with Monterey betas.
 
  • Like
Reactions: Chung123 and JohnD

Trefor Parr

macrumors newbie
Jul 13, 2020
7
0
Is there any way of sending diagnostic reports to Apple I reported one of my Mac Mini recently, I have been experiencing data corruption 14.4 Mac mini 2014 I sent report to apple say problem old Intel CPUs
 

tsialex

Contributor
Jun 13, 2016
13,455
13,601
Is there any way of sending diagnostic reports to Apple I reported one of my Mac Mini recently, I have been experiencing data corruption 14.4 Mac mini 2014 I sent report to apple say problem old Intel CPUs
2014 Mac mini is a fully supported Mac, with Monterey support, open a RADAR.

Edited to correct the answer, since it's about a 2014 mini and not about an unsupported Mac Pro.
 
Last edited:
  • Like
Reactions: Enricote

Trefor Parr

macrumors newbie
Jul 13, 2020
7
0
I think Apple is done this to stop people from updating their old Mac. old Mac Pro not supported in the CPU format found a way of doing it in some type of code has anybody still used netbook at all I was think about before old Mac Mac pond of View try it
 

trifero

macrumors 68030
May 21, 2009
2,958
2,800
Reports are just ignored. 2014 Mac mini is a fully supported Mac, with Monterey support, while the software support for the mid-2012 Mac Pro ended back in 2019 and even the extended repair program ended back in December 2020.
Reports are just ignored?
 

eVasilis

macrumors 6502
Jan 13, 2010
425
182
Has anyone checked the installation log after a failed / hang installation of 11.3 / 11.4?
 

hwojtek

macrumors 68020
Jan 26, 2008
2,274
1,277
Poznan, Poland
I think Apple is done this to stop people from updating their old Mac. old Mac Pro not supported in the CPU format found a way of doing it in some type of code has anybody still used netbook at all I was think about before old Mac Mac pond of View try it
Some punctuation and actual sense would be helpful to convey your message to the masses.
 

tsialex

Contributor
Jun 13, 2016
13,455
13,601
I thought Mac Mini 2014 was discontinued, but not obsolete.
Posting here, the missing punctuation and the reference to old CPU made me think that he wanted to post about a MacPro, not a MacMini, since the 2014 model continue to be fully software supported and will get Monterey. I've edited my post.
 

PeterHolbrook

macrumors 68000
Sep 23, 2009
1,625
441
A report of a presumably pyrrhic success of 11.4 booting on a Mac Pro 5,1

As I've said several times, I've been trying unsuccessfully to boot 11.3 and 11.4 for months now. Today, after updating OC to version 0.7.1, I've tried booting 11.4 four times in a row. The first one was a failed attempt, like two dozen or so before today. The second one showed a progress bar that went a little farther than the previous attempt, but also failed miserably. On the third attempt, much to my surprise, I noticed an access to my Blu-ray burner, which is connected to my Titan-Ridge Thunderbolt card, but, a couple of minutes after that, the Mac rebooted. Selecting OC once again, and my 11.4 boot HDD, this time the boot was entirely successful.

I'm now back in my 11.2.3 regular Big Sur. I'm not particularly optimistic that a new attempt to boot 11.4 will be equally successful (getting to the desktop in less than 5 minutes!), but, who knows?

Has anyone else noticed a betterment of the situation because of OC 0.7.1?
 

JackLeBoul

macrumors member
Mar 5, 2010
48
180
Zurich - Switzerland
A report of a presumably pyrrhic success of 11.4 booting on a Mac Pro 5,1

As I've said several times, I've been trying unsuccessfully to boot 11.3 and 11.4 for months now. Today, after updating OC to version 0.7.1, I've tried booting 11.4 four times in a row. The first one was a failed attempt, like two dozen or so before today. The second one showed a progress bar that went a little farther than the previous attempt, but also failed miserably. On the third attempt, much to my surprise, I noticed an access to my Blu-ray burner, which is connected to my Titan-Ridge Thunderbolt card, but, a couple of minutes after that, the Mac rebooted. Selecting OC once again, and my 11.4 boot HDD, this time the boot was entirely successful.

I'm now back in my 11.2.3 regular Big Sur. I'm not particularly optimistic that a new attempt to boot 11.4 will be equally successful (getting to the desktop in less than 5 minutes!), but, who knows?

Has anyone else noticed a betterment of the situation because of OC 0.7.1?
No, I am having the same issues. Hit and miss really.
Makes no difference when I remove all connected peripherals or not.

Very surprising however, my two macMini (mid 2012) and two MacBook Pro (mid 2012) updates and runs perfectly.
(in fact, they run faster than the original OS (Lion) :cool:
Both run OC 0.7.1 and BS 11.4 and of course not supposed to be compatible. This is really a MP 5,1 issue.
 
Last edited:

Cecco

macrumors regular
Jun 11, 2008
110
9
This sucks. :( But at least 11.2.3 should be usable for a few years yet...
Sorry to add non-technical noise to this thread but this statement cannot be left uncommented.

IMO running a production machine on 11.2.3 especially if it is connected to the internet is not a good idea. Apple already patched dozens of security holes with later updates that we cannot apply due to the boot issue in 11.3 and later.

The only safe way to use a 4.1/5.1 cMP currently is to bite the bullet and downgrade to Catalina with the downside of loosing some Big Sur only features and compatibility with newer apps. But then it will be useable as long as Apple releases security updates for Catalina.
 

trifero

macrumors 68030
May 21, 2009
2,958
2,800
Sorry to add non-technical noise to this thread but this statement cannot be left uncommented.

IMO running a production machine on 11.2.3 especially if it is connected to the internet is not a good idea. Apple already patched dozens of security holes with later updates that we cannot apply due to the boot issue in 11.3 and later.

The only safe way to use a 4.1/5.1 cMP currently is to bite the bullet and downgrade to Catalina with the downside of loosing some Big Sur only features and compatibility with newer apps. But then it will be useable as long as Apple releases security updates for Catalina.
November 2022
 

LordeOurMother

macrumors 6502
Jul 10, 2014
397
122
Sorry to add non-technical noise to this thread but this statement cannot be left uncommented.

IMO running a production machine on 11.2.3 especially if it is connected to the internet is not a good idea. Apple already patched dozens of security holes with later updates that we cannot apply due to the boot issue in 11.3 and later.

The only safe way to use a 4.1/5.1 cMP currently is to bite the bullet and downgrade to Catalina with the downside of loosing some Big Sur only features and compatibility with newer apps. But then it will be useable as long as Apple releases security updates for Catalina.
Oh yeah, if it’s a professional machine, then it’s a terrible idea. I agree.
 
  • Like
Reactions: paalb

Trefor Parr

macrumors newbie
Jul 13, 2020
7
0
Hyper-Threading Technology: on Mac Pro 5.1 could this be causing the problem with the race condition
 
Status
Not open for further replies.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.