OM2008.9 kernel mutex problems

Vasco Névoa vasco.nevoa at sapo.pt
Fri Oct 31 16:51:03 CET 2008


Hi.
I've noticed that the stable kernel throws up a lot of exceptions upon  
resume related to mutexes.
I've also noticed that the latest testing kernel seems to have no  
mutex or spinlock support (or something like that), because some of  
the modules refuse to load. So I presume someone is working on this  
problem and has disabled the mutex mechanisms to eliminate it....
For example, ipv6 and ppp_generic complain about these:
ppp_generic: Unknown symbol _spin_lock_bh
ppp_generic: Unknown symbol _spin_unlock_bh
ppp_generic: Unknown symbol mutex_lock_nested
ppp_generic: Unknown symbol _read_unlock_bh
ppp_generic: Unknown symbol _spin_unlock
ppp_generic: Unknown symbol _write_lock_bh
ppp_generic: Unknown symbol _read_lock_bh
ppp_generic: Unknown symbol __spin_lock_init
ppp_generic: Unknown symbol __rwlock_init
ppp_generic: Unknown symbol _spin_lock
ppp_generic: Unknown symbol _write_unlock_bh
ppp_generic: Unknown symbol _spin_lock_bh
ppp_generic: Unknown symbol _spin_unlock_bh
ppp_generic: Unknown symbol mutex_lock_nested
ppp_generic: Unknown symbol _read_unlock_bh
ppp_generic: Unknown symbol _spin_unlock
ppp_generic: Unknown symbol _write_lock_bh
ppp_generic: Unknown symbol _read_lock_bh
ppp_generic: Unknown symbol __spin_lock_init
ppp_generic: Unknown symbol __rwlock_init
ppp_generic: Unknown symbol _spin_lock
ppp_generic: Unknown symbol _write_unlock_bh
ipv6: Unknown symbol _spin_lock_bh
ipv6: Unknown symbol lockdep_init_map
ipv6: Unknown symbol _spin_unlock_bh
ipv6: Unknown symbol _read_unlock
ipv6: Unknown symbol _write_unlock
ipv6: Unknown symbol _read_unlock_bh
ipv6: Unknown symbol _write_lock
ipv6: Unknown symbol _spin_unlock
ipv6: Unknown symbol _spin_lock_nested
ipv6: Unknown symbol _write_lock_bh
ipv6: Unknown symbol _read_lock_bh
ipv6: Unknown symbol lock_acquire

I'd like to know what is going on. I can't find any concrete ticket in  
trac. Can anyone point me to one, or otherwise clarify what exactly is  
being done to debug the original mutex problem, and why some of the  
modules are broken like this?

Thanks,
Vasco.



More information about the devel mailing list