From: Randolph Chung <randolph@tausq.org>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] unaligned accesses
Date: Thu, 9 Jan 2003 00:29:02 -0800 [thread overview]
Message-ID: <20030109082902.GF23535@tausq.org> (raw)
In-Reply-To: <200301090755.h097tadb003653@vilmos.org>
> The other question. I am using emacs, and I regularly see these messages:
>
> Jan 8 23:52:33 hp kernel: emacs(17795): unaligned access to 0x001cdaf2 at ip=0x0008937f
> Jan 8 23:52:33 hp kernel: emacs(17795): unaligned access to 0x001cdaf2 at ip=0x0008930b
>
> What are they?
Blame LaMont!
(yes, I'm just kidding, I've just been waiting for my chance to say
this... :-)
On a more serious note, on parisc load/stores to half-words, words,
doublewords have specific address alignment requirements. the message
usually means the program in question is buggy and is making unaligned
accesses. The unaligned access is trapped and emulated by the kernel,
so normally the message itself is simply informational.
This is definitely a FAQ.... maybe we should add it to the list :)
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
next prev parent reply other threads:[~2003-01-09 8:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 7:55 [parisc-linux] Printing problem with HP9000 712/80 and two more questions Vilmos Soti
2003-01-09 8:29 ` Randolph Chung [this message]
2003-01-10 7:29 ` [parisc-linux] unaligned accesses jsoe0708
2003-01-10 7:36 ` Randolph Chung
2003-01-10 8:24 ` jsoe0708
2003-01-10 12:52 ` Matthieu Delahaye
2003-01-10 13:45 ` jsoe0708
2003-01-10 16:29 ` Randolph Chung
2003-01-10 15:30 ` John David Anglin
2003-01-10 10:51 ` jsoe0708
2003-01-10 17:08 ` Matthew Wilcox
2003-01-10 18:47 ` jsoe0708
2003-01-10 22:13 ` Thibaut VARENE
2003-01-10 22:25 ` Thibaut VARENE
2003-01-12 15:25 ` Joel Soete
2003-01-12 16:02 ` Thibaut VARENE
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=20030109082902.GF23535@tausq.org \
--to=randolph@tausq.org \
--cc=parisc-linux@lists.parisc-linux.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.