On 12/28/16 3:10 , Ante Vojvodic wrote:
> Hi Robert,
> 
> Here is output from kmdb after sending NMI, I can't get core dump, is this
> too
> early in boot and dump device is not yet configured?
> And is there an option I'm not aware of to disable reboot and get kmdb?
> How to set early on boot apic_panic_on_nmi=0 and apic_kmdb_on_nmi=1?

Hi Ante,

The best thing to do here is to select the kmdb boot option from the
bios menu. This will then let you end up in the debugger when you take
the nmi. When you're at the first prompt, you'll want to use ':c' to
continue.

At the nmi, the most useful things to get started would be the following
commands:

'$C'
'::stacks -m xhci'
'::stacks -m usba'
'::prtusb'

Once we get that, I'll see if we can dig further into what SMCI is doing
with that BIOS option as well and reach out to them.

Thanks,
Robert

> installing kb8042, module id 97.
> 
> panic[cpu0]/thread=fffffffffbc31de0: NMI received
> 
> Warning - stack not written to the dump buffer
> fffffffffbc73d80 fffffffff792970f ()
> fffffffffbc73db0 unix:av_dispatch_nmivect+34 ()
> fffffffffbc73dc0 unix:nmiint+152 ()
> fffffffffbc73f00 unix:ddi_io_get8+f ()
> fffffffffbc73f90 kb8042:kb8042_send_and_wait+b5 ()
> fffffffffbc73fd0 kb8042:kb8042_send_to_keyboard+b6 ()
> fffffffffbc74000 kb8042:kb8042_init+54 ()
> fffffffffbc74040 kb8042:kb8042_attach+205 ()
> fffffffffbc740b0 genunix:devi_attach+92 ()
> fffffffffbc740f0 genunix:attach_node+a7 ()
> fffffffffbc74140 genunix:i_ndi_config_node+7d ()
> fffffffffbc74170 genunix:i_ddi_attachchild+48 ()
> fffffffffbc741b0 genunix:devi_attach_node+5e ()
> fffffffffbc742b0 genunix:devi_config_one+294 ()
> fffffffffbc74330 genunix:ndi_busop_bus_config+c1 ()
> fffffffffbc743c0 i8042:i8042_bus_config+a0 ()
> fffffffffbc74430 genunix:ndi_devi_config_one+186 ()
> fffffffffbc74510 genunix:resolve_pathname+155 ()
> fffffffffbc74540 genunix:ddi_pathname_to_dev_t+19 ()
> fffffffffbc74570 consconfig_dacf:consconfig_load_drivers+a3 ()
> fffffffffbc74590 consconfig_dacf:dynamic_console_config+a5 ()
> fffffffffbc745a0 consconfig:consconfig+9 ()
> fffffffffbc745f0 unix:stubs_common_code+59 ()
> fffffffffbc74630 genunix:main+1e1 ()
> fffffffffbc74640 unix:_locore_start+90 ()
> 
> skipping system dump - no dump device configured
> 
> 
> 
> Next thing I tried is to boot system with "disable-kb8042=true" in kernel
> args.
> And after system boots ok, I tried to manually load kb8042 driver in order
> to
> get coredump but:
> 
> $ modload /kernel/drv/amd64/kb8042
> can't load module: No such device or address
> 
> Any further suggestions?
> 
> On Wed, Dec 28, 2016 at 3:42 AM, Robert Mustacchi <[email protected]> wrote:
> 
>>
>> Do you have ipmi setup on that system? While we have had success on
>> other SMCI X11 boards, that failure is somewhat newer. If you do have
>> IPMI, would it be possible to boot to kmdb and then after it hangs,
>> inject an nmi? If it is, there are a couple of additional diagnostics
>> that'd be worth collecting so we can root cause what's going on.
>>
>> Thanks,
>> Robert
>>
>>
> 
> 


-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Reply via email to