Bugzilla – Bug 116387
Neomagic 256AV integrated audio card in Dell laptop block at configuration : system crash
Last modified: 2006-04-19 14:12:29 UTC
The laptop crash at audio card configuration (Yast2). Thanks to fix this bug :) INFO : version of OpenSuse : super-openSUSE-RC1-20050911-standard-kde.iso Hardware : Dell Latitude Cpi A laptop (P2 366Mhz) audio card : integrated Neomagic MagicMedia 256AV Audio normal alsa audio driver : nm256 Here the output of lspci -v : ======================== 00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03) Flags: bus master, medium devsel, latency 32 Memory at f4000000 (32-bit, prefetchable) [size=64M] Capabilities: [a0] AGP version 1.0 00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03) (prog-if 00 [Normal decode]) Flags: bus master, 66MHz, medium devsel, latency 32 Bus: primary=00, secondary=01, subordinate=01, sec-latency=32 I/O behind bridge: 0000c000-0000cfff Memory behind bridge: fd000000-feffffff Prefetchable memory behind bridge: f8000000-f9ffffff 00:03.0 CardBus bridge: Texas Instruments PCI1225 (rev 01) Subsystem: Dell Latitude CPi A400XT Flags: bus master, medium devsel, latency 168, IRQ 11 Memory at 10100000 (32-bit, non-prefetchable) [size=4K] Bus: primary=00, secondary=02, subordinate=05, sec-latency=176 Memory window 0: 12000000-13fff000 (prefetchable) Memory window 1: 14000000-15fff000 I/O window 0: 00001000-000010ff I/O window 1: 00001400-000014ff 16-bit legacy interface ports at 0001 00:03.1 CardBus bridge: Texas Instruments PCI1225 (rev 01) Subsystem: Dell Latitude CPi A400XT Flags: bus master, medium devsel, latency 168, IRQ 11 Memory at 10101000 (32-bit, non-prefetchable) [size=4K] Bus: primary=00, secondary=06, subordinate=09, sec-latency=176 Memory window 0: 16000000-17fff000 (prefetchable) Memory window 1: 18000000-19fff000 I/O window 0: 00001800-000018ff I/O window 1: 00001c00-00001cff 16-bit legacy interface ports at 0001 00:07.0 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02) Flags: bus master, medium devsel, latency 0 00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01) (prog-if 80 [Master]) Flags: bus master, medium devsel, latency 32 I/O ports at 0860 [size=16] 00:07.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01) (prog-if 00 [UHCI]) Flags: bus master, medium devsel, latency 32, IRQ 11 I/O ports at ece0 [size=32] 00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02) Flags: medium devsel, IRQ 9 01:00.0 VGA compatible controller: Neomagic Corporation NM2200 [MagicGraph 256AV] (rev 12) (prog-if 00 [VGA]) Subsystem: Dell Latitude CPi A Flags: bus master, medium devsel, latency 32, IRQ 11 Memory at f9000000 (32-bit, prefetchable) [size=16M] Memory at fdc00000 (32-bit, non-prefetchable) [size=4M] Memory at fdb00000 (32-bit, non-prefetchable) [size=1M] Capabilities: [dc] Power Management version 1 01:00.1 Multimedia audio controller: Neomagic Corporation NM2200 [MagicMedia 256AV Audio] (rev 12) Subsystem: Dell Latitude CPi A Flags: medium devsel, IRQ 5 Memory at f8c00000 (32-bit, prefetchable) [disabled] [size=4M] Memory at fda00000 (32-bit, non-prefetchable) [disabled] [size=1M] Capabilities: [dc] Power Management version 1 ========================
can you get the oops text in some way?
Also please be more verbose. When exactly does your system crash and how does it crash? Does it happen within YaST or after the sound-driver is loaded (does YaST crash itself)? Also attach the YaST-logs (http://http://www.opensuse.org/Bug_Reporting_FAQ#YaST). The oops should be retrievable by the system log, so please attach the last 500 lines after the error occoured: tail -500 /var/log/messages > messages.txt
Created attachment 49668 [details] messages.txt
Created attachment 49669 [details] Yast 2 logs
Takashi, it seems that the problem is in ALSA. FYI Yast uses this config: [$["bus":"pci", "bus_id":"0000:01:00.1", "model":"Latitude CPi A", "module":"snd-nm256", "options":$["force_ac97":"0", "use_cache":"0", "vaio_hack":"0"], "unique_key":"NXNs.u5BP_nU6GR9"]]
Yes, it's a known bug. But it's hopelessly hard to debug this chipset. We have no hardware around here and no datasheet at all. The existing driver was a result of ugly reverse engineering.
Could you try 10.0 update kernel? This might be fixed with that.
The problem is fixed with 10.1 kernel.