[Bug 57118] xorg-server-1.13.0 lockups with intel driver >= 2.20.10
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu Nov 29 01:54:55 PST 2012
https://bugs.freedesktop.org/show_bug.cgi?id=57118
--- Comment #8 from Tassilo Horn <tsdh at gnu.org> ---
(In reply to comment #7)
> If the machine was no longer accessible over the network, you have a much
> more serious problem. The first issue you reported was that your compositing
> manager stopped drawing, a symptom that is likely the result of the patch I
> suggested.
Well, I could still move my mouse, and the mouse pointer even changed its shape
over window boarders. Not sure if that falls into the responsibility of the
composition manager...
> This issue is however a system freeze, a kernel bug.
Hm, ok. But in any way, I get the same symptoms since 2.20.10. I'd say in
about 50% of the cases I could still ssh to the machine and get a backtrace
like the attached one, and in the other 50% I couldn't connect to it.
> Look for anything unusual in dmesg.
The dmesg log starts at boot time. How can I get the previous dmesg log after
rebooting the machine?
But here's the journald log for the specific period around the latest X freeze.
The freeze occured somewhere at 08:07. Immediately I went into another room,
logged into another machine and tried to ssh into my machine. You can see the
failing ssh logins because of some pam issue. At 08:10:53 I was back in my
room and rebooted using Magic SysRQ keys.
Nov 29 08:07:01 thinkpad /USR/SBIN/CROND[3558]: (horn) CMD (cd ~/GoogleDrive/
&& ping -c 1 www.google.de > /dev/null 2>&1 && grive >
/dev/null 2>&1)
Nov 29 08:07:11 thinkpad CROND[3557]: pam_unix(crond:session): session closed
for user horn
Nov 29 08:07:15 thinkpad kernel: usb 1-4.6.1: unlink qh8-0e01/ffff880131cefd00
start 5 [1/2 us]
Nov 29 08:08:01 thinkpad crond[3594]: pam_unix(crond:session): session opened
for user horn by (uid=0)
Nov 29 08:08:26 thinkpad crond[3594]: pam_systemd(crond:session): Failed to
create session: 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 29 08:08:26 thinkpad /USR/SBIN/CROND[3600]: (horn) CMD (cd ~/GoogleDrive/
&& ping -c 1 www.google.de > /dev/null 2>&1 && grive > /dev/null 2>&1)
Nov 29 08:09:01 thinkpad crond[3608]: pam_unix(crond:session): session opened
for user horn by (uid=0)
Nov 29 08:09:09 thinkpad dhcpcd[428]: wlan0: renewing lease of 141.26.93.134
Nov 29 08:09:11 thinkpad systemd[1]: Starting OpenSSH per-connection server
daemon...
Nov 29 08:09:11 thinkpad systemd[1]: Started OpenSSH per-connection server
daemon.
Nov 29 08:09:12 thinkpad sshd[3611]: SSH: Server;Ltype: Kex;Remote:
141.26.69.157-41931;Enc: aes128-ctr;MAC: hmac-md5;Comp: none [preauth]
Nov 29 08:09:14 thinkpad sshd[3611]: SSH: Server;Ltype: Authname;Remote:
141.26.69.157-41931;Name: horn [preauth]
Nov 29 08:09:19 thinkpad sshd[3611]: Accepted keyboard-interactive/pam for horn
from 141.26.69.157 port 41931 ssh2
Nov 29 08:09:19 thinkpad sshd[3611]: pam_unix(sshd:session): session opened for
user horn by (uid=0)
Nov 29 08:09:26 thinkpad crond[3608]: pam_systemd(crond:session): Failed to
create session: 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 29 08:09:26 thinkpad /USR/SBIN/CROND[3619]: (horn) CMD (cd ~/GoogleDrive/
&& ping -c 1 www.google.de > /dev/null 2>&1 && grive > /dev/null 2>&1)
Nov 29 08:09:44 thinkpad sshd[3611]: pam_systemd(sshd:session): Failed to
create session: 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 29 08:09:59 thinkpad console-kit-daemon[259]: console-kit-daemon[259]:
WARNING: The program /usr/lib/ConsoleKit/run-session.d/pam-foreground-compat.ck
didn't exit within 15 seconds; killing it
Nov 29 08:09:59 thinkpad console-kit-daemon[259]: WARNING: The program
/usr/lib/ConsoleKit/run-session.d/pam-foreground-compat.ck didn't exit within
15 seconds; killing it
Nov 29 08:10:01 thinkpad crond[3630]: pam_unix(crond:session): session opened
for user horn by (uid=0)
Nov 29 08:10:01 thinkpad crond[3629]: pam_unix(crond:session): session opened
for user root by (uid=0)
Nov 29 08:10:24 thinkpad sshd[3611]: pam_systemd(sshd:session): Failed to
create session: 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 29 08:10:24 thinkpad sshd[3611]: Received disconnect from 141.26.69.157:
11: disconnected by user
Nov 29 08:10:24 thinkpad sshd[3611]: pam_unix(sshd:session): session closed for
user horn
Nov 29 08:10:26 thinkpad crond[3630]: pam_systemd(crond:session): Failed to
create session: 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 29 08:10:26 thinkpad crond[3629]: pam_systemd(crond:session): Failed to
create session: 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 29 08:10:26 thinkpad /USR/SBIN/CROND[3646]: (root) CMD (test -x
/usr/sbin/run-crons && /usr/sbin/run-crons )
Nov 29 08:10:26 thinkpad /USR/SBIN/CROND[3645]: (horn) CMD (cd ~/GoogleDrive/
&& ping -c 1 www.google.de > /dev/null 2>&1 && grive > /dev/null 2>&1)
Nov 29 08:10:39 thinkpad console-kit-daemon[259]: console-kit-daemon[259]:
WARNING: The program /usr/lib/ConsoleKit/run-session.d/pam-foreground-compat.ck
didn't exit within 15 seconds; killing it
Nov 29 08:10:39 thinkpad console-kit-daemon[259]: WARNING: The program
/usr/lib/ConsoleKit/run-session.d/pam-foreground-compat.ck didn't exit within
15 seconds; killing it
Nov 29 08:10:53 thinkpad systemd-journal[3667]: Allowing system journal files
to grow to 4.0G.
Nov 29 08:10:53 thinkpad kernel: ACPI: Invalid Power Resource to register!
Nov 29 08:10:53 thinkpad kernel: SysRq :
Nov 29 08:10:53 thinkpad kernel: Emergency Sync
Nov 29 08:10:53 thinkpad kernel: Emergency Sync complete
Nov 29 08:10:53 thinkpad kernel: SysRq :
Nov 29 08:10:53 thinkpad kernel: Emergency Sync
Nov 29 08:10:53 thinkpad kernel: Emergency Sync complete
Nov 29 08:10:53 thinkpad kernel: SysRq :
Nov 29 08:10:53 thinkpad kernel: Kill All Tasks
Nov 29 08:10:53 thinkpad systemd[1]: Unit systemd-journald.service entered
failed state
Nov 29 08:10:53 thinkpad systemd[1]: cups.service: main process exited,
code=killed, status=9/KILL
Nov 29 08:10:53 thinkpad systemd[1]: Unit cups.service entered failed state
Nov 29 08:10:53 thinkpad systemd[1]: ntp.service: main process exited,
code=killed, status=9/KILL
Nov 29 08:10:53 thinkpad systemd[1]: Unit ntp.service entered failed state
Nov 29 08:10:53 thinkpad systemd[1]: cronie.service: main process exited,
code=killed, status=9/KILL
Nov 29 08:10:53 thinkpad systemd[1]: colord.service: main process exited,
code=killed, status=9/KILL
Nov 29 08:10:53 thinkpad systemd[1]: Unit colord.service entered failed state
Nov 29 08:10:53 thinkpad systemd[1]: accounts-daemon.service: main process
exited, code=killed, status=9/KILL
Nov 29 08:10:53 thinkpad systemd[1]: Unit accounts-daemon.service entered
failed state
Nov 29 08:10:53 thinkpad systemd[1]: wpa_supplicant.service: main process
exited, code=killed, status=9/KILL
Nov 29 08:10:53 thinkpad systemd[1]: Unit wpa_supplicant.service entered failed
state
Nov 29 08:10:53 thinkpad systemd[1]: avahi-daemon.service: main process exited,
code=killed, status=9/KILL
Nov 29 08:10:53 thinkpad systemd[1]: Unit avahi-daemon.service entered failed
state
Nov 29 08:10:53 thinkpad systemd[1]: NetworkManager.service: main process
exited, code=killed, status=9/KILL
Nov 29 08:10:53 thinkpad systemd[1]: Unit NetworkManager.service entered failed
state
Nov 29 08:10:53 thinkpad systemd[1]: lightdm.service: main process exited,
code=killed, status=9/KILL
Nov 29 08:10:53 thinkpad systemd[1]: dbus.service: main process exited,
code=killed, status=9/KILL
Nov 29 08:10:53 thinkpad systemd[1]: Unit dbus.service entered failed state
Nov 29 08:10:53 thinkpad systemd[1]: polkit.service: main process exited,
code=killed, status=9/KILL
Nov 29 08:10:53 thinkpad systemd[1]: Unit polkit.service entered failed state
Nov 29 08:10:53 thinkpad systemd[1]: upower.service: main process exited,
code=killed, status=9/KILL
Nov 29 08:10:53 thinkpad systemd[1]: Unit upower.service entered failed state
Nov 29 08:10:53 thinkpad systemd[1]: udisks2.service: main process exited,
code=killed, status=9/KILL
Nov 29 08:10:53 thinkpad systemd[1]: Unit udisks2.service entered failed state
Nov 29 08:10:53 thinkpad systemd[1]: systemd-udevd.service holdoff time over,
scheduling restart.
Nov 29 08:10:53 thinkpad systemd[1]: Stopping udev Kernel Device Manager...
Nov 29 08:10:53 thinkpad systemd[1]: Starting udev Kernel Device Manager...
Nov 29 08:10:53 thinkpad systemd[1]: systemd-journald.service holdoff time
over, scheduling restart.
Nov 29 08:10:53 thinkpad systemd[1]: Stopping Journal Service...
Nov 29 08:10:53 thinkpad systemd[1]: Starting Journal Service...
Nov 29 08:10:53 thinkpad systemd[1]: Started Journal Service.
Nov 29 08:10:53 thinkpad systemd[1]: Starting Trigger Flushing of Journal to
Persistent Storage...
Nov 29 08:10:53 thinkpad systemd-udevd[3666]: starting version 195
Nov 29 08:10:53 thinkpad systemd-journal[3667]: Journal started
Nov 29 08:10:53 thinkpad systemd[1]: systemd-udevd.service: main process
exited, code=killed, status=9/KILL
Nov 29 08:10:53 thinkpad systemd[1]: Unit systemd-udevd.service entered failed
state
Nov 29 08:10:53 thinkpad systemd[1]: systemd-journald.service: main process
exited, code=killed, status=9/KILL
Nov 29 08:10:53 thinkpad systemd[1]: Started udev Kernel Device Manager.
Nov 29 08:10:53 thinkpad systemd-udevd[3666]: IMPORT{builtin}: 'uaccess'
unknown /usr/lib64/udev/rules.d/73-seat-late.rules:15
Nov 29 08:10:53 thinkpad systemd[1]: Started Trigger Flushing of Journal to
Persistent Storage.
Nov 29 08:10:54 thinkpad systemd-journal[3673]: Allowing system journal files
to grow to 4.0G.
Nov 29 08:10:54 thinkpad systemd-journald[3667]: Received SIGUSR1
Nov 29 08:10:54 thinkpad kernel: SysRq :
Nov 29 08:10:54 thinkpad kernel: Kill All Tasks
Nov 29 08:10:54 thinkpad systemd[1]: Unit systemd-journald.service entered
failed state
Nov 29 08:10:54 thinkpad systemd[1]: systemd-udevd.service holdoff time over,
scheduling restart.
Nov 29 08:10:54 thinkpad systemd[1]: Stopping udev Kernel Device Manager...
Nov 29 08:10:54 thinkpad systemd[1]: Starting udev Kernel Device Manager...
Nov 29 08:10:54 thinkpad systemd[1]: systemd-journald.service holdoff time
over, scheduling restart.
Nov 29 08:10:54 thinkpad systemd[1]: Stopping Journal Service...
Nov 29 08:10:54 thinkpad systemd[1]: Starting Journal Service...
Nov 29 08:10:54 thinkpad systemd-udevd[3672]: starting version 195
Nov 29 08:10:54 thinkpad systemd[1]: Started Journal Service.
Nov 29 08:10:54 thinkpad systemd[1]: Starting Trigger Flushing of Journal to
Persistent Storage...
Nov 29 08:10:54 thinkpad systemd-journal[3673]: Journal started
Nov 29 08:10:54 thinkpad systemd[1]: systemd-udevd.service: main process
exited, code=killed, status=9/KILL
Nov 29 08:10:54 thinkpad systemd[1]: Unit systemd-udevd.service entered failed
state
Nov 29 08:10:54 thinkpad systemd[1]: systemd-journald.service: main process
exited, code=killed, status=9/KILL
Nov 29 08:10:54 thinkpad systemd[1]: Started udev Kernel Device Manager.
Nov 29 08:10:54 thinkpad systemd-udevd[3672]: IMPORT{builtin}: 'uaccess'
unknown /usr/lib64/udev/rules.d/73-seat-late.rules:15
Nov 29 08:10:54 thinkpad systemd[1]: Started Trigger Flushing of Journal to
Persistent Storage.
-- Reboot --
--
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20121129/12947dae/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list