On Thu, Jan 24, 2013 at 2:30 PM, Andrew Morton
wrote:
> On Sat, 19 Jan 2013 20:15:33 -0800
> Bret Towe wrote:
>
>> >
>> > it looks like you have a patch for this problem in a queue somewhere
>> > (email found on ocfs2-dev:
>> > https://oss.oracle.com/
On Thu, Jan 24, 2013 at 2:30 PM, Andrew Morton
a...@linux-foundation.org wrote:
On Sat, 19 Jan 2013 20:15:33 -0800
Bret Towe magn...@gmail.com wrote:
it looks like you have a patch for this problem in a queue somewhere
(email found on ocfs2-dev:
https://oss.oracle.com/pipermail/ocfs2
On Tue, Oct 2, 2012 at 8:41 PM, Bret Towe wrote:
> On Sun, Jul 22, 2012 at 1:16 PM, Bret Towe wrote:
>> just booted a fresh 3.5 kernel and got the following on login via gdm
>> on the client computer
>> didn't see any crashes yet on any other computer but didn't give it
On Tue, Oct 2, 2012 at 8:41 PM, Bret Towe magn...@gmail.com wrote:
On Sun, Jul 22, 2012 at 1:16 PM, Bret Towe magn...@gmail.com wrote:
just booted a fresh 3.5 kernel and got the following on login via gdm
on the client computer
didn't see any crashes yet on any other computer but didn't give
On Sun, Jul 22, 2012 at 1:16 PM, Bret Towe wrote:
> just booted a fresh 3.5 kernel and got the following on login via gdm
> on the client computer
> didn't see any crashes yet on any other computer but didn't give it
> long to try after seeing this
> let me know if you
On Sun, Jul 22, 2012 at 1:16 PM, Bret Towe magn...@gmail.com wrote:
just booted a fresh 3.5 kernel and got the following on login via gdm
on the client computer
didn't see any crashes yet on any other computer but didn't give it
long to try after seeing this
let me know if you need more info
On Mon, Jul 30, 2012 at 1:28 AM, Joel Becker wrote:
> On Sun, Jul 22, 2012 at 01:16:21PM -0700, Bret Towe wrote:
>> just booted a fresh 3.5 kernel and got the following on login via gdm
>> on the client computer
>> didn't see any crashes yet on any other computer but didn't g
On Mon, Jul 30, 2012 at 1:28 AM, Joel Becker jl...@evilplan.org wrote:
On Sun, Jul 22, 2012 at 01:16:21PM -0700, Bret Towe wrote:
just booted a fresh 3.5 kernel and got the following on login via gdm
on the client computer
didn't see any crashes yet on any other computer but didn't give
just booted a fresh 3.5 kernel and got the following on login via gdm
on the client computer
didn't see any crashes yet on any other computer but didn't give it
long to try after seeing this
let me know if you need more info
this client is running debian wheezy 64bit
Jul 22 12:48:38 ghoststar
just booted a fresh 3.5 kernel and got the following on login via gdm
on the client computer
didn't see any crashes yet on any other computer but didn't give it
long to try after seeing this
let me know if you need more info
this client is running debian wheezy 64bit
Jul 22 12:48:38 ghoststar
On Dec 18, 2007 9:36 AM, Christoph Hellwig <[EMAIL PROTECTED]> wrote:
>
> This was broken by my '[XFS] simplify xfs_create/mknod/symlink prototype',
> which assigned the re-shuffled ondisk dev_t back to the rdev variable in
> xfs_vn_mknod. Because of that i_rdev is set to the ondisk dev_t instead
On Dec 18, 2007 9:36 AM, Christoph Hellwig [EMAIL PROTECTED] wrote:
This was broken by my '[XFS] simplify xfs_create/mknod/symlink prototype',
which assigned the re-shuffled ondisk dev_t back to the rdev variable in
xfs_vn_mknod. Because of that i_rdev is set to the ondisk dev_t instead
of
I hit a bug in 2.6.24-rc looks to be in 2.6.23 also so not sure how
long it's been there
with an xfs filesystem pbuilder has an issue using device files it
makes for chroot
the mknod command looks to work fine the file is created
however when attempting to use one of the created files you see
I hit a bug in 2.6.24-rc looks to be in 2.6.23 also so not sure how
long it's been there
with an xfs filesystem pbuilder has an issue using device files it
makes for chroot
the mknod command looks to work fine the file is created
however when attempting to use one of the created files you see
On 9/5/07, Andrew Morton <[EMAIL PROTECTED]> wrote:
> > On Wed, 22 Aug 2007 15:41:18 -0700 "Bret Towe" <[EMAIL PROTECTED]> wrote:
>
> More than two weeks, you've bisected it and there's no sign of any action?
>
> I don't see this on Michal's list so perhap
On 9/5/07, Andrew Morton [EMAIL PROTECTED] wrote:
On Wed, 22 Aug 2007 15:41:18 -0700 Bret Towe [EMAIL PROTECTED] wrote:
More than two weeks, you've bisected it and there's no sign of any action?
I don't see this on Michal's list so perhaps it already got fixed in a
different
thread. Have
On 8/30/07, Tony Breeds <[EMAIL PROTECTED]> wrote:
> On Thu, Aug 30, 2007 at 02:56:50PM -0700, Bret Towe wrote:
> > On 8/29/07, Bret Towe <[EMAIL PROTECTED]> wrote:
> > > while trying to build a fresh kernel for my mini after upgrading from
> > > gutsy
>
On 8/28/07, Bret Towe <[EMAIL PROTECTED]> wrote:
> On 8/28/07, Trond Myklebust <[EMAIL PROTECTED]> wrote:
> > On Mon, 2007-08-27 at 20:35 -0500, Florin Iucha wrote:
> > > On Mon, Aug 27, 2007 at 06:19:29PM -0700, Bret Towe wrote:
> > > > On 8/27/07,
On 8/29/07, Bret Towe <[EMAIL PROTECTED]> wrote:
> while trying to build a fresh kernel for my mini after upgrading from gutsy
> (and forgetting to save my .config) I hit the below build error
> 2.6.23-rc3 I did work under feisty but that is with a different .config
> so not sure
On 8/29/07, Bret Towe [EMAIL PROTECTED] wrote:
while trying to build a fresh kernel for my mini after upgrading from gutsy
(and forgetting to save my .config) I hit the below build error
2.6.23-rc3 I did work under feisty but that is with a different .config
so not sure if that makes any
On 8/28/07, Bret Towe [EMAIL PROTECTED] wrote:
On 8/28/07, Trond Myklebust [EMAIL PROTECTED] wrote:
On Mon, 2007-08-27 at 20:35 -0500, Florin Iucha wrote:
On Mon, Aug 27, 2007 at 06:19:29PM -0700, Bret Towe wrote:
On 8/27/07, Trond Myklebust [EMAIL PROTECTED] wrote:
this sounds
On 8/30/07, Tony Breeds [EMAIL PROTECTED] wrote:
On Thu, Aug 30, 2007 at 02:56:50PM -0700, Bret Towe wrote:
On 8/29/07, Bret Towe [EMAIL PROTECTED] wrote:
while trying to build a fresh kernel for my mini after upgrading from
gutsy
(and forgetting to save my .config) I hit the below
On 8/29/07, Felipe Balbi <[EMAIL PROTECTED]> wrote:
> Hi,
>
> On 8/29/07, Bret Towe <[EMAIL PROTECTED]> wrote:
> > while trying to build a fresh kernel for my mini after upgrading from gutsy
> > (and forgetting to save my .config) I hit the below build error
>
On 8/29/07, Felipe Balbi [EMAIL PROTECTED] wrote:
Hi,
On 8/29/07, Bret Towe [EMAIL PROTECTED] wrote:
while trying to build a fresh kernel for my mini after upgrading from gutsy
(and forgetting to save my .config) I hit the below build error
The .config you can get from /boot/config-`uname
On 8/28/07, Trond Myklebust <[EMAIL PROTECTED]> wrote:
> On Mon, 2007-08-27 at 20:35 -0500, Florin Iucha wrote:
> > On Mon, Aug 27, 2007 at 06:19:29PM -0700, Bret Towe wrote:
> > > On 8/27/07, Trond Myklebust <[EMAIL PROTECTED]> wrote:
> > > > > >
On 8/28/07, Trond Myklebust [EMAIL PROTECTED] wrote:
On Mon, 2007-08-27 at 20:35 -0500, Florin Iucha wrote:
On Mon, Aug 27, 2007 at 06:19:29PM -0700, Bret Towe wrote:
On 8/27/07, Trond Myklebust [EMAIL PROTECTED] wrote:
this sounds alot like the post i did yesterday titled 'nfs4 hang
On 8/27/07, Trond Myklebust <[EMAIL PROTECTED]> wrote:
> On Thu, 2007-08-23 at 12:36 -0500, Florin Iucha wrote:
> > On Thu, Aug 23, 2007 at 10:14:38AM -0700, Bret Towe wrote:
> > > this sounds alot like the post i did yesterday titled 'nfs4 hang
> > > regression'
On 8/27/07, Trond Myklebust [EMAIL PROTECTED] wrote:
On Thu, 2007-08-23 at 12:36 -0500, Florin Iucha wrote:
On Thu, Aug 23, 2007 at 10:14:38AM -0700, Bret Towe wrote:
this sounds alot like the post i did yesterday titled 'nfs4 hang
regression'
i tracked it down to commit
On 8/23/07, Florin Iucha <[EMAIL PROTECTED]> wrote:
> Trond,
>
> Fess up... I'm closing in:
>
>http://iucha.net/2.6.23-rc3/2.6.23-rc-bisect.png
>
> [Dropping Jiri and linux-usb-devel from future postings. You are
> included now just for communicating the conclusion of this thread.]
>
> On
On 8/23/07, Florin Iucha [EMAIL PROTECTED] wrote:
Trond,
Fess up... I'm closing in:
http://iucha.net/2.6.23-rc3/2.6.23-rc-bisect.png
[Dropping Jiri and linux-usb-devel from future postings. You are
included now just for communicating the conclusion of this thread.]
On Wed, Aug 22,
On 8/2/07, Jiri Kosina <[EMAIL PROTECTED]> wrote:
> On Thu, 2 Aug 2007, Ulrich Kunitz wrote:
>
> > Here is the .config file. I used it directly with 60bfba7e8 and could
> > reproduce the bug. (All other builds after the patch could also
> > reproduce the bug.)
>
> Thanks, I used your .config
On 8/2/07, Jiri Kosina [EMAIL PROTECTED] wrote:
On Thu, 2 Aug 2007, Ulrich Kunitz wrote:
Here is the .config file. I used it directly with 60bfba7e8 and could
reproduce the bug. (All other builds after the patch could also
reproduce the bug.)
Thanks, I used your .config against 60bfba7e8
On 7/30/07, Michal Piotrowski <[EMAIL PROTECTED]> wrote:
> Subject : 2.6.23-rc1 regression: mm: fix fault vs invalidate race for
> linear mappings
> References : http://lkml.org/lkml/2007/7/24/301
> Last known good : ?
> Submitter : Bret Towe <[EM
On 7/30/07, Michal Piotrowski [EMAIL PROTECTED] wrote:
Subject : 2.6.23-rc1 regression: mm: fix fault vs invalidate race for
linear mappings
References : http://lkml.org/lkml/2007/7/24/301
Last known good : ?
Submitter : Bret Towe [EMAIL PROTECTED]
Caused-By : Nick
On 7/25/07, Nick Piggin <[EMAIL PROTECTED]> wrote:
Hi,
Does this patch solve the X problem? Does anyone see anything wrong
with it or know why agp was locking the pages?
Yeap the mac mini is happy again
Thanks
--
AGP should not need to lock pages. They are not protecting any race
because
On 7/24/07, Nick Piggin <[EMAIL PROTECTED]> wrote:
Bret Towe wrote:
> for a while in -git I've had an issue that on boot when gdm loads the
> screen stays black
> using ctrl-f1 doesn't return to a console and killing X doesn't help any
> ssh'ing into the box does work top only
On 7/24/07, Nick Piggin [EMAIL PROTECTED] wrote:
Bret Towe wrote:
for a while in -git I've had an issue that on boot when gdm loads the
screen stays black
using ctrl-f1 doesn't return to a console and killing X doesn't help any
ssh'ing into the box does work top only shows 100% io-wait
On 7/25/07, Nick Piggin [EMAIL PROTECTED] wrote:
Hi,
Does this patch solve the X problem? Does anyone see anything wrong
with it or know why agp was locking the pages?
Yeap the mac mini is happy again
Thanks
--
AGP should not need to lock pages. They are not protecting any race
because
On 7/24/07, Bret Towe <[EMAIL PROTECTED]> wrote:
for a while in -git I've had an issue that on boot when gdm loads the
screen stays black
using ctrl-f1 doesn't return to a console and killing X doesn't help any
ssh'ing into the box does work top only shows 100% io-wait
dmesg shows nothi
for a while in -git I've had an issue that on boot when gdm loads the
screen stays black
using ctrl-f1 doesn't return to a console and killing X doesn't help any
ssh'ing into the box does work top only shows 100% io-wait
dmesg shows nothing odd
the work around I have is at the moment is to just
for a while in -git I've had an issue that on boot when gdm loads the
screen stays black
using ctrl-f1 doesn't return to a console and killing X doesn't help any
ssh'ing into the box does work top only shows 100% io-wait
dmesg shows nothing odd
the work around I have is at the moment is to just
On 7/24/07, Bret Towe [EMAIL PROTECTED] wrote:
for a while in -git I've had an issue that on boot when gdm loads the
screen stays black
using ctrl-f1 doesn't return to a console and killing X doesn't help any
ssh'ing into the box does work top only shows 100% io-wait
dmesg shows nothing odd
On 7/20/07, Ulrich Kunitz <[EMAIL PROTECTED]> wrote:
Since this week new linux-2.6/master kernels don't work with my
initial ram disks. The sleep binary runs repeatingly into
segmentation faults until the Busybox shell starts. My system is a
x86-64 with Kubuntu Feisty Fawn.
By bisecting I found
On 7/20/07, Ulrich Kunitz [EMAIL PROTECTED] wrote:
Since this week new linux-2.6/master kernels don't work with my
initial ram disks. The sleep binary runs repeatingly into
segmentation faults until the Busybox shell starts. My system is a
x86-64 with Kubuntu Feisty Fawn.
By bisecting I found
On 7/17/07, Tony Breeds <[EMAIL PROTECTED]> wrote:
On Tue, Jul 17, 2007 at 11:04:57AM -0700, Bret Towe wrote:
> this is off my g4 mac mini
> latest git as of when this email was sent
> config file attached
Hi Bret,
the patch below will fix it.
yeap it compiled and bo
On 7/17/07, Tony Breeds [EMAIL PROTECTED] wrote:
On Tue, Jul 17, 2007 at 11:04:57AM -0700, Bret Towe wrote:
this is off my g4 mac mini
latest git as of when this email was sent
config file attached
Hi Bret,
the patch below will fix it.
yeap it compiled and boots fine
thanks
From
On 7/6/07, Johannes Berg <[EMAIL PROTECTED]> wrote:
On Fri, 2007-07-06 at 13:57 -0700, Bret Towe wrote:
> On 7/6/07, Johannes Berg <[EMAIL PROTECTED]> wrote:
> > Oh good. I actually got build problems from that due to a powerpc64 gcc
> > bug so... :)
> this als
On 7/6/07, Johannes Berg <[EMAIL PROTECTED]> wrote:
On Fri, 2007-07-06 at 10:29 -0700, Christoph Lameter wrote:
> On Thu, 5 Jul 2007, Johannes Berg wrote:
>
> > kmem_cache_open is static so shouldn't be exported.
> >
> > Signed-off-by: Johannes Berg <[EMAIL PROTECTED]>
>
> I already fixed that.
On 7/6/07, Johannes Berg [EMAIL PROTECTED] wrote:
On Fri, 2007-07-06 at 10:29 -0700, Christoph Lameter wrote:
On Thu, 5 Jul 2007, Johannes Berg wrote:
kmem_cache_open is static so shouldn't be exported.
Signed-off-by: Johannes Berg [EMAIL PROTECTED]
I already fixed that. Patch is in
On 7/6/07, Johannes Berg [EMAIL PROTECTED] wrote:
On Fri, 2007-07-06 at 13:57 -0700, Bret Towe wrote:
On 7/6/07, Johannes Berg [EMAIL PROTECTED] wrote:
Oh good. I actually got build problems from that due to a powerpc64 gcc
bug so... :)
this also looks to solve booting issue on a g4 mac
On 5/28/07, Bret Towe <[EMAIL PROTECTED]> wrote:
On 5/28/07, Nitin Gupta <[EMAIL PROTECTED]> wrote:
> Hi,
>
> This is kernel port of LZO1X-1 compressor and LZO1X decompressor (safe
> version only).
>
> * Changes since 'take 5' (Full Changelog after this):
> - A
On 5/28/07, Nitin Gupta <[EMAIL PROTECTED]> wrote:
Hi,
Attached is tester code used for testing.
(developed by Daniel Hazelton -- modified slightly to now use 'take 6'
version for 'TinyLZO')
Cheers,
Nitin
On 5/28/07, Nitin Gupta <[EMAIL PROTECTED]> wrote:
> (Using tester program from Daniel)
On 5/28/07, Nitin Gupta <[EMAIL PROTECTED]> wrote:
Hi,
This is kernel port of LZO1X-1 compressor and LZO1X decompressor (safe
version only).
* Changes since 'take 5' (Full Changelog after this):
- Added compressor and decomrpesssor as separate and hidden config
options (default: n)
- Cleanups:
On 5/28/07, Nitin Gupta [EMAIL PROTECTED] wrote:
Hi,
This is kernel port of LZO1X-1 compressor and LZO1X decompressor (safe
version only).
* Changes since 'take 5' (Full Changelog after this):
- Added compressor and decomrpesssor as separate and hidden config
options (default: n)
- Cleanups:
On 5/28/07, Nitin Gupta [EMAIL PROTECTED] wrote:
Hi,
Attached is tester code used for testing.
(developed by Daniel Hazelton -- modified slightly to now use 'take 6'
version for 'TinyLZO')
Cheers,
Nitin
On 5/28/07, Nitin Gupta [EMAIL PROTECTED] wrote:
(Using tester program from Daniel)
On 5/28/07, Bret Towe [EMAIL PROTECTED] wrote:
On 5/28/07, Nitin Gupta [EMAIL PROTECTED] wrote:
Hi,
This is kernel port of LZO1X-1 compressor and LZO1X decompressor (safe
version only).
* Changes since 'take 5' (Full Changelog after this):
- Added compressor and decomrpesssor as separate
On 5/26/07, Nitin Gupta <[EMAIL PROTECTED]> wrote:
Hi Bret,
On 5/25/07, Bret Towe <[EMAIL PROTECTED]> wrote:
>
> [ 237.556167] LZO compress successful: orig_size=17448, comp_size=8183
> [ 253.320760] LZO decompress successful: decomp_size=17448
>
> 2221c586e3eb8
On 5/26/07, Nitin Gupta [EMAIL PROTECTED] wrote:
Hi Bret,
On 5/25/07, Bret Towe [EMAIL PROTECTED] wrote:
[ 237.556167] LZO compress successful: orig_size=17448, comp_size=8183
[ 253.320760] LZO decompress successful: decomp_size=17448
2221c586e3eb869af7f4333d4f56b441b9aa8414 test-input
On 5/24/07, Nitin Gupta <[EMAIL PROTECTED]> wrote:
On 5/25/07, Bret Towe <[EMAIL PROTECTED]> wrote:
> On 5/24/07, Nitin Gupta <[EMAIL PROTECTED]> wrote:
> > On 5/23/07, Bret Towe <[EMAIL PROTECTED]> wrote:
> > > On 5/23/07, Nitin Gupta <[EMAIL P
On 5/24/07, Nitin Gupta [EMAIL PROTECTED] wrote:
On 5/25/07, Bret Towe [EMAIL PROTECTED] wrote:
On 5/24/07, Nitin Gupta [EMAIL PROTECTED] wrote:
On 5/23/07, Bret Towe [EMAIL PROTECTED] wrote:
On 5/23/07, Nitin Gupta [EMAIL PROTECTED] wrote:
For now, tested on x86 only.
If you
On 5/24/07, Nitin Gupta <[EMAIL PROTECTED]> wrote:
On 5/23/07, Bret Towe <[EMAIL PROTECTED]> wrote:
> On 5/23/07, Nitin Gupta <[EMAIL PROTECTED]> wrote:
> > For now, tested on x86 only.
>
> If you have a program to test this I can run it on an amd64 and a g4 ppc
On 5/24/07, Nitin Gupta [EMAIL PROTECTED] wrote:
On 5/23/07, Bret Towe [EMAIL PROTECTED] wrote:
On 5/23/07, Nitin Gupta [EMAIL PROTECTED] wrote:
For now, tested on x86 only.
If you have a program to test this I can run it on an amd64 and a g4 ppc
Attached is the kernel module (compress
On 5/23/07, Nitin Gupta <[EMAIL PROTECTED]> wrote:
Hi,
This contains LZO1X-1 compressor and LZO1X decompressor (safe and
standard version).
This includes changes suggested by various people - Thanks to all who
reviewed previous patches for this LZO port.
Changelog vs original LZO 2.02 code:
-
On 5/23/07, Nitin Gupta [EMAIL PROTECTED] wrote:
Hi,
This contains LZO1X-1 compressor and LZO1X decompressor (safe and
standard version).
This includes changes suggested by various people - Thanks to all who
reviewed previous patches for this LZO port.
Changelog vs original LZO 2.02 code:
-
On 9/6/05, J. Bruce Fields <[EMAIL PROTECTED]> wrote:
> On Mon, Sep 05, 2005 at 08:40:53PM -0700, Bret Towe wrote:
> > Pid: 14169, comm: xmms Tainted: G M 2.6.13
>
> Hm, can someone explain what that means? A proprietary module was
> loaded then unloaded, maybe
On 9/6/05, J. Bruce Fields [EMAIL PROTECTED] wrote:
On Mon, Sep 05, 2005 at 08:40:53PM -0700, Bret Towe wrote:
Pid: 14169, comm: xmms Tainted: G M 2.6.13
Hm, can someone explain what that means? A proprietary module was
loaded then unloaded, maybe?
You may also want to retest
On 9/5/05, Jesper Juhl <[EMAIL PROTECTED]> wrote:
> On 9/5/05, Bret Towe <[EMAIL PROTECTED]> wrote:
> > On 9/4/05, J. Bruce Fields <[EMAIL PROTECTED]> wrote:
> > > On Sun, Sep 04, 2005 at 08:08:22PM -0700, Bret Towe wrote:
> > > > On 9/4/05, J. Bruc
On 9/4/05, J. Bruce Fields <[EMAIL PROTECTED]> wrote:
> On Sun, Sep 04, 2005 at 08:08:22PM -0700, Bret Towe wrote:
> > On 9/4/05, J. Bruce Fields <[EMAIL PROTECTED]> wrote:
> > > Do you get anything from alt-sysrq-T?
> >
> > no i havent used that im usa
On 9/4/05, J. Bruce Fields [EMAIL PROTECTED] wrote:
On Sun, Sep 04, 2005 at 08:08:22PM -0700, Bret Towe wrote:
On 9/4/05, J. Bruce Fields [EMAIL PROTECTED] wrote:
Do you get anything from alt-sysrq-T?
no i havent used that im usally in x when its freezing
x wont even switch to console
On 9/5/05, Jesper Juhl [EMAIL PROTECTED] wrote:
On 9/5/05, Bret Towe [EMAIL PROTECTED] wrote:
On 9/4/05, J. Bruce Fields [EMAIL PROTECTED] wrote:
On Sun, Sep 04, 2005 at 08:08:22PM -0700, Bret Towe wrote:
On 9/4/05, J. Bruce Fields [EMAIL PROTECTED] wrote:
Do you get anything from
On 9/4/05, J. Bruce Fields <[EMAIL PROTECTED]> wrote:
> On Sun, Sep 04, 2005 at 01:51:08PM -0700, Bret Towe wrote:
> > On 9/4/05, Bret Towe <[EMAIL PROTECTED]> wrote:
> > > On 9/4/05, Francois Romieu <[EMAIL PROTECTED]> wrote:
> > > > Bret Towe <
On 9/4/05, Bret Towe <[EMAIL PROTECTED]> wrote:
> On 9/4/05, Francois Romieu <[EMAIL PROTECTED]> wrote:
> > Bret Towe <[EMAIL PROTECTED]> :
> > [...]
> > > after moving some files on the server to a new location then trying to
> > > add the
On 9/4/05, Francois Romieu <[EMAIL PROTECTED]> wrote:
> Bret Towe <[EMAIL PROTECTED]> :
> [...]
> > after moving some files on the server to a new location then trying to
> > add the files
> > to xmms playlist i found the following in dmesg after xmms froze
On 9/4/05, Francois Romieu [EMAIL PROTECTED] wrote:
Bret Towe [EMAIL PROTECTED] :
[...]
after moving some files on the server to a new location then trying to
add the files
to xmms playlist i found the following in dmesg after xmms froze
wonder how many more items i can find
On 9/4/05, Bret Towe [EMAIL PROTECTED] wrote:
On 9/4/05, Francois Romieu [EMAIL PROTECTED] wrote:
Bret Towe [EMAIL PROTECTED] :
[...]
after moving some files on the server to a new location then trying to
add the files
to xmms playlist i found the following in dmesg after xmms froze
On 9/4/05, J. Bruce Fields [EMAIL PROTECTED] wrote:
On Sun, Sep 04, 2005 at 01:51:08PM -0700, Bret Towe wrote:
On 9/4/05, Bret Towe [EMAIL PROTECTED] wrote:
On 9/4/05, Francois Romieu [EMAIL PROTECTED] wrote:
Bret Towe [EMAIL PROTECTED] :
[...]
after moving some files
On 9/3/05, Bret Towe <[EMAIL PROTECTED]> wrote:
> i encountered the following error while using nfs4
> ive hit this error i think twice now not sure what causes it yet tho
> this time the only io related items going on was emerge sync running
> in the background (which shoul
i encountered the following error while using nfs4
ive hit this error i think twice now not sure what causes it yet tho
this time the only io related items going on was emerge sync running
in the background (which shouldnt of touched nfs at all) and xmms
playing some music
another problem i had
i encountered the following error while using nfs4
ive hit this error i think twice now not sure what causes it yet tho
this time the only io related items going on was emerge sync running
in the background (which shouldnt of touched nfs at all) and xmms
playing some music
another problem i had
On 9/3/05, Bret Towe [EMAIL PROTECTED] wrote:
i encountered the following error while using nfs4
ive hit this error i think twice now not sure what causes it yet tho
this time the only io related items going on was emerge sync running
in the background (which shouldnt of touched nfs at all
80 matches
Mail list logo
