OMAP baseline test results for v3.8-rc3

Hi,

On Mon, Jan 14, 2013 at 10:46:54PM +0200, Aaro Koskinen wrote:

On Mon, Jan 14, 2013 at 09:14:59PM +0200, Felipe Balbi wrote:

quoted

On Mon, Jan 14, 2013 at 08:40:18PM +0200, Aaro Koskinen wrote:

quoted

On Mon, Jan 14, 2013 at 05:59:12PM +0000, Paul Walmsley wrote:

quoted

Here are some basic OMAP test results for Linux v3.8-rc3.
Logs and other details at:

    http://www.pwsan.com/omap/testlogs/test_v3.8-rc3/20130109222058/


Test summary
------------

Boot to userspace:
    Pass ( 9/11): 2420n800, 2430sdp, 3517evm, 3530es3beagle,
  	   	  3730beaglexm, 37xxevm, 4430es2panda, 5912osk,
		  4460pandaes
    FAIL ( 2/11): am335xbone, cmt3517 

N900 boot is unstable again, I2C issues are back.

damn!

quoted

Boot succeeds and fails randomly. Let's see if this can be bisected.
The same kernel works on N950.

fair enough, it might be something related to some errata fix which
might have been missed. Can you apply this small patch just so I know if
there is something pending in CNT reg ?

[    0.207946] twl 1-0048: PIH (irq 23) chaining IRQs 338..346
[    0.208129] twl 1-0048: power (irq 343) chaining IRQs 346..353
[    0.209350] twl4030_gpio twl4030_gpio: gpio (irq 338) chaining IRQs 354..371
[    1.218749] omap_i2c omap_i2c.1: timeout waiting for bus ready
[    1.218811] omap_i2c omap_i2c.1: SA 0049 CON 9602 CNT 0004

here's the issue, there is unloaded data in the FIFO. Can you enable
full I2C debugging logs ?

quoted

you might also want to try merging my latest i2c patches, which missed
the merge window, as they might help with this issue too.

The following changes since commit 9931faca02c604c22335f5a935a501bb2ace6e20:

  Linux 3.8-rc3 (2013-01-09 18:59:55 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git i2c-deferred-STP

I could not reproduce the issue with these. Tested around 20 boots.
There's a noticeable delay (over 4 secs!) around where I2C is initialized
and used for the first time, but no errors and the boot completes:

[    0.187530] SCSI subsystem initialized
[    0.188110] usbcore: registered new interface driver usbfs
[    0.188415] usbcore: registered new interface driver hub
[    0.188781] usbcore: registered new device driver usb
[    0.189453] musb-omap2430 musb-omap2430: invalid resource
[    4.296905] twl 1-0048: PIH (irq 23) chaining IRQs 338..346
[    4.297088] twl 1-0048: power (irq 343) chaining IRQs 346..353
[    4.329010] twl4030_gpio twl4030_gpio: gpio (irq 338) chaining IRQs 354..371
[    4.470123] VUSB1V5: 1500 mV normal standby
[    4.470916] VUSB1V8: 1800 mV normal standby

cool, at least it works, but looks like there is something still weird
going on. Can you enable full logs so I see what's happening ?

cheers

-- 
balbi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130114/3adc8864/attachment.sig>