[Bugme-new] [Bug 336] New: KALLSYMS doesn't decode DEBUG_SPINLOCK printks
bugme-daemon at smtp.osdl.org
bugme-daemon at smtp.osdl.org
Tue Feb 11 06:48:28 PST 2003
http://bugme.osdl.org/show_bug.cgi?id=336
Summary: KALLSYMS doesn't decode DEBUG_SPINLOCK printks
Kernel Version: 2.5.59-bk4
Status: NEW
Severity: low
Owner: bugme-janitors at lists.osdl.org
Submitter: bwindle-kbt at fint.org
Distribution: Debian Testing
Hardware Environment: single x86 CPU
Software Environment:
CONFIG_KALLSYMS=y
CONFIG_DEBUG_KERNEL=y
CONFIG_DEBUG_STACKOVERFLOW=y
CONFIG_DEBUG_SLAB=y
CONFIG_DEBUG_IOVIRT=y
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_SPINLOCK_SLEEP=y
Problem Description:
When compiling with KALLSYMS and DEBUG_SPINLOCK (or maybe its
DEBUG_SPINLOCK_SLEEP), kallsyms doesn't decode the spinlock prinkts. I don't
know if this is by design or not, but it is inconsistant with kallsyms's
decoding of oops/bugs... but a very minor complaint, either way :)
Steps to reproduce:
The debug spinlock config option produces output like this:
sound/oss/ad1848.c:1410: spin_lock(sound/oss/ad1848.c:c03c8aa0) already locked
by sound/oss/ad1848.c/988
sound/oss/ad1848.c:219: spin_lock(sound/oss/ad1848.c:c03c8aa0) already locked
by sound/oss/ad1848.c/1410
sound/oss/ad1848.c:1435: spin_unlock(sound/oss/ad1848.c:c03c8aa0) not locked
sound/oss/ad1848.c:1010: spin_unlock(sound/oss/ad1848.c:c03c8aa0) not locked
sound/oss/ad1848.c:329: spin_lock(sound/oss/ad1848.c:c03c8aa0) already locked
by sound/oss/ad1848.c/1143
sound/oss/ad1848.c:219: spin_lock(sound/oss/ad1848.c:c03c8aa0) already locked
by sound/oss/ad1848.c/351
sound/oss/ad1848.c:367: spin_unlock(sound/oss/ad1848.c:c03c8aa0) not locked
sound/oss/ad1848.c:1187: spin_unlock(sound/oss/ad1848.c:c03c8aa0) not locked
Is it possible to get kallsyms to decode c03c8aa0?
bwindle at razor:/giant/linux$ grep c03c8aa0 System.map
c03c8aa0 d ad1848_lock
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
More information about the Bugme-new
mailing list