linux-avmb1:avm B1 ISA (b1isa) & linux-2.6.8-rc2
tristate
tristate at gmx.net
Mon Aug 2 13:50:02 CEST 2004
Hallo Liste,
Ich habe nach langem überlegen nun auf den 2.6er kernel gewechselt...
Leider musste ich festellen das meine alte AVM B1 ISA karte nicht mehr
möchte :-/
Ich habe mir Fedora Core 2 installiert. In der Original konfiguration
Lief hier nichts. Ein 'Capiinit start' brachte jedenfalls nur den
Fehler: ERROR: cannot load module kernelcapi. Nach dem compilieren von
capi4k-utils-2004-06-14.tar.gz funktionierte 'capiinit start' bedingt:
Aug 2 13:32:27 server kernel: CAPI Subsystem Rev 1.1.2.8
Aug 2 13:32:27 server kernel: capifs: Rev 1.1.2.3
Aug 2 13:32:31 server kernel: capi20: Rev 1.1.2.7: started up with major 68
(middleware+capifs)
Aug 2 13:32:31 server kernel: b1: revision 1.1.2.2
Aug 2 13:32:31 server kernel: b1isa: revision 1.1.2.3
Aug 2 13:32:31 server kernel: kcapi: Controller 1: b1isa-150 attached
Aug 2 13:32:31 server kernel: b1isa: AVM B1 ISA at i/o 0x150, irq 7,
revision 255
Aug 2 13:32:31 server kernel: b1isa-150: card 1 "B1" ready.
Aug 2 13:32:31 server kernel: b1isa-150: card 1 Protocol: DSS1
Aug 2 13:32:31 server kernel: b1isa-150: card 1 Linetype: point to point
Aug 2 13:32:31 server kernel: b1isa-150: B1-card (3.11-03) now active
Aug 2 13:32:31 server kernel: Debug: sleeping function called from invalid
context at include/asm/semaphore.h:119
Aug 2 13:32:31 server kernel: in_atomic():1, irqs_disabled():0
Aug 2 13:32:31 server kernel: [<c011757f>] __might_sleep+0x9f/0xb0
Aug 2 13:32:31 server kernel: [<d49d24e9>] capi_ctr_ready+0x29/0xe0
[kernelcapi]
Aug 2 13:32:31 server kernel: [<c0119a60>] printk+0xf0/0x130
Aug 2 13:32:31 server kernel: [<d49588e2>] b1_interrupt+0xcd2/0x19b0 [b1]
Aug 2 13:32:31 server kernel: [<c0200bb4>] end_that_request_last+0x54/0xc0
Aug 2 13:32:31 server kernel: [<c01164fb>] scheduler_tick+0x1b/0x410
Aug 2 13:32:31 server kernel: [<c0107580>] handle_IRQ_event+0x30/0x60
Aug 2 13:32:31 server kernel: [<c010784f>] do_IRQ+0x7f/0x110
Aug 2 13:32:31 server kernel: [<c0105f5c>] common_interrupt+0x18/0x20
Aug 2 13:32:31 server kernel: [<c0104053>] default_idle+0x23/0x40
Aug 2 13:32:31 server kernel: [<c0112629>] apm_cpu_idle+0x79/0x150
Aug 2 13:32:31 server kernel: [<c01040e4>] cpu_idle+0x34/0x40
Aug 2 13:32:31 server kernel: [<c0342707>] start_kernel+0x167/0x1b0
Aug 2 13:32:31 server kernel: [<c0342330>] unknown_bootoption+0x0/0x160
Aug 2 13:32:32 server kernel: kcapi: card 1 "b1isa-150" ready.
----
soweit so gut... was hat das mit in_atomic() zu tun?
Nun...
capiinit stop
Speicherzugriffsfehler
/var/log/messages
Aug 2 13:40:21 server kernel: kcapi: card 1 down.
Aug 2 13:40:21 server kernel: Unable to handle kernel paging request at
virtual address d49465e0
Aug 2 13:40:21 server kernel: printing eip:
Aug 2 13:40:21 server kernel: d49465e0
Aug 2 13:40:21 server kernel: *pde = 0139d067
Aug 2 13:40:21 server kernel: Oops: 0000 [#1]
Aug 2 13:40:21 server kernel: Modules linked in: capi capifs kernelcapi
parport_pc lp parport autofs4 eeprom lm78 i2c_sensor i2c_isa i2c_piix4
i2c_core sunrpc ipt_TOS ipt_MASQUERADE ipt_LOG ipt_TCPMSS ipt_tos
iptable_mangle ip_nat_ftp iptable_nat ipt_tcpmss iptable_filter
ipt_multiport ip_conntrack_ftp ipt_state ip_conntrack ipt_limit ip_tables
ipv6 n_hdlc ppp_synctty ppp_async crc_ccitt ppp_generic slhc e100 mii 3c59x
microcode uhci_hcd ext3 jbd
Aug 2 13:40:21 server kernel: CPU: 0
Aug 2 13:40:21 server kernel: EIP: 0060:[<d49465e0>] Not tainted
Aug 2 13:40:21 server kernel: EFLAGS: 00010282 (2.6.8-rc2)
Aug 2 13:40:21 server kernel: EIP is at 0xd49465e0
Aug 2 13:40:21 server kernel: eax: d23f2cc8 ebx: d23f2cc8 ecx: d49d97c0
edx: d49465e0
Aug 2 13:40:21 server kernel: esi: d49d5c32 edi: d37584a0 ebp: cdceb304
esp: cc319f28
Aug 2 13:40:21 server kernel: ds: 007b es: 007b ss: 0068
Aug 2 13:40:21 server kernel: Process capiinit (pid: 2905,
threadinfo=cc318000 task=ccd1d380)
Aug 2 13:40:21 server kernel: Stack: d49d4cf9 cd3391a0 ccc5875c 00000246
000000d0 d37584a0 cdceb304 00000246
Aug 2 13:40:21 server kernel: d49da060 d37584a0 d49da060 c016638a
d37584b8 00000000 00000400 40000000
Aug 2 13:40:21 server kernel: 00000001 00000000 00000000 00000000
d49d97e0 cdceb2e0 00000400 cdceb304
Aug 2 13:40:21 server kernel: Call Trace:
Aug 2 13:40:21 server kernel: [<d49d4cf9>] controller_show+0x79/0x80
[kernelcapi]
Aug 2 13:40:21 server kernel: [<c016638a>] seq_read+0xfa/0x2a0
Aug 2 13:40:21 server kernel: [<c014bc01>] vfs_read+0xd1/0x120
Aug 2 13:40:21 server kernel: [<c014be48>] sys_read+0x38/0x60
Aug 2 13:40:21 server kernel: [<c0105d9d>] sysenter_past_esp+0x52/0x71
Aug 2 13:40:21 server kernel: Code: Bad EIP value.
....
Md5sum /usr/lib/isdn/b1.t4
e9102699ccae9c1d170929c3178e5603 /usr/lib/isdn/b1.t4
cat /proc/capi/driver
b1isa 1.1.2.3
cat /proc/capi/controller
1 b1isa running b1isa-150 B1 3.11-03 0x150 7 r255
Kann mir jemand helfen?
-Jens
More information about the linux-avmb1
mailing list