[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20141015.143624.941838991598108211.davem@davemloft.net>
Date: Wed, 15 Oct 2014 14:36:24 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: mroos@...ux.ee
Cc: iamjoonsoo.kim@....com, linux-kernel@...r.kernel.org, cl@...ux.com,
penberg@...nel.org, rientjes@...gle.com, akpm@...ux-foundation.org,
linux-mm@...ck.org, sparclinux@...r.kernel.org
Subject: Re: unaligned accesses in SLAB etc.
From: Meelis Roos <mroos@...ux.ee>
Date: Wed, 15 Oct 2014 11:04:49 +0300 (EEST)
>> > My only other current sparc64 problems that I am seeing - V210/V440 die
>> > during bootup if compiled with gcc 4.9 and V480 dies with FATAL
>> > exceptions during bootups since previous kernel release. Maybe also
>> > exit_mmap warning - I do not know if they have been fixed, I see them
>> > rarely.
>>
>> The gcc-4.9 case is interesting, are you saying that a gcc-4.9 compiled
>> kernel works fine on other systems?
>
> Yes, all USII based systems work fine with Debian gcc-4.9, as does
> T2000. Of USIII* systems, V210 and V440 exhibit the boot hang with
> gcc-4.9 and V480 crashes wit FATAL exception during boot that is
> probably earlier than the gcc boot hang so I do not know about V480 and
> gcc-4.9. V240 not tested because of fan failures, V245 is in the queue
> for setup but not tested so far.
Ok, on the V210/V440 can you boot with "-p" on the kernel boot command
line and post the log? Let's start by seeing how far it gets, maybe
we can figure out roughly where it dies.
A boot hang should be relatively easy to diagnose and pinpoint.
Thanks.
--
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