linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: crash in init_ipic_sysfs on efika
Date: Thu, 20 Mar 2008 07:45:42 +0100	[thread overview]
Message-ID: <20080320064542.GA11434@aepfle.de> (raw)
In-Reply-To: <18400.41990.995316.729968@cargo.ozlabs.ibm.com>

On Wed, Mar 19, Paul Mackerras wrote:

> Olaf Hering writes:
> 
> > I cant reproduce this bug on my board, but:
> > 
> > The global primary_ipic in arch/powerpc/sysdev/ipic.c can remain NULL if
> > ipic_init() fails. init_ipic_sysfs() will crash in that case.
> > 
> > Something like this may fix it:
> 
> Is this needed for 2.6.25?  Is the system at all usable if ipic_init
> fails?

CONFIG_PPC_MPC51* needs to be disabled for pmac/chrp/bplan .configs.

A full featured ppc32_defconfig will probably catch such errors.

  reply	other threads:[~2008-03-20  6:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-17 19:53 crash in init_ipic_sysfs on efika Olaf Hering
2008-03-19  5:26 ` Paul Mackerras
2008-03-20  6:45   ` Olaf Hering [this message]
2008-03-19 15:27 ` Olaf Hering
2008-03-20 11:32   ` Matt Sealey
2008-03-21 11:18     ` Benjamin Herrenschmidt
2008-03-20 15:15 ` Kumar Gala
2008-03-21  1:38   ` Paul Mackerras
2008-03-21  5:14 ` Grant Likely
2008-03-21  9:03   ` Paul Mackerras
2008-03-21  9:18     ` Kumar Gala
2008-03-24  8:02       ` Paul Mackerras
2008-03-24 22:59         ` Kumar Gala
2008-03-21 13:14     ` Matt Sealey
2008-03-21 18:51       ` Grant Likely
2008-03-22 15:25         ` Sven Luther
2008-03-23  9:00           ` David Woodhouse
2008-03-23 10:12             ` Sven Luther
2008-03-23 10:13               ` David Woodhouse
2008-03-23 10:24                 ` Sven Luther
2008-03-24 23:01         ` Matt Sealey

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=20080320064542.GA11434@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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).