From: Adrian Bunk <bunk@stusta.de>
To: Mark Lord <lkml@rtr.ca>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.15-rc1: kswapd crash
Date: Mon, 14 Nov 2005 04:56:16 +0100 [thread overview]
Message-ID: <20051114035616.GD5735@stusta.de> (raw)
In-Reply-To: <4377FFA7.4030400@rtr.ca>
On Sun, Nov 13, 2005 at 10:08:23PM -0500, Mark Lord wrote:
> Adrian Bunk wrote:
> >
> >Perhaps your vmware modules?
>
> No, not those. They've been there for years.
>...
So why did you delete the tainted line from the Oops output you sent?
It might be a bug in the kernel or a bug in your vmware modules exposed
by the new kernel.
Unless the opposite is proven, the latter is assumed...
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2005-11-14 3:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-13 23:52 2.6.15-rc1: kswapd crash Mark Lord
2005-11-13 23:55 ` Mark Lord
2005-11-14 0:47 ` Adrian Bunk
2005-11-14 3:08 ` Mark Lord
2005-11-14 3:56 ` Adrian Bunk [this message]
2005-11-14 13:20 ` Mark Lord
2005-11-14 13:25 ` Mark Lord
2005-11-14 13:37 ` Arjan van de Ven
2005-11-14 15:19 ` Mark Lord
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=20051114035616.GD5735@stusta.de \
--to=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
/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