Beast thought to be extinct seen in the wild!

[GreyGeek]

SR, I had Chromium open to your last post and read about your experience with Rekonq, so I decided to try it. I opened it up and made the settings you recommended. I was signing into my gmail account. Gmail failed to accept my valid password. When I entered it again and clicked "Submit" I was greeted with ANOTHER BSOD!!!

Out of curiosity the first thing I did was to try Ctrl+Alt+Bksp and it threw me back to the log in screen! I clicked the Red stop button and selected "Reboot". The Kubuntu splash screen appeared, with the sliding white ball, and it hung there, sliding the ball. I had to power cycle to regain control.

This system was ROCK SOLID before the update that started it crashing. From history.log I can pin-point it to:

Start-Date: 2012-03-22 10:02:27
Install:
linux-headers-3.2.0-20:amd64 (3.2.0-20.32, automatic), linux-image-3.2.0-20-generic:amd64 (3.2.0-20.32), linux-headers-3.2.0-20-generic:amd64 (3.2.0-20.32)


Upgrade:
bluez-alsa:amd64 (4.98-2ubuntu6, 4.98-2ubuntu7),
libswscale2:amd64 (0.8-1ubuntu2, 0.8.1-0ubuntu1),
python-cupshelpers:amd64 (1.3.8+20120201-0ubuntu5, 1.3.8+20120201-0ubuntu6),
libc-bin:amd64 (2.15-0ubuntu5, 2.15-0ubuntu6),
ubuntuone-control-panel-qt:amd64 (2.99.90-0ubuntu2, 2.99.91-0ubuntu1),
python-ubuntuone-client:amd64 (2.99.90-0ubuntu1, 2.99.91-0ubuntu1),
ubuntuone-client:amd64 (2.99.90-0ubuntu1, 2.99.91-0ubuntu1),
python3.2-minimal:amd64 (3.2.3~rc1-1, 3.2.3~rc2-1ubuntu1),
gdebi:amd64 (0.8.5, 0.8.5build1),
gir1.2-indicate-0.7:amd64 (0.6.91-0ubuntu1, 0.6.92-0ubuntu1),
pulseaudio-module-bluetooth:amd64 (1.1-0ubuntu12, 1.1-0ubuntu13),
pulseaudio:amd64 (1.1-0ubuntu12, 1.1-0ubuntu13),
linux-headers-3.2.0-19:amd64 (3.2.0-19.30, 3.2.0-19.31),
gvfs-backends:amd64 (1.11.4-0ubuntu2, 1.11.5-1ubuntu1),
chromium-browser:amd64 (17.0.963.79~r125985-0ubuntu1, 17.0.963.83~r127885-0ubuntu1),
libimobiledevice2:amd64 (1.1.1-3ubuntu1, 1.1.1-4),
libcupsfilters1:amd64 (1.0.7-0bzr1, 1.0.8-0bzr1),
gir1.2-dbusmenu-glib-0.4:amd64 (0.5.94-0ubuntu1, 0.5.95-0ubuntu1),
libpython2.7:amd64 (2.7.3~rc1-1ubuntu2, 2.7.3~rc2-1ubuntu1),
gir1.2-freedesktop:amd64 (1.31.20-1, 1.31.22-1),
libpython3.2:amd64 (3.2.3~rc1-1, 3.2.3~rc2-1ubuntu1),
bluez-cups:amd64 (4.98-2ubuntu6, 4.98-2ubuntu7),
python-zeitgeist:amd64 (0.8.99~alpha3-1, 0.8.99~beta1-1),
libvte-common:amd64 (0.28.2-3ubuntu1, 0.28.2-3ubuntu2),
linux-generic:amd64 (3.2.0.19.21, 3.2.0.20.22),
libavfilter2:amd64 (0.8-1ubuntu2, 0.8.1-0ubuntu1),
libavutil-extra-51:amd64 (0.8.0.1build1+medibuntu1, 0.8.1ubuntu1),
libutouch-frame1:amd64 (2.2.1-0ubuntu1, 2.2.2-0ubuntu1),
python-ubuntuone-storageprotocol:amd64 (2.99.90-0ubuntu1, 2.99.91-0ubuntu1),
libav-tools:amd64 (0.8-1ubuntu2, 0.8.1-0ubuntu1),
gvfs-libs:amd64 (1.11.4-0ubuntu2, 1.11.5-1ubuntu1),
pulseaudio-module-x11:amd64 (1.1-0ubuntu12, 1.1-0ubuntu13),
ubuntuone-control-panel:amd64 (2.99.90-0ubuntu2, 2.99.91-0ubuntu1),
gdebi-core:amd64 (0.8.5, 0.8.5build1),
libgirepository-1.0-1:amd64 (1.31.20-1, 1.31.22-1),
libavdevice53:amd64 (0.8-1ubuntu2, 0.8.1-0ubuntu1),
gvfs-common:amd64 (1.11.4-0ubuntu2, 1.11.5-1ubuntu1),
python-bzrlib:amd64 (2.5.0-1ubuntu1, 2.5.0-2ubuntu1),
bluez:amd64 (4.98-2ubuntu6, 4.98-2ubuntu7),
python2.7:amd64 (2.7.3~rc1-1ubuntu2, 2.7.3~rc2-1ubuntu1),
python3.2:amd64 (3.2.3~rc1-1, 3.2.3~rc2-1ubuntu1),
libindicate5:amd64 (0.6.91-0ubuntu1, 0.6.92-0ubuntu1),
linux-firmware:amd64 (1.71, 1.73),
libappindicator3-1:amd64 (0.4.91-0ubuntu3, 0.4.92-0ubuntu1),
python-gi:amd64 (3.1.92-1, 3.1.93-0svn1),
libgdk-pixbuf2.0-0:amd64 (2.26.0-0ubuntu1, 2.26.0-1),
libgtkspell0:amd64 (2.0.16-1ubuntu3, 2.0.16-1ubuntu5),
ubuntu-sso-client-gtk:amd64 (2.99.90-0ubuntu2, 2.99.91-0ubuntu1),
chromium-browser-l10n:amd64 (17.0.963.79~r125985-0ubuntu1, 17.0.963.83~r127885-0ubuntu1),
bzr:amd64 (2.5.0-1ubuntu1, 2.5.0-2ubuntu1),
ubuntu-sso-client-qt:amd64 (2.99.90-0ubuntu2, 2.99.91-0ubuntu1),
ubuntuone-control-panel-common:amd64 (2.99.90-0ubuntu2, 2.99.91-0ubuntu1),
libdbusmenu-glib4:amd64 (0.5.94-0ubuntu1, 0.5.95-0ubuntu1),
pulseaudio-esound-compat:amd64 (1.1-0ubuntu12, 1.1-0ubuntu13),
libsyncdaemon-1.0-1:amd64 (2.99.90-0ubuntu1, 2.99.91-0ubuntu1),
multiarch-support:amd64 (2.15-0ubuntu5, 2.15-0ubuntu6),
python-vte:amd64 (0.28.2-3ubuntu1, 0.28.2-3ubuntu2),
libvte9:amd64 (0.28.2-3ubuntu1, 0.28.2-3ubuntu2),
indicator-messages:amd64 (0.5.93-0ubuntu2, 0.5.94-0ubuntu1),
libdbusmenu-gtk4:amd64 (0.5.94-0ubuntu1, 0.5.95-0ubuntu1),
system-config-printer-udev:amd64 (1.3.8+20120201-0ubuntu5, 1.3.8+20120201-0ubuntu6),
libpulse-mainloop-glib0:amd64 (1.1-0ubuntu12, 1.1-0ubuntu13),
libdbusmenu-gtk3-4:amd64 (0.5.94-0ubuntu1, 0.5.95-0ubuntu1),
linux-headers-generic:amd64 (3.2.0.19.21, 3.2.0.20.22),
ffmpeg:amd64 (0.8-1ubuntu2, 0.8.1-0ubuntu1),
linux-image-generic:amd64 (3.2.0.19.21, 3.2.0.20.22),
qtcreator-doc:amd64 (2.4.1-0ubuntu1, 2.4.1-0ubuntu2),
libpostproc52:amd64 (0.8-1ubuntu2, 0.8.1-0ubuntu1),
bzr-doc:amd64 (2.5.0-1ubuntu1, 2.5.0-2ubuntu1),
xserver-xorg-input-wacom:amd64 (0.13.0-0ubuntu1, 0.14.0-0ubuntu1),
python-ubuntu-sso-client:amd64 (2.99.90-0ubuntu2, 2.99.91-0ubuntu1),
xul-ext-ubufox:amd64 (2.0-0ubuntu1, 2.0.1-0ubuntu1),
pcmciautils:amd64 (018-5, 018-6),
ubuntu-sso-client:amd64 (2.99.90-0ubuntu2, 2.99.91-0ubuntu1),
libavformat53:amd64 (0.8-1ubuntu2, 0.8.1-0ubuntu1),
gir1.2-glib-2.0:amd64 (1.31.20-1, 1.31.22-1),
gdebi-kde:amd64 (0.8.5, 0.8.5build1),
python-gobject:amd64 (3.1.92-1, 3.1.93-0svn1),
libpng12-0:amd64 (1.2.46-3ubuntu2, 1.2.46-3ubuntu3),
libpng12-0:i386 (1.2.46-3ubuntu2, 1.2.46-3ubuntu3),
libutouch-grail1:amd64 (3.0.2-0ubuntu1, 3.0.3-0ubuntu1),
gir1.2-gdkpixbuf-2.0:amd64 (2.26.0-0ubuntu1, 2.26.0-1),
libvte-2.90-common:amd64 (0.31.0-0ubuntu2, 0.32.0-1ubuntu2),
zeitgeist-core:amd64 (0.8.99~alpha3-1, 0.8.99~beta1-1),
qtcreator:amd64 (2.4.1-0ubuntu1, 2.4.1-0ubuntu2),
python-gdbm:amd64 (2.7.1-3, 2.7.3-1),
libc6-dev:amd64 (2.15-0ubuntu5, 2.15-0ubuntu6),
python2.7-minimal:amd64 (2.7.3~rc1-1ubuntu2, 2.7.3~rc2-1ubuntu1),
libvte-2.90-9:amd64 (0.31.0-0ubuntu2, 0.32.0-1ubuntu2),
libpulse-dev:amd64 (1.1-0ubuntu12, 1.1-0ubuntu13),
indicator-status-provider-mc5:amd64 (0.5.93-0ubuntu2, 0.5.94-0ubuntu1),
libpulse0:amd64 (1.1-0ubuntu12, 1.1-0ubuntu13),
python-ubuntuone-control-panel:amd64 (2.99.90-0ubuntu2, 2.99.91-0ubuntu1),
libpulsedsp:amd64 (1.1-0ubuntu12, 1.1-0ubuntu13),
gvfs:amd64 (1.11.4-0ubuntu2, 1.11.5-1ubuntu1),
linux-libc-dev:amd64 (3.2.0-19.30, 3.2.0-20.32),
system-config-printer-common:amd64 (1.3.8+20120201-0ubuntu5, 1.3.8+20120201-0ubuntu6),
libc-dev-bin:amd64 (2.15-0ubuntu5, 2.15-0ubuntu6),
libc6:amd64 (2.15-0ubuntu5, 2.15-0ubuntu6),
libc6:i386 (2.15-0ubuntu5, 2.15-0ubuntu6),
cups-filters:amd64 (1.0.7-0bzr1, 1.0.8-0bzr1),
indicator-application:amd64 (0.4.93-0ubuntu1, 0.4.94-0ubuntu1),
chromium-codecs-ffmpeg-extra:amd64 (17.0.963.79~r125985-0ubuntu1, 17.0.963.83~r127885-0ubuntu1),
xserver-xorg-input-synaptics:amd64 (1.5.99.901-0ubuntu1, 1.5.99.901-0ubuntu2),
gir1.2-vte-2.90:amd64 (0.31.0-0ubuntu2, 0.32.0-1ubuntu2),
libbluetooth3:amd64 (4.98-2ubuntu6, 4.98-2ubuntu7),
pulseaudio-utils:amd64 (1.1-0ubuntu12, 1.1-0ubuntu13),
libgdk-pixbuf2.0-common:amd64 (2.26.0-0ubuntu1, 2.26.0-1),
libavcodec-extra-53:amd64 (0.8.0.1build1+medibuntu1, 0.8.1ubuntu1),
gvfs-daemons:amd64 (1.11.4-0ubuntu2, 1.11.5-1ubuntu1),
libindicator-messages-status-provider1:amd64 (0.5.93-0ubuntu2, 0.5.94-0ubuntu1),
libpng12-dev:amd64 (1.2.46-3ubuntu2, 1.2.46-3ubuntu3)
End-Date: 2012-03-22 10:08:08

PS. I am now running the -19 kernel to see how it goes.

[SteveRiley]

This system was ROCK SOLID before the update that started it crashing. From history.log I can pin-point it to: linux-3.2.0-20

Jerry, Jerry, Jerry. Everyone knows that you're supposed to perform kernel updates only on Thursdays after 4:00 PM when the bells ring and only when a UFO passes over your house, causes your garage door opener to raise on its own, and makes your Polaroid camera self-eject a photo of the aliens in Roswell. You did it wrong!

[dibl]

Jerry, Jerry, Jerry. Everyone knows that you're supposed to perform kernel updates only on Thursdays after 4:00 PM when the bells ring ...

Plus, I'll bet you didn't burn the chicken feathers and say the chant to the little monkey-god, did you? Shame -- this is what you get!

[tdockery97]

My updates have gone without incident. Of course I hold my laptop over my head and cluck like a chicken before hitting "apply updates".

[GreyGeek]

I confess. I am fresh out of chicken feathers. I used them all to make arrows for Minecraft so I wouldn't have to do hand-to-claw combat. And, I couldn't find a Google translate button for "English-to-Chicken" after I realized that I forgot how to cluck Chicken!

So, I return to report that selecting the -19 kernel has restored my stability to its former glory. And, my average idle temp has dropped by 2F.

UPDATE: I just returned from playing Mincraft 1.2.4 for about 30 minutes. I can report that it plays under the -19 kernel at least 10F cooler, on average. Where before, it was averaging 132 to 138, now it averages around 122F and rarely goes above 127F.

[GreyGeek]

A RETRACTION IS IN ORDER!

On March 11, 2012, I purchased a 4GB RAM chip from BestBuy to boost my memory to its maximum of 8GB. The first thing I did after installing it was to run two memory checks, a day apart. The second ran all night. It passed.

As I've reported elsewhere, I began having problems relating to application stability, xserver dying, wlan0 stability, heating up, etc, but I did not suspect the RAM because it had passed the tests only a few days before.. Then, I blew a BSOD. A couple days later a second one occurred while I was running Minecraft.

I thought it was the new kernel, which I upgraded to on the 23rd. I down graded to the -19 kernel and it appeared to improve things. Then, my FS was corrupted and I had to do an fsck. The problems relating to app, video and wireless stability seemed to increase in frequency and severity during the last couple days. It's been so bad today that I began to suspect memory problems.

I booted into the memory check app and immediately it blew errors and painted the bottom half of the screen red.

I pulled the new ram out and restarted this box. So far, all the applications are stable, and the Chromium browser is not hanging as much as it used to, but there still is an annoying dropout problem with the rtl8192ce wireless driver, which is another issue.

So, neither Linux, nor any application was responsible for the two BSOD's that occurred on this machine! The wild beast is still illusive.

[rms]

On March 11, 2012, I purchased a 4GB RAM chip from BestBuy to boost my memory to its maximum of 8GB. The first thing I did after installing it was to run two memory checks, a day apart. The second ran all night. It passed.

Hi GG,

Merely as a reminder; you should buy module from the same maker(mandatory) end even then if they are not from the same series that may cause trouble. That means safest thing is to buy 8GB... bummer...

[GreyGeek]

Hi GG,

Merely as a reminder; you should buy module from the same maker(mandatory) end even then if they are not from the same series that may cause trouble. That means safest thing is to buy 8GB... bummer...

I knew that, once, but decided that RAM chip sensitivities were a thing of the past. I guess they are not and now I am second-guessing if I should have purchased an 8GB stick, instead of the 4GB that is coming, and used it to replace the 4GB stick that came with the machine.

[rms]

I knew that, once, but decided that RAM chip sensitivities were a thing of the past. I guess they are not and now I am second-guessing if I should have purchased an 8GB stick, instead of the 4GB that is coming, and used it to replace the 4GB stick that came with the machine.

Unfortunately, that still holds true. Maybe you can still find a 4GB module - from the same manufacturer - that can be paired with one in your machine.

[GreyGeek]

Unfortunately, that still holds true. Maybe you can still find a 4GB module - from the same manufacturer - that can be paired with one in your machine.

I tried that initally but found only one source that offered an identical stick to the one that was already in bank0 --- Kingston ACR512....., and they wanted $126 for it. :eek:

I can get 2 4GB's as a "kit", but finding a single 8GB PC3-10600 DDR3 7-7-7-20 is proving a little more difficult.

[rms]

I tried that initally but found only one source that offered an identical stick to the one that was already in bank0 --- Kingston ACR512....., and they wanted $126 for it. :eek:

I can get 2 4GB's as a "kit", but finding a single 8GB PC3-10600 DDR3 7-7-7-20 is proving a little more difficult.

You haven't mentioned the price of the "kit". Maybe you can sell your old module and save some $. It would be money well-spent, I think, because it's way more comfortable to try things in a virtual machine than having to deal with a bunch of partitions like I do. Unless you're planning to buy a new machine.

[GreyGeek]

I had already ordered a 4GB stick from Amazon and it will be here tomorrow. If it doesn't work out I have a set of two 4GB sticks waiting in Amazon's shopping cart and I'll pull out the original and put in two new sticks as a set.

Anyway, running with only the original 4GB and having compiled the rtl8192ce wifi driver, my Precise installation is faultless. I've used the Internet all day and it hasn't lagged or stalled or hung even once.