Fedora :: Kernel Update - Computer Will Hang During Startup And Shutdown Unless Move Mouse Around
May 11, 2011
I just updated to kernel 2.6.35.13-91.fc14.x86_64, and I'm now having a weird issue where my computer will hang during startup and shutdown unless I move the mouse around.
While moving the mouse, it will boot up or shut down normally. Once i stop moving the mouse around it will hang (until I begin to move the mouse again).Once fully booted it acts fine..
I seem unable to get an nvidia driver working properly after upgrading to the latest kernel with Fedora 11.Here is my laptop and its specs: http://h10025.www1.hp.com/ewfrf/wc/d...reg_R1002_USEN[URL]I've tried both the kmod and akmod unsuccessfully. Everytime it gives me a black screen on boot, I can fix the problem by popping in the LiveCD, and changing the xorg.conf file back to the backup.Here are the errors/warnings from my boot.log file:
Code: WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/. Checking for module nvidia.ko: [60G[[0;31mFAILED[0;39m]
just ran the obligatory kernel update for Karmic 9.10 and now my computer doesn't shut down when prompted to do so. It tries...goes through the logoff, makes all the motions and then hangs at the very end.
Reinstalled Ubuntu...same thing after kernel update.
Problem is when srv01 has problems and is taken offline from the network, all the pc01-pc20 computers freeze, you can move the mouse but the menus don't work, you can go restart or shutdown either. only solution at this time is to turn it off or restart through the button on the pc case.
After updating to kernel-2.6.33.6-147.fc13.x86_64 (and updating all kmods) VirtualBox guests no longer boot.
I had a Windows guest (from now on refereed as Crapdows) that worked normally. After the update, I could get to the "Start Windows Normally" screen, but then Crapdows refused to boot. At first, I thought it was a crappy M$ bug, but after creating another VM (Doublecrap), and starting from scratch, I was able to get to the "Windows is loading files" screen, and then the guest hangs again. This problem is generalized to all OS'es I've tried. In Ubuntu, I can get to the language selection screen before the installation freezes. The same applies for Fedora and SUSE guests.
Everything worked fine in Kubuntu 10.04 (64-bit). On the upgrade to 10.10 (64-bit) it takes about a minute until I can move the mouse after startup and the integrated memory card reader doesn't work (but the green LED which used to only come on when there was a card in there is now always on). This has been discussed twice before: here (closed and solved by unplugging cardreader which I do not want to do) and here (unsolved but closed as maverick no longer in beta) dmesg (note the errer -110) follows. Let me know if I can/should include any other logs/info!
Code: [ 13.575002] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro [ 13.790470] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [ 13.903728] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null) [ 16.280020] usb 1-5: device descriptor read/64, error -110 [ 17.375755] sky2 0000:02:00.0: eth0: enabling interface [ 17.376174] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 17.377028] type=1400 audit(1290608578.996:5): apparmor="STATUS" operation="profile_load" [Code]......
1) Any process (including boot, shutdown, download, open programs, etc) is freeze (don't have any progress) until I move the mouse or hit any button, so for install and use my ubuntu I have to keep moving my mouse and as you imagine is VERY TIRED.2) I get some general freeze on random times, neither the mouse, keyboard or process move, I notice that if I unplug power it unfreze, and I can work for some time.This 2 problems annoy me a lot, and I suspect is a problem related to my Netbook Model, I read about someone that has the same problem but no solution there.
This is what I did:I Try Ubuntu loading from my USB memory (1GB), run very good but with the 2 problems, but I thought it can be resolved installing.I installed along side with W7, couldn't boot Ubuntu, so I configured GRUB2 and it could enter now, but if I don't press **** after selecting Ubuntu it give me the BusyBox, and then the same 2 problems.I get rid of my W7 and did a Full Install on my 160GB HDD, hoping it can work fine, but no.I install all updates and no effect on that.
What is the best way to begin troubleshooting startup problems after kernel update to 2.6.31.12-174.22.fc12.x86-64? Since updating, I am experiencing frequent system hangs at startup.
How do I make a server wait on shutdown for a set amount of time?I tried making a service that just does Code: sleep 7m and made it first priority on shutdown but it seems to ignore itI'm pretty sure it runs... I'm currently testing that to make sure
when my pc boots and shuts down my monitor goes into 'input out of range' mode for a bit between the gui and the text only phases of boot/shutdown.is there a way to fix this? or where to start troubleshooting?also, when it shuts down it hangs after coming back to the text only part
Recently I installed vncserver (tigervnc) on my desktop. Ever since my computer refuses to shutdown normally. At shutdown the following message pops up: Quote: System policy prevents stopping the system when other users are logged in Then I have to enter the root password to shutdown. If I stop vncserver before, the computer shuts down normally.
Linux distro: Mandriva One 2010.0-KDE kernel(after update):-> 2.6.31.12-desktop586-1mnb Pentium 4 3.4GHz
Used to boot to kenrel 2.6.31.6 for the past 2 months updating my system whenever i was asked to-NO PROBLEMS so far(till yesterday in fact)Mandriva yesterday, offered a list of system updates including the kernel 2.6.31.12 and the respective Nvidia drivers.Boot to that kernel computer reacted as usual and everything seemed to run properly. HOWEVER,when i tried to shutdown the system everything powered off(hdd-keyboard) except the CPU(and the power supplier).I restart(manually) the system boot in and try to reboot it-NO Problem-logout NO Problem but FAILED TO SHUTDOWN PROPERLY AGAIN.
A while ago, I was applying the new kernel updates (I guess 2.6.32-24, or the one after it.. well, the latest generic update) and accidentally powered off my laptop. And now it wont come up. It comes to the logon page, and neither the keyboard, nor the mouse work. Cant even switch to the TTYs. When I boot with the recovery mode, I just see a black screen (probably the TTYs dont work) but after "processing" some time, nothing happens. Not sure if the keyboard works, as I cannot turn on/off the capslock switch, but ctrl+alt+del works
I have a fresh installation from the demo ISO image of F14 running on an Acer TravelMate 4200. The system is a Dual Boot with win Vista. Windows Vista runs without any problems but when using F14 a kernal crash constantly occurs and it then hard freezes or hangs and the machine needs to be cold booted. There is nothing in particular that I am doing either, the problem happens when the machine is idol or when I am working in various apps.
The F14 system is completely up to date running kernel version 2.6.35.13-91.fc14.i686. The following error below is from the automatic bug reporting tool and I have reported this using the tool:
Package: kernel Latest Crash:Sat 04 Jun 2011 14:55:00 Command: not_applicable Reason: BUG: unable to handle kernel NULL pointer dereference at 000000f8 Comment: None Bug Reports:
I used to have FC11 installed with the nvidia supplied binary driver. Worked fine, very stable. Trying FC12 and FC13 live CDs caused a hang, so I stuck with FC11. FC14 live CD did boot so I backed up my own files and did a clean FC14 install. Upgraded to get kernel 2.6.35.6-48, installed the nvidia driver from RPMFusion (260.19.21) and had a working system! Now, after a cold boot, the kernel always hangs during boot. Tried a number of kernel boot option (apci=off, noapic and a few others too). The hang is not always at the same place. The earliest it has hung is after:Disabling lock debugging due to kernel taint
Sometimes its a few lines later at:NVRM: loading NVIDIA UNIX x86_64 Kernel Module 260.19.12 ...(which would seem to imply that the hang can even occur a step or two before the actual driver is loaded!)
Sometimes it keeps going for a few more seconds and randomly hangs during some other driver load.
Without a specific nvidia driver the system always boots ok, so I'm pretty sure its the nvidia driver but I just can't seem to get a handle on this in a reproducible way. Sometimes, when I have make some other change, it will boot and work ok, but a reboot locks it up again (for example, in case it was SELinux, I disabled it and on the next reboot it booted and worked ok. Then, next boot, it wasn't working again). When I make changes, I reboot using the previous kernel, make the changes and reboot, with an occasional success. Once I start rebooting using the latest kernel, it always hangs.
I'd love to get a solution to this, but even some advice on debugging this would be appreciated!
I'm using 8600GT, 256Mb, PCIe card in a MA69VM motherboard with 3Gb of RAM.
I tried this kernel released on Dec 21th. It makes my F14 constantly suddenly freeze in GUI with no keyboard/mouse response anymore before restart. Only thing to do in this situation is press power-off button and after restart I found no hint in logs.My laptop is thinkpad t400 and I think it's a very common installation.Now I revert to older kernel 2.6.35.9-64.fc14.i686 and it's works quite well.
I installed F11 x86 from the DVD onto one of my machines using a total of 4 partitions:
1. /boot 2. / 3. /home 4. swap
I then created an image of the first 3 partitions with fsarchiver and restored it onto a second machine (with different hardware). Grub was loaded onto the second machine as well without a problem. The new cloned install will get past grub fine but the kernel hangs. After removing 'rhgb quiet' from the boot options, I can see that the last message outputted to the console is something about the PS/2 mouse - this doesn't make sense as the mouse is working perfectly fine.
Additionally, I can still reboot using ctrl-alt-delete so the kernel/CPU must still be responsive. I have tried troubleshooting the various pieces of hardware, so I'm guessing it's something with the clone. All the cloned filesystems appear to be fully intact; the partition UUID's are all the same. I've even tried changing the UUID's both in grub and /etc/fstab to hardcoded /dev/sdaX , but this does not fix anything.
I just finished installing Fedora 11 on a Dell Inspiron 6000. After some tinkering, I was able to get the Broadcom 4318 wireless card to start working. After a restart, I booted into Fedora and attempted to connect to my wireless network.Five seconds later Fedora freezes. I cannot move the mouse, execute any commands (except hold the power button down), or access any log files. The only confirmation I get is that my router does receive a signal from the wireless card, shortly before dying.
THE PROBLEM : gnome 3 freeze sometimes, the PC is freeze (the mouse doesn't move when i move the mouse. I must power down my PC for re-activate it. I want to shift to gnome 2 (i think gnome3 is excellent but it don't work) but it seems to be impossible. What i can do ? Does-it exist some combinaisons (like ctl+alt+suppr on windows) for keep the control ?
I am new to opensuse, coming over from debian based systems. However I am having an issue in which my system will not power off on shutdown. Restarts just fine. i get a missing error during shutdown, but there is nothing to relate the error to on that line. Then the shutdown procedes to The System will be halted immediately then hangs. The keyboard powers off and then thats it. All fans are still running. I have searched extensively on this forum and google.
I'm running V5.3 (newly installed) on an FJ E8020 laptop. The problem I have is when shutting down (*not* rebooting). NetworkManager fails to stop and after (during?) the postfix shutdown, the system seems to hang.I cannot access via another screen or remotely. I can't find any clues in the log files.
Code: Select allshutdown -h now reboot shutdown -r now halt init 0 init 6
And all hang on the same line. This is 100% reproducible. I am not actually running a virtual machine. I don't have qemu-kvm installed. I do have separate partitions on my system. I have a /boot, /, swap, and /home partition.
From looking at other posts: [URL] .....
Solutions tend to be across the board: not unmounting properly, acpi settings in grub, using a different shutdown command.
My fstab file is:
Code: Select all# /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> # / was on /dev/sda2 during installation
[Code] ....
and the result of Code: Select allmount is
Code: Select allsysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=498135,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,relatime,size=800408k,mode=755)
I have been looking for a lightweight bandwidth monitoring app and came across bmon. It does what I need. However it has an interesting way of exiting.
when it is running and you close it down it ask you 'Really quit (y/n)' and does not shut down. I am used to just right clicking on my desktop and selecting 'leave' when it comes to shutdown time.
A few times now the laptop hangs on shutdown if bmon is open. I guess it is due to the app asking if it should shutdown. Is there a way to disable the app asking or alternatively nuke it for sure with some script on shutdown.
I could search the relevant konsole running the app and go thru the steps to shut it down but sometimes I am in a hurry and it doesn't feel like the way to go anyhow?
I installed a fresh copy of Slackware 13.1 (stable) on one of my media servers and I am experiencing something strange.... When I power up the machine, I see the kernel booting, no errors, until it gets to the point where it says:
And then randomly freeze there.... Well the machine is not totally frozen because the cursor still blinks. But it will never continue... Like I said, this happens on a random basis... After a reset, it might go through or simply stall at the same spot.
I remember after installing Slack 13.1, I rebooted the machine but forgot to remove the DVD from the player, so the install routine started up, and froze at the same point when it was loading the kernel for the setup programs...
My mobo is a MSI k9N platinum.
I never had this problem before.... (well I never used 13.1 before). Since I got this machine, I used slack 12.2 and slack 13-current with success.
This problem makes the machine extremely unreliable because I intent to use it as a backup and media server, so chances I will WOL the machine and use it remotely... if that happens.
I have a computer with Fedora 12 installed on it. Previous I had Fedora 8. After shutting down the Fedora 8 it also switched off the computer. With the new Fedora 12 it get stuck on telling me the system has halted. I have to switch off the computer manually. How do I get the Fedora 12 to also switch off the computer?
I downloaded the Fedora 11 KDE livecd, installed it, and after the reboot when I get to that "firstboot" screen, I can't move the mouse, the keyboard doesn't work, I have to hold down the power button to turn off the computer.
I've just installed Debian AMD64 on my main box (Intel Q6600, Ati HD4770, Asus P5K) using the DVD install. It boots, but hangs when it tries starting the graphical interface. No reports, no commandline, nothing at all - a nice black screen and completely unresponsive system.
I've just installed Debian AMD64 on my main box (Intel Q6600, Ati HD4770, Asus P5K) using the DVD install. It boots, but hangs when it tries starting the graphical interface. No reports, no commandline, nothing at all - a nice black screen and completely unresponsive system.
I have an annoying problem with a 2 nodes cluster that I don't understand.
One of my server is totally shutdown.
When I start cman after a reboot on the other server, it hangs on "Starting fencing...". The process which is actually hanging is : /sbin/fence_tool -w -t 300 -m 45 join
When I start this program manually, I get this output :
# /sbin/fence_tool -w -t 300 -m 45 join Waiting for all 2 nodes to be members Waiting for all 2 nodes to be members Waiting for all 2 nodes to be members Waiting for all 2 nodes to be members (and so on...)
What I don't understand is why the fence_tool program wait for the 2nd node to join the cluster and don't fence the other node.
I have ubuntu server installed on a pc. The motherboard died, so I switched the HD to another computer. Everything is fine except the network. I cannot access this computer from other computer (while it was possible before). I looked at the interfaces and everything seems fine. The nic itselft seems to work too.