All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kasper Sandberg <lkml@metanurb.dk>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: vojtech@suse.cz, ak@muc.de,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>,
	David Howells <dhowells@redhat.com>
Subject: Re: BUG? atleast >=2.6.19-rc5, x86 chroot on x86_64
Date: Wed, 13 Dec 2006 05:39:43 +0100	[thread overview]
Message-ID: <1165984783.23819.7.camel@localhost> (raw)
In-Reply-To: <200612110330_MC3-1-D49B-BC0E@compuserve.com>

On Mon, 2006-12-11 at 03:27 -0500, Chuck Ebbert wrote:
> In-Reply-To: <1165409880.15706.9.camel@localhost>
> 
> On Wed, 06 Dec 2006 13:58:00 +0100, Kasper Sandberg wrote:
> 
> > > Kasper, what problems (other that the annoying message) are you having?
> > if it had only been the messages i wouldnt have complained.
> > the thing is, when i get these messages, the app provoking them acts
> > very strange, and in some cases, my system simply hardlocks.
> 
> You can try the patch I sent you to see if it fixes the Wine app.
> (David thought I was proposing it for the mainline kernel but I just
> wanted to see whether it made a difference.)

do you think it may be a bug in the kernel? the stuff with wine that
gets thrown in the kernel messages? cause if it is, i ofcourse wish to
help by testing. one more thing, im 100% positive wine does NOT have
access to any fat32, cause i entirely removed the only disk having such
a filesystem, and it still likes to give this, however the last few
times i havent observed the app going nuts :)

> 
> As for the lockups, there are possibly other bugs lurking in 2.6.19.
yes, when the using-much-ram-perhaps-even-swap thing was mentioned i
came to think, cause i do happen to use alarmingly much swap. i noticed
a ~5 second lockup (where it actually returned to normal again) when i
reached ~50mb free ram, and this was outside the chroot.


> 


  reply	other threads:[~2006-12-13  4:58 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-11  8:27 BUG? atleast >=2.6.19-rc5, x86 chroot on x86_64 Chuck Ebbert
2006-12-13  4:39 ` Kasper Sandberg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-12-13  7:50 Chuck Ebbert
2006-12-13  8:05 ` Kasper Sandberg
2006-12-13 11:08 ` Alan
2006-12-06  2:31 Chuck Ebbert
2006-12-06 12:58 ` Kasper Sandberg
2006-12-06 13:08   ` David Howells
2006-12-06 16:06     ` Kasper Sandberg
2006-12-06 16:48       ` David Howells
2006-12-06 20:05         ` Kasper Sandberg
2006-12-06 21:29   ` Andi Kleen
2006-12-06 22:19     ` Kasper Sandberg
2006-12-05 20:32 Chuck Ebbert
2006-12-05 22:11 ` David Howells
2006-12-05  9:33 Chuck Ebbert
2006-12-05 14:19 ` David Howells
2006-12-06  0:11   ` Kasper Sandberg
2006-11-22 14:29 Kasper Sandberg
2006-11-22 23:25 ` Andrew Morton
2006-11-26 13:47   ` Kasper Sandberg
2006-12-05  2:36   ` Kasper Sandberg
2006-12-05  2:59     ` Kasper Sandberg
2006-12-05  3:20     ` Andrew Morton
2006-12-05 14:17       ` David Howells

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1165984783.23819.7.camel@localhost \
    --to=lkml@metanurb.dk \
    --cc=76306.1226@compuserve.com \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.