public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Dave Jones <davej@redhat.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: unresolved emu10k1 synth symbols.
Date: Tue, 21 Mar 2006 12:04:35 +0100	[thread overview]
Message-ID: <s5hoe0083ek.wl%tiwai@suse.de> (raw)
In-Reply-To: <20060321054634.GA5122@redhat.com>

At Tue, 21 Mar 2006 00:46:34 -0500,
Dave Jones wrote:
> 
> I just noticed this whilst booting 2.6.16 on a test box
> 
> snd_emu10k1_synth: Unknown symbol snd_emu10k1_ptr_read
> snd_emu10k1_synth: Unknown symbol snd_emu10k1_synth_copy_from_user
> snd_emu10k1_synth: Unknown symbol snd_emu10k1_voice_free
> snd_emu10k1_synth: Unknown symbol snd_emu10k1_synth_free
> snd_emu10k1_synth: Unknown symbol snd_emu10k1_ptr_write
> snd_emu10k1_synth: Unknown symbol snd_emu10k1_synth_bzero
> snd_emu10k1_synth: Unknown symbol snd_emu10k1_voice_alloc
> snd_emu10k1_synth: Unknown symbol snd_emu10k1_memblk_map
> snd_emu10k1_synth: Unknown symbol snd_emu10k1_synth_alloc
> 
> This kernel was configured with CONFIG_SND_EMU10K1=m
> and CONFIG_SND_SEQUENCER=m
> 
> This looks like it can't possibly work, unless I change
> CONFIG_SND_EMU10K1 to =y.  Is exporting a symbol from one
> module to another actually supposed to work?
> I thought this was why we had the ill-fated intermodule_register() ?.

Weird.  By modprobe, snd-emu10k1 module should be loaded in prior to 
snd-emu10k1-synth because of the dependency of above symbols.

How is snd-emu10k1-synth module loaded?


Takashi

  parent reply	other threads:[~2006-03-21 11:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-21  5:46 unresolved emu10k1 synth symbols Dave Jones
2006-03-21 10:53 ` Adrian Bunk
2006-03-21 11:04 ` Takashi Iwai [this message]
2006-03-21 18:09   ` Dave Jones
2006-03-22 14:16     ` Takashi Iwai
2006-03-22 17:54       ` Dave Jones
2006-03-23 10:46         ` Takashi Iwai
  -- strict thread matches above, loose matches on Subject: below --
2006-03-23 19:36 Margit Schubert-While

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=s5hoe0083ek.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=davej@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