From: Seungwon Jeon <tgih.jun@samsung.com>
To: 'Daniel Drake' <dsd@laptop.org>, linux-mmc@vger.kernel.org
Subject: RE: "exclude asynchronous transfer" patch causes boot fail
Date: Tue, 18 Jun 2013 21:33:45 +0900 [thread overview]
Message-ID: <001701ce6c20$134cda00$39e68e00$%jun@samsung.com> (raw)
In-Reply-To: <CAMLZHHRzvXucfoUn9ZqVv7Z9Q8oDbZu5-O9t8dJ=YpSjbbzXHg@mail.gmail.com>
On Saturday, June 15, 2013, Daniel Drake wrote:
> On Mon, Jun 10, 2013 at 1:53 PM, Daniel Drake <dsd@laptop.org> wrote:
> > Testing the latest linus kernel on OLPC XO-4 (sdhci-pxav3), boot
> > fails. Userspace does start, and I see that systemd is starting a few
> > services (feels a bit slower than usual), then it hangs still while
> > loading initial services - I don't even get to a shell prompt.
> >
> > git-bisect shows the following commit introduces the problem:
> >
> > commit 369d321ed1baa7748e770aaaae4d8effad699633
> > Author: Seungwon Jeon <tgih.jun@samsung.com>
> > Date: Wed Dec 26 10:40:17 2012 +0900
> >
> > mmc: queue: exclude asynchronous transfer for special request
>
> I realised that I wasn't testing linus master as I thought I was - I
> was some way back in the history.
> Updating to the latest makes the issue go away. I guess this was already fixed.
Okay.
For reference, there is no difference with between REQ_DISCARD and REG_FLUSH
in mmc_blk_issue_rq()'s handling.
Thanks,
Seungwon Jeon
>
> Thanks
> Daniel
prev parent reply other threads:[~2013-06-18 12:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 19:53 "exclude asynchronous transfer" patch causes boot fail Daniel Drake
2013-06-14 21:17 ` Daniel Drake
2013-06-18 12:33 ` Seungwon Jeon [this message]
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='001701ce6c20$134cda00$39e68e00$%jun@samsung.com' \
--to=tgih.jun@samsung.com \
--cc=dsd@laptop.org \
--cc=linux-mmc@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).