linux-kernel - Re: PROBLEM: System Freeze on Particular workload with kernel 2.6.22.6

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 20 Sep 2007 12:00:31 +0200
From:	Jarek Poplawski <jarkao2@...pl>
To:	"Ahmed S\. Darwish" <darwish.07@...il.com>
Cc:	Low Yucheng <ylow@...rew.cmu.edu>,
	Oleg Verych <olecom@...wer.upol.cz>,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: PROBLEM: System Freeze on Particular workload with kernel 2.6.22.6

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.)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/