[indiana-discuss] 2009.06 - Reboot after copyright text

[mary ding]

Haik:

Another useful way of using -kd, this is from engineers that I worked 
with and this is normally what I will do:

Boot with kadb, debug.

On sparc, boot -kd.  On x86, in the GRUB item, type "e" (for edit) and
then another "e" and then add "-k -d "	to the end of the kernel line
or before the -B options.  Finally, press return to boot this entry.

This will cause the kernel debugger to load

          Loading kmdb...

          Welcome to kmdb
          kmdb: unable to determine terminal type: assuming `vt100'
          Loaded modules: [ unix krtld genunix ]
          [0]>

At the prompt, enter "moddebug/W 0x80000000", <return> and then ":c",
<return> which will then print out each module as it's being loaded.

If a specific device can be identified, removing the driver may
allow a boot to proceed.


For b107/b108, there are known issues and some x86 machines will hang:

6800617 - cannot boot nv_107 on Ultra20 and hang in different module


Haik Aftandilian wrote:
>> You can add "-v" option to the kernel command line in
>> the grub to get
>> more information.
>> You may add "-kd" as well to activate kmdb to see
>> more details.
> 
> Booting with -kd will cause kmdb to load (due to the -k), but the -d will cause kmdb to load and then stop Solaris in the debugger early on in the boot. This is useful if you want to modify kernel data structures or variables early in the boot sequence. In this case, hit ":c" to leave kmdb and continue to boot with kmdb still loaded.
> 
> You want kmdb loaded so that if a kernel panic occurs during the boot, the OS will stop in the debugger.
> 
> -v turns on verbose messages during boot.
> 
> So I would just add -v and -k for now.
> 
> Using -kd might be a useful test to see if the kernel even boots far enough to load kmdb.
> 
> Haik