[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4D3A0DC9.8010101@oldelvet.org.uk>
Date: Fri, 21 Jan 2011 22:50:49 +0000
From: Richard Mortimer <richm@...elvet.org.uk>
To: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
CC: David Miller <davem@...emloft.net>, rostedt@...dmis.org,
609371@...s.debian.org, ben@...adent.org.uk,
sparclinux@...r.kernel.org, linux-kernel@...r.kernel.org,
fweisbec@...il.com, mingo@...hat.com
Subject: Re: Bug#609371: linux-image-2.6.37-trunk-sparc64: module scsi_mod:
Unknown relocation: 36
On 21/01/2011 20:40, Mathieu Desnoyers wrote:
> * Richard Mortimer (richm@...elvet.org.uk) wrote:
> [...]
>> P.S. I saw your followup mail so hopefully this matches what you have found!
>
> Thanks for the info! At first glance, it does not seem to contradict my
> findings. When you find time, can you have a try at v3 I just posted ?
>
I'm setting the compilation off now. I will give it a whirl some time
Saturday or Sunday.
Before I did that I created kernel/sched.s and have verified that the
two error locations are accesses to it_func_ptr as you suspected.
ldx [%g1+%lo(__tracepoint_sched_wakeup)+28], %l0 !, it_func_ptr
and
ldx [%g3], %l2 !, it_func_ptr
with v3 of you patches applied it uses +32 to get the offset of
it_func_ptr so that looks good.
> Make sure to start tracing in your tests, as I think the unaligned access only
> happens when accessing the struct tracepoint fields below the "int state" field.
>
Will do.
Regards
Richard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists