From: Pierre Ossman <drzeus-mmc@drzeus.cx>
To: Vitaly Wool <vitalywool@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix "prev->state: 2 != TASK_RUNNING??" problem on SD/MMC card removal
Date: Sun, 26 Nov 2006 21:25:18 +0100 [thread overview]
Message-ID: <4569F82E.1040207@drzeus.cx> (raw)
In-Reply-To: <20061123184217.a971d267.vitalywool@gmail.com>
Vitaly Wool wrote:
> Hello Pierre,
>
> currently on SD/MMC card removal the system exhibits the following message (the platform is ARM Versatile):
>
> prev->state: 2 != TASK_RUNNING??
> mmcqd/762[CPU#0]: BUG in __schedule at linux-2.6/kernel/sched.c:3826
>
Hmm... I can't find any such requirement in HEAD, or 2.6.18. What kernel
are you running?
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core developer http://www.rdesktop.org
next prev parent reply other threads:[~2006-11-26 20:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-23 15:42 [PATCH] fix "prev->state: 2 != TASK_RUNNING??" problem on SD/MMC card removal Vitaly Wool
2006-11-26 20:25 ` Pierre Ossman [this message]
2006-11-27 9:13 ` Vitaly Wool
2006-11-27 13:47 ` Pierre Ossman
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=4569F82E.1040207@drzeus.cx \
--to=drzeus-mmc@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=vitalywool@gmail.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