From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Stefan Jeglinski <jeglin@4pi.com>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: old-world boot freeze; 2.4.19-rc2
Date: Sat, 20 Jul 2002 20:05:34 +0200 [thread overview]
Message-ID: <20020720180534.29622@192.168.4.1> (raw)
In-Reply-To: <p05100300b95ea06f444c@[192.168.0.22]>
>Just rsynced 2.4.19-rc2 from source.mvista.org (although official
>kernel is at rc3?). Built fine, but when I try to boot it on a 9500
>with a Powerlogix G3 upgrade, the last two things I see (early in the
>boot) are:
>
>setup_arch: enter
>setup_arch: bootmem
>
>And then it just locks up.
>
>Any ideas? Last kernel I've been running on this is 2.4.18, with no problems.
I works fine on a 8500 SMP here (with no G3 upgrade though). Can you
try routing printk to the btext engine ?
(use my tree and add printkbext to the command line)
Tell me what are the last messages.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-07-20 18:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-20 5:10 old-world boot freeze; 2.4.19-rc2 Stefan Jeglinski
2002-07-20 18:05 ` Benjamin Herrenschmidt [this message]
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=20020720180534.29622@192.168.4.1 \
--to=benh@kernel.crashing.org \
--cc=jeglin@4pi.com \
--cc=linuxppc-dev@lists.linuxppc.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).