Intriguing about the broadcom driver relationship. I find humor in the brcm log entries:
[ 15.290813] brcm80211: module is from the staging directory, the quality is unknown, you have been warned. Anyway here is the first error encountered by your system: [ 37.785729] ------------[ cut here ]------------ [ 37.785765] WARNING: at /build/buildd/linux-2.6.38/net/mac80211/rx.c:2881 ieee80211_rx+0x8a/0x190 [mac80211]() [ 37.785770] Hardware name: Latitude E4310 [ 37.785772] Modules linked in: aesni_intel cryptd aes_i586 aes_generic usb_storage uas cdc_acm binfmt_misc rfcomm sco bnep l2cap vboxnetadp vboxnetflt vboxdrv dm_crypt wl(P) snd_hda_codec_hdmi snd_hda_codec_idt lib80211 arc4 snd_hda_intel snd_hda_codec btusb snd_hwdep bluetooth snd_pcm ppdev dell_wmi sparse_keymap snd_seq_midi snd_rawmidi brcm80211(C) snd_seq_midi_event snd_seq snd_timer dell_laptop dcdbas psmouse snd_seq_device mac80211 serio_raw intel_ips snd cfg80211 soundcore snd_page_alloc parport_pc lp parport usbhid hid mmc_block i915 drm_kms_helper ahci libahci sdhci_pci sdhci drm e1000e i2c_algo_bit video [ 37.785841] Pid: 0, comm: swapper Tainted: P C 2.6.38-8-generic-pae #42-Ubuntu [ 37.785844] Call Trace: [ 37.785858] [<c1058ce2>] ? warn_slowpath_common+0x72/0xa0 [ 37.785871] [<f98d2f4a>] ? ieee80211_rx+0x8a/0x190 [mac80211] [ 37.785880] [<f98d2f4a>] ? ieee80211_rx+0x8a/0x190 [mac80211] [ 37.785882] [<c1058d32>] ? warn_slowpath_null+0x22/0x30 [ 37.785890] [<f98d2f4a>] ? ieee80211_rx+0x8a/0x190 [mac80211] [ 37.785895] [<c144be60>] ? skb_dequeue+0x50/0x70 [ 37.785901] [<f98bbabf>] ? ieee80211_tasklet_handler+0xaf/0xc0 [mac80211] [ 37.785908] [<c1531756>] ? _raw_spin_unlock_bh+0x16/0x20 [ 37.785924] [<f99e08d8>] ? wl_dpc+0x58/0xb0 [brcm80211] [ 37.785928] [<c105f2b5>] ? tasklet_action+0x55/0xe0 [ 37.785930] [<c105f9f2>] ? __do_softirq+0x82/0x170 [ 37.785932] [<c105f970>] ? __do_softirq+0x0/0x170 [ 37.785933] <IRQ> [<c105fbbd>] ? irq_exit+0x6d/0x80 [ 37.785937] [<c153895b>] ? do_IRQ+0x4b/0xc0 [ 37.785940] [<c107b579>] ? hrtimer_get_next_event+0x119/0x130 [ 37.785943] [<c100b0f0>] ? common_interrupt+0x30/0x38 [ 37.785946] [<c105007b>] ? proc_sched_show_task+0x14b/0x1ac0 [ 37.785951] [<c12cfeb8>] ? intel_idle+0xb8/0x110 [ 37.785955] [<c142fa5d>] ? cpuidle_idle_call+0x7d/0x160 [ 37.785957] [<c100944a>] ? cpu_idle+0x8a/0xc0 [ 37.785961] [<c10420fe>] ? complete+0x4e/0x60 [ 37.785966] [<c151730d>] ? rest_init+0x5d/0x70 [ 37.785970] [<c17c47f2>] ? start_kernel+0x35f/0x366 [ 37.785972] [<c17c43e6>] ? pass_all_bootoptions+0x0/0xa [ 37.785974] [<c17c40f1>] ? i386_start_kernel+0xe0/0xe8 [ 37.785976] ---[ end trace d29e767697ec0596 ]--- [ 38.781611] ------------[ cut here ]------------ I'm not really familiar with wireless network kernel driver debugging but it looks like this is something in the wireless stack. There follows a bunch of other kernel errors in the logs. The X fault may simply be a side effect of your system being in such an inconsistent state after the wireless failure. ** Summary changed: - [arrandale] GPU lockup (ESR: 0x00000001 IPEHR: 0x08914160) + [arrandale] GPU lockup (ESR: 0x00000001 IPEHR: 0x08914160) - broadcomm wireless conflict? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/765432 Title: [arrandale] GPU lockup (ESR: 0x00000001 IPEHR: 0x08914160) - broadcomm wireless conflict? -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
