From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-DE; rv:1.7.10) Gecko/20050717 Firefox/1.0.6

Description of problem:
After loading firmware into AVM B1 controller, strange messages are shown in kernel log.

Note that ISDN is working afterwards.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Put AVM B1 ISDN card into system
2. Fix non-working udev with workaround from https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=139321
3. Load capi modules
# modprobe capidrv
# modprobe capi
4. Load firmware
# /sbin/avmcapictrl load /etc/firmware/isdn/b1.t4 1
Loading Bootcode /etc/firmware/isdn/b1.t4 ... done


  

Actual Results:  dmesg:

capidrv: Rev 1.1.2.2: loaded
SELinux: initialized (dev capifs, type capifs), not configured for labeling
capifs: Rev 1.1.2.3
capi20: Rev 1.1.2.7: started up with major 68 (middleware+capifs)
b1pci-d800: card 1 "B1" ready.
b1pci-d800: card 1 Protocol: DSS1
b1pci-d800: card 1 Linetype: point to multipoint
b1pci-d800: B1-card (3.10-02) now active
Debug: sleeping function called from invalid context at include/asm/semaphore.h:107
in_atomic():1[expected: 0], irqs_disabled():0
 [<c011d89c>] __might_sleep+0x7d/0x89
 [<e08e0427>] capi_ctr_ready+0x24/0xad [kernelcapi]
 [<e08c74ed>] b1_interrupt+0x67c/0x882 [b1]
 [<c0107df7>] handle_IRQ_event+0x25/0x4f
 [<c0108731>] do_IRQ+0x11c/0x242
 [<c0303838>] common_interrupt+0x18/0x20
 [<c010403b>] default_idle+0x23/0x26
 [<c010408c>] cpu_idle+0x1f/0x34
 [<c03a96b4>] start_kernel+0x20f/0x211
bad: scheduling while atomic!
 [<c03011d5>] schedule+0x2d/0x552
 [<c0106539>] dump_stack+0x11/0x13
 [<c011d89c>] __might_sleep+0x7d/0x89
 [<e08e042c>] capi_ctr_ready+0x29/0xad [kernelcapi]
 [<e08c74ed>] b1_interrupt+0x67c/0x882 [b1]
 [<c0107df7>] handle_IRQ_event+0x25/0x4f
 [<c0108731>] do_IRQ+0x11c/0x242
 [<c0303838>] common_interrupt+0x18/0x20
 [<c010403b>] default_idle+0x23/0x26
 [<c010408c>] cpu_idle+0x1f/0x34
 [<c03a96b4>] start_kernel+0x20f/0x211
kcapi: card 1 "b1pci-d800" ready.
capidrv: controller 1 up
capidrv-1: now up (2 B channels)
capidrv-1: D2 trace enabled

Expected Results:  Not such strange messages

Additional info:

Tested also without SELinux and APM instead of ACPI, same strange messages.