After updating to r256624, the system is very unresponsive,
and really unusable - any command (ps, df, top, ls, etc.)
might take up to 1 min to return. However, I could not get
it to panic.
So I reverted back to r255488.
This time I managed to obtain a textdump:
Hi!
On 23 October 2013 02:18, Anton Shterenlikht me...@bris.ac.uk wrote:
After updating to r256624, the system is very unresponsive,
and really unusable - any command (ps, df, top, ls, etc.)
might take up to 1 min to return. However, I could not get
it to panic.
So I reverted back to
From adrian.ch...@gmail.com Wed Oct 23 14:22:00 2013
On 23 October 2013 02:18, Anton Shterenlikht me...@bris.ac.uk wrote:
After updating to r256624, the system is very unresponsive,
and really unusable - any command (ps, df, top, ls, etc.)
might take up to 1 min to return. However, I could not
On Monday, October 14, 2013 4:44:28 am Anton Shterenlikht wrote:
BTW, I see in dmesg:
Starting ddb.
ddb: sysctl: debug.ddb.scripting.scripts: Invalid argument
/etc/rc: WARNING: failed to start ddb
What is that about?
panic: uma_zfree: Freeing to non free bucket index.
cpuid = 0
BTW, I see in dmesg:
Starting ddb.
ddb: sysctl: debug.ddb.scripting.scripts: Invalid argument
/etc/rc: WARNING: failed to start ddb
What is that about?
panic: uma_zfree: Freeing to non free bucket index.
cpuid = 0
KDB: stack backtrace:
db_trace_self(0x9ffc00158380) at db_trace_self+0x40
