public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert F Merrill <griever@t2n.org>
To: linux-kernel@vger.kernel.org
Subject: 2.6.2-mm1 seems to break ALSA and DRI module compilation
Date: Sat, 07 Feb 2004 20:20:34 -0500	[thread overview]
Message-ID: <40258EE2.9000507@t2n.org> (raw)

Just got 2.6.2-mm1 running... however I get a bunch of module errors
when I try to load my (seperately compiled) ALSA and DRI modules

first of all, nearly every alsa module complains about a billion 
undefined symbols
secondly, I get the error "module falsely claims to have symbol ^A".

Feb  7 20:06:00 cheyenne kernel: snd: falsely claims to have parameter ^A
Feb  7 20:06:00 cheyenne kernel: snd_ak4531_codec: Unknown symbol 
snd_ctl_add
Feb  7 20:06:00 cheyenne kernel: snd_ak4531_codec: Unknown symbol 
snd_card_proc_new
Feb  7 20:06:00 cheyenne kernel: snd_ak4531_codec: Unknown symbol 
snd_ctl_new1
Feb  7 20:06:00 cheyenne kernel: snd_ak4531_codec: Unknown symbol 
snd_component_add
Feb  7 20:06:00 cheyenne kernel: snd_ak4531_codec: Unknown symbol 
snd_iprintf
Feb  7 20:06:00 cheyenne kernel: snd_ak4531_codec: Unknown symbol 
snd_kcalloc
Feb  7 20:06:00 cheyenne kernel: snd_ak4531_codec: Unknown symbol 
snd_device_new
Feb  7 20:06:00 cheyenne kernel: snd_page_alloc: falsely claims to have 
parameter ^A


I also get a few errors like this...
Feb  7 20:06:00 cheyenne kernel: i_size_write() called without i_sem
Feb  7 20:06:00 cheyenne kernel: Call Trace:
Feb  7 20:06:00 cheyenne kernel:  [i_size_write_check+91/96] 
i_size_write_check+0x5b/0x60
Feb  7 20:06:00 cheyenne kernel:  [generic_commit_write+98/176] 
generic_commit_write+0x62/0xb0
Feb  7 20:06:00 cheyenne kernel:  [ext2_commit_chunk+65/144] 
ext2_commit_chunk+0x41/0x90
Feb  7 20:06:00 cheyenne kernel:  [ext2_make_empty+362/464] 
ext2_make_empty+0x16a/0x1d0
Feb  7 20:06:00 cheyenne kernel:  [ext2_get_block+0/1056] 
ext2_get_block+0x0/0x420
Feb  7 20:06:00 cheyenne kernel:  [ext2_mkdir+181/336] ext2_mkdir+0xb5/0x150
Feb  7 20:06:00 cheyenne kernel:  [vfs_mkdir+148/272] vfs_mkdir+0x94/0x110
Feb  7 20:06:00 cheyenne kernel:  [sys_mkdir+184/256] sys_mkdir+0xb8/0x100
Feb  7 20:06:00 cheyenne kernel:  [syscall_call+7/11] syscall_call+0x7/0xb
at bootup.

I'm going to go to vanilla 2.6.2 and see if that has the problem.


             reply	other threads:[~2004-02-08  1:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-08  1:20 Robert F Merrill [this message]
2004-02-08  4:12 ` 2.6.2-mm1 seems to break ALSA and DRI module compilation Robert F Merrill
2004-02-08 14:21   ` Adrian Bunk

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=40258EE2.9000507@t2n.org \
    --to=griever@t2n.org \
    --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