Re: Double panic -- KSE and /dev/null???

"Daniel C. Sobral" wrote:
> 
> The /dev/null panic was masked by the KSE panic, unfortunately. All I
> have is the message:
> 
> panic: No strategy on dev null responsible for buffer 0xc78084f8

Dump the buffer header.  With that information, you should be
able to understand why the code is feeling it necessary to
call the panic, and what it wants instead.

Unfortunately, there may not be a way to attribute the buffer
to its source, if it's corrupted, which means tracking sizes
to find out where it came from.

-- Terry