linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Sedat Dilek <sedat.dilek@gmail.com>
To: Zlatko Calusic <zlatko.calusic@iskon.hr>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-mm <linux-mm@kvack.org>
Subject: Re: BUG: unable to handle kernel NULL pointer dereference at 0000000000000500
Date: Fri, 28 Dec 2012 01:24:22 +0100	[thread overview]
Message-ID: <CA+icZUUXbCCtPaimG6hKsSUQTmnoMAZHsd_nrn7eityepqYUkQ@mail.gmail.com> (raw)
In-Reply-To: <50DCDEE5.9000700@iskon.hr>

On Fri, Dec 28, 2012 at 12:51 AM, Zlatko Calusic
<zlatko.calusic@iskon.hr> wrote:
> On 28.12.2012 00:42, Sedat Dilek wrote:
>>
>> On Fri, Dec 28, 2012 at 12:39 AM, Zlatko Calusic
>> <zlatko.calusic@iskon.hr> wrote:
>>>
>>> On 28.12.2012 00:30, Sedat Dilek wrote:
>>>>
>>>>
>>>> Hi Zlatko,
>>>>
>>>> I am not sure if I hit the same problem as described in this thread.
>>>>
>>>> Under heavy load, while building a customized toolchain for the Freetz
>>>> router project I got a BUG || NULL pointer derefence || kswapd ||
>>>> zone_balanced || pgdat_balanced() etc. (details see my screenshot).
>>>>
>>>> I will try your patch from [1] ***only*** on top of my last
>>>> Linux-v3.8-rc1 GIT setup (post-v3.8-rc1 mainline + some net-fixes).
>>>>
>>>
>>> Yes, that's the same bug. It should be fixed with my latest patch, so I'd
>>> appreciate you testing it, to be on the safe side this time. There should
>>> be
>>> no difference if you apply it to anything newer than 3.8-rc1, so go for
>>> it.
>>> Thanks!
>>>
>>
>> Not sure how I can really reproduce this bug as one build worked fine
>> within my last v3.8-rc1 kernel.
>> I increased the parallel-make-jobs-number from "4" to "8" to stress a
>> bit harder.
>> Just building right now... and will report.
>>
>> If you have any test-case (script or whatever), please let me/us know.
>>
>
> Unfortunately not, I haven't reproduced it yet on my machines. But it seems
> that bug will hit only under heavy memory pressure. When close to OOM, or
> possibly with lots of writing to disk. It's also possible that fragmentation
> of memory zones could provoke it, that means testing it for a longer time.
>

I tested successfully by doing simultaneously...
- building Freetz with 8 parallel make-jobs
- building Linux GIT with 1 make-job
- 9 tabs open in firefox
- In one tab I ran YouTube music video
- etc.

I am reading [1] and [2] where another user reports success by reverting this...

commit cda73a10eb3f493871ed39f468db50a65ebeddce
"mm: do not sleep in balance_pgdat if there's no i/o congestion"

BTW, this machine has also 4GiB RAM (Ubuntu/precise AMD64).

Feel free to add a "Reported-by/Tested-by" if you think this is a
positive report.

- Sedat -

[1] http://marc.info/?l=linux-mm&m=135652835931174&w=2
[2] http://marc.info/?l=linux-mm&m=135653399800655&w=2

> --
> Zlatko

--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2012-12-28  0:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-27 23:30 Sedat Dilek
2012-12-27 23:39 ` Zlatko Calusic
2012-12-27 23:42   ` Sedat Dilek
2012-12-27 23:51     ` Zlatko Calusic
2012-12-28  0:24       ` Sedat Dilek [this message]
2012-12-28  0:33         ` Zlatko Calusic
2012-12-28  0:37           ` Sedat Dilek
2012-12-28  0:42             ` Zlatko Calusic
2012-12-28  0:56               ` Sedat Dilek
  -- strict thread matches above, loose matches on Subject: below --
2012-12-25  4:38 kernel BUG at mm/huge_memory.c:1798! Zhouping Liu
2012-12-26 11:22 ` BUG: unable to handle kernel NULL pointer dereference at 0000000000000500 Zhouping Liu
2012-12-26 12:01   ` Hillf Danton
2012-12-26 13:24     ` Zhouping Liu
2012-12-26 15:14       ` Hillf Danton
2012-12-26 14:59   ` Zlatko Calusic
2012-12-27 14:58   ` Zlatko Calusic
     [not found]     ` <20121227235514.GA7166@ganymede>
2012-12-28  0:09       ` Zlatko Calusic
2012-12-28  2:45     ` Zhouping Liu
2012-12-28  2:48       ` Zhouping Liu
2012-12-28  9:01       ` Zhouping Liu
2012-12-28 13:43         ` Zlatko Calusic
2012-12-28 12:57       ` Zlatko Calusic

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=CA+icZUUXbCCtPaimG6hKsSUQTmnoMAZHsd_nrn7eityepqYUkQ@mail.gmail.com \
    --to=sedat.dilek@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=zlatko.calusic@iskon.hr \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox