From: Anders Karlsson <anders@trudheim.com>
To: Oleg Drokin <green@namesys.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: kernel BUG at inode.c:562!
Date: 13 May 2003 17:02:08 +0100 [thread overview]
Message-ID: <1052841728.5349.40.camel@tor.trudheim.com> (raw)
In-Reply-To: <20030513124135.GA28238@namesys.com>
[-- Attachment #1: Type: text/plain, Size: 491 bytes --]
On Tue, 2003-05-13 at 13:41, Oleg Drokin wrote:
> Hello!
[snip]
> Hm, can you please try to reproduce without vmware modules ever being loaded?
I have stopped VMware and prevented it from starting again. I have
without problem built 30+ rpms and subsequently cleaned up the BUILD
directory. Not a single problem. I will however carry on testing.
I will also notify VMware about a potential problem with their product.
They have been helpful before.
Regards,
/Anders
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2003-05-13 15:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 10:58 kernel BUG at inode.c:562! Anders Karlsson
2003-05-13 11:14 ` Arjan van de Ven
2003-05-13 11:25 ` Anders Karlsson
2003-05-13 13:08 ` other BUGs and Oopsen Anders Karlsson
2003-05-13 12:41 ` kernel BUG at inode.c:562! Oleg Drokin
2003-05-13 13:13 ` Anders Karlsson
2003-05-13 16:02 ` Anders Karlsson [this message]
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=1052841728.5349.40.camel@tor.trudheim.com \
--to=anders@trudheim.com \
--cc=green@namesys.com \
--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;
as well as URLs for NNTP newsgroup(s).