From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: linux-parisc@vger.kernel.org
Subject: 3.12.8 is doing nasty things
Date: Fri, 24 Jan 2014 21:44:51 +0100 [thread overview]
Message-ID: <2696873.HIAXvrDslF@caliban.sf-tec.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 3404 bytes --]
I reported that I saw strange things happening after upgrading to 3.12.5.
Meanwhile I upgraded to 3.12.8 and things became worse. I regularly see
processes to fail randomly. I can see this as I somethimes get failures in my
nagios because the SSH connection to the watched host (only the watched one
runs .8) fails. I then see stuff like this in dmesg:
[723945.604000] do_page_fault() pid=30516 command='sshd' type=15
address=0x00000000
[723945.604000] CPU: 1 PID: 30516 Comm: sshd Not tainted 3.12.8 #1
[723945.604000] task: 000000023f0eb7c8 ti: 00000002397ac000 task.ti:
00000002397ac000
[723945.604000] YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
[723945.604000] PSW: 00000000000001001111111100001111 Not tainted
[723945.604000] r00-03 000000ff0004ff0f 0000000040c3dc64 0000000040b63027
0000000000000000
[723945.604000] r04-07 0000000040c3d464 0000000000000000 000000000008d11c
0000000000089ca0
[723945.604000] r08-11 000000000008d11c 000000000008991c 000000000008811c
000000000008811c
[723945.604000] r12-15 000000000008811c 0000000000000000 000000000008811c
00000000000888a8
[723945.604000] r16-19 000000000006eb1c 000000000006eb3c 000000000006e440
0000000040c3d464
[723945.604000] r20-23 00000000fb014990 000000004145eb40 0000000000000000
0000000000000095
[723945.604000] r24-27 00000000fffffff5 0000000040002890 00000000fb014988
000000000008711c
[723945.604000] r28-31 fffffffffffffffe 0000000000000000 00000000fb014a00
0000000040b644c3
[723945.604000] sr00-03 0000000006807000 0000000000000000 0000000000000000
0000000006807000
[723945.604000] sr04-07 0000000006807000 0000000006807000 0000000006807000
0000000006807000
[723945.604000] VZOUICununcqcqcqcqcqcrmunTDVZOUI
[723945.604000] FPSR: 00000000000000000000000000000000
[723945.604000] FPER1: 00000000
[723945.604000] fr00-03 0000000000000000 0000000000000000 0000000000000000
0000000000000000
[723945.604000] fr04-07 41d4b5f44002d0e5 0000000000000000 0000000000000000
0000000000000000
[723945.604000] fr08-11 0000000000000000 0000000000000000 0000000000000000
0000000000000000
[723945.604000] fr12-15 41d4b5f44002d0e5 0000000000000000 0000000000000000
0000000000000000
[723945.604000] fr16-19 0000000000000000 0000000000000000 0000000000000000
0000000000000000
[723945.604000] fr20-23 0000000000000000 0000000000000000 0000000000469971
0000000600000000
[723945.604000] fr24-27 0000000034a94675 0000000000000000 0000000000000000
0000000000000000
[723945.604000] fr28-31 0000000000000000 0000000000000000 0000000000000000
0000000000000000
[723945.604000] IASQ: 0000000006807000 0000000006807000 IAOQ: 0000000040b63033
0000000040b63037
[723945.604000] IIR: 0ca0109c ISR: 0000000006807000 IOR: 0000000000000000
[723945.604000] CPU: 1 CR30: 00000002397ac000 CR31: ffffffffffffffff
[723945.604000] ORIG_R28: 0000000000000000
[723945.604000] IAOQ[0]: 0000000040b63033
[723945.604000] IAOQ[1]: 0000000040b63037
[723945.604000] RP(r2): 0000000040b63027
When I upgraded OpenSSL I also saw an ICE during build, which went away on the
next try.
I also see a lot of those:
[724507.480000] INEQUIVALENT ALIASES 0x42ed0000 and 0x42ed1000 in file
libwrap.so.0.7.6
That could be the binutils bug that was mentioned, this file is from 2010. I'll
rebuild that now to get rid of those warnings.
Next week I'll try 3.13, but since it has the same changes I expect the same
results.
Eike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2014-01-24 20:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 20:44 Rolf Eike Beer [this message]
2014-01-24 21:07 ` 3.12.8 is doing nasty things Jeroen Roovers
2014-01-24 21:26 ` Guy Martin
2014-01-25 22:30 ` James Bottomley
2014-01-25 22:40 ` Rolf Eike Beer
2014-02-11 15:30 ` Rolf Eike Beer
2014-02-13 6:37 ` Rolf Eike Beer
2014-02-15 7:47 ` Rolf Eike Beer
2014-02-25 17:13 ` Rolf Eike Beer
2014-02-26 14:26 ` Aw: " Helge Deller
2014-02-26 16:00 ` John David Anglin
2014-02-26 16:06 ` Rolf Eike Beer
2014-02-26 19:20 ` Jeroen Roovers
2014-02-26 19:33 ` John David Anglin
2014-02-26 19:32 ` Aaro Koskinen
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=2696873.HIAXvrDslF@caliban.sf-tec.de \
--to=eike-kernel@sf-tec.de \
--cc=linux-parisc@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