From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: linux-parisc@vger.kernel.org
Subject: Running the gdb 7.12.1 testsuite breaks kernel 4.13.8 on C8000
Date: Thu, 25 Jan 2018 09:59:03 +0100 [thread overview]
Message-ID: <11946948.1Lt8Nslq4k@devpool21> (raw)
The last message I had for the crash below is:
Running /var/tmp/portage/sys-devel/gdb-7.12.1/work/gdb-7.12.1/gdb/testsuite/gdb.base/bp-permanent.exp ...
[ 909.754182] Backtrace:
[ 909.756303]
[ 909.756303]
[ 909.756303] Bad Address (null pointer deref?): Code=6 (Instruction TLB miss fault) regs=000000007c818a50 (Addr=0000000000000000)
[ 909.756303] CPU: 0 PID: 5191 Comm: bp-permanent Not tainted 4.13.8 #2
[ 909.756303] task: 000000007c8183d0 task.stack: 000000007aad8000
[ 909.756303]
[ 909.756303] YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
[ 909.756303] PSW: 00000000000001000000011100001111 Not tainted
[ 909.756303] r00-03 000000000004070f 00000000f8f07840 00000000000106bb 00000000f8f07880
[ 909.756303] r04-07 00000000f815bc70 00000000000e87a0 0000000000000000 00000000000e8818
[ 909.756303] r08-11 0000000000000000 0000000000000000 000000000000006c 0000000000000000
[ 909.756303] r12-15 0000000000000000 0000000000000000 0000000000080a74 00000000000e83f8
[ 909.756303] r16-19 00000000000c85c8 00000000000cbad8 00000000000c99e8 00000000f815bc70
[ 909.756303] r20-23 00000000000120bc 0000000000000004 ffffffffffffe520 0000000000012022
[ 909.756303] r24-27 00000000000120bc 00000000000105d8 00000000000120b8 0000000000012000
[ 909.756303] r28-31 00000000000120b8 0000000000000001 00000000f8f078c0 00000000f8bffa9f
[ 909.756303] sr00-03 00000000010a1800 00000000010a1800 0000000000000000 00000000010a1800
[ 909.756303] sr04-07 00000000010a1800 00000000010a1800 00000000010a1800 00000000010a1800
[ 909.756303]
[ 909.756303] IASQ: 00000000010a1800 00000000010a1800 IAOQ: 0000000000000000 0000000000000004
[ 909.756303] IIR: 43ffff80 ISR: 0000000010240000 IOR: 000000a43fb07880
[ 909.756303] CPU: 0 CR30: 000000007aad8000 CR31: ffffffffffffffff
[ 909.756303] ORIG_R28: 0000000000000000
[ 909.756303] IAOQ[0]: (null)
[ 909.756303] IAOQ[1]: 0x4
[ 909.756303] RP(r2): 0x106bb
[ 909.756303] Backtrace:
[ 909.756303]
[ 909.756303] Kernel panic - not syncing: Bad Address (null pointer deref?)
[ 909.756303] ---[ end Kernel panic - not syncing: Bad Address (null pointer deref?)
This is actually the second place where it breaks, before that I had the same
with this test (twice):
Running /var/tmp/portage/sys-devel/gdb-7.12.1/work/gdb-7.12.1/gdb/testsuite/gdb.base/async.exp ...
It's a Gentoo system, the kernel has been built with gcc 6.4.0.
next reply other threads:[~2018-01-25 8:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 8:59 Rolf Eike Beer [this message]
2018-01-25 13:01 ` Running the gdb 7.12.1 testsuite breaks kernel 4.13.8 on C8000 John David Anglin
2018-01-25 15:36 ` Rolf Eike Beer
2018-01-26 22:31 ` Helge Deller
2018-01-27 17:42 ` Rolf Eike Beer
2018-01-27 18:41 ` Helge Deller
2018-01-28 19:01 ` John David Anglin
2019-06-30 10:05 ` Rolf Eike Beer
2019-06-30 13:43 ` Rolf Eike Beer
2019-06-30 19:59 ` Helge Deller
2019-07-02 15:59 ` Helge Deller
2019-07-16 20:01 ` Helge Deller
2019-07-17 17:52 ` Rolf Eike Beer
2019-07-17 18:13 ` John David Anglin
2019-07-17 21:00 ` Helge Deller
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=11946948.1Lt8Nslq4k@devpool21 \
--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;
as well as URLs for NNTP newsgroup(s).