* Nick Piggin <[email protected]> wrote:
> > > And yet despite my repeated pleas, none of those people has yet
> > > spent a bit of time with me to help analyse what is happening.
> >
> > btw., it might help to give specific, precise instructions about
> > what people should do to help you analyze this problem.
>
> Ray has been the first one to offer (thank you), and yes I have asked
> him for precise details of info to collect to hopefully work out what
> is happening with his first problem.
do you mean this paragraph:
| I guess /proc/meminfo, /proc/zoneinfo, /proc/vmstat, /proc/slabinfo
| before and after the updatedb run with the latest kernel would be a
| first step. top and vmstat output during the run wouldn't hurt either.
correct? Does "latest kernel" mean v2.6.22.1, or does it have to be
v2.6.23-rc1? I guess v2.6.22.1 would be fine as this is a VM problem,
not a scheduling problem.
the following script will gather all the above information for a 10
seconds interval:
http://people.redhat.com/mingo/cfs-scheduler/tools/cfs-debug-info.sh
Ray, please run this script before the updatedb run, once during the
updatedb run and once after the updatedb run, and send Nick the 3 files
it creates. (feel free to Cc: me too)
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
