[TOOL] [Generate Proper Problem Reporting Files]

[black.dragon74]

Hi black.dragon74,

I am getting this error:

Dumping IOREG.
IOREG dump failed. Retrying
Increased delay x2 for IOREG dump. This will take a while...(33 sec)
/Users/user/Desktop/32611
Stefanos-Mac-Pro
IOREG dump failed. Retrying
Increased delay x2 for IOREG dump. This will take a while...(33 sec)
IOREG dump failed. Retrying
Increased delay x2 for IOREG dump. This will take a while...(33 sec)

that is repeated in an endless loop.
Have you ever seen it?
I have checked the version of IORegistryExplorer and it is 2.1, so it should be good. I have also invoked gen_debug with the -u switch to update it to the latest version, but this has not fixed the issue.
Any help is greatly appreciated.

- Ste

Guess you have a really slow IO speed then. Will release an update with time increased to x3 times. Btw, could you try restarting?

Also, were you doing anything while the script was running? You are not supposed to touch anything until script execution has finished. And, does IORegistryExplorer opens up when you run the script?

 

[nodaris]

Guess you have a really slow IO speed then. Will release an update with time increased to x3 times. Btw, could you try restarting?

Also, were you doing anything while the script was running? You are not supposed to touch anything until script execution has finished. And, does IORegistryExplorer opens up when you run the script?

Hi black.dragon74,

I have restarted and tried again, having on;ly the Terminal open, but same error. I have let it go and did not touch anything, just to be sure, but the script looped several times on the same error before I stopped it.
If you could issue a new patched version that would be great.

Thank you,

- Ste

 

[black.dragon74]

...

Hello you and everyone!

I have a good news, I have finally managed to fix this IOReg issue once and for all. What's changed you'll ask? Well, for the normal user, nothing has changed, script will run normally but talking technically, dumpIOREG function has been rewritten completely and is now dynamic. It will automatically increase the delays if it detects that it is running on a slow system. Here's a sneak peak. Update will be live in a few hours. Bear with me until then.

Regards

 

[black.dragon74]

News! New update is now live! Feedback is most welcome!

 

[RehabMan]

Feature request:
Dump entire kextstat output to a file, eg.
kextstat >kextstat_all_output.txt (or some such).

 

[nodaris]

Hello you and everyone!

I have a good news, I have finally managed to fix this IOReg issue once and for all. What's changed you'll ask? Well, for the normal user, nothing has changed, script will run normally but talking technically, dumpIOREG function has been rewritten completely and is now dynamic. It will automatically increase the delays if it detects that it is running on a slow system. Here's a sneak peak. Update will be live in a few hours. Bear with me until then.

View attachment 315747

Regards

Hi black.dragon74,

thank you for the update script. I have updated it (gen_debug -u now it is version 3.8) and tried again, and indeed it is now dynamic. Unfortunately it is still not working for me, as I have waited until it delayed x10 and still would not dump IOReg.
Any idea what the cause of this error could be?
By the way the first time I have run it gave me this message:

Hey! Before we proceed, I found a new version of the script.
You are running 3.8 and new version is 3.7
Shall I update it now?[y/n]:

so you might want to tweak a bit this check.

Regards,

- Ste

 

[black.dragon74]

so you might want to tweak a bit this check.

Guess it’s due to curl caching the older version. Didn’t happen with me ever.

Unfortunately it is still not working for me, as I have waited until it delayed x10 and still would not dump IOReg.

Can you upload a screen recording of when the script is running. That would help me debug the issue.

 

[black.dragon74]

Feature request:
Dump entire kextstat output to a file, eg.
kextstat >kextstat_all_output.txt (or some such).

Implemented in ver3.9. One question though, do you still need "kextstat|grep -y xxxx" output in kextstat_log.txt as they are now also present in kextstat_all_log.txt.

Regards

 

[black.dragon74]

...

In a new update of gen_debug.sh if the IOREG dump fails for more than 3 times then a generic kind of dump is included in the debug report instead of the script going in an infinite loop.

Generic IOREG dump here referes to the output of "ioreg -f -l" in terminal.

@RehabMan what are your views on it? In my opinion, something is better than nothing, right? Moreover, we can use grep on generic_ioreg.txt to save us from trouble of inspecting it in TextEdit manually.

Feedback is most welcome.
Regards

 

[RehabMan]

Implemented in ver3.9. One question though, do you still need "kextstat|grep -y xxxx" output in kextstat_log.txt as they are now also present in kextstat_all_log.txt.

Regards

They are not really needed, but might be a bit easier to find that information if it is still separate.