Jump to content

TheBloke

Donators
  • Content Count

    226
  • Joined

  • Last visited

About TheBloke

  • Rank
    InsanelyMac Geek

Profile Information

  • Gender
    Male
  • Location
    Brighton, UK

Recent Profile Visitors

1,222 profile views
  1. TheBloke

    Vega Frontier Edition on High Sierra

    So which SMBIOS were you using when you got the freezes? iMacPro 1,1? I've had no problems with that SMBIOS on either my H77 or X58, and I've seen posts from quite a few other people using it on various HW, but I suppose this could well vary with the exact HW in use. When these freezes occur, are you SSHing and confirming they're exactly the same as before, eg a flood of IOAccelerator messages starting with IOAccelFenceMachine::fence_timeout? Just wondering if it could be some other issue, related to switching to OpenCore. I've actually put my H77 back onto Clover for now, because I have a couple of issues that I can't currently be bothered to fix. USB ports issues for one, which are a common problem and I believe are easy to fix, but also a problem with the Realtek gigabit NIC, which keeps disconnecting randomly and throws up PCI errors in Console logs, which I assume is related to missing DSDT/SSDT stuff. I will likely try to fix those at some point, but for now I've reverted the H77 to Clover. The X58 I haven't even attempted to put on OpenCore yet, because I know it requires a lot of DSDT patches else it will mess up the BIOS, and I don't yet know how to make those in OC (I'm pretty sure I can't just use the same DSDT.aml from Clover in OpenCore). Anyway my point is that if you haven't already, I'd advise to confirm that the issue is definitely identical, from checking the Console logs, and also confirm it occurs also in Clover - you can simply remove /System/Library/Extensions/AppleGFXHDA.kext (move it to some other folder) then run Kext Utility, to achieve the same result of disabling that kext in Clover. Just to rule out the possibility of new OpenCore-specific issues. If all that doesn't help, then yeah maybe try an SMBIOS closer to your HW, then use the boot arg "shikigva=96 shiki-id=Mac-7BA5B2D9E42DDD94" to enable HW H264 encode/decode and HEVC decode (on 10.15 you won't get HEVC decode.) Another thing that might be worth mentioning: on my R9 280X GPU I found that remove AppleGFXHDA had no effect on whether I had HDMI/DP sound outputs. I additionally needed to stop injecting AppleALC.kext. Presumably therefore AppleGFXHDA only provides HDMI/DP on certain GPUs, probably newer ones. I would be quite surprised if the VII didn't use GFXHDA, given it's even newer than the Vega 64, but I mention this just in case. In other words, if you definitely don't have AppleGFXHDA loaded, but you do still have HDMI/DP sound outputs visible in Sound Preferences/Audio MIDI Setup, then try removing AppleALC.kext as well, then re-test. Good luck!
  2. TheBloke

    Vega Frontier Edition on High Sierra

    You're very welcome - hope it solves the problem for you as well. Seems there's some hope it might. Today I put the Vega in my X58 legacy hack, and as this machine is still on Clover I disabled AppleGFXHDA by simply moving it out of /System/Library/Extensions, then ran Kext Utility. So far, so good with regards to stability to HW encoding. I've done various Premiere Pro and Resolve tests, including leaving Premiere encoding for over an hour. No errors, no freezes. EDIT: It's now past midnight, the card has been in for at least 12 hours, and still going strong. I've been doing a bunch of H264 accelerated screen recording using OBS, and no problems at all. I'm confident in calling this problem resolved for me. I do still have the bevy of problems that seems to inevitably come with using a modern GPU on a legacy system, and which are noticeably worse with the Vega than they were with the R9 280X I was using before. Even with the R9 280X I got no picture on any monitor from boot and had to SSH to issue a sleep command, then wake it up to get all monitors working. With the Vega, I additionally have to unplug all but one monitor when booting, otherwise the system will fail to sleep, and will eventually crash and have to be restarted. With only one monitor connected I can sleep & wake the system and then all monitors work. Or rather, they all work except for the 4K DP, which has further problems. macOS always detects it OK, but the monitor itself usually reports no signal. I have to unplug and replug it, sometimes three or four times, before the picture appears. Once it does appear it's then fine, unless display sleep kicks in, so I've had to disable that. I leave this system on 24/7, so reboots are rare, so all of that is not too much of a problem. I do turn all my monitors off at the mains when I go to bed, so I expect to find that each morning I will have to do the unplug/replug a few times to get a picture back on the 4K. So that's all quite a bit of hassle, but worth it to have a fully working system with decent GPU and HW acceleration. It hopefully won't be an issue for too long, as I'll will finally be getting a new PC sometime in the next month. And at least now I can be pretty sure that I can put the Vega in it and have it work right. I'm likely going to try Resolve for my next video project. I only started making videos a couple of months ago, and started off using Premiere + After Effects. But now I've learnt a bit and researched quite a lot, I see why people are talking a lot about Resolve. I'm definitely going to try it out, although I do remain concerned about how inflexible the UI is. I have 5 monitors and I make use of three of them in my standard Premiere setup, which is just not possible in Resolve - unless of course I buy a special BlackMagic PCIe card that would allow using an entire monitor as a timeline display. I love the flexibility of Adobe UIs, so going to something quite as rigid and limited as Resolve appears to be is my main concern about switching. However the speed and reliability benefits would of course be welcome. Although, I'm not sure reliability is actually there right now with Resolve - at least not in the latest code. I was browsing the Resolve forum last night and read a three page thread of people complaining about all the terrible bugs in the newly released 16.1, calling it a disaster. Which I have to say somewhat matches my early experiences. I keep getting rendering failures on trivially simple projects, like just throwing three H264 files into a timeline and rendering it without any effects, transitions or anything else. This seems to be happen far more when either the source or destination file are on a network drive. It mostly works when all files are on the local SSD, though it's still happened once in that config. There's no explanation for the error, it will be running fine then it suddenly stops with a message that says little more than "Rendering failed". Rerunning the exact same render may work fine, or may fail earlier, or later. I also had a fun issue back when the H77 was still freezing regularly with the Vega; it froze while Resolve was open, so I rebooted, and when I next opened Resolve, I couldn't see its UI. The Load Project window appeared fine, and after selecting a project I would see the main Resolve window flash on for a for a split second, then it would vanish. I could still see and interact with the menu bar, so I tried stuff like Reset UI, and toggling Dual Display on or off, but that did nothing. Eventually I solved it by unplugging all but one monitor and then launching Resolve, which got the UI back. So perhaps I should roll back to 16.0 before I get stuck into Resolve too much, as learning new software while that software isn't working reliably is not a good experience. But even through all that I can see some of the appeal - it's cool to be able to quickly flick back and forth between Cut, Edit, Fusion and Fairlight, and have it all integrated. As for the 7 hour encode - that was purely a test My longest project is about 15 minutes at the moment. After I first tried the GFXHDA disable, I wanted to leave a long encode running overnight to further test stability, so I made a new sequence and added all my existing sequences to it, and then did Select-All+Paste, Select-All+Paste, over and over until it got to 7 hours Actually this process of testing has shown me how slow Premiere is. On my H77, using H264 source clips and encoding with H264 hardware accel, it was rendering at about 70 FPS; which is barely faster than real-time for my 60 FPS footage. Both Resolve and Final Cut Pro, rendering an identical sequence with identical (or as close as possible) encoder settings, rendered at an average of 175 FPS. Coming over to the X58 which is older but has more cores, a higher clock speed and double the RAM of the H77, Resolve was still at 175 FPS (which may well be the limit of the H264 encoder itself), but Premiere improved to ~90 FPS. Still way down on Resolve though.
  3. TheBloke

    Vega Frontier Edition on High Sierra

    Hey @nefilim I have today made a key discovery: this problem affects me much more when I use DisplayPort. I've spent the last days doing a lot more further testing. This led me to replace Clover with OpenCore, to upgrade to Catalina 10.15.1 beta1, beta2 and beta3, to play around with various UEFI options, and a lot more. Nothing helped, until I stumbled upon a forum post from 2018 where someone was having similar problems in High Sierra, but said they only had the issue when using DisplayPort. My H77 system has three monitors connected. Initially, this was two HDMI plus one DisplayPort. The DP monitor also supports HDMI, so I changed the cable and.. boom. Or rather, no boom. Now my Premier Pro and Resolve exports work just fine. When using DP, Premiere Pro would trigger the GPU freezes within 2-3 minutes. I've now done over 90 minutes of Premiere exporting without a single hitch, plus about 30 minutes in Resolve. EDIT: Removed the rest of what I wrote here. In summary, I wrote a bunch of stuff about being confident it was all good now, as long as I only used HDMI, then came back 2 hours later to say "it's frozen again". I am trying a new test, with a config change based on a hunch, and it's currently looking a little promising. Not going to say any more until I've got more confidence, because I don't want it to be another case of "It's working! Oh no it's not." So all I'll say for now is I have two DP + 1 HDMI monitors connected, and I've been encoding to H264, alternating between Premiere Pro and Resolve, plus also with an ffmpeg H264->H265 going on in the background, for the last 1 hour 45 minutes, without freeze or problem. I'll update again as and when I have firm news, good or bad..
  4. TheBloke

    WhatEverGreen Support Topic

    Understood. Thanks very much for clarifying that. I was already planning to start learning and testing OC, but now I have learnt this, I think I will definitely try to move over to OC for the future. Thanks again.
  5. TheBloke

    WhatEverGreen Support Topic

    WEG not supported in Clover? What does that mean exactly?
  6. TheBloke

    Vega Frontier Edition on High Sierra

    Glad to hear things are working better for you, at least with the Vega. When you say it's all working well: are you doing any extended HW encode/decode work, especially anything like HW accelerated Premiere Pro or Davinci Resolve export? Ie stuff that is 5-20+ minutes of continuous HW encode, alongside reasonably high CPU usage, and probably decode and other GPU activity in parallel. That's what kills it for me every time. In other general usage, I think it's pretty solid, although I haven't done a huge amount of general purpose testing on that system with the Vega.
  7. TheBloke

    Acidanthera Voodoo PS2

    I am trying the acidanthera VoodooPS2 on my HP Probook 640 and I have all these same issues: two finger gestures not working, physical buttons don't work. Therefore I have no way to right-click or scroll up/down. Also I can't find a way to click and drag. However, three finger gestures do work OK. I am a bit confused about this, because it seems to me that if three finger gestures work, then so should two finger ones? So maybe it's some sort of configuration issue? But I can find almost no help regarding the acidanthera VoodooPS2 driver - I thought there would be an official forum thread, but I can't find one? I guess I will have to go back to the RehabMan version I was using before, which allowed me to scroll up/down and use physical buttons, but three-finger gestures did not work. Another thing I don't understand is whether there should be a Preferences Pane available for changing settings? In researching VoodooPS2 I keep finding people talking about changing settings in the Preferences Pane. I am not sure if they are talking about the normal Apple Trackpad PrefPane, which of course I have, or something new and specific to VoodooPS2? EDIT: I have gone back to the RehabMan VoodooPS2, and realised that it does detect three finger gestures, it's just that it doesn't automatically map them to trackpad gestures. It sends keyboard commands. For example, three-finger-swipe up/down sends Cmd + Option + Up/Down, and three-finger-swipe left/right sends Option + Left/Right. So I have used BetterTouchTool (which I already used) to map these to the same actions that I would normally get on my Magic Trackpad 2: However I can't get two-finger-swipe left/right to work as browser back/forward. It seems VoodooPS2 does not send keyboard codes for these gestures, but instead maps them to scroll wheel left/right (a pretty useless gesture 95% of the time, IMHO). So I need to investigate to see if this can be changed.
  8. TheBloke

    WhatEverGreen Support Topic

    @DSM2 what SMBIOS are you using to get HW encode/decode? Is it iMac Pro 1.1? Can you tell me if HW h264/h265 encode/decode works perfectly? Do you use it much, eg with software like Premiere Pro, Final Cut Pro, Davinci Resolve or so? I ask because some of us have regular problem with freezing of screen, requiring reboot, when HW encode is used on system with no internal GPU. For me it happens with Radeon Vega 64, but someone else on this forum has issue with both Vega 64 and VII Pro, like you have. So I would be interested to hear how it is for you. PS. That is an amazing PC you have there, very jealous
  9. TheBloke

    Vega Frontier Edition on High Sierra

    I think I'm pretty much done with testing now. No progress. I carried on the 10.14.5 kext restoration until I'd copied over all kexts seemingly related to GPU stuff into 10.14.6. Then I went the full hog, and wiped that SSD and restored the entire 10.14.5 backup. I get the same freezes in 10.14.5 as I do in 10.14.6 and Catalina 10.15.0, so, at least on this system with this GPU, I can say that 10.14.6 has made no difference at all. As far as I can see, the same problems exist for me prior to .6 as well. I can't easily test 10.14.4 even if I wanted to, as I went straight from 10.14.1 to .5, so I'd have to do a fresh install. But anyway, the MacRumours guys say 10.14.5 is the first version that supports AMD encode/decode. I tried a couple more things. Firstly I tried going back to WEG 1.2.8, the version that the MacRumours guys are using with their real Mac Pros to enable HW encode/decode. But that won't work on 10.14.5 because of the purple lines on boot, causing it to never reach the login screen. The first version that fixes that is 1.3.1, and I didn't bother re-testing with that as hardly anything has changed in WEG between 1.3.1 and the current 1.3.3. I also tried reverting my SMBIOS to iMac 14.2, and enabling HW encode/decode with shikigva=96 shiki-id=Mac-7BA5B2D9E42DDD94. This gives H264 encode/decode and H265 decode, but no encode. But it still fails on a Premiere Pro h264 export almost immediately. So I'm out of stuff to test really. I guess all I can do is cross my fingers that when I eventually get a new PC - hopefully in the next month - it will magically not have these issues. Maybe it works better with other SMBIOS or something. I really don't know. I might try posting on Reddit and other forums, just on the offchance anyone has got further. But I take it you've already posted on Tony, @nefilim without any joy?
  10. TheBloke

    Vega Frontier Edition on High Sierra

    Interim update: no luck so far. I mounted a backup I took in June when I was on 10.14.5 I used About This Mac -> System Report -> Extensions to see all the extensions I had loaded, and browsed through the list to see which might be graphic related. Then I copied all these from the backup to a temporary directory. So far I have done two tests. Test 1: I copied AMD*.kext from 10.14.5, which in practice meant I reverted to 10.14.5 on: AMD10000Controller AMDFrameBuffer AMDSupport AMDRadeonX5000 AMDRadeonX5000HWLibs AMDRadeonX5000Services Test 2: After that failed in the usual way, I also reverted to 10.14.5 on: IOAcceleratorFamily2 I had a good feeling about that one, because it's the kext that appears in 95% of the Console error messages I get, eg "(IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt". But no dice there either. Still failed within 5 minutes of starting a Premiere Pro export. There's a couple more kexts I've not yet copied over, like IOGraphicsFamily and AppleGraphicsControl. Tomorrow I'll put those over as well. But of course I'm not hopeful. If this doesn't work, then it could be it's something in another kext, one that's not obviously GPU related. Or something in the kernel itself. Or it could just be that I would have had the issue on 10.14.5 as well - I never actually ran 10.14.5 with a GPU capable of HW accel, so I don't know if it would work, I'm just trying this based on hearing from others that things were better in .5. And certainly I know some things are definitely worse on .6, like on my X58 legacy hack where I am getting a lot more weird issues since I upgraded to .6, including periods of time where I have to reboot five or six times in a row due to repeated screen freezes, with the same sort of errors we are seeing with the Vega. Even though the X58 is using a 7970Ghz / R9 280X which has no HW encode/decode available. Very frustrating.
  11. TheBloke

    Vega Frontier Edition on High Sierra

    I finally got my H77 onto Catalina and, unsurprisingly, I've eventually hit the issues while encoding in Premiere Pro. At first things looked a little more hopeful. I re-ran my stress test, of running Heaven full screen at 1920x1080 while recording it with macOS built-in screen recorder using h264 accelerated encoding, while also using ffmpeg to encode h264 -> h265, and watching a 4K h265 movie in VLC. That ran for 75 minutes without problems, longer than it ever has before, and I ended it myself. Then I left ffmpeg encoding h265->h264 in a loop for 2+ hours while I was out. But then as soon as I tried a Premiere Pro export, it went down within 10 minutes. Usual set of errors in Console (as seen through SSH). I'm thinking I'll try restoring the AMD kexts from a 10.14.5 backup and putting them into a 10.14.6 install. Might fail immediately due to changes elsewhere, but you never know. As for why it doesn't work for us. Wish I knew. One possibility is that the people who aren't having problems aren't making heavy use of HW accelerated encode/decode? Maybe if all you do is watch the occasional video, it's fine. Certainly when I ran ffmpeg in a loop for 3+ hours today it was OK. The problems come when I do stuff like screen recording and, in particular, Premiere Pro export. If not that then I don't know. I suppose it could be something subtle, like related to the number of monitors connected, what resolution they are at, etc. My H77 has three screens connected right now, though I've also had the problem occur when two were connected. Don't think I've ever tested with only one connected, but a lot of people do only use one monitor. Actually speaking of that, I noticed an error I'd not seen before when I woke the H77 from display sleep this evening, an HDCP error: 2019-10-12 20:47:24.180002+0100 localhost kernel[0]: (AMDRadeonX5000HWLibs) [3:0:0] AMD Error: 2019-10-12 20:47:24.180009+0100 localhost kernel[0]: (AMDRadeonX5000HWLibs) Failed HDCP: status 4 It repeated a couple of times while the monitor was waking up, then went away. The monitor got a picture just fine, and I would never have even known there was the error if I hadn't had the logs streaming via SSH. It might be completely unrelated. I mention it just as another example of some small detail that could be different between people who have and don't have problems. I might try the 10.14.5 kext test later and will report back on that.
  12. TheBloke

    Vega Frontier Edition on High Sierra

    Thanks for the update. I tested Catalina b6 and had the same issue, but there were 5 further betas before it released this week, so finger's crossed they fixed something in those. I've been meaning to try Catalina on a spare drive but haven't had time - hopefully tomorrow. Once I get a chance to upgrade I'll do my concentrated stress test again, where I run Uniengine Heaven at full screen, simultaneously screen recording it with h264 HW encoding, while also on another monitor playing a 4K h265 video with HW decoding.
  13. TheBloke

    WhatEverGreen Support Topic

    Sorry to hear that, @bobpedro Pretty sure it's related to UEFI though. The real iMacPro 1.1 has no iGPU, which is why it's the recommended option when one wants to enable HW accelerated encode/decode, because that's the only real Mac that officially supports h264/h265 encode/decode without also having an iGPU. My Vega 64 now mostly works great in my H77 (which has no iGPU as far as macOS can see) now that I have CSM disabled, with all the usual black-screen-from-boot, flickering, needing to sleep/wake etc completely gone. The one issue that remains is that eventually the GPU hang when using HW h264/h265 encode, eg exporting a Premiere Pro project. But that appears to be specific to the Vega 64 itself (at least in a Hack), as I've recently spoken to another user who has a Vega 64 in a much more modern system than mine, and they are getting those freezes too. They told me that the issue used to exist a while ago (months), then went away for a month or two, then came back, which makes him think that 10.14.6 has re-introduced a problem that 10.14.5 resolved. I've also tested the latest Catalina beta, and sadly the same problem occurs. I'm annoyed that I only upgraded all my macOS installations to .6 a couple of weeks ago. I tested .5 and .6 side by side and could spot no difference, so I did the upgrade. But that was before I knew to disable CSM, so I was still messing about with unplugging monitors and the like, and hadn't properly tested HW encode/decode at that time. I wish I still had a 10.14.5 install I could easily use. When I have some time I might re-install a spare SSD with 10.14.5 to confirm if that resolves the issue. If any of the WEG experts have any idea why 10.14.6 might have re-introduced GPU freezes/crashes with HW h264/h265 encode, and whether WEG could do anything about it, I would be most grateful for any info. Console error messages are shown in this post of mine.
  14. TheBloke

    Vega Frontier Edition on High Sierra

    I recently bought a Gigabyte Vega 64 and I am plagued with an issue which I suspect is the same as yours. In my H77 UEFI system, I can get the GPU running almost fine. I use the iMacPro 1.1 SMBIOS to enable HW accelerated h264 and h265 encode/decode. I get a picture on all monitors from boot. Benchmarks are OK. Everything is fine.. except, a persistent issue with HW accelerated encode. Maybe decode too, I am not sure. At some random point when I am encoding video in Premiere Pro, or using an HW accelerated screen recording app like Screenflick, all displays will freeze. The system is still running, and I can SSH in. Checking the logs via SSH shows lots of errors like the following: kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) AMDRadeonAccelerator: IOAccelDisplayPipeTransaction time out after 300ms. framebufferIndex=5 kernel[0]: (IOAcceleratorFamily2) framebufferIndex=5, wsaa=17 kernel[0]: (IOAcceleratorFamily2) eventInterruptEnabled=0, transactionInterruptEnabled=1, vblInterruptEnabled=0 kernel[0]: (IOAcceleratorFamily2) powerOff=0, pipeTerminated=0, acceleratorEnabled=1, fWSAA=17 kernel[0]: (IOAcceleratorFamily2) lastIOGraphicsMessageEvent=93, fbIndex=5 kernel[0]: (IOAcceleratorFamily2) transactionQueueReadCount=12055, transactionQueueWriteCount=12056 kernel[0]: (IOAcceleratorFamily2) lastCompletedTransaction: ID=12054 dirtyBits=0x1 options=0x1 kernel[0]: (IOAcceleratorFamily2) pendingTransaction ID=12055, isTransactionComplete()=0, dirtyBits=0x1, options=0x1, errorCode=0x0, submittedReturn=0xe0014042 kernel[0]: (IOAcceleratorFamily2) readTransaction ID=12056, dirtyBits=0x1, options=0x1, errorCode=0x0, submittedReturn=0xe0014042, event hasn't finished kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) virtual IOReturn IOAccelEventMachine2::waitForStamp(int32_t, stamp_t, stamp_t *): initial wait for 1 second expired. Continue wait for 4 seconds. stamp 15313 (gpu_stamp=15312) kernel[0]: (IOAcceleratorFamily2) virtual IOReturn IOAccelEventMachine2::waitForStamp(int32_t, stamp_t, stamp_t *): initial wait for 1 second expired. Continue wait for 4 seconds. stamp 9557 (gpu_stamp=9556) kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) virtual IOReturn IOAccelEventMachine2::waitForStamp(int32_t, stamp_t, stamp_t *): timeout waiting for AMDRadeonAccelerator stamp 15313 (gpu_stamp=15312) kernel[0]: (IOAcceleratorFamily2) virtual IOReturn IOAccelEventMachine2::waitForStamp(int32_t, stamp_t, stamp_t *): timeout waiting for AMDRadeonAccelerator stamp 9557 (gpu_stamp=9556) kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) virtual void IOAccelEventMachineFast2::checkGPUProgress() - Signaling hardware error on channel 0.. kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartEnqueued stampIdx=0 type=2 kernel[0]: (IOAcceleratorFamily2) virtual void IOAccelEventMachineFast2::checkGPUProgress() - Signaling hardware error on channel 2.. kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartSignaled stampIdx=2 type=2 prevType=0 numStamps=22 kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartEnqueued stampIdx=2 type=2 kernel[0]: (IOAcceleratorFamily2) virtual void IOAccelEventMachineFast2::checkGPUProgress() - Signaling hardware error on channel 5.. kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartSignaled stampIdx=5 type=2 prevType=0 numStamps=22 kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartEnqueued stampIdx=5 type=2 kernel[0]: (IOAcceleratorFamily2) virtual void IOAccelEventMachineFast2::checkGPUProgress() - Signaling hardware error on channel 6.. kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartSignaled stampIdx=6 type=2 prevType=0 numStamps=22 kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartEnqueued stampIdx=6 type=2 kernel[0]: (IOAcceleratorFamily2) virtual void IOAccelEventMachineFast2::checkGPUProgress() - Signaling hardware error on channel 12.. kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartSignaled stampIdx=12 type=2 prevType=0 numStamps=22 kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartEnqueued stampIdx=12 type=2 kernel[0]: (IOAcceleratorFamily2) virtual void IOAccelEventMachineFast2::checkGPUProgress() - Signaling hardware error on channel 17.. kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartSignaled stampIdx=17 type=2 prevType=0 numStamps=22 kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartEnqueued stampIdx=17 type=2 kernel[0]: (IOAcceleratorFamily2) virtual void IOAccelEventMachineFast2::checkGPUProgress() - Signaling hardware error on channel 18.. kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartSignaled stampIdx=18 type=2 prevType=0 numStamps=22 kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartEnqueued stampIdx=18 type=2 kernel[0]: (IOAcceleratorFamily2) virtual void IOAccelEventMachineFast2::checkGPUProgress() - Signaling hardware error on channel 19.. kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartSignaled stampIdx=19 type=2 prevType=0 numStamps=22 kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartEnqueued stampIdx=19 type=2 kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::hardwareErrorEvent(): setting restart type to 2 (channel 0) kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::hardwareErrorEvent(): GPURestartDequeued stampIdx=0 type=2 kernel[0]: (AMDRadeonX5000) [3:0:0]: channel 0 event timeout kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) virtual IOReturn IOAccelEventMachine2::waitForStamp(int32_t, stamp_t, stamp_t *): a graphics error occurred, exitting.. kernel[0]: (IOAcceleratorFamily2) virtual IOReturn IOAccelEventMachine2::waitForStamp(int32_t, stamp_t, stamp_t *): a graphics error occurred, exitting.. kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (AMDRadeonX5000) [3:0:0]: channel 0 GFX is hung! (lastReadTimestamp=0x0001212a) channelResetMask 0x00000000 These errors will repeat seemingly forever until I reboot. The issue happens so regularly that, during testing, I started checking for these logs at all times, by SSHing in and running this command: log stream --predicate 'process == "kernel"' --style syslog | grep -v IOAudio (I remove IOAudio from the output only because it generates a flood of log messages periodically) Next time this happens to you, can you SSH in and run either the above command, or: log show --predicate 'process == "kernel"' --style syslog --source --last boot The latter command lists all messages since the current boot. Unfortunately it seems that Console logs are not kept between boots, so you can only get this info before you reboot. My guess is you'll see the same or very similar messages. I tested this for literally days last week, and I don't have a solution. The one thing I did not test was going back to 10.14.5, and I may do that when I have time again. I did test extensively on 10.14.6, with various combinations of Clover and WEG options. I also tried upgrading a spare SSD to Catalina, and unfortunately experienced the same problem. At one point I was gettin these freezes as soon as 1-5 minutes after I started doing HW encoding stuff. Latterly, I could go for as long as 45 minutes before it would happen. But given enough time it would always happen. I literally just bought the Vega 64 10 days ago, and after much testing I first found that it couldn't be made to work in a nice way on my legacy boot X58 system (requiring disconnecting all monitors but one on boot, then needing to sleep & wake before reconnecting them). Then I found it mostly worked fine in the H77 UEFI system, once I had disabled CSM in the BIOS, except that I can't use HW encoding without freezes, and that was one of the main things I bought it for I'm not yet using Blackmagic Resolve, but I do plan to try it out soon, along with Fusion. Right now I'm using Adobe Premiere Pro and After Effects. It saddens me to hear these issues might have come with 10.14.6, because I was still kind of hoping maybe there was some solution. But if it's a change in 10.14.6 that also persists in Catalina, the outlook looks bleak
  15. TheBloke

    WhatEverGreen Support Topic

    Some updates: I have got my Vega 64 almost fully working in my second Hack, the H77. From boot, I get a picture on all ports, both DP and HDMI, with no need to sleep. The solution? So simple: Set CSM to Disabled in BIOS. So @bobpedro if your UEFI motherboard has the option to set CSM to Disable, try this; you may find it solves your problems. This also confirms my earlier belief that these problems are UEFI related, and tells me that there is very likely no solution for legacy motherboards, or UEFI boards without CSM control. Unfortunately, my Vega 64 is still not fully functional in the H77. Using HW h264 encode will lead to GPU hangs/display freezes. Exact timing is variable, but in certain tests it is 100% repeatable. I was able to export a 10 minute Premiere Pro project, which took about 25 minutes to export (it has lots of After Effects sections) and exported successfully; something I was never able to do before using HW accelerated encode. However I then tried using a screen recording app (Screenflick) to record 1920x1080 at 60 FPS, and the GPU would always hang after 2 - 5 minutes of recording. I've tested in Windows 10 on the same system, and there are no hangs there, so I do not believe there is any hardware issue with the card. I've tested HW h264 encode both using the iMacPro 1.1 SMBIOS, and also using my standard iMac 14.2 SMBIOS with "shikigva=96 shiki-id=Mac-7BA5B2D9E42DDD94" boot arguments, to simulate the iMacPro. The former gives me h264 and h265 encode and decode. The latter gives me h264 encode/decode, but no h265 encode (might have h265 decode, not checked that.) But both methods result in GPU hangs/freezes after some time using the h264 encode, which is a big shame. When the GPU hangs during h264 encode, I get the following series of errors, and all displays freeze. I can still SSH in and run commands, but shutdown -r now does not work; the only solution is a hardware reset or shutdown. kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) AMDRadeonAccelerator: IOAccelDisplayPipeTransaction time out after 300ms. framebufferIndex=5 kernel[0]: (IOAcceleratorFamily2) framebufferIndex=5, wsaa=17 kernel[0]: (IOAcceleratorFamily2) eventInterruptEnabled=0, transactionInterruptEnabled=1, vblInterruptEnabled=0 kernel[0]: (IOAcceleratorFamily2) powerOff=0, pipeTerminated=0, acceleratorEnabled=1, fWSAA=17 kernel[0]: (IOAcceleratorFamily2) lastIOGraphicsMessageEvent=93, fbIndex=5 kernel[0]: (IOAcceleratorFamily2) transactionQueueReadCount=12055, transactionQueueWriteCount=12056 kernel[0]: (IOAcceleratorFamily2) lastCompletedTransaction: ID=12054 dirtyBits=0x1 options=0x1 kernel[0]: (IOAcceleratorFamily2) pendingTransaction ID=12055, isTransactionComplete()=0, dirtyBits=0x1, options=0x1, errorCode=0x0, submittedReturn=0xe0014042 kernel[0]: (IOAcceleratorFamily2) readTransaction ID=12056, dirtyBits=0x1, options=0x1, errorCode=0x0, submittedReturn=0xe0014042, event hasn't finished kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt <last message repeated many times> kernel[0]: (IOAcceleratorFamily2) virtual IOReturn IOAccelEventMachine2::waitForStamp(int32_t, stamp_t, stamp_t *): initial wait for 1 second expired. Continue wait for 4 seconds. stamp 15313 (gpu_stamp=15312) kernel[0]: (IOAcceleratorFamily2) virtual IOReturn IOAccelEventMachine2::waitForStamp(int32_t, stamp_t, stamp_t *): initial wait for 1 second expired. Continue wait for 4 seconds. stamp 9557 (gpu_stamp=9556) kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt <last message repeated many times> kernel[0]: (IOAcceleratorFamily2) virtual IOReturn IOAccelEventMachine2::waitForStamp(int32_t, stamp_t, stamp_t *): timeout waiting for AMDRadeonAccelerator stamp 15313 (gpu_stamp=15312) kernel[0]: (IOAcceleratorFamily2) virtual IOReturn IOAccelEventMachine2::waitForStamp(int32_t, stamp_t, stamp_t *): timeout waiting for AMDRadeonAccelerator stamp 9557 (gpu_stamp=9556) kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt <last message repeated many times> kernel[0]: (IOAcceleratorFamily2) virtual void IOAccelEventMachineFast2::checkGPUProgress() - Signaling hardware error on channel 0.. kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartEnqueued stampIdx=0 type=2 kernel[0]: (IOAcceleratorFamily2) virtual void IOAccelEventMachineFast2::checkGPUProgress() - Signaling hardware error on channel 2.. kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartSignaled stampIdx=2 type=2 prevType=0 numStamps=22 kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartEnqueued stampIdx=2 type=2 kernel[0]: (IOAcceleratorFamily2) virtual void IOAccelEventMachineFast2::checkGPUProgress() - Signaling hardware error on channel 5.. kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartSignaled stampIdx=5 type=2 prevType=0 numStamps=22 kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartEnqueued stampIdx=5 type=2 kernel[0]: (IOAcceleratorFamily2) virtual void IOAccelEventMachineFast2::checkGPUProgress() - Signaling hardware error on channel 6.. kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartSignaled stampIdx=6 type=2 prevType=0 numStamps=22 kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartEnqueued stampIdx=6 type=2 kernel[0]: (IOAcceleratorFamily2) virtual void IOAccelEventMachineFast2::checkGPUProgress() - Signaling hardware error on channel 12.. kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartSignaled stampIdx=12 type=2 prevType=0 numStamps=22 kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartEnqueued stampIdx=12 type=2 kernel[0]: (IOAcceleratorFamily2) virtual void IOAccelEventMachineFast2::checkGPUProgress() - Signaling hardware error on channel 17.. kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartSignaled stampIdx=17 type=2 prevType=0 numStamps=22 kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartEnqueued stampIdx=17 type=2 kernel[0]: (IOAcceleratorFamily2) virtual void IOAccelEventMachineFast2::checkGPUProgress() - Signaling hardware error on channel 18.. kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartSignaled stampIdx=18 type=2 prevType=0 numStamps=22 kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartEnqueued stampIdx=18 type=2 kernel[0]: (IOAcceleratorFamily2) virtual void IOAccelEventMachineFast2::checkGPUProgress() - Signaling hardware error on channel 19.. kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartSignaled stampIdx=19 type=2 prevType=0 numStamps=22 kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartEnqueued stampIdx=19 type=2 kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::hardwareErrorEvent(): setting restart type to 2 (channel 0) kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::hardwareErrorEvent(): GPURestartDequeued stampIdx=0 type=2 kernel[0]: (AMDRadeonX5000) [3:0:0]: channel 0 event timeout kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (IOAcceleratorFamily2) virtual IOReturn IOAccelEventMachine2::waitForStamp(int32_t, stamp_t, stamp_t *): a graphics error occurred, exitting.. kernel[0]: (IOAcceleratorFamily2) virtual IOReturn IOAccelEventMachine2::waitForStamp(int32_t, stamp_t, stamp_t *): a graphics error occurred, exitting.. kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (AMDRadeonX5000) [3:0:0]: channel 0 GFX is hung! (lastReadTimestamp=0x0001212a) channelResetMask 0x00000000 kernel[0]: (AMDRadeonX5000HWLibs) AMD Cail: [3:0:0] GPU HangState 0x00000040, HangFlags 0x00000005: IndividualEngineHang 1, NonEngineBlockHang 0, FenceNotRetired 1, PerEngineReset 1, FullAsicReset 0 kernel[0]: (AMDRadeonX5000HWLibs) [3:0:0] GPU HangState 0x00000040, HangFlags 0x00000005: IndividualEngineHang 1, NonEngineBlockHang 0, FenceNotRetired 1, PerEngineReset 1, FullAsicReset 0 kernel[0]: (IOAcceleratorFamily2) virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished kernel[0]: (IOAcceleratorFamily2) virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished kernel[0]: (IOAcceleratorFamily2) virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished kernel[0]: (IOAcceleratorFamily2) virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished kernel[0]: (IOAcceleratorFamily2) virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished kernel[0]: (IOAcceleratorFamily2) virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished kernel[0]: (IOAcceleratorFamily2) virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished kernel[0]: (IOAcceleratorFamily2) virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished kernel[0]: (IOAcceleratorFamily2) virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt kernel[0]: (AMDRadeonX5000) [3:0:0] ** AMDRadeonX5000_AMDVega10GraphicsAccelerator Device in slot: SLOT--1 ** kernel[0]: (IOAcceleratorFamily2) Trying to restart GPU (Radeon RX Vega 64)... kernel[0]: (AMDSupport) AMD Recovery Display. kernel[0]: (Sandbox) Sandbox: tailspin(1751) deny(1) sysctl-write kern.procname I note that this first error, "AMDRadeonAccelerator: IOAccelDisplayPipeTransaction" is the same error I first posted about here, on my X58 Hack with the R9 280X getting black screens on boot. I assume this is because it's a generic message when the GPU experiences problems, rather than they have related causes (as the issue on the X58 is surely related to no UEFI). But I don't know for sure of course. So all in all, very frustrating. I keep making small amounts of progress, then spending a huge amount of time on testing, only to find that in no scenario can I get a fully working system. One of the reasons I bought the new GPU was to help with h264 encode, but now I am booting my H77 into Windows 10 to do it there instead. Oh well, at least I have learnt a little bit more in the process..
×