freebsd-current  

Messages by Thread

• • Re: [-CURRENT tinderbox] failure on ia64/ia64 Ruslan Ermilov
  • [-CURRENT tinderbox] failure on ia64/ia64 Tinderbox
  • [-CURRENT tinderbox] failure on ia64/ia64 Tinderbox
  • [-CURRENT tinderbox] failure on ia64/ia64 Tinderbox
  • [-CURRENT tinderbox] failure on ia64/ia64 Tinderbox
  • [-CURRENT tinderbox] failure on ia64/ia64 Tinderbox
  • [-CURRENT tinderbox] failure on ia64/ia64 Tinderbox
  • [-CURRENT tinderbox] failure on ia64/ia64 Tinderbox
  • [-CURRENT tinderbox] failure on ia64/ia64 Tinderbox
  • [-CURRENT tinderbox] failure on ia64/ia64 Tinderbox
  • Re: [-CURRENT tinderbox] failure on ia64/ia64 Marcel Moolenaar
  • [-CURRENT tinderbox] failure on ia64/ia64 Tinderbox
  • [-CURRENT tinderbox] failure on ia64/ia64 Tinderbox
  • [-CURRENT tinderbox] failure on ia64/ia64 Tinderbox
  • [-CURRENT tinderbox] failure on ia64/ia64 Tinderbox
• Re: cvs commit: src/sys/contrib/dev/acpica - Imported sources Larry Rosenman
  • Re: cvs commit: src/sys/contrib/dev/acpica - Imported sources Larry Rosenman
  • Re: cvs commit: src/sys/contrib/dev/acpica - Imported sources Larry Rosenman
  • Re: cvs commit: src/sys/contrib/dev/acpica - Imported sources Nate Lawson
  • Re: cvs commit: src/sys/contrib/dev/acpica - Imported sources Larry Rosenman
  • Re: cvs commit: src/sys/contrib/dev/acpica - Imported sources Paul Richards
• Keyboard not responding on X Juan Rodriguez Hervella
• Re: BCM5703 GigE ifs on Supermicro X5DL8-GG m/b not detectedon5.1-BETA2 or 4.8 Doug White
  • Re: BCM5703 GigE ifs on Supermicro X5DL8-GG m/b not detectedon5.1-BETA2 or 4.8 (resolved) John Dhmioyrgos
• Re: gbde Performance - 35Mb/s vs 5.2 MB/s Guido van Rooij
  • Re: gbde Performance - 35Mb/s vs 5.2 MB/s Poul-Henning Kamp
  • Re: gbde Performance - 35Mb/s vs 5.2 MB/s Paul Richards
  • Re: gbde Performance - 35Mb/s vs 5.2 MB/s James Tanis
  • Re: gbde Performance - 35Mb/s vs 5.2 MB/s Doug Barton
  • Re: gbde Performance - 35Mb/s vs 5.2 MB/s John Stockdale
• [-CURRENT tinderbox] failure on i386/i386 Tinderbox
  • [-CURRENT tinderbox] failure on i386/i386 Tinderbox
  • [-CURRENT tinderbox] failure on i386/i386 Tinderbox
  • [-CURRENT tinderbox] failure on i386/i386 Tinderbox
  • [-CURRENT tinderbox] failure on i386/i386 Tinderbox
  • [-CURRENT tinderbox] failure on i386/i386 Tinderbox
  • [-CURRENT tinderbox] failure on i386/i386 Tinderbox
  • Re: [-CURRENT tinderbox] failure on i386/i386 Poul-Henning Kamp
  • [-CURRENT tinderbox] failure on i386/i386 Tinderbox
  • [-CURRENT tinderbox] failure on i386/i386 Tinderbox
  • [-CURRENT tinderbox] failure on i386/i386 Tinderbox
  • [-CURRENT tinderbox] failure on i386/i386 Tinderbox
  • [-CURRENT tinderbox] failure on i386/i386 Tinderbox
  • [-CURRENT tinderbox] failure on i386/i386 Tinderbox
  • [-CURRENT tinderbox] failure on i386/i386 Tinderbox
  • [-CURRENT tinderbox] failure on i386/i386 Tinderbox
  • Re: [-CURRENT tinderbox] failure on i386/i386 Maksim Yevmenkin
  • Re: [-CURRENT tinderbox] failure on i386/i386 Julian Elischer
  • [-CURRENT tinderbox] failure on i386/i386 Tinderbox
  • [-CURRENT tinderbox] failure on i386/i386 Tinderbox
  • [-CURRENT tinderbox] failure on i386/i386 Tinderbox
  • Re: [-CURRENT tinderbox] failure on i386/i386 Gordon Tetlow
  • [-CURRENT tinderbox] failure on i386/i386 Tinderbox
  • [-CURRENT tinderbox] failure on i386/i386 Tinderbox
  • [-CURRENT tinderbox] failure on i386/i386 Tinderbox
  • [-CURRENT tinderbox] failure on i386/i386 Tinderbox
  • [-CURRENT tinderbox] failure on i386/i386 Tinderbox
  • [-CURRENT tinderbox] failure on i386/i386 Tinderbox
  • [-CURRENT tinderbox] failure on i386/i386 Tinderbox
  • [-CURRENT tinderbox] failure on i386/i386 Tinderbox
  • Re: [-CURRENT tinderbox] failure on i386/i386 John
  • [-CURRENT tinderbox] failure on i386/i386 Tinderbox
  • [-CURRENT tinderbox] failure on i386/i386 Tinderbox
  • [-CURRENT tinderbox] failure on i386/i386 Tinderbox
  • Re: [-CURRENT tinderbox] failure on i386/i386 Peter Wemm
  • Re: [-CURRENT tinderbox] failure on i386/i386 Dag-Erling Smørgrav
  • Re: [-CURRENT tinderbox] failure on i386/i386 Poul-Henning Kamp
  • Re: [-CURRENT tinderbox] failure on i386/i386 Harti Brandt
  • Re: [-CURRENT tinderbox] failure on i386/i386 Mark Murray
  • Re: [-CURRENT tinderbox] failure on i386/i386 Peter Wemm
  • Re: [-CURRENT tinderbox] failure on i386/i386 Dag-Erling Smørgrav
  • Re: [-CURRENT tinderbox] failure on i386/i386 Peter Wemm
  • Re: [-CURRENT tinderbox] failure on i386/i386 Terry Lambert
  • [-CURRENT tinderbox] failure on i386/i386 Tinderbox
  • [-CURRENT tinderbox] failure on i386/i386 Tinderbox
  • [-CURRENT tinderbox] failure on i386/i386 Tinderbox
• Re: 5.1-BETA2 FAILURE on IBM A30p Thinkpad Jesse D. Guardiani
  • Re: 5.1-BETA2 FAILURE on IBM A30p Thinkpad Kevin Oberman
  • Re: 5.1-BETA2 FAILURE on IBM A30p Thinkpad Jesse D. Guardiani
• Re: passwd NIS+ YP compat mode TOMITA Yoshinori
  • Re: passwd NIS+ YP compat mode Thyer, Matthew
  • Re: passwd NIS+ YP compat mode Thyer, Matthew
  • Re: passwd NIS+ YP compat mode Daniel Eischen
  • RE: passwd NIS+ YP compat mode Thyer, Matthew
• Latest -Current ACPI issues... John Wilson
• panic: don't do that, in ugen(4) Juli Mallett
  • Re: panic: don't do that, in ugen(4) Jay Cornwall
• Re: ACPI crash Andrew Thomson
• LOR in vm_object/vm_kern Dennis Kristensen
  • Re: LOR in vm_object/vm_kern Kris Kennaway
• Re: Libthr stable enough for testing Craig Boston
  • Re: Libthr stable enough for testing Glenn Johnson
  • Re: Libthr stable enough for testing Mike Makonnen
  • Re: Libthr stable enough for testing Dan Nelson
  • Re: Libthr stable enough for testing Mike Makonnen
  • Re: Libthr stable enough for testing Glenn Johnson
  • Re: Libthr stable enough for testing Julian Elischer
  • Re: Libthr stable enough for testing Glenn Johnson
  • Re: Libthr stable enough for testing Julian Elischer
  • Re: Libthr stable enough for testing Glenn Johnson
  • Re: Libthr stable enough for testing Dag-Erling Smorgrav
  • Re: Libthr stable enough for testing Lars Eggert
  • Re: Libthr stable enough for testing Norikatsu Shigemura
  • Re: Libthr stable enough for testing Wesley Morgan
  • Re: Libthr stable enough for testing Mike Makonnen
  • Re: Libthr stable enough for testing James Tanis
  • Re: Libthr stable enough for testing Michael Edenfield
  • Re: Libthr stable enough for testing John Baldwin
  • Re: Libthr stable enough for testing James Tanis
  • Re: Libthr stable enough for testing Dan Nelson
  • Re: Libthr stable enough for testing Mike Makonnen
  • Re: Libthr stable enough for testing James Tanis
  • Re: Libthr stable enough for testing James Tanis
  • Re: Libthr stable enough for testing Julian Elischer
  • Re: Libthr stable enough for testing Daniel C. Sobral
  • Re: Libthr stable enough for testing Paul Richards
  • Re: Libthr stable enough for testing Mike Makonnen
  • Re: Libthr stable enough for testing Lars Eggert
  • Re: Libthr stable enough for testing Valentin Nechayev
  • Re: Libthr stable enough for testing Lars Eggert
• HEADSUP: acpi patches in the tree Nate Lawson
  • Re: HEADSUP: acpi patches in the tree Shin-ichi YOSHIMOTO
  • Re: HEADSUP: acpi patches in the tree Nate Lawson
  • Re: [acpi-jp 2267] Re: HEADSUP: acpi patches in the tree Nate Lawson
  • Re: [acpi-jp 2267] Re: HEADSUP: acpi patches in the tree Mark Santcroos
  • Re: HEADSUP: acpi patches in the tree Shin-ichi YOSHIMOTO
  • Re: [acpi-jp 2269] Re: HEADSUP: acpi patches in the tree Nate Lawson
  • Re: [acpi-jp 2269] Re: HEADSUP: acpi patches in the tree Shin-ichi YOSHIMOTO
  • Re: HEADSUP: acpi patches in the tree Anish Mistry
  • Re: [acpi-jp 2272] Re: HEADSUP: acpi patches in the tree Nate Lawson
  • Re: [acpi-jp 2267] Re: HEADSUP: acpi patches in the tree Takayoshi Kochi
  • Re: [acpi-jp 2267] Re: HEADSUP: acpi patches in the tree Takayoshi Kochi
  • Re: [acpi-jp 2267] Re: HEADSUP: acpi patches in the tree Nate Lawson
  • Re: [acpi-jp 2267] Re: HEADSUP: acpi patches in the tree Takayoshi Kochi
  • Re: [acpi-jp 2263] HEADSUP: acpi patches in the tree Andrea Campi
  • Re: [acpi-jp 2286] Re: HEADSUP: acpi patches in the tree Nate Lawson
• Re: FBSD 5.1b2 Inst. Results on Dell i8500 Mark Santcroos
  • Re: FBSD 5.1b2 Inst. Results on Dell i8500 Stijn Hoop
  • Re: FBSD 5.1b2 Inst. Results on Dell i8500 Stijn Hoop
• tinderbox currently slightly broken Dag-Erling Smorgrav
• [Fwd: cvs commit: www/en/releases/5.1R schedule.sgml] Scott Long
• Re: Timecounter "TSC" frequency 451024462 Dag-Erling Smorgrav
• make buildkernel currently broken in sys/pci/agp_intel.c Lukas Ertl
• Just give me a good smack... David Leimbach
• FreeBSD V5.0 and USB to Serial on Toshiba Satellite 1110 Richard Kaestner
  • Re: FreeBSD V5.0 and USB to Serial on Toshiba Satellite 1110 Bernd Walter
• Re: policy on GPL'd drivers? Wilko Bulte
  • Re: policy on GPL'd drivers? David Leimbach
  • Re: policy on GPL'd drivers? Alexander Kabaev
  • Re: policy on GPL'd drivers? Marcin Dalecki
  • Re: policy on GPL'd drivers? Terry Lambert
  • Re: policy on GPL'd drivers? David Leimbach
  • Re: policy on GPL'd drivers? David Leimbach
  • Re: policy on GPL'd drivers? Terry Lambert
  • Re: policy on GPL'd drivers? David O'Brien
  • Re: policy on GPL'd drivers? David Leimbach
  • Re: policy on GPL'd drivers? David Leimbach
  • Re: policy on GPL'd drivers? David Leimbach
  • Re: policy on GPL'd drivers? David Leimbach
  • Re: policy on GPL'd drivers? David Leimbach
  • Re: policy on GPL'd drivers? David Leimbach
  • Re: policy on GPL'd drivers? David Leimbach
  • Re: policy on GPL'd drivers? Chris BeHanna
  • Re: policy on GPL'd drivers? Dag-Erling Smorgrav
  • Re: policy on GPL'd drivers? Daniel O'Connor
  • Re: policy on GPL'd drivers? Q
  • Re: policy on GPL'd drivers? Scott Long
  • Re: policy on GPL'd drivers? Q
  • Re: policy on GPL'd drivers? Scott Long
  • Re: policy on GPL'd drivers? Michael Edenfield
  • Kernel module inconsistency was policy on GPL'd drivers? Q
  • Re: Kernel module inconsistency was policy on GPL'd drivers? Scott Long
  • Re: Kernel module inconsistency was policy on GPL'd drivers? Alexey Neyman
  • Re: Kernel module inconsistency was policy on GPL'd drivers? M. Warner Losh
  • Re: Kernel module inconsistency was policy on GPL'd drivers? Q
  • Re: policy on GPL'd drivers? Daniel O'Connor
  • Re: policy on GPL'd drivers? M. Warner Losh
  • Re: policy on GPL'd drivers? Daniel O'Connor
  • Re: policy on GPL'd drivers? Q
  • Re: policy on GPL'd drivers? Daniel O'Connor
  • Re: policy on GPL'd drivers? M. Warner Losh
  • Re: policy on GPL'd drivers? Daniel O'Connor
  • Re: policy on GPL'd drivers? M. Warner Losh
  • Re: policy on GPL'd drivers? Daniel O'Connor
  • Re: policy on GPL'd drivers? M. Warner Losh
  • Re: policy on GPL'd drivers? Marcin Dalecki
  • Re: policy on GPL'd drivers? Steve Kargl
  • Re: policy on GPL'd drivers? Scott Long
  • Re: policy on GPL'd drivers? Daniel O'Connor
  • Re: policy on GPL'd drivers? Steve Kargl
  • Re: policy on GPL'd drivers? Daniel O'Connor
  • Re: policy on GPL'd drivers? Marcin Dalecki
  • Re: policy on GPL'd drivers? Harti Brandt
  • Re: policy on GPL'd drivers? Marcin Dalecki
  • Re: policy on GPL'd drivers? Paul Richards
  • Re: policy on GPL'd drivers? dave
  • Re: policy on GPL'd drivers? Paul Richards
  • Re: policy on GPL'd drivers? dave
  • Re: policy on GPL'd drivers? Narvi
  • Re: policy on GPL'd drivers? Narvi

[Earlier messages] [Later messages]