Does anyone have any idea what this is? I'm running F14 kernel 11-83, everything else is rock solid but I get this crash randomly, sometimes it runs for days no problem other times it crashes within a few hours.Someone recommended I run memtest86, I did for 24 hours and it showed no problems.
View 6 Replies
[Note: I'm typing this entire thing out. It probably isn't 100% verbatim. And I am using an older version of the kernel because 2.6.30.9.96 was not behaving either.]
Code:
BUG: unable to handle kernel paging request at efd86f5c
*pde = 00000000
[code]....
I am trying to install CentOS 5.3 on a computer where I successfully installed Windows XP.
Booting from the DVD I got the following error:
[<c0458f3c>] serial8250_init+0x6d/0xe4
[<c041abd4>] init+0x25/0x69
[<c041f46b>] ret_from_fork+0x1eb/0x73c
[<c04597eb>] init+0x181/0x19b
[Code]....
I've been trying to install Opensuse 11.3 from the Kde live cd, but the installation hangs when I'm almost done. Right at the beginning the installation is interrupted right with text that among other things says:
Bug: unable to handle kernel paging request at ffffc90010b8000. After a while though, the installation picks up and continues by itself. I'm then able to complete the necessary steps and I reboot the system so that it can complete the installation.
After reboot there is a new text message that says that the bios does not support EEC memory or something to that effect and then continues with the installation. When it has completed 82% of the autoconfiguration the installation just stops and stays that way.
I've had no problem installing previous releases, from 10.2 up to 11.2, on the same machine.
I've checked md5 sum and also checked the media before proceeding with the installation.
Upon reboot after the first installation step, I also tried the failsafe mode but got the same result.
Here's the text from the serial console before I rebooted:
BUG: unable to handle kernel paging request at ffff8140320234b8
IP: [<ffffffff802b0a13>] dentry_iput+0x26/0x9d
PGD 8063 PUD 0
[code]....
My root server is using CentOS release 5.2 (Final), kernel 2.6.26.5-rootserver-20080917a, SMP, 64-bit This Oops happened yesterday and before that it happened on March 14th of this year, and before that on January 31st of this year, so a repeating pattern. On the January 31st Oops, I just rebooted. On the March 14th Oops, I reformatted the two swap partitions as follows: mkswap -c /dev/sda2; mkswap -c /dev/sdb2 On this last Oops, I turned off the swap for 24-hours, then decided to turn it on again after doing the above mkswap again. During the previous uptime, I had dumpcap packet capture running, but this last reboot, I'm not going to run it.
all of the following are made through live usb creator. when i tried with F11 i686 live kde, I got the following error: Bug: unable to handle kernel when i tried with F11 x86_64 live kde then at the time of installation my screen got blurred.
View 4 Replies View RelatedI am trying to install F12 on a Dell Latitude E5400 laptop. It got through the whole install process, but when it rebooted i just get a screen that says
"unable to handle kernel null pointer dereference"
and it just hangs there.
since upgrading to Fedora 11 I keep getting this error:
Code:
BUG: unable to handle kernel NULL pointer dereference at 0000000000000041
IP: [<ffffffffa01fab94>] sync_request+0x1/0x8de [raid456]
PGD 49435067 PUD 494f6067 PMD 0
Oops: 0002 [#1] SMP
last sysfs file: /sys/devices/virtual/block/md0/md/sync_speed
CPU 0
Modules linked in: ip6table_filter ip6_tables ip6t_REJECT nf_conntrack_ipv6
[Code]...
A FC10 server hung and had to be power-cycled. I suspect it hung because of an nfs mount timeout.
Now it does not boot. The error is libc.so.6 not found. Kernel panic. Attempting to kill init.
Booting under rescue:
ls: cannot access libc-2.8.so: Stale NFS file handle
Is there a way to reboot to a clean state? There must be some NFS cache file.
I also tried to cp rescueCD:/lib64/libc-2.8.so to the old lib64 dir, but get the same "Stale NFS file handle" message.
I'm wondering if there is any application being able to handle compressed SWF files. If I try it with mencoder (mplayer), it tells me:[swf @ 0x91a0a30]Compressed SWF format not supported No way in Fedora Core 11?
View 3 Replies View RelatedI use web server apache use php fastcgi (Centos 5.2, apache 2.2.9 , php 5.2.5 and fcgi-2.2.4 ). I receive error : "The server encountered an internal error or misconfiguration and was unable to complete your request. contact the server administrator, no-reply@zz.vn and inform them of the time the error occurred, and anything you might have done that may have caused the error. I view log :
[code]...
I use a pretty fresh installed RHEL 5.4, which should be very similar to Fedora. After the basic installation I installed xen and xen-kernel via yum with no errors. I can select the xen-kernel at boot time. But after booting the normal kernel shows up.
[root@noname boot]# uname -r
2.6.18-164.11.1.el5
My /boot/grub/menu.lst looks like:
default=1
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
[code]....
I can't see anything wrong and I did not change/try anything.
I need to understand southbridge related code in linux source code.
For that I have downloaded Linux source code version:2.6.28 .
I have seen the code but didn't find code specific to southbridge handling.
Is Linux source code contains southbridge specific code?If so where can I find the code?
how to redirect all client http request to https request in squid
View 1 Replies View Relatedi've installed nagios just from a while and after i installed centreon, since this when i try to log in the web interface of nagios it shows up this message: Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request. contact the server administrator, webmaster@localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log. Apache/2.2.17 (Ubuntu) Server at localhost Port 80
For the past several days the Package Updater has popped up wanting me to install an update to iceweasel. Each time I try to do the iceweasel-31.8.0esr-1-deb8u1 (64-bit) I get the following error message:
E: Internal Error, ordering was unable to handle the media swap
Is there something I need to do?
I was wondering what exactly is protected mode, segmentation and paging? Do you know of any good explanations?
View 14 Replies View RelatedI'm having problems to install SCST in Fedora 11.I'm not able to apply the kernel patch because there isn't a file called drivers/scsi/scsi_lib.c in the /usr/src/kernels/2.6.29.4-167.fc11.i868.PAE.Does anybody have an idea on how to proceed?
View 3 Replies View RelatedAfter running update last night from 2.6.35.9-64 to 2.6.35.10-68 my laptop fails to start. Boot process goes most of the way to startup and then hangs just before login screen. Not sure what else to give as far as info.
View 12 Replies View RelatedMy VMWare Player was working fine After updating the kernel it is throwing the error "Unable to build kernel module" my kernel is 2.6.40-4.fc15.x86_64 what to do?
View 2 Replies View Relatedi was trying to install kernel 2.6.29.1 on fedora 14 but it is giving error. First download a package with kernel and i saved in home/user/linux. Afterwards i can extract this package.
1.tar -xvzf linux-2.6.29.1 -C /usr/src
2.cd /usr/src/linux-2.6.29.1/
3.make menuconfig
4.make
5.make modules_install
6.make install
after above steps i got this error.
ERROR: modinfo: could not find module ip6t_REJECT
ERROR: modinfo: could not find module nf_conntrack_ipv6
ERROR: modinfo: could not find module ip6table_filter
ERROR: modinfo: could not find module ip6_tables
ERROR: modinfo: could not find module ipv6
ERROR: modinfo: could not find module fuse
however it gives initramfs,vmlinuz-2.6.29.1 and System.map-2.6.29.1 in /boot folder and menu.lst in /boot/grub is updating according to new kernel. when i reboot my machine and selects the kernel 2.6.29.1 it shows FATAL:kernel too old [1.591633] Kernel panic-not syncing:Attempted to kill init
im trying to install the driver for my nvidia GeForce 7300 GS.i have Fedora 12 installed in an Intel duo core 2 processor 64 bits.kernel installed is 2.6.31.5-127.fc12.x86_64...i followed leigh's guide i did the 4 steps but after reboot screen goes blanck and X dont work.the log says:
-> Kernel module load error: insmod inserting './usr/src/nv/nvidia.ko'
-1 no such device
How can I use DKMS to force the virtualbox setup to run using the correct kernel sources? This is the error I'm getting in the vbox logs
Code:
Attempting to install using DKMS
removing old DKMS module vboxdrv version 3.1.2
Deleting module version: 3.1.2
completely from the DKMS tree.
Done.
Creating symlink /var/lib/dkms/vboxdrv/3.1.2/source ->
/usr/src/vboxdrv-3.1.2
DKMS: add Completed.
Error! Your kernel source for kernel 2.6.31.6-166.fc12.x86_64 cannot be found at
/lib/modules/2.6.31.6-166.fc12.x86_64/build or /lib/modules/2.6.31.6-166.fc12.x86_64/source.
You can use the --kernelsourcedir option to tell DKMS where it's located.
Failed to install using DKMS, attempting to install without:
Makefile:152: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop.
Code:
[root@nevada Downloads]# uname -r
2.6.31.6-166.fc12.x86_64
I am trying to install Fedora12 on a usb hard-drive, the first problem I encountered was that the hard-drive would not boot stating "kernel panic: unable to create root device", this is just using the standard fedora 12 install and mostly clicking next (although I add my vista to the grub and tell grub to install to /dev/sdc which is the location of my usb hdd).
I have also tried livecdtousb (wont boot in stick and wont recognize removable hd as removable)
I have tried setting up disc encryption and installing with no LVM.
The drive has this same problem with ubuntu 9.10 however ubuntu 8.10 installs perfectly and I am guessing earlier versions of fedora will too. The problem is that I would like the kernel features of Fedora 12 (mainly modesetting) without this issue.
I have played about with grub and quite like disabling LVM and using the uuid of the drive to select the root partition, my boot partition has 500mb, I have a 2gb swap space 50gb ext4 root partition & 27gb fat32 partition code...
I am unable to boot my Fedora 14 after last nights kernel update. When I start the boot up and hit F2 the system fails after outputting the line : Starting vservers of type 'default'. At some point the console displays an error message :
serial8250 : Too much work for irq17
How do I restore my previous version? I know some people have suggested in the past - just modify the grub.conf but how? When I boot off the cd I only get access to the liveuser disk. I need to have access to my own /boot/grub/grub.conf file.
host: CentOS 5.4
guest: FC12
Virtual Machine: Virtual Box 3.1.4
I can not for the work get Virtual Box's Additions to install in my FC12 guest. The error log (/var/log/vboxadd-install.log) shows: Makefile:23: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again.. Stop.
I have tried:
# KERN_DIR=/usr/src/kernels
# KERN_DIR=/usr/src/kernels/2.6.31.12-174.2.22.fc12.i686
# KERN_DIR=/usr/src/kernels/2.6.31.12-174.2.22.fc12.i686/kernel
[Code]...
I have a fresh installation of Fedora14_x64 and after that I have updated the OS also.
Then I have installed VMware-Player-3.1.2-301548.x86_64.
All the installation procedure has completed successfully without any error.
But when I am going to run VMWare It is throwing some error.
I am attaching all the needed screenshot and log file also.
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.
grub.conf
Code:
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,
Code:
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.
When I start gparted, to see if I can add extra harddisk where all my data is, I get the next error:
Code:
[root# gparted
libparted : 1.9.0
The kernel was unable to re-read the partition table on /dev/sda (Device or resource busy). This means Linux won't know anything about the modifications you made until you reboot. You should reboot your computer before doing anything with /dev/sda. I can start fedora 12 x64 amd whitout any problem. My partition layout on a single disk (80 gb sata maxtor) for the system is:
Code:
/
/home
swap
When I try to mount one of the extra disks (samsung spinpoint 1 tb, I have 4) I get to next error:
Code:
root# mount /dev/sdb1 /media/sdb1
mount: you must specify the filesystem type
If I add the option with the filesystem I get:
Code:
root# mount -t ext3 /dev/sdb1 /media/sdb1
mount: special device /dev/sdb1 does not exist
In gparted, when I select just a flag option, and deselect, press ok, the disk is forced to be reread by the program. After that I can also mount it. When I use any of the programs linked in this post, I am able to mount the disks whitout any problem. Except after a reboot, I get the same problem. SO whit each reboot, or poweroff, I need to do a re-read of the disks. The system is fedora 12 x64 for amd, installed from a live cd, the rest whit yums groupinstall, the latest kernel.
I am using DEBIAN 6.0 and I wannna update my kernel from 2.6.32 to 2.6.38. Every time, I do it but after the installation & rebooting into the new kernel it gives me error "UNABLE TO BOOT INTO THE KERNEL".
View 1 Replies View Related
