Linux LVM users
 help / color / mirror / Atom feed
From: Raffael Herzog <herzog@raffael.ch>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] How to fix inconsistent LV structs?
Date: Mon Oct  7 06:32:13 2002	[thread overview]
Message-ID: <8765weh4wr.fsf@mail.raffael.ch> (raw)
In-Reply-To: <004101c26dec$5b58c950$2dbb0044@warl0k>

Hi Glenn,

Glenn Shannon wrote:

> Was this computer connected to a network when it went down?

Yes. I'm using the 3c95x driver.


> Looks like a stack overflow to me, but where was the originator? Coda?
> Unlikely but possible. Replaced syscalls usually (IIRC) indicate that
> not only did a stack overflow occur but also that registers were
> modified by whatever overflowed the stack.

Coda always replaces Syscalls, AFAIK. At least, it does so
on initialization.


> The kernel is noting itself
> as tainted, which means that some form on non-GPLed module is running
> (or has entered the stack to converse with the kernel directly, acting
> as a module..)

Correct, the nVidia driver taints the kernel.


cu,

   Raffi


-- 
=> Neu im Usenet? Fragen?    http://www.use-net.ch/usenet_intro_de.html <=
  The difference between theory and practice is that in theory, there is
                 no difference, but in practice, there is.
Raffael Herzog - herzog@raffael.ch - http://www.raffael.ch - ICQ #67961355

  reply	other threads:[~2002-10-07  6:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-05 17:48 [linux-lvm] How to fix inconsistent LV structs? Raffael Herzog
2002-10-07  3:53 ` Heinz J . Mauelshagen
2002-10-07  4:29   ` Raffael Herzog
2002-10-07  5:35     ` Glenn Shannon
2002-10-07  6:32       ` Raffael Herzog [this message]
2002-10-07  6:43     ` Heinz J . Mauelshagen
2002-10-07  8:40       ` Raffael Herzog
2002-10-09  6:24         ` Heinz J . Mauelshagen

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=8765weh4wr.fsf@mail.raffael.ch \
    --to=herzog@raffael.ch \
    --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