freebsd-current
- Re: Panic @r207433: "System call fork returning with the following locks held"
- Re: ZFS Stability & MySQL (Comments Requested)
- From: Jason J. W. Williams
- Re: Making IFQ_MAXLEN tunable
- Re: Panic @r207433: "System call fork returning with the following locks held"
- Making IFQ_MAXLEN tunable
- Re: ZFS Stability & MySQL (Comments Requested)
- Re: Panic @r207433: "System call fork returning with the following locks held"
- Re: Panic @r207433: "System call fork returning with the following locks held"
- Re: Panic @r207433: "System call fork returning with the following locks held"
- Re: Panic @r207433: "System call fork returning with the following locks held"
- Panic @r207433: "System call fork returning with the following locks held"
- Re: SUJ update
- Re: mpt(4) MPI_EVENT_IR_RESYNC_UPDATE
- rsync locks for very long periods (indefinitely?) when using suj over raid5
- Re: SUJ update
- From: Vladimir Grebenschikov
- Re: mpt(4) MPI_EVENT_IR_RESYNC_UPDATE
- Re: SUJ update
- Re: ZFS Stability & MySQL (Comments Requested)
- From: Jason J. W. Williams
- mpt(4) MPI_EVENT_IR_RESYNC_UPDATE
- Re: SUJ update
- Re: SUJ update
- From: Vladimir Grebenschikov
- Re: SUJ update
- From: Vladimir Grebenschikov
- Re: kmem_map too small: 3832475648 total allocated
- Re: kmem_map too small: 3832475648 total allocated
- From: Willem Jan Withagen
- SUJ update
- Re[2]: kmem_map too small: 3832475648 total allocated
- LOR on secondary machine.
- Re: config(8) dumps core
- Re: config(8) dumps core
- Re: config(8) dumps core
- Re: kmem_map too small: 3832475648 total allocated
- Re: config(8) dumps core
- Re: config(8) dumps core
- Re: config(8) dumps core
- Re: kmem_map too small: 3832475648 total allocated
- From: James R. Van Artsdalen
- Re: config(8) dumps core
- Re: config(8) dumps core
- Re: config(8) dumps core
- Re: kmem_map too small: 3832475648 total allocated
- From: James R. Van Artsdalen
- Re: config(8) dumps core
- Re: config(8) dumps core
- Re: kmem_map too small: 3832475648 total allocated
- Re: ZFS Stability & MySQL (Comments Requested)
- From: Jason J. W. Williams
- Re: kmem_map too small: 3832475648 total allocated
- Re: ZFS Stability & MySQL (Comments Requested)
- Re: ZFS Stability & MySQL (Comments Requested)
- From: Jason J. W. Williams
- Re: kmem_map too small: 3832475648 total allocated
- config(8) dumps core
- Re: fixes for enhanced coredump
- Re: kmem_map too small: 3832475648 total allocated
- Re: ZFS Stability & MySQL (Comments Requested)
- ZFS Stability & MySQL (Comments Requested)
- From: Jason J. W. Williams
- Re: sleep bug in taskqueue(9)
- Re: fixes for enhanced coredump
- Re: Ruby w/clang (Was: Re: [CFT]: ClangBSD is selfhosting, we need testers now)
- Re: Ruby w/clang (Was: Re: [CFT]: ClangBSD is selfhosting, we need testers now)
- Re: Failed assertion: "(run->regs_mask[elm] & (1U << bit)) == 0"
- Failed assertion: "(run->regs_mask[elm] & (1U << bit)) == 0"
- Re[2]: kmem_map too small: 3832475648 total allocated
- Re: kmem_map too small: 3832475648 total allocated
- kmem_map too small: 3832475648 total allocated
- From: James R. Van Artsdalen
- sleep bug in taskqueue(9)
- Re: Ruby w/clang (Was: Re: [CFT]: ClangBSD is selfhosting, we need testers now)
- Re: Ruby w/clang (Was: Re: [CFT]: ClangBSD is selfhosting, we need testers now)
- Re: Switchover to CAM ATA?
- From: Dag-Erling Smørgrav
- Re: Switchover to CAM ATA?
- Re: newsyslog patch implementing file includes
- Re: FreeBSD kernel doesn't boot on FUJITSU PRIMERGY RX200 S5 server
- fixes for enhanced coredump
- Re: Ruby w/clang (Was: Re: [CFT]: ClangBSD is selfhosting, we need testers now)
- Problem with reboot
- New Marvell SATA driver for testing
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Ruby w/clang (Was: Re: [CFT]: ClangBSD is selfhosting, we need testers now)
- Re: xorg hangs after last commits
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: Switchover to CAM ATA?
- From: Dag-Erling Smørgrav
- Re: xorg hangs after last commits
- Re: FreeBSD kernel doesn't boot on FUJITSU PRIMERGY RX200 S5 server
- Re: ISO9660 4GB directory structures boundary limit and growisofs
- Re: xorg hangs after last commits
- Re: xorg hangs after last commits
- Re: FreeBSD kernel doesn't boot on FUJITSU PRIMERGY RX200 S5 server
- Re: FreeBSD kernel doesn't boot on FUJITSU PRIMERGY RX200 S5 server
- Re: ISO9660 4GB directory structures boundary limit and growisofs
- Re: FreeBSD kernel doesn't boot on FUJITSU PRIMERGY RX200 S5 server
- Re: FreeBSD kernel doesn't boot on FUJITSU PRIMERGY RX200 S5 server
- Re: FreeBSD kernel doesn't boot on FUJITSU PRIMERGY RX200 S5 server
- Re: Switchover to CAM ATA?
- Re: Switchover to CAM ATA?
- Re: FreeBSD kernel doesn't boot on FUJITSU PRIMERGY RX200 S5 server
- Re: FreeBSD kernel doesn't boot on FUJITSU PRIMERGY RX200 S5 server
- Re: Switchover to CAM ATA?
- Re: Switchover to CAM ATA?
- Re: Switchover to CAM ATA?
- From: Dag-Erling Smørgrav
- Re: xorg hangs after last commits
- Re: xorg hangs after last commits
- Re: Switchover to CAM ATA?
- Re: xorg hangs after last commits
- Re: Switchover to CAM ATA?
- From: Dag-Erling Smørgrav
- Re: Switchover to CAM ATA?
- From: Dag-Erling Smørgrav
- Re: Something wrong with TCP connections in recent -current
- Re: Something wrong with TCP connections in recent -current
- Something wrong with TCP connections in recent -current
- Re: Switchover to CAM ATA?
- xorg hangs after last commits
- Re: HEADS UP: SUJ Going in to head today
- Re: Switchover to CAM ATA?
- Re: HEADS UP: SUJ Going in to head today
- Re: ClangBSD build failures
- Re: ClangBSD build failures
- Re: ClangBSD build failures
- Re: ClangBSD build failures
- Re: ClangBSD build failures
- Re: ClangBSD build failures
- Re: ClangBSD build failures
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- ClangBSD build failures
- Re: HEADS UP: SUJ Going in to head today
- Re: HEADS UP: SUJ Going in to head today
- Re: HEADS UP: SUJ Going in to head today
- Re: HEADS UP: SUJ Going in to head today
- Re: Switchover to CAM ATA?
- Re: HEADS UP: SUJ Going in to head today
- Re: HEADS UP: SUJ Going in to head today - panic on rename()
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: Switchover to CAM ATA?
- Re: Switchover to CAM ATA?
- Re: Keyboard problem with new MacBook Pro.
- Re: Switchover to CAM ATA?
- From: Pawel Jakub Dawidek
- Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
- Re: Switchover to CAM ATA?
- Re: Switchover to CAM ATA?
- Re: Switchover to CAM ATA?
- From: Pawel Jakub Dawidek
- Re: kern+world / ports make options
- Re: Switchover to CAM ATA?
- Re: net/mpd5, ppp, proxy-arp issues
- Re: Switchover to CAM ATA?
- Re: HEADS UP: SUJ Going in to head today
- Re: HEADS UP: SUJ Going in to head today - panic on rename()
- From: Vladimir Grebenschikov
- Re: HEADS UP: SUJ Going in to head today
- Re: HEADS UP: SUJ Going in to head today
- Re: usb/da vs sata geometry calculations (was Re: Switchover to CAM ATA?)
- Re: Switchover to CAM ATA?
- Re: net/mpd5, ppp, proxy-arp issues
- Re: New IPv6 settings in rc.conf
- Re: Switchover to CAM ATA?
- Re: Switchover to CAM ATA?
- Re: New IPv6 settings in rc.conf
- Re: Switchover to CAM ATA?
- Re: SVN rev 206755 breakage
- Re: HEADS UP: SUJ Going in to head today
- Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
- Re: HEADS UP: SUJ Going in to head today
- Re: HEADS UP: SUJ Going in to head today
- Re: Switchover to CAM ATA?
- Re: kern+world / ports make options
- State of tun(4) in -CURRENT? No buffer space available
- Re: HEADS UP: SUJ Going in to head today
- Re: kern+world / ports make options
- sysinstall core dumps when using gsched
- Re: Switchover to CAM ATA?
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- usb/da vs sata geometry calculations (was Re: Switchover to CAM ATA?)
- Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
- Re: New IPv6 settings in rc.conf
- Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
- Re: HEADS UP: SUJ Going in to head today
- Re: HEADS UP: SUJ Going in to head today
- Re: New IPv6 settings in rc.conf
- Re: HEADS UP: SUJ Going in to head today
- New IPv6 settings in rc.conf
- Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
- Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
- Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
- Re: kern+world / ports make options
- HEADS UP: SUJ Going in to head today
- Re: Switchover to CAM ATA?
- Re: kern+world / ports make options
- kern+world / ports make options
- Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
- Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
- Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
- From: Hans Petter Selasky
- Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
- Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
- Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
- 9-CURRENT panic
- Re: newsyslog patch implementing file includes
- Re: newsyslog patch implementing file includes
- Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
- From: James R. Van Artsdalen
- Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
- Re: Switchover to CAM ATA?
- Re: IPv6 configuration in rc.d
- Re: Switchover to CAM ATA?
- Re: Switchover to CAM ATA?
- Re: Switchover to CAM ATA?
- Re: IPv6 configuration in rc.d
- Re: Switchover to CAM ATA?
- Re: Switchover to CAM ATA?
- Re: Switchover to CAM ATA?
- Re: Switchover to CAM ATA?
- Re: Switchover to CAM ATA?
- Re: Switchover to CAM ATA?
- Re: MCA messages in /var/log/message?
- Re: Switchover to CAM ATA?
- Re: Switchover to CAM ATA?
- Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
- Re: Switchover to CAM ATA?
- Re: Switchover to CAM ATA?
- Re: Switchover to CAM ATA?
- Re: HEADS UP: SUJ Going in to head today
- Re: Switchover to CAM ATA?
- Re: Switchover to CAM ATA?
- Re: Switchover to CAM ATA?
- Re: Switchover to CAM ATA?
- Re: Switchover to CAM ATA?
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: MCA messages in /var/log/message?
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: MCA messages in /var/log/message?
- MCA messages in /var/log/message?
- Re: Switchover to CAM ATA?
- Re: FreeBSD kernel doesn't boot on FUJITSU PRIMERGY RX200 S5 server
- Re: Switchover to CAM ATA?
- Re: FreeBSD kernel doesn't boot on FUJITSU PRIMERGY RX200 S5 server
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: Switchover to CAM ATA?
- Re: Switchover to CAM ATA?
- Re: FreeBSD kernel doesn't boot on FUJITSU PRIMERGY RX200 S5 server
- Re: newsyslog patch implementing file includes
- Re: Re: Switchover to CAM ATA?
- Re: Switchover to CAM ATA?
- Re: Switchover to CAM ATA?
- Re: Switchover to CAM ATA?
- Re: Switchover to CAM ATA?
- Re: Switchover to CAM ATA?
- FreeBSD Status Report January-March, 2010
- Re: Switchover to CAM ATA?
- Switchover to CAM ATA?
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: newsyslog patch implementing file includes
- Re: FreeBSD kernel doesn't boot on FUJITSU PRIMERGY RX200 S5 server
- Re: newsyslog patch implementing file includes
- Re: FreeBSD kernel doesn't boot on FUJITSU PRIMERGY RX200 S5 server
- Re: newsyslog patch implementing file includes
- Re: Does "makeoptions WITH_CTF=yes" actually work?
- From: Alexander Leidinger
- Re: Does "makeoptions WITH_CTF=yes" actually work?
- Re: Does "makeoptions WITH_CTF=yes" actually work?
- From: Alexander Leidinger
- Re: newsyslog patch implementing file includes
- Re: newsyslog patch implementing file includes
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- newsyslog patch implementing file includes
- Re: Does "makeoptions WITH_CTF=yes" actually work?
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- SYSCTL_XXX(9) manual page deficiency
- Re: FreeBSD kernel doesn't boot on FUJITSU PRIMERGY RX200 S5 server
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: ANY-ONE-ELSE? ntpd+oncore+i386 doesn't work
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: FreeBSD kernel doesn't boot on FUJITSU PRIMERGY RX200 S5 server
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: HEADS UP: SUJ Going in to head today
- Re: ZFS DEADLKRES - AHCI blocks on ICH7M
- [head tinderbox] failure on i386/pc98
- Re: ANY-ONE-ELSE? ntpd+oncore+i386 doesn't work
- Re: ANY-ONE-ELSE? ntpd+oncore+i386 doesn't work
- ANY-ONE-ELSE? ntpd+oncore+i386 doesn't work
- Re: HEADS UP: SUJ Going in to head today
- Re: HEADS UP: SUJ Going in to head today
- Re: FreeBSD kernel doesn't boot on FUJITSU PRIMERGY RX200 S5 server
- Re: FreeBSD kernel doesn't boot on FUJITSU PRIMERGY RX200 S5 server
- Re: FreeBSD kernel doesn't boot on FUJITSU PRIMERGY RX200 S5 server
- Re: FreeBSD kernel doesn't boot on FUJITSU PRIMERGY RX200 S5 server
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- From: Mehmet Erol Sanliturk
- Re: FreeBSD kernel doesn't boot on FUJITSU PRIMERGY RX200 S5 server
- Re: FreeBSD kernel doesn't boot on FUJITSU PRIMERGY RX200 S5 server
- [head tinderbox] failure on amd64/amd64
- Re: HEADS UP: SUJ Going in to head today
- [head tinderbox] failure on i386/i386
- Re: HEADS UP: SUJ Going in to head today
- [head tinderbox] failure on i386/pc98
- Re: FreeBSD kernel doesn't boot on FUJITSU PRIMERGY RX200 S5 server
- HEADS UP: SUJ Going in to head today
- Re: FreeBSD kernel doesn't boot on FUJITSU PRIMERGY RX200 S5 server
- Re: FreeBSD kernel doesn't boot on FUJITSU PRIMERGY RX200 S5 server
- Re: Strange disk problem
- Re: ZFS behavior when device disappears
- From: Jason J. W. Williams
- Re: ZFS behavior when device disappears
- From: Pawel Jakub Dawidek
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: FreeBSD kernel doesn't boot on FUJITSU PRIMERGY RX200 S5 server
- Re: ZFS behavior when device disappears
- From: Jason J. W. Williams
- [head tinderbox] failure on i386/pc98
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: FreeBSD kernel doesn't boot on FUJITSU PRIMERGY RX200 S5 server
- Re: Strange disk problem
- Re: panic: deadlkres: possible deadlock detected
- newsyslog patch implementing file includes
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: Does "makeoptions WITH_CTF=yes" actually work?
- From: Alexander Leidinger
- [head tinderbox] failure on powerpc/powerpc
- Re: net/mpd5, ppp, proxy-arp issues
- Re: FreeBSD kernel doesn't boot on FUJITSU PRIMERGY RX200 S5 server
- FreeBSD kernel doesn't boot on FUJITSU PRIMERGY RX200 S5 server
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- [head tinderbox] failure on i386/pc98
- [head tinderbox] failure on i386/i386
- Strange disk problem
- Re: panic: deadlkres: possible deadlock detected
- Re: ZFS behavior when device disappears
- From: Pawel Jakub Dawidek
- Re: net/mpd5, ppp, proxy-arp issues
- Re: panic: deadlkres: possible deadlock detected
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: ISO9660 4GB directory structures boundary limit and growisofs
- Re: panic: deadlkres: possible deadlock detected
- panic: deadlkres: possible deadlock detected
- Re: ISO9660 4GB directory structures boundary limit and growisofs
- Re: ISO9660 4GB directory structures boundary limit and growisofs
- Re: ISO9660 4GB directory structures boundary limit and growisofs
- Re: Does "makeoptions WITH_CTF=yes" actually work?
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: SVN rev 206755 breakage
- Re: SVN rev 206755 breakage
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: IPv6 configuration in rc.d
- Re: IPv6 configuration in rc.d
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: Re: SVN rev 206755 breakage
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: SPOOFED: Re: SVN rev 206755 breakage
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: SPOOFED: Re: SVN rev 206755 breakage
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: SPOOFED: Re: SVN rev 206755 breakage
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: SPOOFED: Re: SVN rev 206755 breakage
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: SPOOFED: Re: SVN rev 206755 breakage
- Re: SVN rev 206755 breakage
- Re: SVN rev 206755 breakage
- Re: SVN rev 206755 breakage
- IPv6 configuration in rc.d (Was: Re: svn commit: r206408 ...)
- SVN rev 206755 breakage
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- From: James R. Van Artsdalen
- Re: ISO9660 4GB directory structures boundary limit and growisofs
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: ISO9660 4GB directory structures boundary limit and growisofs
- Re: svn commit: r206408 - in head: etc etc/defaults etc/rc.d share/man/man5
- Re: HP, IBM and Supermicro Servers Compatibility.
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: ISO9660 4GB directory structures boundary limit and growisofs
- Re: ISO9660 4GB directory structures boundary limit and growisofs
- Re: fix for compressed coredumps, please review
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- fix for compressed coredumps, please review
- Re: svn commit: r206408 - in head: etc etc/defaults etc/rc.d share/man/man5
- ISO9660 4GB directory structures boundary limit and growisofs
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: HP, IBM and Supermicro Servers Compatibility.
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- Re: [CFT]: ClangBSD is selfhosting, we need testers now
- [CFT]: ClangBSD is selfhosting, we need testers now
- Re: Does "makeoptions WITH_CTF=yes" actually work?
- From: Alexander Leidinger
- Re: Cross compilling kernel i386/amd64 is failed
- Re: Cross compilling kernel i386/amd64 is failed
- Re: Cross compilling kernel i386/amd64 is failed
- Re: Malloc_init: Bad Malloc type Magic
- Malloc_init: Bad Malloc type Magic
- Re: Cross compilling kernel i386/amd64 is failed
- Re: Cross compilling kernel i386/amd64 is failed
- Cross compilling kernel i386/amd64 is failed
- Re: HP, IBM and Supermicro Servers Compatibility.
- HP, IBM and Supermicro Servers Compatibility.
- Re: Call for testers: SiS190/191 Fast/Gigabit ethernet controller
- Re: HEADS UP: COMPAT_IA32 renamed COMPAT_FREEBSD32
- Re: HEADS UP: COMPAT_IA32 renamed COMPAT_FREEBSD32
- Re: HEADS UP: COMPAT_IA32 renamed COMPAT_FREEBSD32
- Re: Does "makeoptions WITH_CTF=yes" actually work?
- From: Alexander Leidinger
- Re: HEADS UP: COMPAT_IA32 renamed COMPAT_FREEBSD32
- Re: Virtualbox
- Re: Does "makeoptions WITH_CTF=yes" actually work?
- Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
- Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
- Re: [RFC] Rewriting sade(8)
- Re: [RFC] Rewriting sade(8)
- Re: Does "makeoptions WITH_CTF=yes" actually work?
- From: Alexander Leidinger
- Re: Can't get freebsd running on an opteron board
- Re: Does "makeoptions WITH_CTF=yes" actually work?
- Re: Does "makeoptions WITH_CTF=yes" actually work?
- From: Alexander Leidinger
- Does "makeoptions WITH_CTF=yes" actually work?
- Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
- ZFS behavior when device disappears
- From: Jason J. W. Williams
- Re: svn commit: r206497 - in head: sbin/geom/class sbin/geom/class/sched sys/geom/sched sys/modules/geom sys/modules/geom/geom_sched sys/modules/geom/geom_sched/gs_sched sys/modules/geom/geom_sched/gsc...
- Re: svn commit: r206497 - in head: sbin/geom/class sbin/geom/class/sched sys/geom/sched sys/modules/geom sys/modules/geom/geom_sched sys/modules/geom/geom_sched/gs_sched sys/modules/geom/geom_sched/gsc...
- Re: Can't get freebsd running on an opteron board
- Re: ports and PBIs
- Can't get freebsd running on an opteron board
- Re: svn commit: r206497 - in head: sbin/geom/class sbin/geom/class/sched sys/geom/sched sys/modules/geom sys/modules/geom/geom_sched sys/modules/geom/geom_sched/gs_sched sys/modules/geom/geom_sched/gsc...
- Re: Trivial PR, fix shutdown of rc services started with onestart
- Re: svn commit: r206497 - in head: sbin/geom/class sbin/geom/class/sched sys/geom/sched sys/modules/geom sys/modules/geom/geom_sched sys/modules/geom/geom_sched/gs_sched sys/modules/geom/geom_sched/gsc...
- Re: ports and PBIs
- Re: Removing USB keyboard after filesystems synced causes panic with destroyed mutex twa(4)?
- Re: SIGSEGV in dc, at bcode.c:277 (function reset_bmachine())
- Re: ports and PBIs
- Re: Removing USB keyboard after filesystems synced causes panic with destroyed mutex twa(4)?
- Re: Removing USB keyboard after filesystems synced causes panic with destroyed mutex twa(4)?
- Re: SIGSEGV in dc, at bcode.c:277 (function reset_bmachine())
- Re: SIGSEGV in dc, at bcode.c:277 (function reset_bmachine())
- [head tinderbox] failure on sparc64/sun4v
- [head tinderbox] failure on sparc64/sparc64
- [head tinderbox] failure on powerpc/powerpc
- [head tinderbox] failure on ia64/ia64
- [head tinderbox] failure on amd64/amd64
- [head tinderbox] failure on i386/i386
- [head tinderbox] failure on i386/pc98
- Re: Trivial PR, fix shutdown of rc services started with onestart
- Re: Trivial PR, fix shutdown of rc services started with onestart
- Re: LOR on em in HEAD ( was Re: em driver regression
- Re: Trivial PR, fix shutdown of rc services started with onestart
- Re: LOR on em in HEAD ( was Re: em driver regression
- Re: Trivial PR, fix shutdown of rc services started with onestart
- Re: Trivial PR, fix shutdown of rc services started with onestart
- Re: LOR on em in HEAD ( was Re: em driver regression
- Re: Trivial PR, fix shutdown of rc services started with onestart
- Re: When will we can use ZFS v24?
- Re: ports and PBIs
- Re: When will we can use ZFS v24?
- Re: ipfw bug on i386
- Re: ipfw bug on i386
- Re: ipfw bug on i386
- Re: ipfw bug on i386
- Re: ipfw bug on i386
- Re: ipfw bug on i386
- Re: ports and PBIs
- Re: ports and PBIs
- Re: ports and PBIs
- Re: ports and PBIs
- Re: ports and PBIs
- Re: ports and PBIs
- Re: ports and PBIs
- Re: ports and PBIs
- Re: ports and PBIs
- Re: ports and PBIs
- ipfw bug on i386
- Re: ports and PBIs
- Re: ports and PBIs
- boot process gets weirdly interrupted when using scroll lock
- Re: ports and PBIs
- From: Mehmet Erol Sanliturk
- SIGSEGV in dc, at bcode.c:277 (function reset_bmachine())
- Re: LOR on em in HEAD ( was Re: em driver regression
- Re: ports and PBIs
- Re: ports and PBIs
- Re: ports and PBIs
- Re: LOR on em in HEAD ( was Re: em driver regression
- Re: ports and PBIs
- Re: code.google -> Xpra (anyone planning to port it ?)
- Re: ports and PBIs
- Re: ports and PBIs
- Re: ports and PBIs
- Re: LOR on em in HEAD ( was Re: em driver regression
- Re: ports and PBIs
- Re: ports and PBIs
- Re: [RFC] Rewriting sade(8)
- From: Dag-Erling Smørgrav
- Re: LOR on em in HEAD ( was Re: em driver regression
- Re: LOR on em in HEAD ( was Re: em driver regression
- Re: ports and PBIs
- Re: ports and PBIs
- Re: ports and PBIs
- Re: ports and PBIs
- Re: ports and PBIs
- Re: ports and PBIs
- Trivial PR, fix shutdown of rc services started with onestart
- [head tinderbox] failure on sparc64/sun4v
- [head tinderbox] failure on ia64/ia64
- Re: ports and PBIs
- [head tinderbox] failure on sparc64/sparc64
- [head tinderbox] failure on powerpc/powerpc
- Re: ports and PBIs
- [head tinderbox] failure on amd64/amd64
- [head tinderbox] failure on i386/i386
- [head tinderbox] failure on i386/pc98
- Re: ports and PBIs
- ports and PBIs
- Re: BIND from system and from ports
- Re: r206358/r206369 prevent me from connecting via wpi0
- Re: LOR on em in HEAD ( was Re: em driver regression
- Re: LOR on em in HEAD ( was Re: em driver regression
- Re: LOR on em in HEAD ( was Re: em driver regression
- Re: LOR on em in HEAD ( was Re: em driver regression
- Re: Re: [RFC] Rewriting sade(8)
- Re: LOR on em in HEAD ( was Re: em driver regression
- LOR on em in HEAD ( was Re: em driver regression
- Re: [RFC] Rewriting sade(8)
- Re: When will we can use ZFS v24?
- Re: ZFS boot problems with memory > 1MB
- Re: [RFC] Rewriting sade(8)
- Re: ZFS boot problems with memory > 1MB
- Re: gpart and sector size
- Re: gpart and sector size
- Re: ZFS raidz and 4k sector disks
- Re: gpart and sector size
- Re: gpart and sector size
- Re: gpart and sector size
- Re: gpart and sector size
- Re: gpart and sector size
- Re: gpart and sector size
- Re: gpart and sector size
- Re: gpart and sector size
- From: Dag-Erling Smørgrav
- Re: [RFC] Rewriting sade(8)
- From: Dag-Erling Smørgrav
- Re: gpart and sector size
- Re: gpart and sector size
- Re: ZFS raidz and 4k sector disks
- Re: ZFS boot problems with memory > 1MB
- Re: gpart and sector size
- Re: [RFC] Rewriting sade(8)
- Re: load ipfw table addresses from file
- Re: [RFC] Rewriting sade(8)
- From: Dag-Erling Smørgrav
- Re: load ipfw table addresses from file
- Re: load ipfw table addresses from file
- Re: load ipfw table addresses from file
- Re: [RFC] Rewriting sade(8)
- From: Alexander Leidinger
- load ipfw table addresses from file
- Re: When will we can use ZFS v24?
- Re: ipv6_enable
- Re: ipv6_enable
- r206358/r206369 prevent me from connecting via wpi0
- Re: When will we can use ZFS v24?
- Re: When will we can use ZFS v24?
- Re: gpart and sector size
- Re: [RFC] Rewriting sade(8)
- Re: gpart and sector size
- Re: [RFC] Rewriting sade(8)
- Re: [RFC] Rewriting sade(8)
- Re: gpart and sector size
- Re: [RFC] Rewriting sade(8)
- Re: gpart and sector size
- Re: [RFC] Rewriting sade(8)
- Re: [RFC] Rewriting sade(8)
- From: Dag-Erling Smørgrav
- Re: [RFC] Rewriting sade(8)
- Re: [RFC] Rewriting sade(8)
- Re: [RFC] Rewriting sade(8)
- Re: [RFC] Rewriting sade(8)
- Re: [RFC] Rewriting sade(8)
- Re: [RFC] Rewriting sade(8)
- Re: When will we can use ZFS v24?
- Re: gpart and sector size
- Re: gpart and sector size
- Re: [RFC] Rewriting sade(8)
- Re: ZFS DEADLKRES
- Re: [RFC] Rewriting sade(8)
- From: Dag-Erling Smørgrav
- Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
- Re: gpart and sector size
- Re: [RFC] Rewriting sade(8)
- From: Alexander Leidinger
- Re: gpart and sector size
- From: Dag-Erling Smørgrav
- Re: gpart and sector size
- Re: gpart and sector size
- From: Dag-Erling Smørgrav
- Re: [RFC] Rewriting sade(8)
- From: Dag-Erling Smørgrav
- Re: [RFC] Rewriting sade(8)
- From: Dag-Erling Smørgrav
- Re: gpart and sector size
- Re: gpart and sector size
- From: Dag-Erling Smørgrav
- Re: [RFC] Rewriting sade(8)
- Re: [RFC] Rewriting sade(8)
- Re: [RFC] Rewriting sade(8)
- From: Alexander Leidinger
- Re: gpart and sector size
- Re: gpart and sector size
- From: Dag-Erling Smørgrav
- buildworld fails building _dtrace_tools
- gpart and sector size
- Re: [RFC] Rewriting sade(8)
- From: Dag-Erling Smørgrav
- Re: [RFC] Rewriting sade(8)
- From: Dag-Erling Smørgrav
- Re: [RFC] Rewriting sade(8)
- Re: [RFC] Rewriting sade(8)
- Re: [RFC] Rewriting sade(8)
- From: Svein Skogen (Listmail Account)
- Re: [RFC] Rewriting sade(8)
- From: Alexander Leidinger
- Re: [RFC] Rewriting sade(8)
- Re: [RFC] Rewriting sade(8)
- From: Dag-Erling Smørgrav
- Re: When will we can use ZFS v24?
- Re: [RFC] Rewriting sade(8)
- From: Alexander Leidinger
- Re: [RFC] Rewriting sade(8)
- Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
- Re: [RFC] Rewriting sade(8)
- Re: [RFC] Rewriting sade(8)
- Re: [RFC] Rewriting sade(8)
- Re: [RFC] Rewriting sade(8)
- Re: HEADS UP: COMPAT_IA32 renamed COMPAT_FREEBSD32
- [head tinderbox] failure on amd64/amd64
- [head tinderbox] failure on i386/i386
- [head tinderbox] failure on i386/pc98
- Re: [RFC] Rewriting sade(8)
- Re: [RFC] Rewriting sade(8)
- Re: When will we can use ZFS v24?
- [RFC] Rewriting sade(8)
- Re: When will we can use ZFS v24?
- Re: BIND from system and from ports
- BIND from system and from ports
- Re: When will we can use ZFS v24?
- Re: When will we can use ZFS v24?
- Re: When will we can use ZFS v24?
- When will we can use ZFS v24?
- Fwd: HEADSUP: Call for FreeBSD Status Reports - 1Q/2010
- Re: atheros ar 9285
- Re: HEADS UP: COMPAT_IA32 renamed COMPAT_FREEBSD32
- atheros ar 9285
- Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
- Re: Samba problems on 8.0-RC2
- Enabling AHCI on ICH7M
- Re: [head tinderbox] failure on ia64/ia64
- Re: [head tinderbox] failure on ia64/ia64
- [head tinderbox] failure on ia64/ia64
- Re: Call for testers: fxp(4) Rx buffer use after free
- Re: ipv6_enable
- Re: HEADS UP: COMPAT_IA32 renamed COMPAT_FREEBSD32
- Re: ipv6_enable
- Re: ipv6_enable
- Re: ipv6_enable
- Re: ipv6_enable
- Re: Ports breakage since r205471
- Re: Ports breakage since r205471
- Re: Ports breakage since r205471
- Re: ipv6_enable
- Re: Ports breakage since r205471
- Re: ipv6_enable
- Re: ipv6_enable
- Re: ipv6_enable
- Re: ipv6_enable
- Re: ipv6_enable
- Re: Ports breakage since r205471
- Re: ipv6_enable
- weird errors or else?
- Re: ipv6_enable
- Re: ipv6_enable
- Re: ipv6_enable
- Re: Ports breakage since r205471
- Call for testers: fxp(4) Rx buffer use after free
- Re: iwi problems on -CURRENT (Apr 4. 2010)
- Re: newfs_msdos and DVD-RAM
- Ports breakage since r205471
- Re: Results of BIND RFC
- Re: HEADSUP: zlib updated [svn commit: r205471 - in head: . lib/libz lib/libz/contrib lib/libz/doc sys/sys]
- Re: ATA_CAM-ed mvsata(4) on OpenRD-client
- From: Norikatsu Shigemura
- Re: FreeBSD 9-CURRENT (and 8.0) on MacMini (rev. 3,1)
- Re: FreeBSD 9-CURRENT (and 8.0) on MacMini (rev. 3,1)
- Re: FreeBSD 9-CURRENT (and 8.0) on MacMini (rev. 3,1)
- FreeBSD 9-CURRENT (and 8.0) on MacMini (rev. 3,1)
- Re: HEADSUP: zlib updated [svn commit: r205471 - in head: . lib/libz lib/libz/contrib lib/libz/doc sys/sys]
- Re: HEADSUP: zlib updated [svn commit: r205471 - in head: . lib/libz lib/libz/contrib lib/libz/doc sys/sys]
- Re: ipv6_enable
- Re: ipv6_enable
- Re: "npxdna in kernel mode!" from VIA_RNG_store
- "npxdna in kernel mode!" from VIA_RNG_store
- Re: samba failed MD5 Checksum
- samba failed MD5 Checksum
- Re: ipv6_enable
- Re: Results of BIND RFC
- Re: ipv6_enable
- panic: vm_fault: fault on nofault entry, addr: c3dce000
- iwi problems on -CURRENT (Apr 4. 2010)
- Re: newfs_msdos and DVD-RAM
- Re: newfs_msdos and DVD-RAM
- Re: newfs_msdos and DVD-RAM
- Re: newfs_msdos and DVD-RAM
- Re: Results of BIND RFC
- Re: ipv6_enable
- Re: bridged wlan/ether still the same
- ipv6_enable
- Re: Results of BIND RFC
- Re: Results of BIND RFC
- Re: Results of BIND RFC
- Re: ia64 -> panic: deadlkres: possible deadlock detected for 0xe00000001187d880, blocked for 1801437 ticks
- ia64 -> panic: deadlkres: possible deadlock detected for 0xe00000001187d880, blocked for 1801437 ticks
- Re: HEADSUP: zlib updated [svn commit: r205471 - in head: . lib/libz lib/libz/contrib lib/libz/doc sys/sys]
- From: Dag-Erling Smørgrav
- Re: Results of BIND RFC
- Re: HEADSUP: zlib updated [svn commit: r205471 - in head: . lib/libz lib/libz/contrib lib/libz/doc sys/sys]
- Re: HEADSUP: zlib updated [svn commit: r205471 - in head: . lib/libz lib/libz/contrib lib/libz/doc sys/sys]
- Re: Results of BIND RFC
- Re: Results of BIND RFC
- Re: eeemon(4) in current
- Re: Results of BIND RFC
- Re: newfs_msdos and DVD-RAM
- Re: newfs_msdos and DVD-RAM
- Re: Results of BIND RFC
- Re: Results of BIND RFC
- Re: Results of BIND RFC
- Re: eeemon(4) in current
- Re: Results of BIND RFC
- Re: Results of BIND RFC
- Re: Results of BIND RFC
- Re: Results of BIND RFC
- Re: Results of BIND RFC
- Re: Results of BIND RFC
- Re: HEADSUP: zlib updated [svn commit: r205471 - in head: . lib/libz lib/libz/contrib lib/libz/doc sys/sys]
- From: Dag-Erling Smørgrav
- Re: newfs_msdos and DVD-RAM
- Re: newfs_msdos and DVD-RAM
- Re: Results of BIND RFC
- eeemon(4) in current
- Re: Results of BIND RFC
- Re: HEADS-UP: WITH_CTF now picked up from src.conf/make.conf/kernel-config
- Re: Results of BIND RFC
- Re: Results of BIND RFC
- Re: Results of BIND RFC
- Re: HEADSUP: zlib updated [svn commit: r205471 - in head: . lib/libz lib/libz/contrib lib/libz/doc sys/sys]
- Re: Results of BIND RFC
- Re: Results of BIND RFC
- Re: bridged wlan/ether still the same
- Re: bridged wlan/ether still the same
- Re: HEADSUP: zlib updated [svn commit: r205471 - in head: . lib/libz lib/libz/contrib lib/libz/doc sys/sys]
- HEADS-UP: WITH_CTF now picked up from src.conf/make.conf/kernel-config
- From: Alexander Leidinger
- Re: Results of BIND RFC
- Re: Results of BIND RFC
- Re: HEADSUP: zlib updated [svn commit: r205471 - in head: . lib/libz lib/libz/contrib lib/libz/doc sys/sys]
- Re: Results of BIND RFC
- Re: Results of BIND RFC
- bridged wlan/ether still the same
- Re: Results of BIND RFC
- Results of BIND RFC
- Re: HEADSUP: zlib updated [svn commit: r205471 - in head: . lib/libz lib/libz/contrib lib/libz/doc sys/sys]
- From: Dag-Erling Smørgrav
- Re: gpart failing with no such geom after gpt corruption
- Re: HEADSUP: zlib updated [svn commit: r205471 - in head: . lib/libz lib/libz/contrib lib/libz/doc sys/sys]
- Re: gpart failing with no such geom after gpt corruption
- Re: HEADSUP: zlib updated [svn commit: r205471 - in head: . lib/libz lib/libz/contrib lib/libz/doc sys/sys]
- Re: gpart failing with no such geom after gpt corruption
- Re: gpart failing with no such geom after gpt corruption
- Re: gpart failing with no such geom after gpt corruption
- Re: Re: Intel H55 and em0
- From: Jan Henrik Sylvester
- Re: gpart failing with no such geom after gpt corruption
- Re: gpart failing with no such geom after gpt corruption
- Re: Intel H55 and em0
- Re: Re: Intel H55 and em0
- Re: gpart failing with no such geom after gpt corruption
- Re: Intel H55 and em0
- Re: Intel H55 and em0
- gpart failing with no such geom after gpt corruption
- Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
- Re: Intel H55 and em0
- Re: Intel H55 and em0
- Intel H55 and em0
- Re: HEADSUP: zlib updated [svn commit: r205471 - in head: . lib/libz lib/libz/contrib lib/libz/doc sys/sys]
- Re: HEADSUP: zlib updated [svn commit: r205471 - in head: . lib/libz lib/libz/contrib lib/libz/doc sys/sys]
- [head tinderbox] failure on amd64/amd64
- [head tinderbox] failure on i386/i386
- [head tinderbox] failure on i386/pc98
