Red Hat / Fedora :: Server Rebooting No Kernel Panic Halt?
May 14, 2010
We have a server running CentOS 5 Linux 2.6.18-128.1.16.el5xen #1 SMP Tue Jun 30 06:39:23 EDT 2009 x86_64 x86_64 x86_64 GNU Linux. We've seen at random times that the server will just reboot and nothing is logged in messages. I tried to enable kdump but was only able to get a 5.4 gig dump since our /var directory is set to 10GB. Here is the messages I see before and after the server restart. I had thought that when a kernel panics, it is supposed to halt the system and not reboot it. My /proc/sys/kernel/panic is set to 0. I can run an update but want to have some sort of idea what is causing the issue and if the update will fix anything.
May 13 20:05:22 hlotmt01 xinetd: EXIT: bpcd status=0 pid=1071 duration=1(sec)
May 13 20:05:22 hlotmt01 xinetd: START: bpcd pid=1072 from=10.203.1.1
May 13 20:05:23 hlotmt01 xinetd: EXIT: bpcd status=0 pid=1072 duration=1(sec)
I have a Centos 4.8 linuxbox running in VMWare ESXi 4 and the kernel is 2.6.9-89.0.11.ELsmp. Recently, this linuxbox is quite unstable, it has kernel panic once a week... But we didn't have any configuration changes on it. And I have attached the kernel panic console screen and lsmod for the server.[URL]...
I'm having a strange problem on some of our Debian servers. It all started about three weeks ago when we moved our virtual environment (VMWare ESX3) from a SAN to a NAS (NetApp). At first I thought it had to do with that move but since the other 9 servers are working perfectly I eliminated that idea. For over a year all 12 Debian 5 servers have been working great without mentionable failures. All servers are (where) up to date with the latest patches. About three weeks ago I started having kernel panics with the following message on three of our servers:
Code: Code: Bad EIP value EIP  0x0 SS:ESP 0068:f6d7da18
Kernel panic - not syncing: Fatal exception in interrupt and other times it looks like just a dump of hexadecimal data. The only difference between those 3 servers is that they have several mounted shares connecting to the NAS using CIFS. So I was thinking that it might have to do with an update of some kind in regards to smb. I recovered an image from a month ago, before the troubles began, copied over the data and MySQL databases and configured the 'old environment with recent data' exactly the same with MySQL master-master replication, document synchronization and load balancing. This task I performed last night (no other way since it's a production environment). Up to this time neither of the two 'restored' servers had a kernel panic. The one that has not been restored is having one at random about every hour and a half. Following are the different versions between the 'at this time' working server(s) and the failing one:
Recently i've been playing with few variations of linux distros since my Windows XP got infected with something that makes anything flash-player related crash or restart computer even(im saying this because it might be related), reinstall didn't help fix it so i decided to better switch back to Linux world and tried some newest distros. Everything was nice untill..recently some distros after installation gave me kernel-panic or caps lock+scroll lock lights blinking..trouble is Fedora 14 just gave me same stuff after i went maybe 5mins away from keyboard with web browser open then came back to notice..if at first i thought it was wrongly made distribution now i'm bit scared that my PC is dying..i did basic search in google and people say it may be related to hardware beeing too old or drivers but when i use it then i don't encounter this - just when afk. I have almost none experience in Fedora so was just wondering if someone could point me to right direction
The Fedora 11 Live CD was tested on a Dell and it is good. On the HP Pavilion a705w, with an Intel Celeron 2.93HHz w 760MB RAM, the install fails with kernel panic. The cd was burned on the HP.
A colleague suggested that the HP may not be compatible with the kernel. Are there startup settings that I might try to diagnose the panic issue? Perhaps there is a verbose boot up process that pauses so one can take notes?
After installing the latest updates (dont know which ones) yesterday, I get a kernel panic (LED lights flashing at the keyboard and black screen) when starting X (the login manager). I am running on 64 bit with the proprietary ATI catalyst driver. How can I start in text only mode?
I've decided to switch one of my workstations from debian to fedora and I have some issues that I would like to discuss. I've installed the fedora 12 from a live cd and everything worked fine but when I use yum to install software the caps lock key blinds and my old acer 1.5 celeron laptop freezes. Using lmsensors I've noticed that the cpu temp is miniumun 60 degrees and the cpu fan is always on. I've used google and found some ways others tried to resolve this but none worked. I thing it's a kernel bug so I want to know how to collect all the data.
I've been using Linux for a few years, but this is my first time using Fedora. I installed it on an old computer last night and rebooted, and everything seemed good. I let it start to install updates, but after they were about half done I stopped it, turned the computer off, and went to bed. I know that was stupid of me, and I'm afraid it screwed something up because now when I boot I get the error "kernel panic-not syncing VFS:unable to mount root fs on unknown-block(0,0)".
When I looked up the error on Google it seems a lot of people get this after installing a kernel incorrectly, so could stopping the update in the middle perhaps screwed with my kernel? Could I simply chroot into the installation from the live CD and run 'yum install kernel26'?
What happened to my Fedora 14 KDE system! After messing up my desktop by moving all the option buttons at down of desktop (like the clock, start options button, network signal...), I tried to restore it finding the option that restores the bars, colors, and view mode. I clicked this button restore and a panic happened to the laptop. After that my laptop just restarted and when the system open again, gets to ask the initial password, it seems to open up and start over! And do not want to open only hint rebooting! Gave Blackout! What happened?
I have a client who has for the last four years been running a Red Hat 4.1.18 Server with absolutely zero problems. Yesterday somebody had a problem with one of the attached Windows PC's and some genius decided to reboot the server. By genius I mean idiot and by reboot I mean pull turn off the power to the box.
When they tried to reboot, they get a kernel panic. This is what the screen says; Uncompressing Linux... Ok, booting the kernel. audit(1009912323.849:0): initialized Red Hat nash version 4.1.18 starting File descriptor 3 left open Reading all physical volumes. This may take a while... /dev/hda: open failed: No medium found No volume groups found File descriptor 3 left open /dev/hda: open failed: No medium found No volume groups found File descriptor 3 left open /dev/hda: open failed: No medium found No volume groups found mount: error 6 mounting ext3 mount: error 2 mounting none switchroot: mount failed: 22 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempted to kill init!
The server runs the database for their entire POS system so they are now dead in the water. I'm stuck, I've never come across this before. What do I do to recover this?
I'm running Fedora 10 on a HP Compaq 6710b laptop. It is by far the best OS I have ever used and have no complaints, but I seem to be having some trouble with the wireless at work. The office has a single Cisco Aironet 1131 configured for WPA2 using AES with a PSK. The SSID is not broadcast. The mode is B/G mixed. My wireless card is a built-in Intel PRO 3945ABG, the driver is IWL3945 (auto configured during the OS install).
I use the Network Manager to manually add my SSID and select "WPA & WPA2 Personal" on the security tab and enter the PSK in the password field. After a few moments the wireless connects and appears to be working fine. About every 3-5 minutes while using the office network I get the "kernel error" dialog in the bottom right hand corner of my screen and the wireless drops connection. It re connects after about 30 seconds and appears to work fine until the next kernel error.
I have a system here that tends to have kernel panics during an linux installation, though I was able to perform a vista installation on the same hardware. Now I would like to ask what your suggestion for the cause of that problem is. Here a screenshot: [URL]
I suspect the hd to cause it: -it is now over 7 years old -smartctl displays over 16k read error and 0.5mio seek errors (or are such high numbers normalfor that old disks?) -the panic contains the string bad_area in the trace
But it might also be a RAM error, since the trace contains sth about page_fault and vista installs on the very same hdd and does not report any error messages (concerning the hardware, and I heard win doesn't complain about a bad RAM).
Fedora 13 on Asus P5Q Premium, E7500 hangs after 10mins to 2 hour. After some trial and error, I found that the problem could be related to yum although it could be that it is only by running yum that I've been able to trace the problem. On runlevel 3 (to make sure it's not an X server problem), system hangs and prints the following message on the screen (copied it by hand, still have to figure out where to find it after system restart):
BUG: unable to handle kernel NULL pointer dereference at 00...0695 Ooops: 0000  SMP last sysfs file /sys/devices/virtual/block/md127/md/raid-disks CPU 0
I have a hw RAID setup but the problem is the same, only the numbers are a bit different.
It is not a hw-related problem either because both the latest Suse and Kubuntu install without problems (although both seem to have problems in starting with RAID installed, normal disk is OK). Of course, I only have myself to blame because Asus says that this mb is compatible with FC8 - I haven't been able to test because my machine seems to have problems in booting from install DVD - but I suspect it is because that was the time this mb was launched and they haven't tried it on more recent Fedora distros.
Interestingly enough, the same problem comes with F12 and F11, didn't have energy to go further back. I've been using RedHat since ver 5.2. and would hate to give up following the path now. Fedora just stands out from the crowd so much that I can tolerate some inconveniences. This is just a bit too much.
I have to image a sparsely populated 20GB NTFS partition onto an ext4 volume. While doing dd if=/dev/sdb2 bs=10M | gzip F14 64bit falls into kernel panic screen. What other method of taking per-sector image of a HDD is possible?
I am having a problem with lockups on a new FC12 box (dual core 3 ghz, 4 gb memory,nvidia 8400gs). This happens reliably when replaying MythTV videos, but also randomly at other times using other apps (I suspect also boot but I can't be sure; it just occasionally stalls part way through the boot display).
Usually but not always this is accompanied by a kernel panic (caps lock + scroll lock lights flash on keyboard).
I did a core dump with kdump and it reports: Thread 1 (<main task>): Cannot access memory at address 0xffff880028025b70I am in the process of running memtest86+ right now. It's been through several passes without errors. I'm going to let it run some more, but if that is dependable it's looking like the RAM sticks are not the problem.
I untared a few libs on the wrong server (that's the when you're supposed to start laughing!) and I corrupted my server. Everytime it boots up, I get the following error:
/sbin/init: relocation error: /lib/tls/libc.so.6: symbol _dl_out_of_memory, version GLIBC_PRIVATE not defined in file ld-linux.so.2 with link time reference. Kernel panic - not syncing. Attempted to kill init!
I can I restore the original libs? I'm running RHEL 2.6.9-42 on a Proliant DL585.
I was finally able to install Fedora 11 x64 after choosing to only install packages from the repository on the install DVD. Prior to that when I had chosen tio install from the default online repositories, the install itself failed with a Python exception ( see my other post ). Now, however, once I boot after the install I eventually receive a kernel panic message, and failure. The exact same thing happened with CentOS 5.3 x64 after a flawless install. So unless someone knows what might be going on I will assume that Fedore, Red hat, and offshoots for x64 bit systems are just not for me. I have been able to successfully install the latest Mandriva and SUSE x64 Linux distros so whatever Red Hat/Fedora has done just does not work on my system.
It appears that I have really messed up my machine. I was trying to get matlab working on FC 11 and I ran into libc.so.6 issues, so I put an older file libc.2.3.1.so in /lib/tls/ directory and created a symbolic link libc.so.6 to see if the application would work. Unfortunately at the same time the system did some updates and the system hung, so I ended up rebooting, but now it gets stuck at boot screen (after grub) with a kernel panic - not syncing: attempted to kill init.I just need a way to get to the directror /lib/tls and delete the link and the older .so file I threw in there. How do I get this accomplished. I cannot get even to a shell from the boot screen.
I ran into a strange issue after doing a preupgrade from Fedora 10 to Fedora 12: Preupgrade worked as described, I upgraded successfully to Fedora 12 and also worked 2 days without any (major) issue. Then I had some issues with firefox (malloc errors, couldn't start) so I thought I'll do it the "Windows Way" namely reboot, and then no chance to boot fedora. I was hit by a kernel panic saying "init not tainted 188.8.131.52-166.fc12.i686". I was able to boot in rescue mode using the preupgrade installer (still in the grub menu) but even chroot /mnt/sysimage gave me a "Segmentation fault".
I am not able to re-upgrade the system since the installer tells me (on vty3) "product Fedora version 12 found on VolGroup00-LogVol00 is not upgradeable". I also tried to reinstall the installed kernel as well as upstart (hint from [URL]) from the preupgrade repositories (using rpm --root /mnt/sysimage --force ...) but the kernel install failed with %post and %posttrans errors (signal 11). I also did fsck.ext3 for the lvm partition with no success. Does anyone have some additional hints how to recover? It's a 32 bit install on an Intel p4 with 2GB RAM.
I am having a problem with lockups on a new FC12 box (dual core 3 ghz, 4 gb memory,HDPVR,nvidia 8400gs). This happens reliably when replaying MythTV videos, but also randomly at other times using other apps (I suspect also boot but I can't be sure; it just occasionally stalls part way through the boot display).
Usually but not always this is accompanied by a kernel panic (caps lock + scroll lock lights flash on keyboard).
I did a core dump with kdump and it reports:
Thread 1 (<main task>): Cannot access memory at address 0xffff880028025b70
I am in the process of running memtest86+ right now, and it's been through several passes without errors. I know it needs to run more, but given the reliability of this problem with MythTV video playback I am wondering if the problem could be in the video card memory.
Does anyone know of a linux (or bootable) tester for video memory? All I am able to find are some things for windoze like this.
Also is there any way to track that address from the core dump back to a physical location?
I am trying to install Fedora on my computer but I am getting a kernel panic at liveCD boot after boot menu. It occurs to me for F13 and F14 (all x64, F14 x86 seems to boot fine but I'm trying to host a x64 guest OS on it so I need to get the x64 version to work)
My system specs: Dual Opteron 265 4GB RAM Asus K8N-DL (nVidia nForce Pro 2000, BIOS 1010)
I also tried to install F14 in some other computer (which worked flawlessly) and put the HDD into the computer in question, which gave me the same kernel panic.
I am trying to install linux kernel manually, for this I had compiled linux-2.6.36 with minimum drivers and features. Note that ext2, ext3, jffs file system support and sd ata_piix drivers are set as inbuilt kernel modules.
I had two hard disk for my Intel x86 box sda and sdb. I have running linux on sdb from which I can access sda. sda has one partition sda1 as ext3 fs.
I had created following directories at sda1 root, bin, boot, etc, sbin
After compiling kernel, I had copied bzImage, system map files to boot folder. then using 'grub-install' I had installed grub on sda. after installation I edited grub.conf to setup kernel image.
After this I booted sda by changing HDD boot priorities,And wow I got grub prompt -- linux kernel booted but as soon as it tries to mount file system it dies with error,
I accept that I dont have binaries for init and no initialization stuff in /etc, but I think problem is I am not able to give correct rootfs to kernel.
I just installed Fedora 12. When I boot, only the following three lines are printed: pnp 00:09: can't evaluate _CRS: 12298 ACPI: Expecting a [Reference] package element, found type 0 Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) I first installed Fedora using a RAID 1 setup that mirrored each partition, so I thought the problem was coming from GRUB and confusion from what to boot off of. However, I reinstalled Fedora using a simple single drive setup (left the second drive without any partition), and the same error was returned. Is this an ACPI issue with this particular motherboard/BIOS? Any ideas for how I can fix this?