From: Chris Ball <cjb@laptop.org>
To: Cyril Hrubis <metan@ucw.cz>
Cc: pavel@ucw.cz, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, eric.y.miao@gmail.com,
utx@penguin.cz, zaurus-devel@lists.linuxtogo.org,
marek.vasut@gmail.com, linux-mmc@vger.kernel.org
Subject: Re: zaurus: mmcblk0: error -110
Date: Tue, 12 Apr 2011 15:47:34 -0400 [thread overview]
Message-ID: <m3oc4bxne1.fsf@pullcord.laptop.org> (raw)
In-Reply-To: <20110412193944.GC2665@atrey.karlin.mff.cuni.cz> (Cyril Hrubis's message of "Tue, 12 Apr 2011 21:39:44 +0200")
Hi,
On Tue, Apr 12 2011, Cyril Hrubis wrote:
>> Your symptoms match the bug that was fixed by:
>>
>> bad3babace2ee4d ("mmc: fix CONFIG_MMC_UNSAFE_RESUME regression")
>>
>> but this fix made it into 2.6.38, so if you're using 2.6.38 final then
>> you shouldn't be seeing this. Could you confirm that you have this
>> patch?
>
> It seems that the pxa tree I have is still based on 2.6.38-rc8.
>
> And yes, turning CONFIG_MMC_UNSAFE_RESUME off seems to fix that problem.
>
> I'll try to update the kernel tree and try again with CONFIG_MMC_UNSAFE_RESUME
> enabled.
Okay, great. It was introduced in 2.6.38-rc1 and fixed in 2.6.38 final.
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
WARNING: multiple messages have this Message-ID (diff)
From: cjb@laptop.org (Chris Ball)
To: linux-arm-kernel@lists.infradead.org
Subject: zaurus: mmcblk0: error -110
Date: Tue, 12 Apr 2011 15:47:34 -0400 [thread overview]
Message-ID: <m3oc4bxne1.fsf@pullcord.laptop.org> (raw)
In-Reply-To: <20110412193944.GC2665@atrey.karlin.mff.cuni.cz> (Cyril Hrubis's message of "Tue, 12 Apr 2011 21:39:44 +0200")
Hi,
On Tue, Apr 12 2011, Cyril Hrubis wrote:
>> Your symptoms match the bug that was fixed by:
>>
>> bad3babace2ee4d ("mmc: fix CONFIG_MMC_UNSAFE_RESUME regression")
>>
>> but this fix made it into 2.6.38, so if you're using 2.6.38 final then
>> you shouldn't be seeing this. Could you confirm that you have this
>> patch?
>
> It seems that the pxa tree I have is still based on 2.6.38-rc8.
>
> And yes, turning CONFIG_MMC_UNSAFE_RESUME off seems to fix that problem.
>
> I'll try to update the kernel tree and try again with CONFIG_MMC_UNSAFE_RESUME
> enabled.
Okay, great. It was introduced in 2.6.38-rc1 and fixed in 2.6.38 final.
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
WARNING: multiple messages have this Message-ID (diff)
From: Chris Ball <cjb@laptop.org>
To: Cyril Hrubis <metan@ucw.cz>
Cc: pavel@ucw.cz, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, eric.y.miao@gmail.com,
utx@penguin.cz, zaurus-devel@www.linuxtogo.org,
marek.vasut@gmail.com, linux-mmc@vger.kernel.org
Subject: Re: zaurus: mmcblk0: error -110
Date: Tue, 12 Apr 2011 15:47:34 -0400 [thread overview]
Message-ID: <m3oc4bxne1.fsf@pullcord.laptop.org> (raw)
In-Reply-To: <20110412193944.GC2665@atrey.karlin.mff.cuni.cz> (Cyril Hrubis's message of "Tue, 12 Apr 2011 21:39:44 +0200")
Hi,
On Tue, Apr 12 2011, Cyril Hrubis wrote:
>> Your symptoms match the bug that was fixed by:
>>
>> bad3babace2ee4d ("mmc: fix CONFIG_MMC_UNSAFE_RESUME regression")
>>
>> but this fix made it into 2.6.38, so if you're using 2.6.38 final then
>> you shouldn't be seeing this. Could you confirm that you have this
>> patch?
>
> It seems that the pxa tree I have is still based on 2.6.38-rc8.
>
> And yes, turning CONFIG_MMC_UNSAFE_RESUME off seems to fix that problem.
>
> I'll try to update the kernel tree and try again with CONFIG_MMC_UNSAFE_RESUME
> enabled.
Okay, great. It was introduced in 2.6.38-rc1 and fixed in 2.6.38 final.
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2011-04-12 19:42 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 15:15 zaurus: mmcblk0: error -110 Cyril Hrubis
2011-04-12 15:15 ` Cyril Hrubis
2011-04-12 15:17 ` Eric Miao
2011-04-12 15:17 ` Eric Miao
2011-04-12 15:23 ` Cyril Hrubis
2011-04-12 15:23 ` Cyril Hrubis
2011-04-12 15:52 ` Cyril Hrubis
2011-04-12 15:52 ` Cyril Hrubis
2011-04-12 18:04 ` Pavel Machek
2011-04-12 18:04 ` Pavel Machek
2011-04-13 17:10 ` Marek Vasut
2011-04-13 17:10 ` Marek Vasut
2011-04-13 17:12 ` Marek Vasut
2011-04-13 17:12 ` Marek Vasut
2011-04-12 19:24 ` Chris Ball
2011-04-12 19:24 ` Chris Ball
2011-04-12 19:24 ` Chris Ball
[not found] ` <m3aafvz30t.fsf-0VGQAjvlmrQzNDMTQreKSUB+6BGkLq7r@public.gmane.org>
2011-04-12 19:39 ` Cyril Hrubis
2011-04-12 19:39 ` Cyril Hrubis
2011-04-12 19:39 ` Cyril Hrubis
2011-04-12 19:47 ` Chris Ball [this message]
2011-04-12 19:47 ` Chris Ball
2011-04-12 19:47 ` Chris Ball
[not found] ` <m3oc4bxne1.fsf-0VGQAjvlmrQzNDMTQreKSUB+6BGkLq7r@public.gmane.org>
2011-04-12 20:54 ` Cyril Hrubis
2011-04-12 20:54 ` Cyril Hrubis
2011-04-12 20:54 ` Cyril Hrubis
2011-04-12 21:21 ` Chris Ball
2011-04-12 21:21 ` Chris Ball
2011-04-12 21:21 ` Chris Ball
2011-04-12 21:39 ` Chris Ball
2011-04-12 21:39 ` Chris Ball
2011-04-12 21:39 ` Chris Ball
2011-04-12 22:43 ` Cyril Hrubis
2011-04-12 22:43 ` Cyril Hrubis
2011-04-12 22:43 ` Cyril Hrubis
[not found] ` <20110412224333.GA22640-jyMamyUUXNJG4ohzP4jBZS1Fcj925eT/@public.gmane.org>
2011-04-12 22:53 ` Chris Ball
2011-04-12 22:53 ` Chris Ball
2011-04-12 22:53 ` Chris Ball
2011-04-15 21:33 ` Cyril Hrubis
2011-04-15 21:33 ` Cyril Hrubis
2011-04-15 21:33 ` Cyril Hrubis
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=m3oc4bxne1.fsf@pullcord.laptop.org \
--to=cjb@laptop.org \
--cc=eric.y.miao@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=marek.vasut@gmail.com \
--cc=metan@ucw.cz \
--cc=pavel@ucw.cz \
--cc=utx@penguin.cz \
--cc=zaurus-devel@lists.linuxtogo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.