public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Rankin <rankincj@yahoo.com>
To: alan@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Massive problems with 2.4.20 module loading
Date: Sat, 30 Nov 2002 16:08:17 +0000	[thread overview]
Message-ID: <3DE8E271.6090307@yahoo.com> (raw)

On Sat, 2002-11-30 at 08:49, Martin Loschwitz wrote:
 > I'm having massive problems with Linux 2.4.20 and modul loading.
 > In fact, it seems to have something to do with devfs.

On Sat Nov 30 2002 - 09:36:57 EST, Alan Cox wrote:
 > Linux 2,4.20 doesnt include vmware or ALSA. The fact you list those
 > modules alone suggests that the problem is that you haven't rebuilt
 > them for the new kernel.

Well maybe that's his problem and maybe it isn't, but he's not the only 
person thinking that there's something strange about devfs in 2.4.20. I 
have a 2.4.20-SMP box that is deadlocking when loading modules via 
devfs. The NMI watchdog has produced two oopsen for me, which I have 
published to this list, and while one oops is also from the ALSA 
modules, the other is from mga.o. Both oopsen occur in the 
__write_lock_failed() function and have devfs_open() in the module 
stack. I have most definitely NOT forgotten to recompile everything for 
2.4.20, and I am using symbol versioning anyway.

Chris


             reply	other threads:[~2002-11-30 16:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-30 16:08 Chris Rankin [this message]
2002-12-01  2:04 ` Massive problems with 2.4.20 module loading Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2002-11-30  8:49 Martin Loschwitz
2002-11-30 14:36 ` Alan Cox

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=3DE8E271.6090307@yahoo.com \
    --to=rankincj@yahoo.com \
    --cc=alan@redhat.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