Slackware :: X Server Crashes Within 15 Minutes Of Booting?
Mar 1, 2011
Less than 2 days ago i upgraded from slackware 13.0 to 13.1.Since then, I have not been able to use my laptop for more than 15-20 minutes, 'coz the KDE screen freezes all of a sudden without any crash report and in some time the screen goes blank with just a mouse pointer to be seen (Black Screen of Death?)I can do a CTRL-ALT-F* to switch to a console a continue, or reboot (using console) to get the X server started again. (CTRL-ALT-Backspace does not work either).
i am working with an old system that uses a BIOS meant for embedded systems. According to my coworkers this thing boot some version of debian about two years ago. currently I have used there old image and a new one I made of the latest Debian stable build. both images fail to get passed grub.
to be clear the BIOS simply replies "loading grub" takes ten minutes and then crashes.
has anyone ever had trouble with grub crashing systems? this problem seems odd since is did boot with this two years ago and i still have that image.
I've installed Slackware64 on a Toshiba Qosmio laptop (booting with ext4, SAMSUNG HM500JI HDD, 3 GB Ram, Intel Core 2 Duo Processor, Intel chipset and graphics).The system boots the huge kernel just fine. But after booting with the generic kernel AND after having prepared a mkinitrd with the mkinitrd generator, the boot process crashes at ~4sec with a panic.
X crashes exactly 10 minutes after log on, and I am returned to log in screen. I am running: Kernel Linux 2.6.30.10-105.2.23.fc11.i586. Gnome 2.26.3. on a Dell Laptop.
10.04 Ubuntu / Gnome My system has just started crashing back to the Gnome login screen. Tried removing recently installed packages, as well as the repair broken packages from login screen.
I'm running Slackware64-current. Since the upgrade of last Monday I'm experiencing several crashes of the X-server. It begins with an issue that one Window, e.g. Konsole or Firefox don't become active when clicking them. After some seconds the screen becomes dark and I end up on the console. First error I saw was from akonadi. Deinstalling akonadi didn't change anything. But there is an errormessage about a segmentation-fault in the Xorg.0.log. I'll append the logfile to this post. My graphics-card is an ATI HD5470 and have fglrx installed, downloaded from ATI. My kernel is
Code: Linux samsung 2.6.35.10 #3 SMP Thu Jan 6 20:03:53 CST 2011 x86_64 AMD Athlon(tm) II Dual-Core M320 AuthenticAMD GNU/Linux
i'm having a problem with lmms. unlike some posts in the forum, my lmms does output sound, but after a few minutes it crashes. the program itself will just happily go on, but any sound crashes. i hear a glitch, en thereafter no more sound. the only way to fix it is restarting lmms, which is quite a pain in the *** if you have to do that every 5 minutes . the problem occurs to me every time i use lmms, so it is consistent. it seems to me that it crashes faster when i have a bar that includes somekind of chord; a single tone it can handle, but when there's bi- tri- or multiple tones, it just crashes nearly instantly. i've tried both alsa and pulseaudio, and both have the same problems. and it's not my overall sound that's crashing: rhytmbox and videos will just continue to play sound .
After I updated several software including Xorg server using "slackpkg update", I Ignorantly deleted configuration files without backing them up making Xorg server crashes.I try to build Xorg.conf using xorgsetup command but it crashes and spews:
Code: Fatal server error: Caught signal 11. Server aborting /usr/bin/xorgsetup: line 170: 3315 Aborted /usr/X11R6/bin/X -configure
I have a Radeon 4850 Graphic Card with ATI Catalyst as its driver, so I try to reinstall the driver hoping that it will fix the problem, which is a bad logic I admit it, and It fails to uninstall (for some reason the uninstall script is gone) and reinstall (problem with file extraction).
With Fedora 11, I got NetworkManager, and it never worked right.. Right now, the nm-applet crashes regularly, no message nothing, just disappears from the panel. I wrote a two-liner to run it in an infinite loop. But my wifi also disconnects every 10 minutes. It's like clockwork, it just disconnects. I see things about "error 38" in the logs. I tried downgrading, upgrading, nothing helped.
I am having this problem with F 10. First I get the infamous message: Could not detect stabilization, waiting 10 seconds. at the beginning of the booting process. then after I initiate startx, I use gnome, all works fine and only for few minutes and the system freezes. At first the mouse freezes, then after 30 seconds or so, the mouse's cursor can move but clicks are ineffective, not even Ctrl+Alt+Backspace, or Ctrl+Alt+Del. I have to do hard reset.
Server with Centos 5.6 stop boot up for about 90 minutes. He stop: SELinux: Disabled at runtime. SELinux: Unregistering netfilter hooks audit(1307803697.466:2): selinux=0 auid=4294967295 ses=4294967295
Have homebrewed machine, was running Fedora 8. Installed Fedora 10.Firestarter firewall manager keeps crashing after about 5 minutes. Restarts, runs for a while, then crashes.Thought it might be an IPTABLES turf war with the native Fedora 10 gui firewall manager, so disabled that at System > Admin > Firewall. Also disabled SElinux. Still have problems.Firestarter firewall seems to work OK, just the gui Firestarter monitor/manager.If anyone has ideas as to cause, I'll take a clue.I could use Firestarter to generate the IPTABLES by ..manually editing the /etc/firestarter/inbound|outbound/allow-.. files and then../etc/init.d/firestarter restartBut I find the events log useful to look at. Anyone know where the events log file is kept in the file system?
my laptop(dell xps m1330) takes around 2'30" to boot, I don't remember when it started but it wasn't always that slow. even looking at bootcharts I cant seem to figure out what that could be
I've been having this glitch since Maverick. I hoped installing Narwhal would solve it (clearly not), I like Ubuntu, but this makes the OS frustrating and pretty much unusable, forcing me to stick with Windows.
The glitch appears randomly but mostly within 5-10 minutes after booting.
Another thing : when you want to screenshot the glitch, it usually gives you a perfect image, with everything OK. I have no idea why it worked now. I have a Packard Bell Dot M Netbook.
my fedora 10 booting stops at starting udev for 5-6 minutes.when i pressed 'i' for interactive , i see ata3(i think its my DVD-R/W) responding too slow. so, booting stops there till it responds.o/p of
What is the best method for debugging the booting process? Is there a cheatcode (tried debug and failsafe). Slackware 13.1 with standard linux kernel 2.6.35.8. I having a problem with a dell server 2860 booting my build. It is hanging on
[Code]....
Booting my previous kernel 2.6.27.27(different disk with different initrd.gz) it loads the same as above but continues with
Code: loading iSCSI transport class v2.0-870 iscsi registered transport tcp I'm stumped it the problem is with the ata_piix module or the iSCSI transport module or some firmware I might be missing. I booted other pcs without issue.
I have a small Slackware gatway/web server/mail server. Few days ago I upgraded it to 13.1 and from this morning I have the following problem:
After restart the server works for 15 minutes (htop showed max uptime of 15 minutes 15seconds) and than it hangs (or at least the ssh/web/imap connections are lost)
I have checked all logs but there is no problem!
Neither in syslog, nor in messages. The inittab is set to runstate 3 ...
I have actually done a bit of searching on this, but the suggested solutions either don't work or are not applicable to my setup.First, I changed the setterm link in /etc/rc.d/rc.M to be setterm -blank 0 -powersave off -powerdown 0and have xset s off in my fluxbox startup file.Nevertheless, the screen goes blank after 10 minutes. I can't figure out what is causing it and how to stop it.
I have recently installed openSUSE 11.2 on a dell d620. When ever I boot to the default, X seems to freeze and linux crashes. I cannot even hit Ctrl+Alt+F1 to get to the terminal shell.
When it happens, the windows in the bottom turn to a yellow tint color. The windows also become unreadable. The mouse seems to move. I can click the windows, but they are slow to respond and don't seem to correct themselves. When I press Ctrl+Alt+F1 is when the sytem becomes unresponsive and I have to power it off by holding the power button.
When I boot to Failsafe, this problem doesn't seem to occur. Is there a problem booting to Failsafe? What do I lose by doing this?
nVidia Quadro NVS 110M/GeForce Go 7300 Gfxcard and installed the x11-video-nvidiaG02 and nvidia-gfxG02-kmp-desktop packages for my 2.6.31.5-0.1-desktop kernel.
I've installed Fedora 12 64bit, but the computer crashes while booting, basically after the irqbalance or rpcbind steps.
Here are photos of the error messages:
Here are my hardware specs: MB: Biostar TF560 A2+ CPU: AMD Athlon 64 X2 Dual Core 5000+ RAM: DDR2 800 Dual 128 bit, 2T (4GB) GPU: ATI Radeon HD 3870
The sound and network cards are integrated but I've tried disabling them from BIOS and the problem persists.
Note that I've tried Ubuntu (32bit and 64bit) and it also crashes about 30 seconds after loading the graphical interface (either installer or login screen). Fedora's graphical installer worked flawlessly, tho. I've also tried SLAX (using it right now) and it works without any problems.
I have installed mythbuntu 10.04. It worked well for a few days. Now my frontend does not start or crashes just after booting. You can see the frontend background for a few seconds but the menu does not load. After that, the mythtv window disappears and you can see the ubuntu desktop. Here are the last few lines from the log file:
2010-06-07 07:32:49.622 MythContext: Connecting to backend server: 127.0.0.1:6543 (try 1 of 1) 2010-06-07 07:32:49.623 Using protocol version 56 mount: can't find /dev/sdb in /etc/fstab or /etc/mtab
Slackware 13.1, on a Dell... Opliplex GX260... running XFCE4, as root. Stuff runs fine. However, the monitor goes to powersave mode after 10 minutes of inactivity. I've turned off power management in the kernel, in the app., have checked the xorg.conf, checked everywhere I can think of, can't find where this is being set. how I can turn this off?
I'm fairly new to Linux so I'm going to need a step-by-step guide to get me out of this rut. The install of Linux was fine but when I booted up I got this error. VFS: Cannot open root device "302" or unknown-block (3,2) append a correct "root=" boot option;here are the available partitions;
0800 78150744 sda driver:sd 0801 47428608 sda1 <-- this is my Windows partition 0802 30719552 sda2 <-- this is my Linux partition 0b00 1048575 sr0 driver:sr 0b01 1048575 sr1 driver:sr
Kernel panic - not syncing:VFS:Unable to mount root fs on unknown-block (3,2) I guessed from reading this error Lilo isn't pointing to the right partition to boot from? How will I fix this? I read another thread about boot problems on these forums and a guy said to do this:
#mkdir /slacktemp #mount /dev/device /slacktemp #chroot /slacktemp #cd /slacktemp/etc <-- for me it told me that doesn't exist #vi lilo.conf <-- couldn't do nothing and was frozen #lilo -v -t -b /dev/device #lilo -v -b /dev/device
The above solution did not work for me. Can anyone shed a light on a Linux rookie?
I'm using mencoder to capture audio from a Encore ENLTV-FM3 video capture device. I have recently noticed that, since one week ago, when the machine was forcibly restarted due to a power outage, all recordings are slightly pitched, they play back slower than they should.
I narrowed down the problem to the following command line:
$ time mencoder -really-quiet -tv driver=v4l2:device=/dev/video1:chanlist=us-cable:audiorate=32000:alsa:adevice=hw.1:input=0:amode=1:normid=11 -endpos 00:10:00 -ovc copy -oac pcm -of rawaudio -o test-32000.wav tv://69 real 9m54.886s user 0m5.536s sys 0m1.740s $ ls -l test-32000.wav -rw-r--r--@ 1 martin martin 76800000 Mar 15 17:20 test-32000.wav
Somehow, mencode managed to gather precisely 10 minutes worth of raw audio in 9m 55s. That's not physically possible, unless the capture device's A/D converters are "overclocked". I can't think of any other explanation besides hardware failure. Can that be? Could it be that something got burnt during the power outage and now the capture device's internal clock went nuts?
Since the machine's restart, I've also noticed dmesg is flooded with entries like this:
CE: hpet increased min_delta_ns to XXX nsec
Which seem to indicate that the computer's high precision event timer is somehow out of sync. Does this have to do with the audio issue? Can it be that the audio converter's sample rate is linked to the HPET? I'm totally lost here. Has anyone bumped into something similar?
I bought a new laptop HP Pavillion dv3-4170ee that has Core i5 2.53ghz dual core with hyper threading, intel hd graphics and Ati Radeon HD 5470 512 mb dedicated. It came with windows 7 64bit. It also has 6 gb ram(2gb in first slot + 4 gb in the second one).I installed slackware 13.37 64 bit. It installed just fine. installed lilo onto mbr. When it boots up it shows the slackware screen. I am able to boot into windows just fine. When I select Linux it boots into linux bios data check successful. lots of stuff goes on the screen the normal linux boot stuff. and then it goes to the next screen and stays blank
Nothing happens and even the hard disk light is not blinking.By the way the HDD is Western Digital.
I just installed Slackware 13.37 on an old IBM Netvista and when I try to start KDE it gets through most of the splash screen and then crashes with the following error messages: Segmentation fault at address 0x4
Fatal server error: Caught signal 11 (Segmentation fault). Server aborting
[code]...
lspci shows I have an Nvidia chip: NV6 Vanta/Vanta LT rev 15 Other GUIs, such as Fluxbox, do not crash, so I think the problem may be with KDE, but I am at a loss. Has anyone seen or solved such a problem? I have not posted /var/log/Xorg.0.log because the KDE error message above seems more detailed.
I had been using Amaya on Slackware 13.1 32bit with no problems. I then upgraded to 64 bit, basically because of one program. Now, I cannot run Amaya. It crashes X. In my efforts to solve this I cannot find an X log with entries related to the crash. The console after the crash only shows the last lines of the output. I cannot scroll back to view the source of the errors. Is there a way to redirect error output from an X crash to a file for later analysis?
I just made a current iso and installed current and when I tried to start X the screen was washed out in a rainbow kaleidoscope pattern. I exited out and ran xorgset and Xorg -configure. Both of these hardlocked my system.
BTW Im using a geforce 8800GT. i tried installed the nvidia driver but it still locks when I run xorgsetup.
I have to go to work, so I will post the logs when I get home
