From: Randolph Chung <randolph@tausq.org>
To: Peter Weilbacher <weilbach@uni-sw.gwdg.de>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Once more: JFS
Date: Tue, 14 Aug 2001 08:25:32 -0700 [thread overview]
Message-ID: <20010814082532.A15709@tausq.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0108141157560.12006-100000@leo.uni-sw.gwdg.de>
> And hundreds more similar errors when doing a manual fsck.jfs are
> written to kern.log, and this check never finishes...
>
> This time it seems to be a PA-RISC-Linux problem, as I recall
> earlier problems with "unaligned access" messages.
The unaligned messages by themselves indicate a *user-space* problem. We can
look at the fsck.jfs code and see what it's doing.... my guess is that
there's some casting going on that is causing the unaligned accesses.
For example, if you had something like this:
char foo[10];
long *bar = (long *)(foo+2);
*bar = 10;
then it will trigger an unaligned access. (usually it's not quite that
obvious though)
If you see a "Not-handled unaligned access" message then there's a
kernel issue that we need to address, but doesn't seem to be the case
here.
Please visit http://bugs.parisc-linux.org/ and follow the instructions
to file a bug, and we will look into this.
randolph
--
@..@ http://www.TauSq.org/
(----)
( >__< )
^^ ~~ ^^
next prev parent reply other threads:[~2001-08-14 15:26 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
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 [this message]
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=20010814082532.A15709@tausq.org \
--to=randolph@tausq.org \
--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.