From: Nigel Cunningham <ncunningham@linuxmail.org>
To: Ake <Ake.Sandgren@hpc2n.umu.se>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Slab corruption with 2.6.9 + swsusp2.1
Date: Wed, 17 Nov 2004 21:44:40 +1100 [thread overview]
Message-ID: <1100688279.4040.4.camel@desktop.cunninghams> (raw)
In-Reply-To: <20041117064403.GB26723@hpc2n.umu.se>
Hi.
On Wed, 2004-11-17 at 17:44, Ake wrote:
> On Wed, Nov 17, 2004 at 07:09:19AM +1100, Nigel Cunningham wrote:
> > On Tue, 2004-11-16 at 22:59, Ake wrote:
> > > I got a slab corruption message running 2.6.9 + swsusp2.1 and
> > > nvidia_compat.patch + vm-pages_scanned-active_list.patch from -ck3.
> >
> > Just so I'm clear, why do you think it's suspending that's causing the
> > corruption?
>
> I don't. I was just making clear exactly what kernel source i was using.
Oh, okay. I was going off the subject :>
Had you suspended prior to this? If not, you can rule the suspend code
out. If you had, I wouldn't rule it out because I am trying to identify
the cause of some occasional slab corruption at the moment. Haven't got
it reproducible yet.
> It probably haven't got anything to do with the swsusp code, but since
> those patches are applied i though i better let you know.
>
> The machine was basically doing nothing since i was out for lunch.
> X was running screensaver and it was playing some mp3's.
Regards,
Nigel
--
Nigel Cunningham
Pastoral Worker
Christian Reformed Church of Tuggeranong
PO Box 1004, Tuggeranong, ACT 2901
You see, at just the right time, when we were still powerless, Christ
died for the ungodly. -- Romans 5:6
next prev parent reply other threads:[~2004-11-17 10:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-16 11:59 Slab corruption with 2.6.9 + swsusp2.1 Ake
2004-11-16 20:09 ` Nigel Cunningham
2004-11-17 6:44 ` Ake
2004-11-17 10:44 ` Nigel Cunningham [this message]
2004-11-17 11:03 ` Ake
2004-11-17 11:04 ` Nigel Cunningham
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=1100688279.4040.4.camel@desktop.cunninghams \
--to=ncunningham@linuxmail.org \
--cc=Ake.Sandgren@hpc2n.umu.se \
--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