archive mirror
 help / color / mirror / Atom feed
From: "Petr Vandrovec" <>
To: Stephan von Krawczynski <>
Subject: Re: decoded problem in 2.4.22-pre10
Date: Tue, 5 Aug 2003 14:46:52 +0200	[thread overview]
Message-ID: <> (raw)

On  5 Aug 03 at 14:23, Stephan von Krawczynski wrote:
> Hello Petr,
> at this time I can't provide you with details or exact reporting as the box has
> to be used for finding the 2.4.22-pre stability problem I see. And since the
> crashes take quite some time to occur I cannot reboot and check out what's the
> deal with the vmware modules.
> And frankly: I find the application quite ok but tainting the kernel with the
> closed source modules is really something to think about, especially since
> there should be easy ways to avoid that completely.

This is not true. VMware modules are open source, they are just non-GPL.

And no, it is impossible to avoid them. At least nobody I know knows how
to avoid them.

There is only known problem (fixed in that
SuSE backported epoll patches from 2.5.x to both 2.4.19 and 2.4.20, and
while this seriously changes poll_initwait semantic, it caused only
warning at compile time, but at runtime it was corrupting kernel
stack. But I do not see epoll patches in 2.4.22pre10, so it must
be something else.
                                                    Best regards,
                                                        Petr Vandrovec

             reply	other threads:[~2003-08-05 12:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-05 12:46 Petr Vandrovec [this message]
2003-08-06 10:27 ` decoded problem in 2.4.22-pre10 Stephan von Krawczynski
  -- strict thread matches above, loose matches on Subject: below --
2003-08-05 12:57 Petr Vandrovec
2003-08-05 13:24 ` Stephan von Krawczynski
2003-08-05 12:02 Petr Vandrovec
2003-08-05 12:23 ` Stephan von Krawczynski
2003-08-05  8:00 Stephan von Krawczynski
2003-08-05 10:20 ` Stephan von Krawczynski
2003-08-05 12:40 ` Marcelo Tosatti

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).