[Bug 281560] gve (4) uma deadlock during high tcp throughput

[email protected]
Newsgroups gmane.os.freebsd.devel.net
Message-ID <[email protected]/bugzilla/>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281560

--- Comment #11 from [email protected] ---
Just a more succinct view of iperf thread 100719's central role in this
deadlock:

```
db> show lockchain 100413
thread 100413 (pid 0, gve0 rxq 0) is blocked on lock 0xfffffe00df57a3d0 (sleep
mutex) "mbuf"
thread 100719 (pid 857, iperf) is on a run queue

db> show lockchain 100414
thread 100414 (pid 0, gve0 rxq 1) is blocked on lock 0xfffff800b86f8560 (rw)
"tcpinp"
thread 100706 (pid 857, iperf) is blocked on lock 0xfffffe00df57a3d0 (sleep
mutex) "mbuf"
thread 100719 (pid 857, iperf) is on a run queue

db> show lockchain 100433
thread 100433 (pid 0, gve0 txq 2) is blocked on lock 0xfffffe00df57a3d0 (sleep
mutex) "mbuf"
thread 100719 (pid 857, iperf) is on a run queue

db> show lockchain 100419
thread 100419 (pid 0, gve0 rxq 6) is blocked on lock 0xfffff800b8d53020 (rw)
"tcpinp"
thread 100703 (pid 857, iperf) is blocked on lock 0xfffffe00df57a3d0 (sleep
mutex) "mbuf"
thread 100719 (pid 857, iperf) is on a run queue
```

-- 
You are receiving this mail because:
You are the assignee for the bug.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.