https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213
Eugene Grosbein changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org|freebsd-stable@FreeBSD.org
On 02/04/2018 18:35, Eugene Grosbein wrote:
Use such debugging kernel to drop to the debugger when deadlock occurs
using Ctr-Alt-ESC and type "call doadump", you should get crashdump anyway.
Then use "reboot" or just power cycle to get crashdump stored to /var/crash.
Then fill a PR and reply wit
02.04.2018 23:41, Mark Knight пишет:
> On 02/04/2018 14:44, Eugene Grosbein wrote:
>> 3. Boot new kernel using nextboot(8) and see if it will crash instead of
>> deadlock
>> and if so, fill the PR to Bugzilla.
>
> Thanks again. Drat, no crash. The only difference was a few new errors during
> th
On 02/04/2018 14:44, Eugene Grosbein wrote:
3. Boot new kernel using nextboot(8) and see if it will crash instead of
deadlock
and if so, fill the PR to Bugzilla.
Thanks again. Drat, no crash. The only difference was a few new errors
during the boot - which I'm assuming are unrelated.
Apr
Hi,
Anyone offer any suggestions about this?
kernel: panic: solaris assert: arc_decompress(buf) == 0 (0x5 == 0x0), file:
/usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c, line: 4923
kernel: cpuid = 1
kernel: KDB: stack backtrace:
kernel: #0 0x80aadac7 at kdb_backtrace+0x67
k
On 02.04.2018 19:27, Mark Knight wrote:
>> What does it show if you press "CTRL-T" to see a status of "hung" process?
>
> Typically CTRL-T shows [sysctl mem]. In some circumstances I can CTRL-C
> (e.g. if su hangs), in others I cannot (e.g. with sudo).
>
>> Does it help if you comment out the l
On 02/04/2018 06:56, Eugene Grosbein wrote:
What does it show if you press "CTRL-T" to see a status of "hung" process?
Typically CTRL-T shows [sysctl mem]. In some circumstances I can CTRL-C
(e.g. if su hangs), in others I cannot (e.g. with sudo).
Does it help if you comment out the line me
