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,
cat.schulze@alice-dsl.net
Subject: Re: sparc64 WARNING: at mm/mmap.c:2757 exit_mmap+0x13c/0x160()
Date: Wed, 13 Aug 2014 14:44:42 +0300 (EEST) [thread overview]
Message-ID: <alpine.SOC.1.00.1408131327250.18696@math.ut.ee> (raw)
In-Reply-To: <20140730.150722.861254999466992321.davem@davemloft.net>
I tested the merged sparc64 fixes in current git.
V100: with hugetlb, looping git clone still hangs the machine. RED
state on reboot has changed - before it gave the trace on reboot and
continued, now it contonues looping with the trace indefinitely, gcc
4.6.4
Netra X1: works fine with HugeTLB (but no hugetlbfs) and looping git
clone, gcc 4.6.4.
V440: fails to boot with 3.16 and gcc 4.9.1 (same message as before, in
fault_in_user_windows+0xe0/0x100). Tried latest git with gcc 4.9.1 but
it stops after before getting to the previous failure point:
[ 77.871887] console [tty0] enabled
[ 77.912630] bootconsole [earlyprom0] disabled
T2000: works fine with gcc 4.9.1 and hugetlb, 3.16. Hangs at boot at the
same point.
U2: looping git clone fails with 3.16, no hugetlb(!!!), gcc 4.6.4;
E420R: works fine with gcc 4.6.4. 3.16, hugetlb, looping git clone;
fails to boot with current git
E220R: works with gcc 4.6.4, no hugetlb, 3.16. Hangs on boot with
current git + hugetlb.
Did not test current git more. Will test the patches on top of 3.16
separately to see if/which one of these is the culprit.
--
Meelis Roos (mroos@linux.ee)
next prev parent reply other threads:[~2014-08-13 11:45 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 [this message]
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=alpine.SOC.1.00.1408131327250.18696@math.ut.ee \
--to=mroos@linux.ee \
--cc=aaro.koskinen@iki.fi \
--cc=cat.schulze@alice-dsl.net \
--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®