All of lore.kernel.org
 help / color / mirror / Atom feed
From: balducci@units.it
To: Mel Gorman <mgorman@techsingularity.net>
Cc: bugzilla-daemon@bugzilla.kernel.org, linux-mm@kvack.org,
	akpm@linux-foundation.org
Subject: Re: [Bug 203715] New: BUG: unable to handle kernel NULL pointer dereference under stress (possibly related to https://lkml.org/lkml/2019/5/24/292 ?)
Date: Tue, 11 Jun 2019 11:30:32 +0200	[thread overview]
Message-ID: <3045.1560245456@dschgrazlin2.units.it> (raw)
In-Reply-To: Your message of "Tue, 11 Jun 2019 10:03:45 +0100." <20190611090345.GC28744@techsingularity.net>

Mel Gorman writes:
>
> Any news with this patch?
>

oops: I run the patch and reported by email (CC'ing to bugzilla): either
I botched something with the reporting mail or you missed the email...
(my report is on bugzilla, though, comment 20)

I reproduce the report here:

> no joy; I left the FF build running and found the machine frozen this
> morning; however, firefox build could apparently complete successfully;
> I can't say when exactly the problem happened, as I haven't found any
> message in the logs

I can add that since the last attempt, after rebooting into 5.0.15, I
have built a lot of software (including FF) without any problem; this
enforces me in the conviction that there must be some problem for
kernels >=5.1

Does anybody else reproduce this?

thanks a lot
ciao
-g


      reply	other threads:[~2019-06-11  9:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-203715-27@https.bugzilla.kernel.org/>
2019-05-29 23:04 ` [Bug 203715] New: BUG: unable to handle kernel NULL pointer dereference under stress (possibly related to https://lkml.org/lkml/2019/5/24/292 ?) Andrew Morton
2019-06-04 11:05   ` Mel Gorman
2019-06-04 11:43     ` balducci
2019-06-05 12:38     ` balducci
2019-06-05 12:48       ` Mel Gorman
2019-06-05 17:21       ` Mel Gorman
2019-06-06 13:20         ` balducci
2019-06-06 14:44           ` Mel Gorman
2019-06-11  9:03             ` Mel Gorman
2019-06-11  9:30               ` balducci [this message]

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=3045.1560245456@dschgrazlin2.units.it \
    --to=balducci@units.it \
    --cc=akpm@linux-foundation.org \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    /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.