public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcin Dalecki <dalecki@evision.ag>
To: "Michel Eyckmans (MCE)" <mce@pi.be>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.30 unresolved symbol: elv_queue_empty
Date: Fri, 02 Aug 2002 11:38:40 +0200	[thread overview]
Message-ID: <3D4A5320.8070100@evision.ag> (raw)
In-Reply-To: 200208012327.g71NRWZp013762@jebril.pi.be

Użytkownik Michel Eyckmans (MCE) napisał:
> The subject says nearly all: with 2.5.30, I get the following:
> 
> depmod: *** Unresolved symbols in /lib/modules/2.5.30/kernel/drivers/block/floppy.o
> depmod:         elv_queue_empty
> depmod: *** Unresolved symbols in /lib/modules/2.5.30/kernel/drivers/ide/atapi.o
> depmod:         elv_queue_empty
> depmod: *** Unresolved symbols in /lib/modules/2.5.30/kernel/drivers/ide/ide-mod.o
> depmod:         elv_queue_empty
> 
> Oh, while I'm at it: ever since the IDE cleanup started, loading one
> or more of the IDE/CD related modules for a second time after they 
> have been unloaded once already results in a pretty bad oops (total
> lockup). Took me quite a while to narrow this down. 2.5.29 still has 
> this problem. I was going to submit the oops for 2.5.30 if applicable, 
> but first gotta get that symbol resolved...
> 
> This is on a measly SMP P5 with limited memory which is all-SCSI 
> except for the CD drive. Hence the modules.

Yes having the oops at hand would be rather helpfull.
Unfortunately I don't have a SCSI system at hand, which makes
it a bit inconvenient too me to test ide.c compiled as module.


  reply	other threads:[~2002-08-02  9:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-01 23:27 2.5.30 unresolved symbol: elv_queue_empty Michel Eyckmans (MCE)
2002-08-02  9:38 ` Marcin Dalecki [this message]
2002-08-02 23:45   ` Michel Eyckmans (MCE)

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=3D4A5320.8070100@evision.ag \
    --to=dalecki@evision.ag \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin@dalecki.de \
    --cc=mce@pi.be \
    /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