** Description changed: After upgrading to Jaunty, my computer has been having random lockups. This has happened when: 1) Running vmplayer and especially when syncing my iPod touch with iTunes in the VM 2) Just running firefox and other "normal" usage. I started this forum post: http://ubuntuforums.org/showthread.php?p=7207861 In there I mention that rebuilding my box did not help. This was never a problem with Intrepid or Hardy. I can duplicate the problem 100% of the time when syncing my iPod touch with iTunes in my Windows VM inside of the latest vmplayer. After rebuilding my box, it did not hang at all until after running vmplayer, installing my printer software (TurboPrint) and Adobe AIR. I really don't think it is Adobe as it should not be running anything and the crashes all happened when it was not running. TurboPrint may be a problem, I have not had a non-vmware hang yet after removing its gnome-applet from my gnome-panel. Perhaps that is related to the same problem seen with GTK and alarm-clock? That bug is https://bugs.launchpad.net/bugs/321176 I had a tail up, through SSH while hanging my computer with vmware. The syslog, messages and kern.log files all look the same basically. There is no kernel oops printed to these files or the SSH console. When this happens, the only thing that responds is Alt+SysRq+b (the kernel reboot key sequence). All the other Alt+SysRq keystrokes have no visible effect (I tried r, k, o, s, u, m, e, i and l, but only b did anything). CTRL+ALT+F2 does nothing, and SSH locks up as well as my ability to ping the computer, so it appears to be the kernel, not X. Here is the output that I saw while tailing /var/log/syslog and running vmplayer and syncing my iPod: May 3 19:26:35 drewpc kernel: [ 2367.177316] /dev/vmmon[11959]: PTSC: initialized at 2009413000 Hz using reference clock May 3 19:26:35 drewpc kernel: [ 2367.195550] /dev/vmmon[11959]: Vmx86_InitNUMAInfo : numaNumMemRanges=3 and numaNumNodes=1 May 3 19:26:37 drewpc kernel: [ 2369.027601] /dev/vmnet: open called by PID 11965 (vmware-vmx) May 3 19:26:37 drewpc kernel: [ 2369.027622] device eth0 entered promiscuous mode May 3 19:26:37 drewpc kernel: [ 2369.027738] bridge-eth0: enabled promiscuous mode May 3 19:26:37 drewpc kernel: [ 2369.027740] /dev/vmnet: port on hub 0 successfully opened May 3 19:26:59 drewpc kernel: [ 2391.225587] device eth0 left promiscuous mode May 3 19:26:59 drewpc kernel: [ 2391.225708] bridge-eth0: disabled promiscuous mode May 3 19:26:59 drewpc kernel: [ 2391.225813] /dev/vmnet: open called by PID 11965 (vmware-vmx) May 3 19:26:59 drewpc kernel: [ 2391.225831] device eth0 entered promiscuous mode May 3 19:26:59 drewpc kernel: [ 2391.225945] bridge-eth0: enabled promiscuous mode May 3 19:26:59 drewpc kernel: [ 2391.225947] /dev/vmnet: port on hub 0 successfully opened May 3 19:30:01 drewpc /USR/SBIN/CRON[12005]: (root) CMD ([ -x /usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null) May 3 19:31:46 drewpc kernel: [ 2678.408465] usb 1-4.3: reset high speed USB device using ehci_hcd and address 6 May 3 19:31:47 drewpc kernel: [ 2678.757488] usb 1-4.3: reset high speed USB device using ehci_hcd and address 6 May 3 19:31:48 drewpc kernel: [ 2680.334348] usb 1-4.3: usbfs: process 11959 (vmware-vmx) did not claim interface 1 before use May 3 19:31:49 drewpc kernel: [ 2680.740443] usb 1-4.3: usbfs: process 11959 (vmware-vmx) did not claim interface 0 before use May 3 19:31:53 drewpc kernel: [ 2684.717477] usb 1-4.3: usbfs: process 11965 (vmware-vmx) did not claim interface 0 before use May 3 19:31:53 drewpc kernel: [ 2684.719950] usb 1-4.3: usbfs: process 11959 (vmware-vmx) did not claim interface 0 before use May 3 19:33:53 drewpc kernel: [ 2804.873322] usb 1-4.3: usbfs: process 11965 (vmware-vmx) did not claim interface 0 before use May 3 19:35:02 drewpc kernel: [ 2873.835415] NVRM: Xid (0005:00): 26, Ch 000001ff M 00001ffc D ffffffff intr ffffffff That last line was not found in /var/log/syslog after rebooting (never got saved to the filesystem) so it probably directly related to the crash? I tried this 2x and I got the same type of output. The first time that I was SSH'd in, this was the last line (as you can see, it is the same): May 3 18:40:38 drewpc kernel: [82609.870900] NVRM: Xid (0005:00): 26, Ch 000001ff M 00001ffc D ffffffff intr ffffffff Perhaps this is a bug in the nVidia driver and not the kernel as that last line looks like it could be an nvidia log? I am running the same nvidia driver on my MythBuntu box that I also upgraded to Jaunty and no problems with that computer, but it has a built-in graphics card that is newer (eVGA motherboard 113-M2-113 with the nVidia MCP78S FeForce 8200 on board). This is the 180.44 nvidia driver that comes with Jaunty. I can give the old 177 a try by pulling it from the Intrepid repositories (for some reason Jaunty has 173 and 180, but not 177). I say 177 as that is what I was using on Intrepid for a long time with no crashes. I am sorry if this is an invalid bug for the kernel, but since it is the kernel crashing and I can reproduce it, I thought I would give it a try to have you look into this. Thank you, Andrew ProblemType: Bug Architecture: amd64 CurrentDmesg: [ 116.577026] Clocksource tsc unstable (delta = -176552972 ns) DistroRelease: Ubuntu 9.04 HibernationDevice: RESUME=UUID=d698c562-eff7-41ce-95c1-5dd0402a053f MachineType: NonfreeKernelModules: nvidia Package: linux-image-2.6.28-11-generic 2.6.28-11.42 ProcCmdLine: root=UUID=e001ab45-5a60-422b-b6e8-70e0be3848ba ro xforcevesa quiet splash vga=795 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.28-11.42-generic SourcePackage: linux + + [lspci] + 00:00.0 Memory controller [0580]: nVidia Corporation CK804 Memory Controller [10de:005e] (rev a3) + Subsystem: EPoX Computer Co., Ltd. Device [1695:1011] + 05:00.0 VGA compatible controller [0300]: nVidia Corporation G71 [GeForce 7300 GS] [10de:01df] (rev a1) + Subsystem: eVga.com. Corp. Device [3842:c437]
-- Kernel locks up in Jaunty. 100% reproducible with vmplayer https://bugs.launchpad.net/bugs/371472 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
