All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Beveridge <bbeveridge@bluewatersys.com>
To: linux-mtd@lists.infradead.org
Subject: BUG at dcache.h:276! Causing oops when I rmmod a nand module having mulitple partitions
Date: Mon, 22 Nov 2004 14:41:24 +1300	[thread overview]
Message-ID: <41A143C4.2090304@bluewatersys.com> (raw)

Hi all.  Here is the basic problem, I have a nand module that I want to 
insmod & rmmod.  It has multiple partitions that look like
static struct mtd_partition partition_info1[] = {   
        { name: "part1",                   
          offset: 0,                                                     
          size: 4 * 1024 * 1024 },                                     
        { name: "part2",                      
          offset: 4 * 1024 * 
1024,                                          
          size: 4 * 1024 * 1024 
},                                          
        { name: "part3",                             
                  offset: 8 * 1024 * 
1024,                                  
                  size: MTDPART_SIZ_FULL }
};

I call nand_scan on my device, and then add_mtd_partitions.
When I rmmod the module I simply call nand_release, because it 
automatically calls del_mtd_partitions.

However, this causes a BUG in dcache.h:276.
There is no oops if I only use a single partition.

Any thoughts on what might be going on?

Cheers
Brad

             reply	other threads:[~2004-11-22  1:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-22  1:41 Brad Beveridge [this message]
2004-11-22  3:17 ` BUG at dcache.h:276! Causing oops when I rmmod a nand module having mulitple partitions Brad Beveridge
2004-11-24 19:24   ` BUG at dcache.h:276! Causing oops when I rmmod a nand module having mulitple partitions (fix) Brad Beveridge

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=41A143C4.2090304@bluewatersys.com \
    --to=bbeveridge@bluewatersys.com \
    --cc=linux-mtd@lists.infradead.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.