From: Seraphime Kirkovski <kirkseraph@gmail.com>
To: Adrian Hunter <adrian.hunter@intel.com>,
Shawn Lin <shawn.lin@rock-chips.com>, Pavel Machek <pavel@ucw.cz>,
linux-mmc@vger.kernel.org
Cc: kernel list <linux-kernel@vger.kernel.org>, O@macchiaveli
Subject: 4.13 on thinkpad x220: oops when writing to SD card
Date: Wed, 6 Sep 2017 09:08:07 +0200 [thread overview]
Message-ID: <20170906070807.4a4t6udmlbmsaab3@macchiaveli> (raw)
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: Shawn Lin <shawn.lin@rock-chips.com>, Pavel Machek <pavel@ucw.cz>,
linux-mmc@vger.kernel.org,
kernel list <linux-kernel@vger.kernel.org>
Bcc:
Subject: Re: 4.13 on thinkpad x220: oops when writing to SD card
Reply-To:
In-Reply-To: <6689241f-a4d8-7a3e-9f0b-482b034e5710@intel.com>
Hi,
> > Seems 4.13-rc4 was already broken for that but unfortuantely
> > I didn't
> > reproduce that. So maybe Seraphime can do git-bisect as he said "I get
> > it everytime" for which I assume it could be easy for him to find out
> > the problematic commit?
I can reliably reproduce it, although sometimes it needs some more work.
For example, I couldn't trigger it while writing less than 1 gigabyte
and sometimes I have to do it more than once. It helps if the machine is
doing something else in meantime, I do kernel builds.
> Another unrelated issue with mmc_init_request() is that
> mmc_exit_request()
> is not called if mmc_init_request() fails, which means mmc_init_request()
> must free anything it allocates when it fails.
Will try the patch and report back soon.
next reply other threads:[~2017-09-06 7:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 7:08 Seraphime Kirkovski [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-09-06 8:20 4.13 on thinkpad x220: oops when writing to SD card Seraphime Kirkovski
2017-09-08 9:29 ` Pavel Machek
2017-09-05 19:47 Pavel Machek
2017-09-06 2:44 ` Shawn Lin
2017-09-06 6:03 ` Adrian Hunter
2017-09-07 7:18 ` Ulf Hansson
2017-09-07 7:53 ` Adrian Hunter
2017-09-07 10:47 ` Seraphime Kirkovski
2017-09-07 12:06 ` Ulf Hansson
2017-09-07 12:55 ` Pavel Machek
2017-09-07 15:03 ` Ulf Hansson
2017-09-08 8:51 ` Pavel Machek
2017-09-07 19:58 ` Linus Walleij
2017-09-07 20:02 ` Linus Walleij
2017-09-08 2:51 ` Shawn Lin
2017-09-12 9:42 ` Linus Walleij
2017-09-13 4:04 ` Shawn Lin
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=20170906070807.4a4t6udmlbmsaab3@macchiaveli \
--to=kirkseraph@gmail.com \
--cc=6689241f-a4d8-7a3e-9f0b-482b034e5710@intel.com \
--cc=O@macchiaveli \
--cc=adrian.hunter@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=shawn.lin@rock-chips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox