freebsd-current

• Thread Index

• [head tinderbox] failure on amd64/amd64
  • From: FreeBSD Tinderbox
• FreeBSD 7.0 will use GCC 4.1 or 4.2?
  • From: Abdullah Al-Marrie
• Re: Can't link kernel after recent libalias commits?
  • From: Robert Watson
• Re: Can't link kernel after recent libalias commits?
  • From: Max Laier
• Re: 7.0-CURRENT Kernel debug howto
  • From: Joseph Koshy
• Re: Can't link kernel after recent libalias commits?
  • From: Gleb Smirnoff
• 7.0-CURRENT Kernel debug howto
  • From: Abdullah Al-Marrie
• panic on pmap_remove_pages with INVARIANTS
  • From: Norikatsu Shigemura
• Re: Can't link kernel after recent libalias commits?
  • From: Paolo Pisati
• Re: Can't link kernel after recent libalias commits?
  • From: Max Laier
• Re: Can't link kernel after recent libalias commits?
  • From: Paolo Pisati
• Re: Can't link kernel after recent libalias commits?
  • From: David Wolfskill
• Re: Can't link kernel after recent libalias commits?
  • From: Paolo Pisati
• Can't link kernel after recent libalias commits?
  • From: David Wolfskill
• Re: [PATCH] Typo fixes: preceed -> precede
  • From: Yar Tikhiy
• Re: [PATCH] Typo fixes: preceed -> precede
  • From: Simon L. Nielsen
• Re: [PATCH] Typo fixes: preceed -> precede
  • From: Andre Guibert de Bruet
• [head tinderbox] failure on powerpc/powerpc
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on ia64/ia64
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on i386/pc98
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on i386/i386
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on amd64/amd64
  • From: FreeBSD Tinderbox
• Re: [PATCH] Typo fixes: preceed -> precede
  • From: Yar Tikhiy
• Re: A stuck system
  • From: Randall Stewart
• Re: Enabling MSI on the Asus Vintage AH-1
  • From: Pyun YongHyeon
• Re: Enabling MSI on the Asus Vintage AH-1
  • From: Bruce M. Simpson
• Re: ddb(4) spoils kernel stack in CURRENT?
  • From: John Baldwin
• Re: A stuck system
  • From: John Baldwin
• Re: how to invoke a network configure dialog in install.cfg
  • From: John Baldwin
• Re: Enabling MSI on the Asus Vintage AH-1
  • From: John Baldwin
• re(4) timing out?
  • From: Rene Ladan
• Re: sysv_ipc.c broken in v1.30 (was Re: sysvshm appearse broken in -current)
  • From: Robert Watson
• Re: sysv_ipc.c broken in v1.30 (was Re: sysvshm appearse broken in -current)
  • From: Andrey Chernov
• Re: msdosfs and cd9660: stat(2) returns garbled birthtime
  • From: Oliver Fromme
• [PATCH] Typo fixes: preceed -> precede
  • From: Andre Guibert de Bruet
• Re: Lots of READ_BIG errors on my new cd drive
  • From: Doug Barton
• Re: Lots of READ_BIG errors on my new cd drive
  • From: Chuck Swiger
• Re: Fwd: Re: pf: BAD state happens often with portsnap fetch update
  • From: Chuck Swiger
• Lots of READ_BIG errors on my new cd drive
  • From: Doug Barton
• Re: Fwd: Re: pf: BAD state happens often with portsnap fetch update
  • From: Colin Percival
• Re: Fwd: Re: pf: BAD state happens often with portsnap fetch update
  • From: Chuck Swiger
• sys/dev/usb/usbdi_util.h not protected from multiple includes ?
  • From: Luigi Rizzo
• Re: FreeBSD 7.0 i386 via cvsup failed in buildkernel
  • From: René Ladan
• Re: FreeBSD 7.0 i386 via cvsup failed in buildkernel
  • From: Doug Barton
• Re: FreeBSD 7.0 i386 via cvsup failed in buildkernel
  • From: Abdullah Al-Marrie
• Re: msdosfs and cd9660: stat(2) returns garbled birthtime
  • From: Ulrich Spoerlein
• Re: msdosfs and cd9660: stat(2) returns garbled birthtime
  • From: Oliver Fromme
• FreeBSD 7.0 i386 via cvsup failed in buildkernel
  • From: Abdullah Al-Marrie
• msdosfs and cd9660: stat(2) returns garbled birthtime
  • From: Ulrich Spoerlein
• Re: Fwd: Re: pf: BAD state happens often with portsnap fetch update
  • From: Mike Silbersack
• Re: Fwd: Re: pf: BAD state happens often with portsnap fetch update
  • From: Adam McDougall
• Re: Fwd: Re: pf: BAD state happens often with portsnap fetch update
  • From: Colin Percival
• Re: Fwd: Re: pf: BAD state happens often with portsnap fetch update
  • From: Mike Silbersack
• Re: Fwd: Re: pf: BAD state happens often with portsnap fetch update
  • From: Max Laier
• Re: Enabling MSI on the Asus Vintage AH-1
  • From: Pyun YongHyeon
• Re: Enabling MSI on the Asus Vintage AH-1
  • From: Scott Long
• Re: Enabling MSI on the Asus Vintage AH-1
  • From: Pyun YongHyeon
• Re: Fwd: Re: pf: BAD state happens often with portsnap fetch update
  • From: Colin Percival
• Re: [head tinderbox] failure on sparc64/sun4v
  • From: Kip Macy
• panic in cache_zap
  • From: Eric Anderson
• Re: [head tinderbox] failure on sparc64/sun4v
  • From: Gary Palmer
• [head tinderbox] failure on sparc64/sun4v
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on sparc64/sun4v
  • From: FreeBSD Tinderbox
• Re: Acer Aspire 5102 WLMi with Turion 64 X2 dual-core TL-50 1.6 GHz on FreeBSD 6.2 ACPI problems
  • From: M. Warner Losh
• [head tinderbox] failure on sparc64/sun4v
  • From: FreeBSD Tinderbox
• Re: vge(4) bad checksum
  • From: Andrew Pantyukhin
• [head tinderbox] failure on sparc64/sun4v
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on sparc64/sun4v
  • From: FreeBSD Tinderbox
• Re: vge(4) bad checksum
  • From: Kris Kennaway
• Enabling MSI on the Asus Vintage AH-1
  • From: Bruce M. Simpson
• Re: double trap on reboot (kernel trap 0 with interrupts disabled)
  • From: Bjoern A. Zeeb
• double trap on reboot (kernel trap 0 with interrupts disabled)
  • From: Bjoern A. Zeeb
• Re: UFS_GJOURNAL and ufs.ko
  • From: Coleman Kane
• Re: settimeofday function taking 24 - 30 minutes to complete
  • From: Poul-Henning Kamp
• [head tinderbox] failure on i386/pc98
  • From: FreeBSD Tinderbox
• Re: settimeofday function taking 24 - 30 minutes to complete
  • From: Scot Hetzel
• Re: settimeofday function taking 24 - 30 minutes to complete
  • From: Scot Hetzel
• Re: sysv_ipc.c broken in v1.30 (was Re: sysvshm appearse broken in -current)
  • From: Robert Watson
• Re: Laptop display stays on with lid closed
  • From: Andre Guibert de Bruet
• Re: vge(4) bad checksum
  • From: Ruslan Ermilov
• [head tinderbox] failure on i386/pc98
  • From: FreeBSD Tinderbox
• Re: sysv_ipc.c broken in v1.30 (was Re: sysvshm appearse broken in -current)
  • From: Andrey Chernov
• [head tinderbox] failure on i386/i386
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on amd64/amd64
  • From: FreeBSD Tinderbox
• Re: UFS_GJOURNAL and ufs.ko
  • From: Yar Tikhiy
• Re: bigdisk and scsi_da
  • From: mjacob
• building kernel with lang/gcc41 (or lang/gcc42)
  • From: Yuriy Tsibizov
• Re: ddb(4) spoils kernel stack in CURRENT?
  • From: Kip Macy
• Re: settimeofday function taking 24 - 30 minutes to complete
  • From: Scot Hetzel
• Re: ddb(4) spoils kernel stack in CURRENT?
  • From: Kip Macy
• Re: Acer Aspire 5102 WLMi with Turion 64 X2 dual-core TL-50 1.6 GHz on FreeBSD 6.2 ACPI problems
  • From: Abdullah Al-Marrie
• Re: [head tinderbox] failure on i386/pc98
  • From: Alexander Leidinger
• [head tinderbox] failure on i386/pc98
  • From: FreeBSD Tinderbox
• Re: Laptop display stays on with lid closed
  • From: Anton Karpov
• [head tinderbox] failure on amd64/amd64
  • From: FreeBSD Tinderbox
• Re: UFS_GJOURNAL and ufs.ko
  • From: Yar Tikhiy
• [head tinderbox] failure on i386/i386
  • From: FreeBSD Tinderbox
• Re: settimeofday function taking 24 - 30 minutes to complete
  • From: Yuri Pankov
• [head tinderbox] failure on i386/pc98
  • From: FreeBSD Tinderbox
• Polling bug (was Re: packets duplicated *massively* on transmit.)
  • From: Ian FREISLICH
• Re: packets duplicated *massively* on transmit.
  • From: Ian FREISLICH
• Re: Laptop display stays on with lid closed
  • From: Adam McDougall
• [head tinderbox] failure on amd64/amd64
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on i386/pc98
  • From: FreeBSD Tinderbox
• Re: Laptop display stays on with lid closed
  • From: Daan Vreeken [PA4DAN]
• [head tinderbox] failure on ia64/ia64
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on sparc64/sun4v
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on sparc64/sparc64
  • From: FreeBSD Tinderbox
• Re: settimeofday function taking 24 - 30 minutes to complete
  • From: Garrett Cooper
• [head tinderbox] failure on sparc64/sun4v
  • From: FreeBSD Tinderbox
• Re: A stuck system
  • From: Andre Guibert de Bruet
• [head tinderbox] failure on amd64/amd64
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on i386/i386
  • From: FreeBSD Tinderbox
• Re: settimeofday function taking 24 - 30 minutes to complete
  • From: M. Warner Losh
• [head tinderbox] failure on i386/i386
  • From: FreeBSD Tinderbox
• kernel trap 0 on amd64 SMP
  • From: David Xu
• Re: ddb(4) spoils kernel stack in CURRENT?
  • From: Dmitry Pryanishnikov
• Re: Laptop display stays on with lid closed
  • From: Andrew Pantyukhin
• Re: bigdisk and scsi_da
  • From: Rong-en Fan
• Re: Can the mpt0: <LSILogic 1030 Ultra4 Adapter> be rebooted on current.
  • From: eculp@xxxxxxxxxxxxxx
• Re: bigdisk and scsi_da
  • From: Scott Long
• Re: bigdisk and scsi_da
  • From: Rong-en Fan
• Re: Laptop display stays on with lid closed
  • From: Anton Karpov
• Re: Can the mpt0: <LSILogic 1030 Ultra4 Adapter> be rebooted on current.
  • From: Scott Long
• Re: A stuck system
  • From: Randall Stewart
• Can the mpt0: <LSILogic 1030 Ultra4 Adapter> be rebooted on current.
  • From: eculp@xxxxxxxxxxxxxx
• Re: A stuck system
  • From: Andre Guibert de Bruet
• Re: bigdisk and scsi_da
  • From: Scott Long
• Re: bigdisk and scsi_da
  • From: Rong-en Fan
• Re: bigdisk and scsi_da
  • From: Scott Long
• [head tinderbox] failure on sparc64/sun4v
  • From: FreeBSD Tinderbox
• Re: ddb(4) spoils kernel stack in CURRENT?
  • From: Dmitry Pryanishnikov
• Re: ddb(4) spoils kernel stack in CURRENT?
  • From: Kostik Belousov
• Re: A stuck system
  • From: Randall Stewart
• Re: bigdisk and scsi_da
  • From: Rong-en Fan
• Re: A stuck system
  • From: Luigi Rizzo
• Re: A stuck system
  • From: Randall Stewart
• A stuck system
  • From: Randall Stewart
• Re: ddb(4) spoils kernel stack in CURRENT?
  • From: Dmitry Pryanishnikov
• packets duplicated *massively* on transmit.
  • From: Ian FREISLICH
• Laptop display stays on with lid closed
  • From: Andrew Pantyukhin
• [head tinderbox] failure on sparc64/sun4v
  • From: FreeBSD Tinderbox
• Re: settimeofday function taking 24 - 30 minutes to complete
  • From: Garrett Cooper
• Re: settimeofday function taking 24 - 30 minutes to complete
  • From: Scot Hetzel
• Re: settimeofday function taking 24 - 30 minutes to complete
  • From: Mark Kirkwood
• Re: settimeofday function taking 24 - 30 minutes to complete
  • From: Mark Kirkwood
• Re: settimeofday function taking 24 - 30 minutes to complete
  • From: Scot Hetzel
• Re: settimeofday function taking 24 - 30 minutes to complete
  • From: Garrett Cooper
• Re: settimeofday function taking 24 - 30 minutes to complete
  • From: Devon H. O'Dell
• Re: settimeofday function taking 24 - 30 minutes to complete
  • From: Garrett Cooper
• how to invoke a network configure dialog in install.cfg
  • From: shava knightmare
• Re: settimeofday function taking 24 - 30 minutes to complete
  • From: Garrett Cooper
• Re: settimeofday function taking 24 - 30 minutes to complete
  • From: Garrett Cooper
• ddb(4) spoils kernel stack in CURRENT?
  • From: Dmitry Pryanishnikov
• settimeofday function taking 24 - 30 minutes to complete
  • From: Scot Hetzel
• Re: bigdisk and scsi_da
  • From: Matthew Jacob
• Re: bigdisk and scsi_da
  • From: Scott Long
• bigdisk and scsi_da
  • From: Rong-en Fan
• Re: UFS_GJOURNAL and ufs.ko
  • From: Coleman Kane
• Re: cbb hangs during suspend if ath card active
  • From: Stepan Zastupov
• FreeBSD/amd64 CURRENT@12/18/06: reproducible hang/panic
  • From: Paolo Pisati
• /etc/rc.d/mdconfig2
  • From: Vincent Blondel
• [PATCH] Remove watchdog warnings from ral(4)
  • From: Bruce M Simpson
• Re: UFS_GJOURNAL and ufs.ko
  • From: Max Laier
• Re: UFS_GJOURNAL and ufs.ko
  • From: Brooks Davis
• UFS_GJOURNAL and ufs.ko
  • From: Coleman Kane
• Call for testers: aac(4) driver update from vendor
  • From: LI Xin
• Re: vge(4) bad checksum
  • From: gnn
• Re: cbb hangs during suspend if ath card active
  • From: Sam Leffler
• Re: cbb hangs during suspend if ath card active
  • From: Stepan Zastupov
• [head tinderbox] failure on amd64/amd64
  • From: FreeBSD Tinderbox
• Re: Am I an Idiot?
  • From: Doug Barton
• Re: Am I an Idiot?
  • From: Astrodog
• Re: cbb hangs during suspend if ath card active
  • From: Nate Lawson
• Re: Am I an Idiot?
  • From: Doug Barton
• Re: vge(4) bad checksum
  • From: Andrew Pantyukhin
• Re: vge(4) bad checksum
  • From: Kris Kennaway
• vge(4) bad checksum
  • From: Andrew Pantyukhin
• Re: Am I an Idiot?
  • From: Beech Rintoul
• [head tinderbox] failure on amd64/amd64
  • From: FreeBSD Tinderbox
• Re: Let's use gcc-4.2, not 4.1 -- OpenMP
  • From: Stefan Ehmann
• Re: Am I an Idiot?
  • From: Astrodog
• Re: sysv_ipc.c broken in v1.30 (was Re: sysvshm appearse broken in -current)
  • From: Andrey Chernov
• Re: Let's use gcc-4.2, not 4.1 -- OpenMP
  • From: Ulrich Spoerlein
• [head tinderbox] failure on amd64/amd64
  • From: FreeBSD Tinderbox
• Re: Am I an Idiot?
  • From: Doug Barton
• Re: cbb hangs during suspend if ath card active
  • From: Nate Lawson
• Re: Am I an Idiot?
  • From: Per olof Ljungmark
• Re: Fatal trap at booting after last kmacy@ changes
  • From: Andrey Chernov
• Re: Fatal trap at booting after last kmacy@ changes
  • From: Yuriy Tsibizov
• Easy kernel panic as ordinary user with msdosfs
  • From: Alexander Leidinger
• Re: Let's use gcc-4.2, not 4.1 -- OpenMP
  • From: Stefan Ehmann
• Re: sysv_ipc.c broken in v1.30 (was Re: sysvshm appearse broken in -current)
  • From: Andrey Chernov
• Fatal trap at booting after last kmacy@ changes
  • From: Andrey Chernov
• Re: sysv_ipc.c broken in v1.30 (was Re: sysvshm appearse broken in -current)
  • From: Robert Watson
• Re: sysv_ipc.c broken in v1.30 (was Re: sysvshm appearse broken in -current)
  • From: Andrey Chernov
• Re: CURRENT freezes on Laitude D520
  • From: Robert Watson
• Re: sysv_ipc.c broken in v1.30 (was Re: sysvshm appearse broken in -current)
  • From: Robert Watson
• Re: CURRENT freezes on Laitude D520
  • From: Tai-hwa Liang
• Re: sysv_ipc.c broken in v1.30 (was Re: sysvshm appearse broken in -current)
  • From: Andrey Chernov
• Re: sysv_ipc.c broken in v1.30 (was Re: sysvshm appearse broken in -current)
  • From: Robert Watson
• Re: sysv_ipc.c broken in v1.30 (was Re: sysvshm appearse broken in -current)
  • From: Andrey Chernov
• Re: sysv_ipc.c broken in v1.30 (was Re: sysvshm appearse broken in -current)
  • From: Andrey Chernov
• Re: sysv_ipc.c broken in v1.30 (was Re: sysvshm appearse broken in -current)
  • From: Robert Watson
• Re: sysv_ipc.c broken in v1.30 (was Re: sysvshm appearse broken in -current)
  • From: Robert Watson
• sysv_ipc.c broken in v1.30 (was Re: sysvshm appearse broken in -current)
  • From: Andrey Chernov
• [head tinderbox] failure on i386/i386
  • From: FreeBSD Tinderbox
• Re: Socket problems with latest -current
  • From: Bruce A. Mah
• [head tinderbox] failure on sparc64/sun4v
  • From: FreeBSD Tinderbox
• sysvshm appearse broken in -current
  • From: Andrey Chernov
• [head tinderbox] failure on sparc64/sparc64
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on ia64/ia64
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on amd64/amd64
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on sparc64/sun4v
  • From: FreeBSD Tinderbox
• Re: Socket problems with latest -current
  • From: Doug Barton
• [head tinderbox] failure on sparc64/sparc64
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on ia64/ia64
  • From: FreeBSD Tinderbox
• Re: Socket problems with latest -current
  • From: Bruce A. Mah
• [head tinderbox] failure on amd64/amd64
  • From: FreeBSD Tinderbox
• WD_PASSIVE kernel based tickling of the watchdog - request for ideas
  • From: Nick Hibma
• [head tinderbox] failure on sparc64/sun4v
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on sparc64/sparc64
  • From: FreeBSD Tinderbox
• two uarts pccard
  • From: rmgls
• [head tinderbox] failure on ia64/ia64
  • From: FreeBSD Tinderbox
• Re: Let's use gcc-4.2, not 4.1 -- OpenMP
  • From: David O'Brien
• Re: Let's use gcc-4.2, not 4.1 -- OpenMP
  • From: David O'Brien
• Re: kern/58953
  • From: Marcel Moolenaar
• Re: Socket problems with latest -current
  • From: Bruce A. Mah
• Re: vfs_hash_get panic
  • From: Rong-en Fan
• Re: Socket problems with latest -current
  • From: Doug Barton
• Re: kern/58953
  • From: Milan Obuch
• Re: kern/58953
  • From: Matthew Jacob
• [head tinderbox] failure on amd64/amd64
  • From: FreeBSD Tinderbox
• vfs_hash_get panic
  • From: Rong-en Fan
• Re: kern/58953
  • From: Wilko Bulte
• Re: kern/58953
  • From: LI Xin
• Re: Let's use gcc-4.2, not 4.1 -- OpenMP
  • From: Stefan Ehmann
• Re: Let's use gcc-4.2, not 4.1 -- OpenMP
  • From: Poul-Henning Kamp
• [head tinderbox] failure on sparc64/sun4v
  • From: FreeBSD Tinderbox
• Re: kqueue LOR
  • From: Attilio Rao
• kern/58953
  • From: Milan Obuch
• [head tinderbox] failure on sparc64/sparc64
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on ia64/ia64
  • From: FreeBSD Tinderbox
• Re: Socket problems with latest -current
  • From: Bruce A. Mah
• diskless stations and 7-current
  • From: Boris Samorodov
• Re: Kernel Virtual Machine
  • From: Bruce M. Simpson
• Re: Let's use gcc-4.2, not 4.1 -- OpenMP
  • From: Stefan Ehmann
• [head tinderbox] failure on amd64/amd64
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on sparc64/sun4v
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on sparc64/sparc64
  • From: FreeBSD Tinderbox
• Re: Let's use gcc-4.2, not 4.1 -- OpenMP
  • From: Luigi Rizzo
• Re: Let's use gcc-4.2, not 4.1 -- OpenMP
  • From: Poul-Henning Kamp
• Re: Let's use gcc-4.2, not 4.1 -- OpenMP
  • From: Ricardo Nabinger Sanchez
• Re: Let's use gcc-4.2, not 4.1 -- OpenMP
  • From: Stefan Ehmann
• Kernel Virtual Machine
  • From: Danny Braniss
• Re: Let's use gcc-4.2, not 4.1 -- OpenMP
  • From: Steve Kargl
• Re: Let's use gcc-4.2, not 4.1 -- OpenMP
  • From: Scott Long
• Re: Let's use gcc-4.2, not 4.1 -- OpenMP
  • From: David Xu
• Re: Let's use gcc-4.2, not 4.1 -- OpenMP
  • From: Steve Kargl
• Re: SD slot on ThinkPad X60
  • From: Scot Hetzel
• Re: Let's use gcc-4.2, not 4.1 -- OpenMP
  • From: Steve Kargl
• Re: Let's use gcc-4.2, not 4.1 -- OpenMP
  • From: Daniel O'Connor
• Re: Let's use gcc-4.2, not 4.1 -- OpenMP
  • From: Kris Kennaway
• Re: Let's use gcc-4.2, not 4.1 -- OpenMP
  • From: Juha Saarinen
• Re: SD slot on ThinkPad X60
  • From: Alexandre \"Sunny\" Kovalenko
• Re: Let's use gcc-4.2, not 4.1 -- OpenMP
  • From: Scott Long
• Re: Let's use gcc-4.2, not 4.1 -- OpenMP
  • From: George V. Neville-Neil
• Re: D-Link DGE-350T and if_sk (no go)
  • From: Pyun YongHyeon
• Re: Let's use gcc-4.2, not 4.1 -- OpenMP
  • From: David O'Brien
• Re: Let's use gcc-4.2, not 4.1 -- OpenMP
  • From: David O'Brien
• Re: Automatic TCP send and receive socket buffer sizing
  • From: Chris
• cbb hangs during suspend if ath card active
  • From: Stepan Zastupov
• [head tinderbox] failure on i386/pc98
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on i386/i386
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on amd64/amd64
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on arm/arm
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on sparc64/sun4v
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on sparc64/sparc64
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on ia64/ia64
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on powerpc/powerpc
  • From: FreeBSD Tinderbox
• Re: Page table walk on TLB miss
  • From: Lars Heidieker
• [head tinderbox] failure on i386/i386
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on i386/pc98
  • From: FreeBSD Tinderbox
• Re: [head tinderbox] failure on i386/i386
  • From: othermark
• [head tinderbox] failure on amd64/amd64
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on arm/arm
  • From: FreeBSD Tinderbox
• SD slot on ThinkPad X60
  • From: Rong-en Fan
• [head tinderbox] failure on sparc64/sparc64
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on sparc64/sun4v
  • From: FreeBSD Tinderbox
• Page table walk on TLB miss
  • From: Martin Cracauer
• Re: Let's use gcc-4.2, not 4.1 -- OpenMP
  • From: Scott Long
• [head tinderbox] failure on ia64/ia64
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on powerpc/powerpc
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on i386/i386
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on i386/pc98
  • From: FreeBSD Tinderbox
• Re: Let's use gcc-4.2, not 4.1 -- OpenMP
  • From: Peter Jeremy
• [head tinderbox] failure on amd64/amd64
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on arm/arm
  • From: FreeBSD Tinderbox
• Re: curious results
  • From: Randall Stewart
• [head tinderbox] failure on sparc64/sun4v
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on sparc64/sparc64
  • From: FreeBSD Tinderbox
• Re: Fwd: Re: pf: BAD state happens often with portsnap fetch update
  • From: Adam McDougall
• [head tinderbox] failure on ia64/ia64
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on powerpc/powerpc
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on i386/pc98
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on i386/i386
  • From: FreeBSD Tinderbox
• Re: Let's use gcc-4.2, not 4.1 -- OpenMP
  • From: Ivan Voras
• [head tinderbox] failure on amd64/amd64
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on arm/arm
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on sparc64/sparc64
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on sparc64/sun4v
  • From: FreeBSD Tinderbox
• Re: Let's use gcc-4.2, not 4.1 -- OpenMP
  • From: Luigi Rizzo
• Re: Let's use gcc-4.2, not 4.1 -- OpenMP
  • From: Ivan Voras
• Re: Let's use gcc-4.2, not 4.1 -- OpenMP
  • From: Mikhail Teterin
• Re: Automatic TCP send and receive socket buffer sizing
  • From: Andre Oppermann
• Re: D-Link DGE-350T and if_sk (no go)
  • From: Pascal Hofstee
• Re: Let's use gcc-4.2, not 4.1 -- OpenMP
  • From: O. Hartmann
• Re: D-Link DGE-350T and if_sk (no go)
  • From: Pascal Hofstee
• Re: Let's use gcc-4.2, not 4.1 -- OpenMP
  • From: Scott Long
• Re: Let's use gcc-4.2, not 4.1 -- OpenMP
  • From: Doug Barton
• Re: CFT: new ath hal
  • From: Beech Rintoul
• Re: Automatic TCP send and receive socket buffer sizing
  • From: Chris
• Re: D-Link DGE-350T and if_sk (no go)
  • From: Pyun YongHyeon
• Re: Let's use gcc-4.2, not 4.1 -- OpenMP
  • From: Mikhail Teterin
• Re: PCI sio card
  • From: Bruce M. Simpson
• D-Link DGE-350T and if_sk (no go)
  • From: Pascal Hofstee
• Re: Let's use gcc-4.2, not 4.1 -- OpenMP
  • From: Scott Long
• Let's use gcc-4.2, not 4.1 -- OpenMP
  • From: Mikhail Teterin
• Re: CFT: new ath hal
  • From: Brooks Davis
• Re: Socket problems with latest -current
  • From: Doug Barton
• Re: kqueue LOR
  • From: John Baldwin
• Re: cpufreq est and Enhanced Sleep (Cx) States for Intel Core and above
  • From: Stephane E. Potvin
• Re: kqueue LOR
  • From: Attilio Rao
• Re: kqueue LOR
  • From: Kostik Belousov
• Re: PCI sio card
  • From: Ian FREISLICH
• Re: Socket problems with latest -current
  • From: gnn
• Re: Automatic TCP send and receive socket buffer sizing
  • From: Maxim Konovalov
• Re: Automatic TCP send and receive socket buffer sizing
  • From: Andre Oppermann
• Re: Call for Marvell/SysKonnect Yukon II Gigabit Ethernet testers.
  • From: Pyun YongHyeon
• Re: PCI sio card
  • From: Mike Tancsa
• Re: Automatic TCP send and receive socket buffer sizing
  • From: Maxim Konovalov
• Re: Call for Marvell/SysKonnect Yukon II Gigabit Ethernet testers.
  • From: Andre Guibert de Bruet
• Re: Call for Marvell/SysKonnect Yukon II Gigabit Ethernet testers.
  • From: Pyun YongHyeon
• Re: Call for Marvell/SysKonnect Yukon II Gigabit Ethernet testers.
  • From: Andre Guibert de Bruet
• Re: PCI sio card
  • From: Ian FREISLICH
• Re: kqueue LOR
  • From: Tor Egge
• Re: kqueue LOR
  • From: Bruce Evans
• Re: CURRENT freezes on Laitude D520
  • From: Tai-hwa Liang
• Re: cpufreq est and Enhanced Sleep (Cx) States for Intel Core and above
  • From: Adam McDougall
• Re: kqueue LOR
  • From: Attilio Rao
• Re: kqueue LOR
  • From: Attilio Rao
• Re: kqueue LOR
  • From: John Baldwin
• Automatic TCP send and receive socket buffer sizing
  • From: Andre Oppermann
• Re: nvidia driver version 9631
  • From: Rod Person
• Re: kqueue LOR
  • From: John Baldwin
• Re: kqueue LOR
  • From: Attilio Rao
• Re: kqueue LOR
  • From: Suleiman Souhlal
• Re: nvidia driver version 9631
  • From: Eric Anderson
• Re: kqueue LOR
  • From: Attilio Rao
• Re: kqueue LOR
  • From: John Baldwin
• Re: kqueue LOR
  • From: Attilio Rao
• [head tinderbox] failure on sparc64/sun4v
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on sparc64/sparc64
  • From: FreeBSD Tinderbox
• Re: CURRENT freezes on Laitude D520 (fwd)
  • From: David Wolfskill
• [head tinderbox] failure on powerpc/powerpc
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on ia64/ia64
  • From: FreeBSD Tinderbox
• Re: cpufreq est and Enhanced Sleep (Cx) States for Intel Core and above
  • From: Rong-en Fan
• [head tinderbox] failure on i386/pc98
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on i386/i386
  • From: FreeBSD Tinderbox
• Re: curious results
  • From: Ricardo Nabinger Sanchez
• [head tinderbox] failure on amd64/amd64
  • From: FreeBSD Tinderbox
• Re: PCI sio card
  • From: Mike Tancsa
• Re: kqueue LOR
  • From: Attilio Rao
• Re: kqueue LOR
  • From: Kostik Belousov
• Re: Call for Marvell/SysKonnect Yukon II Gigabit Ethernet testers.
  • From: Michel Talon
• Re: PCI sio card
  • From: Ian FREISLICH
• Re: kqueue LOR
  • From: Bruce Evans
• Re: kqueue LOR
  • From: Kostik Belousov
• curious results
  • From: Randall Stewart
• Re: kqueue LOR
  • From: Suleiman Souhlal
• Re: umass intermittently "stalling" ... processes seemingly stuck in "wdrain" state
  • From: Julian H. Stacey
• Re: Call for Marvell/SysKonnect Yukon II Gigabit Ethernet testers.
  • From: Pyun YongHyeon
• umass intermittently "stalling" ... processes seemingly stuck in "wdrain" state
  • From: Pascal Hofstee
• Re: PCI sio card
  • From: Bjoern A. Zeeb
• Re: Slight interface change on the watchdog fido
  • From: Nick Hibma
• Re: nvidia driver version 9631
  • From: Joel Dahl
• PCI sio card
  • From: Ian FREISLICH
• QUOTA on CURRENT: mount -a -l gives "mount: /dev/amrd0s1a Unable to initialize radix node head: No buffer space available"
  • From: Andre Guibert de Bruet
• Re: Latest Broadcom NDIS driver requires 4 additional functions
  • From: Scot Hetzel
• Re: nvidia driver version 9631
  • From: Eric Anderson
• Re: Call for Marvell/SysKonnect Yukon II Gigabit Ethernet testers.
  • From: Andre Guibert de Bruet
• Re: CURRENT freezes on Laitude D520
  • From: Andrew Pantyukhin
• Re: CURRENT freezes on Laitude D520
  • From: Tai-hwa Liang
• Re: Call for Marvell/SysKonnect Yukon II Gigabit Ethernet testers.
  • From: Pyun YongHyeon
• Re: mk48txx
  • From: Marius Strobl
• Re: mk48txx
  • From: M. Warner Losh
• Re: mk48txx
  • From: Scott Long
• [head tinderbox] failure on i386/pc98
  • From: FreeBSD Tinderbox
• Re: kdb_backtrace 'feature'?
  • From: Kris Kennaway
• Re: kdb_backtrace 'feature'?
  • From: Julian Elischer
• Re: mk48txx
  • From: Marius Strobl
• Re: kdb_backtrace 'feature'?
  • From: Julian Elischer
• Re: kdb_backtrace 'feature'?
  • From: Kris Kennaway
• Re: nvidia driver version 9631
  • From: Rod Person
• Re: Slight interface change on the watchdog fido
  • From: Olivier Houchard
• Re: Call for Marvell/SysKonnect Yukon II Gigabit Ethernet testers.
  • From: Bruce M. Simpson
• Re: Slight interface change on the watchdog fido
  • From: Marius Strobl
• kdb_backtrace 'feature'?
  • From: Julian Elischer
• Re: rescue/rescue not compiling ?
  • From: Rene Ladan
• Re: nvidia driver version 9631
  • From: Nicolas Blais
• Re: FreeBSD 6 (or 7) on a HP DL140 G3 SATA
  • From: John Baldwin
• Re: Slight interface change on the watchdog fido
  • From: John Baldwin
• Re: rescue/rescue not compiling ?
  • From: Ruslan Ermilov
• Re: rescue/rescue not compiling ?
  • From: Giorgos Keramidas
• Re: CURRENT freezes on Laitude D520 (fwd)
  • From: Maxim Konovalov
• Re: CURRENT freezes on Laitude D520 (fwd)
  • From: Robert Watson
• rescue/rescue not compiling ?
  • From: Rene Ladan
• Re: nvidia driver version 9631
  • From: Rod Person
• Re: nvidia driver version 9631
  • From: Jona Joachim
• Re: CURRENT freezes on Laitude D520 (fwd)
  • From: David Wolfskill
• Re: CURRENT freezes on Laitude D520 (fwd)
  • From: Maxim Konovalov
• Re: New Challenges ( FreeBSD on PS3 )
  • From: Peter Grehan
• Re: nvidia driver version 9631
  • From: Ricardo Nabinger Sanchez
• nvidia driver version 9631
  • From: Rod Person
• Re: CURRENT freezes on Laitude D520
  • From: Robert Watson
• Re: New Challenges ( FreeBSD on PS3 )
  • From: Eprha Carvajal
• Re: New Challenges ( FreeBSD on PS3 )
  • From: pfgshield-freebsd
• Re: CURRENT freezes on Laitude D520
  • From: Tai-hwa Liang
• dcons kldunload panic
  • From: Anish Mistry
• Re: New Challenges ( FreeBSD on PS3 )
  • From: Gavin Atkinson
• Re: CURRENT freezes on Laitude D520 (fwd)
  • From: Robert Watson
• Re: CURRENT freezes on Laitude D520
  • From: yal
• Re: Am I an Idiot?
  • From: Gaspar Chilingarov
• Re: Socket problems with latest -current
  • From: Doug Barton
• Re: FreeBSD 6 (or 7) on a HP DL140 G3 SATA
  • From: Robert Watson
• Re: New Challenges ( FreeBSD on PS3 )
  • From: Philip S. Schulz
• Re: Slight interface change on the watchdog fido
  • From: M. Warner Losh
• Re: mk48txx
  • From: M. Warner Losh
• Re: Am I an Idiot?
  • From: M. Warner Losh
• Re: New Challenges ( FreeBSD on PS3 )
  • From: Kip Macy
• New Challenges ( FreeBSD on PS3 )
  • From: Eprha Carvajal
• Socket problems with latest -current
  • From: Doug Barton
• Re: Slight interface change on the watchdog fido
  • From: Nick Hibma
• Re: Slight interface change on the watchdog fido
  • From: Nick Hibma
• Re: FreeBSD 6 (or 7) on a HP DL140 G3 SATA
  • From: Ulf Zimmermann
• Re: samba-cups-pdf virtual printer
  • From: John Nielsen
• Re: Slight interface change on the watchdog fido
  • From: Poul-Henning Kamp
• Re: Slight interface change on the watchdog fido
  • From: Marius Strobl
• Re: Slight interface change on the watchdog fido
  • From: Nick Hibma
• Re: FreeBSD 6 (or 7) on a HP DL140 G3 SATA
  • From: J. Martin Petersen
• Re: CURRENT freezes on Laitude D520
  • From: yal
• Re: CURRENT freezes on Laitude D520
  • From: Robert Watson
• Re: Slight interface change on the watchdog fido
  • From: Poul-Henning Kamp
• Re: CURRENT freezes on Laitude D520
  • From: Robert Watson
• Slight interface change on the watchdog fido
  • From: Nick Hibma
• Re: CURRENT freezes on Laitude D520
  • From: Maxim Konovalov
• Re: mk48txx
  • From: Nick Hibma
• Re: CURRENT freezes on Laitude D520
  • From: Robert Watson
• samba-cups-pdf virtual printer
  • From: fulan Peng
• [head tinderbox] failure on sparc64/sun4v
  • From: FreeBSD Tinderbox
• Re: CURRENT freezes on Laitude D520
  • From: Tai-hwa Liang
• Re: Fwd: Re: pf: BAD state happens often with portsnap fetch update
  • From: Colin Percival
• Re: Fwd: Re: pf: BAD state happens often with portsnap fetch update
  • From: Adam McDougall
• Re: Fwd: Re: pf: BAD state happens often with portsnap fetch update
  • From: Colin Percival
• Fwd: Re: pf: BAD state happens often with portsnap fetch update
  • From: Adam McDougall
• Re: cpufreq est and Enhanced Sleep (Cx) States for Intel Core and above
  • From: Dimitry Andric
• cpufreq est and Enhanced Sleep (Cx) States for Intel Core and above
  • From: Adam McDougall
• Re: Am I an Idiot?
  • From: Scott Robbins
• Re: CURRENT freezes on Laitude D520
  • From: yal
• Re: CFT: new ath hal
  • From: Wilko Bulte
• Re: Am I an Idiot?
  • From: Doug Barton
• Re: CURRENT freezes on Laitude D520
  • From: Maxim Konovalov
• Re: Am I an Idiot?
  • From: David Stanford
• Re: CURRENT freezes on Laitude D520
  • From: yal
• Re: CURRENT freezes on Laitude D520
  • From: Robert Watson
• Re: Am I an Idiot?
  • From: David Stanford
• Re: CURRENT freezes on Laitude D520
  • From: Andrew Pantyukhin
• Re: Am I an Idiot?
  • From: Per olof Ljungmark
• Re: mk48txx
  • From: Marius Strobl
• Re: CURRENT freezes on Laitude D520
  • From: Robert Watson
• Re: Am I an Idiot?
  • From: David Stanford
• Re: mk48txx
  • From: Nick Hibma
• Re: FreeBSD 6 (or 7) on a HP DL140 G3 SATA
  • From: Ulf Zimmermann
• Re: mk48txx
  • From: Marius Strobl
• Re: CURRENT freezes on Laitude D520
  • From: yal
• Re: CURRENT freezes on Laitude D520
  • From: Maxim Konovalov
• Re: CFT: new ath hal
  • From: Sam Leffler
• CURRENT freezes on Laitude D520
  • From: Francesco Maiorca
• Re: CURRENT freezes on Laitude D520
  • From: David Wolfskill
• CURRENT freezes on Laitude D520
  • From: yal
• mk48txx
  • From: Nick Hibma
• Re: FreeBSD 6 (or 7) on a HP DL140 G3 SATA
  • From: Robert Watson
• Re: FreeBSD 6 (or 7) on a HP DL140 G3 SATA
  • From: J. Martin Petersen
• Re: CFT: new ath hal
  • From: Wilko Bulte
• Re: CFT: new ath hal
  • From: Alexandre \"Sunny\" Kovalenko
• Re: Am I an Idiot?
  • From: David Nugent
• Re: Running -CURRENT in production
  • From: Giorgos Keramidas
• Re: Running -CURRENT in production
  • From: Per olof Ljungmark
• Re: Running -CURRENT in production (was: Am I an Idiot?)
  • From: Giorgos Keramidas
• Re: Running -CURRENT in production (was: Am I an Idiot?)
  • From: JoaoBR
• Re: Running -CURRENT in production
  • From: Mark Kirkwood
• Re: Running -CURRENT in production (was: Am I an Idiot?)
  • From: Cédric Jonas
• Re: Running -CURRENT in production
  • From: Chris
• Re: Running -CURRENT in production (was: Am I an Idiot?)
  • From: JoaoBR
• Re: Running -CURRENT in production (was: Am I an Idiot?)
  • From: Eprha Carvajal
• Re: Running -CURRENT in production (was: Am I an Idiot?)
  • From: Greg 'groggy' Lehey
• Re: Running -CURRENT in production
  • From: Per olof Ljungmark
• Re: Running -CURRENT in production (was: Am I an Idiot?)
  • From: JoaoBR
• Re: Am I an Idiot?
  • From: Per olof Ljungmark
• Re: Am I an Idiot?
  • From: Doug Barton
• Running -CURRENT in production (was: Am I an Idiot?)
  • From: Greg 'groggy' Lehey
• Re: Am I an Idiot?
  • From: Beech Rintoul
• Re: Am I an Idiot?
  • From: Derek Ragona
• Am I an Idiot?
  • From: Per olof Ljungmark
• Re: Problem with gif and IPv6 in -CURRENT
  • From: Doug Barton
• Re: Problem with gif and IPv6 in -CURRENT
  • From: Joe Marcus Clarke
• Re: Problem with gif and IPv6 in -CURRENT
  • From: Bjoern A. Zeeb
• Re: Problem with gif and IPv6 in -CURRENT
  • From: Joe Marcus Clarke
• Re: Problem with gif and IPv6 in -CURRENT
  • From: Joe Marcus Clarke
• Re: Problem with gif and IPv6 in -CURRENT
  • From: Bjoern A. Zeeb
• Re: Problem with gif and IPv6 in -CURRENT
  • From: gnn
• Re: Problem with gif and IPv6 in -CURRENT
  • From: gnn
• Re: FreeBSD 6 (or 7) on a HP DL140 G3 SATA
  • From: Dominic Marks
• Re: Current for Benchmarking
  • From: Dominic Marks
• Current for Benchmarking
  • From: Benjamin D Adams
• FreeBSD 6 (or 7) on a HP DL140 G3 SATA
  • From: Peter Losher
• Leaked mountpoints
  • From: Kris Kennaway
• [head tinderbox] failure on sparc64/sun4v
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on sparc64/sparc64
  • From: FreeBSD Tinderbox
• anyone remember fixing this bug (in serial debugger in 6.1)
  • From: Julian Elischer
• Re: [head tinderbox] failure on powerpc/powerpc
  • From: mjacob
• [head tinderbox] failure on powerpc/powerpc
  • From: FreeBSD Tinderbox
• Problem with gif and IPv6 in -CURRENT
  • From: Joe Marcus Clarke
• Re: CFT: new ath hal
  • From: Tai-hwa Liang
• Re: how to get supported channels from iwi firmware
  • From: YAMAMOTO Shigeru
• Re: CFT: new ath hal
  • From: Ian FREISLICH
• /etc/rc.firewall and setup_loopback()
  • From: Ian FREISLICH
• Re: Reporting 2 LORs
  • From: Bjoern A. Zeeb
• Re: CFT: new ath hal
  • From: Sam Leffler
• Re: CFT: new ath hal
  • From: Wilko Bulte
• Re: Reporting 2 LORs
  • From: Nuno Antunes
• Re: Reporting 2 LORs
  • From: Max Laier
• Re: HEADS UP: compat6x
  • From: Matthew D. Fuller
• Reporting 2 LORs
  • From: Nuno Antunes
• Re: Java problem on i386 7.0-CURRENT-200611 Again
  • From: Vince Hoffman
• Re: HEADS UP: compat6x
  • From: Florent Thoumie
• CFT: new ath hal
  • From: Sam Leffler
• Re: HEADS UP: compat6x
  • From: Alexander Leidinger
• Re: Java problem on i386 7.0-CURRENT-200611 Again
  • From: Tommy Rehn
• Re: HEADS UP: compat6x
  • From: Florent Thoumie
• Re: Updating a server with Vinum
  • From: Ulf Lilleengen
• Re: HEADS UP: compat6x
  • From: Alexander Leidinger
• Re: Updating a server with Vinum
  • From: Freddie Cash
• RE: Updating a server with Vinum
  • From: Eric Germann
• Re: HEADS UP: compat6x
  • From: Daniel Eischen
• Re: Java problem on i386 7.0-CURRENT-200611
  • From: Jan Mikael Melen
• Re: DRM forced malloc(M_NOWAIT)
  • From: Kip Macy
• Re: DRM forced malloc(M_NOWAIT)
  • From: John Baldwin
• Re: HEADS UP: compat6x
  • From: John Baldwin
• Java problem on i386 7.0-CURRENT-200611
  • From: Tommy Rehn
• Re: Odd problem with a NetCell SyncRAID SR3000 SATA RAID
  • From: Søren Schmidt
• Re: How supported are SATA DVD burners?
  • From: Søren Schmidt
• Odd problem with a NetCell SyncRAID SR3000 SATA RAID
  • From: Rink Springer
• How supported are SATA DVD burners?
  • From: Martin Nilsson
• Re: debugging signal 11 on -current ...
  • From: Greg 'groggy' Lehey
• LOCK_PROFILING confusion
  • From: John Polstra
• Re: LOR with netisr changes
  • From: Sam Leffler
• Re: LOR with netisr changes
  • From: Max Laier
• Re: EHCI problem on -current, and unknown devs
  • From: Doug Barton
• Re: LOR with netisr changes
  • From: John Baldwin
• Re: cvsync doesn't work simply on 7-current with SYMVER_ENABLED=yes
  • From: Norikatsu Shigemura
• Re: cvsync doesn't work simply on 7-current with SYMVER_ENABLED=yes
  • From: Norikatsu Shigemura
• Re: cvsync doesn't work simply on 7-current with SYMVER_ENABLED=yes
  • From: Michael Bushkov
• Re: EHCI problem on -current, and unknown devs
  • From: Stephane E. Potvin
• Re: kern/105229: panic in sync_fsync
  • From: Kostik Belousov
• Re: Call for e1000phy(4) testers.
  • From: Pyun YongHyeon
• Re: Call for e1000phy(4) testers.
  • From: Pyun YongHyeon
• Re: Updating a server with Vinum
  • From: Juraj Lutter
• Updating a server with Vinum
  • From: Eric Germann
• USB/umass problems.
  • From: Ian FREISLICH
• DRM forced malloc(M_NOWAIT)
  • From: Nick Hibma
• debugging signal 11 on -current ...
  • From: Wilkinson, Alex
• Re: /usr/src/Makefile target to create an 'installed' subtree ?
  • From: Luigi Rizzo
• umass mount woes
  • From: Neil Short
• Re: /usr/src/Makefile target to create an 'installed' subtree ?
  • From: Pieter de Goeje
• Re: /usr/src/Makefile target to create an 'installed' subtree ?
  • From: Alexander Leidinger
• Re: /usr/src/Makefile target to create an 'installed' subtree ?
  • From: Bjoern A. Zeeb
• Re: /usr/src/Makefile target to create an 'installed' subtree ?
  • From: Gary Palmer
• Re: [panic] Re: small heads-up: Syncing amd64 GENERIC with i386 GENERIC (removing LINUX stuff)
  • From: Alexander Leidinger
• /usr/src/Makefile target to create an 'installed' subtree ?
  • From: Luigi Rizzo
• Re: [panic] Re: small heads-up: Syncing amd64 GENERIC with i386 GENERIC (removing LINUX stuff)
  • From: Boris Samorodov
• Re: sched_ule completely hosed?
  • From: Julian Elischer
• RELENG6/amd64: weird tcp window scaling behaviour
  • From: Jacco Braat
• RELENG6/amd64: weird tcp window scaling behaviour
  • From: Jacco Braat
• Re: cvsync doesn't work simply on 7-current with SYMVER_ENABLED=yes
  • From: Norikatsu Shigemura
• Re: [panic] Re: small heads-up: Syncing amd64 GENERIC with i386 GENERIC (removing LINUX stuff)
  • From: Divacky Roman
• Re: cvsync doesn't work simply on 7-current with SYMVER_ENABLED=yes
  • From: Daniel Eischen
• bin/105721: Misleading error message from e.g. "df -l -t ufs"
  • From: Fabian Ruch
• Re: sched_ule completely hosed?
  • From: Eprha Carvajal
• Re: LOR with netisr changes
  • From: Munehiro Matsuda
• Re: sched_ule completely hosed?
  • From: Maxim Konovalov
• Re: sched_ule completely hosed?
  • From: Maxim Konovalov
• Re: HEADS UP: compat6x
  • From: Daniel Eischen
• Re: [panic] Re: small heads-up: Syncing amd64 GENERIC with i386 GENERIC (removing LINUX stuff)
  • From: Boris Samorodov
• Re: HEADS UP: compat6x
  • From: John Hay
• Re: [ANN] unionfs patchset-17 release, lock mechanism changed for robust working
  • From: Daichi GOTO
• Re: [ANN] unionfs patchset-17 release, lock mechanism changed for robust working
  • From: Daichi GOTO
• Re: HEADS UP: compat6x
  • From: Astrodog
• Re: sched_ule completely hosed?
  • From: Astrodog
• sched_ule completely hosed?
  • From: Julian Elischer
• Re: [panic] Re: small heads-up: Syncing amd64 GENERIC with i386 GENERIC (removing LINUX stuff)
  • From: Divacky Roman
• Re: HEADS UP: compat6x
  • From: Simon L. Nielsen
• Re: HEADS UP: compat6x
  • From: John Hay
• Re: HEADS UP: compat6x
  • From: Doug Barton
• Re: HEADS UP: compat6x
  • From: John Hay
• Re: [ANN] unionfs patchset-17 release, lock mechanism changed for robust working
  • From: Kris Kennaway
• Re: [ANN] unionfs patchset-17 release, lock mechanism changed for robust working
  • From: Scott Long
• [panic] Re: small heads-up: Syncing amd64 GENERIC with i386 GENERIC (removing LINUX stuff)
  • From: Boris Samorodov
• Re: [ANN] unionfs patchset-17 release, lock mechanism changed for robust working
  • From: Kris Kennaway
• [head tinderbox] failure on sparc64/sun4v
  • From: FreeBSD Tinderbox
• Re: [ANN] unionfs patchset-17 release, lock mechanism changed for robust working
  • From: Kris Kennaway
• [head tinderbox] failure on sparc64/sparc64
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on powerpc/powerpc
  • From: FreeBSD Tinderbox
• Re: small heads-up: Syncing amd64 GENERIC with i386 GENERIC (removing LINUX stuff)
  • From: Andrew Pantyukhin
• Re: small heads-up: Syncing amd64 GENERIC with i386 GENERIC (removing LINUX stuff)
  • From: Divacky Roman
• Re: small heads-up: Syncing amd64 GENERIC with i386 GENERIC (removing LINUX stuff)
  • From: Boris Samorodov
• Re: HEADS UP: compat6x
  • From: Rene Ladan
• Re: cvsync doesn't work simply on 7-current with SYMVER_ENABLED=yes
  • From: Daniel Eischen
• Re: small heads-up: Syncing amd64 GENERIC with i386 GENERIC (removing LINUX stuff)
  • From: Boris Samorodov
• Re: cvsync doesn't work simply on 7-current with SYMVER_ENABLED=yes
  • From: Norikatsu Shigemura
• Re: HEADS UP: compat6x
  • From: Daniel Eischen
• Re: small heads-up: Syncing amd64 GENERIC with i386 GENERIC (removing LINUX stuff)
  • From: Rink Springer
• small heads-up: Syncing amd64 GENERIC with i386 GENERIC (removing LINUX stuff)
  • From: Alexander Leidinger
• Re: LOR with netisr changes
  • From: Bjoern A. Zeeb
• Re: HEADS UP: compat6x
  • From: Rene Ladan
• Re: kern/105229: panic in sync_fsync
  • From: Yoichi Nakayama
• Re: Call for e1000phy(4) testers.
  • From: Scott Long
• Re: Call for e1000phy(4) testers.
  • From: Tai-hwa Liang
• Re: EHCI problem on -current, and unknown devs
  • From: Doug Barton
• Re: Call for e1000phy(4) testers.
  • From: John Baldwin
• Re: Call for e1000phy(4) testers.
  • From: John Baldwin
• [bug found] Re: byte swapped udp length in diskless bootp request ?
  • From: Luigi Rizzo
• Re: EHCI problem on -current, and unknown devs
  • From: John Baldwin
• [ANN] unionfs patchset-17 release, lock mechanism changed for robust working
  • From: Daichi GOTO
• Re: Call for e1000phy(4) testers.
  • From: Pyun YongHyeon
• [HEADSUP] if_watchdog considered unsafe
  • From: Gleb Smirnoff
• wrong definition of prefixes of bits in systat(1)
  • From: Rostislav Krasny
• Re: Call for e1000phy(4) testers.
  • From: Scott Long
• Re: Call for e1000phy(4) testers.
  • From: Tai-hwa Liang
• AsiaBSDCon Presentation Submission Deadline
  • From: gnn
• Re: EHCI problem on -current, and unknown devs
  • From: Stephane E. Potvin
• Re: shmget regression?
  • From: Robert Watson

• Security
• UNIX
• Linux
• Coding
• Usenet

• Mailing-Lists
• Newsgroups
• About
• Privacy
• Search
• Imprint