[Crash-utility] crash bug on 2.6.27.8

Durga Prasad durgaprasadsharma at gmail.com
Tue Feb 10 09:02:17 UTC 2009


You can find the kprobe module that Dave mentioned on the thread *Date: Sat,
8 Mar 2008 00:34:27 +0530*

Regards
Durga


On Tue, Feb 10, 2009 at 2:15 PM, Jun Koi <junkoi2004 at gmail.com> wrote:

> On Mon, Feb 9, 2009 at 11:51 PM, Dave Anderson <anderson at redhat.com>
> wrote:
> >
> > ----- "Jun Koi" <junkoi2004 at gmail.com> wrote:
> >
> >> Hi,
> >>
> >> When using the latest crash on 2.6.27.14 to analyze live memory
> >> (running crash without any option), I got a bug like below. How can I
> >> fix that?
> >>
> >> (A similar problem is also seen on 2.6.27.8)
> >>
> >> Thanks,
> >> Jun
> >
> > The "read error" indications are most likely due to your kernel
> > being configured with CONFIG_STRICT_DEVMEM, which restricts
> > /dev/mem access to the first 256 pages of physical memory,
> > which makes it useless for the crash utility.
>
> Thanks a lot for the information - I can fix the kernel here.
>
> But perhaps it is better to give some hints when we have such a error
> report, so users know that they should turn off the above
> configuration? I am sure that many people will have this problem, as
> the option may be ON by default.
>
> Thanks,
> Jun
>
> --
> Crash-utility mailing list
> Crash-utility at redhat.com
> https://www.redhat.com/mailman/listinfo/crash-utility
>



-- 

---------
Keep dreaming, for dreams are the precursors of things to come real.. @!#$
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/crash-utility/attachments/20090210/a346ec99/attachment.htm>


More information about the Crash-utility mailing list