Hide Forgot
abrt version: 2.0.3 architecture: i686 cmdline: ro root=/dev/mapper/vg_gio-lv_root rd_LVM_LV=vg_gio/lv_root rd_LVM_LV=vg_gio/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_GB.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet comment: network manager makes the plasma desktop to crash every time I try to enable (and to connect) to the wifi component: kernel kernel: 2.6.38.8-32.fc15.i686 kernel_tainted: 2048 kernel_tainted_long: Working around severe firmware bug. os_release: Fedora release 15 (Lovelock) package: kernel reason: WARNING: at drivers/pci/dmar.c:634 warn_invalid_dmar+0x85/0x94() time: Mon Jun 27 12:03:52 2011 backtrace: :WARNING: at drivers/pci/dmar.c:634 warn_invalid_dmar+0x85/0x94() :Hardware name: Aspire 3810T :Your BIOS is broken; DMAR reported at address 0! :BIOS vendor: Acer; Ver: V1.07; Product Version: V1.07 :Modules linked in: :Pid: 0, comm: swapper Not tainted 2.6.38.8-32.fc15.i686 #1 :Call Trace: : [<c043aad9>] warn_slowpath_common+0x7c/0x91 : [<c05f1d9a>] ? warn_invalid_dmar+0x85/0x94 : [<c05f1d9a>] ? warn_invalid_dmar+0x85/0x94 : [<c043ab44>] warn_slowpath_fmt_taint+0x32/0x34 : [<c05f1d9a>] warn_invalid_dmar+0x85/0x94 : [<c0a82094>] check_zero_address+0xee/0x124 : [<c062a9a5>] ? acpi_get_table_with_size+0x59/0xb3 : [<c0a820dc>] detect_intel_iommu+0x12/0x78 : [<c0a5f21e>] pci_iommu_alloc+0x35/0x5a : [<c0a6a57a>] mem_init+0xe/0x275 : [<c0a734a7>] ? __alloc_bootmem_node_nopanic+0x72/0x99 : [<c07ced36>] ? printk+0x2d/0x2f : [<c0a778ba>] ? page_cgroup_init_flatmem+0xaa/0xd8 : [<c0a5966e>] start_kernel+0x1af/0x35d : [<c0a5920c>] ? unknown_bootoption+0x0/0x19e : [<c0a590d6>] i386_start_kernel+0xd6/0xdc
Package: kernel Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- Every time network manager try to use the wireless, the plasma desktop crash
Package: kernel Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- Wlan crashed the plasma-desktop
the kernel message says it all.. "Your BIOS is broken" There's nothing we can do about that. Look for a BIOS update maybe. This is unlikely to have anything to do with plasma crashing. That sounds like either a problem with network manager, or plasma.