DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello everyone, I'm running the DebianEEEPC (Lenny) variant on my Asus EEEE 904HA netbook. It has been working quite well except for one recurrent and unfortunate problem: Occasionally X fails unexpectedly and won't restart until I reboot. The screen suddenly goes black and turns on and off a few times before displaying a blue screen with a gray box informing me that X has failed to initiate. Entering "startx" into a terminal does not work, but after rebooting X starts just fine as it always does.
So far I have not been able to reproduce this problem intentionally, but I have noticed that it only seems to occur while I am using Iceweasel. The last time it happened, I chose the "Restore previous session" option when I started Iceweasel again, and X crashed again a few seconds later, which reinforces my suspicion that it is somehow causing this to happen. This has never happened when I am not using Iceweasel.
The X error screen which appears after these crashes has an option to view some sort of logs, but does not offer an option to save a copy. Is there somewhere on the disk where these logs are stored, so that I might be able to post them here?
Well, I just experienced another crash, but unfortunately logs related to that crash appear to have been overwritten when I attempted startx. Next time I'll make copies of them first. I do have a little bit more information, though.
When I ran startx (after the crash), I got these error messages after failure:
Code:
xinit: Connection reset by peer (errno 104): unable to connect to X server
xinit: No such process (errno 3): Server error
And thankfully, I do have one of the logs from one of these attempts to start X. Here's the part where the failure happened, so far as I can tell:
Code:
...
(**) Generic Keyboard: XkbRules: "xorg"
(**) Option "XkbModel" "pc104"
(**) Generic Keyboard: XkbModel: "pc104"
(**) Option "XkbLayout" "us"
(**) Generic Keyboard: XkbLayout: "us"
(**) Option "CustomKeycodes" "off"
(**) Generic Keyboard: CustomKeycodes disabled
(II) evaluating device (Configured Mouse)
(II) XINPUT: Adding extended input device "Configured Mouse" (type: MOUSE)
(II) evaluating device (Generic Keyboard)
(II) XINPUT: Adding extended input device "Generic Keyboard" (type: KEYBOARD)
(--) Configured Mouse: PnP-detected protocol: "ExplorerPS/2"
(II) Configured Mouse: ps2EnableDataReporting: succeeded
Error in I830WaitLpRing(), timeout for 2 seconds
pgetbl_ctl: 0x3ffc0001 getbl_err: 0x00000000
ipeir: 0x00000000 iphdr: 0x54f00006
LP ring tail: 0x0000f3f0 head: 0x0000f414 len: 0x0001f001 start 0x00000000
eir: 0x0000 esr: 0x0000 emr: 0xffff
instdone: 0xfa41 instpm: 0x0000
memmode: 0x00000306 instps: 0x800f04d1
hwstam: 0xfffe ier: 0x0002 imr: 0x0000 iir: 0x0020
Ring at virtual 0xa78bb000 head 0xf414 tail 0xf3f0 count 32759
0000f394: 03cc1000
0000f398: 001c0258
0000f39c: 0020025c
0000f3a0: 00800000
0000f3a4: 00000000
0000f3a8: 00000010
0000f3ac: 00c00000
0000f3b0: 54f00006
0000f3b4: 03cc1000
0000f3b8: 001c025c
0000f3bc: 00200260
0000f3c0: 00800000
0000f3c4: 00000000
0000f3c8: 00000010
0000f3cc: 00c00000
0000f3d0: 54f00006
0000f3d4: 03cc1000
0000f3d8: 001c0260
0000f3dc: 00200264
0000f3e0: 00800000
0000f3e4: 00000000
0000f3e8: 00000010
0000f3ec: 00c00000
0000f3f0: cec10720
0000f3f4: cec1cec1
0000f3f8: cec10720
0000f3fc: cec1cec1
0000f400: cec10720
0000f404: cec1cec1
0000f408: cec10720
0000f40c: cec1cec1
0000f410: cec10720
0000f414: cec1cec1
Ring end
space: 28 wanted 32
(II) intel(0): [drm] removed 1 reserved context for kernel
(II) intel(0): [drm] unmapping 8192 bytes of SAREA 0xf8d67000 at 0xb7aca000
(II) intel(0): [drm] Closed DRM master.
Fatal server error:
lockup
(II) AIGLX: Suspending AIGLX clients for VT switch
(II) intel(0): xf86UnbindGARTMemory: unbind key 0
(II) intel(0): xf86UnbindGARTMemory: unbind key 1
(II) intel(0): xf86UnbindGARTMemory: unbind key 2
(II) intel(0): xf86UnbindGARTMemory: unbind key 3
(II) intel(0): xf86UnbindGARTMemory: unbind key 4
[end of log]
I realize this probably isn't enough to go on, but any insights would be appreciated. Next time it crashes I'll be more careful about saving the output.
It just happened again. I made copies of the logs before I restarted, but unfortunately the logs seem to reflect only the couple times that X automatically attempted to restart following the crash. I can post them if anyone thinks they might be helpful. I don't really know how to read them and thus I don't know what section to post.
I have, however, noticed an interesting correlation. I don't remember the circumstances of the first couple crashes, but recently every time it's crashed, it has been when I attempted to access this webcomic: http://chronillogical.com/ . Now it doesn't crash every time I go there, but I'm not sure it has ever crashed under different circumstances. What this means I have no idea.
I am not sure, but maybe is the flash support what is failing. A while ago, my Iceweasel crashed, but without crashing the whole X server, but it was due to some files missing for the flash plug-in to work correctly, maybe this could be related to something like that, but is only an assumption.
By the way, did you try running iceweasel from the console, maybe when it crashes it throws important messages.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.