[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090807025454.GL3095@hansolo.jdub.homelinux.org>
Date: Thu, 6 Aug 2009 22:54:54 -0400
From: Josh Boyer <jwboyer@...il.com>
To: Benjamin Herrenschmidt <benh@...nel.crashing.org>
Cc: michael@...erman.id.au, netdev <netdev@...r.kernel.org>,
David Miller <davem@...emloft.net>, linuxppc-dev@...abs.org
Subject: Re: 2.6.31-rc5-git2 crash [net/core/flow.c:flow_cache_new_hashrnd]
On Fri, Aug 07, 2009 at 08:23:05AM +1000, Benjamin Herrenschmidt wrote:
>On Wed, 2009-08-05 at 00:15 +1000, Michael Ellerman wrote:
>
>> > c000000000600000 00001010 .long 0x1010
>> > 0:mon>
>> > c000000000600004 00000008 .long 0x8
>> > c000000000600008 00001013 .long 0x1013
>> > c00000000060000c 0000000f .long 0xf
>> > c000000000600010 7961626f rldimi. r1,r11,44,41
>> > c000000000600014 6f740000 xoris r20,r27,0
>> > c000000000600018 00101600 .long 0x101600
>> > c00000000060001c 00000c00 .long 0xc00
>> > c000000000600020 00000400 .long 0x400
>> > c000000000600024 00101100 .long 0x101100
>> > c000000000600028 000008e9 .long 0x8e9
>
>BTW. Corruption looks like bi_recs... ie, broken yaboot. This was fixed
>recently, yaboot would eventually crap over the kernel for certain sizes
>of the kernel image.
>
>0x1010 = BI_FIRST
>0x1013 = BI_BOOTLOADER_ID followed by 0x7961626f6f74 which is
>"yaboot" :-)
>0x1016 = BI_MACHTYPE
I know we fixed it in Fedora for F11/F12. Did it get fixed upstream?
josh
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists