From: narmstrong@baylibre.com (Neil Armstrong)
To: linus-amlogic@lists.infradead.org
Subject: emmc problems with linux 4.10-rc1
Date: Thu, 29 Dec 2016 10:04:30 +0100 [thread overview]
Message-ID: <c36847da-2f19-f18b-1569-e44e0873d15c@baylibre.com> (raw)
In-Reply-To: <1c70f4ea-f310-ec70-4a42-ca59da42cc54@poczta.onet.pl>
On 12/28/2016 04:19 PM, Micha? Zegan wrote:
> Hello, it seems there are the following problems with mmc on linux
> 4.10.0-rc1 or actually the latest master near rc1:
> First, attempt to unload the module causes a kernel warning, so the
> module is not properly unloadable
> Second, I once loaded mmc module first then mmc_block and the kernel
> panicked because of a fatal exception in interrupt. I was currently
> unable to reproduce the second problem.
>
>
>
> _______________________________________________
> linux-amlogic mailing list
> linux-amlogic at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-amlogic
>
Hi,
could you provide some console logs ?
Those statements won't help us until we have some proper kernel messages,
current kernel config, kernel exact version and way for use to reproduce the issue.
Thanks,
Meil
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-amlogic/attachments/20161229/89f8b5e9/attachment.sig>
next prev parent reply other threads:[~2016-12-29 9:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-28 15:19 Michał Zegan
2016-12-29 9:04 ` Neil Armstrong [this message]
2016-12-29 15:39 ` Michał Zegan
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=c36847da-2f19-f18b-1569-e44e0873d15c@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=linus-amlogic@lists.infradead.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
all inboxes | Powered by JetHome®