Journaling on estrip is easy and free. sign up here

Tinypliny's Journal

tinypliny
My Podcast Link

01/01/2012 09:24 #55829

Whatever it takes.
Category: goals
That is going to be my philosophy this date onwards.

In the year 2000...
2012...

I will
  1. Work all year in pomodoros and squash as many tomatoes as I can.
  1. Publish. Publish. Publish
  1. Master R and Perl.
  1. Learn how to manipulate and code in Bioconductor
  1. Analyze and publish on least one public dataset in genetics.
  1. Transition into more genetics and bioinformatics.
  1. Write more science. Make future-oriented useful notes.
  1. Be more in contact with my family.
  1. Be less confused, Be more mentally organized
  1. Set priorities and stick with them regardless of what comes in between.
  1. Reach a better place and work on feeling less guilty

tinypliny - 01/02/12 15:19
Yeah, all of them are priorities. Equally important, without exceptions.
metalpeter - 01/01/12 10:35
Guess you put a space or extra enter in there.... Well I wish you luck with those...

12/24/2011 08:24 #55789

Merry Holidays!
Category: e:strip
For Paul, Matt and Terry. :-)

image

---
NB: (e:matthew), check out the illustrations here:
heidi - 12/24/11 16:00
Love it!
metalpeter - 12/24/11 09:21
That is pretty wild :)

12/23/2011 15:38 #55788

Off.
Category: goals
My new deadline is December 31. I am dead serious about this and want to finish it once and for all. Even if lake Erie burst into flames right now and it was a grand public spectacle, I wouldn't want to go see it more than I want to finish my dissertation writing.

So I am taking off the internets and (e:strip) till the next year.

All of you, happy holidays and behave yourselves.

cheerio,
TP

metalpeter - 12/24/11 09:20
So Is this Time to Say Happy New Year!?
paul - 12/23/11 17:43
Happy dissertation writing.

12/19/2011 21:13 #55775

Graphic details
Category: linux
rpm -qa *\nvidia\*  *\kernel\*|sort;uname -r;lsmod |grep -e nvidia -e nouveau;cat /etc/X11/xorg.conf


Hmmm.. that doesn't look so good


rpm -qa *\nvidia\* *\kernel\*|sort;uname -r;lsmod |grep -e nvidia -e nouveau;cat /etc/X11/xorg.conf



nouveau;cat /etc/X11/xorg.conf
abrt-addon-kerneloops-2.0.6-1.fc16.x86_64
kernel-3.1.4-1.fc16.x86_64
kernel-3.1.5-1.fc16.x86_64
kernel-3.1.5-2.fc16.x86_64
kernel-headers-3.1.5-2.fc16.x86_64
libreport-plugin-kerneloops-2.0.7-1.fc16.x86_64
texlive-l3kernel-2011-4.SVN_2966.svn24657.fc16.noarch
3.1.5-2.fc16.x86_64
nouveau 754554 0
ttm 61533 1 nouveau
drm_kms_helper 30277 2 i915,nouveau
drm 213647 7 i915,nouveau,ttm,drm_kms_helper
i2c_algo_bit 5572 2 i915,nouveau
i2c_core 28203 7 videodev,i2c_i801,i915,nouveau,drm_kms_helper,drm,i2c_algo_bit
mxm_wmi 1743 1 nouveau
video 12388 2 i915,nouveau
cat: /etc/X11/xorg.conf: No such file or directory

PS: I would like a decent lighter background code box for christmas.
With
  • Inconsolata monospace font
  • line-wrapping
  • syntax highlighting (even without syntax highlighting is fine really)
  • for perl and bash.
Thanks! :)
tinypliny - 12/19/11 23:20
Yes, it works for me too. Just posted that for reference. No particular reason. I guess I like having information about my hardware/software out in the internets! :))
uncutsaniflush - 12/19/11 22:10
Fedora doesn't use xorg.conf. because X is configured automagically during the boot process. For most users that just works.

I think you could make yourself a xorg.conf file if you want.

12/17/2011 20:51 #55762

More fedora 16 freezes
Category: linux
Thankfully, I waited for a complete 5 minutes (took (e:metalpeter)'s advice and went to get tea) instead of jumping on the power button. It recovered after taking its own sweet time.

Dec 17 20:20:26 why udevd[11705]: timeout: killing '/sbin/blkid -o udev -p /dev/sdb1' [12021]
Dec 17 20:20:27 why udevd[11705]: timeout: killing '/sbin/blkid -o udev -p /dev/sdb1' [12021]
Dec 17 20:20:28 why udevd[11705]: timeout: killing '/sbin/blkid -o udev -p /dev/sdb1' [12021]
Dec 17 20:20:28 why dbus-daemon[1173]: dbus[1173]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper)
Dec 17 20:20:28 why dbus[1173]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper)
Dec 17 20:20:28 why dbus-daemon[1173]: Launching FprintObject
Dec 17 20:20:28 why dbus[1173]: [system] Successfully activated service 'net.reactivated.Fprint'
Dec 17 20:20:28 why dbus-daemon[1173]: dbus[1173]: [system] Successfully activated service 'net.reactivated.Fprint'
Dec 17 20:20:28 why dbus-daemon[1173]: ** Message: D-Bus service launched with name: net.reactivated.Fprint
Dec 17 20:20:28 why dbus-daemon[1173]: ** Message: entering main loop
Dec 17 20:20:29 why udevd[11705]: timeout: killing '/sbin/blkid -o udev -p /dev/sdb1' [12021]
Dec 17 20:20:30 why udevd[11705]: timeout: killing '/sbin/blkid -o udev -p /dev/sdb1' [12021]
Dec 17 20:20:31 why udevd[11705]: timeout: killing '/sbin/blkid -o udev -p /dev/sdb1' [12021]


This is the tail of the /var/log/messages. With all those mentions of killings and daemons, it totally looks like notes from a homicidal maniac with a medieval tilt.

Farther back the log has these entries:

Dec 17 16:17:19 why dbus-daemon[1173]: dbus[1173]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Dec 17 16:26:35 why kernel: [65687.762948] CPU6: Package power limit notification (total events = 2)
Dec 17 16:26:35 why kernel: [65687.762956] CPU2: Package power limit notification (total events = 2)
Dec 17 16:26:35 why kernel: [65687.762956] CPU1: Package power limit notification (total events = 2)
Dec 17 16:26:35 why kernel: [65687.762965] CPU0: Package power limit notification (total events = 2)
Dec 17 16:26:35 why kernel: [65687.762969] CPU4: Package power limit notification (total events = 2)
Dec 17 16:26:35 why kernel: [65687.762972] CPU7: Package power limit notification (total events = 2)
Dec 17 16:26:35 why kernel: [65687.762977] CPU5: Package power limit notification (total events = 2)
Dec 17 16:26:35 why kernel: [65687.762977] CPU3: Package power limit notification (total events = 2)
Dec 17 16:26:35 why kernel: [65687.773971] CPU5: Package power limit normal
Dec 17 16:26:35 why kernel: [65687.773975] CPU2: Package power limit normal
Dec 17 16:26:35 why kernel: [65687.773982] CPU4: Package power limit normal
Dec 17 16:26:35 why kernel: [65687.773984] CPU6: Package power limit normal
Dec 17 16:26:35 why kernel: [65687.773988] CPU3: Package power limit normal
Dec 17 16:26:35 why kernel: [65687.773992] CPU7: Package power limit normal
Dec 17 16:26:35 why kernel: [65687.773997] CPU1: Package power limit normal
Dec 17 16:26:35 why kernel: [65687.773999] CPU0: Package power limit normal
Dec 17 16:26:48 why kernel: [65700.686031] [Hardware Error]: Machine check events logged
Dec 17 16:26:48 why mcelog[1166]: Hardware event. This is not a software error.
Dec 17 16:26:48 why mcelog[1166]: MCE 0
Dec 17 16:26:48 why mcelog[1166]: CPU 2 THERMAL EVENT TSC 7740a8dc9110
Dec 17 16:26:48 why mcelog[1166]: TIME 1324157195 Sat Dec 17 16:26:35 2011
Dec 17 16:26:48 why mcelog[1166]: Processor 2 below trip temperature. Throttling disabled
Dec 17 16:26:48 why mcelog[1166]: STATUS c0000000881b0c00 MCGSTATUS 0
Dec 17 16:26:48 why mcelog[1166]: MCGCAP c09 APICID 4 SOCKETID 0
Dec 17 16:26:48 why mcelog[1166]: CPUID Vendor Intel Family 6 Model 42
Dec 17 16:26:48 why mcelog[1166]: Hardware event. This is not a software error.
Dec 17 16:26:48 why mcelog[1166]: MCE 1
Dec 17 16:26:48 why mcelog[1166]: CPU 1 THERMAL EVENT TSC 7740a8dcb633
Dec 17 16:26:48 why mcelog[1166]: TIME 1324157195 Sat Dec 17 16:26:35 2011
Dec 17 16:26:48 why mcelog[1166]: Processor 1 below trip temperature. Throttling disabled
Dec 17 16:26:48 why mcelog[1166]: STATUS c0000000881b0c00 MCGSTATUS 0
Dec 17 16:26:48 why mcelog[1166]: MCGCAP c09 APICID 2 SOCKETID 0
Dec 17 16:26:48 why mcelog[1166]: CPUID Vendor Intel Family 6 Model 42
Dec 17 16:26:48 why mcelog[1166]: Hardware event. This is not a software error.


It killed something in cold blood and is now gloating over it?

Apparently it is some bios issue as described here:

According to the followup to that post, it's a kernel issue that sprang up after 2.6.38.7 The kernel is not able to balance loads on the CPU/GPU well in processors with a sandy bridge and gives rise to these errors. Updating the bios does not solve the issue.


Why does it ALL have to happen in my machine?! Seriously, this is not even my super-sucky original machine. It's a machine from my bro. Does the linux universe hate me or what?!

tinypliny - 12/17/11 23:44
I followed that thread to the bugzilla on kernels: :::link:::

Its apparently not a bios issue anymore. Its now seen as an issue with how the kernel handling CPU and GPU loads in intel chips with a sandy bridge processor. They made a patch for it, but now are worried how it would affect performance on these chips.

So if /var/log/messages claims its a hardware issue, it might not really be true and might actually be about how the new kernel is treating the CPU/GPU. Confusion ++

tinypliny - 12/17/11 22:46
Not that the productivity ruining freezes are not serious, but the freezes don't seem to be near these bios related hardware thermal problems...
tinypliny - 12/17/11 22:45
With my fabulous luck, what if I run into one of these issues with the new BIOS: :::link:::

I am wondering if it might not be a safer bet to live these thermal issues (or non-issues) rather than inherit some really serious problems...
tinypliny - 12/17/11 22:41
Btw, I posted that VLC related error in the earlier post. Something connected with LIRC.
tinypliny - 12/17/11 22:38
I have had this issue for quite a while. He didn't run into it. I am updating my bios as soon as I can (if there is an update, that is).

How about the other 1000 errors that are not connected to this particular error? :) The bios related error was a whole 3 hours before the freeze actually happened. The errors with the freeze (and around that pointframe) have no mentions of any thermal problems. They seem to be glitches in how fedora is handling mounted drives.
paul - 12/17/11 21:39
Oh I have the latest bios firmware on my laptops. However, if your bios is trigger thermal events it really is not fedora's fault. I never though to mention that but it does seem to be related to a hardware issue "Hardware event. This is not a software error." I guess that's a good thing in a way. There is also the possibility that you device is truly having thermal issues. Did you brother not run into this?