Red Hat / Fedora :: FC12 Freeze - Lockup - Kernel Panic ?
Jan 31, 2010
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 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 had FC10 working nicely but decided to move to FC12 to be able to use the latest and greatest... Turning out to be nightmare!
My HDD is partitioned into three:
(hd0, 0) 100MB : used to be original /boot for FC 10 (hd0, 1) 120GB : /home (hd0, 2) 30GB : / > First thing tried: preupgrade
Using this preupgrade setup happend and asked to reboot. However, upton reboot got locked in stage2. So this option was abondoned.
> Second thing tried: installation CDs
Using this method formatted (hd0,2) and installed FC12 on (hd0,2). However, did not change anything on (hd0,0). This still held all the upgrade information from the previous trial. Now, when I rebooted after the install there was a kernel panic with error "kernel panic not syncing vfs". Thinking it might due to the (hd0,0) partition and errors in my install, I abandoned this.
> Third thing tried: installation CDs
Using this method I formatted both (hd0,0) and (hd0,2). The install was similar to above but now (hd0,0) was also formatted and after install was empty. But upton reboot I still got the "kernel panic not syncing vfs" message. I dug through google and saw references to problems in grub.conf and lo behold there were problems with my grub.conf. I don't see the initrd line at all nor do I see the initrd*.img file in my disk. The grub.conf is:
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. 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, 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. Any linux (or bootable) tester for video memory? All I am able to find are some things for windoze such as this. Also is there any way to track that address from the core dump back to a physical location?
I just installed a fresh copy of Fedora Core 12 on a system. I have a 1 GB swap partition, a 20 GB root partition and a 50 GB /video partition (for a mythtv system I am building).
Installation went fine, but upon the initial boot, I get:
Kernel panic - not syncing: vfs: unable to mount root fs on unknown block (0,0)
I can boot off the FC12 cd and go to the rescue option and get to a shell, but not sure where to go from
I've been running F@H on my system for a while now, these specs:
ASUS Rampage Formula Q9450 @ 3.6Ghz 4GB DDR2 8800GT 512MB Fedora 12
Running various different nvidia drivers, with working 3D, and running the latest nvidia drivers with cuda for GPU2 folding + SMP folding.
I decided to add a 9800GT to the machine for more folding PPD, and I've run into some issues.
Firstly there were problems starting X, it would hang as it started or even before it started, so I switched to RPMFusion's repo drivers which have the VGA_ARB patch applied. This now gets me into X and working 2D.
The problem I have is, although the system is completely stable running folding on all four cores, SMP, 24/7, as soon as I start anything involving 3D (such as glxgears) it will run for 3 seconds then hardlock the machine. I mean seriously lock it, no switching to terminals, and an ssh session into it from another PC dies.
Its the same with any other driver that will boot into X with the VGA_ARB patch (talking nvidia binary here).
Both cards work perfectly individually, AND both cards work, including full 3D in Windows 7 when together, which would tend to rule out a hardware fault.
I've just installed OpenSuse 11.3 on my two Sony Vaio VPCF11Z1E machines (which have a Geforce GT 330M graphics card).Both machines appear to setup correctly and behave normally, but at seemingly random intervals (of the order of magnitude of 15-30 minutes) the whole system locks up for no readily apparent reason. I can still move the mouse pointer around the screen, but I cannot click on anything, and the whole keyboard is unresponsive (including any reasonable ctrl-alt-xxx which might normally help). The only way to get out of this seems to be to press and hold the power button to shut the whole machine off (which is not ideal!)
Running updated 11.04 on a older Dell Precision 360n. Been having random system freezes for the past month that requires a hard restart (REISUB doesn't work) each time. Sometimes the caps lock and scroll lock LEDs blink, other times not. sometimes it happens during boot, other times during normal usage. There hasn't been anything in any of the logs (except once, which I'll post below). This happened running 10.04 and 10.10 as well. I've run PC-check a few times and all hardware diagnostics have passed. Until today, i've been able to boot and run Trinity Rescue Kit 3.4 to mount the disk and examine the logs (and do backups), but now TRK won't boot and spews kernel panics when loading.
my problem is on installing nvidia driver on fc12 32bit but, first of all, as i understood the pae kernel requires more than 4gb of ram,i have a 2.2 ghz cpu with 2 gb ram,but when i run command:uname -r it answers: 2.6.31.5-127.PAE [i have fc12 32 bit] when we try to download linux we have a 32bit edition or 64bit edition,do we have an edition which is only for pae? or when we install for example the 32bit edition on a computer with more than 4gb of ram then the kernel automatically will change to be a pae kernel??
Basically when I add more than a single 2gb RAM module, my computer starts randomly crashing every half hour or so, the screen freezes with no response. I have tested the RAM with memtest 86+, it only happens when there is more than one module. The system is openSuse 11.2 64bit and it had a single 2gb RAM module when I first installed it, and removing all but this seemingly fixes the issue. The following is the error message I get when the system crashes, It seems to continue messaging after the initial visual lockup.
I don't know what the problem is, but from searching the web it could be a number of problems, the memory is not being allocated correctly or it maybe there's some conflict no between my ATI HD card/driver (latest driver from ATI repo).
Not wanting to speculate why, in the repositories, Fedora doesn't *also* provide a on-KVM enabled kernel counterpart to the default KVM enabled kernel that *is* supplied, I must say I'm frustrated that they haven't done this simple thing.
Considering that everyone who upgrades to KVM enabled FC12 from a previous non-KVM release of Fedora (like FC10) ... considering that these people will be guaranteed to no longer be able to run VirtualBox or VMWare Workstation after upgrading, is a disappointing oversight by / or intent of Fedora (one that manifests in *lost productivity*).
And try though you may to install the kernel source RPM and compile it after running "make xconfig" to disable KVM support, you usually can't! Fedora kernel compile attempts often die very early in the "make" process, indicating something like ...
"Kernel compile error: No rule to make target `missing-syscalls'
or some other silliness. And when you successfully compile a "kernel.org" kernel, and try to boot it, you get all kinds of missing library errors (etc).
Given that it would be simple to provide both a KVM enabled kernel (as they do), and also a non-KVM enabled kernel (which they don't) so the rest of us can seamlessly continue to run VirtualBox and/or VMWare Workstation after an upgrade - and avoid getting entangled with deciding whether use KVM or XEN for guest O/S's... it's a frustrating misstep to not have done this basic thing (i.e. include a non-KVM kernel). It was a rude awakening when we tried to launch VirtualBox only to have it fail after the upgrade.
Anyway, has anyone successfully compiled their own kernel for FC12 and not get errors after boot? If so, which sources did you use; and what kernel version? In the meantime I'll try out other kernels and compile options.
I just upgraded to Fedora 12 x86_64 via yum upgrade. However I have problems with booting. The new FC12 kernel won't boot. Boot output is something like
Code: ERROR: sil: RAID type 253 not supported ERROR: adding /dev/sda to RAID set "sil_ajabaccaaidg ERROR: sil: RAID type 253 not supported ERROR: adding /dev/sdb to RAID set "sil_ajabaccaaihe No root device found Boot has failed
I resized boot partition to 400MB, formatted it as ext4 and recopied all files, modified fstab to update boot partition's UUID. Tried to set a boot flag on boot, still, I can only boot with the old kernel from Fedora 11. Is it a Fedora 12 kernel's bug or something wrong with my setup? I don't use any RAID, and the sil error is present with Fedora 11 kernel also.
Having just updated various files including the kernel using Package Manager I no longer seem to have the correct version of the Nvidia graphics driver. On previous updates this has been done automatically by the "kmod Nvidia" Metapackage. My last kernel was 2.6.32.19-163 fc12.i686.PAE and the Nvidia driver for that did get downloaded correctly. Looking on Yumex I cannot see a driver for this latest kernel listed.
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
I'm experiencing random lockups. There are 2 types.1st time this happened when I enabled Kwin compositing effects. The screen turned black and it froze, the mouse pointer froze. Nothing would move. 5 Minutes later I just hard reset the Laptop. I was afraid something could be corrupted as it was shutdown in a bad way. On boot up Kwin's compositing effects were in place.Randomly working on the laptop, everything will freeze except the mouse pointer. This happens like once in a while though.I have a feeling this has something to do with my Dell Studio 1555 Intel GM4500 MHD graphics.
I have some programs, that will only install on i586 architecture (opposed to x86_64). My CPU is 64-bit architecture. Can I install FC12/11 with i586 kernel on the hardware? How? Any disadvantages except the fact that I'm supposedly not able to use the 64-bit feature of the CPU?
I have an issue with kernel-2.6.31.9-174.fc12.x86_64. I ran the updates on Christmas Eve and it updated from kernel-2.6.31.6-166.fc12.x86_64 to kernel-2.6.31.9-174.fc12.x86_64. When I rebooted, I no longer received the Fedora Bubble boot screen. It comes up with the Fedora boot bar (across the bottom). Also, I receive failures during boot with the following:
Forgive me if I have posted this in the wrong forum, first time poster with Fedora. I have been using Linux for some time now, mostly Mint, but Fedora 12 @ work. Anyway, I receive the following error in my /var/log/boot.log:
Code: nvidia.ko for kernel 2.6.32.9-70.fc12.i686 was not found and the driver does not load (My xorg.conf file is not loaded), but once I am at a
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'd like to have a shot at building FBReader 12.1 from source for use within F12 (kernel 2.6.31.9-174.fc12.i686.PAE) but am having problems locating the following .rpm files:
libz and libbz2 -- libraries for zip and bzip2 (de)compression libfribidi -- for bidirectional text support lincurl, version >= 7.17 -- for network libraries integration
I had fedora 12 installed on a Macbook pro Intel first generation with ATI Radeon graphics card (see the attachment). Compiz crash when trying to watch *.wmv movie codified with wmvvc1dmo on kernel-PAE-2.6.32.9-67.fc12.i686. I want to convert the film to *.mpg, then I download the mplayer codecs in order to see the film, I can do it without problems with the on kernel-PAE-2.6.31.12-174.2.22.fc12.i686. But I updated my system last Saturday and when I was trying to see the movie again the computer began to respond really slow, then I began to close applications and when I tried to restart I got the message: "compiz is not responding".
I tried again but the same problem. Other thing that I noticed is that when the computer go to sleep, when I wake up it, the display show horizontal black spikes, it is like it doesn't have the appropriate refreshing rate. I think that the problem is related with the acceleration on graphic card. Yesterday, I booted on kernel-PAE-2.6.31.12-174.2.22.fc12.i686, and I watched the film, and the wake up was without problems. That is the reason I call it a regression.
kernel-2.6.32.10-90.fc12 seems to break 802.11n with my intel 4965 chip on my thinkpad t61p. Anyone else seeing the same thing? iwconfig shows extremely low bit rate. dmesg doesn't show anything at all unusual.
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'?
I get kernel panic when i try to use the f14 kernel but with the last kernel of f13 i have no probelm, and the sources are form f13 where can I find the repos for f14
