Re: Bug#609371: linux-image-2.6.37-trunk-sparc64: module scsi_mod:Unknown relocation: 36

From: Richard Mortimer
Date: Fri Jan 21 2011 - 13:06:14 EST




On 21/01/2011 00:04, Mathieu Desnoyers wrote:
* David Miller (davem@xxxxxxxxxxxxx) wrote:
From: Mathieu Desnoyers<mathieu.desnoyers@xxxxxxxxxxxx>
Date: Wed, 19 Jan 2011 17:33:39 -0500

So I guess we go for the following. Is it verbose enough ?

It's got all of the details that seem to matter, thanks.

I'm letting people following this thread and the bug report know that I posted
the patch we discussed about here in the following thread:

https://lkml.org/lkml/2011/1/19/509

Feedback is welcome,

Hi Mathieu,

Thanks for this.

The good news is that I have a 2.6.37 kernel + your patches booting and it has been running for about an hour on sparc64/Sun Fire V120. I did a bit of poking around in /debug and turned on/off a bit of tracing and nothing broke.

I did have a few problems applying your patch series. Your diffs have semicolons at the end of a couple of the macros that don't appear in the mainline 2.6.37. One was circa line 174 of include/linux/tracepoint.h but I don't have the other to hand at the moment and I don't have much time before I need to go out.

I'm also getting a lot of Kernel unaligned access errors from the kernel. I don't know if they are related to this or not and this is the first time that I personally have got 2.6.37 to boot on sparc64. The messages that I am getting seem to be repeats of

[ 4376.807811] Kernel unaligned access at TPC[456e94] try_to_wake_up+0x58/0xec
[ 4376.807908] Kernel unaligned access at TPC[75541c] schedule+0x454/0x660
[ 4376.808044] Kernel unaligned access at TPC[75541c] schedule+0x454/0x660
[ 4376.808871] Kernel unaligned access at TPC[456e94] try_to_wake_up+0x58/0xec
[ 4376.808965] Kernel unaligned access at TPC[75541c] schedule+0x454/0x660
[ 4381.813354] log_unaligned: 337 callbacks suppressed

I have to go out now but will be around later/over the weekend.

Regards

Richard

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/