2008/freebsd-current/20080525.freebsd-current
Messages: 133, sorted by subject
|
Last update: Mon Feb 13 14:16:03 UTC 2023
|
|
home | up | archive sorted by: subject | author | date | reverse date
1. May 22 FreeBSD Tinderbox [head tinderbox] failure on amd64/amd64 2. May 22 FreeBSD Tinderbox [head tinderbox] failure on amd64/amd64 3. May 23 FreeBSD Tinderbox [head tinderbox] failure on amd64/amd64 4. May 24 FreeBSD Tinderbox [head tinderbox] failure on amd64/amd64 5. May 24 FreeBSD Tinderbox [head tinderbox] failure on amd64/amd64 6. May 24 FreeBSD Tinderbox [head tinderbox] failure on amd64/amd64 7. May 24 FreeBSD Tinderbox [head tinderbox] failure on amd64/amd64 8. May 22 FreeBSD Tinderbox [head tinderbox] failure on arm/arm 9. May 22 FreeBSD Tinderbox [head tinderbox] failure on arm/arm 10. May 18 FreeBSD Tinderbox [head tinderbox] failure on i386/i386 11. May 18 FreeBSD Tinderbox [head tinderbox] failure on i386/i386 12. May 18 Remko Lodder Re: [head tinderbox] failure on i386/i386 13. May 22 FreeBSD Tinderbox [head tinderbox] failure on i386/i386 14. May 23 FreeBSD Tinderbox [head tinderbox] failure on i386/i386 15. May 24 FreeBSD Tinderbox [head tinderbox] failure on i386/i386 16. May 24 FreeBSD Tinderbox [head tinderbox] failure on i386/i386 17. May 24 FreeBSD Tinderbox [head tinderbox] failure on i386/i386 18. May 24 Robert Watson Re: [head tinderbox] failure on i386/i386 19. May 22 FreeBSD Tinderbox [head tinderbox] failure on i386/pc98 20. May 22 FreeBSD Tinderbox [head tinderbox] failure on i386/pc98
21. May 23 FreeBSD Tinderbox [head tinderbox] failure on i386/pc98 22. May 23 FreeBSD Tinderbox [head tinderbox] failure on i386/pc98 23. May 23 Ed Schouten Re: [head tinderbox] failure on i386/pc98 24. May 24 FreeBSD Tinderbox [head tinderbox] failure on i386/pc98 25. May 24 FreeBSD Tinderbox [head tinderbox] failure on i386/pc98 26. May 24 FreeBSD Tinderbox [head tinderbox] failure on i386/pc98 27. May 22 FreeBSD Tinderbox [head tinderbox] failure on ia64/ia64 28. May 22 FreeBSD Tinderbox [head tinderbox] failure on ia64/ia64 29. May 23 FreeBSD Tinderbox [head tinderbox] failure on ia64/ia64 30. May 23 FreeBSD Tinderbox [head tinderbox] failure on ia64/ia64 31. May 22 FreeBSD Tinderbox [head tinderbox] failure on powerpc/powerpc 32. May 22 FreeBSD Tinderbox [head tinderbox] failure on powerpc/powerpc 33. May 23 FreeBSD Tinderbox [head tinderbox] failure on powerpc/powerpc 34. May 23 FreeBSD Tinderbox [head tinderbox] failure on powerpc/powerpc 35. May 22 FreeBSD Tinderbox [head tinderbox] failure on sparc64/sparc64 36. May 22 FreeBSD Tinderbox [head tinderbox] failure on sparc64/sparc64 37. May 23 FreeBSD Tinderbox [head tinderbox] failure on sparc64/sparc64 38. May 23 FreeBSD Tinderbox [head tinderbox] failure on sparc64/sparc64 39. May 22 FreeBSD Tinderbox [head tinderbox] failure on sparc64/sun4v 40. May 22 FreeBSD Tinderbox [head tinderbox] failure on sparc64/sun4v
41. May 23 FreeBSD Tinderbox [head tinderbox] failure on sparc64/sun4v 42. May 23 FreeBSD Tinderbox [head tinderbox] failure on sparc64/sun4v 43. May 23 FreeBSD Tinderbox [head tinderbox] failure on sparc64/sun4v 44. May 18 Ian FREISLICH Re: Anyone else seeing this (cvs wierdness)? 45. May 19 Garrett Cooper Re: Anyone else seeing this (cvs wierdness)? 46. May 20 Peter Wemm Re: Anyone else seeing this (cvs wierdness)? 47. May 23 phoemix@harmless.hu ata mode at startup 48. May 23 Alexey Shuvaev Re: ata mode at startup 49. May 23 Julian Stacey Re: ata mode at startup 50. May 23 Gary Jennejohn Re: ata mode at startup 51. May 23 =?ISO-8859-1?Q?S=F8ren_Sch Re: ata mode at startup 52. May 23 Julian Stacey Re: ata mode at startup 53. May 24 CZUCZY Gergely Re: ata mode at startup 54. May 24 Julian Stacey Re: ata mode at startup 55. May 21 =?ISO-8859-1?Q?S=F8ren_Sch Re: atadev->param.model problem or bug with Marvell 88SE6811 chip 56. May 22 Andrey Chernov Re: atadev->param.model problem or bug with Marvell 88SE6811 chip 57. May 20 Alex Keda Broken start scripts for wireless lan 58. May 20 Michael Proto Re: bsnmpd hrProcessorLoad results incorrect on FreeBSD 7 or 8? 59. May 20 Bjoern A. Zeeb Re: bsnmpd hrProcessorLoad results incorrect on FreeBSD 7 or 8? 60. May 21 Stanislav A Svirid Re: bsnmpd hrProcessorLoad results incorrect on FreeBSD 7 or 8?
61. May 19 Pyun YongHyeon Re: Call for testers : age(4), Attansic/Atheros L1 gigabit ethernet controller 62. May 19 Pyun YongHyeon Re: Cardbus GbE (Realtek 8169SBL) supported? 63. May 19 Pyun YongHyeon Re: Cardbus GbE (Realtek 8169SBL) supported? 64. May 19 Norikatsu Shigemura Re: Cardbus GbE (Realtek 8169SBL) supported? 65. May 20 Pyun YongHyeon Re: Cardbus GbE (Realtek 8169SBL) supported? 66. May 22 Norikatsu Shigemura Re: Cardbus GbE (Realtek 8169SBL) supported? 67. May 22 Pyun YongHyeon Re: Cardbus GbE (Realtek 8169SBL) supported? 68. May 22 Norikatsu Shigemura Re: Cardbus GbE (Realtek 8169SBL) supported? 69. May 22 Pyun YongHyeon Re: Cardbus GbE (Realtek 8169SBL) supported? 70. May 24 Wojciech A. Koszek ddb.4 which is a bit more up-to-date 71. May 24 Julian Elischer Re: ddb.4 which is a bit more up-to-date 72. May 20 Philip Paeps Re: development of framebuffer driver hi res console 73. May 20 Peter Jeremy Re: development of framebuffer driver hi res console 74. May 23 Eric Anholt Re: development of framebuffer driver hi res console 75. May 23 Wilkinson, Alex Re: development of framebuffer driver hi res console 76. May 23 Sam Fourman Jr. Re: development of framebuffer driver hi res console 77. May 23 ketracel Re: development of framebuffer driver hi res console 78. May 23 Eric Anholt Re: development of framebuffer driver hi res console 79. May 23 Jeremie Le Hen Re: development of framebuffer driver hi res console 80. May 23 Eric Anholt Re: development of framebuffer driver hi res console
81. May 23 Michel Talon Re: development of framebuffer driver hi res console 82. May 24 Robert Watson HEAD UP: non-MPSAFE network drivers to be disabled (was: 8.0 network stack MPsafet 83. May 24 Coleman Kane Re: HEAD UP: non-MPSAFE network drivers to be disabled (was: 8.0 network stack MPs 84. May 24 Robert Watson Re: HEAD UP: non-MPSAFE network drivers to be disabled (was: 8.0 network stack MPs 85. May 24 Robert Watson Re: HEAD UP: non-MPSAFE network drivers to be disabled (was: 8.0 network stack MPs 86. May 24 Julian Stacey Re: HEAD UP: non-MPSAFE network drivers to be disabled (was: 8.0 network stack MPs 87. May 22 John Birrell HEADSUP: ZFS users 88. May 21 =?ISO-8859-1?Q?S=F8ren_Sch Mail lossage... 89. May 19 sam possible bug in /usr/include/sys/proc.h 90. May 19 Bruce M. Simpson Re: possible bug in /usr/include/sys/proc.h 91. May 19 sam Re: possible bug in /usr/include/sys/proc.h 92. May 19 Garrett Cooper Re: possible bug in /usr/include/sys/proc.h 93. May 19 sam Re: possible bug in /usr/include/sys/proc.h 94. May 19 Kip Macy Re: possible bug in /usr/include/sys/proc.h 95. May 20 Vladimir Ermakov re: possible bug in /usr/include/sys/proc.h 96. May 19 Pietro Cerutti Problem since "wlan" came in: SIOCS80211: Device not configured 97. May 19 Rink Springer Re: Problem since "wlan" came in: SIOCS80211: Device not configured 98. May 19 Pietro Cerutti Re: Problem since "wlan" came in: SIOCS80211: Device not configured 99. May 19 Coleman Kane Re: Problem since "wlan" came in: SIOCS80211: Device not configured 100. May 19 Pietro Cerutti Re: Problem since "wlan" came in: SIOCS80211: Device not configured
101. May 19 Sam Leffler Re: Problem since "wlan" came in: SIOCS80211: Device not configured 102. May 19 Pietro Cerutti Re: Problem since "wlan" came in: SIOCS80211: Device not configured 103. May 19 Coleman Kane Re: Problem since "wlan" came in: SIOCS80211: Device not configured 104. May 19 Pietro Cerutti Re: Problem since "wlan" came in: SIOCS80211: Device not configured 105. May 19 Coleman Kane Re: Problem since "wlan" came in: SIOCS80211: Device not configured 106. May 19 Pietro Cerutti Re: Problem since "wlan" came in: SIOCS80211: Device not configured 107. May 19 Andrew Thompson Re: Problem since "wlan" came in: SIOCS80211: Device not configured 108. May 19 Pietro Cerutti Re: Problem since "wlan" came in: SIOCS80211: Device not configured 109. May 20 Andrew Thompson Re: Problem since "wlan" came in: SIOCS80211: Device not configured 110. May 20 Pietro Cerutti Re: Problem since "wlan" came in: SIOCS80211: Device not configured 111. May 23 =?iso-8859-1?Q?Miguel_V=E1 Problem with modem CMOTECH CCU-550 112. May 23 =?iso-8859-1?Q?Miguel_V=E1 Problem with modem CMOTECH CCU550 113. May 24 =?iso-8859-1?Q?Miguel_V=E1 Problem with modem CMOTECH CCU550 114. May 23 Okalany Daniel Squid 115. May 23 Doug Rabson Re: Squid 116. May 19 Lionel Garth Jones Top 5 Reasons to Attend USENIX '08 117. May 18 Jille Timmermans Unprivileged jail_attach 118. May 19 Bill Moran Re: Unprivileged jail_attach 119. May 19 Andrew Moran Updated php, and apache segfaults on SIGHUP 120. May 20 Kevin Downey Re: Updated php, and apache segfaults on SIGHUP
121. May 20 Barry Pederson Re: Updated php, and apache segfaults on SIGHUP 122. May 20 Randy Bush Re: Updated php, and apache segfaults on SIGHUP 123. May 20 Kevin Downey Re: Updated php, and apache segfaults on SIGHUP 124. May 20 Randy Bush Re: Updated php, and apache segfaults on SIGHUP 125. May 20 Randy Bush Re: Updated php, and apache segfaults on SIGHUP 126. May 20 Odhiambo Washington Re: Updated php, and apache segfaults on SIGHUP 127. May 20 Randy Bush Re: Updated php, and apache segfaults on SIGHUP 128. May 20 Claus Guttesen Re: Updated php, and apache segfaults on SIGHUP 129. May 20 Sean C. Farley Re: Updated php, and apache segfaults on SIGHUP 130. May 20 Andrew Moran Re: Updated php, and apache segfaults on SIGHUP 131. May 20 Andrew Moran Re: Updated php, and apache segfaults on SIGHUP 132. May 20 Sean C. Farley Re: Updated php, and apache segfaults on SIGHUP 133. May 20 Claus Guttesen Re: Updated php, and apache segfaults on SIGHUP
home | up | archive sorted by: subject | author | date | reverse date