Seltener Fehler NVRAM-WAKEUP

alex141077 · 21. März 2006

Hallo, ich wollte nur mal ein seltsames Problem mit NVRAM-Wakeup schildern, das mir gestern passiert ist, als ich den VDR einschaltete und feststellen mußte, daß alle geplanten Aufnahmen vom letzten Tag nicht aufgenommen waren. Nach Analyse des Logfiles lag es daran:
Ich habe den VDR mit der Fernbedienung ausgeschaltet. Das hat aber, warum auch immer, etwas länger gedauert. Dann habe ich den Fernseher ausgeschaltet, der VDR war immer noch an. Also habe ich einfach nochmal die Powertaste der FB gedrückt. Das war mein Fehler, denn nun wurde der VDR nicht mit dem Poweroff-Kernel gebootet, sondern einfach heruntergefahren, da ja bereits die neue Wakeup-Zeit von meinem ersten Ausschalteversuch im NVRAM eingetragen war. Also Vorsicht mit einem zweimaligen Drücken der Powertaste. Das ganze habe ich gerade in meiner syslog gefunden:

Code

Mar 19 21:58:53 localhost vdr: [3787] Power button pressed
Mar 19 21:58:53 localhost vdr: [3787] next timer event at Mon Mar 20 02:43:00 2006
Mar 19 21:58:53 localhost vdr: [3787] confirm: Taste drücken, um Shutdown abzubrechen
Mar 19 21:58:53 localhost vdr: [3787] warning: Taste drücken, um Shutdown abzubrechen
Mar 19 21:58:53 localhost vdr: [4179] Text2Skin: message display update thread started (pid=4179, tid=4179)
Mar 19 21:58:59 localhost vdr: [4179] Text2Skin: message display update thread ended (pid=4179, tid=4179)
Mar 19 21:58:59 localhost vdr: [3787] confirmed
Mar 19 21:58:59 localhost vdr: [3787] executing '/usr/lib/vdr/vdr-shutdown.wrapper 1142818980 17041 5 "Die Farbe Lila" 1'
Mar 19 21:58:59 localhost vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S50.noad as shell script
Mar 19 21:58:59 localhost vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S50.vdr-plugin-burn as shell script
Mar 19 21:58:59 localhost vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S90.custom as shell script
Mar 19 21:58:59 localhost vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S90.nvram-wakeup as shell script
Mar 19 21:58:59 localhost vdr-nvram-wakeup: /usr/sbin/nvram-wakeup -ls 1142818980 -C /etc/nvram-wakeup.conf
Mar 19 21:58:59 localhost nvram-wakeup[4197]:
Mar 19 21:58:59 localhost nvram-wakeup[4197]: All values are displayed as they are stored in the nvram/rtc.
Mar 19 21:58:59 localhost nvram-wakeup[4197]: (and do not correspond necessarily to the system date/time)
Mar 19 21:58:59 localhost nvram-wakeup[4197]:
Mar 19 21:58:59 localhost nvram-wakeup[4197]: WakeUp  : Enabled (0x60)
Mar 19 21:58:59 localhost nvram-wakeup[4197]: Day     : 19 (0x13)
Mar 19 21:58:59 localhost nvram-wakeup[4197]: Hour    : 18 (0x12)
Mar 19 21:58:59 localhost nvram-wakeup[4197]: Minute  : 55 (0x37)
Mar 19 21:58:59 localhost nvram-wakeup[4197]: Second  : 00 (0x00)
Mar 19 21:58:59 localhost nvram-wakeup[4197]: Checksum: 0x0D30
Mar 19 21:58:59 localhost nvram-wakeup[4197]:
Mar 19 21:58:59 localhost nvram-wakeup[4197]: Enabling (0x60) WakeUp-on-RTC in nvram.
Mar 19 21:58:59 localhost nvram-wakeup[4197]: New Day     : 20 (0x14)
Mar 19 21:58:59 localhost nvram-wakeup[4197]: New Hour    : 02 (0x02)
Mar 19 21:58:59 localhost nvram-wakeup[4197]: New Minute  : 38 (0x26)
Mar 19 21:58:59 localhost nvram-wakeup[4197]: New Second  : 00 (0x00)
Mar 19 21:58:59 localhost nvram-wakeup[4197]: New Checksum: 0x0D10
Mar 19 21:58:59 localhost nvram-wakeup[4197]:
Mar 19 21:58:59 localhost nvram-wakeup[4197]: Now really WRITING into /dev/nvram...
Mar 19 21:58:59 localhost nvram-wakeup[4197]:    The changes to take effect, you must reboot your computer now.
Mar 19 21:58:59 localhost nvram-wakeup[4197]:
Mar 19 21:58:59 localhost vdr-nvram-wakeup: nvram-wakeup: everything ok - need to reboot first
Mar 19 21:59:00 localhost kernel: cdrom: open failed.
Mar 19 21:59:00 localhost shutdown[4203]: shutting down for system reboot
Mar 19 21:59:00 localhost init: Switching to runlevel: 6
Mar 19 21:59:01 localhost vdr: [3787] connect from 127.0.0.1, port 40409 - accepted
Mar 19 21:59:01 localhost vdr: [3787] Power button pressed
Mar 19 21:59:01 localhost vdr: [3787] next timer event at Mon Mar 20 02:43:00 2006
Mar 19 21:59:01 localhost vdr: [3787] confirm: Taste drücken, um Shutdown abzubrechen
Mar 19 21:59:01 localhost vdr: [3787] warning: Taste drücken, um Shutdown abzubrechen
Mar 19 21:59:01 localhost vdr: [4221] Text2Skin: message display update thread started (pid=4221, tid=4221)
Mar 19 21:59:01 localhost vdr: [3787] closing SVDRP connection
Mar 19 21:59:01 localhost lircd 0.7.1pre2[3190]: caught signal
Mar 19 21:59:01 localhost vdr: [3858] ERROR: lircd connection broken, trying to reconnect every 3.0 seconds
Mar 19 21:59:03 localhost vdr: [4221] Text2Skin: message display update thread ended (pid=4221, tid=4221)
Mar 19 21:59:03 localhost vdr: [3787] confirmed
Mar 19 21:59:03 localhost vdr: [3787] executing '/usr/lib/vdr/vdr-shutdown.wrapper 1142818980 17037 5 "Die Farbe Lila" 1'
Mar 19 21:59:03 localhost vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S50.noad as shell script
Mar 19 21:59:03 localhost vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S50.vdr-plugin-burn as shell script
Mar 19 21:59:03 localhost vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S90.custom as shell script
Mar 19 21:59:03 localhost vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S90.nvram-wakeup as shell script
Mar 19 21:59:03 localhost vdr-nvram-wakeup: /usr/sbin/nvram-wakeup -ls 1142818980 -C /etc/nvram-wakeup.conf
Mar 19 21:59:03 localhost nvram-wakeup[4279]:
Mar 19 21:59:03 localhost nvram-wakeup[4279]: All values are displayed as they are stored in the nvram/rtc.
Mar 19 21:59:03 localhost nvram-wakeup[4279]: (and do not correspond necessarily to the system date/time)
Mar 19 21:59:03 localhost nvram-wakeup[4279]:
Mar 19 21:59:03 localhost nvram-wakeup[4279]: WakeUp  : Enabled (0x60)
Mar 19 21:59:03 localhost nvram-wakeup[4279]: Day     : 20 (0x14)
Mar 19 21:59:03 localhost nvram-wakeup[4279]: Hour    : 02 (0x02)
Mar 19 21:59:03 localhost nvram-wakeup[4279]: Minute  : 38 (0x26)
Mar 19 21:59:03 localhost nvram-wakeup[4279]: Second  : 00 (0x00)
Mar 19 21:59:03 localhost nvram-wakeup[4279]: Checksum: 0x0D10
Mar 19 21:59:03 localhost nvram-wakeup[4279]:
Mar 19 21:59:03 localhost nvram-wakeup[4279]: Enabling (0x60) WakeUp-on-RTC in nvram.
Mar 19 21:59:03 localhost nvram-wakeup[4279]: New Day     : 20 (0x14)
Mar 19 21:59:03 localhost nvram-wakeup[4279]: New Hour    : 02 (0x02)
Mar 19 21:59:03 localhost nvram-wakeup[4279]: New Minute  : 38 (0x26)
Mar 19 21:59:03 localhost nvram-wakeup[4279]: New Second  : 00 (0x00)
Mar 19 21:59:03 localhost nvram-wakeup[4279]: New Checksum: 0x0D10
Mar 19 21:59:03 localhost nvram-wakeup[4279]:
Mar 19 21:59:03 localhost vdr-nvram-wakeup: nvram-wakeup: everything ok
Mar 19 21:59:04 localhost shutdown[4285]: shutting down for system halt
Mar 19 21:59:04 localhost init: Switching to runlevel: 0
Mar 19 21:59:04 localhost vdr: [3787] caught signal 15
Mar 19 21:59:04 localhost vdr: [3787] stopping plugin: text2skin
Mar 19 21:59:04 localhost vdr: [3787] stopping plugin: vcd
Mar 19 21:59:04 localhost vdr: [3787] stopping plugin: solitaire
Mar 19 21:59:04 localhost vdr: [3787] stopping plugin: dvd
Mar 19 21:59:04 localhost vdr: [3787] stopping plugin: dvdselect
Mar 19 21:59:04 localhost vdr: [3787] stopping plugin: mp3
Mar 19 21:59:04 localhost vdr: [3787] stopping plugin: graphtft
Mar 19 21:59:04 localhost vdr: [3787] stopping plugin: games
Mar 19 21:59:04 localhost vdr: [3787] stopping plugin: femon
Mar 19 21:59:04 localhost vdr: [3787] stopping plugin: mplayer
Mar 19 21:59:04 localhost vdr: [3787] stopping plugin: autotimeredit
Mar 19 21:59:04 localhost vdr: [3787] stopping plugin: timeline
Mar 19 21:59:04 localhost vdr: [3787] stopping plugin: osdteletext
Mar 19 21:59:04 localhost vdr: [3787] stopping plugin: mailbox
Mar 19 21:59:04 localhost vdr: [3787] stopping plugin: osdpip
Mar 19 21:59:04 localhost vdr: [3787] stopping plugin: burn
Mar 19 21:59:04 localhost vdr: [3787] stopping plugin: tvonscreen
Mar 19 21:59:07 localhost vdr: [3787] ERROR: thread 3859 won't end (waited 3 seconds) - canceling it...
Mar 19 21:59:07 localhost vdr: [3787] saved setup to /var/lib/vdr/setup.conf
Mar 19 21:59:07 localhost vdr: [3847] tuner on device 1 thread ended (pid=3847, tid=3847)
Mar 19 21:59:07 localhost rpc.statd[3811]: Caught signal 15, un-registering and exiting.
Mar 19 21:59:07 localhost vdr: [4120] receiver on device 1 thread ended (pid=4120, tid=4120)
Mar 19 21:59:07 localhost kernel: nfsd: last server has exited
Mar 19 21:59:07 localhost kernel: nfsd: unexporting all filesystems
Mar 19 21:59:07 localhost rpc.mountd: Caught signal 15, un-registering and exiting.
Mar 19 21:59:07 localhost kernel: Kernel logging (proc) stopped.
Mar 19 21:59:07 localhost kernel: Kernel log daemon terminating.
Mar 19 21:59:07 localhost exiting on signal 15

Alles anzeigen

SurfaceCleanerZ · 21. März 2006

Der Poweroff-Kernel ist obsolet!!!

man braucht im grub nur nen halt Eintrag:
http://www.vdr-wiki.de/wiki/in…eup_f%FCr_VIA_EPIA_M10000

Negge · 22. März 2006

genau: Einfach nur "halt" in die Grub-config-Datei eintragen und der Rechner schaltet aus.

Wobei das aber ja grundlegend nichts an dem obigen Problem ändert, oder?

Denn wenn als Rebbot-Option nicht "grub-reboot 1 --no-floppy" (Grub-Menüpunkt 1 ist "halt") ausgeführt wird sondern der Rechner einfach nur abschaltet, weil NVRAM denkt das NVRAM wäre schon gesetzt. Sinniger wäre es ja dann, wenn der Rechner "statt shutdown -h" IMMER "grub-reboot 1" bei Runterfahren ausführt. Dann hätte man das Problem nicht mehr.

Ist das einfach umzusetzen?

SurfaceCleanerZ · 22. März 2006

gibs doch im conf von nvram always reboot

Seltener Fehler NVRAM-WAKEUP

Jetzt mitmachen!

Teilen