On 3 Jun 2009, at 13:49, John Martin wrote: > Chris Ridd wrote: >> >> I'm still unsure how to extract extra diagnostics from a wedged >> system via a serial console. > One of the advantages of the serial console is it runs at a higher > priority (usually IPL 12) which allows it to still work when a lower > priority driver is stuck in its interrupt code. Have you tried > booting > the debugger by adding the options " -Bconsole=ttya -kd" to the > kernel line in grub?
I just have, and it drops straight into kmdb and then ignores anything I type using minicom. I suspect there's something simple I'm missing in the serial console setup... menu.lst has: serial --unit=0 --speed=9600 terminal serial and ",console=ttya" on the kernel line, and running eeprom: root at canopus:/boot/solaris# eeprom console=ttya eeprom: error returned from bootadm: Default /boot/grub/menu.lst entry is not controlled by bootadm. Exiting root at canopus:/boot/solaris# grep setprop bootenv.rc setprop ata-dma-enabled '1' setprop atapi-cd-dma-enabled '1' setprop ttyb-rts-dtr-off 'false' setprop ttyb-ignore-cd 'true' setprop ttya-rts-dtr-off 'false' setprop ttya-ignore-cd 'true' setprop ttyb-mode '9600,8,n,1,-' setprop ttya-mode '9600,8,n,1,-' setprop lba-access-ok '1' setprop keyboard-layout 'Unknown' setprop console 'ttya' >> >> However I have since forced the box to boot this BE (111b) with a >> 32-bit kernel - it only has 3GB of RAM anyway - and so far things >> have been fine... > Is the time to failure short enough to believe the issue is unique to > booting 64-bit? Yesterday I'd have said yes, but frustratingly today it seems harder to break in a 64-bit kernel. Sorry the kernel bitness might be a red herring. Cheers, Chris
