From: David Woodhouse <dwmw2@infradead.org>
To: William Jhun <wjhun@ayrnetworks.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: "Kernel panic: mtdblock: request list destroyed" with recent changes
Date: Sat, 16 Mar 2002 08:56:50 +0000 [thread overview]
Message-ID: <25466.1016269010@redhat.com> (raw)
In-Reply-To: <20020315200923.J6821@ayrnetworks.com>
wjhun@ayrnetworks.com said:
> This happens whether there are MTD devices registered or not, so I
> doubt this is related to any low-level flash drivers/devices. I
> noticed some changes that happened to mtdblock.c on 3/11; perhaps
> these are related? Sorry, no call trace or anything...
This happens for the NFTL driver too, which is confusing - there are
_definitely_ no changes there which are likely to have caused this. Can you
try it with a completely up to date tree except for v1.52 of mtdblock.c ?
Other people who reported this with NFTL - did you also have
CONFIG_MTD_BLOCK enabled for some reason?
--
dwmw2
next prev parent reply other threads:[~2002-03-16 8:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-16 4:09 "Kernel panic: mtdblock: request list destroyed" with recent changes William Jhun
2002-03-16 8:56 ` David Woodhouse [this message]
2002-03-17 10:35 ` David Woodhouse
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=25466.1016269010@redhat.com \
--to=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=wjhun@ayrnetworks.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