(03a) - Rechner wird beim Herunterfahren manchmal nicht ausgeschalten

mk75 · 2. August 2011

Hallo, ich benötige ein bisschen Hilfe,
ich habe vor einiger Zeit mal wieder ein update/dist-upgrade gemacht und habe jetzt ein Problem beim Ausschalten.

Der VDR verschwindet, das LCD wird ausgemacht aber der Rechner läuft weiter (Lampe und HDD, Lüfter läuft weiter).
Netzwerk ist weg und der Bildschirm ist schwarz.

Wenn ich danach den Reset Knopf drücke fährt der VDR wieder hoch. Wenn ich direkt danach den VDR per Power-Button ausschalte, fährt der
Rechner ganz normal runter und geht auch aus.

Der Tipp von ein paar Threads zuvor (chmod +s ...) hat nicht geholfen.

Hier ein paar Infos aus den messages, der letzte Eintrag hat immer was mit rsyslogd zu tun:

Code

Jul 31 04:35:01 vdr3 vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S90.nvram-wakeup as shell script
Jul 31 04:35:01 vdr3 vdr-nvram-wakeup: nvram-wakeup functionality is disabled
Jul 31 04:35:01 vdr3 vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S90.shutdown
Jul 31 04:35:01 vdr3 vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S91.lifeguard as shell script
Jul 31 04:35:01 vdr3 vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S92.imonlcd
Jul 31 04:35:02 vdr3 kernel: [ 5024.571089] lirc_imon: IR port closed
Jul 31 04:35:02 vdr3 vdr-sxfe[1325]: [1325] [vdr-fe]    caught signal 15
Jul 31 04:35:03 vdr3 kernel: [ 5025.249652] display port closed
Jul 31 04:35:03 vdr3 vdr: [1381] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE)
Jul 31 04:35:03 vdr3 vdr: last message repeated 61 times
Jul 31 04:35:03 vdr3 kernel: [ 5025.447309] nfsd: last server has exited, flushing export cache
Jul 31 04:35:03 vdr3 vdr-sxfe[1325]: [1325] [input_vdr] Connections closed.
Jul 31 04:35:03 vdr3 vdr-sxfe[1325]: [1325] [scrnsaver] Failed to open connection to bus: /bin/dbus-launch terminated abnormally without any error message
Jul 31 04:35:04 vdr3 kernel: [ 5026.261008] display port opened
Jul 31 04:35:04 vdr3 kernel: [ 5026.288463] display port closed
Jul 31 07:43:19 vdr3 kernel: imklog 4.2.0, log source = /proc/kmsg started.
Jul 31 07:43:19 vdr3 rsyslogd: [origin software="rsyslogd" swVersion="4.2.0" x-pid="1185" x-info="http://www.rsyslog.com"] (re)start
Jul 31 07:43:20 vdr3 rsyslogd: rsyslogd's groupid changed to 103
Jul 31 07:43:20 vdr3 rsyslogd: rsyslogd's userid changed to 101
Jul 31 07:43:20 vdr3 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 31 07:43:20 vdr3 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 31 07:43:20 vdr3 kernel: [    0.000000] Linux version 2.6.32-33-generic (buildd@palmer) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #71-Ubuntu SMP We$
Jul 31 07:43:20 vdr3 kernel: [    0.000000] KERNEL supported cpus:

Alles anzeigen

Code

Jul 31 07:44:28 vdr3 vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S90.shutdown
Jul 31 07:44:28 vdr3 vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S91.lifeguard as shell script
Jul 31 07:44:28 vdr3 vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S92.imonlcd
Jul 31 07:44:29 vdr3 kernel: [   86.041136] lirc_imon: IR port closed
Jul 31 07:44:29 vdr3 vdr-sxfe[2177]: [2177] [vdr-fe]    caught signal 15
Jul 31 07:44:29 vdr3 vdr-sxfe[2177]: [2177] [input_vdr] Connections closed.
Jul 31 07:44:29 vdr3 vdr: [2175] [xine..put] Closing connection 0
Jul 31 07:44:29 vdr3 vdr-sxfe[2177]: [2177] [scrnsaver] Failed to open connection to bus: /bin/dbus-launch terminated abnormally without any error message
Jul 31 07:44:29 vdr3 kernel: [   86.379549] display port closed
Jul 31 07:44:29 vdr3 kernel: [   86.398856] nfsd: last server has exited, flushing export cache
Jul 31 07:44:30 vdr3 kernel: Kernel logging (proc) stopped.
Jul 31 07:44:30 vdr3 rsyslogd: [origin software="rsyslogd" swVersion="4.2.0" x-pid="1185" x-info="http://www.rsyslog.com"] exiting on signal 15.
Jul 31 07:44:30 vdr3 kernel: imklog 4.2.0, log source = /proc/kmsg started.
Jul 31 07:44:30 vdr3 rsyslogd: [origin software="rsyslogd" swVersion="4.2.0" x-pid="2524" x-info="http://www.rsyslog.com"] (re)start
Jul 31 07:44:30 vdr3 rsyslogd: rsyslogd's groupid changed to 103
Jul 31 07:44:30 vdr3 rsyslogd: rsyslogd's userid changed to 101
Jul 31 07:44:30 vdr3 kernel: [   87.343717] display port opened
Jul 31 07:44:30 vdr3 kernel: [   87.387433] display port closed
Jul 31 18:41:32 vdr3 kernel: imklog 4.2.0, log source = /proc/kmsg started.
Jul 31 18:41:32 vdr3 rsyslogd: [origin software="rsyslogd" swVersion="4.2.0" x-pid="1032" x-info="http://www.rsyslog.com"] (re)start
Jul 31 18:41:32 vdr3 rsyslogd: rsyslogd's groupid changed to 103
Jul 31 18:41:32 vdr3 rsyslogd: rsyslogd's userid changed to 101
Jul 31 18:41:32 vdr3 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 31 18:41:32 vdr3 kernel: [    0.000000] Initializing cgroup subsys cpu

Alles anzeigen

Code

Jul 31 23:44:39 vdr3 vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S90.shutdown
Jul 31 23:44:39 vdr3 vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S91.lifeguard as shell script
Jul 31 23:44:40 vdr3 vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S92.imonlcd
Jul 31 23:44:40 vdr3 kernel: [18201.820326] lirc_imon: IR port closed
Jul 31 23:44:40 vdr3 vdr-sxfe[1362]: [1362] [vdr-fe]    caught signal 15
Jul 31 23:44:40 vdr3 vdr-sxfe[1362]: [1362] [input_vdr] Connections closed.
Jul 31 23:44:40 vdr3 vdr: [1360] [xine..put] Closing connection 0
Jul 31 23:44:40 vdr3 vdr-sxfe[1362]: [1362] [scrnsaver] Failed to open connection to bus: /bin/dbus-launch terminated abnormally without any error message
Jul 31 23:44:41 vdr3 kernel: [18202.548754] display port closed
Jul 31 23:44:41 vdr3 kernel: [18202.594764] nfsd: last server has exited, flushing export cache
Jul 31 23:44:42 vdr3 kernel: [18203.775106] display port opened
Jul 31 23:44:42 vdr3 kernel: [18203.820700] display port closed
Jul 31 23:45:53 vdr3 kernel: imklog 4.2.0, log source = /proc/kmsg started.
Jul 31 23:45:53 vdr3 rsyslogd: [origin software="rsyslogd" swVersion="4.2.0" x-pid="1178" x-info="http://www.rsyslog.com"] (re)start
Jul 31 23:45:53 vdr3 rsyslogd: rsyslogd's groupid changed to 103
Jul 31 23:45:53 vdr3 rsyslogd: rsyslogd's userid changed to 101
Jul 31 23:45:53 vdr3 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 31 23:45:53 vdr3 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 31 23:45:53 vdr3 kernel: [    0.000000] Linux version 2.6.32-33-generic (buildd@palmer) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #71-Ubuntu SMP We$
Jul 31 23:45:53 vdr3 kernel: [    0.000000] KERNEL supported cpus:
Jul 31 23:45:53 vdr3 kernel: [    0.000000]   Intel GenuineIntel

Alles anzeigen

mk75 · 28. August 2011

Hallo,
könnt ihr mir vielleicht Tipps geben nach was ich suchen könnte ? Das Problem besteht leider immer noch,
ich hab jetzt schon mehrere Aufnahmen verpasst.

Heute wieder 19:37 letzter Eintrag, dann hab ich um 20:29 reset gedrückt.

Code

Aug 28 18:46:00 vdr3 recordingaction: executing /usr/share/vdr/recording-hooks/R90.custom before recording /srv/vdr/video.00/Lindenstraße/2011-08-28.18.46.1-0.rec as shell script
Aug 28 18:56:11 vdr3 vdr: [1570] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE)
Aug 28 18:57:06 vdr3 vdr: last message repeated 426 times
Aug 28 19:30:00 vdr3 recordingaction: executing /usr/share/vdr/recording-hooks/R90.custom after recording /srv/vdr/video.00/Lindenstraße/2011-08-28.18.46.1-0.rec as shell script
Aug 28 19:37:03 vdr3 vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S50.noad as shell script
Aug 28 19:37:03 vdr3 vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S90.acpiwakeup as shell script
Aug 28 19:37:03 vdr3 vdr-addon-acpiwakeup: Setting ACPI alarm time to: 2011-08-28 18:06:00
Aug 28 19:37:03 vdr3 vdr-addon-acpiwakeup: Writing to /sys/class/rtc/rtc0/wakealarm
Aug 28 19:37:03 vdr3 vdr-addon-acpiwakeup: Writing to /sys/class/rtc/rtc0/wakealarm
Aug 28 19:37:03 vdr3 vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S90.custom as shell script
Aug 28 19:37:03 vdr3 vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S90.nvram-wakeup as shell script
Aug 28 19:37:03 vdr3 vdr-nvram-wakeup: nvram-wakeup functionality is disabled
Aug 28 19:37:03 vdr3 vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S90.shutdown
Aug 28 19:37:03 vdr3 vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S91.lifeguard as shell script
Aug 28 19:37:03 vdr3 vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S92.imonlcd
Aug 28 19:37:04 vdr3 kernel: [ 3345.883334] lirc_imon: IR port closed
Aug 28 19:37:04 vdr3 vdr-sxfe[1488]: [1488] [vdr-fe]    caught signal 15
Aug 28 19:37:04 vdr3 vdr: [1570] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE)
Aug 28 19:37:04 vdr3 vdr: last message repeated 26 times
Aug 28 19:37:04 vdr3 vdr-sxfe[1488]: [1488] [input_vdr] Connections closed.
Aug 28 19:37:04 vdr3 vdr: [1486] [xine..put] Closing connection 0
Aug 28 19:37:04 vdr3 kernel: [ 3346.399549] display port closed
Aug 28 19:37:04 vdr3 vdr-sxfe[1488]: [1488] [scrnsaver] Failed to open connection to bus: /bin/dbus-launch terminated abnormally without any error message
Aug 28 19:37:05 vdr3 kernel: [ 3346.468329] nfsd: last server has exited, flushing export cache
Aug 28 19:37:05 vdr3 kernel: [ 3346.502455] saa7146 (0) vpeirq: used 1 times >80% of buffer (176720 bytes now)
Aug 28 19:37:05 vdr3 kernel: [ 3347.418963] display port opened
Aug 28 19:37:06 vdr3 kernel: [ 3347.462837] display port closed
Aug 28 20:29:50 vdr3 kernel: imklog 4.2.0, log source = /proc/kmsg started.
Aug 28 20:29:50 vdr3 rsyslogd: [origin software="rsyslogd" swVersion="4.2.0" x-pid="1153" x-info="http://www.rsyslog.com"] (re)start
Aug 28 20:29:50 vdr3 rsyslogd: rsyslogd's groupid changed to 103
Aug 28 20:29:51 vdr3 rsyslogd: rsyslogd's userid changed to 101
Aug 28 20:29:51 vdr3 kernel: [    0.000000] Initializing cgroup subsys cpuset

Alles anzeigen

MajestyIV · 29. August 2011

Hi, ich habe am Wochenden auch damit gekämpft. Bei mir wollte ich suspend2ram aktivieren.

Geholfen hat dann, ACPI 2.0 support im BIOS abzuschalten.

Evtl. hilft Dir das ja.

Majesty

(03a) - Rechner wird beim Herunterfahren manchmal nicht ausgeschalten

Jetzt mitmachen!

Teilen