linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: decoded problem in 2.4.22-pre10
Date: Tue, 5 Aug 2003 14:02:38 +0200	[thread overview]
Message-ID: <9433E945C9B@vcnet.vc.cvut.cz> (raw)

On  5 Aug 03 at 12:20, Stephan von Krawczynski wrote:
> On Tue, 5 Aug 2003 10:00:40 +0200
> Stephan von Krawczynski <skraw@ithnet.com> wrote:
> 
> > Hello all,
> > 
> > the testbox crashed again this night, unfortunately I made a mistake
> > yesterday and started vmware once. Although only the usual modules were
> > loaded at crash time and not the application, the kernel was tainted of
> > course. Nevertheless I present the data:
> 
> I re-checked the setup with vmware and found out I can shoot it down in no
> time. So you probably should just forget about this bug report, because loading
> vmware modules does obviously do harm.

Any details? Were there some warning while vmmon was built?
                                                            Petr
                                                            


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

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-05 12:02 Petr Vandrovec [this message]
2003-08-05 12:23 ` 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:46 Petr Vandrovec
2003-08-06 10:27 ` 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:
  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=9433E945C9B@vcnet.vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skraw@ithnet.com \
    /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;
as well as URLs for NNTP newsgroup(s).