From: Maxim <maximlevitsky@gmail.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Eric Dumazet <dada1@cosmosbay.com>, Andi Kleen <ak@suse.de>,
David Howells <dhowells@redhat.com>,
Jeremy Fitzhardinge <jeremy@goop.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] : Is /proc/kcore still usefull and/or maintained ?
Date: Thu, 22 Mar 2007 01:28:18 +0200 [thread overview]
Message-ID: <200703220128.18610.maximlevitsky@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0703220011080.9555@yvahk01.tjqt.qr>
On Thursday 22 March 2007 01:11:57 Jan Engelhardt wrote:
>
> On Mar 21 2007 23:58, Eric Dumazet wrote:
> > Hi all
> >
> > On i386 , 2.6.20 / 2.6.21-rc4 :
> >
> > # gdb vmlinux /proc/kcore
> > error
> > # file /proc/kcore
> > error
>
> 00:11 ichi:/hld # file /proc/kcore
> /proc/kcore: ELF 32-bit LSB core file Intel 80386, version 1 (SYSV),
> SVR4-style, from 'vmlinux'
> 00:11 ichi:/hld # hexdump -C /proc/kcore | head -n5
> 00000000 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00 |.ELF............|
> 00000010 04 00 03 00 01 00 00 00 00 00 00 00 34 00 00 00 |............4...|
> 00000020 00 00 00 00 00 00 00 00 34 00 20 00 03 00 00 00 |........4. .....|
> 00000030 00 00 00 00 04 00 00 00 94 00 00 00 00 00 00 00 |................|
> 00000040 00 00 00 00 a8 06 00 00 00 00 00 00 00 00 00 00 |................|
> 00:11 ichi:/hld # uname -rm
> 2.6.20.2 i686
>
> >
> >
> > Apparently we can not llseek() anymore on this file (returns -EINVAL)
> >
> > On x86_64 2.6.20 it's working
> >
> > # file /proc/kcore
> > /proc/kcore: ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style
> >
> >
> > On i386 2.6.14 it's working too.
> >
> > Eric
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
> >
> >
>
> Jan
Hello,
I once had similar problem with /proc/kcore
then gdb showed all zeros for all kernel memory,
I had look at code , and I found that "Sparse memory model" was the problem, it doesn't say where kernel memory is
(I don't remember details now)
I once choosed it just for experiment, so I switched to Flat memory, and /proc/kcore works fine till then,
I use 32 bit x86 kernel.
Regards,
Maxim Levitsky
next prev parent reply other threads:[~2007-03-21 23:28 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 16:40 [BUG] Code reordering in swsusp breaks suspend on SMP systems Maxim Levitsky
2007-03-21 21:22 ` Nigel Cunningham
2007-03-21 21:38 ` Rafael J. Wysocki
2007-03-21 23:47 ` Nigel Cunningham
2007-03-22 0:25 ` Maxim
2007-03-22 4:51 ` David Chinner
2007-03-22 7:23 ` Rafael J. Wysocki
2007-03-22 7:31 ` Andrew Morton
2007-03-22 8:17 ` Rafael J. Wysocki
[not found] ` <200703220114.05228.maximlevitsky@gmail.com>
2007-03-21 23:16 ` Maxim
2007-03-22 0:32 ` Maxim
2007-03-21 22:21 ` Pavel Machek
2007-03-21 22:39 ` Rafael J. Wysocki
2007-03-21 22:58 ` [RFC] : Is /proc/kcore still usefull and/or maintained ? Eric Dumazet
2007-03-21 23:11 ` Jan Engelhardt
2007-03-21 23:28 ` Maxim [this message]
2007-03-21 23:53 ` Eric Dumazet
2007-03-22 0:04 ` Maxim
2007-03-22 6:35 ` Eric Dumazet
[not found] ` <200703220109.54719.maximlevitsky@gmail.com>
2007-03-21 23:18 ` [BUG] Code reordering in swsusp breaks suspend on SMP systems Maxim
[not found] ` <200703220024.25436.rjw@sisk.pl>
2007-03-21 23:39 ` Maxim
2007-03-21 23:44 ` Maxim
2007-03-21 23:53 ` Rafael J. Wysocki
2007-03-22 0:01 ` Maxim
2007-03-22 23:30 ` Rafael J. Wysocki
2007-03-23 14:42 ` Rafael J. Wysocki
2007-03-25 0:40 ` Maxim
2007-03-25 12:13 ` Rafael J. Wysocki
2007-03-25 15:10 ` Maxim
2007-03-25 19:27 ` Rafael J. Wysocki
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=200703220128.18610.maximlevitsky@gmail.com \
--to=maximlevitsky@gmail.com \
--cc=ak@suse.de \
--cc=dada1@cosmosbay.com \
--cc=dhowells@redhat.com \
--cc=jengelh@linux01.gwdg.de \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.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