From: Joel Reardon <joel@clambassador.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Artem Bityutskiy <dedekind1@gmail.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: mtdchar kernel oops
Date: Mon, 16 Apr 2012 14:37:06 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.00.1204161329200.21808@eristoteles.iwoars.net> (raw)
In-Reply-To: <20120415215355.GS6589@ZenIV.linux.org.uk>
The troubled asm pair corresponds to this line:
this_cpu_add(mnt->mnt_pcp->mnt_count, n) in the inline mnt_add_count().
So I suppose that perhaps either mnt is bad, or mnt_pcp is bad.
I'm using nandsim to simulate the mtd device. Steps are simple, load the
modules:
nand_ecc nand nand_ids mtd mtd_blkdevs mtdblock mtdchar
nandsim first_id_byte=0x20 second_id_byte=0xa5 third_id_byte=0x00 fourth_id_byte=0x15 parts=0xa40 rptwear=1000
then `ubiformat /dev/mtd0` does the oops.
>
> Could you add printk into mtdchar_open(), dumping mnt and count values
> right after simple_pin_fs() call?
>
It oopses before it returns from the simple_pin_fs call, so that won't be
possible...
Cheers,
Joel
WARNING: multiple messages have this Message-ID (diff)
From: Joel Reardon <joel@clambassador.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: mtdchar kernel oops
Date: Mon, 16 Apr 2012 14:37:06 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.00.1204161329200.21808@eristoteles.iwoars.net> (raw)
In-Reply-To: <20120415215355.GS6589@ZenIV.linux.org.uk>
The troubled asm pair corresponds to this line:
this_cpu_add(mnt->mnt_pcp->mnt_count, n) in the inline mnt_add_count().
So I suppose that perhaps either mnt is bad, or mnt_pcp is bad.
I'm using nandsim to simulate the mtd device. Steps are simple, load the
modules:
nand_ecc nand nand_ids mtd mtd_blkdevs mtdblock mtdchar
nandsim first_id_byte=0x20 second_id_byte=0xa5 third_id_byte=0x00 fourth_id_byte=0x15 parts=0xa40 rptwear=1000
then `ubiformat /dev/mtd0` does the oops.
>
> Could you add printk into mtdchar_open(), dumping mnt and count values
> right after simple_pin_fs() call?
>
It oopses before it returns from the simple_pin_fs call, so that won't be
possible...
Cheers,
Joel
next prev parent reply other threads:[~2012-04-16 12:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-15 11:58 mtdchar kernel oops Joel Reardon
2012-04-15 14:19 ` Fabio Estevam
2012-04-15 14:19 ` Fabio Estevam
2012-04-19 0:51 ` Fabio Estevam
2012-04-19 0:51 ` Fabio Estevam
2012-04-15 14:28 ` Richard Weinberger
2012-04-15 14:34 ` Fabio Estevam
2012-04-15 15:32 ` Al Viro
2012-04-15 15:32 ` Al Viro
2012-04-15 17:57 ` Joel Reardon
2012-04-15 17:57 ` Joel Reardon
2012-04-15 21:53 ` Al Viro
2012-04-15 21:53 ` Al Viro
2012-04-16 12:37 ` Joel Reardon [this message]
2012-04-16 12:37 ` Joel Reardon
2012-04-16 19:17 ` Al Viro
2012-04-16 19:17 ` Al Viro
2012-04-18 12:55 ` Joel Reardon
2012-04-18 12:55 ` Joel Reardon
2012-04-18 13:12 ` Artem Bityutskiy
2012-04-18 13:12 ` Artem Bityutskiy
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=alpine.DEB.2.00.1204161329200.21808@eristoteles.iwoars.net \
--to=joel@clambassador.com \
--cc=dedekind1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=viro@ZenIV.linux.org.uk \
/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.