On 1/14/15 7:01 , Lukas Kaltenbach via smartos-discuss wrote: > Hi Garret, > > i booted with kmdb, but what do you mean with F1-A? Pressing "F1" + "A"? > If yes, that doesn't work. > Can you explain me how to debug this problem?
In this case, I would take a different approach. Here, I would boot with -kd, and basically the goal is to try and find the last instruction you can execute. One trick would be to set the moddebug variable to 0xf0000001, which when you get to the prompt can be done by running: > moddebug/W 0xf0000001 That will cause the system to have a break point on every module loading entry and exit point. There, I'd do one pass that determines what the last breakpoint you hit is, and use ':c' each time to continue to the next. Next, I would take another lap and basically single step until you find what the last instruction you can single step over is. From there, we can figure out what the next steps are. An alternative path is to determine if your laptop has some means of injecting a non-maskable interrupt. > So all in all its not a good idea to use smartos on a laptop? It's certainly not the design center, which is that of a headless server in a datacenter, eg. if you're looking for X11, it's going to be quite painful and not really part of the design center. 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
