Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 233102

Summary: sys-fs/vhba-1.1.0: Kernel warning occur if cdemud start up
Product: Gentoo Linux Reporter: Marcel Schmedes <sm>
Component: [OLD] Core systemAssignee: Marcelo Goes (RETIRED) <vanquirius>
Status: RESOLVED FIXED    
Severity: normal CC: dev-zero, djmatic8
Priority: High    
Version: unspecified   
Hardware: x86   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: Warning and stack trace of kernel with vhba and cdemud started
stack trace with 2.6.27 (genpatches 2)

Description Marcel Schmedes 2008-07-27 12:49:26 UTC
If starting cdemud an kernel warning occur in logs, system and cdemu still work.

Reproducible: Always

Steps to Reproduce:
1. Compile module vhba-1.1.0 against running kernel
2. Load module vhba
3. start cdemud (/etc/init.d/cdemud start)

Actual Results:  
Kernel outputs warning:
WARNING: at kernel/softirq.c:139 local_bh_enable()
plus stack trace

Expected Results:  
No warning, just start cdemud.

Here the emerge --info:
Portage 2.1.4.4 (default/linux/x86/2008.0/desktop, gcc-4.1.2, glibc-2.6.1-r0, 2.6.24-tuxonice-r9 i686)
=================================================================
System uname: 2.6.24-tuxonice-r9 i686 Intel(R) Pentium(R) M processor 1.73GHz
Timestamp of tree: Sat, 26 Jul 2008 10:03:01 +0000
distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled]
ccache version 2.4 [disabled]
app-shells/bash:     3.2_p33
dev-java/java-config: 1.3.7, 2.1.6
dev-lang/python:     2.4.4-r9
dev-python/pycrypto: 2.0.1-r6
dev-util/ccache:     2.4-r7
sys-apps/baselayout: 1.12.11.1
sys-apps/sandbox:    1.2.18.1-r2
sys-devel/autoconf:  2.13, 2.61-r1
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10.1
sys-devel/binutils:  2.18-r1
sys-devel/gcc-config: 1.4.0-r4
sys-devel/libtool:   1.5.26
virtual/os-headers:  2.6.23-r3
ACCEPT_KEYWORDS="x86"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2 -mtune=pentium-m -march=pentium-m -mmmx -msse -msse2 -fomit-frame-pointer -pipe"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/config /var/lib/hsqldb"
CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/revdep-rebuild /etc/splash /etc/terminfo /etc/texmf/web2c /etc/udev/rules.d"
CXXFLAGS="-O2 -mtune=pentium-m -march=pentium-m -mmmx -msse -msse2 -fomit-frame-pointer -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="distcc distlocks metadata-transfer sandbox sfperms strict unmerge-orphans userfetch userpriv usersandbox"
GENTOO_MIRRORS="ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo"
LANG="en_US.utf8"
LC_ALL="en_US.utf8"
LDFLAGS="-Wl,-O1"
LINGUAS="de en"
MAKEOPTS="-j4"
PKGDIR="/usr/portage/packages"

As you see tuxonice-sources, if you need info about config - let me now what you need. Stack trace is attached to this bug, please note that the kernel is tainted because of nvidia module, but the warning occur the same without nvidia loaded.
cdemu System:
app-cdr/cdemu-1.0.0 app-cdr/cdemud-1.0.0 app-cdr/gcdemu-1.0.0 sys-fs/vhba-1.1.0
Comment 1 Marcel Schmedes 2008-07-27 12:53:00 UTC
Created attachment 161465 [details]
Warning and stack trace of kernel with vhba and cdemud started
Comment 2 Vlad 2008-10-10 14:36:00 UTC
I can confirm this, but for kernel 2.6.27. For earlier versions (<=2.6.26.6) everything works fine.
Comment 3 Rafał Mużyło 2008-10-23 11:00:22 UTC
Created attachment 169552 [details]
stack trace with 2.6.27 (genpatches 2)

With 2.6.27 stack trace looks bit different (at least for me).
I don't recall this happening in 2.6.26.
Maybe description of this bug should be changed,
so it refers directly to the vhba module ?
Comment 4 Rafał Mużyło 2008-10-23 11:02:10 UTC
I missed one line in the attachment:
WARNING: at kernel/softirq.c:136 local_bh_enable_ip+0x78/0xa0()
Comment 5 Rafał Mużyło 2008-10-23 11:05:04 UTC
And as for comment 3,
the part about bug description was made
while I was not fully awake.
Comment 6 Rafał Mużyło 2008-10-23 11:16:24 UTC
Strange thing is that this only happens once.
If I'll do `/etc/init.d/cdemud stop`,
at the next `/etc/init.d/cdemud start` stack trace is no printed again.
Comment 7 Tiziano Müller (RETIRED) gentoo-dev 2009-03-12 08:01:27 UTC
I did not encounter this with vhba-1.2.1.
Can you please update and test it again? I guess they fixed it by now, please reopen if the warning still shows up.