From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Nathan Pilatzke <nathanpilatzke@gmail.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: ppc32 kernel boot problem (pmu related?)
Date: Tue, 16 May 2006 14:43:13 +1000 [thread overview]
Message-ID: <1147754594.13588.17.camel@localhost.localdomain> (raw)
In-Reply-To: <98889dd30605152106m9090ba3ga1a4c7706aace3ef@mail.gmail.com>
> And that's where is locks hard. Just as an alternative I tried
> compiling without i2c support, but the kernel locks hard at the exact
> same point. Compiling without the pmu code is the only way I can get
> the kernel to boot. There are some kernel messages missing from a
> kernel compiled with pmu versus a kernel without pmu, namely:
>
> On node 0 total pages: 163840
> DMA zone: 163840 pages, LIFO batch: 31
>
> and
>
> Calibrating delay loop... 49.79 BogoMIPS (lpj=99584)
>
> but they do not seem to be anything serious. Where to go from here?
> Thanks for the debugging suggestions so far, keep them coming please.
Can you try editing arch/powerpc/platforms/powermac/low_i2c.c, in
function pmac_i2c_init(), comment out the call to pmac_i2c_devscan() and
tell me if that makes a difference.
Thanks,
Ben.
next prev parent reply other threads:[~2006-05-16 4:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-11 19:07 ppc32 kernel boot problem (pmu related?) Nathan Pilatzke
2006-05-12 3:12 ` Benjamin Herrenschmidt
2006-05-12 12:40 ` Nathan Pilatzke
2006-05-15 1:58 ` Benjamin Herrenschmidt
2006-05-16 4:06 ` Nathan Pilatzke
2006-05-16 4:43 ` Benjamin Herrenschmidt [this message]
2006-05-16 15:04 ` Nathan Pilatzke
2006-05-16 22:07 ` Benjamin Herrenschmidt
2006-05-16 4:44 ` 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=1147754594.13588.17.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=nathanpilatzke@gmail.com \
/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).