From: "Manfred Spraul" <manfred@colorfullife.com>
To: "Hartmut Holz" <hartmut.holz@arcor.de>,
"Rik van Riel" <riel@conectiva.com.br>
Cc: "Linux kernel" <linux-kernel@vger.kernel.org>
Subject: Re: Uptime again?
Date: Sun, 27 Jan 2002 20:46:56 +0100 [thread overview]
Message-ID: <002801c1a76b$623033f0$010411ac@local> (raw)
In-Reply-To: <Pine.LNX.4.33L.0201261935330.32617-100000@imladris.surriel.com> <3C54546C.0@arcor.de>
From: "Hartmut Holz" <hartmut.holz@arcor.de>
> Rik van Riel wrote:
> >
> > The fact that lavrec crashes the machine while Xawtv works
> > suggests a device driver may be corrupting memory somewhere.
> >
>
> I got a debug patch from Manfred Spraul to debug slab.c.
poisoning of fields of 'struct page', slab poisoning, even of objects with constructors.
Same patch as:
http://groups.google.com/groups?selm=linux.kernel.3C3B6F65.F9226437%40colorfullife.com&rnum=1
> With this patch
> the machine ran for about 3 hours. No problem. I looked into slab.c and had an
> idea. What about just one CPU. So I built a new Kernel with just one CPU.
> Result: 1 CPU 1 Minute - 2 CPU 20 Minutes. I aspected a different result.
> In my opinion the whole thing has something to do with slab, SMP and threads.
>
Not with slab itself, probably with a slab user. Someone uses a stale pointer.
What do you means with one cpu? Did you boot a SMP kernel with "nosmp" on the command line, or did you make a kernel without
CONFIG_SMP?
--
Manfred
next prev parent reply other threads:[~2002-01-27 19:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-25 18:50 Uptime again? Richard B. Johnson
2002-01-25 21:24 ` jjs
2002-01-26 17:18 ` Hartmut Holz
2002-01-26 17:22 ` Rik van Riel
2002-01-26 21:32 ` Hartmut Holz
2002-01-26 21:40 ` Rik van Riel
2002-01-27 19:26 ` Hartmut Holz
2002-01-27 19:46 ` Manfred Spraul [this message]
2002-01-27 22:27 ` Hartmut Holz
-- strict thread matches above, loose matches on Subject: below --
2002-01-25 21:32 Greg Boyce
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='002801c1a76b$623033f0$010411ac@local' \
--to=manfred@colorfullife.com \
--cc=hartmut.holz@arcor.de \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.