From: Daniel Mack <zonque@gmail.com>
To: Nishanth Menon <nm@ti.com>, Vaibhav Bedia <vaibhav.bedia@gmail.com>
Cc: Gururaja Hebbar <gururaja.hebbar@ti.com>,
joelf@ti.com, Matt Porter <matt@ohporter.com>,
balajitk@ti.com, s.neumann@raumfeld.com,
Sekhar Nori <nsekhar@ti.com>, Russ Dill <Russ.Dill@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Linux ARM Kernel List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v4] ARM: omap: edma: add suspend suspend/resume hooks
Date: Sun, 17 Nov 2013 23:09:41 +0100 [thread overview]
Message-ID: <52893EA5.7080809@gmail.com> (raw)
In-Reply-To: <52863232.30207@ti.com>
Hi Nishanth,
On 11/15/2013 03:39 PM, Nishanth Menon wrote:
> To trigger the fail, I created a custom Test case on TI vendor kernel
> based on v3.12 tag:
> On beagleBone-Black
> test scenario (BBB):
>
> Boot from SD card
> ensure firmware is loaded (rev 0x182)
> run LTP fsstress [1] in background on EMMC
> mkdir -p /tmp/testing
> mke2fs /dev/mmcblk1p1
> mount /dev/mmcblk1p1 /tmp/testing
> fsstress -d /tmp/testing p 4 -n 1000 -l0 -v >/dev/null &
> run ping in the background (to add yet another interface)
> run memtester[2] (70% of free memory)
> memtester 343M >/dev/null &
> sleep 10 (to allow memtester to start up properly)
> start=`date`;i=0; while [ 1 ]; do rtcwake -d /dev/rtc0 -m mem -s
> 2; i=$((i + 1)); echo "$i: start =$start, now="`date`; sleep 2; done
>
> Eventual hang log (using the regular suspend-resume): [3] - took close
> to two days of testing to trigger this.
>
> Moving to a suspend_late and resume_early such as in [4], it passed
> the test for over 4 days now.
Wow, that's an intense test that you have there :)
> Daniel,
> will be good if you could post [4] for comments if you think that is
> the right thing to do and helps solve the issue you saw as well.
Alright, will do!
Thanks a lot,
Daniel
WARNING: multiple messages have this Message-ID (diff)
From: zonque@gmail.com (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] ARM: omap: edma: add suspend suspend/resume hooks
Date: Sun, 17 Nov 2013 23:09:41 +0100 [thread overview]
Message-ID: <52893EA5.7080809@gmail.com> (raw)
In-Reply-To: <52863232.30207@ti.com>
Hi Nishanth,
On 11/15/2013 03:39 PM, Nishanth Menon wrote:
> To trigger the fail, I created a custom Test case on TI vendor kernel
> based on v3.12 tag:
> On beagleBone-Black
> test scenario (BBB):
>
> Boot from SD card
> ensure firmware is loaded (rev 0x182)
> run LTP fsstress [1] in background on EMMC
> mkdir -p /tmp/testing
> mke2fs /dev/mmcblk1p1
> mount /dev/mmcblk1p1 /tmp/testing
> fsstress -d /tmp/testing p 4 -n 1000 -l0 -v >/dev/null &
> run ping in the background (to add yet another interface)
> run memtester[2] (70% of free memory)
> memtester 343M >/dev/null &
> sleep 10 (to allow memtester to start up properly)
> start=`date`;i=0; while [ 1 ]; do rtcwake -d /dev/rtc0 -m mem -s
> 2; i=$((i + 1)); echo "$i: start =$start, now="`date`; sleep 2; done
>
> Eventual hang log (using the regular suspend-resume): [3] - took close
> to two days of testing to trigger this.
>
> Moving to a suspend_late and resume_early such as in [4], it passed
> the test for over 4 days now.
Wow, that's an intense test that you have there :)
> Daniel,
> will be good if you could post [4] for comments if you think that is
> the right thing to do and helps solve the issue you saw as well.
Alright, will do!
Thanks a lot,
Daniel
next prev parent reply other threads:[~2013-11-17 22:09 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 20:21 [PATCH v4] ARM: omap: edma: add suspend suspend/resume hooks Daniel Mack
2013-10-30 20:21 ` Daniel Mack
2013-10-31 22:25 ` Vaibhav Bedia
2013-10-31 22:25 ` Vaibhav Bedia
2013-11-06 17:36 ` Joel Fernandes
2013-11-06 17:36 ` Joel Fernandes
2013-11-07 13:30 ` Gururaja Hebbar
2013-11-07 13:30 ` Gururaja Hebbar
2013-11-07 13:32 ` Daniel Mack
2013-11-07 13:32 ` Daniel Mack
2013-11-07 15:18 ` Nishanth Menon
2013-11-07 15:18 ` Nishanth Menon
2013-11-07 15:36 ` Daniel Mack
2013-11-07 15:36 ` Daniel Mack
2013-11-07 15:48 ` Nishanth Menon
2013-11-07 15:48 ` Nishanth Menon
2013-11-07 20:42 ` Vaibhav Bedia
2013-11-07 20:42 ` Vaibhav Bedia
2013-11-15 14:39 ` Nishanth Menon
2013-11-15 14:39 ` Nishanth Menon
2013-11-17 22:09 ` Daniel Mack [this message]
2013-11-17 22:09 ` Daniel Mack
2013-11-07 20:34 ` Vaibhav Bedia
2013-11-07 20:34 ` Vaibhav Bedia
2013-11-07 15:34 ` Nishanth Menon
2013-11-07 15:34 ` Nishanth Menon
2013-11-07 16:27 ` Grygorii Strashko
2013-11-07 16:27 ` Grygorii Strashko
2013-11-07 20:46 ` Vaibhav Bedia
2013-11-07 20:46 ` Vaibhav Bedia
2013-11-07 16:34 ` Joel Fernandes
2013-11-07 16:34 ` Joel Fernandes
2013-11-07 16:49 ` Joel Fernandes
2013-11-07 16:49 ` Joel Fernandes
2013-11-07 17:37 ` Daniel Mack
2013-11-07 17:37 ` Daniel Mack
2013-11-07 21:39 ` Joel Fernandes
2013-11-07 21:39 ` Joel Fernandes
2013-11-08 4:07 ` Gururaja Hebbar
2013-11-08 4:07 ` Gururaja Hebbar
2013-11-08 7:51 ` Daniel Mack
2013-11-08 7:51 ` Daniel Mack
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=52893EA5.7080809@gmail.com \
--to=zonque@gmail.com \
--cc=Russ.Dill@ti.com \
--cc=balajitk@ti.com \
--cc=gururaja.hebbar@ti.com \
--cc=joelf@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=matt@ohporter.com \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=s.neumann@raumfeld.com \
--cc=vaibhav.bedia@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.