laptop is hung on kernel panic after doing kdump configurations.

Hi all,


For my client kernel panic is happening. I recommended the settings below:


https://developer.apple.com/library/content/technotes/tn2004/tn2118.html



When I generated the panic using dtrace on VMWare everything worked as expected and I got te core file on kdump server machine in /PanicDump folder. But same configuration, when tried from physical machine, after running the dtrace panic command, machine just hung without any communication with kdump server. I could not even see the black panic screen unless I forcibly rebooted.


Suprisingly it is working on all Virtual machines and not working from any of the physical laptops.


Below is the configuration of my laptop:

10.11.5 (15F34)

MacBook Pro (Retina, 15-inch, Mid 2015)


Did anyone face the same problem? Any suggestions?

Replies

Install/Setup/Configuration questions might have better luck over on Apple's public support forums, thanks and good luck.

But same configuration, when tried from physical machine, after running the dtrace panic command, machine just hung without any communication with kdump server.

What type of network interface are you using for this?

Share and Enjoy

Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

Tried using both wi-fi as well as Thunderbolt Ethernet.

I’ve helped dshiralkar with this issue in a separate context but I wanted to post the following, just for the record.

Tried using both wi-fi as well as Thunderbolt Ethernet.

Wi-Fi is simply not supported.

Thunderbolt Ethernet is supported, but you have to jump through some hoops.

As general advice, I recommend that you combine the info from:

Share and Enjoy

Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

)Running into the same issue (macOS 10.14.4, first touchbar 15" MBP, Thunderbolt 3 to ethernet adaptor).


Core dump server is connected via ethernet.

Even tried started kdumpd manually inside launchctl to see if having it running rather than on-demand would help. No dice.


client (panic-ing mac):


$ nvram -p | grep boot-args
boot-args    debug=0xd44 _panicd_ip=192.168.1.213 kdp_match_name=en9
$ ifconfig

en9: flags=8863<up,broadcast,smart,running,simplex,multicast> mtu 1500
    options=4<vlan_mtu>
    ether 58:ef:68:13:96:66
    inet6 fe80::452:8c4d:571b:c390%en9 prefixlen 64 secured scopeid 0x7
    inet 192.168.1.108 netmask 0xffffff00 broadcast 192.168.1.255
    nd6 options=201<performnud,dad>
    media: autoselect (1000baseT )
    status: active

…


Checked the kernel debug kit as per Quinn's suggestion, no dice.


Disabled SIP so I could use the dtrace test to force a panic:


sudo dtrace -w -n "BEGIN{ panic();}"



(note that neither the technote or kernel debug kit readme mention that the nvram commands have to be done while in recovery mode, nor that you have to disable SIP to run the dtrace test. Technote references InstantPanic attached to it but that is only built for PPC and modifying and building oneself results in something that I'm not able to get installed - unauthorized kext error. Feedback ID: 6127904)


Also the recommended keystrokes to generate NMI (both command keys and power button as per http://developer.apple.com/qa/qa2001/qa1264.html ) don't seem to work on my 15" late 2016 touchbar MBP (?).


Currently when I run the dtrace the mac just hangs.


Any suggestions appreciated.