| 2009-01-12 22:39:41 |
max |
bug |
|
|
added bug |
| 2009-01-14 18:06:58 |
max |
bug |
|
|
added attachment 'xorg.conf' (xorg.conf) |
| 2009-01-14 18:13:44 |
max |
bug |
|
|
added attachment 'Xorg.0.log' (Xorg.0.log) |
| 2009-01-14 18:14:21 |
max |
bug |
|
|
added attachment 'Xorg.0.log.old' (Xorg.0.log.old) |
| 2009-01-14 18:14:47 |
max |
bug |
|
|
added attachment 'Xorg.20.log' (Xorg.20.log) |
| 2009-01-14 18:15:18 |
max |
bug |
|
|
added attachment 'Xorg.20.log.old' (Xorg.20.log.old) |
| 2009-01-14 18:18:02 |
max |
bug |
|
|
added attachment '.xsession-errors' (.xsession-errors) |
| 2009-01-14 18:18:37 |
max |
bug |
|
|
added attachment '.xsession-errors.old' (.xsession-errors.old) |
| 2009-01-14 18:19:58 |
max |
bug |
|
|
added attachment '.xsession-errors (copy)' (.xsession-errors (copy)) |
| 2009-01-14 21:34:01 |
max |
bug |
|
|
added attachment 'kern.log-fragment' (kern.log-fragment) |
| 2009-01-16 05:12:55 |
Bryce Harrington |
xorg: status |
New |
Incomplete |
|
| 2009-01-16 12:26:33 |
max |
bug |
|
|
added attachment 'lspci' (lspci -vvnn) |
| 2009-01-16 21:09:58 |
max |
xorg: status |
Incomplete |
New |
|
| 2009-01-16 21:09:58 |
max |
xorg: statusexplanation |
|
|
|
| 2009-01-17 09:23:08 |
Bryce Harrington |
xorg: status |
New |
Incomplete |
|
| 2009-01-17 09:23:08 |
Bryce Harrington |
xorg: statusexplanation |
|
Max, unfortunately none of these files show an error message or backtrace. No troubleshooting can begin until we know what the error is.
Perhaps they are in one of your files in /var/log/gdm/. Look in your :0.log.1, :0.log.2, etc. to see if it indicates an error.
|
|
| 2009-01-17 09:28:53 |
Bryce Harrington |
xorg: bugtargetdisplayname |
xorg (Ubuntu) |
Ubuntu |
|
| 2009-01-17 09:28:53 |
Bryce Harrington |
xorg: bugtargetname |
xorg (Ubuntu) |
ubuntu |
|
| 2009-01-17 09:28:53 |
Bryce Harrington |
xorg: statusexplanation |
Max, unfortunately none of these files show an error message or backtrace. No troubleshooting can begin until we know what the error is.
Perhaps they are in one of your files in /var/log/gdm/. Look in your :0.log.1, :0.log.2, etc. to see if it indicates an error.
|
Ahh, I spoke too soon. Your kernel log does indeed show a problem:
Jan 14 14:57:37 max-work-lap kernel: [ 203.600093] Call Trace:
Jan 14 14:57:37 max-work-lap kernel: [ 203.600106] [<ffffffff802aff35>] oom_kill_process+0x95/0x240
Jan 14 14:57:37 max-work-lap kernel: [ 203.600113] [<ffffffff802b06ef>] ? select_bad_process+0xef/0x130
Jan 14 14:57:37 max-work-lap kernel: [ 203.600120] [<ffffffff802b07e4>] out_of_memory+0xb4/0x150
Jan 14 14:57:37 max-work-lap kernel: [ 203.600129] [<ffffffff804958a0>] ? moom_callback+0x0/0x20
Jan 14 14:57:37 max-work-lap kernel: [ 203.600135] [<ffffffff804958b7>] moom_callback+0x17/0x20
Jan 14 14:57:37 max-work-lap kernel: [ 203.600142] [<ffffffff8026113a>] run_workqueue+0xba/0x190
Jan 14 14:57:37 max-work-lap kernel: [ 203.600148] [<ffffffff80261417>] worker_thread+0xa7/0x120
Jan 14 14:57:37 max-work-lap kernel: [ 203.600155] [<ffffffff80265770>] ? autoremove_wake_function+0x0/0x40
Jan 14 14:57:37 max-work-lap kernel: [ 203.600161] [<ffffffff80261370>] ? worker_thread+0x0/0x120
Jan 14 14:57:37 max-work-lap kernel: [ 203.600167] [<ffffffff80265309>] kthread+0x49/0x90
Jan 14 14:57:37 max-work-lap kernel: [ 203.600174] [<ffffffff80213979>] child_rip+0xa/0x11
Jan 14 14:57:37 max-work-lap kernel: [ 203.600180] [<ffffffff802652c0>] ? kthread+0x0/0x90
Jan 14 14:57:37 max-work-lap kernel: [ 203.600186] [<ffffffff8021396f>] ? child_rip+0x0/0x11
The kernel is calling the "Out of Memory killer", "oom_kill_process". This means that your system has catastrophically run out of memory for some reason. This is not an Xorg bug, so I'm refiling to Ubuntu for better triaging.
Meanwhile, look into why you would be running out of memory. Are you running a program that uses too much memory? Is your hardware memory bad? Do you have enough of it? There are various programs, like 'top', which you can use to display memory usage and watch the memory use of different processes so you can learn which package has the fault.
Good luck! |
|
| 2009-01-17 09:28:53 |
Bryce Harrington |
xorg: title |
Bug #316566 in xorg (Ubuntu): "xorg freeze randomly" |
Bug #316566 in Ubuntu: "xorg freeze randomly" |
|
| 2009-01-17 10:05:53 |
Bryce Harrington |
title |
xorg freeze randomly |
oom killer causes xorg to freeze |
|
| 2009-01-17 13:33:20 |
max |
bug |
|
|
added attachment 'kern.log' (Kern.log on clear system after freezing) |
| 2009-01-18 15:48:46 |
max |
bug |
|
|
added attachment 'kern.log' (kern.log) |
| 2009-01-18 15:49:39 |
max |
bug |
|
|
added attachment 'kern.log.0' (kern.log.0) |
| 2009-01-18 22:58:12 |
max |
bug |
|
|
added attachment 'lspci' (lspci -vv) |
| 2009-01-18 23:05:12 |
max |
bug |
|
|
added attachment 'lshw' (lshw) |
| 2009-01-18 23:05:39 |
max |
bug |
|
|
added attachment 'lsusb' (lsusb) |
| 2009-01-18 23:25:59 |
max |
title |
oom killer causes xorg to freeze |
Xorg randomly freeze |
|
| 2009-01-19 00:43:22 |
Bryce Harrington |
marked as duplicate |
|
318600 |
|
| 2009-01-19 00:44:00 |
Bryce Harrington |
title |
Xorg randomly freeze |
system randomly freezes |
|
| 2009-05-02 21:31:30 |
lasombra |
attachment added |
|
dmesg.zip http://launchpadlibrarian.net/26260827/dmesg.zip |
|
| 2009-05-02 21:32:01 |
lasombra |
attachment added |
|
Xorg.0.log http://launchpadlibrarian.net/26260829/Xorg.0.log |
|
| 2009-05-02 21:32:43 |
lasombra |
attachment added |
|
lspci_vv http://launchpadlibrarian.net/26260846/lspci_vv |
|
| 2009-05-02 21:34:11 |
lasombra |
attachment added |
|
lshw http://launchpadlibrarian.net/26260882/lshw |
|
| 2009-05-02 21:35:23 |
lasombra |
attachment added |
|
lsusb http://launchpadlibrarian.net/26260910/lsusb |
|
