On 17/02/13 06:54 AM, Sašo Kiselkov wrote:
On 02/16/2013 09:49 PM, John D Groenveld wrote:
Boot with kernel debugger so you can see the panic.

Sadly, though, without access to the source code, all he do can at that
point is log a support ticket with Oracle (assuming he has paid his
support fees) and hope it will get picked up by somebody there. People
on this list have few, if any ways of helping out.

You're missing the point. Booting with kmdb enabled
is The Way(tm) to get anything remotely resembling
a paused screen so you can see what the message is.

Whether that message winds up being something you need
to talk with a Oracle about is entirely different.

The OP mentioned that he was running S11 Express, for
which, iirc, you can dig through source on a non-Oracle
site and investigate.

Really, though, just adding


to the kernel$ line in the grub menu prior to booting
should be enough for him to make significant progress.

James C. McPherson
Systems / Solaris / Core
zfs-discuss mailing list

Reply via email to