From: Meelis Roos <mroos@linux.ee>
To: sparclinux@vger.kernel.org
Subject: in:imklog segfault in 4.12+git on most sparc64's
Date: Mon, 10 Jul 2017 08:25:51 +0000 [thread overview]
Message-ID: <alpine.LRH.2.20.1707101111290.5280@math.ut.ee> (raw)
I tested yesterdays git with 4.13 sparc merge on a big bunch of my test
machines.
Good news: the timestamps starting from boot seem to work on all the
machines, starting with Ultra 1 and Ultra 2.
Bad news: all working sun4u machines have the following line in dmesg
(PID varies):
in:imklog[1036]: segfault at 49 ip 0000000000035bb0 (rpc 00000000f779dfa0) sp 00000002f7a78818 error 30002 in rsyslogd[10000+88000]
This is with Debian unstable 32-bit userland as of 2015 summer. It did
not happen with 4.12.
More bad news: all my sun4v machines crash on boot with DMA+IOMMU
problem (will send a separate mail with details).
--
Meelis Roos (mroos@linux.ee)
next reply other threads:[~2017-07-10 8:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 8:25 Meelis Roos [this message]
2017-07-10 8:38 ` in:imklog segfault in 4.12+git on most sparc64's John Paul Adrian Glaubitz
2017-07-10 11:46 ` Meelis Roos
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.1707101111290.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.