linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
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 00:06:37 -0400	[thread overview]
Message-ID: <98889dd30605152106m9090ba3ga1a4c7706aace3ef@mail.gmail.com> (raw)
In-Reply-To: <1147658309.21291.73.camel@localhost.localdomain>

Ok, here is the new log:

time_init: processor frequency =3D 700.000000 MHz
Console: colour dummy device 80x25
Dentry cache hash table entries: 131072 (order: 7,524288 bytes)
Inode-cache hash table entries: 65536 (order: 6,262144 bytes)
Memory: 643456k/655360k available (2908k kernel code, 11564k reserved,
272k data, 131k bss, 156k init)
Mount-cache hash table entries: 512
device-tree: Duplicate name in /cpus/PowerPC,G4@0, renamed to "l2-cache#1"
NET: Registered protocol family 16

KeyWest i2c @0xf8001003 irq 42 /uni-n@f8000000/i2c@f8001000
 channel 0 bus <multibus>
 channel 1 bus <multibus>
KeyWest i2c @0x80018000 irq 26 /pci@f2000000/mac-io@17/i2c@18000
 channel 0 bus <multibus>
PMU i2c /pci@f2000000/mac-io@17/via-pmu@16000/pmu-i2c
 channel 1 bus <multibus>
 channel 2 bus <multibus>
PCI: Probing PCI hardware

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=3D99584)

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.


On 5/14/06, Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
>
> Hrm... that's pretty much when console_init() gets called, which means
> no message until the fbdev kicks in, thus we just "miss" the messages
> from there to the crash.... Can you edit arch/powerpc/kernel/udbg.c,
> there is a function called disable_early_printk() which contains a #if
> 1, turn that into #if 0 and tell me if you get a more useful log after
> the time_init thing. Thanks !
>
>
>

  reply	other threads:[~2006-05-16  4:06 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 [this message]
2006-05-16  4:43         ` Benjamin Herrenschmidt
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=98889dd30605152106m9090ba3ga1a4c7706aace3ef@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).