From: Ricardo Mendoza <ricmm@gentoo.org>
To: Clem Taylor <clem.taylor@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: early hang in 2.6.24 on au1550 (MIPSLE)
Date: Tue, 10 Jun 2008 20:27:18 -0430 [thread overview]
Message-ID: <484F22EE.5090601@gentoo.org> (raw)
In-Reply-To: <ecb4efd10806101430o426a2b51r3895871e31ceec89@mail.gmail.com>
Clem Taylor wrote:
> A few months ago I switched from 2.6.16.16 to 2.6.24 on an AU1550
> (MIPSLE) system. I started rolling this out to more systems, getting
> ready for a new software release and discovered that on fresh powerup,
> the 2.6.24 kernel sometimes (1 in 10-25 power cycles) fails to start.
> The bootloader (uboot) decompresses the kernel from a jffs2 filesystem
> and then jumps to it, but I don't get any serial messages from the
> kernel.
>
> If I switch back to the 2.6.16.16 kernel, everything is happy. The
> annoying thing is that I have been unable to catch the problem with
> the JTAG debugger connected, so I'm not sure where it is hanging.
>
> I've been looking at diffs in the arch/mips tree and nothing has
> jumped out at me. I don't think this is a hardware problem, this
> hardware platform has been fairly stable and it works just fine with
> the older kernel. I was wondering if anyone has any suggestions where
> I might look? Also, is anyone using 2.6.24 with a Au1550?
Nothing? What about time layer switch to make use of cevt and csrc
devices for example. Gotta keep in mind that 2.6.16 is archaic; you
should write an early printk implementation for au1550 and see where it
dies. With another board once I experienced something similar and it
happened to be timer interrupts getting skipped at times, so, you might
be dying in calibration if your problem is similar.
Ricardo
prev parent reply other threads:[~2008-06-11 0:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 21:30 early hang in 2.6.24 on au1550 (MIPSLE) Clem Taylor
2008-06-11 0:57 ` Ricardo Mendoza [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=484F22EE.5090601@gentoo.org \
--to=ricmm@gentoo.org \
--cc=clem.taylor@gmail.com \
--cc=linux-mips@linux-mips.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