LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@o2.pl>
To: "Ahmed S\. Darwish" <darwish.07@gmail.com>
Cc: Low Yucheng <ylow@andrew.cmu.edu>,
	Oleg Verych <olecom@flower.upol.cz>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: PROBLEM: System Freeze on Particular workload with kernel 2.6.22.6
Date: Thu, 20 Sep 2007 12:00:31 +0200	[thread overview]
Message-ID: <20070920100031.GA2796@ff.dom.local> (raw)
In-Reply-To: <20070919192546.GA3153@Ahmed>

On 19-09-2007 21:25, Ahmed S. Darwish wrote:
> Hi Low,
> 
> On Wed, Sep 19, 2007 at 12:16:39PM -0400, Low Yucheng wrote:
>> There are no additional console messages.
>> Not sure what this is: * no relevant Cc (memory management added)
> 
> Relevant CCs means CCing maintainers or subsystem mailing lists related to your
> bug report. i.e, if it's a networking bug, you need to CC the linux kernel
> networking mailing list. If it's a kobject bug, you need to CC its maintainer
> (Greg) and so on.

So, which one do you recommend here?

Regards,
Jarek P.

PS#1: I don't think we should require from users so much expertise
in bug reporting: after a few questions cc-ing should be no problem
here.

PS#2: Low Yucheng: maybe it's something else, but it seems your swap
could be bigger for this amount of memory. (You could try to monitor
this e.g. with "top" running in another console window.)

  reply	other threads:[~2007-09-20  9:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-19  8:45 Low Yucheng
2007-09-19 15:47 ` Oleg Verych
2007-09-19 16:16   ` Low Yucheng
2007-09-19 19:25     ` Ahmed S. Darwish
2007-09-20 10:00       ` Jarek Poplawski [this message]
2007-09-20 15:24         ` Ahmed S. Darwish
2007-12-01 22:39     ` Daniel Phillips
2007-09-20 16:14 ` Ray Lee
2007-09-21  1:04   ` Yucheng Low

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=20070920100031.GA2796@ff.dom.local \
    --to=jarkao2@o2.pl \
    --cc=akpm@linux-foundation.org \
    --cc=darwish.07@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=olecom@flower.upol.cz \
    --cc=ylow@andrew.cmu.edu \
    --subject='Re: PROBLEM: System Freeze on Particular workload with kernel 2.6.22.6' \
    /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

This is a public inbox, see mirroring instructions
on how to clone and mirror all data and code used for this inbox