Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Torsten Neumann <torsten@imke.infodrom.ffis.de>,
	parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Problems compiling LVM
Date: Thu, 28 Jun 2001 21:36:15 +0200	[thread overview]
Message-ID: <20010628193654.0239E482A@dsl2.external.hp.com> (raw)
In-Reply-To: <20010628202937.A13724@imke.infodrom.ffis.de>

Hi Torsten,

The problem is that your userspace program tries to do a direct 16 or 32-bit 
read- or write-access to address 0x40067cf3 - which lies on a "unaligned 
address" (e.g. not a a 32-bit boundary). 
On Intel architectures this fault is automatically handled by the hardware, 
while you get an unaligned access trap on parisc.

The first parisc-kernel which should handle this trap correctly is 2.4.0-pa39 
(in CVS), so I would encourage you to update your kernel.

Greetings,
Helge

On Thursday 28 June 2001 20:29, Torsten Neumann wrote:
> Hi,
>
> the linux-lvm code was inspired by the hp-ux LVM. So I thougt it would be
> real cool if the linux-lvm runs under hppa-linux.
> Compiling the kernel with lvm support is no problem, the userspace tools
> have some problems with gcc-3 (code uses #ifdef constructs in printf
> macro), but then also compiles cleanly.
>
> Now I want to create a VG but I only got the error message
> imke kernel: pvcreate(188): unaligned access to 0x40067cf3 at ip=0x400310db
> imke kernel: Not-handled unaligned insn 0x48350376
>
> >from the program pvcreate.
>
> Could somebody tell what kind of problem this is. Is it a kernel problem or
> a userspace problem ?
> Is there a way to avoid this problem ?
>
>   Torsten

  reply	other threads:[~2001-06-28 19:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-28 18:29 [parisc-linux] Problems compiling LVM Torsten Neumann
2001-06-28 19:36 ` Helge Deller [this message]
     [not found] ` <20010628193653.77706115D6@finlandia.infodrom.north.de>
2001-06-28 20:14   ` Torsten Neumann
2001-06-28 20:26     ` Randolph Chung

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=20010628193654.0239E482A@dsl2.external.hp.com \
    --to=deller@gmx.de \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=torsten@imke.infodrom.ffis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox