linux-kernel  

Messages by Thread

• • Re: Duplicate messages Andreas Dilger
• [linux-audio-dev] Ingo's lowlatency-test7-A0 excellent latencies (<1msec), but kernel filesync problems ... Benno Senoner
  • Re: [linux-audio-dev] Ingo's lowlatency-test7-A0 excellent latencies (<1msec), but kernel filesync problems ... Chris Baugher
  • [linux-audio-dev] Re: Ingo's lowlatency-test7-A0 excellent latencies (<1msec), butkernel filesync problems ... Ingo Molnar
• Fix for data corrupting bug (years late) Jari Ruusu
• (reiserfs) Re: More on 2.2.18pre2aa2 Rik van Riel
  • (reiserfs) Re: More on 2.2.18pre2aa2 Andrea Arcangeli
  • (reiserfs) Re: More on 2.2.18pre2aa2 Rik van Riel
• NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Trond Myklebust
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Alan Cox
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Trond Myklebust
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Alan Cox
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Jeff Epler
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Trond Myklebust
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Trond Myklebust
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Jeff Epler
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Andi Kleen
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Trond Myklebust
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Andi Kleen
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Frank van Maarseveen
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Jeff Epler
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Jeff Epler
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Trond Myklebust
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Albert D. Cahalan
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Trond Myklebust
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Jamie Lokier
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Trond Myklebust
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Jeff Epler
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Trond Myklebust
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Albert D. Cahalan
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Trond Myklebust
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Albert D. Cahalan
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Trond Myklebust
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Andi Kleen
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Trond Myklebust
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Andi Kleen
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Theodore Y. Ts'o
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Trond Myklebust
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Theodore Y. Ts'o
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Trond Myklebust
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Theodore Y. Ts'o
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() doesnot provide coherency guarantee Rogier Wolff
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() doesnot provide coherency guarantee Theodore Y. Ts'o
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() doesnot provide coherency guarantee Rogier Wolff
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() doesnot provide coherency guarantee Theodore Y. Ts'o
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() doesnot provide coherency guarantee Andreas Dilger
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Albert D. Cahalan
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Theodore Y. Ts'o
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Andi Kleen
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Trond Myklebust
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Theodore Y. Ts'o
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Trond Myklebust
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Andi Kleen
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Trond Myklebust
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Trond Myklebust
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Michael Eisler
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Jeff Epler
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Trond Myklebust
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee James Yarbrough
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Trond Myklebust
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Michael Eisler
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Trond Myklebust
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Michael Eisler
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Trond Myklebust
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock()does not provide coherency guarantee Linus Torvalds
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Michael Eisler
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Trond Myklebust
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Michael Eisler
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Trond Myklebust
  • Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee Alan Cox
• Masking out one page of RAM because of bit-errors. Patrick Mau
  • Re: Masking out one page of RAM because of bit-errors. Christer Weinigel
  • Re: Masking out one page of RAM because of bit-errors. John Levon
  • Re: Masking out one page of RAM because of bit-errors. Jan Niehusmann
• [patch] Card services & yenta driver Andrew Morton
  • Re: [patch] Card services & yenta driver Linus Torvalds
  • Re: [patch] Card services & yenta driver David Hinds
  • Re: [patch] Card services & yenta driver Linus Torvalds
  • Re: [patch] Card services & yenta driver Andrew Morton
  • Re: [patch] Card services & yenta driver Andrew Morton
• 2.4.0-test8 ethernet problems nbecker
• files bigger than 2 GB Arnaud Installe
  • Re: files bigger than 2 GB Alan Cox
  • Re: files bigger than 2 GB Jakub Jelinek
  • Re: files bigger than 2 GB Andreas Jaeger
  • Re: files bigger than 2 GB Arnaud Installe
  • Re: files bigger than 2 GB Andreas Jaeger
  • Re: files bigger than 2 GB Matti Aarnio
  • Re: files bigger than 2 GB Petr Vandrovec
  • Re: files bigger than 2 GB Matti Aarnio
  • Re: files bigger than 2 GB Andreas Jaeger
• recvmsg bug: copied 0 seq 476C726 rob
• Device Driver Question. Kishore Kumar C.
  • Re: Device Driver Question. Jonathan Corbet
• 2.2.18pre* CONFIG_AGP=Y compile problem Nicholas N.
  • Re: 2.2.18pre* CONFIG_AGP=Y compile problem Arjan van de Ven
  • Re: 2.2.18pre* CONFIG_AGP=Y compile problem Nicholas L. Nigay
• [patch] VIA IDE driver v2.3 Vojtech Pavlik
  • Re: [patch] VIA IDE driver v2.3 Andre Hedrick
  • [PATCH][minor] Re: [patch] VIA IDE driver v2.3 Bartlomiej Zolnierkiewicz
  • Re: [PATCH][minor] Re: [patch] VIA IDE driver v2.3 Vojtech Pavlik
  • Re: [PATCH][minor] Re: [patch] VIA IDE driver v2.3 Andre Hedrick
  • Re: [PATCH][minor] Re: [patch] VIA IDE driver v2.3 Vojtech Pavlik
  • Re: [PATCH][minor] Re: [patch] VIA IDE driver v2.3 Bartlomiej Zolnierkiewicz
• [PATCH *] VM and scheduler patch Rik van Riel
  • Re: [PATCH *] VM and scheduler patch Rui Sousa
  • Re: [PATCH *] VM and scheduler patch Rik van Riel
• Re: Adding set_system_gate fails in arch/i386/kernel/traps. Petr Vandrovec
  • Re: Adding set_system_gate fails in arch/i386/kernel/traps. Malcolm Beattie
• 2.2.17 dead after "Now booting the kernel"-message (586) Heusden, Folkert van
  • Re: 2.2.17 dead after "Now booting the kernel"-message (586) Arjan van de Ven
  • RE: 2.2.17 dead after "Now booting the kernel"-message (586) Heusden, Folkert van
• Adding set_system_gate fails in arch/i386/kernel/traps.c Malcolm Beattie
  • Re: Adding set_system_gate fails in arch/i386/kernel/traps.c Keith Owens
• 2.2.17 doesn't boot up when configured for 2GB RAM on Intel 2U boxen Yusuf Goolamabbas
  • Re: 2.2.17 doesn't boot up when configured for 2GB RAM on Intel 2U boxen Alan Cox
• I/O statistics per process? Samuli Kaski
  • Re: I/O statistics per process? Karim Yaghmour
• test7/8: hda lost interrupt..... Bruno Boettcher
• Test 8 Kernel Unable to get the password prompt? David Freedom
  • Re: Test 8 Kernel Unable to get the password prompt? Miles Lane
  • Re: Test 8 Kernel Unable to get the password prompt? Steven Walter
  • Re: Test 8 Kernel Unable to get the password prompt? Andries Brouwer
  • Re: Test 8 Kernel Unable to get the password prompt? Gerhard Mack
  • Re: Test 8 Kernel Unable to get the password prompt? Helge Hafting
  • Re: Test 8 Kernel Unable to get the password prompt? FORT David ou popo
• Memtest suite 0.0.4 Juan J. Quintela
• [PATCH][RFC] check fib6_lookup_1 return in fib6_lookup_1 Arnaldo Carvalho de Melo
  • Re: [PATCH][RFC] check fib6_lookup_1 return in fib6_lookup_1 David S. Miller
  • Re: [PATCH][RFC] check fib6_lookup_1 return in fib6_lookup_1 Arnaldo Carvalho de Melo
  • Re: [PATCH][RFC] check fib6_lookup_1 return in fib6_lookup_1 kuznet
• Signal handling different for root and others jury gerold
  • Re: Signal handling different for root and others Andi Kleen
  • Re: Signal handling different for root and others jury gerold
  • Re: Signal handling different for root and others Andi Kleen
  • Re: Signal handling different for root and others Alan Cox
  • Re: Signal handling different for root and others Andi Kleen
  • Re: Signal handling different for root and others Alan Cox
  • Re: Signal handling different for root and others jury gerold
  • Re: Signal handling different for root and others Andi Kleen
  • Re: Signal handling different for root and others gerold
  • Re: Signal handling different for root and others Dan Kegel
• emu10k1 reversing channels Jan Niehusmann
• [BUG] threaded processes get stuck in rt_sigsuspend/fillonedir/exit_notify David Ford
  • Re: [BUG] threaded processes get stuck in rt_sigsuspend/fillonedir/exit_notify Ulrich Drepper
  • Re: [BUG] threaded processes get stuck in rt_sigsuspend/fillonedir/exit_notify Ray Bryant
  • Re: [BUG] threaded processes get stuck in rt_sigsuspend/fillonedir/exit_notify Ulrich Drepper
  • Re: [BUG] threaded processes get stuck in rt_sigsuspend/fillonedir/exit_notify David Ford
  • Re: [BUG] threaded processes get stuck in rt_sigsuspend/fillonedir/exit_notify Ulrich Drepper
  • Re: [BUG] threaded processes get stuck in rt_sigsuspend/fillonedir/exit_notify David Ford
  • Re: [BUG] threaded processes get stuck in rt_sigsuspend/fillonedir/exit_notify Theodore Y. Ts'o
  • Re: [BUG] threaded processes get stuck in rt_sigsuspend/fillonedir/exit_notify David Ford
  • Re: [BUG] threaded processes get stuck in rt_sigsuspend/fillonedir/exit_notify tytso
  • Re: [BUG] threaded processes get stuck in rt_sigsuspend/fillonedir/exit_notify David Ford
  • Re: [BUG] threaded processes get stuck in rt_sigsuspend/fillonedir/exit_notify Ulrich Drepper
  • Re: [BUG] threaded processes get stuck in rt_sigsuspend/fillonedir/exit_notify Jamie Lokier
• -2.2.18-5 Bob Lorenzini
  • Re: -2.2.18-5 Ted Gervais
• Re: [PATCH] (was: [OOPS] dquot_transfer() - 2.4.0-test8) Marc Duponcheel
• ide-pci-patch for 2.2.18pre5 Dag Wieers
• Linux 2.2.18pre5 Alan Cox
  • Re: Linux 2.2.18pre5 Eyal Lebedinsky
  • Re: Linux 2.2.18pre5 Jamie Fifield
  • Re: Linux 2.2.18pre5 Keith Owens
  • Re: Linux 2.2.18pre5 Alan Cox
  • Re: Linux 2.2.18pre5 Miquel van Smoorenburg
  • Linux 2.2.18pre5 Alan Cox
  • Re: Linux 2.2.18pre8 Andrea Arcangeli
• a bug in the command-line parser OKUJI Yoshinori
• Booting into /bin/bash Richard B. Johnson
  • Re: Booting into /bin/bash Adam
  • Re: Booting into /bin/bash Richard B. Johnson
  • Re: Booting into /bin/bash Miquel van Smoorenburg
  • Re: Booting into /bin/bash Ion Badulescu
  • Re: Booting into /bin/bash Jesse Pollard
  • Re: Booting into /bin/bash Miquel van Smoorenburg
  • Re: Booting into /bin/bash Ion Badulescu
  • Re: Booting into /bin/bash David Mansfield
  • Re: Booting into /bin/bash Ion Badulescu
  • Re: Booting into /bin/bash Ion Badulescu
  • Re: Booting into /bin/bash Miquel van Smoorenburg
  • Re: Booting into /bin/bash Ion Badulescu
  • Re: Booting into /bin/bash Richard B. Johnson
  • Re: Booting into /bin/bash David S. Miller
  • Re: Booting into /bin/bash Richard B. Johnson
  • Re: Booting into /bin/bash Miquel van Smoorenburg
  • Re: Booting into /bin/bash Miquel van Smoorenburg
  • Re: Booting into /bin/bash Richard B. Johnson
  • Re: Booting into /bin/bash Russell King
  • Re: Booting into /bin/bash Ion Badulescu
  • Re: Booting into /bin/bash Richard B. Johnson
  • Re: Booting into /bin/bash Richard B. Johnson
  • Re: Booting into /bin/bash Ion Badulescu
  • Re: Booting into /bin/bash Bernd Eckenfels
  • Re: Booting into /bin/bash Olaf Titz
• PROBLEM: Xircom Realport gets MAC 00:00:00...... Card known good. Dag B
• write_space in kernel Lee Chin
  • write_space in kernel Lee Chin
• bizarre problems with Athlon system after upgrdaing motherboard Marty Leisner
  • Re: bizarre problems with Athlon system after upgrdaing motherboard Brian Gerst

[Earlier messages] [Later messages]