LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Fedora
User Name
Password
Fedora This forum is for the discussion of the Fedora Project.

Notices

Reply
 
Search this Thread
Old 12-20-2011, 10:07 PM   #1
Yoshimitsuspeed
Member
 
Registered: Apr 2006
Distribution: FC6
Posts: 78

Rep: Reputation: 15
FC16 rebooting


Haven't posted here in a while. Last couple times I have looked for help on the fedora forums has been really disheartening.

I'll just past my post from my other thread

http://forums.fedoraforum.org/showthread.php?t=273577

First thread. Got some answeres but it didn't go anywhere.
http://forums.fedoraforum.org/showthread.php?t=271582


Quick rundown. FC14 boots and runs fine. FC16 beta worked fine. At some point it started randomly rebooting. I checked for logs, and ran memtest and nothing looks out of the ordinary. Temps and system monitors all look fine around the time of reboots.
Once after installing the latest FC16 it worked fine for a couple days. The last time it worked fine for about a day. However after the first reboot it would do it pretty quickly after startup.
Don't understand what could be going on.
Z68 mobo and 2600k processor.

Just found this bug. Sounds just like mine.

https://bugzilla.redhat.com/show_bug.cgi?id=755578
 
Old 12-20-2011, 10:15 PM   #2
John VV
Guru
 
Registered: Aug 2005
Posts: 13,024

Rep: Reputation: 1740Reputation: 1740Reputation: 1740Reputation: 1740Reputation: 1740Reputation: 1740Reputation: 1740Reputation: 1740Reputation: 1740Reputation: 1740Reputation: 1740
what is in the error logs ?
is the fan working ? ( as in is it overheating )

Are you running gnome3 or KDE or xfce or something else ?

Have you opened up the computer and reset all the cables .
They can come loose sometimes .
 
Old 12-20-2011, 10:21 PM   #3
Yoshimitsuspeed
Member
 
Registered: Apr 2006
Distribution: FC6
Posts: 78

Original Poster
Rep: Reputation: 15
Error log stuff is in the second link I posted. The one I was told to check was check /var/log/messages and nothing looked too unusual.
Quote:
So last night I logged in under Gnome and ran updates then logged into KDE. It ran all night without a problem and I thought it was fixed. Tonight it has been crashing again and crashed last under Gnome.

This is the Log/messages from the last login to the crash.

Nov 2 22:49:53 Tetsu dbus[901]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper)
Nov 2 22:49:53 Tetsu dbus-daemon[901]: dbus[901]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper)
Nov 2 22:49:53 Tetsu dbus-daemon[901]: Launching FprintObject
Nov 2 22:49:53 Tetsu dbus[901]: [system] Successfully activated service 'net.reactivated.Fprint'
Nov 2 22:49:53 Tetsu dbus-daemon[901]: dbus[901]: [system] Successfully activated service 'net.reactivated.Fprint'
Nov 2 22:49:53 Tetsu dbus-daemon[901]: ** Message: D-Bus service launched with name: net.reactivated.Fprint
Nov 2 22:49:53 Tetsu dbus-daemon[901]: ** Message: entering main loop
Nov 2 22:49:53 Tetsu dbus-daemon[901]: dbus[901]: [system] Activating via systemd: service name='org.freedesktop.ConsoleKit' unit='console-kit-daemon.service'
Nov 2 22:49:53 Tetsu dbus[901]: [system] Activating via systemd: service name='org.freedesktop.ConsoleKit' unit='console-kit-daemon.service'
Nov 2 22:49:53 Tetsu dbus[901]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'
Nov 2 22:49:53 Tetsu dbus-daemon[901]: dbus[901]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'
Nov 2 22:49:53 Tetsu systemd-logind[883]: New user yoshi logged in.
Nov 2 22:49:53 Tetsu systemd-logind[883]: New session 1 of user yoshi.
Nov 2 22:49:53 Tetsu systemd-logind[883]: Linked /tmp/.X11-unix/X0 to /run/user/yoshi/X11/display.
Nov 2 22:49:53 Tetsu kernel: [ 519.998330] fuse init (API version 7.17)
Nov 2 22:49:53 Tetsu systemd[1]: sys-fs-fuse-connections.mount mount process exited, code=exited status=32
Nov 2 22:49:54 Tetsu dbus-daemon[901]: dbus[901]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service'
Nov 2 22:49:54 Tetsu dbus[901]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service'
Nov 2 22:49:54 Tetsu dbus[901]: [system] Activating service name='org.freedesktop.UPower' (using servicehelper)
Nov 2 22:49:54 Tetsu dbus-daemon[901]: dbus[901]: [system] Activating service name='org.freedesktop.UPower' (using servicehelper)
Nov 2 22:49:54 Tetsu dbus[901]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Nov 2 22:49:54 Tetsu dbus-daemon[901]: dbus[901]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Nov 2 22:49:54 Tetsu dbus[901]: [system] Successfully activated service 'org.freedesktop.UPower'
Nov 2 22:49:54 Tetsu dbus-daemon[901]: dbus[901]: [system] Successfully activated service 'org.freedesktop.UPower'
Nov 3 04:49:54 Tetsu rtkit-daemon[1340]: Successfully made thread 1339 of process 1339 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
Nov 2 22:49:54 Tetsu pulseaudio[1339]: pid.c: Stale PID file, overwriting.
Nov 3 04:49:54 Tetsu rtkit-daemon[1340]: Successfully made thread 1363 of process 1339 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
Nov 3 04:49:54 Tetsu rtkit-daemon[1340]: Successfully made thread 1364 of process 1339 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
Nov 2 22:49:54 Tetsu dbus[901]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Nov 2 22:49:54 Tetsu dbus-daemon[901]: dbus[901]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Nov 2 22:49:54 Tetsu dbus[901]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details.
Nov 2 22:49:54 Tetsu dbus-daemon[901]: dbus[901]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details.
Nov 2 22:49:54 Tetsu pulseaudio[1339]: bluetooth-util.c: Error from ListAdapters reply: org.freedesktop.systemd1.LoadFailed
Nov 2 22:49:55 Tetsu NetworkManager[857]: (NetworkManager:857): GLib-GIO-WARNING **: Missing callback called fullpath = /var/run/ConsoleKit/database
Nov 2 22:49:56 Tetsu dbus[901]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
Nov 2 22:49:56 Tetsu dbus-daemon[901]: dbus[901]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
Nov 2 22:49:56 Tetsu dbus[901]: [system] Activating service name='org.freedesktop.UDisks' (using servicehelper)
Nov 2 22:49:56 Tetsu dbus-daemon[901]: dbus[901]: [system] Activating service name='org.freedesktop.UDisks' (using servicehelper)
Nov 2 22:49:56 Tetsu dbus[901]: [system] Successfully activated service 'org.freedesktop.UDisks'
Nov 2 22:49:56 Tetsu dbus-daemon[901]: dbus[901]: [system] Successfully activated service 'org.freedesktop.UDisks'
Nov 2 22:49:56 Tetsu dbus[901]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Nov 2 22:49:56 Tetsu dbus-daemon[901]: dbus[901]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Nov 2 22:49:56 Tetsu dbus-daemon[901]: dbus[901]: [system] Activating service name='org.freedesktop.ColorManager' (using servicehelper)
Nov 2 22:49:56 Tetsu dbus[901]: [system] Activating service name='org.freedesktop.ColorManager' (using servicehelper)
Nov 2 22:49:56 Tetsu dbus[901]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Nov 2 22:49:56 Tetsu dbus-daemon[901]: dbus[901]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Nov 2 22:49:57 Tetsu goa[1523]: goa-daemon version 3.2.1 starting [main.c:112, main()]
Nov 2 22:49:57 Tetsu dbus[901]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Nov 2 22:49:57 Tetsu dbus[901]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details.
Nov 2 22:49:57 Tetsu dbus[901]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Nov 2 22:49:57 Tetsu dbus-daemon[901]: dbus[901]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Nov 2 22:49:57 Tetsu dbus[901]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details.
Nov 2 22:49:57 Tetsu dbus-daemon[901]: dbus[901]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details.
Nov 2 22:49:57 Tetsu dbus-daemon[901]: dbus[901]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Nov 2 22:49:57 Tetsu dbus-daemon[901]: dbus[901]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details.
Nov 2 22:49:58 Tetsu kernel: [ 524.249589] lp: driver loaded but no devices found
Nov 2 22:49:58 Tetsu udev-configure-printer: Failed to get parent
Nov 2 22:49:58 Tetsu kernel: [ 524.256806] ppdev: user-space parallel port driver
Nov 2 22:49:58 Tetsu dbus[901]: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit='accounts-daemon.service'
Nov 2 22:49:58 Tetsu dbus-daemon[901]: dbus[901]: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit='accounts-daemon.service'
Nov 2 22:49:58 Tetsu dbus[901]: [system] Successfully activated service 'org.freedesktop.Accounts'
Nov 2 22:49:58 Tetsu dbus-daemon[901]: dbus[901]: [system] Successfully activated service 'org.freedesktop.Accounts'
Nov 2 22:49:58 Tetsu accounts-daemon[1552]: started daemon version 0.6.14
Nov 2 22:50:23 Tetsu dbus-daemon[901]: ** Message: No devices in use, exit
Nov 2 22:50:31 Tetsu dbus[901]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper)
Nov 2 22:50:31 Tetsu dbus-daemon[901]: dbus[901]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper)
Nov 2 22:50:31 Tetsu dbus-daemon[901]: Launching FprintObject
Nov 2 22:50:31 Tetsu dbus[901]: [system] Successfully activated service 'net.reactivated.Fprint'
Nov 2 22:50:31 Tetsu dbus-daemon[901]: dbus[901]: [system] Successfully activated service 'net.reactivated.Fprint'
Nov 2 22:50:31 Tetsu dbus-daemon[901]: ** Message: D-Bus service launched with name: net.reactivated.Fprint
Nov 2 22:50:31 Tetsu dbus-daemon[901]: ** Message: entering main loop
Nov 2 22:51:02 Tetsu dbus-daemon[901]: ** Message: No devices in use, exit
Quote:
Here's the last couple min of a previous session I believe auto shut down.

Nov 2 22:21:00 Tetsu dbus[910]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service'
Nov 2 22:21:00 Tetsu dbus-daemon[910]: dbus[910]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service'
Nov 2 22:21:00 Tetsu dbus[910]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Nov 2 22:21:00 Tetsu dbus-daemon[910]: dbus[910]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Nov 3 04:21:00 Tetsu rtkit-daemon[1510]: Successfully made thread 1509 of process 1509 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
Nov 2 22:21:00 Tetsu pulseaudio[1509]: pid.c: Stale PID file, overwriting.
Nov 3 04:21:00 Tetsu rtkit-daemon[1510]: Successfully made thread 1515 of process 1509 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
Nov 3 04:21:00 Tetsu rtkit-daemon[1510]: Successfully made thread 1517 of process 1509 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
Nov 2 22:21:00 Tetsu dbus[910]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Nov 2 22:21:00 Tetsu dbus-daemon[910]: dbus[910]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Nov 2 22:21:00 Tetsu dbus[910]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details.
Nov 2 22:21:00 Tetsu dbus-daemon[910]: dbus[910]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details.
Nov 2 22:21:00 Tetsu pulseaudio[1509]: bluetooth-util.c: Error from ListAdapters reply: org.freedesktop.systemd1.LoadFailed
Nov 3 04:21:01 Tetsu rtkit-daemon[1510]: Successfully made thread 1544 of process 1544 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
Nov 2 22:21:01 Tetsu pulseaudio[1544]: pid.c: Daemon already running.
Nov 3 04:21:01 Tetsu rtkit-daemon[1510]: Successfully made thread 1553 of process 1553 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
Nov 2 22:21:01 Tetsu pulseaudio[1553]: pid.c: Daemon already running.
Nov 2 22:21:06 Tetsu pulseaudio[1509]: alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write!
Nov 2 22:21:06 Tetsu pulseaudio[1509]: alsa-sink.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
Nov 2 22:21:06 Tetsu pulseaudio[1509]: alsa-sink.c: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Nov 2 22:21:13 Tetsu dbus[910]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
Nov 2 22:21:13 Tetsu dbus-daemon[910]: dbus[910]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
Nov 2 22:21:13 Tetsu chronyd[900]: Selected source 24.124.0.251
Nov 2 22:21:13 Tetsu dbus[910]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Nov 2 22:21:13 Tetsu dbus-daemon[910]: dbus[910]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Nov 2 22:21:15 Tetsu chronyd[900]: Selected source 64.73.32.135
Nov 2 22:21:16 Tetsu kernel: [ 44.331827] TCP lp registered
Nov 2 22:21:24 Tetsu dbus-daemon[910]: ** Message: No devices in use, exit
Nov 2 22:21:27 Tetsu yum[1789]: Updated: rpmfusion-free-release-16-1.1.noarch
Nov 2 22:21:27 Tetsu yum[1789]: Updated: rpmfusion-nonfree-release-16-1.1.noarch
Nov 2 22:21:40 Tetsu nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/11-dhclient' exited with error status 1.
Nov 2 22:22:41 Tetsu systemd[1]: Startup finished in 1s 666ms 66us (kernel) + 2s 29ms 561us (initrd) + 2min 5s 51ms 677us (userspace) = 2min 8s 747ms 304us.

---------- Post added at 11:10 PM ---------- Previous post was at 11:06 PM ----------

This one seems common shortly before big skips in the timeline indicating a restart.
Nov 2 22:49:57 Tetsu dbus[901]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Nov 2 22:49:57 Tetsu dbus[901]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details.
Nov 2 22:49:57 Tetsu dbus[901]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Nov 2 22:49:57 Tetsu dbus-daemon[901]: dbus[901]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Nov 2 22:49:57 Tetsu dbus[901]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details.
Nov 2 22:49:57 Tetsu dbus-daemon[901]: dbus[901]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details.
Nov 2 22:49:57 Tetsu dbus-daemon[901]: dbus[901]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Nov 2 22:49:57 Tetsu dbus-daemon[901]: dbus[901]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load:
Edit/Delete Message
Quote:
Originally Posted by AdamW View Post
the dbus bluez message is pretty harmless. there's no obvious culprit there that I can see does the system feel like it's getting very hot perhaps?
 
Old 12-20-2011, 10:23 PM   #4
Yoshimitsuspeed
Member
 
Registered: Apr 2006
Distribution: FC6
Posts: 78

Original Poster
Rep: Reputation: 15
Happens in KDE and in Gnome. Original install was KDE. One time it rebooted in the live image on the USB stick before even getting to the install.
All fans are working, system monitors show all things normal. Everything works fine in fedora 14.
 
Old 12-20-2011, 11:58 PM   #5
John VV
Guru
 
Registered: Aug 2005
Posts: 13,024

Rep: Reputation: 1740Reputation: 1740Reputation: 1740Reputation: 1740Reputation: 1740Reputation: 1740Reputation: 1740Reputation: 1740Reputation: 1740Reputation: 1740Reputation: 1740
I would start with getting ride of the errors anyway
yes the bluetooth one looks like a harmless one ,but ????

turn off services that are not in use ( good security practice anyway)

you are not using any bluetooth devices so turn that startup service off

removing error massages also might show other things
Quote:
Nov 2 22:49:58 Tetsu udev-configure-printer: Failed to get parent
is there a printer connected ? or is it powered down ?
 
Old 12-21-2011, 12:11 AM   #6
Yoshimitsuspeed
Member
 
Registered: Apr 2006
Distribution: FC6
Posts: 78

Original Poster
Rep: Reputation: 15
I'll try that and see what happens.

I'm pretty sure the printer was disconnected.
 
Old 12-21-2011, 12:22 AM   #7
John VV
Guru
 
Registered: Aug 2005
Posts: 13,024

Rep: Reputation: 1740Reputation: 1740Reputation: 1740Reputation: 1740Reputation: 1740Reputation: 1740Reputation: 1740Reputation: 1740Reputation: 1740Reputation: 1740Reputation: 1740
I have found ,over the years, that the very first thing i do in setting up a system is remove all the warnings from the logs
that way when something dose go wrong ,it is a bit easier to find .

And with fedora things will go a bit wrong a bit more often than other OS's .
 
Old 12-21-2011, 12:54 AM   #8
Yoshimitsuspeed
Member
 
Registered: Apr 2006
Distribution: FC6
Posts: 78

Original Poster
Rep: Reputation: 15
Ok I unchecked a few services that were easy to tell. I also did an update, been running for a while with no problems yet.

Should I uncheck any of the following services?

Drive ejector
ObexFTP
Input Actions
Network Status
Display Management change monitor
free space notifier
Keyboard Daemon
Remote URL Change Notifier
Nepomuk Search Module
NetworkManager User Settings Service

I'm also still getting
Quote:
Dec 20 23:36:18 Tetsu dbus[912]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Dec 20 23:36:18 Tetsu dbus-daemon[912]: dbus[912]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Dec 20 23:36:18 Tetsu dbus[912]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details.
Dec 20 23:36:18 Tetsu dbus-daemon[912]: dbus[912]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details.
Dec 20 23:36:18 Tetsu pulseaudio[1401]: bluetooth-util.c: Error from ListAdapters reply: org.freedesktop.systemd1.LoadFailed
 
Old 12-21-2011, 08:39 PM   #9
Yoshimitsuspeed
Member
 
Registered: Apr 2006
Distribution: FC6
Posts: 78

Original Poster
Rep: Reputation: 15
It worked fine all night last night. Tonight it ran for about 5 min then rebooted.
Here's the last couple min of var/log/messages

Quote:
21 19:23:02 Tetsu dbus[908]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Dec 21 19:23:02 Tetsu dbus-daemon[908]: dbus[908]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Dec 21 19:23:02 Tetsu dbus[908]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details.
Dec 21 19:23:02 Tetsu dbus-daemon[908]: dbus[908]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details.
Dec 21 19:23:02 Tetsu pulseaudio[1365]: bluetooth-util.c: Error from ListAdapters reply: org.freedesktop.systemd1.LoadFailed
Dec 22 02:23:02 Tetsu rtkit-daemon[1368]: Successfully made thread 1438 of process 1438 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
Dec 21 19:23:02 Tetsu pulseaudio[1438]: pid.c: Daemon already running.
Dec 22 02:23:02 Tetsu rtkit-daemon[1368]: Successfully made thread 1439 of process 1439 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
Dec 21 19:23:02 Tetsu pulseaudio[1439]: pid.c: Daemon already running.
Dec 21 19:23:25 Tetsu dbus-daemon[908]: ** Message: No devices in use, exit
Dec 21 19:23:27 Tetsu systemd[1]: Startup finished in 1s 652ms 172us (kernel) + 1s 909ms 845us (initrd) + 1min 7s 157ms 831us (userspace) = 1min 10s 719ms 848us.
Dec 21 19:24:02 Tetsu chronyd[904]: Selected source 69.65.40.29
Dec 21 19:25:07 Tetsu dbus[908]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper)
Dec 21 19:25:07 Tetsu dbus-daemon[908]: dbus[908]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper)
Dec 21 19:25:07 Tetsu dbus-daemon[908]: Launching FprintObject
Dec 21 19:25:07 Tetsu dbus[908]: [system] Successfully activated service 'net.reactivated.Fprint'
Dec 21 19:25:07 Tetsu dbus-daemon[908]: dbus[908]: [system] Successfully activated service 'net.reactivated.Fprint'
Dec 21 19:25:07 Tetsu dbus-daemon[908]: ** Message: D-Bus service launched with name: net.reactivated.Fprint
Dec 21 19:25:07 Tetsu dbus-daemon[908]: ** Message: entering main loop
Dec 21 19:25:16 Tetsu kernel: [ 180.176355] EXT4-fs (sdb2): mounted filesystem with ordered data mode. Opts: (null)
Dec 21 19:25:38 Tetsu dbus-daemon[908]: ** Message: No devices in use, exit
 
Old 12-26-2011, 10:41 PM   #10
Yoshimitsuspeed
Member
 
Registered: Apr 2006
Distribution: FC6
Posts: 78

Original Poster
Rep: Reputation: 15
Really no other ideas?
 
Old 12-26-2011, 11:50 PM   #11
John VV
Guru
 
Registered: Aug 2005
Posts: 13,024

Rep: Reputation: 1740Reputation: 1740Reputation: 1740Reputation: 1740Reputation: 1740Reputation: 1740Reputation: 1740Reputation: 1740Reputation: 1740Reputation: 1740Reputation: 1740
It dose sound like a hardware issue

clean logs so it's " look for a horse and not a zebra " time .

most of the time on a non windows box a random reboot is hardware overheating
open up the box
take a vac to it
unplug and plug back in all the connections .

if a nvidia card turn on the GPU temp monitor
 
Old 12-27-2011, 11:00 AM   #12
Yoshimitsuspeed
Member
 
Registered: Apr 2006
Distribution: FC6
Posts: 78

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by John VV View Post
It dose sound like a hardware issue

clean logs so it's " look for a horse and not a zebra " time .

most of the time on a non windows box a random reboot is hardware overheating
open up the box
take a vac to it
unplug and plug back in all the connections .

if a nvidia card turn on the GPU temp monitor
It's a brand new computer other than the PSU. The weird thing is that it works perfectly running FC14. If it was overheating isn't it the BIOS that would cause it to reboot? If that were the case the problem should be the same in FC14 right?
FC14 is on a different HD and the new HD is a solid state which I have heard seem to tend to have more problems however I feel I have ruled that out since it rebooted on the USB install stick one time. I might just have to try to install FC15 or ubuntu or something different just to see if that fixes it.
 
Old 12-27-2011, 09:12 PM   #13
Yoshimitsuspeed
Member
 
Registered: Apr 2006
Distribution: FC6
Posts: 78

Original Poster
Rep: Reputation: 15
Here is something interesting. It just rebooted and when it did right after grub it threw an error, something about a problem with several of the cores. When I logged in the fans were screaming. When I opened up system monitor it only showed cores 1 at 0% 5 at 200% and 8 at 300%. I rebooted and everything shows normal, 8 cores all running fine and minimal load. Averaging about 2%

I also reinstalled lm-sensors and everything looks fine. All temps in the mid 30s except my Nvidia card which hangs in the mid 50s.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] FC16 x86_64 - Radeon display connector DVI-D-1: No monitor connected or invalid EDID coolsg5636 Linux - Newbie 6 12-15-2011 10:45 AM
[SOLVED] fakenes not installing on fc16 frieza Linux - Games 3 12-10-2011 11:55 PM
[SOLVED] FC14 to FC16 disaster tethysgods Linux - Newbie 11 12-07-2011 01:50 PM
rebooting spuppett Linux - Newbie 3 04-11-2004 04:21 PM
rebooting into a different OS apberzerk Linux - General 2 02-04-2004 07:42 AM


All times are GMT -5. The time now is 08:14 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration