From: Stefan Wahren <stefan.wahren-eS4NqCHxEME@public.gmane.org>
To: Aaro Koskinen <aaro.koskinen-X3B1VOXEql0@public.gmane.org>,
linux-mmc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-rpi-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: Linux v5.0-rc7: bcm2835 MMC issues
Date: Sun, 24 Feb 2019 20:03:10 +0100 (CET) [thread overview]
Message-ID: <155745885.93258.1551034990363@email.ionos.de> (raw)
In-Reply-To: <20190224150746.GC26495-4/PLUo9XfK9owWHViPbQSXlKr5M7+etX9Sl0XMgJPXI@public.gmane.org>
Hi Aaro,
> Aaro Koskinen <aaro.koskinen-X3B1VOXEql0@public.gmane.org> hat am 24. Februar 2019 um 16:07 geschrieben:
>
>
> Hi,
>
> After upgrading from v4.20 -> v5.0-rc7, I'm getting MMC issues on
> RPi3. Below is one example, system just ends up being completely freezed
> after couple hours into GCC bootstrap (passed fine with v4.20).
>
> Happened three times already (also after replacing the MMC card just
> in case).
>
thanks for your report.
Can you give us a more detailed test scenario?
How long does it take until the issue occur?
Did you already tested v4.20.12 or only v4.20?
Does the issue occur in v5.0-rc7 if you make sdhost use PIO mode (CONFIG_DMA_BCM2835=m)?
next prev parent reply other threads:[~2019-02-24 19:03 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 [this message]
[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
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=155745885.93258.1551034990363@email.ionos.de \
--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