[Crash-utility] "cannot access vmalloc'd module memory" when loading kdump'ed vmcore in crash

[Worth, Kevin]

Thanks, Dave. Is it valid to just do "make modules" since it appears we're just adding a module or does the modification to arch/i386/mm/init.c necessitate a rebuilt kernel?

-Kevin

-----Original Message-----
From: crash-utility-bounces at redhat.com [mailto:crash-utility-bounces at redhat.com] On Behalf Of Dave Anderson
Sent: Tuesday, October 14, 2008 9:09 AM
To: Discussion list for crash utility usage, maintenance and development
Subject: Re: [Crash-utility] "cannot access vmalloc'd module memory" when loading kdump'ed vmcore in crash

Worth, Kevin wrote:
 > Thanks, Dave. I was actually going to ask about that since you had mentioned that  > /dev/crash should behave correctly in contrast to /dev/mem / /dev/kmem. Does it  > matter that my arch is i386 and not x86_64? I'll give this a shot.

D'oh...

Sorry yes, it sure does -- I've attached the i386 version of crash.h.
(The crash.c file is arch-neutral)

For that matter, 2.6.20 does have an i386 version of page_is_ram(), so all you'll have to do is add EXPORT_SYMBOL_GPL(page_is_ram) in "arch/i386/mm/init.c".

Dave