2018/freebsd-current/20180107.freebsd-current
Messages: 96, sorted by subject
|
Last update: Mon Feb 13 14:17:08 UTC 2023
|
|
home | up | archive sorted by: subject | author | date | reverse date
1. Dec 31 Re: evdev broken 2. Jan 2 Michael Butler Intel CPU design flaw - FreeBSD affected? 3. Jan 2 Zaphod Beeblebrox Re: Intel CPU design flaw - FreeBSD affected? 4. Jan 3 Warner Losh Re: Intel CPU design flaw - FreeBSD affected? 5. Jan 3 Cy Schubert RE: Intel CPU design flaw - FreeBSD affected? 6. Jan 3 Cy Schubert RE: Intel CPU design flaw - FreeBSD affected? 7. Jan 3 Cy Schubert RE: Intel CPU design flaw - FreeBSD affected? 8. Jan 3 Cy Schubert RE: Intel CPU design flaw - FreeBSD affected? 9. Jan 3 Michael Butler Re: Intel CPU design flaw - FreeBSD affected? 10. Jan 3 Cy Schubert Re: Intel CPU design flaw - FreeBSD affected? 11. Jan 3 Kurt Jaeger Re: Intel CPU design flaw - FreeBSD affected? 12. Jan 3 Cy Schubert RE: Intel CPU design flaw - FreeBSD affected? 13. Jan 3 Cy Schubert RE: Intel CPU design flaw - FreeBSD affected? 14. Jan 4 Mark Heily Re: Intel CPU design flaw - FreeBSD affected? 15. Jan 4 blubee blubeeme Re: Intel CPU design flaw - FreeBSD affected? 16. Jan 4 Darren Reed Re: Intel CPU design flaw - FreeBSD affected? 17. Jan 4 Tomoaki AOKI Re: Intel CPU design flaw - FreeBSD affected? 18. Jan 4 Stefan Esser Re: Intel CPU design flaw - FreeBSD affected? 19. Jan 4 Chris H Re: Intel CPU design flaw - FreeBSD affected? 20. Jan 4 Warner Losh Re: Intel CPU design flaw - FreeBSD affected?
21. Jan 5 Mark Millard Re: Intel CPU design flaw - FreeBSD affected? 22. Jan 5 Erich Dollansky Re: Intel CPU design flaw - FreeBSD affected? 23. Jan 4 Klaus P. Ohrhallinger Re: Intel CPU design flaw - FreeBSD affected? // disabling _R_DTSC 24. Jan 4 blubee blubeeme Re: Intel CPU design flaw - FreeBSD affected? // disabling _R_DTSC 25. Jan 6 Andrew Reilly Re: Intel CPU design flaw - FreeBSD affected? // disabling _R_DTSC 26. Jan 4 Klaus P. Ohrhallinger Re: Intel CPU design flaw - FreeBSD affected? // disabling LDTSC 27. Jan 4 =?UTF-8?Q?Jan_Kokem=c3=bcl Re: Intel CPU design flaw - FreeBSD affected? // disabling LDTSC 28. Jan 4 Klaus P. Ohrhallinger Re: Intel CPU design flaw - FreeBSD affected? // disabling LDTSC 29. Jan 4 Michael Butler Re: Intel CPU design flaw - FreeBSD affected? // disabling LDTSC 30. Jan 4 Conrad Meyer Re: Intel CPU design flaw - FreeBSD affected? // disabling LDTSC 31. Jan 6 Klaus P. Ohrhallinger Re: Intel CPU design flaw - FreeBSD affected? // disabling LDTSC 32. Jan 6 Mark Millard Re: Intel CPU design flaw - FreeBSD affected? [AMD family Zen/17h status] 33. Jan 5 Jon Brawn Re: Intel CPU design flaw - FreeBSD affected? Information from Arm 34. Jan 2 Don Lewis more fallout from removal of lint 35. Jan 2 Shawn Webb Re: more fallout from removal of lint 36. Jan 4 O. Hartmann Re: more fallout from removal of lint 37. Jan 4 Mark Heily Re: more fallout from removal of lint 38. Jan 5 Mark Millard Re: more fallout from removal of lint 39. Jan 5 Mark Millard Re: more fallout from removal of lint 40. Dec 30 Matthias Apitz Re: panic: invalid bcd 194
41. Dec 31 Matthias Apitz Re: panic: invalid bcd 194 42. Dec 31 Ian Lepore Re: panic: invalid bcd 194 43. Jan 1 Matthias Apitz Re: panic: invalid bcd 194 44. Jan 1 Kurt Jaeger Re: panic: invalid bcd 194 45. Jan 1 Matthias Apitz Re: panic: invalid bcd 194 46. Jan 1 Ian Lepore Re: panic: invalid bcd 194 47. Jan 2 Ian Lepore Re: panic: invalid bcd 194 48. Jan 2 Rodney W. Grimes Re: panic: invalid bcd 194 49. Jan 2 Matthias Apitz Re: panic: invalid bcd 194 50. Jan 2 Matthias Apitz Re: panic: invalid bcd 194 51. Jan 2 Kurt Jaeger Re: panic: invalid bcd 194 52. Jan 2 Matthias Apitz Re: panic: invalid bcd 194 53. Jan 1 Pierre DAVID Problem with C11 _Atomic 54. Jan 1 Konstantin Belousov Re: Problem with C11 _Atomic 55. Jan 2 Pierre DAVID Re: Problem with C11 _Atomic 56. Jan 2 Konstantin Belousov Re: Problem with C11 _Atomic 57. Jan 1 Adrian Chadd Re: Programmatically cache line 58. Jan 1 David Chisnall Re: Programmatically cache line 59. Jan 1 Konstantin Belousov Re: Programmatically cache line 60. Jan 1 Ian Lepore Re: Programmatically cache line
61. Jan 2 blubee blubeeme Re: Programmatically cache line 62. Jan 3 Maurizio Vairani Re: Programmatically cache line 63. Jan 3 Ed Schouten Re: Programmatically cache line 64. Jan 3 Nathan Whitehorn Re: Programmatically cache line 65. Jan 4 David Chisnall Re: Programmatically cache line 66. Jan 4 Konstantin Belousov Re: Programmatically cache line 67. Jan 4 blubee blubeeme Re: Programmatically cache line 68. Jan 5 Jon Brawn Re: Programmatically cache line 69. Jan 5 David Chisnall Re: Programmatically cache line 70. Dec 31 Warner Losh Re: r327359: cylinder checksum failed: cg0, cgp: 0x4515d2a3 != bp: 0xd9fba319 Dec 71. Jan 4 Michael Tuexen Re: r327359: cylinder checksum failed: cg0, cgp: 0x4515d2a3 != bp: 0xd9fba319 Dec 72. Jan 4 O. Hartmann Re: r327359: cylinder checksum failed: cg0, cgp: 0x4515d2a3 != bp: 0xd9fba319 Dec 73. Jan 4 Michael Tuexen Re: r327359: cylinder checksum failed: cg0, cgp: 0x4515d2a3 != bp: 0xd9fba319 Dec 74. Jan 4 Kristof Provost RFC: mallocarray() 75. Jan 2 Mark Millard rpi2 head -r327485 (e.g.): rpi2 leaves one "CPU n" always idle for some boots 76. Jan 2 Mark Millard Re: rpi2 head -r327485 (e.g.): rpi2 leaves one "CPU n" always idle for some boots 77. Jan 4 Benjamin Kaduk Second Call for 2017Q4 quarterly status reports 78. Dec 31 Michael Butler SVN r327433 fails to build 79. Dec 31 Herbert J. Skuhra Re: SVN r327433 fails to build 80. Dec 31 Colin Percival Re: SVN r327433 fails to build
81. Dec 31 Colin Percival Re: SVN r327433 fails to build 82. Dec 31 Michael Butler SVN r327444 breaks current build 83. Dec 31 Ian Lepore Re: SVN r327444 breaks current build 84. Dec 31 Oleksandr Tymoshenko Re: SVN r327444 breaks current build 85. Dec 31 Nathan Whitehorn Re: SVN r327444 breaks current build 86. Dec 31 Oleksandr Tymoshenko Re: SVN r327444 breaks current build 87. Jan 1 Ian Lepore Re: SVN r327444 breaks current build 88. Jan 1 Oleksandr Tymoshenko Re: SVN r327444 breaks current build 89. Jan 4 Leonardo Fogel To which list should I submit a patch? 90. Jan 4 Conrad Meyer Re: To which list should I submit a patch? 91. Jan 3 blubee blubeeme USB stack 92. Jan 3 blubee blubeeme Re: USB stack 93. Jan 3 O'Connor, Daniel Re: USB stack 94. Jan 3 O'Connor, Daniel Re: USB stack 95. Jan 4 Gary Jennejohn Re: USB stack 96. Jan 4 O'Connor, Daniel Re: USB stack
home | up | archive sorted by: subject | author | date | reverse date