You are not logged in.

#1 2013-10-25 07:33:48

cmeury
Member
Registered: 2013-10-24
Posts: 6

Screens dark every morning, requiring cold reboot [cannot reproduce]

Since a few days, I come into the office and I cannot login anymore. Moving the mouse and keyboard does not help, neither does pressing the power button on the case or CTRL+ALT+DELETE, CTRL+ALT+BACKSPACE - nothing happens. Then I just do a cold boot. The reboots so far:

Oct 25 08:55:44
Oct 24 08:30:39
Oct 23 08:41:19

There's nothing to be seen in journalctl in the evening, no entries at all until the reboot messages from the morning. I tried replacing xscreensaver with xlockmore, does not help. Locking and login works fine during the day.

On Oct 22, I did a full system upgrade (including kernel 3.11.6-1) and I suspect it's something in there that gives me the trouble (see pacman.log below). Does anyone have an idea where else I could look for log messages or any other pointers? What other data could I provide that helps trouble-shooting this?

[2013-10-22 09:14] [PACMAN] Running 'pacman -Syu'
[2013-10-22 09:14] [PACMAN] synchronizing package lists
[2013-10-22 09:14] [PACMAN] starting full system upgrade
[2013-10-22 09:18] [PACMAN] upgraded apr (1.4.8-1 -> 1.4.8-2)
[2013-10-22 09:18] [PACMAN] upgraded apr-util (1.5.2-1 -> 1.5.2-3)
[2013-10-22 09:18] [PACMAN] upgraded curl (7.32.0-2 -> 7.33.0-1)
[2013-10-22 09:18] [PACMAN] upgraded dosfstools (3.0.22-1 -> 3.0.23-1)
[2013-10-22 09:18] [PACMAN] upgraded gcc-libs (4.8.1-3 -> 4.8.2-1)
[2013-10-22 09:18] [PACMAN] upgraded gcc (4.8.1-3 -> 4.8.2-1)
[2013-10-22 09:18] [PACMAN] installed libspiro (20071029-3)
[2013-10-22 09:18] [PACMAN] upgraded gegl (0.2.0-9 -> 0.2.0-10)
[2013-10-22 09:18] [PACMAN] upgraded hunspell (1.3.2-2 -> 1.3.2-3)
[2013-10-22 09:18] [PACMAN] upgraded ilmbase (2.0.1-1 -> 2.0.1-2)
[2013-10-22 09:18] [PACMAN] upgraded libltdl (2.4.2-10 -> 2.4.2-11)
[2013-10-22 09:18] [PACMAN] upgraded imagemagick (6.8.7.0-1 -> 6.8.7.1-1)
[2013-10-22 09:18] [PACMAN] upgraded lib32-dbus (1.6.14-1 -> 1.6.16-1)
[2013-10-22 09:18] [PACMAN] upgraded lib32-gcc-libs (4.8.1-3 -> 4.8.2-1)
[2013-10-22 09:18] [PACMAN] upgraded mesa (9.2.1-1 -> 9.2.2-1)
[2013-10-22 09:18] [PACMAN] upgraded lib32-mesa (9.2.1-1 -> 9.2.2-1)
[2013-10-22 09:18] [PACMAN] upgraded lib32-mesa-libgl (9.2.1-1 -> 9.2.2-1)
[2013-10-22 09:18] [PACMAN] upgraded sqlite (3.8.0.2-1 -> 3.8.1-1)
[2013-10-22 09:18] [PACMAN] upgraded lib32-sqlite (3.8.0.2-1 -> 3.8.1-1)
[2013-10-22 09:18] [PACMAN] upgraded libjpeg-turbo (1.3.0-2 -> 1.3.0-3)
[2013-10-22 09:18] [PACMAN] upgraded v4l-utils (1.0.0-1 -> 1.0.0-2)
[2013-10-22 09:18] [PACMAN] upgraded lib32-v4l-utils (1.0.0-1 -> 1.0.0-2)
[2013-10-22 09:18] [PACMAN] upgraded libical (1.0-2 -> 1.0-3)
[2013-10-22 09:18] [PACMAN] upgraded libice (1.0.8-1 -> 1.0.8-2)
[2013-10-22 09:18] [PACMAN] upgraded libpciaccess (0.13.2-1 -> 0.13.2-2)
[2013-10-22 09:18] [PACMAN] upgraded libpng (1.6.5-1 -> 1.6.6-1)
[2013-10-22 09:18] [PACMAN] upgraded libraw1394 (2.1.0-1 -> 2.1.0-2)
[2013-10-22 09:18] [PACMAN] upgraded libsm (1.2.2-1 -> 1.2.2-2)
[2013-10-22 09:18] [PACMAN] upgraded libtasn1 (3.3-1 -> 3.3-2)
[2013-10-22 09:18] [PACMAN] upgraded libtool (2.4.2-10 -> 2.4.2-11)
[2013-10-22 09:18] [PACMAN] upgraded libwbclient (4.0.10-1 -> 4.1.0-1)
[2013-10-22 09:18] [PACMAN] upgraded libxau (1.0.8-1 -> 1.0.8-2)
[2013-10-22 09:18] [PACMAN] upgraded libxinerama (1.1.3-1 -> 1.1.3-2)
[2013-10-22 09:18] [PACMAN] upgraded libxrandr (1.4.2-1 -> 1.4.2-2)
[2013-10-22 09:18] [PACMAN] upgraded libxss (1.2.2-1 -> 1.2.2-2)
[2013-10-22 09:18] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2013-10-22 09:18] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio.  Please wait...
[2013-10-22 09:18] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2013-10-22 09:18] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2013-10-22 09:18] [ALPM-SCRIPTLET] ==> Starting build: 3.11.6-1-ARCH
[2013-10-22 09:18] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2013-10-22 09:18] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2013-10-22 09:18] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2013-10-22 09:18] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2013-10-22 09:18] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2013-10-22 09:18] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2013-10-22 09:18] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2013-10-22 09:18] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2013-10-22 09:18] [ALPM-SCRIPTLET]   -> Running build hook: [fglrx]
[2013-10-22 09:18] [ALPM-SCRIPTLET] Building fglrx module for 3.11.6-1-ARCH kernel ...
[2013-10-22 09:18] [ALPM-SCRIPTLET] ESC[37;44mESC[1mFailed!!! Check out log: /var/log/catalyst-install.logESC[0m
[2013-10-22 09:18] [ALPM-SCRIPTLET] - /usr/lib/modules/3.11.5-1-ARCH looks like unused, maybe remove it manualy?
[2013-10-22 09:18] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-10-22 09:18] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2013-10-22 09:18] [ALPM-SCRIPTLET] ==> Image generation successful
[2013-10-22 09:18] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2013-10-22 09:18] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2013-10-22 09:18] [ALPM-SCRIPTLET] ==> Starting build: 3.11.6-1-ARCH
[2013-10-22 09:18] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2013-10-22 09:18] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2013-10-22 09:18] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2013-10-22 09:18] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2013-10-22 09:18] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2013-10-22 09:18] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: bfa
[2013-10-22 09:18] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: smsmdtv
[2013-10-22 09:18] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2013-10-22 09:18] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2013-10-22 09:18] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2013-10-22 09:18] [ALPM-SCRIPTLET]   -> Running build hook: [fglrx]
[2013-10-22 09:18] [ALPM-SCRIPTLET] Building fglrx module for 3.11.6-1-ARCH kernel ...
[2013-10-22 09:18] [ALPM-SCRIPTLET] ESC[37;44mESC[1mFailed!!! Check out log: /var/log/catalyst-install.logESC[0m
[2013-10-22 09:18] [ALPM-SCRIPTLET] - /usr/lib/modules/3.11.5-1-ARCH looks like unused, maybe remove it manualy?
[2013-10-22 09:18] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-10-22 09:18] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2013-10-22 09:18] [ALPM-SCRIPTLET] ==> Image generation successful
[2013-10-22 09:18] [PACMAN] upgraded linux (3.11.5-1 -> 3.11.6-1)
[2013-10-22 09:18] [PACMAN] upgraded linux-headers (3.11.5-1 -> 3.11.6-1)
[2013-10-22 09:18] [PACMAN] upgraded logrotate (3.8.6-1 -> 3.8.7-1)
[2013-10-22 09:18] [PACMAN] installed libunistring (0.9.3-5)
[2013-10-22 09:18] [PACMAN] installed gc (7.2.d-2)
[2013-10-22 09:18] [PACMAN] installed guile (2.0.9-1)
[2013-10-22 09:18] [PACMAN] upgraded make (3.82-6 -> 4.0-1)
[2013-10-22 09:18] [PACMAN] upgraded meld (1.8.1-1 -> 1.8.2-1)
[2013-10-22 09:18] [PACMAN] upgraded musicbrainz (2.1.5-5 -> 2.1.5-6)
[2013-10-22 09:18] [PACMAN] upgraded nodejs (0.10.20-1 -> 0.10.21-1)
[2013-10-22 09:18] [PACMAN] upgraded openexr (2.0.1-1 -> 2.0.1-2)
[2013-10-22 09:18] [PACMAN] upgraded opus (1.0.3-1 -> 1.0.3-2)
[2013-10-22 09:18] [PACMAN] upgraded pam (1.1.6-4 -> 1.1.8-1)
[2013-10-22 09:18] [PACMAN] upgraded qpdf (5.0.0-1 -> 5.0.1-1)
[2013-10-22 09:18] [PACMAN] upgraded qt4 (4.8.5-2 -> 4.8.5-3)
[2013-10-22 09:18] [PACMAN] upgraded smbclient (4.0.10-1 -> 4.1.0-1)
[2013-10-22 09:18] [PACMAN] upgraded speex (1.2rc1-3 -> 1.2rc1-4)
[2013-10-22 09:18] [ALPM-SCRIPTLET] In order to use the new version, reload all virtualbox modules manually.
[2013-10-22 09:18] [PACMAN] upgraded virtualbox-host-modules (4.2.18-7 -> 4.3.0-1)
[2013-10-22 09:18] [PACMAN] upgraded virtualbox (4.2.18-2 -> 4.3.0-1)
[2013-10-22 09:18] [PACMAN] upgraded yajl (2.0.4-1 -> 2.0.4-2)
[2013-10-22 09:20] [PACMAN] Running 'pacman -S -y -u'
[2013-10-22 09:20] [PACMAN] synchronizing package lists
[2013-10-22 09:20] [PACMAN] starting full system upgrade
[2013-10-22 09:21] [PACMAN] Running '/usr/bin/pacman -U /tmp/pacaurtmp-ced/virtualbox-extension-pack/virtualbox-extension-pack-4.3.0-1-x86_64.pkg.tar.xz'
[2013-10-22 09:21] [PACMAN] upgraded virtualbox-extension-pack (4.2.18-1 -> 4.3.0-1)
[2013-10-22 09:22] [PACMAN] Running '/usr/bin/pacman -U /tmp/pacaurtmp-ced/jdk/jdk-7.45-1-x86_64.pkg.tar'
[2013-10-22 09:22] [ALPM-SCRIPTLET] ESC[1mESC[34m==>ESC(BESC[mESC[1m Updating desktop MIME database...ESC(BESC[m
[2013-10-22 09:22] [ALPM-SCRIPTLET] ESC[1mESC[34m==>ESC(BESC[mESC[1m Updating MIME database...ESC(BESC[m
[2013-10-22 09:22] [ALPM-SCRIPTLET] ESC[1mESC[34m==>ESC(BESC[mESC[1m Updating icon cache...ESC(BESC[m
[2013-10-22 09:22] [PACMAN] upgraded jdk (7.40-1 -> 7.45-1)
[2013-10-22 09:22] [PACMAN] Running '/usr/bin/pacman -U /tmp/pacaurtmp-ced/google-chrome/google-chrome-30.0.1599.101-1-x86_64.pkg.tar'
[2013-10-22 09:22] [ALPM-SCRIPTLET] ESC[1mESC[34m==>ESC(BESC[mESC[1m Updating desktop MIME database...ESC(BESC[m
[2013-10-22 09:22] [ALPM-SCRIPTLET] ESC[1mESC[34m==>ESC(BESC[mESC[1m Updating icon cache..ESC(BESC[m
[2013-10-22 09:22] [PACMAN] upgraded google-chrome (29.0.1547.76-1 -> 30.0.1599.101-1)

Last edited by cmeury (2013-10-30 07:55:45)

Offline

#2 2013-10-26 02:38:36

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,140

Re: Screens dark every morning, requiring cold reboot [cannot reproduce]

Welcome to the forums.

Well what did you do about the errors with fglrx?!

Also, you would want to see what is in the logs from the last boot in the morning - not, probably, in the evening. At least, there might be something in the evening but much more likely in the morning. This assuming you use persistent journalling. Obviously if you don't, you should do so at least temporarily.

Last edited by cfr (2013-10-26 02:38:58)


CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#3 2013-10-26 08:06:55

cmeury
Member
Registered: 2013-10-24
Posts: 6

Re: Screens dark every morning, requiring cold reboot [cannot reproduce]

cfr, thanks for responding. The fglrx error seems unsettling, but it's fine: I always built the modules after a kernel upgrade. For some reason it doesn't work automatically, have not gotten around to fixing this.

I don't quite understand what you mean regarding the logs. The system seems to in some way "halt" in the time from evening (leaving office) and morning (coming to work). So I look at the journal from yesterday up until today's reboot. In any way, I looked through the whole log, but could not find anything suspicious. The journal stops having entries about 2-3 hrs after I leave the office, so I suspect the "thing" happens around then.

What is persistent journaling? How can I turn it on? I've looked at the systemd wiki page but could not find anything apart from setting the journal size limit.

Offline

#4 2013-10-26 14:59:38

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,140

Re: Screens dark every morning, requiring cold reboot [cannot reproduce]

You must be using persistent journalling already, then. (It's default so you'd know if you'd changed it anyway.)

What's in the journal right before the messages stop? What is the computer doing around that time? Any cron jobs set to run then, for example?


CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#5 2013-10-26 15:24:13

cmeury
Member
Registered: 2013-10-24
Posts: 6

Re: Screens dark every morning, requiring cold reboot [cannot reproduce]

I have no access to the work-station right now, but I know pretty much what the last entries were about: slim[500] logged various errors from the ghostery plugin in Firefox. I really wonder how they end up in the journal, but okay. They are not extraordinary though, every couple of minutes and sometimes hours these Javascript error messages show up in the journal. I'll post the full log entries on Wednesday. So that's it, some JS errors and then nothing.
I don't recall setting up any cron-jobs, for sure not in the last few days - but I will verify this, too.

Other than the journal, I have no clue what the computer is doing. It's a software development workstation, so various editors, IDE, browser, virtual machines etc. are running.

Offline

#6 2013-10-26 15:29:27

cmeury
Member
Registered: 2013-10-24
Posts: 6

Re: Screens dark every morning, requiring cold reboot [cannot reproduce]

Is there a way to set-up some sort of a full debugging level journal? Or any other monitoring tool that could provide more detailed information?

Offline

#7 2013-10-26 15:33:35

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,140

Re: Screens dark every morning, requiring cold reboot [cannot reproduce]

See /etc/systemd/journalctl.conf which has options for setting the level of messages which are logged. However, I think you might also want to pass a suitable parameter on the kernel command line - the wiki has a page on the options available.


CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#8 2013-10-30 07:55:21

cmeury
Member
Registered: 2013-10-24
Posts: 6

Re: Screens dark every morning, requiring cold reboot [cannot reproduce]

And today it did not happen. Cannot reproduce. I'll observe the next few days and re-open the thread if needed. Thanks cfr for your assistance.

Offline

Board footer

Powered by FluxBB