Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Subject: RE: Help: strange messages from kernel on IA64 platform
Date: Tue, 16 May 2006 15:12:51 -0600
Message-ID: <890BF3111FB9484E9526987D912B261901BD86@NAMAIL3.ad.lsil.com>
Thread-Topic: Help: strange messages from kernel on IA64 platform
Thread-Index: AcZ5K7zvpC6zXIW4ShqByfERQdSNcAAASG9w
From: "Ju, Seokmann" <Seokmann.Ju@lsil.com>
To: "Chase Venters" <chase.venters@clientec.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
       <linux-scsi@vger.kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1952
Lines: 64

Hi,

Tuesday, May 16, 2006 5:00 PM, Chase Venters wrote:
> It's a trap, which means the CPU is effectively calling that 
> function.
O.K, that's why...
Then, Is there anyway to look up trap table that the CPU has?
> My best suggestion is to figure out what data is at 
> 0xe00000007f3d80dc and 
> what instructions are at 0xa0000002000373b1.
I will try as you suggested.
Thank you very much for comment.

Regards,

> -----Original Message-----
> From: Chase Venters [mailto:chase.venters@clientec.com] 
> Sent: Tuesday, May 16, 2006 5:00 PM
> To: Ju, Seokmann
> Cc: Linux Kernel Mailing List; linux-scsi@vger.kernel.org
> Subject: Re: Help: strange messages from kernel on IA64 platform
> 
> On Tue, 16 May 2006, Ju, Seokmann wrote:
> 
> > Hi,
> >
> > During communication in between application and megaraid driver via
> > IOCTL, the system displays messages which are not easy to 
> track down.
> > Following is one of the messages and same messages with 
> different values
> > are poping up regularly.
> > ---
> > Kernel unaligned access to 0xe00000007f3d80dc ip=0xa0000002000373b1
> > ---
> >
> > I understand the kernel is complaining about the address 
> which is not
> > aligned and, found the message is coming from function
> > 'ia64_handle_unaligned()' in the arch/ia64/kernel/unaligned.c.
> > But, I couldn't find who is calling this function and 
> further details of
> > reasons.
> >
> > Where should I start to figure out it?
> 
> It's a trap, which means the CPU is effectively calling that 
> function. My 
> best suggestion is to figure out what data is at 
> 0xe00000007f3d80dc and 
> what instructions are at 0xa0000002000373b1.
> 
> > Thank you,
> >
> > Seokmann
> 
> Thanks,
> Chase
> 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/