2001/freebsd-alpha/20010610.freebsd-alpha
Messages: 164, new messages first
|
Last update: Mon Feb 13 14:13:43 2023
|
|
home | archive sorted by: subject | author | date | reverse date
1. Jun 9 Martijn Pronk Re: de network card not working on -current 2. Jun 9 Andrew Gallatin Re: ofehr@www.ofehr.com recipient unknown " Re: de network card not working on -current" 3. Jun 9 Matthew N. Dodd Re: de network card not working on -current 4. Jun 9 Matthew N. Dodd Re: de network card not working on -current 5. Jun 9 Martijn Pronk Re: de network card not working on -current 6. Jun 8 Vahe Khachikyan (ccc & libtool) II 7. Jun 8 Martijn Pronk Re: de network card not working on -current 8. Jun 8 Andrew Gallatin Re: de network card not working on -current 9. Jun 8 Martijn Pronk Re: de network card not working on -current 10. Jun 8 Andrew Gallatin Re: de network card not working on -current 11. Jun 8 Martijn Pronk de network card not working on -current 12. Jun 8 Andrew Gallatin Re: CFR: db_trace.c from NetBSD 13. Jun 8 Matthew Jacob Re: CFR: db_trace.c from NetBSD 14. Jun 8 Andrew Gallatin Re: CFR: db_trace.c from NetBSD 15. Jun 8 David O'Brien Re: CFR: db_trace.c from NetBSD 16. Jun 8 Andrew Gallatin Re: CFR: db_trace.c from NetBSD 17. Jun 8 Doug Rabson Re: Wow, have I got a stack for you! 18. Jun 8 Doug Rabson Re: 8 CPU SMP attempt 19. Jun 7 David O'Brien Re: CFR: db_trace.c from NetBSD 20. Jun 7 Matthew Jacob freebsd/alphaincluded
21. Jun 7 Alexander Langer Re: alpha/27930: NE2000 not supported on FreeBSD Alpha 4.x; fix included 22. Jun 7 Matthew Jacob Re: alpha/27930: NE2000 not supported on FreeBSD Alpha 4.x; fix included 23. Jun 7 Alexander Langer Re: alpha/27930: NE2000 not supported on FreeBSD Alpha 4.x; fix included 24. Jun 7 Andrew Gallatin Re: Wow, have I got a stack for you! 25. Jun 7 Andrew Gallatin RE: Wow, have I got a stack for you! 26. Jun 7 John Baldwin RE: Wow, have I got a stack for you! 27. Jun 7 John Baldwin Re: Possible VM patch.. 28. Jun 7 Andrew Gallatin RE: CFR: db_trace.c from NetBSD 29. Jun 7 John Baldwin RE: CFR: db_trace.c from NetBSD 30. Jun 7 Wilko Bulte Re: 8 CPU SMP attempt 31. Jun 7 Matthew Jacob Re: 8 CPU SMP attempt 32. Jun 7 Alfred Perlstein Re: Wow, have I got a stack for you! 33. Jun 7 Andrew Gallatin CFR: db_trace.c from NetBSD 34. Jun 7 Andrew Gallatin Wow, have I got a stack for you! 35. Jun 7 Andrew Gallatin Re: 8 CPU SMP attempt 36. Jun 7 Wilko Bulte Re: 8 CPU SMP attempt 37. Jun 7 Andrew Gallatin Re: Possible VM patch.. 38. Jun 7 David O'Brien Re: ccc 39. Jun 7 <obrien@FreeBSD.org> Re: alpha/27930: NE2000 not supported on FreeBSD Alpha 4.x; fix included 40. Jun 7 David O'Brien Re: ccc
41. Jun 7 Chris Casey Re: ccc 42. Jun 7 Andrew Gallatin Re: ccc 43. Jun 7 David O'Brien Re: ccc 44. Jun 7 David O'Brien Re: ccc 45. Jun 7 David O'Brien Re: ccc 46. Jun 7 David O'Brien Re: ccc 47. Jun 7 Matthew Jacob Re: alpha/27930: NE2000 not supported on FreeBSD Alpha 4.x; fix included 48. Jun 7 Matthew Jacob Re: alpha/27930: NE2000 not supported on FreeBSD Alpha 4.x; fix included 49. Jun 7 Yoriaki FUJIMORI Re: ccc 50. Jun 7 Chris Casey Re: ccc 51. Jun 7 Andrew Gallatin Re: alpha compile problem - L0phtcrack 1.5 52. Jun 7 Andrew Gallatin Re: ccc 53. Jun 7 Reed, Mike alpha compile problem - L0phtcrack 1.5 54. Jun 7 Chris Casey Re: ccc 55. Jun 7 Chris Casey Re: ccc 56. Jun 7 Andrew Gallatin Re: 8 CPU SMP attempt 57. Jun 7 thomas.pornin@ens.fr alpha/27933: Time jitter under load on FreeBSD 4.3 alpha 58. Jun 7 thomas.pornin@ens.fr Time jitter under load on FreeBSD 4.3 alpha 59. Jun 7 thomas.pornin@ens.fr alpha/27930: NE2000 not supported on FreeBSD Alpha 4.x; fix included 60. Jun 7 thomas.pornin@ens.fr NE2000 not supported on FreeBSD Alpha 4.x; fix included
61. Jun 7 Wilko Bulte 8 CPU SMP attempt 62. Jun 6 Greg Lehey Re: DEV_T size mismatch 63. Jun 6 Andrew Gallatin Re: Possible VM patch.. 64. Jun 6 Andrew Gallatin Re: Possible VM patch.. 65. Jun 6 John Baldwin Re: Possible VM patch.. 66. Jun 6 Mike Smith Re: -current kernel still considered dangerous 67. Jun 6 Andrew Gallatin Re: Possible VM patch.. 68. Jun 6 John Baldwin Re: -current kernel still considered dangerous 69. Jun 6 Alfred Perlstein Re: -current kernel still considered dangerous 70. Jun 6 John Baldwin Possible VM patch.. 71. Jun 6 David O'Brien Re: ccc 72. Jun 6 David O'Brien Re: ccc 73. Jun 6 Chris Casey Re: ccc 74. Jun 6 Andrew Gallatin Re: ccc 75. Jun 6 Chris Casey Re: ccc 76. Jun 6 Wilko Bulte Re: how does the 4.3 ISO work for you? 77. Jun 6 David O'Brien Re: how does the 4.3 ISO work for you? 78. Jun 6 Jordan Hubbard Re: how does the 4.3 ISO work for you? 79. Jun 6 David O'Brien Re: how does the 4.3 ISO work for you? 80. Jun 6 John Baldwin Re: -current kernel still considered dangerous
81. Jun 6 John Baldwin Re: -current kernel still considered dangerous 82. Jun 6 David O'Brien Re: ccc 83. Jun 6 Jordan Hubbard Re: how does the 4.3 ISO work for you? 84. Jun 6 Joseph Scott Re: how does the 4.3 ISO work for you? 85. Jun 6 Andrew Gallatin Re: how does the 4.3 ISO work for you? 86. Jun 6 Andrew Gallatin Re: how does the 4.3 ISO work for you? 87. Jun 6 Riccardo.Veraldi@fi.infn.i Re: how does the 4.3 ISO work for you? 88. Jun 6 Riccardo.Veraldi@fi.infn.i Re: how does the 4.3 ISO work for you? 89. Jun 6 Mark Nipper Re: how does the 4.3 ISO work for you? 90. Jun 6 Chris Casey Re: ccc 91. Jun 6 Matthew Jacob Re: -current kernel still considered dangerous 92. Jun 6 David O'Brien -Alpha how does the 4.3 ISO work for you? 93. Jun 6 Andrew Gallatin Re: -current kernel still considered dangerous 94. Jun 6 Andrew Gallatin Re: -current kernel still considered dangerous 95. Jun 6 David O'Brien Re: -current kernel still considered dangerous 96. Jun 6 Matthew Jacob Re: -current kernel still considered dangerous 97. Jun 6 David O'Brien Re: -current kernel still considered dangerous 98. Jun 6 Andrew Gallatin Re: -current kernel still considered dangerous 99. Jun 6 Riccardo.Veraldi@fi.infn.i a little bit of support on XFree86 pls... 100. Jun 6 Riccardo.Veraldi@fi.infn.i XFree 3.3.6 PROBLEM
101. Jun 5 Wes Kurdziolek Re: XFree86 (3.3.6_9) install failed ? 102. Jun 5 David O'Brien Re: -current kernel still considered dangerous 103. Jun 5 David O'Brien Re: -current kernel still considered dangerous 104. Jun 5 Andrew Gallatin Re: -current kernel still considered dangerous 105. Jun 5 David O'Brien Re: -current kernel still considered dangerous 106. Jun 5 Andrew Gallatin Re: -current kernel still considered dangerous 107. Jun 5 John Baldwin Re: -current kernel still considered dangerous 108. Jun 5 David O'Brien Re: -current kernel still considered dangerous 109. Jun 5 David O'Brien Re: ccc 110. Jun 5 Andrew Gallatin Re: ccc 111. Jun 5 Chris Casey Re: ccc 112. Jun 5 Christian Weisgerber Re: 3Com 905-TX 113. Jun 5 John Baldwin RE: alpha kernel panic... 114. Jun 5 Matthew Jacob alpha kernel panic... 115. Jun 5 David O'Brien Re: -current kernel still considered dangerous 116. Jun 5 John Baldwin Re: -current kernel still considered dangerous 117. Jun 5 Riccardo.Veraldi@fi.infn.i XFree86 (3.3.6_9) install failed ? 118. Jun 5 Andrew Gallatin Re: 3Com 905-TX (was: Re: SCSI devices settling and illegal request) 119. Jun 5 Andrew Gallatin Re: 3Com 905-TX (was: Re: SCSI devices settling and illegal request) 120. Jun 5 Christian Weisgerber 3Com 905-TX (was: Re: SCSI devices settling and illegal request)
121. Jun 5 Riccardo.Veraldi@fi.infn.i Matrox Millennium II 122. Jun 5 Koster, K.J. Observation (was: SCSI devices settling and illegal request) 123. Jun 4 Wilko Bulte Re: SCSI devices settling and illegal request 124. Jun 4 Matthew Jacob Re: SCSI devices settling and illegal request 125. Jun 4 Mike Smith Re: SCSI devices settling and illegal request 126. Jun 4 John Polstra Re: SCSI devices settling and illegal request 127. Jun 4 Mike Smith Re: SCSI devices settling and illegal request 128. Jun 4 David O'Brien Re: -current kernel still considered dangerous 129. Jun 4 Andrew Gallatin Re: SCSI devices settling and illegal request 130. Jun 4 John Polstra Re: SCSI devices settling and illegal request 131. Jun 4 Andrew Gallatin Re: SCSI devices settling and illegal request 132. Jun 4 Andrew Gallatin Re: SCSI devices settling and illegal request 133. Jun 4 Mark Nipper Re: SCSI devices settling and illegal request 134. Jun 4 Mark Nipper Re: SCSI devices settling and illegal request 135. Jun 4 Andrew Gallatin Re: SCSI devices settling and illegal request 136. Jun 4 Matthew Jacob Re: SCSI devices settling and illegal request 137. Jun 4 Mark Nipper Re: SCSI devices settling and illegal request 138. Jun 4 Andrew Gallatin Re: SCSI devices settling and illegal request 139. Jun 4 Matthew Jacob Re: SCSI devices settling and illegal request 140. Jun 4 Andrew Gallatin Re: SCSI devices settling and illegal request
141. Jun 4 Matthew Jacob Re: SCSI devices settling and illegal request 142. Jun 4 Matthew Jacob Re: SCSI devices settling and illegal request 143. Jun 4 Andrew Gallatin Re: SCSI devices settling and illegal request 144. Jun 4 Mark Nipper Re: SCSI devices settling and illegal request 145. Jun 4 Andrew Gallatin Re: SCSI devices settling and illegal request 146. Jun 4 Mark Nipper Re: SCSI devices settling and illegal request 147. Jun 4 Andrew Gallatin Re: SCSI devices settling and illegal request 148. Jun 4 Mark Nipper Re: SCSI devices settling and illegal request 149. Jun 4 Andrew Gallatin Re: SCSI devices settling and illegal request 150. Jun 4 Mark Nipper SCSI devices settling and illegal request 151. Jun 4 John Baldwin RE: -current kernel still considered dangerous 152. Jun 4 Andrew Gallatin interrupt latency 153. Jun 4 David O'Brien Re: make.conf 154. Jun 4 John Polstra Re: make.conf 155. Jun 4 Yoriaki FUJIMORI Does Tru64 5.1 run Linux elf? 156. Jun 4 Wilko Bulte Re: make.conf 157. Jun 4 David O'Brien -Alpha Re: make.conf 158. Jun 4 Andrew Gallatin Re: make.conf 159. Jun 4 Riccardo.Veraldi@fi.infn.i make.conf 160. Jun 3 <mjacob@FreeBSD.org> Re: alpha/27866: Fast interrupts handled via interrupt threads
161. Jun 3 Peter Jeremy Re: Abyssmal interrupt latency with -current 162. Jun 3 Matthew Jacob Re: alpha/27866: Fast interrupts handled via interrupt threads 163. Jun 3 peter.jeremy@alcatel.com.a alpha/27866: Fast interrupts handled via interrupt threads 164. Jun 3 Mike Smith Re: PCI Interrupt Routing Broken on my Miata
home | archive sorted by: subject | author | date | reverse date