Re: Instability in Wheezy system
On Thu, Jul 26, 2012 at 10:22:23PM -0500, Mark Allums wrote: I can say that Chrome and Chromium themselves very unstable on all my systems. Not true on any of my boxen. Running Chromium from Debian SID. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120727133537.ga3...@thinkpad.gateway.2wire.net
Re: Instability in Wheezy system
On 27 July 2012 14:35, Stephen Allen marathon.duran...@gmail.com wrote: On Thu, Jul 26, 2012 at 10:22:23PM -0500, Mark Allums wrote: I can say that Chrome and Chromium themselves very unstable on all my systems. Not true on any of my boxen. Running Chromium from Debian SID. Nor here with Chrome, last three weeks or so.. -- Sent from FOSS (Free Open Source Software) Debian GNU/Linux -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cal36vgkk5ftw2kcyr3ivdhsdt_lzxtcojuaozor5gygi2px...@mail.gmail.com
Instability in Wheezy system
I report a problem I experienced. I have a homebrew tower built around the AMD FX-8120 running Wheezy. 16 GB of RAM, an 80 GB SSD for the OS and a 2 TB spinning disk drive for data. Today I had a 30 minute Skype call. (2.2 client) After I hung up, I clicked on a message in my GMail box in Chromium. I started getting the Stopped responding, click Kill or Wait dialog. Killed Chromium, reloaded, tried again. Same. Loaded Super Tux Kart. It drew its window but didn't actually load any karts or tracks, and froze with an empty frame. Ran htop in a terminal, except it never ran. Ctrl-Alt-F1 to get a VT. htop as root froze there, too. In VT2, ps a froze. In VT3, nothing interesting in the logs. Regular top would run but showed nothing useful. I ran reboot. The shutdown process froze at deactivating BlueTooth. I had to use the mechanical reset button. Linux boxes should never need mechanical reset. Ideas? -- Carl Fink nitpick...@nitpicking.com Read my blog at blog.nitpicking.com. Reviews! Observations! Stupid mistakes you can correct! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120727023722.ga22...@panix.com
Re: Instability in Wheezy system
On 7/26/2012 9:37 PM, Carl Fink wrote: I report a problem I experienced. I have a homebrew tower built around the AMD FX-8120 running Wheezy. 16 GB of RAM, an 80 GB SSD for the OS and a 2 TB spinning disk drive for data. Today I had a 30 minute Skype call. (2.2 client) After I hung up, I clicked on a message in my GMail box in Chromium. I started getting the Stopped responding, click Kill or Wait dialog. Killed Chromium, reloaded, tried again. Same. Loaded Super Tux Kart. It drew its window but didn't actually load any karts or tracks, and froze with an empty frame. Ran htop in a terminal, except it never ran. Ctrl-Alt-F1 to get a VT. htop as root froze there, too. In VT2, ps a froze. In VT3, nothing interesting in the logs. Regular top would run but showed nothing useful. I ran reboot. The shutdown process froze at deactivating BlueTooth. I had to use the mechanical reset button. Linux boxes should never need mechanical reset. Ideas? I can say that Chrome and Chromium themselves very unstable on all my systems. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5012096f.6000...@allums.com
Re: Instability in Wheezy system
On 26/07/12 10:37 PM, Carl Fink wrote: I report a problem I experienced. I have a homebrew tower built around the AMD FX-8120 running Wheezy. 16 GB of RAM, an 80 GB SSD for the OS and a 2 TB spinning disk drive for data. Today I had a 30 minute Skype call. (2.2 client) After I hung up, I clicked on a message in my GMail box in Chromium. I started getting the Stopped responding, click Kill or Wait dialog. Killed Chromium, reloaded, tried again. Same. Loaded Super Tux Kart. It drew its window but didn't actually load any karts or tracks, and froze with an empty frame. Ran htop in a terminal, except it never ran. Ctrl-Alt-F1 to get a VT. htop as root froze there, too. In VT2, ps a froze. In VT3, nothing interesting in the logs. Regular top would run but showed nothing useful. I ran reboot. The shutdown process froze at deactivating BlueTooth. I had to use the mechanical reset button. Linux boxes should never need mechanical reset. Ideas? Have you run memtest86+? Another problem could be your motherboard. Have you tried booting from a (different distro) live CD to see if the problem occurs on it too? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50120c3e.3070...@rogers.com
Re: Instability in Wheezy system
On Thu, Jul 26, 2012 at 11:34:22PM -0400, Gary Dale wrote: Have you run memtest86+? No. Would this specific problem (presumably with the process table) be characteristic of a RAM problem? Another problem could be your motherboard. Have you tried booting from a (different distro) live CD to see if the problem occurs on it too? It's only happened once, total. -- Carl Fink nitpick...@nitpicking.com Read my blog at blog.nitpicking.com. Reviews! Observations! Stupid mistakes you can correct! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120727034037.ga3...@panix.com
Re: Instability in Wheezy system
On 26/07/12 11:40 PM, Carl Fink wrote: On Thu, Jul 26, 2012 at 11:34:22PM -0400, Gary Dale wrote: Have you run memtest86+? No. Would this specific problem (presumably with the process table) be characteristic of a RAM problem? Could happen. It's always worth checking. I've seen memory issues cause all kinds of weird problems. I've also seen a lot of memory problems lately. In fact, I'm running tests on new stick I got that doesn't seem to play nice with the existing stick in a system. It was a warranty replacement on another stick that went bad. Both are the same model number but this new one seems to need a different BIOS setting. The system actually booted and ran fine, but I decided to run memtest86+ on it and was shocked to receive tens of thousands of errors. Conversely, two other systems I look after were constantly acting up with just a few memory errors reported by memtest. Another problem could be your motherboard. Have you tried booting from a (different distro) live CD to see if the problem occurs on it too? It's only happened once, total. If it's not repeatable, then you can't tell if you've fixed it. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50121168.1090...@rogers.com
