Current-Users by thread

• Date Index
• Date Index (newest page)
• Old Index

• Networking issues with NetBSD-8 on Supermicro with, Brian Buhrow
  • <Possible follow-ups>
  • Re: Networking issues with NetBSD-8 on Supermicro , David H. Gutteridge
• distrib/sets/sets.subr rev.1.181 fails build, Adam
  • Re: distrib/sets/sets.subr rev.1.181 fails build, Robert Elz
• Build failing on new gdb?, Tom Ivar Helbekkmo
• amd64 stuck in tstile, Patrick Welche
  • Re: amd64 stuck in tstile, Hisashi T Fujinaka
    • Re: amd64 stuck in tstile, Patrick Welche
      • Re: amd64 stuck in tstile, Hisashi T Fujinaka
  • Re: amd64 stuck in tstile, Aaron J. Grier
    • Re: amd64 stuck in tstile, Christos Zoulas
• latest 'config' creates broken "ioconf.c" w/some c, John D. Baker
  • Re: latest 'config' creates broken "ioconf.c" w/so, John D. Baker
    • Re: latest 'config' creates broken "ioconf.c" w/so, John D. Baker
    • Re: latest 'config' creates broken "ioconf.c" w/so, John D. Baker
  • Re: latest 'config' creates broken "ioconf.c" w/so, John D. Baker
  • Re: latest 'config' creates broken "ioconf.c" w/so, John D. Baker
    • Re: latest 'config' creates broken "ioconf.c" w/so, John D. Baker
      • Re: latest 'config' creates broken "ioconf.c" w/so, John D. Baker
• Another pmap panic, Chavdar Ivanov
  • <Possible follow-ups>
  • Another pmap panic, Chavdar Ivanov
    • Re: Another pmap panic, Andrew Doran
      • Re: Another pmap panic, Chavdar Ivanov
  • Re: Another pmap panic, MLH
  • Re: Another pmap panic, MLH
• os-test, Thomas Klausner
• cross-compiling ARM img question, bch
  • Re: cross-compiling ARM img question, Robert Elz
    • Re: cross-compiling ARM img question, bch
    • Re: cross-compiling ARM img question, Robert Elz
      • Re: cross-compiling ARM img question, bch
      • Re: cross-compiling ARM img question, bch
      • Re: cross-compiling ARM img question, Chavdar Ivanov
  • Re: cross-compiling ARM img question, bch
  • Re: cross-compiling ARM img question, Robert Elz
    • Re: cross-compiling ARM img question, Robert Elz
    • Re: cross-compiling ARM img question, bch
• Panic in Xen DomU when dumping a WAPBL enabled FFS, Matthias Petermann
• ThinkPad sleep issues current kernel, Riccardo Mottola
• poll, bozohttp and rump, Patrick Welche
  • Re: poll, bozohttp and rump, Patrick Welche
• Kernel RNG "23504 8 17" runs test FAILURE: too man, Thomas Klausner
• Custom kernel builds failing w/undeclared identifi, John D. Baker
  • Re: Custom kernel builds failing w/undeclared iden, Paul Goyette
    • Re: Custom kernel builds failing w/undeclared iden, Paul Goyette
      • Re: Custom kernel builds failing w/undeclared iden, John D. Baker
      • Re: Custom kernel builds failing w/undeclared iden, Robert Elz
      • Re: Custom kernel builds failing w/undeclared iden, Christos Zoulas
      • Re: Custom kernel builds failing w/undeclared iden, John D. Baker
• libsigsegv self test hanging, Thomas Klausner
  • Re: libsigsegv self test hanging, maya
    • Re: libsigsegv self test hanging, Thomas Klausner
• panic by "acpidump -dt" on -current(Nov 22), Kengo NAKAHARA
  • Re: panic by "acpidump -dt" on -current(Nov 22), Chavdar Ivanov
    • Re: panic by "acpidump -dt" on -current(Nov 22), Chavdar Ivanov
      • Re: panic by "acpidump -dt" on -current(Nov 22), Chavdar Ivanov
      • Re: panic by "acpidump -dt" on -current(Nov 22), Christos Zoulas
      • Re: panic by "acpidump -dt" on -current(Nov 22), Kengo NAKAHARA
• I love Fortune && bsd-games, Swift Griggs
• iwn failure on -current (XEN3_DOM0), Chavdar Ivanov
  • Re: iwn failure on -current (XEN3_DOM0), Michael van Elst
    • Re: iwn failure on -current (XEN3_DOM0), Chavdar Ivanov
      • Re: iwn failure on -current (XEN3_DOM0), maya
      • Re: iwn failure on -current (XEN3_DOM0), Chavdar Ivanov
      • Re: iwn failure on -current (XEN3_DOM0), Chavdar Ivanov
      • Re: iwn failure on -current (XEN3_DOM0), Michael van Elst
      • Re: iwn failure on -current (XEN3_DOM0), Chavdar Ivanov
• Remove fortune quotes attributed to or providing a, Rhialto
  • Re: Remove fortune quotes attributed to or providi, Kamil Rytarowski
  • Re: Remove fortune quotes attributed to or providi, Chavdar Ivanov
    • Re: Remove fortune quotes attributed to or providi, Andy Ruhl
      • Re: Remove fortune quotes attributed to or providi, Jaromír Doleček
      • Re: Remove fortune quotes attributed to or providi, Chavdar Ivanov
      • Re: Remove fortune quotes attributed to or providi, William D. Jones
      • Re: Remove fortune quotes attributed to or providi, David Holland
  • Re: Remove fortune quotes attributed to or providi, Hauke Fath
    • Re: Remove fortune quotes attributed to or providi, Rhialto
      • Re: Remove fortune quotes attributed to or providi, Joerg Sonnenberger
      • Re: Remove fortune quotes attributed to or providi, Harry Waddell
      • Re: Remove fortune quotes attributed to or providi, Hauke Fath
      • Re: Remove fortune quotes attributed to or providi, Kamil Rytarowski
      • Re: Remove fortune quotes attributed to or providi, John Nemeth
      • Re: Remove fortune quotes attributed to or providi, Steffen Nurpmeso
      • Re: Remove fortune quotes attributed to or providi, Steffen Nurpmeso
      • Re: Remove fortune quotes attributed to or providi, Steffen Nurpmeso
  • Re: Remove fortune quotes attributed to or providi, maya
    • Re: Remove fortune quotes attributed to or providi, Tom Ivar Helbekkmo
    • Re: Remove fortune quotes attributed to or providi, John Nemeth
      • Re: Remove fortune quotes attributed to or providi, coypu
  • Re: Remove fortune quotes attributed to or providi, Joerg Sonnenberger
    • Re: Remove fortune quotes attributed to or providi, William D. Jones
      • Re: Remove fortune quotes attributed to or providi, Joerg Sonnenberger
      • Re: Remove fortune quotes attributed to or providi, Andy Ruhl
      • Re: Remove fortune quotes attributed to or providi, Hisashi T Fujinaka
      • Re: Remove fortune quotes attributed to or providi, Andrew Cagney
      • Re: Remove fortune quotes attributed to or providi, Marc Balmer
      • Re: Remove fortune quotes attributed to or providi, Thomas Mueller
      • Re: Remove fortune quotes attributed to or providi, Ken Hornstein
      • Re: Remove fortune quotes attributed to or providi, Joerg Sonnenberger
      • Re: Remove fortune quotes attributed to or providi, Steffen Nurpmeso
  • Re: Remove fortune quotes attributed to or providi, Steffen Nurpmeso
  • Re: Remove fortune quotes attributed to or providi, David Holland
    • Re: Remove fortune quotes attributed to or providi, Rhialto
      • Re: Remove fortune quotes attributed to or providi, Jan Danielsson
      • Re: Remove fortune quotes attributed to or providi, Andy Ruhl
      • Re: Remove fortune quotes attributed to or providi, maya
      • Re: Remove fortune quotes attributed to or providi, Marc Balmer
      • Re: Remove fortune quotes attributed to or providi, coypu
      • Re: Remove fortune quotes attributed to or providi, Marc Balmer
      • Re: Remove fortune quotes attributed to or providi, coypu
      • Re: Remove fortune quotes attributed to or providi, Marc Balmer
      • Re: Remove fortune quotes attributed to or providi, coypu
      • Re: Remove fortune quotes attributed to or providi, Christos Zoulas
      • Re: Remove fortune quotes attributed to or providi, Rhialto
      • Re: Remove fortune quotes attributed to or providi, Joerg Sonnenberger
      • Re: Remove fortune quotes attributed to or providi, Rhialto
      • Re: Remove fortune quotes attributed to or providi, Andy Ruhl
      • Re: Remove fortune quotes attributed to or providi, Chavdar Ivanov
      • Re: Remove fortune quotes attributed to or providi, Jan Danielsson
      • Re: Remove fortune quotes attributed to or providi, William D. Jones
      • Re: Remove fortune quotes attributed to or providi, John Nemeth
      • Re: Remove fortune quotes attributed to or providi, Paul Goyette
      • Re: Remove fortune quotes attributed to or providi, Andrew Cagney
      • Re: Remove fortune quotes attributed to or providi, Marc Balmer
      • Re: Remove fortune quotes attributed to or providi, trebol
      • Re: Remove fortune quotes attributed to or providi, trebol
      • Re: Remove fortune quotes attributed to or providi, John Nemeth
      • Re: Remove fortune quotes attributed to or providi, Steffen Nurpmeso
• Re: toolchain/52722: config(8) busy-loops, then co, John D. Baker
  • Re: toolchain/52722: config(8) busy-loops, then co, John D. Baker
  • Re: toolchain/52722: config(8) busy-loops, then co, bch
• zfs tests fails, pool related, Manuel Bouyer
  • Re: zfs tests fails, pool related, Christos Zoulas
• New panic with today's kernel, Chavdar Ivanov
• liblto_plugin.so undefined symbol xasprintf, Riccardo Mottola
  • Re: liblto_plugin.so undefined symbol xasprintf, Martin Husemann
• current still unstable, Thomas Klausner
• dump -X of large LVM based FFSv2 with WAPBL panics, Matthias Petermann
  • Re: dump -X of large LVM based FFSv2 with WAPBL pa, Jaromír Doleček
    • Re: dump -X of large LVM based FFSv2 with WAPBL pa, Manuel Bouyer
    • Re: dump -X of large LVM based FFSv2 with WAPBL pa, Matthias Petermann
• anoncvs.netbsd.org, Chavdar Ivanov
  • Re: anoncvs.netbsd.org, Paul Goyette
    • Re: anoncvs.netbsd.org, Chavdar Ivanov
  • Re: anoncvs.netbsd.org, Patrick Welche
    • Re: anoncvs.netbsd.org, Christos Zoulas
      • Re: anoncvs.netbsd.org, Chavdar Ivanov
      • Re: anoncvs.netbsd.org, Patrick Welche
• Compile failure in nand.c, Chavdar Ivanov
  • Re: Compile failure in nand.c, Jared McNeill
    • Re: Compile failure in nand.c, Chavdar Ivanov
      • Re: Compile failure in nand.c, bch
• p5-Module-Build weirdness, Thomas Klausner
  • Re: p5-Module-Build weirdness, Chavdar Ivanov
    • Re: p5-Module-Build weirdness, Chavdar Ivanov
• current build failure (gcc), Riccardo Mottola
• Possible regression in wm(4)?, Jimmy Johansson
  • Re: Possible regression in wm(4)?, Bert Kiers
    • Re: Possible regression in wm(4)?, Kengo NAKAHARA
      • Re: Possible regression in wm(4)?, Bert Kiers
      • Re: Possible regression in wm(4)?, Kengo NAKAHARA
      • Re: Possible regression in wm(4)?, Bert Kiers
      • Re: Possible regression in wm(4)?, Kengo NAKAHARA
      • Re: Possible regression in wm(4)?, Kengo NAKAHARA
      • Re: Possible regression in wm(4)?, Bert Kiers
      • Re: Possible regression in wm(4)?, Bert Kiers
      • Re: Possible regression in wm(4)?, Bert Kiers
      • Re: Possible regression in wm(4)?, Masanobu SAITOH
      • Re: Possible regression in wm(4)?, Bert Kiers
      • Re: Possible regression in wm(4)?, Masanobu SAITOH
      • Re: Possible regression in wm(4)?, Brian Buhrow
      • Re: Possible regression in wm(4)?, Jimmy Johansson
• New amd64 8.99.6 panic, Chavdar Ivanov
  • Re: New amd64 8.99.6 panic, bch
    • Re: New amd64 8.99.6 panic, Iain Hibbert
• netbsd 8 (beta) failing to load ixg device, Derrick Lobo
  • RE: netbsd 8 (beta) failing to load ixg device, Derrick Lobo
  • Re: netbsd 8 (beta) failing to load ixg device, Thor Lancelot Simon
    • RE: netbsd 8 (beta) failing to load ixg device, Derrick Lobo
    • Re: netbsd 8 (beta) failing to load ixg device, Jaromír Doleček
      • Re: netbsd 8 (beta) failing to load ixg device, Masanobu SAITOH
      • RE: netbsd 8 (beta) failing to load ixg device, Derrick Lobo
      • Re: netbsd 8 (beta) failing to load ixg device, Martin Husemann
      • RE: netbsd 8 (beta) failing to load ixg device, Derrick Lobo
      • RE: netbsd 8 (beta) failing to load ixg device, Derrick Lobo
• new fork issues; preventing shutdown, Thomas Klausner
  • Re: new fork issues; preventing shutdown, Simon Burge
  • Re: new fork issues; preventing shutdown, Robert Elz
  • 8.99.6 instability (was Re: new fork issues; preve, Thomas Klausner
• dmesg spam: ahcisata0 port 1: active 2 is 0x400000, Stefan Hertenberger
  • Re: dmesg spam: ahcisata0 port 1: active 2 is 0x40, Martin Husemann
    • Re: dmesg spam: ahcisata0 port 1: active 2 is 0x40, stefan
      • Re: dmesg spam: ahcisata0 port 1: active 2 is 0x40, Martin Husemann
      • Re: dmesg spam: ahcisata0 port 1: active 2 is 0x40, stefan
      • Re: dmesg spam: ahcisata0 port 1: active 2 is 0x40, Jaromír Doleček
      • Re: dmesg spam: ahcisata0 port 1: active 2 is 0x40, Martin Husemann
      • Re: dmesg spam: ahcisata0 port 1: active 2 is 0x40, Stefan Hertenberger
      • Re: dmesg spam: ahcisata0 port 1: active 2 is 0x40, Jaromír Doleček
      • Re: dmesg spam: ahcisata0 port 1: active 2 is 0x40, Stefan Hertenberger
      • Re: dmesg spam: ahcisata0 port 1: active 2 is 0x40, Jaromír Doleček