Re: DFly-stable as of April 1st crashed, but no crash dump was possible due to ips driver being unable to do crash dumps

[Raphael Marmier <raphael@xxxxxxxxxxx>]

I am unable to get a crash dump through the ddb and typing panic and 
hitting enter twice. I end up in the same state as you discribe.

hint anyone?

This is with CURRENT of a few days ago.

Raphael

Tomaž Borštnar wrote:
> Hello!
>
>     This morning I update Dfly-stable from end of October to April 1st 
> version and already got one crash - due to some sort of panic (Panic-A 
> something?). Unfortunately even though I have :
>
> dumpdev="/dev/ipsd0s1b" # Device name to crashdump to (or NO).
> dumpdir="/net/crash"    # Directory where crash dumps are to be stored
>
>
> in both rc.conf and loader.conf machine was not able to do anything 
> about it. It was stuck in "Syncing disks...". So no logs.
>
> I can try to connect serial port to another machine and log everything 
> there, but would need a bit of advice what to do to catch more info next 
> time.
>
> Also, would some watchdog thing help in this case to at least restart 
> the machine if some userland program was not updating its timer? Or 
> maybe this:
>
> # Set the amount of time (in seconds) the system will wait before
> # rebooting automatically when a kernel panic occurs.  If set to (-1),
> # the system will wait indefinitely until a key is pressed on the
> # console.
> options         PANIC_REBOOT_WAIT_TIME=16
>
>
> Thanks in advance.
>
> Tomaz