linux-mips
[Top] [All Lists]

Re: Disable EARLY_PRINTK on IP22 to make the system boot

To: Martin Michlmayr <tbm@cyrius.com>
Subject: Re: Disable EARLY_PRINTK on IP22 to make the system boot
From: Dmitri Vorobiev <dmitri.vorobiev@gmail.com>
Date: Thu, 19 Nov 2009 22:05:06 +0200
Cc: linux-mips@linux-mips.org
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=ZXQBx5Qb8s3aNIGvw2jYDmjA+zMTvYS0/C8Dg6nu5dQ=; b=iwX3d0UPCzj25uhUtSyanNkXOlLrR5wG0ul0hlMBwcwURwV6uswIGnm3/23gjqm0it 3q4yGZ/Pw9YnMxxEry7dAeBtpf5Zmhjr35AKQs0S99+Wzy/oA9ny8ETUvQGP4d2NPyiC 9rd2pY600hWXzTRhyRmfEv+FM2n9JpCWSrJmA=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=BrTBah4oRJvLBD9zQQAPhCPx8sf82vbdW9xWPOpJgoSUrR+6UuZ3cEbXSF1bTfsgj/ 2oeUdWcHsyTFbvAZCrkcMmTT78p7zKU0+PBJ8HHC0/JMOh7bqs2E3UUUfEGSE2h8ZsQg JwciRo/HPPKg2LlGr385AUO/mPVzDAprmwAEA=
In-reply-to: <20091119170051.GX31954@deprecation.cyrius.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20091119164009.GA15038@deprecation.cyrius.com> <90edad820911190856m62275563yf610c4a7dcdd1f67@mail.gmail.com> <20091119170051.GX31954@deprecation.cyrius.com>
Sender: linux-mips-bounce@linux-mips.org
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.

>
> Since Thomas Bogendoerfer disagnosed the problem, he should be able to
> say more.

OK.

Dmitri

>
> --
> Martin Michlmayr
> http://www.cyrius.com/
>

<Prev in Thread] Current Thread [Next in Thread>