freebsd-current

• Date Index

---

• Importing clang/LLVM into FreeBSD HEAD, Roman Divacky
  • Re: Importing clang/LLVM into FreeBSD HEAD, Ollivier Robert
    • Re: Importing clang/LLVM into FreeBSD HEAD, Chris Ruiz
  • Re: Importing clang/LLVM into FreeBSD HEAD, Steve Kargl
    • Re: Importing clang/LLVM into FreeBSD HEAD, Roman Divacky
  • Re: Importing clang/LLVM into FreeBSD HEAD, Mike Jakubik
    • Re: Importing clang/LLVM into FreeBSD HEAD, Andrius Morkūnas
    • Re: Importing clang/LLVM into FreeBSD HEAD, Freddie Cash
  • Re: Importing clang/LLVM into FreeBSD HEAD, Bakul Shah
    • Re: Importing clang/LLVM into FreeBSD HEAD, Roman Divacky
      • Re: Importing clang/LLVM into FreeBSD HEAD, M. Warner Losh
      • Re: Importing clang/LLVM into FreeBSD HEAD, Bakul Shah
      • Re: Importing clang/LLVM into FreeBSD HEAD, Mehmet Erol Sanliturk
      • Re: Importing clang/LLVM into FreeBSD HEAD, Garrett Cooper
      • Re: Importing clang/LLVM into FreeBSD HEAD, Alexander Kabaev
      • Re: Importing clang/LLVM into FreeBSD HEAD, Garrett Cooper
  • Re: Importing clang/LLVM into FreeBSD HEAD, Brandon Gooch
• AES NI vs BIOS settings, Xin LI
  • Re: AES NI vs BIOS settings, Kostik Belousov
• ^T reports negative real time..., Robert Watson
• need better POSIX semaphore support, Dmitry Marakasov
  • Re: need better POSIX semaphore support, Kostik Belousov
• [TESTING]: ClangBSD branch needs testing before the import to HEAD, Roman Divacky
  • Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD, Kostik Belousov
    • Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD, Scott Long
      • Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD, Kostik Belousov
      • Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD, Roman Divacky
      • Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD, Kostik Belousov
      • Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD, Roman Divacky
      • Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD, Astrodog
      • Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD, Kostik Belousov
      • Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD, Daniel Nebdal
      • Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD, Ashley Penney
      • Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD, Scott Long
      • Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD, Robert Watson
      • Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD, Daniel Eischen
      • Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD, Matthew Seaman
      • Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD, Attilio Rao
      • Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD, Roman Divacky
      • Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD, Attilio Rao
      • Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD, Roman Divacky
      • Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD, Astrodog
      • Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD, Bruce Cran
  • Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD, Brandon Gooch
    • Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD, Steve Kargl
      • Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD, Dimitry Andric
      • Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD, Steve Kargl
      • Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD, Dimitry Andric
      • Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD, Eitan Adler
      • Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD, Alexander Kabaev
      • Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD, Brandon Gooch
    • Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD, Alexandre \"Sunny\" Kovalenko
      • Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD, Dimitry Andric
      • Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD, Alexandre \"Sunny\" Kovalenko
  • Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD, Erik Cederstrand
  • Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD, Alexandre \"Sunny\" Kovalenko
• Yoics! Just upgraded and cc is (mostly) bus-error-ing on buildworld., Andrew Reilly
  • Re: Yoics! Just upgraded and cc is (mostly) bus-error-ing on buildworld., Andriy Gapon
• Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626)), b. f.
  • Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626)), Doug Barton
    • Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626)), b. f.
      • Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626)), Rui Paulo
      • Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626)), b. f.
      • Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626)), Doug Barton
      • Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626)), Lars Engels
• wpi not working on today's current (r208626), Doug Barton
  • wpa_supplicant (Was: Re: wpi not working on today's current (r208626)), Doug Barton
• clangBSD build error on r208621, Norikatsu Shigemura
  • Re: clangBSD build error on r208621, Norikatsu Shigemura
    • Re: clangBSD build error on r208621, Roman Divacky
• hid_get_item: Number of items truncated to 255, Alban Hertroys
• GPT on amd64 and boot managers, Alban Hertroys
  • Re: GPT on amd64 and boot managers, Michael Reifenberger
    • Re: GPT on amd64 and boot managers, Alban Hertroys
      • Re: GPT on amd64 and boot managers, Andriy Gapon
      • Re: GPT on amd64 and boot managers, Alban Hertroys
      • Re: GPT on amd64 and boot managers, Andriy Gapon
      • Re: GPT on amd64 and boot managers, Michael Reifenberger
  • Re: GPT on amd64 and boot managers, C. P. Ghost
• NIS crankiness at bootup, Garrett Cooper
• SUJ Rocks!, Tim Kientzle
• nvidia-driver 195.22 use horribly broken on amd64 between r206173 and, Garrett Cooper
  • Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and, Vrachnis Ilias-Dimitrios
  • Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and, Alan Cox
    • Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and, Kostik Belousov
      • Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and, Alan Cox
      • Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and, Garrett Cooper
      • Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and, Ryan Stone
      • Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and, Alan Cox
      • Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and, Kostik Belousov
      • Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and, Doug Barton
      • Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and, Doug Barton
      • Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and, Kostik Belousov
      • Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and, Doug Barton
      • Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and, Doug Barton
      • Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and, datastream datastream.freecity
      • Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and, Garrett Cooper
      • Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and, Craig Rodrigues
• No internet with snapshots, Gerd Truschinski
  • Re: No internet with snapshots, Gary Jennejohn
    • Re: No internet with snapshots, Gerd Truschinski
  • Re: No internet with snapshots, Super Biscuit
  • Re: No internet with snapshots, Super Biscuit
  • Re: No internet with snapshots, Gerd Truschinski
• AppleTalk status, Stefan Bethke
  • Re: AppleTalk status, Daniel O'Connor
    • Re: AppleTalk status, Stefan Bethke
      • Re: AppleTalk status, Daniel O'Connor
      • RE: AppleTalk status, Sean Cavanaugh
  • Re: AppleTalk status, Nathan Whitehorn
    • Re: AppleTalk status, Robert N. M. Watson
  • Re: AppleTalk status, Julian Elischer
    • Re: AppleTalk status, Robert N. M. Watson
  • Re: AppleTalk status, Chris Ruiz
• panic: lapic_enable_cmc: missing APIC 0, Ronald van der Pol
  • Re: panic: lapic_enable_cmc: missing APIC 0, John Baldwin
• MROUTING issues (r200287) with multicast routing daemons, Kamigishi Rei
  • Re: MROUTING issues (r200287) with multicast routing daemons, Kamigishi Rei
• gcc segfault: Cannot build virtualbox-ose on 8-STABLE amd64, Bernhard Froehlich
• About 32bit binary on amd64, Kohji Okuno
  • Re: About 32bit binary on amd64, pluknet
    • Re: About 32bit binary on amd64, Garrett Cooper
      • Re: About 32bit binary on amd64, Kohji Okuno
      • Re: About 32bit binary on amd64, Kostik Belousov
• MAKEOBJDIRPREFIX and installkernel, Boris Samorodov
  • Re: MAKEOBJDIRPREFIX and installkernel, Yuri Pankov
    • Re: MAKEOBJDIRPREFIX and installkernel, Boris Samorodov
• clangBSD build error, ambrosehuang ambrose
  • Re: clangBSD build error, Roman Divacky
    • Re: clangBSD build error, Vanilla Hsu
      • Re: clangBSD build error, Roman Divacky
    • Re: clangBSD build error, ambrosehuang ambrose
      • Re: clangBSD build error, Roman Divacky
      • Re: clangBSD build error, ambrosehuang ambrose
      • Re: clangBSD build error, Roman Divacky
      • Re: clangBSD build error, Roman Divacky
• HEAD can't bring up APs on Intel LC5528(Jasper Forest), Ryan Stone
  • Re: HEAD can't bring up APs on Intel LC5528(Jasper Forest), Jack Vogel
    • Re: HEAD can't bring up APs on Intel LC5528(Jasper Forest), Ryan Stone
      • Re: HEAD can't bring up APs on Intel LC5528(Jasper Forest), Jack Vogel
      • Re: HEAD can't bring up APs on Intel LC5528(Jasper Forest), Alexander Kabaev
      • Re: HEAD can't bring up APs on Intel LC5528(Jasper Forest), Ryan Stone
      • Re: HEAD can't bring up APs on Intel LC5528(Jasper Forest), Jack Vogel
      • Re: HEAD can't bring up APs on Intel LC5528(Jasper Forest), Jack Vogel
      • Re: HEAD can't bring up APs on Intel LC5528(Jasper Forest), Ryan Stone
• ffs_copyonwrite panics, Roman Bogorodskiy
  • Re: ffs_copyonwrite panics, Fabian Keil
  • Re: ffs_copyonwrite panics, Jeff Roberson
    • Re: ffs_copyonwrite panics, Roman Bogorodskiy
      • Re: ffs_copyonwrite panics, Jeff Roberson
      • Re: ffs_copyonwrite panics, Roman Bogorodskiy
• make release broken, Rob Farmer
  • Re: make release broken, Garrett Cooper
    • Re: make release broken, jhell
      • Re: make release broken, James R. Van Artsdalen
      • Re: make release broken, Rob Farmer
      • Re: make release broken, James R. Van Artsdalen
      • Re: make release broken, Rob Farmer
  • Re: make release broken, Julian H. Stacey
• SUJ Changes, Jeff Roberson
  • Re: SUJ Changes, Marcelo/Porks
    • Re: SUJ Changes, Marcelo/Porks
      • Re: SUJ Changes, Garrett Cooper
      • Re: SUJ Changes, Mario Lobo
      • Re: SUJ Changes, Garrett Cooper
      • Re: SUJ Changes, John Baldwin
      • Re: SUJ Changes, Marcelo/Porks
      • Re: SUJ Changes, John Baldwin
      • Re: SUJ Changes, Marcelo/Porks
      • Re: SUJ Changes, Garrett Cooper
      • Re: SUJ Changes, Marcelo/Porks
      • Re: SUJ Changes, Garrett Cooper
  • SUJ and "mount" reporting, Ivan Voras
    • Re: SUJ and "mount" reporting, Michael Butler
    • Re: SUJ and "mount" reporting, Bjoern A. Zeeb
      • Re: SUJ and "mount" reporting, Ivan Voras
      • Re: SUJ and "mount" reporting, Scott Long
• Re: SYSCTL_XXX(9) manual page deficiency, Giorgos Keramidas
• an issue with head..., Randall Stewart
• missing /usr/lib/liblzma.a during HEAD buildworld ?, Luigi Rizzo
  • Re: missing /usr/lib/liblzma.a during HEAD buildworld ?, Renato Botelho
• AESNI driver and fpu_kern KPI, Kostik Belousov
  • Re: AESNI driver and fpu_kern KPI, Marius Strobl
    • Re: AESNI driver and fpu_kern KPI, Kostik Belousov
  • Re: AESNI driver and fpu_kern KPI, Pawel Jakub Dawidek
    • Re: AESNI driver and fpu_kern KPI, Kostik Belousov
      • Re: AESNI driver and fpu_kern KPI, Fabien Thomas
• RE: Crash dump problem - sleeping thread owns a non-sleepable lock during crash dump write, Matthew Fleming
  • Re: Crash dump problem - sleeping thread owns a non-sleepable lock during crash dump write, Matthew Jacob
  • RE: Crash dump problem - sleeping thread owns a non-sleepable lock during crash dump write, Terry Kennedy
  • Re: Crash dump problem - sleeping thread owns a non-sleepable lock during crash dump write, John Baldwin
• cpuset at boot time or separating processes by CPU, Sylvio Cesar Teixeira
• kgdb unuseable with cores on current (for some people), Benjamin Kaduk
  • Re: kgdb unuseable with cores on current (for some people), Kostik Belousov
    • Re: kgdb unuseable with cores on current (for some people), Benjamin Kaduk
      • Re: kgdb unuseable with cores on current (for some people), Alan Cox
      • Re: kgdb unuseable with cores on current (for some people), Benjamin Kaduk
      • Re: kgdb unuseable with cores on current (for some people), Benjamin Kaduk
      • Re: kgdb unuseable with cores on current (for some people), Benjamin Kaduk
      • Re: kgdb unuseable with cores on current (for some people), Alan Cox
• GrandCentralDispatch in FreeBSD?, Tom Evans
  • Re: GrandCentralDispatch in FreeBSD?, Christian Brueffer
  • Re: GrandCentralDispatch in FreeBSD?, Brooks Davis
  • Re: GrandCentralDispatch in FreeBSD?, Robert N. M. Watson
• dc(1) -e "6 2 / p" is still broken as of r207919, Alexey Shuvaev
• [mini headsup] updating from 7.x to -CURRENT after lzma import, Xin LI
  • Re: [mini headsup] updating from 7.x to -CURRENT after lzma import, Kostik Belousov
  • Re: [mini headsup] updating from 7.x to -CURRENT after lzma import, Tim Kientzle
    • Re: [mini headsup] updating from 7.x to -CURRENT after lzma import, Kai Wang
      • Re: [mini headsup] updating from 7.x to -CURRENT after lzma import, Xin LI
• Re: fsck unable to read disk sectors, Alexander Best
  • Re: fsck unable to read disk sectors, Alexander Best
    • Re: fsck unable to read disk sectors, Bernd Walter
      • Re: fsck unable to read disk sectors, Alexander Best
      • Re: fsck unable to read disk sectors, Matt Thyer
      • Re: fsck unable to read disk sectors, Bernd Walter
      • Re: fsck unable to read disk sectors, Matt Thyer
• Addition of lzma/xz compression to HEAD, Alexey Shuvaev
  • Re: Addition of lzma/xz compression to HEAD, Fabien Thomas
• [PATCH:] psm(4) IntelliMouse Explorer KVM hack breaks my mouse, Juergen Lock
  • Re: [PATCH:] psm(4) IntelliMouse Explorer KVM hack breaks my mouse, Gary Jennejohn
    • Re: [PATCH:] psm(4) IntelliMouse Explorer KVM hack breaks my mouse, Juergen Lock
      • Re: [PATCH:] psm(4) IntelliMouse Explorer KVM hack breaks my mouse, Gary Jennejohn
      • Re: [PATCH:] psm(4) IntelliMouse Explorer KVM hack breaks my mouse, Juergen Lock
• Re: kmem_map too small: 3832475648 total allocated, Bruce Cran
  • Re: kmem_map too small: 3832475648 total allocated, Willem Jan Withagen
• Panic @r207844; current process: flowcleaner "Fatal trap 12: page fault while in kernel mode", David Wolfskill
  • Message not available
    • Re: Panic @r207844; current process: flowcleaner "Fatal trap 12: page fault while in kernel mode", David Wolfskill
      • RE: Panic @r207844; current process: flowcleaner "Fatal trap 12: page fault while inkernel mode", Li, Qing
      • Re: Panic @r207844; current process: flowcleaner "Fatal trap 12: page fault while in kernel mode", K. Macy
      • Re: Panic @r207844; current process: flowcleaner "Fatal trap 12: page fault while in kernel mode", K. Macy
      • Re: Panic @r207844; current process: flowcleaner "Fatal trap 12: page fault while in kernel mode", David Wolfskill
      • Re: Panic @r207844; current process: flowcleaner "Fatal trap 12: page fault while in kernel mode", K. Macy
      • Re: Panic @r207844; current process: flowcleaner "Fatal trap 12: page fault while in kernel mode", David Wolfskill
      • Re: Panic @r207844; current process: flowcleaner "Fatal trap 12: page fault while in kernel mode", David Wolfskill
      • Re: Panic @r207844; current process: flowcleaner "Fatal trap 12: page fault while in kernel mode", David Wolfskill
      • Re: Panic @r207844; current process: flowcleaner "Fatal trap 12: page fault while in kernel mode", K. Macy
      • Re: Panic @r207844; current process: flowcleaner "Fatal trap 12: page fault while in kernel mode", David Wolfskill
      • Re: Panic @r207844; current process: flowcleaner "Fatal trap 12: page fault while in kernel mode", K. Macy
• Today's snapshot is broken, TAKAHASHI Yoshihiro
• a panic on uart_z8530_class?, Weongyo Jeong
  • Re: a panic on uart_z8530_class?, Benjamin Kaduk
    • Re: a panic on uart_z8530_class?, ben wilber
      • Re: a panic on uart_z8530_class?, Brandon Gooch
      • Re: a panic on uart_z8530_class?, Yuri Pankov
      • Re: a panic on uart_z8530_class?, Benjamin Kaduk
      • Re: a panic on uart_z8530_class?, Brandon Gooch
  • Re: a panic on uart_z8530_class?, Kostik Belousov
  • Re: a panic on uart_z8530_class?, Marcel Moolenaar
  • Re: a panic on uart_z8530_class?, Bjoern A. Zeeb
• SC_PIXEL_MODE in GENERIC on i386/amd64?, Anonymous
  • Re: SC_PIXEL_MODE in GENERIC on i386/amd64?, Alex Keda
• LOR: ufs vs bufwait, Ulrich Spörlein
  • Re: LOR: ufs vs bufwait, Ulrich Spörlein
    • Message not available
      • Re: LOR: ufs vs bufwait, Ulrich Spörlein
      • Re: LOR: ufs vs bufwait, Attilio Rao
      • Re: LOR: ufs vs bufwait, Jeff Roberson
      • Re: LOR: ufs vs bufwait, Attilio Rao
  • Re: LOR: ufs vs bufwait, Peter Jeremy
    • Re: LOR: ufs vs bufwait, Attilio Rao
      • Re: LOR: ufs vs bufwait, Ulrich Spörlein
      • Re: LOR: ufs vs bufwait, Jeff Roberson
      • Re: LOR: ufs vs bufwait, Attilio Rao
      • Re: LOR: ufs vs bufwait, Erik Cederstrand
      • Re: LOR: ufs vs bufwait, Jeff Roberson
• LOR: acpi_dock vs sysctl, Ulrich Spörlein
• weekly whatis database and readonly /usr mount, Boris Samorodov
• igb broken? Unexplained weirdness with intel 82576 nics on a supermicro board., joe
  • Re: igb broken? Unexplained weirdness with intel 82576 nics on a supermicro board., joe
  • Message not available
    • Re: igb broken? Unexplained weirdness with intel 82576 nics on a supermicro board., joe
  • Message not available
    • Re: igb broken? Unexplained weirdness with intel 82576 nics on a supermicro board., Ian FREISLICH
      • Re: igb broken? Unexplained weirdness with intel 82576 nics on a supermicro board., joe
      • Re: igb broken? Unexplained weirdness with intel 82576 nics on a supermicro board., Ian FREISLICH
      • Re: igb broken? Unexplained weirdness with intel 82576 nics on a supermicro board., joe
      • Re: igb broken? Unexplained weirdness with intel 82576 nics on a supermicro board., Jack Vogel
      • Re: igb broken? Unexplained weirdness with intel 82576 nics on a supermicro board., joe
      • Re: igb broken? Unexplained weirdness with intel 82576 nics on a supermicro board., Jack Vogel
      • Re: igb broken? Unexplained weirdness with intel 82576 nics on a supermicro board., joe
      • Re: igb broken? Unexplained weirdness with intel 82576 nics on a supermicro board., Jack Vogel
      • Re: igb broken? Unexplained weirdness with intel 82576 nics on a supermicro board., joe
      • Re: igb broken? Unexplained weirdness with intel 82576 nics on a supermicro board., joe
      • Re: igb broken? Unexplained weirdness with intel 82576 nics on a supermicro board., Jack Vogel
      • Re: igb broken? Unexplained weirdness with intel 82576 nics on a supermicro board., Patrick Mahan
  • <Possible follow-ups>
  • igb broken? Unexplained weirdness with intel 82576 nics on a supermicro board., Joe
• PT_ATTACH resumes suspended process, Ben Widawsky
  • Re: PT_ATTACH resumes suspended process, Gary Jennejohn
    • Re: PT_ATTACH resumes suspended process, Ben Widawsky
• if_re regression on RELENG_8, McLone
  • Re: if_re regression on RELENG_8, Pyun YongHyeon
    • Re: if_re regression on RELENG_8, McLone
      • Re: if_re regression on RELENG_8, Pyun YongHyeon
• Re: Problem with reboot, Cy Schubert
  • Re: Problem with reboot, Garrett Cooper
    • Re: Problem with reboot, Garrett Cooper
• HEADS UP: 64-bit quotas going in to head today, Kirk McKusick
  • Re: HEADS UP: 64-bit quotas going in to head today, Ivan Voras
    • Re: HEADS UP: 64-bit quotas going in to head today, Dag-Erling Smørgrav
      • Re: HEADS UP: 64-bit quotas going in to head today, Kostik Belousov
      • Re: HEADS UP: 64-bit quotas going in to head today, Dag-Erling Smørgrav
      • Re: HEADS UP: 64-bit quotas going in to head today, Kostik Belousov
• Revision 205728: broken bluetooth mouse support, Alex Deiter
  • Re: Revision 205728: broken bluetooth mouse support, Kai Wang
    • Re: Revision 205728: broken bluetooth mouse support, Alex Deiter
• Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver, Weongyo Jeong
  • Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver, Attilio Rao
    • Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver, Weongyo Jeong
    • Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver, Tom Uffner
  • Message not available
    • Message not available
      • Message not available
      • Message not available
      • Message not available
      • Message not available
      • Message not available
      • Message not available
      • Message not available
      • Message not available
      • Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver, Ian FREISLICH
  • Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver, Gustavo Perez Querol
    • Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver, Weongyo Jeong
    • Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver, Weongyo Jeong
      • Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver, Gustau Pérez
      • Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver, Weongyo Jeong
      • Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver, Gustau Pérez
      • Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver, Weongyo Jeong
      • Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver, Buganini
      • Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver, Tom Uffner
    • Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver, Ian FREISLICH
    • Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver, Ian FREISLICH
      • Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver, Weongyo Jeong
    • Message not available
      • Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver, Weongyo Jeong
  • <Possible follow-ups>
  • Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver, b. f.
• Help with igb driver/nics, strange issue., joe
  • Message not available
    • Re: Help with igb driver/nics, strange issue., Ian FREISLICH
      • Re: Help with igb driver/nics, strange issue., joe
• Time accounting is all wrong ..., Ulrich Spörlein
  • Re: Time accounting is all wrong ..., Kostik Belousov
• strange svnsync mirror problem., Mark Atkinson
  • Re: strange svnsync mirror problem., Mark Atkinson
• Re: Strange disk problem, Jeremie Le Hen
• Re: unzip in basesystem, Alex Kozlov
• Re: [CFT]: ClangBSD is selfhosting, we need testers now - STATUS UPDATE, Roman Divacky
  • Re: [CFT]: ClangBSD is selfhosting, we need testers now - STATUS UPDATE, Dima Panov
  • Re: [CFT]: ClangBSD is selfhosting, we need testers now - STATUS UPDATE, Doug Barton
• Recent sys/vm/ changes and nvidia-driver, Yuri Pankov
  • Re: Recent sys/vm/ changes and nvidia-driver, Alan Cox
    • Re: Recent sys/vm/ changes and nvidia-driver, Doug Barton
      • Re: Recent sys/vm/ changes and nvidia-driver, Alan Cox
      • Re: Recent sys/vm/ changes and nvidia-driver, Doug Barton
      • Re: Recent sys/vm/ changes and nvidia-driver, Alan Cox
      • Re: Recent sys/vm/ changes and nvidia-driver, Rainer Hurling
  • <Possible follow-ups>
  • Re: Recent sys/vm/ changes and nvidia-driver, b. f.
    • Re: Recent sys/vm/ changes and nvidia-driver, Brandon Gooch
      • Re: Recent sys/vm/ changes and nvidia-driver, Kip Macy
      • Re: Recent sys/vm/ changes and nvidia-driver, b. f.
      • Re: Recent sys/vm/ changes and nvidia-driver, Brandon Gooch
      • Re: Recent sys/vm/ changes and nvidia-driver, b. f.
    • Re: Recent sys/vm/ changes and nvidia-driver, K. Macy
• acpi_hp fails attach at boot, Ian FREISLICH
• unzip in basesystem., David DEMELIER
  • Re: unzip in basesystem., David DEMELIER
    • Re: unzip in basesystem., Rob Farmer
• amdtemp(4) issue, Norikatsu Shigemura
  • Re: amdtemp(4) issue, Jung-uk Kim
    • Re: amdtemp(4) issue, Jung-uk Kim
    • Re: amdtemp(4) issue, Norikatsu Shigemura
• [head tinderbox] failure on ia64/ia64, FreeBSD Tinderbox
  • <Possible follow-ups>
  • [head tinderbox] failure on ia64/ia64, FreeBSD Tinderbox
• [head tinderbox] failure on amd64/amd64, FreeBSD Tinderbox
  • <Possible follow-ups>
  • [head tinderbox] failure on amd64/amd64, FreeBSD Tinderbox
• [head tinderbox] failure on i386/i386, FreeBSD Tinderbox
  • <Possible follow-ups>
  • [head tinderbox] failure on i386/i386, FreeBSD Tinderbox
• [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
  • <Possible follow-ups>
  • [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
  • [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
    • Re: [head tinderbox] failure on i386/pc98, pluknet
      • Re: [head tinderbox] failure on i386/pc98, TAKAHASHI Yoshihiro
  • [head tinderbox] failure on i386/pc98, FreeBSD Tinderbox
• [head tinderbox] failure on arm/arm, FreeBSD Tinderbox
• [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • <Possible follow-ups>
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sun4v, FreeBSD Tinderbox
• [head tinderbox] failure on sparc64/sparc64, FreeBSD Tinderbox
  • <Possible follow-ups>
  • [head tinderbox] failure on sparc64/sparc64, FreeBSD Tinderbox
  • [head tinderbox] failure on sparc64/sparc64, FreeBSD Tinderbox
• [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • <Possible follow-ups>
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
  • [head tinderbox] failure on powerpc/powerpc, FreeBSD Tinderbox
• [head tinderbox] failure on mips/mips, FreeBSD Tinderbox
  • <Possible follow-ups>
  • [head tinderbox] failure on mips/mips, FreeBSD Tinderbox
• Non-SUJ deadlock in -current, Peter Jeremy
• Re: New Marvell SATA driver for testing, Kristof Provost
  • Re: New Marvell SATA driver for testing, Alexander Motin
    • Re: New Marvell SATA driver for testing, Kristof Provost
• SUJ deadlock, Fabien Thomas
  • Re: SUJ deadlock, Mark Atkinson
    • Re: SUJ deadlock, Fabien Thomas
      • Re: SUJ deadlock, Jeff Roberson
      • Re: SUJ deadlock, Jeff Roberson
      • Re: SUJ deadlock, Fabien Thomas
      • Re: SUJ deadlock, Fabien Thomas
      • Re: SUJ deadlock, Jeff Roberson
• Re: Switchover to CAM ATA?, Marius Strobl
• m_getjcl and packet cache, Fabien Thomas
• Unable to establish HE gif0 tunnel, Mark Atkinson
  • Re: Unable to establish HE gif0 tunnel, Chris Ruiz
    • Re: Unable to establish HE gif0 tunnel, Mark Atkinson
      • Re: Unable to establish HE gif0 tunnel, Mark Atkinson
  • Re: Unable to establish HE gif0 tunnel, Doug Barton
• exclusive sleep mutex mskc0 (network driver) r = 0 (0xc32c3690) locked @ /usr/src/sys/dev/msk/if_msk.c:3589, Mark Atkinson
  • Re: exclusive sleep mutex mskc0 (network driver) r = 0 (0xc32c3690) locked @ /usr/src/sys/dev/msk/if_msk.c:3589, Pyun YongHyeon
    • Re: exclusive sleep mutex mskc0 (network driver) r = 0 (0xc32c3690) locked @ /usr/src/sys/dev/msk/if_msk.c:3589, Mark Atkinson
    • Re: exclusive sleep mutex mskc0 (network driver) r = 0 (0xc32c3690) locked @ /usr/src/sys/dev/msk/if_msk.c:3589, John Baldwin
      • Re: exclusive sleep mutex mskc0 (network driver) r = 0 (0xc32c3690) locked @ /usr/src/sys/dev/msk/if_msk.c:3589, Pyun YongHyeon
• Re: SUJ update - new panic - "ffs_copyonwrite: recursive call", Vladimir Grebenschikov
  • Re: SUJ update - new panic - "ffs_copyonwrite: recursive call", Jeff Roberson
  • Re: SUJ update - new panic - "ffs_copyonwrite: recursive call", Jeff Roberson
    • Re: SUJ update - new panic - "ffs_copyonwrite: recursive call", Vladimir Grebenschikov
• Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless, PseudoCylon
  • Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless, Ganbold
    • Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless, PseudoCylon
      • Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless, Ganbold
      • Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless, Hans Petter Selasky
      • Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless, PseudoCylon
      • Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless, Ganbold
      • Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless, PseudoCylon
      • Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless, Ganbold Tsagaankhuu
      • Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless, Ganbold
  • Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless, Ganbold
• Re: SUJ update, Vladimir Grebenschikov
  • <Possible follow-ups>
  • Re: SUJ update, Bruce Cran
    • Re: SUJ update, Jeff Roberson
      • Re: SUJ update, Doug Barton
      • Re: SUJ update, sthaug
      • Re: SUJ update, Alexander Leidinger
      • Re: SUJ update, Ben Kelly
      • Re: SUJ update, sthaug
      • Re: SUJ update, Doug Barton
      • Re: SUJ update, Ed Maste
      • Re: SUJ update, Jeff Roberson
    • Re: SUJ update, Alan Cox
      • Re: SUJ update, Bruce Cran
  • Re: SUJ update, Fabien Thomas
    • Re: SUJ update, Jeff Roberson
      • Re: SUJ update, Fabien Thomas
  • Re: SUJ update, Bruce Cran
• Re: ZFS Stability & MySQL (Comments Requested), Pierre Massat
  • <Possible follow-ups>
  • Re: ZFS Stability & MySQL (Comments Requested), Eirik Øverby
• Re: mpt(4) MPI_EVENT_IR_RESYNC_UPDATE, Marius Strobl
  • Re: mpt(4) MPI_EVENT_IR_RESYNC_UPDATE, pluknet
• if_em.c prevents the 2nd time resuming, Taku YAMAMOTO
  • Followup: if_em.c prevents the 2nd time resuming, Taku YAMAMOTO
    • Re: Followup: if_em.c prevents the 2nd time resuming, Brandon Gooch
    • Re: Followup: if_em.c prevents the 2nd time resuming, Marius Strobl
• Re: ports and PBIs, James Butler
  • Re: ports and PBIs, Kris Moore
    • Re: ports and PBIs, Garrett Cooper
      • Re: ports and PBIs, Reinhard Haller
      • Re: ports and PBIs, Garrett Cooper
      • Re: ports and PBIs, Julian Elischer
      • Re: ports and PBIs, Reinhard Haller
      • Re: ports and PBIs, Garrett Cooper
• Re: Panic @r207433: "System call fork returning with the following locks held", K. Macy
  • Re: Panic @r207433: "System call fork returning with the following locks held", Michael Butler
  • <Possible follow-ups>
  • Re: Panic @r207433: "System call fork returning with the following locks held", Andrew Reilly
    • Re: Panic @r207433: "System call fork returning with the following locks held", K. Macy
      • Re: Panic @r207433: "System call fork returning with the following locks held", Andrew Reilly
• Re: Making IFQ_MAXLEN tunable, Maxim Sobolev
  • Re: Making IFQ_MAXLEN tunable, Bjoern A. Zeeb
  • <Possible follow-ups>
  • Re: Making IFQ_MAXLEN tunable, Gary Jennejohn
    • Re: Making IFQ_MAXLEN tunable, Maxim Sobolev
      • Re: Making IFQ_MAXLEN tunable, Gary Jennejohn

• Security
• UNIX
• Linux
• Coding
• Usenet

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

unix.derkeiler.com  > Mailing-Lists  > FreeBSD  > current  > 2010-05