From: Dave Jones <davej@redhat.com>
To: M <sah_8@yahoo.com>
Cc: linux-mm@kvack.org
Subject: Re: kernel crash
Date: Thu, 22 Sep 2011 17:24:32 -0400 [thread overview]
Message-ID: <20110922212432.GB25623@redhat.com> (raw)
In-Reply-To: <1316717125.61795.YahooMailClassic@web162017.mail.bf1.yahoo.com>
On Thu, Sep 22, 2011 at 11:45:25AM -0700, M wrote:
> Hi,
>
> I am running Fedora 15 644bit on AMD 64bit arch. After update 3 days ago, kernel started to crash when I submit a heavy computation job. It happened today also with similar type of job.
>
> I submitted a bug report to https://bugzilla.redhat.com/ d=740613 . They referred me to contact linux memory management group. I have also uploaded my log file in the bug report. I will be very happy to provide more information if required to resolve this issue.
>
> Thanks.
(fixed url is https://bugzilla.redhat.com/show_bug.cgi?id=740613)
Manoj's report here has a system with 32GB of RAM and 40GB of swap
oomkill'ing processes when there seems to be ram still available.
I note the gfp mask of the failing allocations has GFP_HIGHMEM,
and this apparently doesn't happen when he runs 32-bit.
Could that be a clue ?
Dave
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-09-22 21:24 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 18:45 kernel crash M
2011-09-22 21:24 ` Dave Jones [this message]
2011-09-22 21:38 ` David Rientjes
2011-09-22 21:53 ` Dave Jones
-- strict thread matches above, loose matches on Subject: below --
2014-01-16 10:24 Kernel Crash Nieścierowicz Adam
2012-05-30 17:35 Kernel crash Guido Winkelmann
2012-06-08 16:35 ` Tommi Virtanen
2011-10-06 21:59 kernel crash Pau Espin Pedrol
2008-01-29 10:32 fenglg
2008-01-29 13:34 ` Patrick McHardy
2008-01-29 17:55 ` Jan Engelhardt
2008-01-29 17:59 ` Patrick McHardy
2007-12-30 18:25 Jerry Geis
2006-02-11 5:37 Kernel Crash Jayaprakash Shanmugam
2005-01-19 12:54 Kernel crash Ian Pratt
2005-01-19 14:04 ` Tobias Hunger
2005-01-19 15:12 ` Keir Fraser
2005-01-19 16:54 ` Derrik Pates
2005-01-19 21:05 ` Tobias Hunger
2005-01-20 8:56 ` Keir Fraser
2005-01-20 10:00 ` Tobias Hunger
2005-01-20 11:30 ` Keir Fraser
2005-01-20 22:55 ` Tobias Hunger
2005-01-19 17:46 ` Philip R Auld
2005-01-19 1:31 Ian Pratt
2005-01-19 10:52 ` Tobias Hunger
2005-01-18 21:50 Tobias Hunger
2004-09-05 18:51 Giuliano Pochini
2004-09-06 15:16 ` Takashi Iwai
2004-09-07 7:55 ` Giuliano Pochini
2003-05-29 20:41 kernel crash Gordon Messmer
2003-05-29 21:20 ` John M Flinchbaugh
2003-05-29 22:36 ` Martin Josefsson
2003-05-30 4:23 ` Gordon Messmer
2003-05-30 10:53 ` Martin Josefsson
2003-05-30 10:18 ` Eicke Friedrich
2002-06-26 11:02 Pavel Gulchouck
2002-06-26 19:03 ` James Stevenson
2002-06-27 8:00 ` Pavel Gulchouck
2001-04-12 15:16 Cyrille Ngalle
2001-04-12 15:31 ` Russell King
2001-04-13 13:16 ` nak
2001-04-02 16:40 Wayne.Brown
2001-04-01 10:15 nak
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=20110922212432.GB25623@redhat.com \
--to=davej@redhat.com \
--cc=linux-mm@kvack.org \
--cc=sah_8@yahoo.com \
/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.