public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: grinberg@compulab•co.il (Igor Grinberg)
To: linux-arm-kernel@lists•infradead.org
Subject: OMAP baseline test results for v3.6-rc7
Date: Thu, 27 Sep 2012 15:52:29 +0200	[thread overview]
Message-ID: <50645A1D.5040108@compulab.co.il> (raw)
In-Reply-To: <alpine.DEB.2.00.1209241919130.25811@utopia.booyaka.com>

On 09/24/12 21:21, Paul Walmsley wrote:
> 
> Here are some basic OMAP boot and power management test results for 
> v3.6-rc6:
> 
>    http://www.pwsan.com/omap/testlogs/test_v3.6-rc6/20120918101040/
> 
> Some observations:
> 
> Boot tests:
> 
> * CM-T3517: L3 in-band error with IPSS during boot
>   - Cause unknown but see 
> http://marc.info/?l=linux-omap&m=134833869730129&w=2
>   - Longstanding issue; does not occur on the 3517EVM

I'll be able to put some human resources on investigating this
in a couple of weeks hopefully. Currently, it does not affect all
boards (using the same boot loader) and does not look that it interferes
with any functionality later in the boot or runtime.

> 
> * 3517EVM & CM-T3517: boot hangs               
>   - Probably due to the use of NFS root; there are likely some Kconfig,
>     board file, and PM issues with EMAC

Have you tried the nohlt boot parameter?
It looks like the wfi is killing those SoCs once you use EMAC.

> 
> PM tests:
> 
> * 37xx EVM: CORE not entering dynamic off-idle
>   - Cause unknown; dynamic retention-idle seems to work; system suspend to 
>     off works
> 
> * 3730 Beagle XM: does not serial wake from off-idle suspend when console
>   UART doesn't clock gate ("debug ignore_loglevel")
>   - Not shown in the current test logs; cause unknown
> 
> * 4430ES2 Panda: UART corruption during long transmit buffers
>   - Presumably due to either a missing hardware workaround or a bug in
>     the OMAP serial driver
> 
> Other:
> 
> * RCU stall messages appear if boards are booted into a minimal userspace
>   and left to sit for a few minutes
>   - Fixed by http://marc.info/?l=linux-arm-kernel&m=134835120600590&w=2
> 
> 
> Changes from v3.6-rc6 (test 20120918101040):
> (see http://www.pwsan.com/omap/testlogs/test_v3.6-rc6/20120918101040/ )
> 
> - Added comments about RCU stalls, appearing since at least v3.6-rc3
> 
> - Updated CM-T3517 "USB OTG" (really IPSS) comment
> 
> object size (delta in bytes from test_v3.6-rc6 (5698bd757d55b1bb87edd1a9744ab09c142abfc2)):
>   text 	  data 	   bss 	 total 	kernel
>   -328 	   +72 	     0 	  -256 	2430_testconfig
>    -16 	   +16 	     0 	     0 	5912osk_testconfig
>   -376 	   +72 	     0 	  -304 	am33xx_testconfig
>    +64 	   +32 	     0 	   +96 	n800_b_testconfig
>    +80 	   +64 	     0 	  +144 	n800_multi_omap2xxx
>    +80 	   +32 	     0 	  +112 	n800_testconfig
>    +72 	   +80 	     0 	  +152 	omap1510_defconfig
>    +40 	   +16 	     0 	   +56 	omap1_defconfig
>    +80 	   +64 	     0 	  +144 	omap2_4_testconfig
>   -376 	   +40 	     0 	  -336 	omap2plus_defconfig
>   -376 	   +72 	     0 	  -304 	omap2plus_defconfig_cpupm
>    +20 	   +72 	     0 	   +92 	omap2plus_no_pm
>    +20 	    +8 	     0 	   +28 	omap3_4_testconfig
>   +140 	   +72 	     0 	  +212 	omap3_testconfig
>    +20 	   +40 	     0 	   +60 	omap4_testconfig
>    -40 	   +72 	     0 	   +32 	rmk_omap3430_ldp_oldconfig
>   -200 	    +8 	     0 	  -192 	rmk_omap4430_sdp_oldconfig
> 
> 
> 
> - Paul
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

-- 
Regards,
Igor.

  reply	other threads:[~2012-09-27 13:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-24 19:21 OMAP baseline test results for v3.6-rc7 Paul Walmsley
2012-09-27 13:52 ` Igor Grinberg [this message]
2012-10-01 18:34   ` Paul Walmsley
2012-10-01 23:28   ` Paul Walmsley
2012-10-02  9:38     ` Igor Grinberg

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=50645A1D.5040108@compulab.co.il \
    --to=grinberg@compulab$(echo .)co.il \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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