From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: michael@ellerman.id.au
Cc: netdev <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
linuxppc-dev@ozlabs.org
Subject: Re: 2.6.31-rc5-git2 crash [net/core/flow.c:flow_cache_new_hashrnd]
Date: Fri, 07 Aug 2009 08:23:05 +1000 [thread overview]
Message-ID: <1249597385.24311.10.camel@pasglop> (raw)
In-Reply-To: <1249395350.8016.5.camel@concordia>
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
etc...
Cheers,
Ben.
next prev parent reply other threads:[~2009-08-06 22:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 12:27 2.6.31-rc5-git2 crash on a idle system Sachin Sant
2009-08-04 13:43 ` 2.6.31-rc5-git2 crash [net/core/flow.c:flow_cache_new_hashrnd] Sachin Sant
2009-08-04 14:15 ` Michael Ellerman
2009-08-06 22:23 ` Benjamin Herrenschmidt [this message]
2009-08-07 2:54 ` Josh Boyer
2009-08-07 3:13 ` Benjamin Herrenschmidt
2009-08-07 3:49 ` Tony Breeds
2009-08-11 5:25 ` Sachin Sant
2009-08-04 21:27 ` 2.6.31-rc5-git2 crash on a idle system Benjamin Herrenschmidt
2009-08-05 9:17 ` Sachin Sant
2009-08-05 9:52 ` Benjamin Herrenschmidt
2009-08-06 13:33 ` Sachin Sant
2009-08-06 13:40 ` Michael Ellerman
2009-08-06 21:51 ` Benjamin Herrenschmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1249597385.24311.10.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).