PDA

Archiv verlassen und diese Seite im Standarddesign anzeigen : Audigy 2 ZS PCMCIA - PC hängt wenn eingesteckt



linuckser
25.12.07, 20:55
Wenn ich meine Creative Audigy 2 ZS in den PCMCIA Slot stecke bleibt Fedora 8 einfach stehen, sobald ich sie rausnehme läuft das System wieder.
Wenn ich sie bereits vor dem Booten in den Slot stecke bleibt das System beim booten hängen und erst wenn ich die Karte rausnehme bricht der Bootvorgang mit einer Fehlermeldung ab.

Im Betrieb steht im Terminal, dann folgendes:



Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: Oops: 0000 [#1] SMP

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: EIP: 0060:[<f03013c1>] Not tainted VLI

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: EFLAGS: 00010086 (2.6.23.9-85.fc8 #1)

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<f02e107f>] snd_emux_free+0x53/0x86 [snd_emux_synth]

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<f02d6137>] snd_emu10k1_synth_new_device+0xf3/0x138 [snd_emu10k1_synth]

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<c061e15b>] mutex_lock+0x1a/0x29

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<f024837d>] snd_seq_device_dev_register+0x29/0x35 [snd_seq_device]

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: EIP is at snd_emu10k1_ptr_write+0x9/0xaa [snd_emu10k1]

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: Process pccardd (pid: 392, ti=ef66a000 task=ef3fa610 task.ti=ef66a000)

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: ee175000 f02e2432 ea23ea00 00000286 f02e107f ee175694 c7e74000 ee175600

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: Call Trace:

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: CPU: 0

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: esi: 00000000 edi: 00000000 ebp: 00000000 esp: ef66acd4

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: eax: 00000000 ebx: e8768000 ecx: 00000000 edx: 00000019

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<f02e180f>] snd_emux_terminate_all+0x45/0x7e [snd_emux_synth]

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<f02d65ed>] free_voice+0x23/0x83 [snd_emu10k1_synth]

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<f02e2432>] snd_emux_detach_seq+0xf/0x3e [snd_emux_synth]

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<f02480e9>] init_device+0x4d/0x82 [snd_seq_device]

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<f024825a>] find_driver+0xc9/0xcf [snd_seq_device]

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: ds: 007b es: 007b fs: 00d8 gs: 0000 ss: 0068

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: Stack: ea23ea00 ef66ad14 e8768000 00000000 00000000 00000000 f02d65ed 0000ff00

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: ea23ea00 e8768000 f02e180f ea23ea7c 00000286 ea23ea00 00000286 ea23ea7c

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<f01cfabd>] snd_device_register_all+0x20/0x42 [snd]

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<f01cc81a>] snd_card_register+0xe/0x20c [snd]

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<f01f173b>] snd_hwdep_new+0xa7/0xb5 [snd_hwdep]

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<f02e1162>] snd_emux_register+0xb0/0xfb [snd_emux_synth]

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<f02e2f1e>] snd_emux_init_hwdep+0x8a/0x9a [snd_emux_synth]

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<f02fb3bd>] snd_card_emu10k1_probe+0x2f8/0x31f [snd_emu10k1]

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<c061cf41>] klist_next+0x4b/0x6c

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<c0566f93>] driver_probe_device+0xea/0x168

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<c0567011>] __device_attach+0x0/0x5

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<f02d612a>] snd_emu10k1_synth_new_device+0xe6/0x138 [snd_emu10k1_synth]

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<c061e15b>] mutex_lock+0x1a/0x29

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<c05670a3>] device_attach+0x72/0x86

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<c0567011>] __device_attach+0x0/0x5

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<c05003cb>] pci_device_probe+0x36/0x57

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<c05666e1>] bus_add_device+0xd0/0x10b

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<c05653aa>] device_add+0x301/0x51a

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<f02e1000>] sf_sample_new+0x0/0x1e [snd_emux_synth]

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<c0566412>] bus_for_each_drv+0x39/0x60

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<c04fba13>] pci_bus_add_device+0xc/0x4b

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<c04fba6a>] pci_bus_add_devices+0x18/0xfa

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<c056fe1b>] cb_alloc+0x97/0xa9

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<c0566383>] bus_attach_device+0x26/0x7c

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<c056cf9c>] socket_insert+0xb6/0xdc

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<c056d459>] pccardd+0x14e/0x1f7

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<f02e101e>] sf_sample_free+0x0/0x8 [snd_emux_synth]

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<c0427c6f>] default_wake_function+0x0/0xc

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<c043d396>] kthread+0x0/0x5e

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<f02480e9>] init_device+0x4d/0x82 [snd_seq_device]

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<c043d3ce>] kthread+0x38/0x5e

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<c0405dbb>] kernel_thread_helper+0x7/0x10

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<c056d30b>] pccardd+0x0/0x1f7

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: =======================

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<f024825a>] find_driver+0xc9/0xcf [snd_seq_device]

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<f01cfabd>] snd_device_register_all+0x20/0x42 [snd]

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<f024837d>] snd_seq_device_dev_register+0x29/0x35 [snd_seq_device]

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: Code: d9 31 d0 8b 53 04 89 c1 89 f0 ef 83 c2 04 ed 89 c6 89 ca 89 e8 e8 5f da 31 d0 5b 89 f0 5b 5e 5f 5d c3 55 89 c5 57 56 53 83 ec 08 <83> 78 10 01 8b 7c 24 1c 19 c0 83 e1 3f 25 00 00 00 f8 8d b0 00

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: [<f01cc81a>] snd_card_register+0xe/0x20c [snd]

Message from syslogd@sascha at Dec 25 21:51:00 ...
kernel: EIP: [<f03013c1>] snd_emu10k1_ptr_write+0x9/0xaa [snd_emu10k1] SS:ESP 0068:ef66acd4





Woran kann das liegen?

undefined
25.12.07, 21:40
Oops bedeutet das beim Kernel ein schwerwiegender fehler aufgetreten ist. Da kann dir hier keiner helfen. Halte dich an die Kernel Mailing listen.

linuckser
26.12.07, 12:36
Danke. Nach einer Suche dort habe ich herausgefunden, dass das Problem scheinbar nur in Fedora auftritt und da auch wieder in Fedora 8 scheinbar war es in Fedora 7 mal behoben und in 6 lief es ohne Fehler.
Gibt auch bereits einen Eintrack bei bugzilla von redhat, da bleibt mir dann wohl nix anderes übrig als abzuwarten.