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
Trivial repro:
dd if=/dev/zero of=blah & tail -F blah
^C
load: 0.21 cmd: tail 72381 [prev->lr_read_cv] 2.17r 0.00u 0.01s 0% 2600k
#0 0x80bce615 at mi_switch+0x155
#1 0x80c1cfea at sleepq_switch+0x11a
#2 0x80b57f0a at _cv_wait+0x15a
#3 0x829ddab6 at rangelock_enter+
> panic: deadlres_td_sleep_q: possible deadlock detected for 0xfe25eefa2e00
> (find), blocked for 1802392 ticks
2 stuck processes from procstat -kk before panic
> 72559 101698 tail- mi_switch+0x155
> sleepq_switch+0x11a _cv_wait+0x15a rangelock_enter+0x306
On 5/11/20 4:21 PM, Pete Wright wrote:
On 5/11/20 3:28 PM, Yuri Pankov wrote:
Pete Wright wrote:
hello,
i have a lenovo thinkpad P43s that exhibits lockups under CURRENT
but behaves fine when running STABLE. i've tried to find a fully
reproducible situation to get this system to lockup b
