Summary: | sys-fs/vhba-1.1.0: Kernel warning occur if cdemud start up | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Marcel Schmedes <sm> |
Component: | [OLD] Core system | Assignee: | 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
Created attachment 161465 [details]
Warning and stack trace of kernel with vhba and cdemud started
I can confirm this, but for kernel 2.6.27. For earlier versions (<=2.6.26.6) everything works fine. 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 ?
I missed one line in the attachment: WARNING: at kernel/softirq.c:136 local_bh_enable_ip+0x78/0xa0() And as for comment 3, the part about bug description was made while I was not fully awake. 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. 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. |