From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Dmitri Vorobiev <dmitri.vorobiev@gmail.com>
Cc: Martin Michlmayr <tbm@cyrius.com>, linux-mips@linux-mips.org
Subject: Re: Disable EARLY_PRINTK on IP22 to make the system boot
Date: Thu, 19 Nov 2009 21:55:03 +0100 [thread overview]
Message-ID: <20091119205503.GA17383@alpha.franken.de> (raw)
In-Reply-To: <90edad820911191205h77f298b4u788039abff2db1d0@mail.gmail.com>
On Thu, Nov 19, 2009 at 10:05:06PM +0200, Dmitri Vorobiev wrote:
> On Thu, Nov 19, 2009 at 7:00 PM, Martin Michlmayr <tbm@cyrius.com> wrote:
> > * Dmitri Vorobiev <dmitri.vorobiev@gmail.com> [2009-11-19 18:56]:
> >> > Some Debian users have reported that the kernel hangs early
> >> > during boot on some IP22 systems. Thomas Bogendoerfer found
> >> > that this is due to a "bad interaction between CONFIG_EARLY_PRINTK
> >> > and overwritten prom memory during early boot". Since there's
> >> > no fix yet, disable CONFIG_EARLY_PRINTK for now.
> >>
> >> Never experienced anything like that, although I'm quite extensively
> >> using IP22 with recent kernels. Any details on the hangs?
> >
> > It doesn't happen on all machines. It has been reported e.g. with an
> > Indigo2. See http://bugs.debian.org/507557
>
> Interesting, thanks. Good to know that, since one of my machines is Indigo2.
I guess is depending on RPOM version and installed memory. I haven't
figured out exactly which parts get overwritten, but since we completely
ignore ARCS reservered memory and still use ARCS prom calls, it's not
a real safe game we are doing.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessary a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2009-11-19 20:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 16:40 Disable EARLY_PRINTK on IP22 to make the system boot Martin Michlmayr
2009-11-19 16:56 ` Dmitri Vorobiev
2009-11-19 17:00 ` Martin Michlmayr
2009-11-19 20:05 ` Dmitri Vorobiev
2009-11-19 20:55 ` Thomas Bogendoerfer [this message]
2009-11-24 1:39 ` Ralf Baechle
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=20091119205503.GA17383@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=dmitri.vorobiev@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=tbm@cyrius.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.