11.4 - deadly crashes: "exception Emask 0x32 SAct 0x0 SErr 0x0 action 0x

kullmann · July 19, 2011, 4:43pm

Hello,

I have an Inspiron 1764 laptop with
Linux linux-vp82.site 2.6.37.6-0.5-desktop #1 SMP PREEMPT 2011-04-25 21:48:33 +0200 x86_64 x86_64 x86_64 GNU/Linux

Installed 11.4, with all updates applied.

With 11.3 on the same laptop I got from time to time an X-server crash. This was more often with 11.4, but still bearable.
Then came complete crashes (system didn’t react anymore, apparently dead), where a coloured blinking mosaic showed
up. Finally I got today two further such complete crashes (no reactions anymore), this time with completely blank
screen. So it seems getting serious.

From these two last crashes here are the log messages from /var/log/messages (around the places which seem
related):

Number I:

Jul 19 01:45:05 linux-vp82 kernel: [18158.665956] ata2.00: exception Emask 0x32 SAct 0x0 SErr 0x0 action 0xe frozen
Jul 19 01:45:05 linux-vp82 kernel: [18158.666083] ata2.00: irq_stat 0xffffffff, unknown FIS 00000000 00000000 00000000 00000000, host bus
Jul 19 01:45:05 linux-vp82 kernel: [18158.666150] sr 1:0:0:0: CDB: Prevent/Allow Medium Removal: 1e 00 00 00 00 00
Jul 19 01:45:05 linux-vp82 kernel: [18158.666245] ata2.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Jul 19 01:45:05 linux-vp82 kernel: [18158.666246] res 50/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x32 (host bus error)
Jul 19 01:45:05 linux-vp82 kernel: [18158.666342] ata2.00: status: { DRDY }
Jul 19 01:45:05 linux-vp82 kernel: [18158.666407] ata2: hard resetting link
Jul 19 01:45:06 linux-vp82 kernel: [18159.390789] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Jul 19 01:45:06 linux-vp82 kernel: [18159.394953] ata2.00: configured for UDMA/100
Jul 19 01:45:06 linux-vp82 kernel: [18159.411672] ata2: EH complete
Jul 19 01:45:06 linux-vp82 kernel: [18159.411707] sr 1:0:0:0: ioctl_internal_command return code = 8000002
Jul 19 01:45:06 linux-vp82 kernel: [18159.411738] : Sense Key : Aborted Command [current] [descriptor]
Jul 19 01:45:06 linux-vp82 kernel: [18159.411769] : Add. Sense: No additional sense information
Jul 19 01:45:07 linux-vp82 kernel: [18160.338908] ata1: illegal qc_active transition (00000001->ffffffff)
Jul 19 01:45:07 linux-vp82 kernel: [18160.339102] ata1.00: exception Emask 0x2 SAct 0x0 SErr 0x0 action 0x6 frozen
Jul 19 01:45:07 linux-vp82 kernel: [18160.339166] ata1.00: failed command: WRITE DMA
Jul 19 01:45:07 linux-vp82 kernel: [18160.339201] ata1.00: cmd ca/00:08:c8:5e:c6/00:00:00:00:00/e7 tag 0 dma 4096 out
Jul 19 01:45:07 linux-vp82 kernel: [18160.339202] res 50/00:00:cf:5e:c6/00:00:07:00:00/e7 Emask 0x2 (HSM violation)
Jul 19 01:45:07 linux-vp82 kernel: [18160.339267] ata1.00: status: { DRDY }
Jul 19 01:45:07 linux-vp82 kernel: [18160.339330] ata1: hard resetting link
Jul 19 01:45:07 linux-vp82 kernel: [18160.643376] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jul 19 01:45:07 linux-vp82 kernel: [18160.651164] ata1.00: configured for UDMA/133
Jul 19 01:45:07 linux-vp82 kernel: [18160.662381] ata1: EH complete
Jul 19 01:49:25 linux-vp82 smartd[1931]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 110 to 111
Jul 19 06:57:16 linux-vp82 kernel: imklog 5.6.5, log source = /proc/kmsg started.

Number II:

Jul 19 11:45:55 linux-vp82 sudo: root : TTY=pts/22 ; PWD=/home/kullmann/FrequencyUtility ; USER=root ; COMMAND=/usr/bin/cpufreq-set -c 3 -f 2.266GHz
Jul 19 12:00:06 linux-vp82 kernel: [17998.692899] ata1.00: exception Emask 0x32 SAct 0x0 SErr 0x0 action 0xe frozen
Jul 19 12:00:06 linux-vp82 kernel: [17998.692914] ata1.00: irq_stat 0xffffffff, unknown FIS 00000000 00000000 00000000 00000000, host bus
Jul 19 12:00:06 linux-vp82 kernel: [17998.692925] ata1.00: failed command: WRITE DMA
Jul 19 12:00:06 linux-vp82 kernel: [17998.692936] ata1.00: cmd ca/00:48:10:7a:c5/00:00:00:00:00/e7 tag 0 dma 36864 out
Jul 19 12:00:06 linux-vp82 kernel: [17998.692937] res 50/00:00:57:7a:c5/00:00:07:00:00/e7 Emask 0x32 (host bus error)
Jul 19 12:00:06 linux-vp82 kernel: [17998.692952] ata1.00: status: { DRDY }
Jul 19 12:00:06 linux-vp82 kernel: [17998.692961] ata1: hard resetting link
Jul 19 12:00:07 linux-vp82 kernel: [17999.414567] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Jul 19 12:00:07 linux-vp82 kernel: [17999.418929] ata1.00: configured for UDMA/33
Jul 19 12:00:07 linux-vp82 kernel: [17999.429507] ata1: EH complete
Jul 19 12:14:18 linux-vp82 kernel: imklog 5.6.5, log source = /proc/kmsg started.
Jul 19 12:14:18 linux-vp82 rsyslogd: [origin software=“rsyslogd” swVersion=“5.6.5” x-pid=“1174” x-info=“http://www.rsyslog.com”] start

Anybody any idea?

Oliver

kullmann · July 20, 2011, 10:10pm

Hi,

it continues to crash; any help would be highly welcome.

There are three types of crashes:

The “dizzy screen” crash: only the screen shows flicker, while the system still runs (and thus,
using ctrl-alt-del plus return one can shutdown the system; that is, it used to be like that,
but now the KDE login screen doesn’t allow keyboard control, only the mouse, and that
doesn’t work; only the power-button helps here).
The “blinking screen death”: screen shows a coloured mosaic, partially blinking, system apparently
completely dead.
The “dark screen death”: screen dark, all dead.

Today I had another blinking screen death, after suspend-to-RAM; /var/log/messages contains

Jul 20 13:16:25 linux-vp82 smartd[2068]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 118 to 119
Jul 20 13:56:08 linux-vp82 kernel: imklog 5.6.5, log source = /proc/kmsg started.
Jul 20 13:56:08 linux-vp82 rsyslogd: [origin software=“rsyslogd” swVersion=“5.6.5” x-pid=“1242” x-info=“http://www.rsyslog.com”] start
Jul 20 13:56:08 linux-vp82 kernel: 22.450278] type=1400 audit(1311166562.71

At 13:16:25 it was still running, and I guess the 13:56:08 message relates to the rebooting, so no message, just sudden death.

Another reboot, directly after the Suse boot menu, resulted in the dark screen death, and again no traces in /var/log/messages.

Oliver

baskitcaise · July 21, 2011, 1:11am

kullmann adjusted his/her AFDB on Wed 20 July 2011 21:16 to write:

>
> Hi,
>
> it continues to crash; any help would be highly welcome.
>
> There are three types of crashes:
> - The “dizzy screen” crash: only the screen shows flicker, while the
> system still runs (and thus,
> using ctrl-alt-del plus return one can shutdown the system; that is,
> it used to be like that,
> but now the KDE login screen doesn’t allow keyboard control, only
> the mouse, and that
> doesn’t work; only the power-button helps here).
> - The “blinking screen death”: screen shows a coloured mosaic,
> partially blinking, system apparently
> completely dead.
> - The “dark screen death”: screen dark, all dead.
>
> Today I had another blinking screen death, after suspend-to-RAM;
> /var/log/messages contains
>
> Jul 20 13:16:25 linux-vp82 smartd[2068]: Device: /dev/sda [SAT], SMART
> Usage Attribute: 194 Temperature_Celsius changed from 118 to 119
> Jul 20 13:56:08 linux-vp82 kernel: imklog 5.6.5, log source =
> /proc/kmsg started.
> Jul 20 13:56:08 linux-vp82 rsyslogd: [origin software=“rsyslogd”
> swVersion=“5.6.5” x-pid=“1242” x-info=“http://www.rsyslog.com”] start
> Jul 20 13:56:08 linux-vp82 kernel: 22.450278] type=1400
> audit(1311166562.71
>
> At 13:16:25 it was still running, and I guess the 13:56:08 message
> relates to the rebooting, so no message, just sudden death.
>
> Another reboot, directly after the Suse boot menu, resulted in the dark
> screen death, and again no traces in /var/log/messages.
>
> Oliver
>
>

Hi Oliver,

I have just seen your first post and had a look round, I cannot find the exact
specs for that machine but the errors suggest that there could be something
amiss with your SATA controller, there are plenty of reports that if it is a
micron SATA controller it does not play very well with certain drives and
the only way around it is to either change the drive model/manufacturer or
disable the controller which I realise is not an option on a laptop.

Off the top of my head I would suggest you try and see if there is any way to
change the settings in the bios to see if it makes any difference.

If it is set to AHCI then see if you can change it to “SATA” “legacy” or
"IDE Mode"or whatever.

Not having much luck finding anything about the bios options for that model
so you will just have to experiment.

I take it you have the latest BIOS?

HTH

–
Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum

baskitcaise · July 21, 2011, 1:29am

kullmann adjusted his/her AFDB on Wed 20 July 2011 21:16 to write:

> Another reboot, directly after the Suse boot menu, resulted in the dark
> screen death, and again no traces in /var/log/messages.
>
> Oliver
>
>

Another thought: (gosh 2 in one day )

try issuing the command:

lspci -vv

so we can see what is actually in the machine and also I want to see what
the interrupts are, there are reports about sharing the SATA irq’s with
others like onboard nic can give these symptoms.

If there are any conflicts you could try the boot param of:

irqpoll

–
Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum

kullmann · July 22, 2011, 8:01pm

Hello,

I waited a bit, but it seems that one of the installations by chance made the problem go away:
for two days no more crashes yet. Perhaps laptop-mode-tools, though not activated, had an
effect?

Okay, today I had another dark screen death, but that was after awaking from hibernation, and hibernation
has now major problems (it worked with 11.3), so I assume that is a different issue.

Thus I avoided to send more information (more noise). I hope the problem is gone now.

By the way, the BIOS is up-to-date (though I never noticed any change after any BIOS-update).

It might be that the crashes happened with kernel
Linux linux-vp82.site 2.6.37.1-1.2-default #1 SMP 2011-02-21 10:34:10 +0100 x86_64 x86_64 x86_64 GNU/Linux
and then update to
Linux linux-vp82.site 2.6.37.6-0.5-desktop #1 SMP PREEMPT 2011-04-25 21:48:33 +0200 x86_64 x86_64 x86_64 GNU/Linux
happened via installation of laptop-mode-tools, and that cured the problem (hopefully).
Via Yast, installation of new kernels always happens by-the-way, as unnoticable as possible, and it seems that Yast
also has no record on these things (at least not visibly), so kernel-changes happen in a rather hidden way.

Anyway, let’s hope the best, and thanks for your replies!

Oliver

kullmann · July 22, 2011, 9:41pm

Sigh, the blinking screen death returned. I just had a happy dream of a joyous live with my laptop, and then it
happened, out of nowhere …

Can’t detect anything in /var/log/messages, but who knows, perhaps you can (at 19:49:12 and somewhat later it
was still working, I just opened something; due to “15000 characters” I’ve capped the file):

Jul 22 19:49:12 linux-vp82 sudo: root : TTY=pts/24 ; PWD=/home/kullmann/FrequencyUtility ; USER=root ; COMMAND=/usr/bin/cpufreq-set -c 3 -f 2.133GHz
Jul 22 20:06:27 linux-vp82 kernel: imklog 5.6.5, log source = /proc/kmsg started.
Jul 22 20:06:27 linux-vp82 rsyslogd: [origin software=“rsyslogd” swVersion=“5.6.5” x-pid=“1183” x-info=“http://www.rsyslog.com”] start
Jul 22 20:06:27 linux-vp82 kernel: 24.604969] type=1400 audit(1311361582.166:2): apparmor=“STATUS” operation=“profile_load” name="/bin/ping" pid=953 comm=“apparmor_parser”
Jul 22 20:06:27 linux-vp82 kernel: 24.681246] type=1400 audit(1311361582.243:3): apparmor=“STATUS” operation=“profile_load” name="/sbin/klogd" pid=958 comm=“apparmor_parser”
Jul 22 20:06:27 linux-vp82 kernel: 24.858702] type=1400 audit(1311361582.420:4): apparmor=“STATUS” operation=“profile_load” name="/sbin/syslog-ng" pid=962 comm=“apparmor_parser”
Jul 22 20:06:27 linux-vp82 kernel: 25.051424] type=1400 audit(1311361582.613:5): apparmor=“STATUS” operation=“profile_load” name="/sbin/syslogd" pid=966 comm=“apparmor_parser”
Jul 22 20:06:27 linux-vp82 kernel: 25.787054] type=1400 audit(1311361583.350:6): apparmor=“STATUS” operation=“profile_load” name="/usr/lib/apache2/mpm-prefork/apache2" pid=971 comm=“apparmor_parser”
Jul 22 20:06:27 linux-vp82 kernel: 25.787221] type=1400 audit(1311361583.351:7): apparmor=“STATUS” operation=“profile_load” name="/usr/lib/apache2/mpm-prefork/apache2//DEFAULT_URI" pid=971 comm=“apparmor_parser”
Jul 22 20:06:27 linux-vp82 kernel: 25.787317] type=1400 audit(1311361583.351:8): apparmor=“STATUS” operation=“profile_load” name="/usr/lib/apache2/mpm-prefork/apache2//HANDLING_UNTRUSTED_INPUT" pid=971 comm=“apparmor_parser”
Jul 22 20:06:27 linux-vp82 kernel: 25.787483] type=1400 audit(1311361583.351:9): apparmor=“STATUS” operation=“profile_load” name="/usr/lib/apache2/mpm-prefork/apache2//phpsysinfo" pid=971 comm=“apparmor_parser”
Jul 22 20:06:27 linux-vp82 kernel: 25.977769] type=1400 audit(1311361583.541:10): apparmor=“STATUS” operation=“profile_load” name="/usr/lib/dovecot/deliver" pid=975 comm=“apparmor_parser”
Jul 22 20:06:27 linux-vp82 kernel: 26.081236] type=1400 audit(1311361583.645:11): apparmor=“STATUS” operation=“profile_load” name="/usr/lib/dovecot/dovecot-auth" pid=979 comm=“apparmor_parser”
Jul 22 20:06:27 linux-vp82 kernel: 30.032727] ip6_tables: (C) 2000-2006 Netfilter Core Team
Jul 22 20:06:27 linux-vp82 kernel: 30.278907] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 22 20:06:28 linux-vp82 kernel: 30.440475] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 22 20:06:28 linux-vp82 SuSEfirewall2: Firewall rules set to CLOSE.
Jul 22 20:06:29 linux-vp82 kernel: 31.500071] BIOS EDD facility v0.16 2004-Jun-25, 1 devices found
Jul 22 20:06:29 linux-vp82 kernel: Kernel logging (proc) stopped.
Jul 22 20:06:29 linux-vp82 rsyslogd: [origin software=“rsyslogd” swVersion=“5.6.5” x-pid=“1183” x-info=“http://www.rsyslog.com”] exiting on signal 15.
Jul 22 20:06:29 linux-vp82 kernel: imklog 5.6.5, log source = /proc/kmsg started.
Jul 22 20:06:29 linux-vp82 rsyslogd: [origin software=“rsyslogd” swVersion=“5.6.5” x-pid=“1356” x-info=“http://www.rsyslog.com”] start
Jul 22 20:06:30 linux-vp82 avahi-daemon[1432]: Found user ‘avahi’ (UID 104) and group ‘avahi’ (GID 107).
Jul 22 20:06:30 linux-vp82 avahi-daemon[1432]: Successfully dropped root privileges.
Jul 22 20:06:30 linux-vp82 avahi-daemon[1432]: avahi-daemon 0.6.28 starting up.
Jul 22 20:06:30 linux-vp82 bluetoothd[1455]: Bluetooth deamon 4.88
Jul 22 20:06:30 linux-vp82 avahi-daemon[1432]: Loading service file /etc/avahi/services/sftp-ssh.service.
Jul 22 20:06:30 linux-vp82 avahi-daemon[1432]: Loading service file /etc/avahi/services/ssh.service.
Jul 22 20:06:30 linux-vp82 bluetoothd[1468]: Starting SDP server
Jul 22 20:06:30 linux-vp82 avahi-daemon[1432]: Loading service file /etc/avahi/services/udisks.service.
Jul 22 20:06:30 linux-vp82 network: Starting the NetworkManager
Jul 22 20:06:30 linux-vp82 kernel: 32.803345] Bluetooth: L2CAP ver 2.15
Jul 22 20:06:30 linux-vp82 kernel: 32.803348] Bluetooth: L2CAP socket layer initialized
Jul 22 20:06:30 linux-vp82 avahi-daemon[1432]: Network interface enumeration completed.
Jul 22 20:06:30 linux-vp82 avahi-daemon[1432]: Registering HINFO record with values ‘X86_64’/‘LINUX’.
Jul 22 20:06:30 linux-vp82 avahi-daemon[1432]: Server startup complete. Host name is linux-vp82.local. Local service cookie is 3533592466.
Jul 22 20:06:30 linux-vp82 avahi-daemon[1432]: Service “linux-vp82” (/etc/avahi/services/udisks.service) successfully established.
Jul 22 20:06:30 linux-vp82 avahi-daemon[1432]: Service “linux-vp82” (/etc/avahi/services/ssh.service) successfully established.
Jul 22 20:06:30 linux-vp82 avahi-daemon[1432]: Service “linux-vp82” (/etc/avahi/services/sftp-ssh.service) successfully established.
Jul 22 20:06:30 linux-vp82 auditd[1568]: Started dispatcher: /sbin/audispd pid: 1570
Jul 22 20:06:30 linux-vp82 audispd: priority_boost_parser called with: 4
Jul 22 20:06:30 linux-vp82 audispd: max_restarts_parser called with: 10
Jul 22 20:06:30 linux-vp82 audispd: No plugins found, exiting
Jul 22 20:06:30 linux-vp82 auditd[1568]: Init complete, auditd 2.0.5 listening for events (startup state disable)
Jul 22 20:06:30 linux-vp82 bluetoothd[1468]: Parsing /etc/bluetooth/input.conf failed: No such file or directory
Jul 22 20:06:30 linux-vp82 bluetoothd[1468]: Parsing /etc/bluetooth/audio.conf failed: No such file or directory
Jul 22 20:06:30 linux-vp82 kernel: 33.121069] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Jul 22 20:06:30 linux-vp82 kernel: 33.121072] Bluetooth: BNEP filters: protocol multicast
Jul 22 20:06:30 linux-vp82 mcelog: Unsupported new Family 6 Model 25 CPU: only decoding architectural errors
Jul 22 20:06:30 linux-vp82 mcelog: failed to prefill DIMM database from DMI data
Jul 22 20:06:31 linux-vp82 kernel: 33.514491] Bluetooth: SCO (Voice Link) ver 0.6
Jul 22 20:06:31 linux-vp82 kernel: 33.514493] Bluetooth: SCO socket layer initialized
Jul 22 20:06:31 linux-vp82 bluetoothd[1468]: Listening for HCI events on hci0
Jul 22 20:06:31 linux-vp82 bluetoothd[1468]: HCI dev 0 up
Jul 22 20:06:31 linux-vp82 kdm_config[1358]: Multiple occurrences of section [General] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them.
Jul 22 20:06:31 linux-vp82 kdm_config[1419]: Multiple occurrences of section [General] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them.
Jul 22 20:06:31 linux-vp82 kdm_config[1419]: Multiple occurrences of section [Xdmcp] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them.
Jul 22 20:06:31 linux-vp82 kdm_config[1358]: Multiple occurrences of section [Xdmcp] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them.
Jul 22 20:06:31 linux-vp82 kdm_config[1419]: Multiple occurrences of section [X--Core] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them.
Jul 22 20:06:31 linux-vp82 kdm_config[1358]: Multiple occurrences of section [X--Core] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them.
Jul 22 20:06:31 linux-vp82 kdm_config[1358]: Multiple occurrences of section [X--Greeter] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them.
Jul 22 20:06:31 linux-vp82 kdm_config[1419]: Multiple occurrences of section [X--Greeter] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them.
Jul 22 20:06:31 linux-vp82 kdm_config[1358]: Multiple occurrences of key ‘UseTheme’ in section [X--Greeter] of /usr/share/kde4/config/kdm/kdmrc
Jul 22 20:06:31 linux-vp82 kdm_config[1419]: Multiple occurrences of key ‘UseTheme’ in section [X--Greeter] of /usr/share/kde4/config/kdm/kdmrc
Jul 22 20:06:31 linux-vp82 kdm_config[1358]: Multiple occurrences of section [X-:-Core] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them.
Jul 22 20:06:31 linux-vp82 kdm_config[1358]: Multiple occurrences of section [X-:0-Core] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them.
Jul 22 20:06:31 linux-vp82 kdm_config[1419]: Multiple occurrences of section [X-:-Core] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them.
Jul 22 20:06:31 linux-vp82 kdm_config[1419]: Multiple occurrences of section [X-:0-Core] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them.
Jul 22 20:06:31 linux-vp82 kdm[1418]: Cannot create/lock pid file /var/run/kdm.pid
Jul 22 20:06:31 linux-vp82 bluetoothd[1468]: Parsing /etc/bluetooth/serial.conf failed: No such file or directory
Jul 22 20:06:31 linux-vp82 kernel: 34.124940] Bluetooth: RFCOMM TTY layer initialized
Jul 22 20:06:31 linux-vp82 kernel: 34.124947] Bluetooth: RFCOMM socket layer initialized
Jul 22 20:06:31 linux-vp82 kernel: 34.124949] Bluetooth: RFCOMM ver 1.11
Jul 22 20:06:31 linux-vp82 bluetoothd[1468]: Adapter /org/bluez/1455/hci0 has been enabled
Jul 22 20:06:32 linux-vp82 sshd[1644]: Server listening on 0.0.0.0 port 22.
Jul 22 20:06:32 linux-vp82 sshd[1644]: Server listening on :: port 22.
Jul 22 20:06:32 linux-vp82 acpid: 1 client rule loaded
Jul 22 20:06:32 linux-vp82 polkitd[1547]: started daemon version 0.99 using authority implementation local' version 0.99’
Jul 22 20:06:33 linux-vp82 modem-manager: ModemManager (version 0.4) starting…
Jul 22 20:06:33 linux-vp82 modem-manager: Loaded plugin Novatel
Jul 22 20:06:33 linux-vp82 modem-manager: Loaded plugin AnyData
Jul 22 20:06:33 linux-vp82 modem-manager: Loaded plugin Sierra
Jul 22 20:06:33 linux-vp82 modem-manager: Loaded plugin Ericsson MBM
Jul 22 20:06:33 linux-vp82 modem-manager: Loaded plugin Nokia
Jul 22 20:06:33 linux-vp82 modem-manager: Loaded plugin Option High-Speed
Jul 22 20:06:33 linux-vp82 modem-manager: Loaded plugin SimTech
Jul 22 20:06:33 linux-vp82 modem-manager: Loaded plugin Huawei
Jul 22 20:06:33 linux-vp82 modem-manager: Loaded plugin Gobi
Jul 22 20:06:33 linux-vp82 modem-manager: Loaded plugin Option
Jul 22 20:06:33 linux-vp82 modem-manager: Loaded plugin Generic
Jul 22 20:06:33 linux-vp82 modem-manager: Loaded plugin MotoC
Jul 22 20:06:33 linux-vp82 modem-manager: Loaded plugin ZTE
Jul 22 20:06:33 linux-vp82 modem-manager: Loaded plugin Longcheer
Jul 22 20:06:33 linux-vp82 modem-manager: (tty/ttyS0): port’s parent platform driver is not whitelisted
Jul 22 20:06:33 linux-vp82 modem-manager: (tty/ttyS1): port’s parent platform driver is not whitelisted
Jul 22 20:06:33 linux-vp82 modem-manager: (tty/ttyS2): port’s parent platform driver is not whitelisted
Jul 22 20:06:33 linux-vp82 modem-manager: (tty/ttyS3): port’s parent platform driver is not whitelisted
Jul 22 20:06:33 linux-vp82 modem-manager: (tty/ttyS4): port’s parent platform driver is not whitelisted
Jul 22 20:06:33 linux-vp82 modem-manager: (tty/ttyS5): port’s parent platform driver is not whitelisted
Jul 22 20:06:33 linux-vp82 modem-manager: (tty/ttyS6): port’s parent platform driver is not whitelisted
Jul 22 20:06:33 linux-vp82 modem-manager: (tty/ttyS7): port’s parent platform driver is not whitelisted
Jul 22 20:06:33 linux-vp82 kernel: 35.666165] r8169 0000:05:00.0: eth0: link up
Jul 22 20:06:33 linux-vp82 kernel: 35.666172] r8169 0000:05:00.0: eth0: link up
Jul 22 20:06:33 linux-vp82 /usr/sbin/cron[1866]: (CRON) STARTUP (1.4.7)
Jul 22 20:06:33 linux-vp82 /usr/sbin/cron[1866]: (CRON) bad username (/etc/cron.d/smolt)
Jul 22 20:06:33 linux-vp82 /usr/sbin/cron[1866]: (CRON) INFO (running with inotify support)
Jul 22 20:06:33 linux-vp82 dhclient: Internet Systems Consortium DHCP Client 4.2.1
Jul 22 20:06:33 linux-vp82 dhclient: Copyright 2004-2011 Internet Systems Consortium.
Jul 22 20:06:33 linux-vp82 dhclient: All rights reserved.
Jul 22 20:06:33 linux-vp82 dhclient: For info, please visit https://www.isc.org/software/dhcp/
Jul 22 20:06:33 linux-vp82 dhclient:
Jul 22 20:06:34 linux-vp82 kernel: 36.711936] NET: Registered protocol family 17
Jul 22 20:06:34 linux-vp82 dhclient: Listening on LPF/eth0/f0:4d:a2:45:c1:7a
Jul 22 20:06:34 linux-vp82 dhclient: Sending on LPF/eth0/f0:4d:a2:45:c1:7a
Jul 22 20:06:34 linux-vp82 dhclient: Sending on Socket/fallback
Jul 22 20:06:34 linux-vp82 smartd[1912]: smartd 5.40 2010-10-16 r3189 [x86_64-unknown-linux-gnu] (SUSE RPM)#012Copyright (C) 2002-10 by Bruce Allen, smartmontools
Jul 22 20:06:34 linux-vp82 smartd[1912]: Opened configuration file /etc/smartd.conf
Jul 22 20:06:34 linux-vp82 smartd[1912]: Drive: DEVICESCAN, implied ‘-a’ Directive on line 26 of file /etc/smartd.conf
Jul 22 20:06:34 linux-vp82 smartd[1912]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
Jul 22 20:06:34 linux-vp82 smartd[1912]: Device: /dev/sda, type changed from ‘scsi’ to ‘sat’
Jul 22 20:06:34 linux-vp82 smartd[1912]: Device: /dev/sda [SAT], opened
Jul 22 20:06:34 linux-vp82 smartd[1912]: Device: /dev/sda [SAT], found in smartd database.
Jul 22 20:06:35 linux-vp82 avahi-daemon[1432]: Registering new address record for fe80::f24d:a2ff:fe45:c17a on eth0.*.
Jul 22 20:06:35 linux-vp82 smartd[1912]: Device: /dev/sda [SAT], is SMART capable. Adding to “monitor” list.
Jul 22 20:06:35 linux-vp82 smartd[1912]: Device: /dev/sda [SAT], state read from /var/lib/smartmontools/smartd.WDC_WD5000BEVT_75A0RT0-WD_WXB1A60V9698.ata.state
Jul 22 20:06:35 linux-vp82 smartd[1912]: Monitoring 1 ATA and 0 SCSI devices
Jul 22 20:06:35 linux-vp82 smartd[1912]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.WDC_WD5000BEVT_75A0RT0-WD_WXB1A60V9698.ata.state

thanks

Oliver

P.S. no more happy dreams :-((( ;<|

kullmann · July 22, 2011, 9:42pm

And the output of lspci -v is

00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 18)
Subsystem: Dell Device 0434
Flags: bus master, fast devsel, latency 0
Capabilities: [e0] Vendor Specific Information: Len=0c <?>

00:01.0 PCI bridge: Intel Corporation Core Processor PCI Express x16 Root Port (rev 18) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: 00002000-00002fff
Memory behind bridge: cfe00000-cfefffff
Prefetchable memory behind bridge: 00000000d0000000-00000000dfffffff
Capabilities: [88] Subsystem: Dell Device 0434
Capabilities: [80] Power Management version 3
Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-
Capabilities: [a0] Express Root Port (Slot+), MSI 00
Capabilities: [100] Virtual Channel

00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06)
Subsystem: Dell Device 0434
Flags: bus master, fast devsel, latency 0, IRQ 5
Memory at f0305800 (64-bit, non-prefetchable) [size=16]
Capabilities: [50] Power Management version 3
Capabilities: [8c] MSI: Enable- Count=1/1 Maskable- 64bit+

00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06) (prog-if 20 [EHCI])
Subsystem: Dell Device 0434
Flags: bus master, medium devsel, latency 0, IRQ 16
Memory at f0306000 (32-bit, non-prefetchable) [size=1]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port: BAR=1 offset=00a0
Capabilities: [98] PCI Advanced Features
Kernel driver in use: ehci_hcd

00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06)
Subsystem: Dell Device 0434
Flags: bus master, fast devsel, latency 0, IRQ 43
Memory at f0300000 (64-bit, non-prefetchable) [size=16]
Capabilities: [50] Power Management version 2
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [130] Root Complex Link
Kernel driver in use: HDA Intel

00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 06) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
I/O behind bridge: 00004000-00004fff
Memory behind bridge: c0000000-c01fffff
Prefetchable memory behind bridge: 00000000c0200000-00000000c03fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: Dell Device 0434
Capabilities: [a0] Power Management version 2

00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 06) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
I/O behind bridge: 00005000-00005fff
Memory behind bridge: f0200000-f02fffff
Prefetchable memory behind bridge: 00000000c0400000-00000000c05fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: Dell Device 0434
Capabilities: [a0] Power Management version 2

00:1c.5 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 6 (rev 06) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=05, subordinate=05, sec-latency=0
I/O behind bridge: 00003000-00003fff
Memory behind bridge: c0600000-c09fffff
Prefetchable memory behind bridge: 00000000f0400000-00000000f04fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: Dell Device 0434
Capabilities: [a0] Power Management version 2

00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06) (prog-if 20 [EHCI])
Subsystem: Dell Device 0434
Flags: bus master, medium devsel, latency 0, IRQ 23
Memory at f0306400 (32-bit, non-prefetchable) [size=1]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port: BAR=1 offset=00a0
Capabilities: [98] PCI Advanced Features
Kernel driver in use: ehci_hcd

00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a6) (prog-if 01 [Subtractive decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=06, subordinate=06, sec-latency=0
Capabilities: [50] Subsystem: Dell Device 0434

00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 06)
Subsystem: Dell Device 0434
Flags: bus master, medium devsel, latency 0
Capabilities: [e0] Vendor Specific Information: Len=10 <?>

00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA AHCI Controller (rev 06) (prog-if 01 [AHCI 1.0])
Subsystem: Dell Device 0434
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 40
I/O ports at 1830 [size=8]
I/O ports at 1824 [size=4]
I/O ports at 1828 [size=8]
I/O ports at 1820 [size=4]
I/O ports at 1800 [size=32]
Memory at f0305000 (32-bit, non-prefetchable) [size=2]
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [70] Power Management version 3
Capabilities: [a8] SATA HBA v1.0
Capabilities: [b0] PCI Advanced Features
Kernel driver in use: ahci

00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 06)
Subsystem: Dell Device 0434
Flags: medium devsel, IRQ 18
Memory at f0306800 (64-bit, non-prefetchable) [size=256]
I/O ports at 1840 [size=32]

00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 06)
Subsystem: Dell Device 0434
Flags: fast devsel, IRQ 18
Memory at f0304000 (64-bit, non-prefetchable) [size=4]
Capabilities: [50] Power Management version 3
Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
Kernel driver in use: intel ips

02:00.0 VGA compatible controller: ATI Technologies Inc Manhattan [Mobility Radeon HD 5000 Series] (prog-if 00 [VGA controller])
Subsystem: Dell Device 0434
Flags: bus master, fast devsel, latency 0, IRQ 41
Memory at d0000000 (64-bit, prefetchable) [size=256]
Memory at cfee0000 (64-bit, non-prefetchable) [size=128]
I/O ports at 2000 [size=256]
[virtual] Expansion ROM at cfe00000 [disabled] [size=128]
Capabilities: [50] Power Management version 3
Capabilities: [58] Express Legacy Endpoint, MSI 00
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
Kernel driver in use: radeon

02:00.1 Audio device: ATI Technologies Inc Manhattan HDMI Audio [Mobility Radeon HD 5000 Series]
Subsystem: Dell Device 0434
Flags: bus master, fast devsel, latency 0, IRQ 44
Memory at cfedc000 (64-bit, non-prefetchable) [size=16]
Capabilities: [50] Power Management version 3
Capabilities: [58] Express Legacy Endpoint, MSI 00
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
Kernel driver in use: HDA Intel

04:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)
Subsystem: Dell Wireless 1397 WLAN Mini-Card
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at f0200000 (64-bit, non-prefetchable) [size=16]
Capabilities: [40] Power Management version 3
Capabilities: [58] Vendor Specific Information: Len=78 <?>
Capabilities: [e8] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [d0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Virtual Channel
Capabilities: [160] Device Serial Number 81-e6-a1-ff-ff-ff-70-f1
Capabilities: [16c] Power Budgeting <?>
Kernel driver in use: b43-pci-bridge

05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
Subsystem: Dell Device 0434
Flags: bus master, fast devsel, latency 0, IRQ 42
I/O ports at 3000 [size=256]
Memory at f0410000 (64-bit, prefetchable) [size=4]
Memory at f0400000 (64-bit, prefetchable) [size=64]
[virtual] Expansion ROM at f0420000 [disabled] [size=128]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 01
Capabilities: [ac] MSI-X: Enable- Count=2 Masked-
Capabilities: [cc] Vital Product Data
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Virtual Channel
Capabilities: [160] Device Serial Number 01-00-00-00-ff-ff-00-00
Kernel driver in use: r8169

ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 05)
Subsystem: Intel Corporation Device 8086
Flags: bus master, fast devsel, latency 0

ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 05)
Subsystem: Intel Corporation Device 8086
Flags: bus master, fast devsel, latency 0

ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 05)
Subsystem: Intel Corporation Device 8086
Flags: bus master, fast devsel, latency 0

ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 05)
Subsystem: Intel Corporation Device 8086
Flags: bus master, fast devsel, latency 0

ff:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 05)
Subsystem: Intel Corporation Device 8086
Flags: bus master, fast devsel, latency 0

ff:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 05)
Subsystem: Intel Corporation Device 8086
Flags: bus master, fast devsel, latency 0[/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size]

kullmann · July 25, 2011, 7:43pm

Hi,

over the weekend there were no further dark/blinking screen deaths, so let’s forget for now about that.
However the X-server crashes (that is apparently the meaning of the “dizzy screen crash”) continue:

Suspending-to-RAM once typically works, but then the second time the X-server crashes.
Since the screen is dysfunctional, all what I can do is to shut down. But is there a possibility
to restart the X-server? I’ve heard about Ctrl-Alt-Backspace, but that is just a no-op. Shall
I configure something?

Better, how can I avoid the crashes at all?

Should I start a new threat, for “X server crash after suspend-to-RAM”?

Oliver

kullmann · July 31, 2011, 2:18am

Hello,

after a few days of peace, I just had another crash:

Now I use kernel-version

> uname -a
Linux linux-vp82.site 2.6.38.8-0.5-desktop #1 SMP PREEMPT Fri Jul 29 00:59:42 BST 2011 x86_64 x86_64 x86_64 GNU/Linux

and that might have changed a bit: before I had the dark screen death (just black screen) and the blinking screen death (blinking
coloured pattern), in both cases apparently the machine dead (no sign of activity, no reaction to anything), and in both cases
also no traces in any log-files. Now I got the same sudden death, but now a black screen with a few red squares on it.
One might consider this as a kind of synthesis (the abyss and the chaos sublimated in a reawakening of suprematism),
so I will try a higher kernel version, hoping for a revelation. Also as before, the death was repeated on the second(!) rebooting.

Let’s see.

Oliver

kullmann · August 6, 2011, 8:25pm

Just a quick update:

newer kernel version


kullmann-0:~> uname -a
Linux linux-vp82.site 2.6.39.3-0.5-desktop #1 SMP PREEMPT Sun Jul 31 02:04:11 BST 2011 x86_64 x86_64 x86_64 GNU/Linux

But again there was a sudden death with few red squares; /var/log/messages says nothing:


Aug  6 13:17:11 linux-vp82 smartd[2210]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 121 to 119
Aug  6 13:47:18 linux-vp82 smartd[2210]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 119 to 123
Aug  6 18:36:31 linux-vp82 kernel: imklog 5.6.5, log source = /proc/kmsg started.
Aug  6 18:36:31 linux-vp82 rsyslogd: [origin software="rsyslogd" swVersion="5.6.5" x-pid="1037" x-info="http://www.rsyslog.com"] start

At around 14:00 the crash happened.

Oliver

kasi042 · August 6, 2011, 9:43pm

Hi,

I’m not an expert on this. I know CPU’s can get pretty hot.

Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 119 to 123

Is the HDD supposed to work at temperatures beyond 100°C i.e. 123°?
I’m not sure if there is a relation but if yes, it might be worth a try getting the temperature down.

rds

kasi

kullmann · August 6, 2011, 10:07pm

According to
Hot Drives: Dealing with SMART data on OpenSuse 10.3 | Late Night PC
these aren’t real temperatures, and reading the temperatures via smartctl yields


root-0:kullmann> smartctl --all /dev/sda
...
194 Temperature_Celsius     0x0022   119   095   000    Old_age   Always       -       28
...
root-0:kullmann> smartctl --all /dev/sdc
194 Temperature_Celsius     0x0022   120   109   000    Old_age   Always       -       30

So I think the disk temperatures are really okay (also it feels like that).
And actually both disks (internal and externals) weren’t working when the crash happened.

Temperature on this machine is kind of a problem, as discussed at
Very poor CPU performance, likely due to bad heat management
but therefore I’m constantly monitoring it, and the cpu-temperature didn’t exceed 84 degree Celsius (and I’m using
an external cooling device).

This type of crash can also happen directly when booting (exactly at that moment, when the screen goes completely
dark — there it can happen that it crashes), and it happened after suspend-to-disk.

So I’m quite sure it is not temperature-related.

Thanks nevertheless.

Oliver

kullmann · August 12, 2011, 11:19pm

Just had another crash (as usual now, black screen with some read squares, no reaction to anything,
hard disk dead), as usual without a trace (/var/log/messages):

Aug 12 19:36:29 linux-vp82 dhclient: bound to 192.168.1.64 – renewal in 36791 seconds.
Aug 12 19:44:42 linux-vp82 smartd[1674]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 117 to 118
Aug 12 20:44:44 linux-vp82 rsyslogd: – MARK –
Aug 12 21:34:59 linux-vp82 kernel: imklog 5.6.5, log source = /proc/kmsg started.
Aug 12 21:34:59 linux-vp82 rsyslogd: [origin software=“rsyslogd” swVersion=“5.6.5” x-pid=“1022” x-info=“http://www.rsyslog.com”] start

The crash happened around 21:30. This time the machine has been running for several hours, screen turned out and locked,
I hit a key, first second it looked like as usual, and then it crashed.

INTERESTINGLY, it seems always to happen that after the first crash on booting it crashes a second time!
Very short after the boot menu it crashes with the same screen pattern.
Only then with the second boot it gets up. This second crash leaves absolutely no trace in /var/log/messages
(apparently it happens before the logging starts).

Are there other logging files worth to investigate?

To me it looks like a clear software error: it seems not to happen under Windows (I let it run for quite some time,
never a crash), and that it always happens after rebooting seems also to indicate that it’s a software problem.

kullmann · September 6, 2011, 9:03am

I noticed that the crash seemed always related to the screen going dark, that is, the crash either
happened after rewaking from Suspen-to-RAM/disk or in connection with the screensaver.

So first I disabled the screensaver (KDE System Settings/Hardware/Screen Saver), but I got another crash.
Then I disabled the automatic dimming of the display, in System Settings/Hardware/Power Management/Power Profiles,
for the profile “Performance” I’m running), and since then I had no crash: For over a week now, and also
Suspend-to-Ram works now without crashing (while before at least with the second time it would crash after
waking up). (Suspend-to-disk just doesn’t work: it never achieves it.)

This night I had the curious event of the laptop by itself performing Suspend-to-RAM: there was a short
power failure, where the Laptop switched to Powersave mode (I guess), which has “Suspend Session”
enabled, and then apparently this setting prevailed also after return of the power.
Looks like a bug to me, but so well. (It would be good if in /var/log/messages we had general informative messages
like “I start now the boot process” or, in this case, “Starting Suspend-to-Ram, because no user-action has been
performed for 10m, and I’m in power-mode Powersave, where automatic suspension has been set.” This
is trivial to do, and would solve A LARGE AMOUNT OF PROBLEMS, for everybody (given that this is done
systematically). Sigh, the problem is of course, that the kernel is written by hackers, who don’t like to speak …)

Now I have the problem that I need to find out how to shut off the monitor manually: After activating the screen saver
(manually), the screen used to go rather dark (though I’m not sure whether this was fully dark), however now it stays
rather bright, you can read a book. Anybody any idea?

Oliver

DenverD · September 6, 2011, 9:57am

On 09/06/2011 09:06 AM, kullmann wrote:
>
> happened after rewaking from Suspen-to-RAM/disk or in connection with
> the screensaver.

free advice: do not select ‘random’ for the screensaver…because it
will eventually find one that does not like your system, and causes a
crash, freeze or some other strange problem…

i prefer “blank screen”…suggest you pick one, and stick to it…see
if that helps at all…

–
DD
Caveat-Hardware-Software-
openSUSE®, the “German Automobiles” of operating systems

kullmann · September 6, 2011, 10:14am

I already only use the blank screensaver (never could stand that noise created by any
other screensaver).

And perhaps the screensaver is not the problem: Okay, I didn’t try to have screensaver
activated while automatic dimming deactivated, whether this might also cause the
crash. I (somehow) guess that’s not the case, and that the screensaver is not guilty here.
(Trying this out takes possibly some time, and moreover, it interrupts my computations.
And then, due to these many errors in KDE, after restarting most windows are lost or
redistributed to other desktops, and the settings for Konsole-windows are lost, …
so it always takes at least 10m after a restart to get back to a not completely unreasonable desktop.)