From: GCS <gcs@lsc.hu>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Kernel 2.4.12 bug?
Date: Wed Oct 24 08:01:01 2001 [thread overview]
Message-ID: <20011024151503.A4309@lsc.hu> (raw)
In-Reply-To: <20011024113747.C2271@tykepenguin.com>; from caulfield@sistina.com on Wed, Oct 24, 2001 at 11:37:47AM +0100
On Wed, Oct 24, 2001 at 11:37:47AM +0100, Patrick Caulfield <caulfield@sistina.com> wrote:
> It was just a thought. I'd like to see more of the ksymoops output - I'm also
> worried by the "Tainted" flag in the extract you posted last time.
Ok, I will get a new one, as 2.4.13 is out. I cross my fingers to have this
bug fixed (if it is kernel related even). The tainted flag is set because the
vfat module I think. Kernel says: no license, will taint the kernel (or
similar to this).
GCS
next prev parent reply other threads:[~2001-10-24 8:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-20 4:01 [linux-lvm] Kernel 2.4.12 bug? GCS
2001-10-22 3:52 ` Patrick Caulfield
2001-10-24 1:08 ` GCS
2001-10-24 2:59 ` Patrick Caulfield
2001-10-24 4:58 ` GCS
2001-10-24 5:38 ` Patrick Caulfield
2001-10-24 8:01 ` GCS [this message]
2001-10-24 9:00 ` Patrick Caulfield
-- strict thread matches above, loose matches on Subject: below --
2001-10-24 2:19 Jean-Eric Cuendet
2001-10-25 1:29 ` GCS
2001-10-24 10:30 Jean-Eric Cuendet
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=20011024151503.A4309@lsc.hu \
--to=gcs@lsc.hu \
--cc=linux-lvm@sistina.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