From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: PXA270 Random Hangs at Low Core Freq
Date: Wed, 10 Nov 2010 14:54:23 +0100 [thread overview]
Message-ID: <20101110135422.GA1553@ucw.cz> (raw)
In-Reply-To: <AANLkTi=Y-JYQ_eZ4EdNirPrm_xkiduSZP19BPWckP2iW@mail.gmail.com>
Hi!
> > The best I've been able to do is two alternate cases (stock high-freq u-boot + a current Linux with CPUfreq enabled so that it lowers the speed; and my custom u-boot that runs only at low speed + a current Linux with CPUfreq disabled so linux just uses what u-boot sets). Both of these hang as described.
> >
> > Meaningfully rolling back to the Gumstix's vendor-supplied Linux distro is more difficult. It's running a 3+ year old 2.6.21 kernel variant that lacks support for recent MTD FLASH parts and features like UBIFS. I used that version on an OMAP and recall its MMC support was rather sketchy and since writing to a uSD card is my test case I'm somewhat doubtful that the results from such testing would mean much.
> >
> > Lastly, I've run Charles Cazabon's memtester (c. 2006 v 4.0.6) over 99% of the free SDRAM for days at a time and have seen no problems at all. If it were an outright SDRAM init/timing/refresh issue I'd expect something that strenuous to report an error.
> >
> >> Suggest to check errata first. Maybe we need some special code sequence.
> >
> > I agree that it has the feel of a CPU errata. (What else would hang the core so badly that JTAG would disconnect?) So I've re-read the Rev E (April 3rd 2009) errata docs from Marvell from start to finish but nothing jumps out at me. The problem is not knowing where to focus. Having eliminated the CPU-freq code itself (which relies on CPU features with many errata) I'm left rather empty handed.
> >
> > My only idea is that some kernel code path (likely interacting with an integrated peripheral) is too slow at low core frequencies and is either violating the hardware spec outright or is hitting an errata.
> >
> > My testing to date (and that I'm on commercial hardware) makes me think that others should be seeing the same problem. It won't occur out-of-the-box because normally people want highest performance (high core CPU frequencies). With the default u-boot and without CPU-freq to lower it the hang doesn't happen.
> >
> > But perhaps someone has prioritized power savings as I'm trying to do and then they should see it.
> >
ZAurus Spitz (pxa270) has always had problems -- inside suspend memory
is corrupted fairly often, and MMC produces high number of bit errors
-- like one in 20MB.
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2010-11-10 13:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-18 17:38 PXA270 Random Hangs at Low Core Freq Michael Cashwell
2010-10-22 0:22 ` Marek Vasut
2010-10-22 8:41 ` Haojian Zhuang
2010-10-25 19:02 ` Michael Cashwell
2010-10-25 19:22 ` Eric Miao
2010-10-26 0:05 ` Haojian Zhuang
2010-10-26 17:06 ` Michael Cashwell
2011-02-03 12:04 ` Vasily Khoruzhick
2011-02-03 12:52 ` Michael Cashwell
2011-03-04 16:16 ` Vasily Khoruzhick
2011-03-04 18:42 ` Michael Cashwell
2011-03-04 18:51 ` Vasily Khoruzhick
2011-03-30 11:45 ` Michael Cashwell
2010-11-10 13:54 ` Pavel Machek [this message]
2010-10-25 19:46 ` Marek Vasut
2010-10-25 20:53 ` Michael Cashwell
2010-10-26 14:47 ` Marek Vasut
2010-12-03 20:20 ` Robert Jarzmik
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=20101110135422.GA1553@ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-arm-kernel@lists.infradead.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 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.