From: Ralf Baechle <ralf@linux-mips.org>
To: Martin Michlmayr <tbm@cyrius.com>
Cc: linux-mips@linux-mips.org, jblache@debian.org
Subject: Re: IP22 doesn't shutdown properly
Date: Mon, 20 Feb 2006 21:55:31 +0000 [thread overview]
Message-ID: <20060220215531.GA27383@linux-mips.org> (raw)
In-Reply-To: <20060220181227.GA17439@deprecation.cyrius.com>
On Mon, Feb 20, 2006 at 06:12:27PM +0000, Martin Michlmayr wrote:
> Date: Mon, 20 Feb 2006 18:12:27 +0000
> From: Martin Michlmayr <tbm@cyrius.com>
> To: Ralf Baechle <ralf@linux-mips.org>
> Cc: linux-mips@linux-mips.org, jblache@debian.org
> Subject: Re: IP22 doesn't shutdown properly
> Content-Type: text/plain; charset=us-ascii
>
> * Ralf Baechle <ralf@linux-mips.org> [2006-02-19 16:52]:
> > > beginning, the light on the Indy is green but after about 20 seconds
> > > it turns red. Nothing happens on the console and the machine doesn't
> > > turn off. Seen on Indy and Indigo2.
> > > Anyone got a fix?
> > No. Do you know when this problems started?
>
> A long time ago, it seems. I can trace it back to 2.6.9;
> unfortunately I don't get any older kernel to run/compile, possibily
> because my toolchain isn't old enough (I even installed the SDE that's
> based on 3.3).
>
> Here's what I got:
>
> 2.6.15 - broken
> 2.6.14 - broken
> 2.6.13 - broken
> 2.6.10 - broken
> 2.6.9 - broken
> 2.6.8 - hangs after download (SDE)
> 2.6.6 - hangs after download (SDE)
> 2.6.5 - hangs after download (SDE)
> 2.6.4 - hangs after download (SDE)
> 2.6.3 - fails to load with: Text start 0x8000000, size 0x25e998 doesn't
> fit in a FreeMemory area.
Somehow this all sounds suspicious. I ran at least a few of those kernels
on my own Indy.
> 2.6.1 - doesn't compile
Okay, I had to try this one. Clear case of bitrot. Don't use fancy
new compilers with that kernel, it doesn't like them.
Ralf
next prev parent reply other threads:[~2006-02-21 13:00 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 22:58 IP22 doesn't shutdown properly Martin Michlmayr
2006-02-18 1:19 ` Kumba
2006-02-18 1:27 ` Martin Michlmayr
2006-02-18 10:36 ` Julien BLACHE
2006-02-19 16:52 ` Ralf Baechle
2006-02-20 18:12 ` Martin Michlmayr
2006-02-20 21:55 ` Ralf Baechle [this message]
2006-02-21 13:59 ` Thiemo Seufer
2006-02-21 14:23 ` Stephen P. Becker
2006-02-21 14:31 ` Thiemo Seufer
2006-02-23 21:14 ` Martin Michlmayr
2006-02-23 22:13 ` Martin Michlmayr
2006-02-23 22:43 ` Russell King
2006-02-24 0:39 ` Martin Michlmayr
2006-02-24 1:30 ` Kumba
2006-02-24 8:31 ` Russell King
2006-02-27 10:54 ` Martin Michlmayr
2006-02-24 19:05 ` Christoph Hellwig
2006-02-27 10:51 ` Martin Michlmayr
2006-02-27 10:52 ` Martin Michlmayr
2006-02-27 11:22 ` Geert Uytterhoeven
2006-02-27 11:25 ` Martin Michlmayr
2006-02-27 12:53 ` Ralf Baechle
2006-02-27 18:30 ` Martin Michlmayr
2006-03-25 17:34 ` Russell King
2006-04-07 16:21 ` Martin Michlmayr
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=20060220215531.GA27383@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=jblache@debian.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox