after two hours of operation my Fedora 15 shuts down and system reboots byitself suddenly: I was thinking that it was at the end of his life, but I noticed after rebooting that I was already logged as user and I got a message about Selinux stating that some cups/backend/hp could not write somewhere (I deleted the message by mistake).Any comment?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 09/22/2011 03:42 PM, antonio montagnani wrote:
after two hours of operation my Fedora 15 shuts down and system reboots byitself suddenly: I was thinking that it was at the end of his life, but I noticed after rebooting that I was already logged as user and I got a message about Selinux stating that some cups/backend/hp could not write somewhere (I deleted the message by mistake).Any comment?
Sounds like a kernel issue or hardware, overheating. I doubt this is an SELinux issue. I would look in the /var/log/messages for indication of why the system is going down.
Daniel J Walsh ha scritto / said the following il giorno/on 22/09/2011 21:56:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 09/22/2011 03:42 PM, antonio montagnani wrote:
after two hours of operation my Fedora 15 shuts down and system reboots byitself suddenly: I was thinking that it was at the end of his life, but I noticed after rebooting that I was already logged as user and I got a message about Selinux stating that some cups/backend/hp could not write somewhere (I deleted the message by mistake).Any comment?
Sounds like a kernel issue or hardware, overheating. I doubt this is an SELinux issue. I would look in the /var/log/messages for indication of why the system is going down. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk57kv8ACgkQrlYvE4MpobNWsQCggIw7lbrBDDFcaIUzWbYmbTbt s0sAoKMi5sEE+3R4SVMsKlmwmW3P005a =DPzk -----END PGP SIGNATURE-----
This is tthe kernel message about Selinux:
SELinux is preventing /usr/lib/cups/backend/hp from read access on the chr_file 044. For complete SELinux messages. run sealert -l b826ab3e-5b7c-4b13-84b3-cfa77eb8e7b2
and this is the messages file and the crash happened between these lines
Sep 22 20:42:10 localhost python: io/hpmud/pp.c 627: unable to read device-id ret=-1 Sep 22 20:42:10 localhost udev-configure-printer: no corresponding CUPS device found Sep 22 20:42:12 localhost setroubleshoot: SELinux is preventing /usr/lib/cups/backend/hp from read access on the chr_file 044. For complete SELinux messages. run sealert -l b826ab3e-5b7c-4b13-84b3-cfa77eb8e7b2 Sep 22 20:42:14 localhost setroubleshoot: SELinux is preventing /usr/lib/cups/backend/hp from read access on the chr_file 044. For complete SELinux messages. run sealert -l b826ab3e-5b7c-4b13-84b3-cfa77eb8e7b2 Sep 22 20:49:30 localhost kernel: [ 5538.231226] [drm] nouveau 0000:01:00.0: Setting dpms mode 0 on vga encoder (output 0) Sep 22 21:04:25 localhost kernel: [ 6433.067959] [drm] nouveau 0000:01:00.0: Setting dpms mode 3 on vga encoder (output 0) Sep 22 21:09:15 localhost dbus: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) Sep 22 21:09:15 localhost dbus: [system] Successfully activated service 'org.freedesktop.PackageKit' Sep 22 21:12:06 localhost kernel: [ 6894.301934] [drm] nouveau 0000:01:00.0: Setting dpms mode 0 on vga encoder (output 0) Sep 22 21:18:39 localhost kernel: imklog 5.8.2, log source = /proc/kmsg started. Sep 22 21:18:39 localhost rsyslogd: [origin software="rsyslogd" swVersion="5.8.2" x-pid="739" x-info="http://www.rsyslog.com"] start Sep 22 21:18:39 localhost kernel: [ 0.000000] Initializing cgroup subsys cpuset Sep 22 21:18:39 localhost kernel: [ 0.000000] Initializing cgroup subsys cpu Sep 22 21:18:39 localhost kernel: [ 0.000000] Linux version 2.6.40.4-5.fc15.i686.PAE (mockbuild@x86-14.phx2.fedoraproject.org) (gcc version 4.6.0 20110603 (Red Hat 4.6.0-10) (GCC) ) #1 SMP Tue Aug 30 14:43:52 UTC 2011 Sep 22 21:18:39 localhost kernel: [ 0.000000] BIOS-provided physical RAM map: Sep 22 21:18:39 localhost kernel: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable) Sep 22 21:18:39 localhost kernel: [ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved) Sep 22 21:18:39 localhost kernel: [ 0.000000] BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
butfrom sensors I get
sensors atk0110-acpi-0 Adapter: ACPI interface Vcore Voltage: +1.37 V (min = +1.45 V, max = +1.75 V) +3.3 Voltage: +1.60 V (min = +3.00 V, max = +3.60 V) +5.0 Voltage: +1.62 V (min = +4.50 V, max = +5.50 V) +12.0 Voltage: +11.98 V (min = +11.20 V, max = +13.20 V) CPU FAN Speed: 3068 RPM (min = 0 RPM) CHASSIS FAN Speed: 2410 RPM (min = 0 RPM) CPU Temperature: +50.0°C (high = +90.0°C, crit = +125.0°C) MB Temperature: +46.0°C (high = +70.0°C, crit = +125.0°C) Power Temperature: +123.0°C (high = +80.0°C, crit = +125.0°C)
w83627ehf-isa-0290 Adapter: ISA adapter Vcore: +1.37 V (min = +0.00 V, max = +1.85 V) in1: +1.82 V (min = +0.00 V, max = +0.03 V) ALARM AVCC: +3.22 V (min = +0.00 V, max = +0.00 V) ALARM +3.3V: +3.20 V (min = +0.00 V, max = +0.06 V) ALARM in4: +2.04 V (min = +0.00 V, max = +0.00 V) ALARM in5: +1.62 V (min = +0.00 V, max = +0.00 V) ALARM in6: +1.97 V (min = +0.00 V, max = +0.00 V) ALARM 3VSB: +3.18 V (min = +0.00 V, max = +0.00 V) ALARM Vbat: +0.00 V (min = +0.00 V, max = +0.00 V) in9: +1.35 V (min = +0.00 V, max = +0.00 V) ALARM fan1: 2410 RPM (min = 168750 RPM, div = 4) ALARM fan2: 3068 RPM (min = 0 RPM, div = 2) ALARM fan3: 0 RPM (min = 164 RPM, div = 128) ALARM fan5: 0 RPM (min = 0 RPM, div = 4) temp1: +46.0°C (high = +0.0°C, hyst = +0.0°C) ALARM sensor = thermistor temp2: +50.0°C (high = +80.0°C, hyst = +75.0°C) sensor = diode temp3: +123.5°C (high = +80.0°C, hyst = +75.0°C) ALARM sensor = thermistor
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 09/22/2011 04:08 PM, antonio montagnani wrote:
Daniel J Walsh ha scritto / said the following il giorno/on 22/09/2011 21:56: On 09/22/2011 03:42 PM, antonio montagnani wrote:
after two hours of operation my Fedora 15 shuts down and system reboots byitself suddenly: I was thinking that it was at the end of his life, but I noticed after rebooting that I was already logged as user and I got a message about Selinux stating that some cups/backend/hp could not write somewhere (I deleted the message by mistake).Any comment?
Sounds like a kernel issue or hardware, overheating. I doubt this is an SELinux issue. I would look in the /var/log/messages for indication of why the system is going down.
This is tthe kernel message about Selinux:
SELinux is preventing /usr/lib/cups/backend/hp from read access on the chr_file 044. For complete SELinux messages. run sealert -l b826ab3e-5b7c-4b13-84b3-cfa77eb8e7b2
and this is the messages file and the crash happened between these lines
Sep 22 20:42:10 localhost python: io/hpmud/pp.c 627: unable to read device-id ret=-1 Sep 22 20:42:10 localhost udev-configure-printer: no corresponding CUPS device found Sep 22 20:42:12 localhost setroubleshoot: SELinux is preventing /usr/lib/cups/backend/hp from read access on the chr_file 044. For complete SELinux messages. run sealert -l b826ab3e-5b7c-4b13-84b3-cfa77eb8e7b2 Sep 22 20:42:14 localhost setroubleshoot: SELinux is preventing /usr/lib/cups/backend/hp from read access on the chr_file 044. For complete SELinux messages. run sealert -l b826ab3e-5b7c-4b13-84b3-cfa77eb8e7b2 Sep 22 20:49:30 localhost kernel: [ 5538.231226] [drm] nouveau 0000:01:00.0: Setting dpms mode 0 on vga encoder (output 0) Sep 22 21:04:25 localhost kernel: [ 6433.067959] [drm] nouveau 0000:01:00.0: Setting dpms mode 3 on vga encoder (output 0) Sep 22 21:09:15 localhost dbus: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) Sep 22 21:09:15 localhost dbus: [system] Successfully activated service 'org.freedesktop.PackageKit' Sep 22 21:12:06 localhost kernel: [ 6894.301934] [drm] nouveau 0000:01:00.0: Setting dpms mode 0 on vga encoder (output 0) Sep 22 21:18:39 localhost kernel: imklog 5.8.2, log source = /proc/kmsg started. Sep 22 21:18:39 localhost rsyslogd: [origin software="rsyslogd" swVersion="5.8.2" x-pid="739" x-info="http://www.rsyslog.com"] start Sep 22 21:18:39 localhost kernel: [ 0.000000] Initializing cgroup subsys cpuset Sep 22 21:18:39 localhost kernel: [ 0.000000] Initializing cgroup subsys cpu Sep 22 21:18:39 localhost kernel: [ 0.000000] Linux version 2.6.40.4-5.fc15.i686.PAE (mockbuild@x86-14.phx2.fedoraproject.org) (gcc version 4.6.0 20110603 (Red Hat 4.6.0-10) (GCC) ) #1 SMP Tue Aug 30 14:43:52 UTC 2011 Sep 22 21:18:39 localhost kernel: [ 0.000000] BIOS-provided physical RAM map: Sep 22 21:18:39 localhost kernel: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable) Sep 22 21:18:39 localhost kernel: [ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved) Sep 22 21:18:39 localhost kernel: [ 0.000000] BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
butfrom sensors I get
sensors atk0110-acpi-0 Adapter: ACPI interface Vcore Voltage: +1.37 V (min = +1.45 V, max = +1.75 V) +3.3 Voltage: +1.60 V (min = +3.00 V, max = +3.60 V) +5.0 Voltage: +1.62 V (min = +4.50 V, max = +5.50 V) +12.0 Voltage: +11.98 V (min = +11.20 V, max = +13.20 V) CPU FAN Speed: 3068 RPM (min = 0 RPM) CHASSIS FAN Speed: 2410 RPM (min = 0 RPM) CPU Temperature: +50.0°C (high = +90.0°C, crit = +125.0°C) MB Temperature: +46.0°C (high = +70.0°C, crit = +125.0°C) Power Temperature: +123.0°C (high = +80.0°C, crit = +125.0°C)
w83627ehf-isa-0290 Adapter: ISA adapter Vcore: +1.37 V (min = +0.00 V, max = +1.85 V) in1: +1.82 V (min = +0.00 V, max = +0.03 V) ALARM AVCC: +3.22 V (min = +0.00 V, max = +0.00 V) ALARM +3.3V: +3.20 V (min = +0.00 V, max = +0.06 V) ALARM in4: +2.04 V (min = +0.00 V, max = +0.00 V) ALARM in5: +1.62 V (min = +0.00 V, max = +0.00 V) ALARM in6: +1.97 V (min = +0.00 V, max = +0.00 V) ALARM 3VSB: +3.18 V (min = +0.00 V, max = +0.00 V) ALARM Vbat: +0.00 V (min = +0.00 V, max = +0.00 V) in9: +1.35 V (min = +0.00 V, max = +0.00 V) ALARM fan1: 2410 RPM (min = 168750 RPM, div = 4) ALARM fan2: 3068 RPM (min = 0 RPM, div = 2) ALARM fan3: 0 RPM (min = 164 RPM, div = 128) ALARM fan5: 0 RPM (min = 0 RPM, div = 4) temp1: +46.0°C (high = +0.0°C, hyst = +0.0°C) ALARM sensor = thermistor temp2: +50.0°C (high = +80.0°C, hyst = +75.0°C) sensor = diode temp3: +123.5°C (high = +80.0°C, hyst = +75.0°C) ALARM sensor = thermistor
Daniel J Walsh ha scritto / said the following il giorno/on 22/09/2011 22:13:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 09/22/2011 04:08 PM, antonio montagnani wrote:
Daniel J Walsh ha scritto / said the following il giorno/on 22/09/2011 21:56: On 09/22/2011 03:42 PM, antonio montagnani wrote:
after two hours of operation my Fedora 15 shuts down and system reboots byitself suddenly: I was thinking that it was at the end of his life, but I noticed after rebooting that I was already logged as user and I got a message about Selinux stating that some cups/backend/hp could not write somewhere (I deleted the message by mistake).Any comment?
Sounds like a kernel issue or hardware, overheating. I doubt this is an SELinux issue. I would look in the /var/log/messages for indication of why the system is going down.
This is tthe kernel message about Selinux:
SELinux is preventing /usr/lib/cups/backend/hp from read access on the chr_file 044. For complete SELinux messages. run sealert -l b826ab3e-5b7c-4b13-84b3-cfa77eb8e7b2
and this is the messages file and the crash happened between these lines
Sep 22 20:42:10 localhost python: io/hpmud/pp.c 627: unable to read device-id ret=-1 Sep 22 20:42:10 localhost udev-configure-printer: no corresponding CUPS device found Sep 22 20:42:12 localhost setroubleshoot: SELinux is preventing /usr/lib/cups/backend/hp from read access on the chr_file 044. For complete SELinux messages. run sealert -l b826ab3e-5b7c-4b13-84b3-cfa77eb8e7b2 Sep 22 20:42:14 localhost setroubleshoot: SELinux is preventing /usr/lib/cups/backend/hp from read access on the chr_file 044. For complete SELinux messages. run sealert -l b826ab3e-5b7c-4b13-84b3-cfa77eb8e7b2 Sep 22 20:49:30 localhost kernel: [ 5538.231226] [drm] nouveau 0000:01:00.0: Setting dpms mode 0 on vga encoder (output 0) Sep 22 21:04:25 localhost kernel: [ 6433.067959] [drm] nouveau 0000:01:00.0: Setting dpms mode 3 on vga encoder (output 0) Sep 22 21:09:15 localhost dbus: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) Sep 22 21:09:15 localhost dbus: [system] Successfully activated service 'org.freedesktop.PackageKit' Sep 22 21:12:06 localhost kernel: [ 6894.301934] [drm] nouveau 0000:01:00.0: Setting dpms mode 0 on vga encoder (output 0) Sep 22 21:18:39 localhost kernel: imklog 5.8.2, log source = /proc/kmsg started. Sep 22 21:18:39 localhost rsyslogd: [origin software="rsyslogd" swVersion="5.8.2" x-pid="739" x-info="http://www.rsyslog.com"] start Sep 22 21:18:39 localhost kernel: [ 0.000000] Initializing cgroup subsys cpuset Sep 22 21:18:39 localhost kernel: [ 0.000000] Initializing cgroup subsys cpu Sep 22 21:18:39 localhost kernel: [ 0.000000] Linux version 2.6.40.4-5.fc15.i686.PAE (mockbuild@x86-14.phx2.fedoraproject.org) (gcc version 4.6.0 20110603 (Red Hat 4.6.0-10) (GCC) ) #1 SMP Tue Aug 30 14:43:52 UTC 2011 Sep 22 21:18:39 localhost kernel: [ 0.000000] BIOS-provided physical RAM map: Sep 22 21:18:39 localhost kernel: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable) Sep 22 21:18:39 localhost kernel: [ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved) Sep 22 21:18:39 localhost kernel: [ 0.000000] BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
butfrom sensors I get
sensors atk0110-acpi-0 Adapter: ACPI interface Vcore Voltage: +1.37 V (min = +1.45 V, max = +1.75 V) +3.3 Voltage: +1.60 V (min = +3.00 V, max = +3.60 V) +5.0 Voltage: +1.62 V (min = +4.50 V, max = +5.50 V) +12.0 Voltage: +11.98 V (min = +11.20 V, max = +13.20 V) CPU FAN Speed: 3068 RPM (min = 0 RPM) CHASSIS FAN Speed: 2410 RPM (min = 0 RPM) CPU Temperature: +50.0°C (high = +90.0°C, crit = +125.0°C) MB Temperature: +46.0°C (high = +70.0°C, crit = +125.0°C) Power Temperature: +123.0°C (high = +80.0°C, crit = +125.0°C)
w83627ehf-isa-0290 Adapter: ISA adapter Vcore: +1.37 V (min = +0.00 V, max = +1.85 V) in1: +1.82 V (min = +0.00 V, max = +0.03 V) ALARM AVCC: +3.22 V (min = +0.00 V, max = +0.00 V) ALARM +3.3V: +3.20 V (min = +0.00 V, max = +0.06 V) ALARM in4: +2.04 V (min = +0.00 V, max = +0.00 V) ALARM in5: +1.62 V (min = +0.00 V, max = +0.00 V) ALARM in6: +1.97 V (min = +0.00 V, max = +0.00 V) ALARM 3VSB: +3.18 V (min = +0.00 V, max = +0.00 V) ALARM Vbat: +0.00 V (min = +0.00 V, max = +0.00 V) in9: +1.35 V (min = +0.00 V, max = +0.00 V) ALARM fan1: 2410 RPM (min = 168750 RPM, div = 4) ALARM fan2: 3068 RPM (min = 0 RPM, div = 2) ALARM fan3: 0 RPM (min = 164 RPM, div = 128) ALARM fan5: 0 RPM (min = 0 RPM, div = 4) temp1: +46.0°C (high = +0.0°C, hyst = +0.0°C) ALARM sensor = thermistor temp2: +50.0°C (high = +80.0°C, hyst = +75.0°C) sensor = diode temp3: +123.5°C (high = +80.0°C, hyst = +75.0°C) ALARM sensor = thermistor
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk57ltEACgkQrlYvE4MpobOengCfXd1zQsSS3nFkt+WS1X6FTmeu YHcAnjTbMiwJ0MJJ5L+PPBsVzL82LEXv =UgVD -----END PGP SIGNATURE-----
I miss your comment: but whyreboot starts with imklog?? Forgot to say that I am experiencing reboots ona rgularbasis, i.e. every two hours more or less
Joe Zeff ha scritto / said the following il giorno/on 22/09/2011 22:52:
On 09/22/2011 01:28 PM, antonio montagnani wrote:
I miss your comment: but whyreboot starts with imklog?? Forgot to say that I am experiencing reboots ona rgularbasis, i.e. every two hours more or less
That sounds like a hardware issue. Have you checked your fans?
yes, fans seems to work fine...
On 09/22/2011 01:54 PM, antoniomontagnani@gmail.com wrote:
yes, fans seems to work fine...
Good. That's one possibility eliminated. Somebody else mentioned the power supply for your box. Is it practical for you to swap a different one in to see if it makes a difference? Also, you might want to consider running memtest to make sure you don't have any dodgy RAM.
On Thu, 2011-09-22 at 22:54 +0200, antoniomontagnani@gmail.com wrote:
yes, fans seems to work fine...
I'll add the obvious: It's not enough that they spin, there has to be airflow through the heatsink that the fans blow across, and throughout the cabinet. Also, heatsinks need to make good physical contact with what they're attached too.
On 09/23/2011 03:42 AM, antonio montagnani wrote:
after two hours of operation my Fedora 15 shuts down and system reboots byitself suddenly: I was thinking that it was at the end of his life, but I noticed after rebooting that I was already logged as user and I got a message about Selinux stating that some cups/backend/hp could not write somewhere (I deleted the message by mistake).Any comment?
FWIW, several years ago I had a system that would spontaneously "reboot". More accurately, crash/restart. Nothing in the logs revealed anything of value. After a week of this, it finally crashed and stayed crashed. The culprit was the power supply.
Ed Greshko ha scritto / said the following il giorno/on 22/09/2011 22:35:
On 09/23/2011 03:42 AM, antonio montagnani wrote:
mment?
FWIW, several years ago I had a system that would spontaneously "reboot". More accurately, crash/restart. Nothing in the logs revealed anything of value. After a week of this, it finally crashed and stayed crashed. The culprit was the power supply.
you mean the main power supply, don't you??
Ed Greshko ha scritto / said the following il giorno/on 22/09/2011 22:35:
On 09/23/2011 03:42 AM, antonio montagnani wrote:
after two hours of operation my Fedora 15 shuts down and system reboots byitself suddenly: I was thinking that it was at the end of his life, but I noticed after rebooting that I was already logged as user and I got a message about Selinux stating that some cups/backend/hp could not write somewhere (I deleted the message by mistake).Any comment?
FWIW, several years ago I had a system that would spontaneously "reboot". More accurately, crash/restart. Nothing in the logs revealed anything of value. After a week of this, it finally crashed and stayed crashed. The culprit was the power supply.
FYI
I changed the PSU (Power supply unit) and I am testing: so far no reboots.
Tnx
-
Antonio M -
antonio montagnani -
Daniel J Walsh -
Ed Greshko -
Joe Zeff -
Tim