[Bug 1001625] Re: Guest clock stops after live migration on Ubuntu 12.04 hosts
Hey guys, there is a anoying bug in libvirt-migrate-qemu-machinetype. It will remove the vnc password from any changed xml. Reason: the script triggers virsh dumpxml, this command doesn't return the vnc password. virsh should be able to also return the password with virsh dumpxml domain-id --security-info, but in fact this also doesn't sent the password. Environment: ~ # virsh version Compiled against library: libvir 0.9.8 Using library: libvir 0.9.8 Using API: QEMU 0.9.8 Running hypervisor: QEMU 1.0.0 ~ # dpkg-query -W $version qemu-kvm libvirt-bin libvirt-bin 0.9.8-2ubuntu17.18 qemu-kvm1.0+noroms-0ubuntu14.14 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1001625 Title: Guest clock stops after live migration on Ubuntu 12.04 hosts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1001625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 746114] Re: FreeBSD freeze during boot when running in Qemu KVM on AMD and Intel
I tried 3.2.0-27-generic and 3.11.0-18-generic from the precise repos. Also a vanilla 3.10.18 and 3.10.28 based on the 3.2.0-27-generic config file. I tried these ubuntu packages for qemu: saucy (1.5.0+dfsg- 3ubuntu5.3) and trusty (1.7.0+dfsg-3ubuntu5). Also the plain qemu from http://wiki.qemu-project.org/download/qemu-1.5.3.tar.bz2 I debugged this issue further. I got the freebsd Images from a friend. They are modified with MSFBSD(http://mfsbsd.vx.sk/). Plain FreeBSD is also working fine (sorry for the wrong information in the above messages). I notifed the responsible developer Martin Matuška and waiting for his reply. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/746114 Title: FreeBSD freeze during boot when running in Qemu KVM on AMD and Intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/746114/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 746114] Re: FreeBSD freeze during boot when running in Qemu KVM on AMD and Intel
I tried 3.2.0-27-generic and 3.11.0-18-generic from the precise repos. Also a vanilla 3.10.18 and 3.10.28 based on the 3.2.0-27-generic config file. I tried these ubuntu packages for qemu: saucy (1.5.0+dfsg- 3ubuntu5.3) and trusty (1.7.0+dfsg-3ubuntu5). Also the plain qemu from http://wiki.qemu-project.org/download/qemu-1.5.3.tar.bz2 I debugged this issue further. I got the freebsd Images from a friend. They are modified with MSFBSD(http://mfsbsd.vx.sk/). Plain FreeBSD is also working fine (sorry for the wrong information in the above messages). I notifed the responsible developer Martin Matuška and waiting for his reply. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/746114 Title: FreeBSD freeze during boot when running in Qemu KVM on AMD and Intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/746114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 746114] Re: FreeBSD freeze during boot when running in Qemu KVM on AMD and Intel
Hi Serge, You should be able to reproduce this with any iso from http://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/ISO-IMAGES/10.0/ Let me know if you need more information. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/746114 Title: FreeBSD freeze during boot when running in Qemu KVM on AMD and Intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/746114/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 746114] Re: FreeBSD freeze during boot when running in Qemu KVM on AMD and Intel
Hi Serge, You should be able to reproduce this with any iso from http://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/ISO-IMAGES/10.0/ Let me know if you need more information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/746114 Title: FreeBSD freeze during boot when running in Qemu KVM on AMD and Intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/746114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 746114] Re: FreeBSD freeze during boot when running in Qemu KVM on AMD and Intel
This happens also with vanilla kernel, so its more an qemu-kvm bug then kernel related ** Package changed: linux (Ubuntu) = qemu-kvm (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/746114 Title: FreeBSD freeze during boot when running in Qemu KVM on AMD and Intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/746114/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 746114] Re: FreeBSD freeze during boot when running in Qemu KVM on AMD and Intel
Tested this with vanilla Qemu 1.7.1 and 1.5. I have no issues with these vanilla versions. the bug seems to be ubuntu related -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/746114 Title: FreeBSD freeze during boot when running in Qemu KVM on AMD and Intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 746114] Re: FreeBSD freeze during boot when running in Qemu KVM on AMD and Intel
This happens also with vanilla kernel, so its more an qemu-kvm bug then kernel related ** Package changed: linux (Ubuntu) = qemu-kvm (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/746114 Title: FreeBSD freeze during boot when running in Qemu KVM on AMD and Intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/746114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 746114] Re: FreeBSD freeze during boot when running in Qemu KVM on AMD and Intel
Hi, could anybody offer me some ideas for debugging. Or has anybody some thoughts about this issue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/746114 Title: FreeBSD freeze during boot when running in Qemu KVM on AMD and Intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 746114] Re: FreeBSD freeze during boot when running in Qemu KVM on AMD and Intel
** Summary changed: - FreeBSD freeze when running in Qemu KVM on AMD + FreeBSD freeze during boot when running in Qemu KVM on AMD and Intel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/746114 Title: FreeBSD freeze during boot when running in Qemu KVM on AMD and Intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 746114] Re: FreeBSD freeze when running in Qemu KVM on AMD
Hey Guys, I ran into the same bug as Gijs Peskens did. My FreeBSD virtual maschines are freezing at the boot menu if the beastie logo is enabled and if I use a qemu version from saucy (1.5.0+dfsg-3ubuntu5.3) or trusty (1.7.0+dfsg-3ubuntu5). Version 1.2.0+noroms-0ubuntu2.12.10.6 and 1.0 +noroms-0ubuntu14.13 from quantal/precise are working fine. I've no control of the virtual maschines, only the host system so I can't modify the /boot/loader.conf. Any thoughts on how I can fix this issue on the server side? Let my know if you need any logs or more information- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/746114 Title: FreeBSD freeze when running in Qemu KVM on AMD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 746114] Re: FreeBSD freeze when running in Qemu KVM on AMD
Forgot to mention: I've tested this on two different CPUs: model name : Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz model name : Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz so this isn't only AMD related. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/746114 Title: FreeBSD freeze when running in Qemu KVM on AMD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070690] Re: BUG: unable to handle kernel NULL pointer dereference at (null); RIP: 0010:[ffffffff8167f93a] [ffffffff8167f93a] __mutex_lock_slowpath+0xaa/0x150
Dear Dave, for Markus and me the oops was fixed in 3.5.0-18. I haven't seen your intel(0)... messages on my test systems, where did you get them? dmesg? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070690 Title: BUG: unable to handle kernel NULL pointer dereference at (null); RIP: 0010:[8167f93a] [8167f93a] __mutex_lock_slowpath+0xaa/0x150 To manage notifications about this bug go to: https://bugs.launchpad.net/bumblebee/+bug/1070690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070690] Re: BUG: unable to handle kernel NULL pointer dereference at (null); RIP: 0010:[ffffffff8167f93a] [ffffffff8167f93a] __mutex_lock_slowpath+0xaa/0x150
My and Daniels email about this problem: http://lists.freedesktop.org/archives/intel- gfx/2012-November/022707.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070690 Title: BUG: unable to handle kernel NULL pointer dereference at (null); RIP: 0010:[8167f93a] [8167f93a] __mutex_lock_slowpath+0xaa/0x150 To manage notifications about this bug go to: https://bugs.launchpad.net/bumblebee/+bug/1070690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070690] Re: BUG: unable to handle kernel NULL pointer dereference at (null); RIP: 0010:[ffffffff8167f93a] [ffffffff8167f93a] __mutex_lock_slowpath+0xaa/0x150
I talked to Daniel Vetter, he is responsible for the i915 driver and works for Intel. He told me that this chipset series doesn't support the parameter nomodeset. So this bug report can be closed now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070690 Title: BUG: unable to handle kernel NULL pointer dereference at (null); RIP: 0010:[8167f93a] [8167f93a] __mutex_lock_slowpath+0xaa/0x150 To manage notifications about this bug go to: https://bugs.launchpad.net/bumblebee/+bug/1070690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070690] Re: BUG: unable to handle kernel NULL pointer dereference at (null); RIP: 0010:[ffffffff8167f93a] [ffffffff8167f93a] __mutex_lock_slowpath+0xaa/0x150
Dear Christopher, Daniel wrote to me in a personal email usermodesetting was _never_ supported on these machines. (talking about Ivy Bridge chipsets). As written by Markus in the initial post, we had an OOPS/Kernel Panic with the i915 driver and the first official Ubuntu 12.10 driver (3.5.17?). As also written before, there are no longer kernel Panics with the new 3.5.18 kernel. In the past, we had some very hard problems with broken gpu drivers for our servers. The easiest way to fix that was adding the nomodeset parameter to the kernel command line on every server (we are freaks, we have many many servers). Looks like we now have to blacklist every gpu driver on every maschine running kernels newer than 3.6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070690 Title: BUG: unable to handle kernel NULL pointer dereference at (null); RIP: 0010:[8167f93a] [8167f93a] __mutex_lock_slowpath+0xaa/0x150 To manage notifications about this bug go to: https://bugs.launchpad.net/bumblebee/+bug/1070690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070690] Re: BUG: unable to handle kernel NULL pointer dereference at (null); RIP: 0010:[ffffffff8167f93a] [ffffffff8167f93a] __mutex_lock_slowpath+0xaa/0x150
FYI: the error is still present in the newest 3.7-rc6 mainline release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070690 Title: BUG: unable to handle kernel NULL pointer dereference at (null); RIP: 0010:[8167f93a] [8167f93a] __mutex_lock_slowpath+0xaa/0x150 To manage notifications about this bug go to: https://bugs.launchpad.net/bumblebee/+bug/1070690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070690] Re: BUG: unable to handle kernel NULL pointer dereference at (null); RIP: 0010:[ffffffff8167f93a] [ffffffff8167f93a] __mutex_lock_slowpath+0xaa/0x150
Hi, my previous posts were not accurate enough, sorry for that. To clarify some facts: The Raring Kernel 3.7.0-0.5 and the newer one from last night 3.7.0-1.7 are as buggy as the real quantal kernel. Their dmesg output is the same as mentioned in my comment #42. Also as written in post #49, the dmesg log from 3.6.4-030604-generic 3.6.6-030606-generic 3.7.0-030700rc1-generic 3.7.0-030700rc2-generic 3.7.0-030700rc3-generic 3.7.0-030700rc4-generic is the same as mentioned in post #42. conclusion: none of the listed kernels in this post is working with the bootparameter nomodeset -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070690 Title: BUG: unable to handle kernel NULL pointer dereference at (null); RIP: 0010:[8167f93a] [8167f93a] __mutex_lock_slowpath+0xaa/0x150 To manage notifications about this bug go to: https://bugs.launchpad.net/bumblebee/+bug/1070690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070690] Re: BUG: unable to handle kernel NULL pointer dereference at (null); RIP: 0010:[ffffffff8167f93a] [ffffffff8167f93a] __mutex_lock_slowpath+0xaa/0x150
I justed tested several other raring Kernel: 3.6.4-030604-generic 3.6.6-030606-generic 3.7.0-030700rc1-generic 3.7.0-030700rc2-generic 3.7.0-030700rc3-generic 3.7.0-030700rc4-generic they are all working, dmesg output looks like the one posted in #42 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070690 Title: BUG: unable to handle kernel NULL pointer dereference at (null); RIP: 0010:[8167f93a] [8167f93a] __mutex_lock_slowpath+0xaa/0x150 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1070690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070690] Re: BUG: unable to handle kernel NULL pointer dereference at (null); RIP: 0010:[ffffffff8167f93a] [ffffffff8167f93a] __mutex_lock_slowpath+0xaa/0x150
I tested the 3.7.0-030700rc5 #20120835 too, looks like it works without the kernelparameter nomodeset: [9.374325] [drm] Initialized drm 1.1.0 20060810 [9.429448] pci :00:00.0: Intel Ivybridge Chipset [9.429524] pci :00:00.0: detected gtt size: 2097152K total, 262144K mappable [9.431003] pci :00:00.0: detected 262144K stolen memory [9.431044] i915 :00:02.0: setting latency timer to 64 [9.455005] i915 :00:02.0: irq 47 for MSI/MSI-X [9.455010] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [9.455011] [drm] Driver supports precise vblank timestamp query. [9.455067] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [9.493056] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off [9.904155] fbcon: inteldrmfb (fb0) is primary device [ 10.121160] Console: switching to colour frame buffer device 240x67 [ 10.123510] fb0: inteldrmfb frame buffer device [ 10.123511] drm: registered panic notifier [ 10.151005] acpi device:43: registered as cooling_device13 [ 10.151117] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) [ 10.151143] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input4 [ 10.151243] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 but with nomodeset: [8.969763] [drm] Initialized drm 1.1.0 20060810 [9.019220] wmi: Mapper loaded [9.042668] asus_wmi: ASUS WMI generic driver loaded [9.054022] asus_wmi: Initialization: 0x0asus_wmi: BIOS WMI version: 0.9 [9.054063] asus_wmi: SFUN value: 0x06[9.054241] input: Eee PC WMI hotkeys as /devices/platform/eeepc-wmi/input/input3 [9.054738] asus_wmi: Backlight controlled by ACPI video driver [9.147639] [drm:drm_pci_agp_init] *ERROR* Cannot initialize the agpgart module. [9.147682] DRM: Fill_in_dev failed. [9.452735] r8169 :03:00.0 eth0: link down [9.452759] r8169 :03:00.0 eth0: link down [9.452790] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [9.756940] init: udev-fallback-graphics main process (830) terminated with status 1 ** Attachment added: dmesg 3.7.0-030700rc5 with nomodeset https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1070690/+attachment/3431294/+files/dmesg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070690 Title: BUG: unable to handle kernel NULL pointer dereference at (null); RIP: 0010:[8167f93a] [8167f93a] __mutex_lock_slowpath+0xaa/0x150 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1070690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070690] Re: BUG: unable to handle kernel NULL pointer dereference at (null); RIP: 0010:[ffffffff8167f93a] [ffffffff8167f93a] __mutex_lock_slowpath+0xaa/0x150
** Attachment added: dmesg 3.7.0-030700rc5 without nomodeset https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1070690/+attachment/3431295/+files/dmesg_no_nomodeset -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070690 Title: BUG: unable to handle kernel NULL pointer dereference at (null); RIP: 0010:[8167f93a] [8167f93a] __mutex_lock_slowpath+0xaa/0x150 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1070690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070690] Re: BUG: unable to handle kernel NULL pointer dereference at (null); RIP: 0010:[ffffffff8167f93a] [ffffffff8167f93a] __mutex_lock_slowpath+0xaa/0x150
@Joseph I tested together with Markus 3.5.0-16.25 and several older ones, all are working. In 3.5.0-17.26 were some drm/i915 related things added. Booting the 17.26 prints the following at boot: * Starting load fallback graphics devices [fail] the curious thing is that I can't find anything realted in dmesg/syslog. I attach the dmesg output, maybe I have something overlooked. Any hints on how I can test the different (44 :( ) commits to drivers/gpu/drm/i915 between 3.5.0-16.25 and 3.5.0-17.26? I'm kinda new to git repositorys. ** Attachment added: dmesg output from 3.5.0-17.26 at Asus H77 mainboard i7-3770 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1070690/+attachment/3426580/+files/dmesg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070690 Title: BUG: unable to handle kernel NULL pointer dereference at (null); RIP: 0010:[8167f93a] [8167f93a] __mutex_lock_slowpath+0xaa/0x150 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1070690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
