From: Bob Tracy <rct@frus.com>
To: debian-alpha@lists.debian.org
Cc: linux-alpha@vger.kernel.org
Subject: dbus-daemon unaligned accesses
Date: Sat, 18 Jan 2020 10:06:23 -0600 [thread overview]
Message-ID: <20200118160623.GA2136@gherkin.frus.com> (raw)
On my alpha, the system logs are getting spammed with unaligned trap
errors as follows:
[34656.586748] dbus-daemon(700): unaligned trap at 00000200000a9720: 00000000d68c7222 28 18
[34656.599443] dbus-daemon(700): unaligned trap at 00000200000a9720: 00000000d68c7222 28 18
[34656.612138] dbus-daemon(700): unaligned trap at 00000200000a9720: 00000000d68c7222 28 18
[34656.617021] dbus-daemon(700): unaligned trap at 00000200000a9720: 00000000d68c7222 28 18
[34656.624833] dbus-daemon(700): unaligned trap at 00000200000a9720: 00000000d68c7222 28 18
The current "dbus" package version is 1.12.16-2.
If no one else is actively working to fix this annoyance, I'll see what
I can do. For me, it's mostly a matter of finding the time to download
the source package and its dependencies, build a debug version with
symbols in it that "gdb" can use, and then *maybe* figure out the best
way to code around the unaligned access.
If anyone else has the time and would like to have a go at it, the
following two links might be useful:
https://wiki.gentoo.org/wiki/Project:Alpha/Porting_guide#Unaligned_accesses
https://www.redhat.com/archives/axp-list/2000-May/msg00151.html
(Yes, the problem has been around at least as long as the alpha
architecture :-) ).
Michael Cree et al.: do we have a working "gdb" on alpha these days?
I seem to recall brokenness there in the not-too-distant past.
--Bob
next reply other threads:[~2020-01-18 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-18 16:06 Bob Tracy [this message]
2020-01-18 16:36 ` dbus-daemon unaligned accesses John Paul Adrian Glaubitz
2020-01-18 17:33 ` Witold Baryluk
2020-01-19 5:49 ` Bob Tracy
2020-01-19 15:02 ` Witold Baryluk
2020-01-19 22:42 ` Witold Baryluk
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=20200118160623.GA2136@gherkin.frus.com \
--to=rct@frus.com \
--cc=debian-alpha@lists.debian.org \
--cc=linux-alpha@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