From: "Nathan Pilatzke" <nathanpilatzke@gmail.com>
To: "Benjamin Herrenschmidt" <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: ppc32 kernel boot problem (pmu related?)
Date: Tue, 16 May 2006 11:04:14 -0400 [thread overview]
Message-ID: <98889dd30605160804i78fc6a31w5147aba1dc5562b@mail.gmail.com> (raw)
In-Reply-To: <1147754594.13588.17.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 986 bytes --]
On 5/16/06, Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
>
> 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.
>
>
Commenting out the call to pmac_i2c_devscan() in function
pmac_i2c_init() allowed the kernel to boot. I am typing this email
booted under it. The kernel messages were printed a bit strangely
though. There was no scrolling or clearing of the screen. The kernel
messages would start at the top and overwrite old messages, with the
cursor jumping back to the top of the screen every so often. The
/proc/device-tree is attached for the booting 2.6.17-rc3 kernel with
pmu enabled, as is the new dmesg output. If you need the
/proc/device-tree from a 2.6.15 working kernel with pmu enabled
instead, let me know.
Is this kernel fairly safe/stable to use? What can be done next?
Nathan
[-- Attachment #2: device-tree_2.6.17-rc3-pmuworking.tar.bz2 --]
[-- Type: application/x-bzip2, Size: 15848 bytes --]
[-- Attachment #3: dmesg_2.6.17-rc3-pmuworking.bz2 --]
[-- Type: application/x-bzip2, Size: 3942 bytes --]
next prev parent reply other threads:[~2006-05-16 15:04 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
2006-05-16 15:04 ` Nathan Pilatzke [this message]
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=98889dd30605160804i78fc6a31w5147aba1dc5562b@mail.gmail.com \
--to=nathanpilatzke@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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).