public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	"Andreas Müller" <schnitzeltony@googlemail.com>,
	grinberg@compulab.co.il, "Sourav Poddar" <sourav.poddar@ti.com>
Subject: Re: OMAP baseline test results for v3.6-rc5
Date: Mon, 10 Sep 2012 08:51:20 +0300	[thread overview]
Message-ID: <20120910055118.GA19264@arwen.pp.htv.fi> (raw)
In-Reply-To: <alpine.DEB.2.00.1209091814380.28047@utopia.booyaka.com>

[-- Attachment #1: Type: text/plain, Size: 684 bytes --]

Hi,

On Sun, Sep 09, 2012 at 06:15:04PM +0000, Paul Walmsley wrote:
> > * 4430ES2 Panda: UART corruption during long transmit buffers
> >   - Presumably due to either a missing hardware workaround or a bug in
> >     the OMAP serial driver
> > 
> * 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

How do you trigger these two ? Can you share whatever script you wrote
for this to fail ? I'm assuming the bugs are only triggered on those two
particular platforms, so it could just be missing workaround on both
cases (?)

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-09-10  5:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-09 17:56 OMAP baseline test results for v3.6-rc5 Paul Walmsley
2012-09-09 18:15 ` Paul Walmsley
2012-09-10  5:51   ` Felipe Balbi [this message]
2012-09-10 16:46     ` 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=20120910055118.GA19264@arwen.pp.htv.fi \
    --to=balbi@ti.com \
    --cc=grinberg@compulab.co.il \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=schnitzeltony@googlemail.com \
    --cc=sourav.poddar@ti.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