From: Stefan Wahren <stefan.wahren-eS4NqCHxEME@public.gmane.org>
To: Aaro Koskinen <aaro.koskinen-X3B1VOXEql0@public.gmane.org>
Cc: linux-mmc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-rpi-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: Linux v5.0-rc7: bcm2835 MMC issues
Date: Thu, 28 Feb 2019 09:09:41 +0100 [thread overview]
Message-ID: <7122d61d-eca7-e571-7840-99987d271c97@i2se.com> (raw)
In-Reply-To: <20190227185101.GA28051-4/PLUo9XfK9owWHViPbQSXlKr5M7+etX9Sl0XMgJPXI@public.gmane.org>
Hi Aaro,
Am 27.02.2019 um 19:51 schrieb Aaro Koskinen:
> On Tue, Feb 26, 2019 at 09:31:14AM +0100, Stefan Wahren wrote:
>> it will take some time for to setup this test scenario. Could you please
>> do me a favor and test 4.20.12 which has some backports of recent mmc /
>> DMA fixes.
> Both 4.20 and 4.20.12 work fine. Only 5.0-rc fails reliably.
thanks. Yesterday i ran the gcc bootstraping with multi_v7_defconfig on
a 32 bit rootfs. It completed the build without any issues (took several
hours).
We need to find a faster scenario.
I think of something like this:
|stress-ng --vm 2 --vm-bytes 1G --timeout 60s|
|Stefan
|
>
> A.
next prev parent reply other threads:[~2019-02-28 8:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-24 15:07 Linux v5.0-rc7: bcm2835 MMC issues Aaro Koskinen
[not found] ` <20190224150746.GC26495-4/PLUo9XfK9owWHViPbQSXlKr5M7+etX9Sl0XMgJPXI@public.gmane.org>
2019-02-24 19:03 ` Stefan Wahren
[not found] ` <155745885.93258.1551034990363-uEpKuDZ350hmhno068Nerg@public.gmane.org>
2019-02-24 20:15 ` Aaro Koskinen
2019-02-26 1:15 ` Aaro Koskinen
[not found] ` <06528ceb-ff1d-626b-f520-477b0ea49d6f@i2se.com>
[not found] ` <06528ceb-ff1d-626b-f520-477b0ea49d6f-eS4NqCHxEME@public.gmane.org>
2019-02-27 18:51 ` Aaro Koskinen
[not found] ` <20190227185101.GA28051-4/PLUo9XfK9owWHViPbQSXlKr5M7+etX9Sl0XMgJPXI@public.gmane.org>
2019-02-28 8:09 ` Stefan Wahren [this message]
2019-03-09 10:57 ` Stefan Wahren
[not found] ` <1685719010.348465.1552129077871-uEpKuDZ350hmhno068Nerg@public.gmane.org>
2019-03-10 0:51 ` Aaro Koskinen
[not found] ` <20190310005131.GF30189-4/PLUo9XfK9owWHViPbQSXlKr5M7+etX9Sl0XMgJPXI@public.gmane.org>
2019-03-15 17:12 ` Stefan Wahren
2019-03-28 22:58 ` Aaro Koskinen
[not found] ` <20190328225818.GE16484-4/PLUo9XfK9owWHViPbQSXlKr5M7+etX9Sl0XMgJPXI@public.gmane.org>
2019-03-29 19:19 ` Aaro Koskinen
[not found] ` <20190329191926.GG16484-4/PLUo9XfK9owWHViPbQSXlKr5M7+etX9Sl0XMgJPXI@public.gmane.org>
2019-03-30 13:15 ` Stefan Wahren
[not found] ` <1632685811.158736.1553951733181-uEpKuDZ350hmhno068Nerg@public.gmane.org>
2019-03-30 14:53 ` Aaro Koskinen
[not found] ` <20190330145300.GI16484-4/PLUo9XfK9owWHViPbQSXlKr5M7+etX9Sl0XMgJPXI@public.gmane.org>
2019-03-30 15:13 ` Stefan Wahren
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=7122d61d-eca7-e571-7840-99987d271c97@i2se.com \
--to=stefan.wahren-es4nqchxeme@public.gmane.org \
--cc=aaro.koskinen-X3B1VOXEql0@public.gmane.org \
--cc=linux-mmc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-rpi-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
/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