System freeze with possible HDD/SATA link problem

enigmatichus · 2013-11-21 15:53:43

Hello,
I'm experiencing frequent system hard locks without ability to use TTYs nor Ctrl+Alt+Bkspc or any other keyboard input, often with caps-lock led blinking. I splitted this post from another thread I posted originally on because it may not be related to original post problem:
original post.
System is a Dell XPS L702X with a SATA Seagate Momentus 7200.4 500GB hard drive. I've tried several different kernels (3.10-lts, 3.11.x 3.12 for x86, all of them with PAE enabled and disabled), but I cannot say how much this is relevant, since so far I've experienced problems with every kernel I tried. The most usual log entry I see is in kernel.log:

[43329.363003] ata6.00: exception Emask 0x10 SAct 0x0 SErr 0x50000 action 0xe frozen
[43329.363006] ata6.00: irq_stat 0x00400000, PHY RDY changed
[43329.363008] ata6: SError: { PHYRdyChg CommWake }
[43329.363011] sr 5:0:0:0: CDB: 
[43329.363012] cdb[0]=0x4a: 4a 01 00 00 10 00 00 00 08 00
[43329.363018] ata6.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 0 pio 16392 in
[43329.363018]          res 50/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x10 (ATA bus error)
[43329.363020] ata6.00: status: { DRDY }
[43329.363023] ata6: hard resetting link
[43330.112721] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[43330.118491] ata6.00: configured for UDMA/100
[43330.132756] ata6: EH complete

I failed to find any certain clue on the Internet so far, and I don't know yet if this may or may not be a hardware drive problem or a hardware SATA link problem (according to a full SMART analysis, there are no pre-failure conditions), but another seemingly unrelated but evident problem is that often, before a lock-up, in kernel.log I can see some core dumps, with most usual processes which dump core being pulseaudio, alsa-sink, network-manager, sd_festival, chromium and emacs. This is not constant, so again I failed to find a direct link to a problem. I include additional kernel.log informations, as in my original post in the above link:
kernel.log.0
kernel.log.1
I'm sorry if there are missing informations or if I missed an existing relevant thread, but I don't properly know where to start.
Thanks,
Luca

enigmatichus · 2013-11-21 23:23:37

Completely disabling SATA power management in laptop-mode let the ata errors disappear, but several hard freezes still occured. I think that logs may miss some crucial information which simply can't get written in. Exploring journalctl output gives me no more informations:

# journalctl --since=yesterday --until=now -p 3
nov 21 15:22:52 anubis gdm[992]: GLib-GObject: g_object_ref: assertion 'object->ref_count > 0' failed
nov 21 15:22:52 anubis gdm[992]: GLib-GObject: g_object_unref: assertion 'object->ref_count > 0' failed
nov 21 15:22:52 anubis gdm[992]: GLib-GObject: g_object_ref: assertion 'object->ref_count > 0' failed
nov 21 15:22:52 anubis gdm[992]: GLib-GObject: g_object_unref: assertion 'object->ref_count > 0' failed
nov 21 15:22:52 anubis gdm[992]: GLib-GObject: g_object_ref: assertion 'object->ref_count > 0' failed
nov 21 15:22:52 anubis gdm[992]: GLib-GObject: g_object_unref: assertion 'object->ref_count > 0' failed
nov 21 15:22:52 anubis gdm[992]: GLib-GObject: g_object_ref: assertion 'object->ref_count > 0' failed
nov 21 15:22:52 anubis gdm[992]: GLib-GObject: g_object_unref: assertion 'object->ref_count > 0' failed
nov 21 15:22:52 anubis gdm[992]: GLib-GObject: g_object_ref: assertion 'object->ref_count > 0' failed
nov 21 15:22:52 anubis gdm[992]: GLib-GObject: g_object_unref: assertion 'object->ref_count > 0' failed
nov 21 15:22:52 anubis gdm[992]: GLib-GObject: g_object_ref: assertion 'object->ref_count > 0' failed
nov 21 15:22:52 anubis gdm[992]: GLib-GObject: g_object_unref: assertion 'object->ref_count > 0' failed
nov 21 15:22:52 anubis gdm[992]: GLib-GObject: g_object_ref: assertion 'object->ref_count > 0' failed
nov 21 15:22:52 anubis gdm[992]: GLib-GObject: g_object_unref: assertion 'object->ref_count > 0' failed
nov 21 15:26:23 anubis login[1629]: pam_systemd(login:session): Failed to release session: Connection was disconnected before a reply was received
nov 21 15:26:23 anubis NetworkManager[951]: dbus_g_proxy_begin_call: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed
nov 21 15:26:23 anubis NetworkManager[951]: dbus_g_proxy_begin_call: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed
nov 21 15:26:23 anubis NetworkManager[951]: dbus_g_proxy_begin_call: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed
nov 21 15:26:24 anubis NetworkManager[951]: dbus_g_proxy_begin_call: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed
nov 21 15:26:24 anubis NetworkManager[951]: dbus_g_proxy_call_no_reply: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed
nov 21 15:26:24 anubis NetworkManager[951]: dbus_g_proxy_new_for_name: assertion 'connection != NULL' failed
nov 21 15:26:24 anubis NetworkManager[951]: <error> [1385043984.595613] [nm-dispatcher.c:285] _dispatcher_call(): could not get dispatcher proxy!
nov 21 15:26:24 anubis kernel: watchdog watchdog0: watchdog did not stop!
-- Reboot --
nov 21 15:27:34 anubis pulseaudio[1793]: [pulseaudio] bluetooth-util.c: org.bluez.Manager.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method "GetProperties" with signature "" on interface "org.bluez.Manager" doesn't exist
-- Reboot --
nov 21 15:34:17 anubis pulseaudio[1795]: [pulseaudio] bluetooth-util.c: org.bluez.Manager.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method "GetProperties" with signature "" on interface "org.bluez.Manager" doesn't exist
nov 21 15:48:14 anubis systemd-tmpfiles[3024]: stat(/run/user/1000/gvfs) failed: Permission denied
nov 21 15:53:45 anubis systemd-coredump[3211]: Process 3210 (sd_festival) dumped core.
nov 21 15:53:45 anubis pulseaudio[1795]: [alsa-sink-ALC665 Analog] alsa-sink.c: Attivazione da parte di ALSA per scrivere nuovi dati sul dispositivo, ma non c'era nulla da scrivere.
nov 21 15:53:45 anubis pulseaudio[1795]: [alsa-sink-ALC665 Analog] alsa-sink.c: Molto probabilmente si tratta di un bug nei driver ALSA "snd_hda_intel". Segnalare questo problema agli sviluppatori di ALSA.
nov 21 15:53:45 anubis pulseaudio[1795]: [alsa-sink-ALC665 Analog] alsa-sink.c: Attivazione avvenuta con POLLOUT impostato -- tuttavia, una successiva snd_pcm_avail() ha ritornato 0 o un altro valore < min_avail.
nov 21 15:55:38 anubis gdm[995]: GLib-GObject: g_object_ref: assertion 'object->ref_count > 0' failed
nov 21 15:55:38 anubis NetworkManager[955]: dbus_g_proxy_begin_call: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed
nov 21 15:55:38 anubis NetworkManager[955]: dbus_g_proxy_begin_call: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed
nov 21 15:55:38 anubis NetworkManager[955]: dbus_g_proxy_begin_call: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed
nov 21 15:55:40 anubis NetworkManager[955]: dbus_g_proxy_begin_call: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed
nov 21 15:55:40 anubis NetworkManager[955]: dbus_g_proxy_call_no_reply: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed
nov 21 15:55:40 anubis NetworkManager[955]: dbus_g_proxy_new_for_name: assertion 'connection != NULL' failed
nov 21 15:55:40 anubis NetworkManager[955]: <error> [1385045740.172903] [nm-dispatcher.c:285] _dispatcher_call(): could not get dispatcher proxy!
nov 21 15:55:40 anubis gdm[995]: GLib-GObject: g_object_unref: assertion 'object->ref_count > 0' failed
nov 21 15:55:40 anubis systemd[1]: Failed unmounting /tmp.
nov 21 15:55:40 anubis systemd[1]: Failed unmounting /home.
-- Reboot --
nov 21 16:07:49 anubis pulseaudio[1794]: [pulseaudio] bluetooth-util.c: org.bluez.Manager.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method "GetProperties" with signature "" on interface "org.bluez.Manager" doesn't exist
nov 21 16:22:01 anubis systemd-tmpfiles[2805]: stat(/run/user/1000/gvfs) failed: Permission denied
nov 21 17:05:49 anubis dhclient[1607]: receive_packet failed on wlan0: Network is down
nov 21 17:05:51 anubis gdm[989]: GLib-GObject: g_object_ref: assertion 'object->ref_count > 0' failed
nov 21 17:05:51 anubis gdm[989]: GLib-GObject: g_object_unref: assertion 'object->ref_count > 0' failed
nov 21 17:05:52 anubis systemd[1]: Failed unmounting /tmp.
nov 21 17:05:52 anubis systemd[1]: Failed unmounting /home.
-- Reboot --
nov 21 17:07:08 anubis pulseaudio[1766]: [pulseaudio] bluetooth-util.c: org.bluez.Manager.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method "GetProperties" with signature "" on interface "org.bluez.Manager" doesn't exist
nov 21 17:21:20 anubis systemd-tmpfiles[2374]: stat(/run/user/1000/gvfs) failed: Permission denied
nov 21 18:48:37 anubis systemd-coredump[2904]: Process 2903 (sd_festival) dumped core.
nov 21 19:10:24 anubis gdm[996]: GLib-GObject: g_object_ref: assertion 'object->ref_count > 0' failed
nov 21 19:10:24 anubis NetworkManager[953]: dbus_g_proxy_begin_call: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed
nov 21 19:10:24 anubis NetworkManager[953]: dbus_g_proxy_begin_call: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed
nov 21 19:10:24 anubis NetworkManager[953]: dbus_g_proxy_begin_call: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed
nov 21 19:10:24 anubis gdm[996]: GLib-GObject: g_object_unref: assertion 'object->ref_count > 0' failed
nov 21 19:10:24 anubis NetworkManager[953]: dbus_g_proxy_begin_call: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed
nov 21 19:10:24 anubis NetworkManager[953]: dbus_g_proxy_call_no_reply: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed
nov 21 19:10:24 anubis NetworkManager[953]: dbus_g_proxy_new_for_name: assertion 'connection != NULL' failed
nov 21 19:10:24 anubis NetworkManager[953]: <error> [1385057424.942622] [nm-dispatcher.c:285] _dispatcher_call(): could not get dispatcher proxy!
nov 21 19:10:25 anubis systemd[1]: Failed unmounting /home.
nov 21 19:10:25 anubis systemd[1]: Failed unmounting /tmp.
-- Reboot --
nov 21 20:03:21 anubis pulseaudio[1765]: [pulseaudio] bluetooth-util.c: org.bluez.Manager.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method "GetProperties" with signature "" on interface "org.bluez.Manager" doesn't exist
nov 21 20:04:59 anubis systemd-coredump[2628]: Process 2627 (sd_festival) dumped core.
nov 21 20:17:33 anubis systemd-tmpfiles[3334]: stat(/run/user/1000/gvfs) failed: Permission denied
nov 21 21:17:43 anubis kernel: iwlwifi 0000:03:00.0: fail to flush all tx fifo queues Q 2
nov 21 21:17:44 anubis kernel: iwlwifi 0000:03:00.0: Current SW read_ptr 76 write_ptr 122
nov 21 21:17:44 anubis kernel: iwl data: 00000000: 00 e0 ff 0f 00 00 00 00 00 00 00 00 00 00 00 00  ................
nov 21 21:17:44 anubis kernel: iwlwifi 0000:03:00.0: FH TRBs(0) = 0x80003007
nov 21 21:17:44 anubis kernel: iwlwifi 0000:03:00.0: FH TRBs(1) = 0x8010205b
nov 21 21:17:44 anubis kernel: iwlwifi 0000:03:00.0: FH TRBs(2) = 0x80201001
nov 21 21:17:44 anubis kernel: iwlwifi 0000:03:00.0: FH TRBs(3) = 0x803000ac
nov 21 21:17:44 anubis kernel: iwlwifi 0000:03:00.0: FH TRBs(4) = 0x00000000
nov 21 21:17:44 anubis kernel: iwlwifi 0000:03:00.0: FH TRBs(5) = 0x00000000
nov 21 21:17:44 anubis kernel: iwlwifi 0000:03:00.0: FH TRBs(6) = 0x00000000
nov 21 21:17:44 anubis kernel: iwlwifi 0000:03:00.0: FH TRBs(7) = 0x00704077
nov 21 21:17:44 anubis kernel: iwlwifi 0000:03:00.0: Q 0 is active and mapped to fifo 3 ra_tid 0x0000 [173,173]
nov 21 21:17:44 anubis kernel: iwlwifi 0000:03:00.0: Q 1 is active and mapped to fifo 2 ra_tid 0x0000 [2,2]
nov 21 21:17:44 anubis kernel: iwlwifi 0000:03:00.0: Q 2 is active and mapped to fifo 1 ra_tid 0x0000 [77,122]
nov 21 21:17:44 anubis kernel: iwlwifi 0000:03:00.0: Q 3 is active and mapped to fifo 0 ra_tid 0x0000 [8,8]
nov 21 21:17:44 anubis kernel: iwlwifi 0000:03:00.0: Q 4 is active and mapped to fifo 7 ra_tid 0x0000 [120,120]
nov 21 21:17:44 anubis kernel: iwlwifi 0000:03:00.0: Q 5 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
nov 21 21:17:44 anubis kernel: iwlwifi 0000:03:00.0: Q 6 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
nov 21 21:17:44 anubis kernel: iwlwifi 0000:03:00.0: Q 7 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
nov 21 21:17:44 anubis kernel: iwlwifi 0000:03:00.0: Q 8 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
nov 21 21:17:44 anubis kernel: iwlwifi 0000:03:00.0: Q 9 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
nov 21 21:17:44 anubis kernel: iwlwifi 0000:03:00.0: Q 10 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
nov 21 21:17:44 anubis kernel: iwlwifi 0000:03:00.0: Q 11 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
nov 21 21:17:44 anubis kernel: iwlwifi 0000:03:00.0: Q 12 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
nov 21 21:17:44 anubis kernel: iwlwifi 0000:03:00.0: Q 13 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
nov 21 21:17:44 anubis kernel: iwlwifi 0000:03:00.0: Q 14 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
nov 21 21:17:44 anubis kernel: iwlwifi 0000:03:00.0: Q 15 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
nov 21 21:17:44 anubis kernel: iwlwifi 0000:03:00.0: Q 16 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
nov 21 21:17:44 anubis kernel: iwlwifi 0000:03:00.0: Q 17 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
nov 21 21:17:44 anubis kernel: iwlwifi 0000:03:00.0: Q 18 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
nov 21 21:17:44 anubis kernel: iwlwifi 0000:03:00.0: Q 19 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
nov 21 21:17:45 anubis kernel: iwlwifi 0000:03:00.0: fail to flush all tx fifo queues Q 2
nov 21 21:17:45 anubis kernel: iwlwifi 0000:03:00.0: Current SW read_ptr 101 write_ptr 44
nov 21 21:17:45 anubis kernel: iwl data: 00000000: 00 00 00 00 00 00 00 00 e0 3f 00 00 00 00 00 00  .........?......
nov 21 21:17:45 anubis kernel: iwlwifi 0000:03:00.0: FH TRBs(0) = 0x80003007
nov 21 21:17:45 anubis kernel: iwlwifi 0000:03:00.0: FH TRBs(1) = 0x8010206d
nov 21 21:17:45 anubis kernel: iwlwifi 0000:03:00.0: FH TRBs(2) = 0x80201001
nov 21 21:17:45 anubis kernel: iwlwifi 0000:03:00.0: FH TRBs(3) = 0x803000ae
nov 21 21:17:45 anubis kernel: iwlwifi 0000:03:00.0: FH TRBs(4) = 0x00000000
nov 21 21:17:45 anubis kernel: iwlwifi 0000:03:00.0: FH TRBs(5) = 0x00000000
nov 21 21:17:45 anubis kernel: iwlwifi 0000:03:00.0: FH TRBs(6) = 0x00000000
nov 21 21:17:45 anubis kernel: iwlwifi 0000:03:00.0: FH TRBs(7) = 0x00704079
nov 21 21:17:45 anubis kernel: iwlwifi 0000:03:00.0: Q 0 is active and mapped to fifo 3 ra_tid 0x0000 [175,175]
nov 21 21:17:45 anubis kernel: iwlwifi 0000:03:00.0: Q 1 is active and mapped to fifo 2 ra_tid 0x0000 [2,2]
nov 21 21:17:45 anubis kernel: iwlwifi 0000:03:00.0: Q 2 is active and mapped to fifo 1 ra_tid 0x0000 [101,44]
nov 21 21:17:45 anubis kernel: iwlwifi 0000:03:00.0: Q 3 is active and mapped to fifo 0 ra_tid 0x0000 [8,8]
nov 21 21:17:45 anubis kernel: iwlwifi 0000:03:00.0: Q 4 is active and mapped to fifo 7 ra_tid 0x0000 [122,122]
nov 21 21:17:45 anubis kernel: iwlwifi 0000:03:00.0: Q 5 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
nov 21 21:17:45 anubis kernel: iwlwifi 0000:03:00.0: Q 6 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
nov 21 21:17:45 anubis kernel: iwlwifi 0000:03:00.0: Q 7 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
nov 21 21:17:45 anubis kernel: iwlwifi 0000:03:00.0: Q 8 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
nov 21 21:17:45 anubis kernel: iwlwifi 0000:03:00.0: Q 9 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
nov 21 21:17:45 anubis kernel: iwlwifi 0000:03:00.0: Q 10 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
nov 21 21:17:45 anubis kernel: iwlwifi 0000:03:00.0: Q 11 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
nov 21 21:17:45 anubis kernel: iwlwifi 0000:03:00.0: Q 12 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
nov 21 21:17:45 anubis kernel: iwlwifi 0000:03:00.0: Q 13 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
nov 21 21:17:45 anubis kernel: iwlwifi 0000:03:00.0: Q 14 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
nov 21 21:17:45 anubis kernel: iwlwifi 0000:03:00.0: Q 15 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
nov 21 21:17:45 anubis kernel: iwlwifi 0000:03:00.0: Q 16 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
nov 21 21:17:45 anubis kernel: iwlwifi 0000:03:00.0: Q 17 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
nov 21 21:17:45 anubis kernel: iwlwifi 0000:03:00.0: Q 18 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
nov 21 21:17:45 anubis kernel: iwlwifi 0000:03:00.0: Q 19 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
-- Reboot --
nov 21 22:53:52 anubis pulseaudio[1759]: [pulseaudio] bluetooth-util.c: org.bluez.Manager.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method "GetProperties" with signature "" on interface "org.bluez.Manager" doesn't exist
nov 21 23:07:56 anubis systemd-tmpfiles[2952]: stat(/run/user/1000/gvfs) failed: Permission denied
nov 21 23:23:56 anubis gdm[995]: GLib-GObject: g_object_ref: assertion 'object->ref_count > 0' failed
nov 21 23:23:56 anubis gdm-password][1675]: pam_systemd(gdm-password:session): Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
nov 21 23:23:56 anubis NetworkManager[955]: dbus_g_proxy_begin_call: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed
nov 21 23:23:56 anubis NetworkManager[955]: dbus_g_proxy_begin_call: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed
nov 21 23:23:56 anubis NetworkManager[955]: dbus_g_proxy_begin_call: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed
nov 21 23:23:57 anubis NetworkManager[955]: dbus_g_proxy_begin_call: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed
nov 21 23:23:57 anubis NetworkManager[955]: dbus_g_proxy_call_no_reply: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed
nov 21 23:23:57 anubis NetworkManager[955]: dbus_g_proxy_new_for_name: assertion 'connection != NULL' failed
nov 21 23:23:57 anubis NetworkManager[955]: <error> [1385072637.461416] [nm-dispatcher.c:285] _dispatcher_call(): could not get dispatcher proxy!
nov 21 23:23:57 anubis gdm[995]: GLib-GObject: g_object_unref: assertion 'object->ref_count > 0' failed
nov 21 23:23:57 anubis systemd[1]: Failed unmounting /home.
nov 21 23:23:57 anubis systemd[1]: Failed unmounting /tmp.
-- Reboot --
nov 21 23:25:46 anubis pulseaudio[1765]: [pulseaudio] bluetooth-util.c: org.bluez.Manager.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method "GetProperties" with signature "" on interface "org.bluez.Manager" doesn't exist
nov 21 23:29:22 anubis systemd-coredump[2713]: Process 2712 (sd_festival) dumped core.
nov 21 23:39:34 anubis systemd-tmpfiles[2882]: stat(/run/user/1000/gvfs) failed: Permission denied
-- Reboot --
nov 22 00:04:14 anubis pulseaudio[1765]: [pulseaudio] bluetooth-util.c: org.bluez.Manager.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method "GetProperties" with signature "" on interface "org.bluez.Manager" doesn't exist
nov 22 00:05:27 anubis systemd-coredump[2313]: Process 2307 (journalctl) dumped core.
nov 22 00:05:56 anubis systemd-coredump[2321]: Process 1532 (Xorg) dumped core.
nov 22 00:05:57 anubis systemd-coredump[2324]: Process 1903 (tracker-miner-f) dumped core.
nov 22 00:05:57 anubis systemd-coredump[2326]: Process 1902 (nautilus) dumped core.
nov 22 00:06:54 anubis gdm[995]: GLib-GObject: g_object_ref: assertion 'object->ref_count > 0' failed
nov 22 00:06:54 anubis gdm[995]: GLib-GObject: g_object_unref: assertion 'object->ref_count > 0' failed
nov 22 00:08:57 anubis pulseaudio[2521]: [pulseaudio] bluetooth-util.c: org.bluez.Manager.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method "GetProperties" with signature "" on interface "org.bluez.Manager" doesn't exist

I explored several tracks.

iwlwifi 0000:03:00.0: fail to flush all tx fifo queues

seems related to a long-standing bug in kernel space involving some Intel Centrino wireless card, and I tried to disable 11n connectivity, which I think was pointless.
I could not understand why so many processes dump core and crash. Pulseaudio also complains about bluetooth modules (which I don't have installed on my laptop and therefore which I just don't want to be enabled), like:

[pulseaudio] bluetooth-util.c: org.bluez.Manager.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method "GetProperties" with signature "" on interface "org.bluez.Manager" doesn't exist

I don't know how much is relevant to the main problem. As you could easily guess, I don't know what to do and I feel a little bit lost right now.
I'll try to downgrade systemd to a pre-200 version since it gives me idea that it may have something to do with the problem.
Thanks,
Luca

Last edited by enigmatichus (2013-11-21 23:34:23)

enigmatichus · 2013-11-25 18:26:43

I'm resolving to reinstall Arch from the ground up in the next few days as things are getting worse. No clues about what's happening, for what I know it may even be an imminent hardware failure (hard disk *seems* ok according to SMART, checked RAM with a few memtests and it seems ok as well).
I attach a dmesg output I captured a few minutes ago, the system is not freezed yet even if pulseaudio crashed and volume control applet in gnome-shell disappeared, though sound is still correctly played.
dmesg output
Will report any update in situation, just for the sake of completeness.
Luca

Lone_Wolf · 2013-11-26 12:06:17

enigmatichus,

i just noticed something that i missed before : you appear to be using a pae enabled kernel.
Afaik the arch stock kernels have no pae support, so where did that kernel come from ?

Also, why are you using an i686 32-bit kernel on a system that should be x86_64 capable and has 8 GB ram ?

enigmatichus · 2013-11-26 12:10:43

I forgot to mention it, I was using PAE-enabled kernels (but I found problems even when using stock 32-bit kernel) from aur, from pae.archlinux.ca binary unofficial repository and from manually-recompiled stock kernel (by myself).
I'm preparing to reinstall the system from the ground up, last time (more than 2 years ago) I made the mistake of installing a 32-bit system, something I was too lazy to fix until this problem forced me to restart from zero.
I know, it's shameful that I'm using PAE rather than using 64-bit.
Thanks for your time,
Luca

jrussell · 2013-11-26 15:57:15

Had an issue with a sata cable here https://bbs.archlinux.org/viewtopic.php?pid=1350866, don't if that is going to help you, but there it is.

enigmatichus · 2013-11-26 16:00:44

jrussell wrote:

Had an issue with a sata cable here https://bbs.archlinux.org/viewtopic.php?pid=1350866, don't if that is going to help you, but there it is.

I'm checking right now, thank you.

nomorewindows · 2013-11-26 22:44:49

Seeing this problem in my dmesg occasionally. Not freezing most of the time. No reporting any problems with smartctl.

enigmatichus · 2013-11-26 23:00:55

nomorewindows wrote:

Seeing this problem in my dmesg occasionally. Not freezing most of the time. No reporting any problems with smartctl.

I will report when I can exclude hardware problems. This is a frankly slightly messed-up system, as I have never had time (in more than two years) to make a serious backup and wipe disk out (I heavily rely on this laptop for university, laziness is not a man's friend and this was the first Arch system I set up).

EDIT: again, logs: journalctl_output_20131127151000

Last edited by enigmatichus (2013-11-27 14:43:09)

nomorewindows · 2013-12-01 00:47:35

My disk keeps beeping and yep, there's the message in dmesg.

enigmatichus · 2013-12-07 18:08:07

Just formatted drive and reinstalled a plain updated system. Just had the first hard freezing with blinking caps-lock led.
I'm desperate and clueless. I can't exclude a hardware problem, as well as I cannnot determine if that could be the problem.

last freezing journald log

Even after no more than 20 minutes of use, dmesg spits message like these:

dic 07 19:03:55 anubis systemd-coredump[1361]: Process 1360 (sd_festival) dumped core.
dic 07 19:15:32 anubis systemd-tmpfiles[2345]: stat(/run/user/1000/gvfs) failed: Permission denied

Last edited by enigmatichus (2013-12-07 18:24:05)

Lone_Wolf · 2013-12-08 14:03:39

enigmatichus,

it's beginning to look like you got a hardware problem.

I suggest you try running from a live CD with support for X, like knoppix .
If that runs without problems, it's a software issue.
If not, it's very likely you got a HW problem.

enigmatichus · 2013-12-09 00:23:00

Lone_Wolf wrote:

enigmatichus,
it's beginning to look like you got a hardware problem.
I suggest you try running from a live CD with support for X, like knoppix .
If that runs without problems, it's a software issue.
If not, it's very likely you got a HW problem.

Thanks for the suggestion, I will try in the next days.

EDIT: journald log of last partial freeze (I was able to reboot system using tty but, apart from mouse movements, entire gnome-shell was freezed).

Last edited by enigmatichus (2013-12-09 12:56:18)

whaler · 2013-12-10 16:45:03

I am worried about a similar message:

# dmesg | grep sd_festival
[  140.699952] sd_festival[890]: segfault at 2d0 ip 00007fcaa0068191 sp 00007fff2b40e9f0 error 4 in libpthread-2.18.so[7fcaa005b000+18000]

What does 'sd_festival' refer to?

enigmatichus · 2013-12-10 18:22:27

whaler wrote:

I am worried about a similar message:

# dmesg | grep sd_festival
[  140.699952] sd_festival[890]: segfault at 2d0 ip 00007fcaa0068191 sp 00007fff2b40e9f0 error 4 in libpthread-2.18.so[7fcaa005b000+18000]

What does 'sd_festival' refer to?

It should be related to festival speech engine, but I don't know what kind of component it is. Anyway, I think it's something shipped with gnome-shell, maybe as accessibility component, as I don't have festival installed on my system.

whaler · 2013-12-11 08:28:20

Thanks, enigmatichus.

I don't have Festival installed either, or not as I know. However, writing 'festival' in KDE's K, I am referred to Accessibility --> Text to Speech, which cannot be configured, presumably/possibly because Festival is not installed?

Anyway, I find it strange if that alone should cause the rather sinister dmesg error report.

Last edited by whaler (2013-12-11 08:35:16)

enigmatichus · 2013-12-11 09:30:48

whaler wrote:

Thanks, enigmatichus.
I don't have Festival installed either, or not as I know. However, writing 'festival' in KDE's K, I am referred to Accessibility --> Text to Speech, which cannot be configured, presumably/possibly because Festival is not installed?
Anyway, I find it strange if that alone should cause the rather sinister dmesg error report.

I find it very strange too, but I have no clues on how much impact such a log entry could reflect. Looking forward to discover some new element on this matter.

enigmatichus · 2013-12-18 10:50:37

After a few days without any problem, another sd_festival core dump with hard lock and blinking caps-lock led. No way to check for a clear hardware failure.

dic 18 11:22:33 anubis systemd-coredump[1610]: Process 1609 (sd_festival) dumped core.

Lone_Wolf · 2013-12-18 12:16:20

SD_festival appears to be part of the speech-dispatcher 0.8-2 package, which doesn't have to many dependencies.

chromium
kdeaccessibility-jovie
kdeaccessibility-jovie (staging)
kdeaccessibility-kaccessible
kdeaccessibility-kaccessible (staging)
orca
python2-speechd

Is it possible for you to remove speech_dispatcher ?

enigmatichus · 2013-12-19 10:40:47

Lone_Wolf wrote:

SD_festival appears to be part of the speech-dispatcher 0.8-2 package, which doesn't have to many dependencies.
chromium
kdeaccessibility-jovie
kdeaccessibility-jovie (staging)
kdeaccessibility-kaccessible
kdeaccessibility-kaccessible (staging)
orca
python2-speechd
Is it possible for you to remove speech_dispatcher ?

I'm trying right now, thanks for insight!

enigmatichus · 2013-12-19 11:03:33

I just lost pulseaudio together with the sound control gnome applet, in dmesg there are a bunch of acpi warnings:

[   15.276409] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130725/nsarguments-95)
[   15.276476] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130725/nsarguments-95)
[   15.276508] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130725/nsarguments-95)
[   15.276537] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130725/nsarguments-95)
[   15.276565] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130725/nsarguments-95)
[   15.276681] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130725/nsarguments-95)
[   15.276710] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130725/nsarguments-95)
[   15.276738] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130725/nsarguments-95)
[   15.474417] wlp3s0: authenticate with 00:90:d0:dc:57:34
[   15.486826] wlp3s0: send auth to 00:90:d0:dc:57:34 (try 1/3)
[   15.489620] wlp3s0: authenticated
[   15.489769] iwlwifi 0000:03:00.0 wlp3s0: disabling HT/VHT due to WEP/TKIP use
[   15.490400] wlp3s0: associate with 00:90:d0:dc:57:34 (try 1/3)
[   15.493101] wlp3s0: RX AssocResp from 00:90:d0:dc:57:34 (capab=0x431 status=0 aid=4)
[   15.497018] wlp3s0: associated
[   15.497043] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
[   15.693352] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130725/nsarguments-95)
[   39.680547] fuse init (API version 7.22)
[  685.617956] alsa-sink-ALC66[704]: segfault at 7fd3360c5910 ip 00007fd3360c5910 sp 00007fd330e8b398 error 14 in libsamplerate.so.0.1.8[7fd336061000+1ff000]

And interestingly, when I was finishing this post, I suddendly had another hard freeze with caps-lock blinking led. Checking journald logs result in this:

dic 19 11:33:30 anubis kernel: ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument
dic 19 11:33:30 anubis kernel: ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument
dic 19 11:33:30 anubis kernel: ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument
dic 19 11:33:30 anubis kernel: ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument
dic 19 11:33:30 anubis kernel: ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument
dic 19 11:33:30 anubis kernel: ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument
dic 19 11:33:30 anubis kernel: ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument
dic 19 11:33:30 anubis kernel: ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument
dic 19 11:33:30 anubis kernel: ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument
dic 19 11:33:30 anubis dhcpcd[433]: wlp3s0: ipv6nd_sendrsprobe: sendmsg: Cannot 
dic 19 11:33:32 anubis systemd[445]: Failed to open private bus connection: Fail
dic 19 11:33:36 anubis gnome-session[446]: WARNING: Could not parse desktop file
dic 19 11:33:53 anubis systemd[604]: Failed to open private bus connection: Fail
dic 19 11:33:57 anubis pulseaudio[687]: [pulseaudio] bluez4-util.c: org.bluez.Ma
dic 19 11:44:40 anubis systemd-coredump[3253]: Process 687 (alsa-sink-ALC66) dum
dic 19 11:48:15 anubis systemd-tmpfiles[3303]: stat(/run/user/1000/gvfs) failed:
-- Reboot --

Apparently, after ACPI warning messages, the system was dying and those were the last log entries before the hard lock.

Last edited by enigmatichus (2013-12-19 11:46:49)

Lone_Wolf · 2013-12-19 12:14:38

Finally we're getting closer to finding the cause, it now looks like the sata link errors had very little to do with the real problem.

searching for "ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM" and "SB_.PCI0.PEG0.PEGP._DSM" gives many results about video problems and often mentions bumblebee.

please post lspci output .
Which video drivers do you have installed ?
Do you use bumblebee ?

Sidenote :
It may seem a bit weird that video problems would crash sound, but if your videocard supports HDMI then it supplies both video and audio.

enigmatichus · 2013-12-19 13:42:35

Lone_Wolf wrote:

Finally we're getting closer to finding the cause, it now looks like the sata link errors had very little to do with the real problem.
searching for "ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM" and "SB_.PCI0.PEG0.PEGP._DSM" gives many results about video problems and often mentions bumblebee.
please post lspci output .
Which video drivers do you have installed ?
Do you use bumblebee ?
Sidenote :
It may seem a bit weird that video problems would crash sound, but if your videocard supports HDMI then it supplies both video and audio.

Thanks for the reply. First of all, my lspci output:

$ lspci
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5)
00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5)
00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5)
00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5)
00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation HM67 Express Chipset Family LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
01:00.0 VGA compatible controller: NVIDIA Corporation GF106M [GeForce GT 555M] (rev a1)
01:00.1 Audio device: NVIDIA Corporation GF106 High Definition Audio Controller (rev a1)
03:00.0 Network controller: Intel Corporation Centrino Wireless-N 1000 [Condor Peak]
04:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04)
0a:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 06)

This machine is equipped with a 3D LCD panel, which implies that NVIDIA Optimus technology was disabled at hardware level, so I've never had to bother with bumblebee (NVIDIA card is just always on, together with the CPU-integrated VGA which is the actual video output, being hardwired with LCD display facilities). Video card is NVIDIA GT 555M, CPU is a Intel i7-2720QM Sandy Bridge.
I use nVidia proprietary video drivers (up-to-date 331.20-2 extra repository version), which usually works very well.
Again, thank you for the support, which is most appreciated.

Lone_Wolf · 2013-12-20 13:58:14

Ok, that makes clear that you do have hdmi audio and standard audio.

Unfortuntately I know little about pulseaudio (i prefer plain alsa) and/or the proprietary nvidia driver, so others will have to take over.

enigmatichus · 2013-12-20 14:12:11

Lone_Wolf wrote:

Ok, that makes clear that you do have hdmi audio and standard audio.
Unfortuntately I know little about pulseaudio (i prefer plain alsa) and/or the proprietary nvidia driver, so others will have to take over.

What I could do is try to disable at all the HDMI audio output and see if this helps since I just don't need the HDMI audio functionality right now.
Avoiding the use of chromium browser (which depends on speech-dispatcher, which usually shows itself in logs when system crashes) seems to help since I did not have any sd_festival dump core since then. I do almost always have those weird ACPI errors in dmesg, though.
Thanks for your support.

Arch Linux

#1 2013-11-21 15:53:43

System freeze with possible HDD/SATA link problem

#2 2013-11-21 23:23:37

Re: System freeze with possible HDD/SATA link problem

#3 2013-11-25 18:26:43

Re: System freeze with possible HDD/SATA link problem

#4 2013-11-26 12:06:17

Re: System freeze with possible HDD/SATA link problem

#5 2013-11-26 12:10:43

Re: System freeze with possible HDD/SATA link problem

#6 2013-11-26 15:57:15

Re: System freeze with possible HDD/SATA link problem

#7 2013-11-26 16:00:44

Re: System freeze with possible HDD/SATA link problem

#8 2013-11-26 22:44:49

Re: System freeze with possible HDD/SATA link problem

#9 2013-11-26 23:00:55

Re: System freeze with possible HDD/SATA link problem

#10 2013-12-01 00:47:35

Re: System freeze with possible HDD/SATA link problem

#11 2013-12-07 18:08:07

Re: System freeze with possible HDD/SATA link problem

#12 2013-12-08 14:03:39

Re: System freeze with possible HDD/SATA link problem

#13 2013-12-09 00:23:00

Re: System freeze with possible HDD/SATA link problem

#14 2013-12-10 16:45:03

Re: System freeze with possible HDD/SATA link problem

#15 2013-12-10 18:22:27

Re: System freeze with possible HDD/SATA link problem

#16 2013-12-11 08:28:20

Re: System freeze with possible HDD/SATA link problem

#17 2013-12-11 09:30:48

Re: System freeze with possible HDD/SATA link problem

#18 2013-12-18 10:50:37

Re: System freeze with possible HDD/SATA link problem

#19 2013-12-18 12:16:20

Re: System freeze with possible HDD/SATA link problem

#20 2013-12-19 10:40:47

Re: System freeze with possible HDD/SATA link problem

#21 2013-12-19 11:03:33

Re: System freeze with possible HDD/SATA link problem

#22 2013-12-19 12:14:38

Re: System freeze with possible HDD/SATA link problem

#23 2013-12-19 13:42:35

Re: System freeze with possible HDD/SATA link problem

#24 2013-12-20 13:58:14

Re: System freeze with possible HDD/SATA link problem

#25 2013-12-20 14:12:11

Re: System freeze with possible HDD/SATA link problem

Board footer