On 12/28/16 8:25 , Ante Vojvodic wrote: > Hi Robert, > > Problem is as I wrote in my previous mail that when I issue NMI (chassis > power diag), Instead of entering kmdb (SmartoS is booted with kmdb) I get > panic with same stack trace as in previous mail and system gets rebooted.
Hi Ante, Sorry, I hadn't realized you had booted with -kd. Normally when you inject an nmi that works just fine and it traps into kmdb. Hmm. May be worth just trying to inject a normal break (if on the ipmi serial you can usually use ~b to get into it). If that doesn't work, let me know and I'll try and put together some more involved instructions on breaking and get some time to dig further into the stack trace to see if I might be able to manually put together what I/O port we're writing to so I can follow up with SMCI. Robert > On Wed, Dec 28, 2016 at 3:32 PM, Robert Mustacchi <[email protected]> wrote: > >> 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. >> > > ------------------------------------------- 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
