Skip site navigation (1)Skip section navigation (2)


2019/freebsd-current/20190922.freebsd-current

Messages: 105, sorted by author
Last update: Mon Feb 13 14:17:14 2023

home | archive sorted by: subject | author | date | reverse date
  1. Sep 16 =?UTF-8?Q?Trond_Endrest=C3 Re: hang up with r352239 and r352386 with i5-7500
  2. Sep 16 =?iso-8859-2?Q?M=26S_-_Kra error message during "mergemaster"
  3. Sep 19 Adrian Chadd               Re: wlan can't discover known networks after relocating
  4. Sep 19 Adrian Chadd                Re: wlan can't discover known networks after relocating
  5. Sep 19 Adrian Chadd                Re: wlan can't discover known networks after relocating
  6. Sep 16 Alastair Hogge             Re: panic: sleeping thread on r352386
  7. Sep 18 Andreas Nilsson            Problems upgrading -current with pkgbase
  8. Sep 19 Andreas Nilsson            Re: Lockdown adaX numbers to allow booting ?
  9. Sep 18 Andreas Nilsson            Re: Problems upgrading -current with pkgbase
 10. Sep 19 Bjoern A. Zeeb             Re: wlan can't discover known networks after relocating
 11. Sep 15 CSO@riseup.net             Re: AMD & 13.0 Current
 12. Sep 15 Clay Daniels Jr.            AMD & 13.0 Current
 13. Sep 16 Clay Daniels Jr.            Re: AMD & 13.0 Current
 14. Sep 16 Clay Daniels Jr.            Re: AMD & 13.0 Current
 15. Sep 19 Clay Daniels Jr.           Re: Another X server start failure
 16. Sep 19 Cy Schubert                Re: wlan can't discover known networks after relocating
 17. Sep 20 Cy Schubert                 Re: wlan can't discover known networks after relocating
 18. Sep 20 Cy Schubert                 Re: wlan can't discover known networks after relocating
 19. Sep 19 Daniel Engberg             Re: Lockdown adaX numbers to allow booting ?
 20. Sep 15 Don Lewis                  Re: poudriere, swap full and top says memory is free ?


21. Sep 15 Don Lewis Re: spurious out of swap kills 22. Sep 15 Don Lewis Re: spurious out of swap kills 23. Sep 16 Emmanuel Vadot Re: svn commit: r351858 - in head: bin/uuidgen ... 24. Sep 19 Freddie Cash Re: Lockdown adaX numbers to allow booting ? 25. Sep 19 Freddie Cash Re: Lockdown adaX numbers to allow booting ? 26. Sep 20 Freddie Cash Re: Lockdown adaX numbers to allow booting ? 27. Sep 19 Gary Jennejohn Re: Lockdown adaX numbers to allow booting ? 28. Sep 19 Graham Perrin =?UTF-8?Q?Firefox_=e2=80=93_GtkFileChooserNative_=e2=80=93_file_sel?= =?UTF-8?Q?ection_dialogues?= 29. Sep 20 Greg V =?UTF-8?Q?Re=3A_Firefox_=E2=80=93_GtkFileChooserNa?= =?UTF-8?Q?tive_=E2=80=93_file_selection_dialogues?= 30. Sep 19 Guido Falsi Re: Lockdown adaX numbers to allow booting ? 31. Sep 19 Guido Falsi Re: Lockdown adaX numbers to allow booting ? 32. Sep 21 Hans Petter Selasky Re: r351680 kernel panic in login 33. Sep 19 Johannes Lundberg Re: wlan can't discover known networks after relocating 34. Sep 20 Johannes Lundberg Re: wlan can't discover known networks after relocating 35. Sep 20 Johannes Lundberg Re: wlan can't discover known networks after relocating 36. Sep 17 Johannes Lundberg wlan can't discover known networks after relocating 37. Sep 21 KIRIYAMA Kazuhiko r351680 kernel panic in login 38. Sep 17 KIRIYAMA Kazuhiko r352368 can't boot 39. Sep 16 Konstantin Belousov Re: "Sleeping with non-sleepable lock" in NFS on recent -current 40. Sep 16 Konstantin Belousov Re: "Sleeping with non-sleepable lock" in NFS on recent -current
41. Sep 21 Konstantin Belousov Re: Direct exec of /usr/bin/ld fails with "mmap of entire address space failed: Cannot allocate memory" 42. Sep 17 Konstantin Belousov Re: panic: sleeping thread on r352386 43. Sep 17 Konstantin Belousov Re: panic: sleeping thread on r352386 44. Sep 15 Konstantin Belousov Re: spurious out of swap kills 45. Sep 19 Kurt Jaeger Lockdown adaX numbers to allow booting ? 46. Sep 19 Kurt Jaeger Re: Lockdown adaX numbers to allow booting ? 47. Sep 19 Kurt Jaeger Re: Lockdown adaX numbers to allow booting ? 48. Sep 19 Kurt Jaeger Re: Lockdown adaX numbers to allow booting ? 49. Sep 20 Kurt Jaeger Re: Lockdown adaX numbers to allow booting ? 50. Sep 18 Kyle Evans Re: Problems upgrading -current with pkgbase 51. Sep 17 Li-Wen Hsu FreeBSD CI Weekly Report 2019-09-15 52. Sep 17 Mark Johnston Re: hang up with r352239 and r352386 with i5-7500 53. Sep 20 Mark Martinec Re: Lockdown adaX numbers to allow booting ? 54. Sep 16 Masachika ISHIZUKA Re: hang up with r352239 and r352386 with i5-7500 55. Sep 16 Masachika ISHIZUKA Re: hang up with r352239 and r352386 with i5-7500 56. Sep 16 Masachika ISHIZUKA Re: hang up with r352239 and r352386 with i5-7500 57. Sep 16 Masachika ISHIZUKA Re: hang up with r352239 and r352386 with i5-7500 58. Sep 17 Masachika ISHIZUKA Re: hang up with r352239 and r352386 with i5-7500 59. Sep 18 Masachika ISHIZUKA Re: hang up with r352239 and r352386 with i5-7500 60. Sep 18 Masachika ISHIZUKA Re: hang up with r352239 and r352386 with i5-7500
61. Sep 17 Masachika ISHIZUKA Re: panic: sleeping thread on r352386 62. Sep 17 Masachika ISHIZUKA Re: panic: sleeping thread on r352386 63. Sep 17 Masachika ISHIZUKA Re: panic: sleeping thread on r352386 64. Sep 16 Masachika ISHIZUKA hang up with r352239 and r352386 with i5-7500 65. Sep 16 Masachika ISHIZUKA panic: sleeping thread on r352386 66. Sep 19 Michael Gmelin Re: Lockdown adaX numbers to allow booting ? 67. Sep 19 Michael Gmelin Re: Lockdown adaX numbers to allow booting ? 68. Sep 16 Niclas Zeising Re: hang up with r352239 and r352386 with i5-7500 69. Sep 16 Niclas Zeising Re: hang up with r352239 and r352386 with i5-7500 70. Sep 16 Niclas Zeising Re: hang up with r352239 and r352386 with i5-7500 71. Sep 18 Niclas Zeising Re: hang up with r352239 and r352386 with i5-7500 72. Sep 16 Pete Wright Re: AMD & 13.0 Current 73. Sep 16 Peter Jeremy "Sleeping with non-sleepable lock" in NFS on recent -current 74. Sep 16 Peter Jeremy Re: "Sleeping with non-sleepable lock" in NFS on recent -current 75. Sep 16 Peter Jeremy Re: "Sleeping with non-sleepable lock" in NFS on recent -current 76. Sep 17 Peter Jeremy Re: panic: sleeping thread on r352386 77. Sep 18 Peter Jeremy Re: panic: sleeping thread on r352386 78. Sep 17 Poul-Henning Kamp Re: wlan can't discover known networks after relocating 79. Sep 18 Rebecca Cran Re: ESXi VM does not boot in UEFI mode from 20190906 snapshot ISO 80. Sep 19 Rebecca Cran Re: ESXi VM does not boot in UEFI mode from 20190906 snapshot ISO
81. Sep 19 Rebecca Cran Re: ESXi VM does not boot in UEFI mode from 20190906 snapshot ISO 82. Sep 21 Rebecca Cran Re: ESXi VM does not boot in UEFI mode from 20190906 snapshot ISO 83. Sep 21 Ryan Stone Direct exec of /usr/bin/ld fails with "mmap of entire address space failed: Cannot allocate memory" 84. Sep 21 Ryan Stone Re: Direct exec of /usr/bin/ld fails with "mmap of entire address space failed: Cannot allocate memory" 85. Sep 20 Slawa Olhovchenkov Re: Lockdown adaX numbers to allow booting ? 86. Sep 20 Slawa Olhovchenkov Re: Lockdown adaX numbers to allow booting ? 87. Sep 20 Slawa Olhovchenkov Re: Lockdown adaX numbers to allow booting ? 88. Sep 19 Tom Jones Re: wlan can't discover known networks after relocating 89. Sep 18 Toomas Soome Re: ESXi VM does not boot in UEFI mode from 20190906 snapshot ISO 90. Sep 19 Toomas Soome Re: Lockdown adaX numbers to allow booting ? 91. Sep 19 Toomas Soome Re: Lockdown adaX numbers to allow booting ? 92. Sep 19 Toomas Soome Re: Lockdown adaX numbers to allow booting ? 93. Sep 17 Toomas Soome Re: r352368 can't boot 94. Sep 17 Toomas Soome Re: r352368 can't boot 95. Sep 18 Toomas Soome Re: r352368 can't boot 96. Sep 15 Trev Re: poudriere, swap full and top says memory is free ? 97. Sep 17 Warner Losh Re: r352368 can't boot 98. Sep 17 Warner Losh Re: r352368 can't boot 99. Sep 18 Warner Losh Re: r352368 can't boot 100. Sep 15 Warner Losh Re: spurious out of swap kills
101. Sep 18 Yuri Pankov ESXi VM does not boot in UEFI mode from 20190906 snapshot ISO 102. Sep 18 Yuri Pankov Re: ESXi VM does not boot in UEFI mode from 20190906 snapshot ISO 103. Sep 18 Yuri Pankov Re: ESXi VM does not boot in UEFI mode from 20190906 snapshot ISO 104. Sep 19 mms.vanbreukelingen@gmail. Another X server start failure 105. Sep 21 mms.vanbreukelingen@gmail. The X11 error correction went to a non-booting kernel


home | archive sorted by: subject | author | date | reverse date