Re: OMAP baseline test results for v3.6-rc4

2012-09-23 Thread Shilimkar, Santosh
On Sun, Sep 23, 2012 at 12:01 AM, Paul Walmsley p...@pwsan.com wrote: cc Santosh Hi Igor, I regret the delay in responding, On Fri, 7 Sep 2012, Igor Grinberg wrote: On 09/05/12 18:44, Paul Walmsley wrote: * CM-T3517: L3 in-band error with USB OTG during boot - Cause unknown;

Re: OMAP baseline test results for v3.6-rc4

2012-09-22 Thread Paul Walmsley
cc Santosh Hi Igor, I regret the delay in responding, On Fri, 7 Sep 2012, Igor Grinberg wrote: On 09/05/12 18:44, Paul Walmsley wrote: * CM-T3517: L3 in-band error with USB OTG during boot - Cause unknown; longstanding issue; does not occur on the 3517EVM We see this problem on

Re: OMAP baseline test results for v3.6-rc4

2012-09-07 Thread Igor Grinberg
On 09/05/12 18:44, Paul Walmsley wrote: Here are some basic boot and power management test results for v3.6-rc4: http://www.pwsan.com/omap/testlogs/test_v3.6-rc4/20120904122415/ Some observations: [...] * CM-T3517: L3 in-band error with USB OTG during boot - Cause unknown;

Re: OMAP baseline test results for v3.6-rc4

2012-09-07 Thread Andreas Müller
On Wed, Sep 5, 2012 at 5:44 PM, Paul Walmsley p...@pwsan.com wrote: Here are some basic boot and power management test results for v3.6-rc4: http://www.pwsan.com/omap/testlogs/test_v3.6-rc4/20120904122415/ Some observations: * N800: panics during kernel init - This is caused by an

Re: OMAP baseline test results for v3.6-rc4

2012-09-07 Thread Paul Walmsley
Hi, On Sat, 8 Sep 2012, Andreas Müller wrote: On Wed, Sep 5, 2012 at 5:44 PM, Paul Walmsley p...@pwsan.com wrote: Here are some basic boot and power management test results for v3.6-rc4: http://www.pwsan.com/omap/testlogs/test_v3.6-rc4/20120904122415/ Some observations: *

OMAP baseline test results for v3.6-rc4

2012-09-05 Thread Paul Walmsley
Here are some basic boot and power management test results for v3.6-rc4: http://www.pwsan.com/omap/testlogs/test_v3.6-rc4/20120904122415/ Some observations: * N800: panics during kernel init - This is caused by an MMC driver bug; fixed by [PATCH] MMC: OMAP MSDI: fix broken PIO mode,