From: Matthew Wilcox <willy@debian.org>
To: Peter Weilbacher <weilbach@uni-sw.gwdg.de>
Cc: jfs-discussion@oss.software.ibm.com, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] JFS on PA-RISC-Linux
Date: Tue, 3 Jul 2001 16:15:09 +0100 [thread overview]
Message-ID: <20010703161509.A6103@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.33.0107031224210.15161-100000@leo.uni-sw.gwdg.de>; from weilbach@uni-sw.gwdg.de on Tue, Jul 03, 2001 at 12:51:27PM +0200
On Tue, Jul 03, 2001 at 12:51:27PM +0200, Peter Weilbacher wrote:
> <4>mkfs.jfs(379): unaligned access to 0x00035245 at ip=0x000137af
> Not-handled unaligned insn 0x4a740108
> Unaligned handler failed, ret = -1
>
> (optionally without <4> or with Bus error)
>
> Is it JFS's fault or that of the PA-RISC-Linux port? The messages do
> not seem to be from mkfs.jfs, as I did not find anything like that
> in its source. Is it too early to try things like this?
It's the fault of both, really. The userspace program is attempting to do
an unaligned access. say, loading an int from a non-word-aligned address.
Most CPUs can't handle this and take a fault. We haven't yet implemented
a trap handler for that fault.
Or rather, tausq has implemented one, but hasn't activated it yet,
I believe.... tausq?
--
Revolutions do not require corporate support.
next prev parent reply other threads:[~2001-07-03 15:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010702180851.A19547@nickel.kgarner.com>
2001-07-03 10:51 ` [parisc-linux] JFS on PA-RISC-Linux Peter Weilbacher
2001-07-03 15:15 ` Matthew Wilcox [this message]
2001-07-03 16:01 ` Randolph Chung
2001-07-03 15:21 ` Grant Grundler
2001-07-03 15:26 ` Matthew Wilcox
2001-08-14 10:46 ` [parisc-linux] Once more: JFS Peter Weilbacher
2001-08-14 15:25 ` Randolph Chung
2001-08-14 16:24 ` Peter Weilbacher
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=20010703161509.A6103@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=jfs-discussion@oss.software.ibm.com \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=weilbach@uni-sw.gwdg.de \
/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.