public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: Aaro Koskinen <aaro.koskinen@nokia.com>,
	Tony Lindgren <tony@atomide.com>,
	linux-omap@vger.kernel.org
Subject: Re: Open issues after 2.6.38 merge window
Date: Mon, 17 Jan 2011 12:11:44 +0000	[thread overview]
Message-ID: <20110117121144.GA18600@flint.arm.linux.org.uk> (raw)
In-Reply-To: <701a8169276ef3a1eccbac0d31117a6b@mail.gmail.com>

On Mon, Jan 17, 2011 at 05:29:01PM +0530, Santosh Shilimkar wrote:
> > On Fri, 14 Jan 2011, Tony Lindgren wrote:
> > > Before I update out master branch, let's try to summarize the
> > > open issues after the merge window. Here's a list of issues
> > > in omap-fixes-for-linus that I'm aware of:
> > >
> > > - NFS root oopses while mounting root
> > >
> > > - omap4430 es1.0 hangs if L2X0 cache is enabled
> > >
> > > - omap4 panda powers down after boot (watchdog?)
> > >
> > > - omap3 ldp board powers down after boot?

This doesn't happen for me.

> > >
> > > Any other issues?
> >
> > Amstrad E3 fails during the boot. Bisection points to:
> >
> >  	commit 211baa7016894c02fc18693e21ca479cd08ac0c0
> >  	Author: Russell King <rmk+kernel@arm.linux.org.uk>
> >  	Date:   Tue Jan 11 16:23:04 2011 +0000
> >
> >  	    ARM: sched_clock: allow init_sched_clock() to be called
> > early
> >
> > The board does not have sched_clock(), although HAVE_SCHED_CLOCK is
> > defined for all OMAP.
> >
> I guess above is sorted out by the attached patch from Paul.

There's an issue missing from Tony's list:

- running an omap2plus_defconfig kernel on SMP is unsafe to the point
  of being data corrupting for filesystems, especially for ext2/ext3
  mounted read-write.

This is because when CPU_32v6K is disabled - which is required to build
a kernel to boot on ARMv6, it turns off the SMP safe bitops - the SMP
safe bitops only use instructions available to ARMv6K and above.  They
are reduced to local-irq-disabling, plain byte loads and stores.

So, running omap2plus_defconfig on SMP is risking filesystem corruption.

Patches for this are being worked on, but they won't be ready for -rc1.
I strongly suggest someone restores some kind of build or runtime error
(eg, by removing CPU_32v6K's dependence on !OMAP2 - thereby _intentionally_
breaking omap2plus_defconfig) before someone ends up with a corrupted
filesystem.  Or just make sure that everyone is aware that
omap2plus_defconfig can eat filesystems at the moment.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:

  reply	other threads:[~2011-01-17 12:12 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-14 19:47 Open issues after 2.6.38 merge window Tony Lindgren
2011-01-14 20:24 ` Tony Lindgren
2011-01-14 20:37 ` Jarkko Nikula
2011-01-14 20:54   ` Tony Lindgren
2011-01-14 22:22     ` Nishanth Menon
2011-01-14 20:57 ` David Anders
2011-01-14 23:38   ` Tony Lindgren
2011-01-14 23:59     ` Tony Lindgren
2011-01-14 23:54 ` Thomas Weber
2011-01-15  5:19 ` Santosh Shilimkar
2011-01-17 10:15   ` Santosh Shilimkar
2011-01-27 18:41     ` Tony Lindgren
2011-01-17 11:37 ` Aaro Koskinen
2011-01-17 11:59   ` Santosh Shilimkar
2011-01-17 12:11     ` Russell King [this message]
2011-01-17 12:19       ` Santosh Shilimkar
2011-01-17 12:24         ` Russell King
2011-01-17 18:29           ` Tony Lindgren
2011-01-17 12:22     ` Aaro Koskinen
2011-01-17 12:35       ` Santosh Shilimkar
2011-01-17 12:50         ` Russell King
2011-01-17 18:20           ` Tony Lindgren
2011-01-17 20:31       ` Paul Walmsley
2011-01-17 20:39         ` Russell King
2011-01-17 21:00           ` Paul Walmsley
2011-01-17 21:19             ` Russell King
2011-01-17 22:49               ` Paul Walmsley

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=20110117121144.GA18600@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=aaro.koskinen@nokia.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=santosh.shilimkar@ti.com \
    --cc=tony@atomide.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