Big Sur kernel panic

McGroarty,

Thanks for the insightful information you provided.

According to Mac Support team my MacBook Pro's kernel panics are being cause by USB buses/ cables as this frequent script suggests: "panic(cpu 12 caller 0xffffff801e489d2a): Sleep transition timed out after 180 seconds while entering darkwake on way to sleep. Suspected bundle: com.apple.driver.usb.AppleUSBXHCI."

The bottom line is that after almost 12months of the initial purchase that costed me around £3,700 I would never but never imagined that I would have spent so long hours to resolve an issue that still remains unresolved (not to mention the new or replaced external hard drives and monitor that did not stop the kernel panics).

As you mentioned in your epilogue 'Good Luck', because after all that it is only luck to count on.

I hate to say that but I will think twice of a mac purchase in the future.

Hi guys,

I've got an early 2015 MacBook pro which keeps restarting on daily basis since last November after updating it to Big Sur. I called apple support for a few times and they remotely connected to my MacBook looking at the error logs and doing some trick assuring me that this time should be fin, but no luck so far. I'm really annoyed about this situation. I've attached the error logs which I can't understand myself. Is someone able to tell me what's wrong with this junk ? Thanks in advance.

My late 2015 iMac has similar problem but running Catalina. Does not restart by itself, but nearly always fails to shut down normally, then restarts with the same kernel panic message. Sometimes the restart fails to enable Bluetooth, so the keyboard and mouse need to be plugged in to USB ports to get going again. Another restart usually clears it up. Alex's post confirms that upgrading to Big Sur won't help me. I've also seen posts about kernel panics on brand new Macs. I've tried disconnecting the external drive that serves Time Machine, but eventually I get kernel panics during shutdown. I've tried letting the machine sit idle all day, and get normal shutdown/restart. As soon as I start Internet browsing again, no matter which browser, and using email, after awhile I can count on a kernel panic on shutdown, even after normally quitting mail and browsers.

From this and other posts I conclude that system communications error checking since Catalina is looking for something that even new hardware can't deliver when peripherals are running.

I've gone into an Apple store to browse new Mac Books and told the sales guy I won't buy another Mac machine until they resolve Big Sur kernel panics. He said he never heard of the problem but assured me Apple pays attention to problems reported in forums. I said, Uh-huh. But I'm still not buying a new Mac until I hear it's fixed.

We need to keep posting about this.

Resetting pram, disconnecting and reconnecting, adjusting settings, power all down, disconnect peripherals, power up and add peripherals one at a time, and similar supposed remedies have not permanently fixed the problem, so far as I can tell from posts by other people. Kernel panics come back.

However, I will be glad to stand corrected if "AppleToTheCore" can report that he has used one of these remedies successfully or knows of someone who has.

Sorry to sound cranky.

Yes I used Catalina but I had some problems when I turned off the Mac (was so slow), Mojave is stable for me and I can use 32-bit applications and some old peripherals for which 64-bit updates do not exist. I believe I'll keep the partition with Mojave just for that, even if Apple fixes the problems with Big Sur (I'll keep the partition with Big Sur as well).

Speaking of my Mac Pro 6.1, I am beginning to believe that if you have 'not new' hardware, it is better not to upgrade it to recent OS versions, even if they support it. Better to give up some new features of the last hour and have a Mac as efficient and fast as it was when it was new. It also saves a lot of money on updated applications and peripherals.

I'm becoming a computer minimalist! ;-)

Ran all day, as usual, with nothing plugged into the back of the machine except a short Ethernet cable to the modem. On manual shutdown, the screen went dark but not black for a long time, which I guess is the period causing the panic because of the failure of watchdogd to check in. The machine restarted itself because of "a problem." Here's the report. Where's the bad hardware, and why didn't it upset Mojave? Thanks.

i hope Apple Engineers respond to you. I believe you are doing them a great service and that you are permitted to post an ending.

by chance are you running an uninterrupted power supply backup setup?

in any event, best of luck?

Ok, thanks. Just for the record, should I say this recommendation comes from Apple?

I'm not sure what recommendation you mean, but nobody here works for Apple except for a few moderators and community helpers.

Sorry, my previous post asking whether using un-interrupted power source is in response to Alexandros80 and

the recommendation was to prepare a drive with multiple partitions and install different MacOS on each, computer hardware permitting. User can then boot into whichever OS they chose to run, didn’t know practice from Apple

I will post an update whenever they come back to me - hopefully soon.

From my experience one needs to keep pushing the Support team for a resolution. It is all down to how much patience and time a user has to investigate an issue like that. After one year of constant Kernel issues I am almost convinced that there is nothing wrong with my external hardwares or my data but Mac's operating system.

No I don't have an uninterrupted power supply backup setup.

Thanks.

Giorgio C,

I am following up your suggestion above regarding Mojave OS. However, I have been experiencing an issue downloading the Mojave installer to my MacBook Pro's volume - see the attachment. Did you experience something similar?

Thanks for the reply Giorgio C. - I tried to download the software through the links you had posted already.

Safari, Mozilla and Chrome cannot downlaod the installer and also on my partner's MacBook Pro could not download the installer. I will try again though - maybe I did something wrong at first place.

My crash message: panic(cpu 4 caller 0xffffff8021553a13): userspace watchdog timeout: no successful checkins from com.apple.remoted in 180 seconds