2023/freebsd-threads/20230111.freebsd-threads
Messages: 97, sorted by author
|
Last update: Mon Feb 13 14:24:35 2023
|
|
home | archive sorted by: subject | author | date | reverse date
1. Jun 7 Floyd, Paul Re: LDT/GDT and TCB use by threads 2. May 14 Konstantin Belousov Re: LDT/GDT and TCB use by threads 3. Apr 11 Natalino Picone FreeBSD 13.0 thread issue 4. May 14 Paul Floyd LDT/GDT and TCB use by threads 5. May 27 Paul Floyd Re: LDT/GDT and TCB use by threads 6. Apr 3 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 7. Apr 10 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 8. Apr 17 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 9. Apr 24 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 10. Aug 21 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 11. Aug 28 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 12. Dec 4 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 13. Dec 5 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 14. Dec 11 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 15. Dec 12 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 16. Dec 18 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 17. Dec 19 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 18. Dec 25 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 19. Dec 26 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 20. Feb 6 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention
21. Feb 13 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 22. Feb 20 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 23. Feb 27 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 24. Jan 1 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 25. Jan 2 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 26. Jan 9 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 27. Jan 16 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 28. Jan 23 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 29. Jan 30 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 30. Jul 3 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 31. Jul 10 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 32. Jul 17 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 33. Jul 24 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 34. Jul 31 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 35. Jun 5 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 36. Jun 12 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 37. Jun 19 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 38. Jun 26 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 39. Mar 6 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 40. Mar 13 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention
41. Mar 20 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 42. Mar 27 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 43. May 1 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 44. May 8 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 45. May 15 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 46. May 22 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 47. May 29 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 48. Nov 6 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 49. Nov 13 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 50. Nov 20 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 51. Nov 27 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 52. Nov 28 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 53. Oct 2 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 54. Oct 9 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 55. Oct 16 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 56. Oct 23 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 57. Oct 30 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 58. Sep 4 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 59. Sep 11 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 60. Sep 18 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention
61. Sep 25 bugzilla-noreply@FreeBSD.o Problem reports for threads@FreeBSD.org that need special attention 62. Feb 9 bugzilla-noreply@freebsd.o [Bug 192686] Segfaults using combinations of -pie -pthread -lm(|_p) when profiling 63. Feb 9 bugzilla-noreply@freebsd.o [Bug 192686] Segfaults using combinations of -pie -pthread -lm(|_p) when profiling 64. Aug 6 bugzilla-noreply@freebsd.o [Bug 237195] pthread_mutex_unlock crash as unlocked mutex destroyed by signaled thread 65. Aug 6 bugzilla-noreply@freebsd.o [Bug 237195] pthread_mutex_unlock crash as unlocked mutex destroyed by signaled thread 66. Aug 7 bugzilla-noreply@freebsd.o [Bug 237195] pthread_mutex_unlock crash as unlocked mutex destroyed by signaled thread 67. Aug 8 bugzilla-noreply@freebsd.o [Bug 237195] pthread_mutex_unlock crash as unlocked mutex destroyed by signaled thread 68. Apr 6 bugzilla-noreply@freebsd.o [Bug 254995] pthread_cond_timedwait() returns EDEADLK 69. Jan 17 bugzilla-noreply@freebsd.o [Bug 254995] pthread_cond_timedwait() returns EDEADLK 70. Jan 19 bugzilla-noreply@freebsd.o [Bug 254995] pthread_cond_timedwait() returns EDEADLK 71. Jan 19 bugzilla-noreply@freebsd.o [Bug 254995] pthread_cond_timedwait() returns EDEADLK 72. Jan 19 bugzilla-noreply@freebsd.o [Bug 254995] pthread_cond_timedwait() returns EDEADLK 73. Jan 19 bugzilla-noreply@freebsd.o [Bug 254995] pthread_cond_timedwait() returns EDEADLK 74. Jan 7 bugzilla-noreply@freebsd.o [Bug 261010] Trace/BPT trap after interrupting truss 75. Jan 8 bugzilla-noreply@freebsd.o [Bug 261010] Trace/BPT trap after interrupting truss 76. Jan 12 bugzilla-noreply@freebsd.o [Bug 261010] Trace/BPT trap after interrupting truss 77. Jan 13 bugzilla-noreply@freebsd.o [Bug 261010] Trace/BPT trap after interrupting truss 78. Jan 19 bugzilla-noreply@freebsd.o [Bug 261338] [PATCH] kernel panic "bad pte" on heavy CPU load on 12.2 and 12.3 (i386) 79. Jan 19 bugzilla-noreply@freebsd.o [Bug 261338] [PATCH] kernel panic "bad pte" on heavy CPU load on 12.2 and 12.3 (i386) 80. Jan 19 bugzilla-noreply@freebsd.o [Bug 261338] [PATCH] kernel panic "bad pte" on heavy CPU load on 12.2 and 12.3 (i386)
81. Jan 19 bugzilla-noreply@freebsd.o [Bug 261338] [PATCH] kernel panic "bad pte" on heavy CPU load on 12.2 and 12.3 (i386) 82. Jan 19 bugzilla-noreply@freebsd.o [Bug 261338] [PATCH] kernel panic "bad pte" under heavy CPU load on 12.2 and 12.3 (i386) 83. Jan 19 bugzilla-noreply@freebsd.o [Bug 261338] [PATCH] kernel panic "bad pte" under heavy CPU load on 12.2 and 12.3 (i386) 84. Jan 19 bugzilla-noreply@freebsd.o [Bug 261338] [PATCH] kernel panic "bad pte" under heavy CPU load on 12.2 and 12.3 (i386) 85. Jan 19 bugzilla-noreply@freebsd.o [Bug 261338] [PATCH] kernel panic "bad pte" under heavy CPU load on 12.2 and 12.3 (i386) 86. Jan 19 bugzilla-noreply@freebsd.o [Bug 261338] [PATCH] kernel panic "bad pte" under heavy CPU load on 12.2 and 12.3 (i386) 87. Feb 4 bugzilla-noreply@freebsd.o [Bug 261713] ThreadSanitizer detects race in __catopen_l (via strerror_r) 88. Feb 4 bugzilla-noreply@freebsd.o [Bug 261713] ThreadSanitizer detects race in __catopen_l (via strerror_r) 89. Feb 4 bugzilla-noreply@freebsd.o [Bug 261713] ThreadSanitizer detects race in __catopen_l (via strerror_r) 90. Feb 15 bugzilla-noreply@freebsd.o [Bug 261713] ThreadSanitizer detects race in __catopen_l (via strerror_r) 91. Jun 8 bugzilla-noreply@freebsd.o [Bug 264549] e1000/bridge: "sleep on wchan ... with sleeping prohibited" 92. Jun 8 bugzilla-noreply@freebsd.o [Bug 264549] e1000/bridge: "sleep on wchan ... with sleeping prohibited" 93. Jun 8 bugzilla-noreply@freebsd.o [Bug 264549] e1000/bridge: "sleep on wchan ... with sleeping prohibited" 94. Aug 19 bugzilla-noreply@freebsd.o [Bug 265950] POSIX 2008 locale failures when global locale not C 95. Sep 6 bugzilla-noreply@freebsd.o [Bug 265950] POSIX 2008 locale failures when global locale not C 96. Dec 27 bugzilla-noreply@freebsd.o [Bug 268532] [libthr] pthread_mutex_destroy/pshared_gc slow when destroying many process shared locks 97. Jan 1 bugzilla-noreply@freebsd.o [Bug 268532] [libthr] pthread_mutex_destroy/pshared_gc slow when destroying many process shared locks
home | archive sorted by: subject | author | date | reverse date