Linux PARISC architecture development
 help / color / mirror / Atom feed
From: joel.soete@freebel.net
To: Randolph Chung <randolph@tausq.org>
Cc: joel.soete@freebel.net, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] "unaligned access to ... at ip=..." problem with evms and jfs
Date: Thu, 04 Apr 2002 11:46:06 +0200 (CEST)	[thread overview]
Message-ID: <1017913566.3cac20de230de@webmail.tiscalinet.be> (raw)
In-Reply-To: <20020403181337.GA3759@tausq.org>

Quoting Randolph Chung <randolph@tausq.org>:

> > It seems harmless but not sure.
> 
> well.... in general this is not a problem, however....
> 
> Fleedwood found a bug in the unaligned handler last week. it doesn't
> handle the pre/post increment cases of load and store, and there may be
> some cases where these messages will indicate the cause of errors.
> 
> I'll look into fixing this, but it might take some time.
> 

Well I will be patient as till now (at least a month) evms seems to works
correctly :-)

> > I query the ml db and found similar problems (and its solution :_)
> )(reiserfs:
> > http://lists.parisc-linux.org/hypermail/parisc-linux/5862.html), but I
> do not
> > very well understand what I have to find the sources (_u32* ?).
> 
> it depends, you need to make sure all the memory accesses happen on
> natural boundaries...  (e.g. int on 4 byte boundaries, short on 2 byte
> boundaries, etc). From the ip reported by the unaligned message you
> should be able to trace back to the asm insn and function (if your
> objects are not stripped) that is causing the unaligned access.

Humm... in evms (not yet investigate jfs) I notice that 4-byte variables are
pass to function parameters actualy 2-byte without casting. Could this be a reason?

> 
> randolph
> -- 
>    @..@                                         http://www.TauSq.org/
>   (----)
>  ( >__< )
>  ^^ ~~ ^^
> 
> 

Thanks for explanation,
    Joel

-------------------------------------------------
This mail sent through Tiscali Webmail (http://webmail.tiscali.be)

  reply	other threads:[~2002-04-04  9:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-03 17:24 [parisc-linux] "unaligned access to ... at ip=..." problem with evms and jfs joel.soete
2002-04-03 18:13 ` Randolph Chung
2002-04-04  9:46   ` joel.soete [this message]
2002-04-04 15:46     ` John David Anglin
2002-04-08  6:15       ` [parisc-linux] GCC support for dwarf2 joel.soete
2002-04-08 16:08         ` John David Anglin
2002-04-11 11:58           ` joel.soete
2002-04-11 15:31             ` John David Anglin
2002-04-11 16:35               ` joel.soete
2002-04-12 11:49                 ` joel.soete
2002-04-12 16:14                   ` John David Anglin
2002-04-12 16:37                     ` joel.soete
2002-04-15 16:26                     ` [parisc-linux] Patch to debina glibc-2.2.5 for gcc-3.2 build (was GCC support for dwarf2) joel.soete
2002-04-12 21:44                   ` [parisc-linux] GCC support for dwarf2 Carlos O'Donell Jr.
2002-04-15  6:30                     ` joel.soete
2002-08-03 19:27   ` [parisc-linux] "unaligned access to ... at ip=..." problem with evms and jfs Joel Soete
2002-08-07  6:11     ` Randolph Chung
2002-08-07  8:12       ` jsoe0708

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=1017913566.3cac20de230de@webmail.tiscalinet.be \
    --to=joel.soete@freebel.net \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=randolph@tausq.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