From: Meelis Roos <mroos@linux.ee>
To: sparclinux@vger.kernel.org
Subject: Re: in:imklog segfault in 4.12+git on most sparc64's
Date: Mon, 10 Jul 2017 11:46:19 +0000 [thread overview]
Message-ID: <alpine.LRH.2.20.1707101442220.5280@math.ut.ee> (raw)
In-Reply-To: <alpine.LRH.2.20.1707101111290.5280@math.ut.ee>
> > This is with Debian unstable 32-bit userland as of 2015 summer. It did
> > not happen with 4.12.
>
> Did you also perform tests with a current 64-bit userland?
No, for the current test this is not relevant since if the breakage
happens with some userlan, it is kernel at fault.
I have tested sparc64 debian-port on my T5120 where I expected it to be
fast. For some test it was faster than 32-bit userland. for some things
slower, but it worked.
I never tested it on older machines so far. I might have tried
installing on Blade 150 (I am not sure if it was sparc or sparc64) but
the install was hanging, and I have not finished with it as I suspected
the PSU that I had just replaced and I have had no time to to hardware
bisecting with Blade 100.
--
Meelis Roos (mroos@linux.ee)
next prev parent reply other threads:[~2017-07-10 11:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 8:25 in:imklog segfault in 4.12+git on most sparc64's Meelis Roos
2017-07-10 8:38 ` John Paul Adrian Glaubitz
2017-07-10 11:46 ` Meelis Roos [this message]
2017-07-10 11:48 ` John Paul Adrian Glaubitz
2017-07-10 18:31 ` David Miller
2017-07-10 18:32 ` David Miller
2017-07-10 18:35 ` John Paul Adrian Glaubitz
2017-07-10 18:42 ` David Miller
2017-07-10 18:47 ` John Paul Adrian Glaubitz
2017-07-11 11:48 ` Meelis Roos
2017-07-11 11:48 ` Meelis Roos
2017-07-12 3:13 ` David Miller
2017-07-12 3:13 ` David Miller
2017-07-12 3:59 ` Al Viro
2017-07-12 3:59 ` Al Viro
2017-07-12 4:09 ` David Miller
2017-07-12 4:09 ` David Miller
2017-07-12 7:09 ` Meelis Roos
2017-07-12 7:09 ` Meelis Roos
2017-07-12 16:09 ` David Miller
2017-07-12 16:09 ` David Miller
2017-07-12 16:14 ` Linus Torvalds
2017-07-12 16:14 ` Linus Torvalds
2017-07-11 13:56 ` David Miller
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.LRH.2.20.1707101442220.5280@math.ut.ee \
--to=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 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.