All of lore.kernel.org
 help / color / mirror / Atom feed
From: GCS <gcs@lsc.hu>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Kernel 2.4.12 bug?
Date: Wed Oct 24 01:08:02 2001	[thread overview]
Message-ID: <20011024082146.A3130@lsc.hu> (raw)
In-Reply-To: <20011022094833.B557@tykepenguin.com>; from caulfield@sistina.com on Mon, Oct 22, 2001 at 09:48:33AM +0100

Hi,

On Mon, Oct 22, 2001 at 09:48:33AM +0100, Patrick Caulfield <caulfield@sistina.com> wrote:
> Not that I've seen. I'm running 2.4.12 ATM quite happily, LVM is a module rather
> than in the kernel though.
 My kernel is still complaining during vgscan, see the syslog:
lvm -- Module successfully initialized
invalidate: busy buffer
last message repeated 8 times

Also at reboot/halt I get:
 printing eip:
c014c022
Oops: 0000
CPU:    0
EIP:    0010:[proc_match+18/56]    Tainted: P
EFLAGS: 00010206
eax: d9fc2609   ebx: 03   ecx: 03   edx: 5a5a5a5a
esi: d9fc2609   edi: d9fc260d   ebp: d65f7d18   esp: d65f7d10
ds: 0018   es: 0018   ss: 0018
Process vgchange (pid: 345, stackpage=d65f7000)
etc...

Eip points inside c014bf4c t meminfo_read_proc. I have even patched it to
2.4.13pre3, but I get the same result. What should I check out? With 2.4.9
everything works normaly.

Cheers, GCS

  reply	other threads:[~2001-10-24  1:08 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 [this message]
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
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=20011024082146.A3130@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.