Just to get a bigger exposure: https://reviews.freebsd.org/D24779
I think that this is a good idea and, if I am not mistaken, it should match the
Linux behavior.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/ma
On Mon, 2017-09-11 at 22:44 -0500, Jeremy wrote:
> Lock order reversals are quite normal if you are using 12 Current,
> especially with the GENERIC kernel, since all of the debugging
> features are
> turned on. I think the options WITNESS causes LORs to be printed. I
> see
> them when I restart my
doing really well like with the
previous 10.x-Release. Though I am seeing a kernel stack trace:
lock order reversal:
1st 0xf80106be25f0 zfs (zfs) @ /usr/src/sys/kern/vfs_mount.c:849
2nd 0xf80106c53068 devfs (devfs) @
/usr/src/sys/kern/vfs_subr.c:2606
stack backtrace:
#0 0x80ac52d3 at
On Sat, 19 Apr 2014, R. Tyler Croy wrote:
I've noticed this as of late on my i386 -CURRENT Thinkpad T43 when I perform
some file operations, but an exact reproduction case I've not yet stumbled
upon:
Apr 20 01:29:32 lemon kernel: lock order reversal:
Apr 20 01:29:32 lemon kernel: 1st 0xc58323
I've noticed this as of late on my i386 -CURRENT Thinkpad T43 when I
perform some file operations, but an exact reproduction case I've not
yet stumbled upon:
Apr 20 01:29:32 lemon kernel: lock order reversal:
Apr 20 01:29:32 lemon kernel: 1st 0xc5832358 bufwait (bufwait) @
/usr/home/tyler/sour
This is 10days old kernel panic, the same type I report before, but now I
use dont-sync-on-panic sysctl, so some stack trace finally available:
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x24
fault code = supervisor read, page not present
instruction
Hi,
How does one go about dumping the stack trace for the other cpu
while in ddb or gdb?
This is on current.
Thanks,
Lars
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
