mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Meelis Roos <mroos@linux.ee>
To: David Miller <davem@davemloft.net>
Cc: aaro.koskinen@iki.fi, sparclinux@vger.kernel.org,
	linux-kernel@vger.kernel.org, hughd@google.com
Subject: Re: sparc64 WARNING: at mm/mmap.c:2757 exit_mmap+0x13c/0x160()
Date: Mon, 9 Jun 2014 09:36:33 +0300 (EEST)	[thread overview]
Message-ID: <alpine.SOC.1.00.1406090931470.5548@math.ut.ee> (raw)
In-Reply-To: <20140524.170834.1561021346958622230.davem@davemloft.net>

> > This is todays fresh git with 3.15.0-rc6-00190-g1ee1cea on V210, THP 
> > enabled & always on. Got this and a segfault on apt-spawned xz.
> 
> Thanks a lot for the report.
> 
> I've been bogged down with other things but I will come back to
> this stuff soon.

Just to document a strangeness that does not seem to fit the pattern of 
UltraSparc III era split: 

V210 with USIII family CPUs is still problematic (can not survive 
repetituos local git clone, hangs (watchdog detects hang) with 
filesystem corruption. This still holds for 3.15 release.

On the other hand, E420R with 4 USII CPUs does not hang and works 100% 
stable with git clones etc. Very similar E220R with different config 
hangs on that load.

Maybe related to some other options in kernel configs - each config is 
unique and they vary intentionally.

-- 
Meelis Roos (mroos@linux.ee)

      reply	other threads:[~2014-06-09  6:36 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
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 [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=alpine.SOC.1.00.1406090931470.5548@math.ut.ee \
    --to=mroos@linux.ee \
    --cc=aaro.koskinen@iki.fi \
    --cc=davem@davemloft.net \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --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®