All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sachin Sant <sachinp@in.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
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: Tue, 11 Aug 2009 10:55:00 +0530	[thread overview]
Message-ID: <4A8100AC.30404@in.ibm.com> (raw)
In-Reply-To: <1249597385.24311.10.camel@pasglop>

Benjamin Herrenschmidt wrote:
> 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
>   
Was away from office for few days.

Thanks for the help. The machine under test is running
F11. I will try out the latest yaboot.

Thanks
-Sachin



-- 

---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------

  parent reply	other threads:[~2009-08-11  5:25 UTC|newest]

Thread overview: 35+ 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-04 14:15     ` Michael Ellerman
2009-08-06 22:23     ` Benjamin Herrenschmidt
2009-08-06 22:23       ` Benjamin Herrenschmidt
2009-08-07  2:54       ` Josh Boyer
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 [this message]
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:17     ` Sachin Sant
2009-08-05  9:52     ` Benjamin Herrenschmidt
2009-08-05  9:52       ` Benjamin Herrenschmidt
2009-08-06 13:33       ` Sachin Sant
2009-08-06 13:33         ` Sachin Sant
2009-08-06 13:40         ` Michael Ellerman
2009-08-06 13:40           ` Michael Ellerman
2009-08-06 21:51         ` Benjamin Herrenschmidt
2009-08-07  0:08           ` Draft Mirrored Linux Mini How-to Harold Pritchett
2009-08-07  2:09             ` Goswin von Brederlow
2009-08-07  3:53             ` Tapani Tarvainen
2009-08-08  1:11               ` Goswin von Brederlow
2009-08-08  1:41                 ` NeilBrown
2009-08-08  7:59                   ` Goswin von Brederlow
2009-08-08 15:24                     ` John Robinson
2009-08-08 14:09                   ` Bill Davidsen
2009-08-07  8:10             ` Fredrik Pettersson
2009-08-07  9:51             ` Keld Jørn Simonsen
     [not found]               ` <4A7C5BD2.80508@uga.edu>
     [not found]                 ` <20090807173423.GA32127@rap.rap.dk>
2009-08-08 11:36                   ` Keld Jørn Simonsen
2009-08-07 15:27             ` Draft Mirrored Linux Mini How-to - sfdisk suggestion Maurice Hilarius
2009-08-08  1:13               ` Goswin von Brederlow
2009-08-09 18:55     ` 2.6.31-rc5-git2 crash on a idle system Louwrentius

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=4A8100AC.30404@in.ibm.com \
    --to=sachinp@in.ibm.com \
    --cc=benh@kernel.crashing.org \
    --cc=davem@davemloft.net \
    --cc=linuxppc-dev@ozlabs.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.