public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Vipin Malik <vipin.malik@daniel.com>
To: Abraham vd Merwe <abraham@2d3d.co.za>
Cc: Erik Mouw <J.A.K.Mouw@ITS.TUDelft.NL>,
	MTD for Linux <linux-mtd@lists.infradead.org>
Subject: Re: partitioning bug
Date: Tue, 12 Jun 2001 09:21:11 -0500	[thread overview]
Message-ID: <3B262557.6B9EF53@daniel.com> (raw)
In-Reply-To: 20010611142913.A30396@crystal.2d3d.co.za

Abraham vd Merwe wrote:

> That's the problem, the addresses that do show up is useless:
>
> Same for System.map
>
> I can't get any references to calls in my module or the mtdpart module
> which
> is obviously where things go wrong ):

Compile the modules with EXTRA_CFLAGS =-g

Then recompile the kernel and reinstall the new modules.
Get another Oops, reboot (if your machine locked up), then reinstall
the modules in *exactly the same order* as the last time (but don't do the
oops step this time ;), then
run your saved ooops file through ksymoops, pointing it to /proc/ksyms, your
new module locations and
new System.map and new vmlinux files.


>
>
> I've even removed the static declarations in my module so that the
> functions
> can show up in /proc/ksyms but nothing. I don't think there's a bug in
> my
> module anyhow since it works perfectly without partiti

If it still does not work, then compile your MTD stuff into the kernel (not
as modules)
and get your oops that way.

System.map does not contain any info re. module symbols as modules are loaded
at run time and
System.map is created during compile.

Vipin

  reply	other threads:[~2001-06-12 14:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-08 10:04 partitioning bug Abraham vd Merwe
2001-06-10 12:22 ` Erik Mouw
2001-06-11 12:29   ` Abraham vd Merwe
2001-06-12 14:21     ` Vipin Malik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-06-10 13:19 Kári Davíðsson
2001-06-11  7:37 ` Abraham vd Merwe

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=3B262557.6B9EF53@daniel.com \
    --to=vipin.malik@daniel.com \
    --cc=J.A.K.Mouw@ITS.TUDelft.NL \
    --cc=abraham@2d3d.co.za \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox