2.6.2-mm1 seems to break ALSA and DRI module compilation

From: Robert F Merrill
Date: Sat Feb 07 2004 - 20:22:09 EST


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.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/