mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: aaro.koskinen@iki.fi
Cc: mroos@linux.ee, sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: sparc64 WARNING: at mm/mmap.c:2757 exit_mmap+0x13c/0x160()
Date: Tue, 22 Oct 2013 13:54:42 -0400 (EDT)	[thread overview]
Message-ID: <20131022.135442.1072093301788210177.davem@davemloft.net> (raw)
In-Reply-To: <20131022174612.GC24448@blackmetal.musicnaut.iki.fi>

From: Aaro Koskinen <aaro.koskinen@iki.fi>
Date: Tue, 22 Oct 2013 20:46:12 +0300

> Hi,
> 
> On Sat, Aug 03, 2013 at 01:40:42PM -0700, David Miller wrote:
>> > On Mon, Jun 17, 2013 at 08:32:25AM +0300, Aaro Koskinen wrote:
>> >> On Mon, Jun 17, 2013 at 12:06:00AM +0300, Meelis Roos wrote:
>> >> > Got this in 3.10-rc6 whil testing debian unstable upgrade with aptitude. 
>> >> > 3.10-rc5 did not exhibit this (nor any other kernel recently tried, 
>> >> > including most -rc's). Does not seem to be reproducible.
>> >> 
>> >> I get this regularly on Ultrasparc during long compilations. It's been
>> >> there with all recent kernels (probably at least since 3.8). Latest I
>> >> saw with 3.10-rc5.
>> > 
>> > Two examples:
>> 
>> Thanks for the reports, I'm actively looking into this.
> 
> Got this again with 3.12-rc5 while doing GCC 4.8.2 bootstrap (during
> make check phase):
 ...
> The box didn't die yet... Let's hope it will let GCC testsuite to finish.

Thanks for reporting this again, it's in my long TODO list to look into
still.

  reply	other threads:[~2013-10-22 17:54 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-16 21:06 Meelis Roos
2013-06-17  5:32 ` Aaro Koskinen
2013-06-17  5:58   ` Aaro Koskinen
2013-08-03 20:40     ` David Miller
2013-10-22 17:46       ` Aaro Koskinen
2013-10-22 17:54         ` David Miller [this message]
2014-04-14 18:43           ` Aaro Koskinen
2014-04-14 18:58             ` David Miller
2014-04-16 18:58             ` David Miller
2014-04-16 22:22               ` mroos
2014-04-16 22:49                 ` David Miller
2014-07-29 23:26                 ` David Miller
2014-07-30 22:02                   ` Meelis Roos
2014-07-30 22:07                     ` David Miller
2014-08-13 11:44                       ` Meelis Roos
2014-08-13 19:46                         ` David Miller
2014-08-14 12:20                           ` Meelis Roos
2014-08-15 12:42                           ` Meelis Roos
2014-08-18 12:30                             ` Meelis Roos
2014-08-18 17:35                               ` Aaro Koskinen
2014-08-18 17:38                                 ` David Miller
2014-08-30 22:27                                   ` Aaro Koskinen
2014-08-18 23:45                                 ` Julian Calaby
2014-08-19 21:29                                   ` Aaro Koskinen
2014-08-19  8:22                   ` Meelis Roos
2014-04-25 20:09               ` Aaro Koskinen
2014-04-25 20:17                 ` David Miller
2014-05-24 20:02                   ` mroos
2014-05-24 21:08                     ` David Miller
2014-06-09  6:36                       ` Meelis Roos

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=20131022.135442.1072093301788210177.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=aaro.koskinen@iki.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mroos@linux.ee \
    --cc=sparclinux@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®