Marcus Heine wrote:
Brian,


Brian Ruthven - Sun UK wrote:

Marcus Heine wrote:

Hi,

I am currently playing around with diskless Solaris (iscsi, network booted ramdisk, etc) and found that dumpadm allows me to configure a USB stick or an iscsi device as a dump
device no problem, like
    dumpadm -c kernel -d /dev/dsk/...
but testing this with "reboot -d" did not result in any crashdump activity.
The x86 system just hung for about 5 seconds and then reset.
How are you concluding there was no "crashdump activity"?
To me, that sounds like it was dumping to the USB stick - 5 seconds could be about right for a fast x86 system. Did you check for a corresponding panic message in the /var/adm/messages file when the system came back up?

My USB stick has a little LED that flashes when it is written to. In the 5 seconds it did not flash at all. Also savecore when enabled (thanks for pointing that out) does not find any crashdump when it reboots.
I just tried once more.

Fair enough. At least we explored it to make sure.



Also, should I not see a panic string on the console and even a kernel stack trace for a couple of seconds
on the screen, before resetting?

This depends on what state the system is in. If you are in a graphical environment, then the text-mode panic string will not be visible. If you are operating either in text mode on the console or via a serial port (ALOM, SP, SC, etc...) then you should see the panic and reboot messages.


Does /var/adm/messages contain any clues along the lines of "could not dump to /dev/XXX" in place of the expected "dumping to /dev/XXX"?


Anyway, to me it sounds like USB is not a valid dump device (as you originally postulated), but my main points were to make sure we had arrived at that conclusion for the right reasons, and to make sure savecore was enabled.

I'll have to leave this to one of the USB / drivers teams to answer.

In any case, I wonder whether a bug should be logged, perhaps not to prevent dumping to an inappropriate device (as it is still useful for "savecore -L" use), but at least display a warning when setting it. The same goes for setting a dump device to an iscsi target if this too is not valid.


Regards,
Brian

--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG

_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss

Reply via email to