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 2.6.31.6-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 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
I have built a CentOS 5.6 kernel with the Preemption Model changed from Voluntary to Preemptible Kernel. Everything works fine except for gdb. When attempting to debug a binary using start or run there is a segmentation fault. If I attach to a running process everything works fine. I expect that I need to make an additional change to the kernel config file, but don't know what it might be. I'm using menuconfig to make the changes: Processor type and features --->Preemption Model ---> [x] Preemptible Kernel (Low-Latency Desktop).
gdb /bin/true (gdb) run Starting program: /bin/true During startup program terminated with signal SIGSEGV, Segmentation Fault.
When I install GNU Common Lisp, and run (help), it suggest that as a next step I run (HELP 'CONS). This halts with a segmentation fault.<br>When I attempt to install the CVS version, the installer compains and bails, also with a segmentation fault.<br>If the fault in my hardware, or is it a program bug that should be reported to someone? If hardware, how do I force a full fsck on /dev/sda when I boot up?<br>Instinct tells me the problem is in gcl (GNU Common Lisp, stable or CVS either one), because I'm not seeing problems otherwise.<br>
My computer sporadically gets segmentation faults multiple times daily, but when I try to upgrade, it consistently faults on the download. I've runCode:sudo rm /var/cache/apt/*.binbut it still faults. I'm at a loss with this, is there something else I can do to solve the segmentation faulting
my KDE is making segmentation fault. KDE is not required to restart but this segmentation fault is making every time (after 2 min) when i login to kde/fedora. this is making me annoying.. my linux info is following:
Synaptic does not run. When I start it from Menu/system/administration/synaptic package manager , it asks for root password, then crashes. Nor does aptitude from the root terminal.localhost:/home/user# aptitude
Since upgrading to 10.04 Thunderbird doesn't work properly. It is Thunderbird 3.04. It works for locally-created users but exits with 'segmentation fault' when the user is from LDAP. In the latter case, the home directory is local, created by pam_mkhomedir. I get the same problem with a newly-installed 10.04 system.
I cannot understand why it worked fine in 9.10 but not in 10.04. I set "set -x" in the thunderbird script and here is the trace from that:
I would like to know if there is a way to repair a fedora 13 installation without using yum or using smart .Both applications are exiting with a "segmenttation fault".This happend after an general update and the installation of a couple of applications when the installer exited with an error message that indicated that there was not enough diskspace left.The message was wrong because there was plenty of space left and all of the applications were installed, just important programs used for changing the systems started crashing.Here is a small list of prgs that are crashing: yum , smart, system-config-firewall, system-config-printer, abrt-gui and I guess I might find easily more.Strange rpm seems to work.
I've just upgraded my fileserver to Fedora 10, but it crashed half-way through a 'yum update' of the newly installed system.
It is telling me to run yum-complete-transaction to finish off the previous update, but all it does is throw a "Segmentation Fault" now. Even 'yum update' does the same thing.
yum -v update doesn't reveal much, other than it is "Building updates object" when it crashes. yum clean all doesn't help, nor does rebuilding the rpm database.
A few days ago I bought a Raspberry PI B with Debian Wheezy (7.0 - I think) on it. Before installing a media centre on it I wanted to do some basic configuration/upgrade and decided to upgrade to Debian Jessie. I followed the instructions provided on [URL] .....
Before moving to Jessie I have upgraded the original Wheezy; after the upgrade the version was 7.8. Everything went well till I executed "apt-get dist-upgrade". Errors where generated. As suggested I tried the "apt-get -f install"; but it did not go smoothly either. However, so far, I am accessing the desktop and everything seems fine (although I did not do anything fancy yet). The version recorded is 8.0. Thus, should I worry about the error messages generated?
Please find the log file here: [URL] ......
Note that I put the log file on Google Drive because each time I clicked on "add file" in the "Upload Attachment" tab when editing this message I got:
Internal Server Error: The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, forum-admin@forums.debian.net 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.
Fedora 13-64. While booting the nvidia driver has a segmentation fault:
Code: Enabling the nvidia driver: /etc/rc.d/init.d/functions: line 530: 1406 Segmentation fault "$@"[FAILED] It is not a problem when using the notebook's led/mouse/keyboard. The problem is when I'm using an external monitor/mouse/keyboard. In this case I must first boot using the notebook until it gets to the login screen when I can start using the external configuration. That is annoying because the notebook seats under the table and must be put over the table to boot. The notebook model is HP DV6 2173 CL with a discrete GeForce G105M
My other notebook running Ubuntu works exactly as needed. The whole boot process is shown and controlled by the external monitor/mouse/keyboard.
Every time I boot up FC13 I get a boot message which is showing a failed task. The line is as follows: Enabling the nvidia driver: /etc/rc.d/init.d/functions: line 530: 1174 Segmentation fault "$@"[FAILED] Everything appears to be running fine on my system. This message is more nuisance that a functionality message. But I could be wrong.
Due certain torrent sites I'm visiting I was forced to upgrade to rtorrent 0.7.9, which isn't avaiable through F8 repositories so I had to compile it myself. It went fairly smooth and I've been using it now for couple of months with no problems whatsoever.
However, recently, it started crashing on me, at the start, throwing out following message:
Caught Segmentation fault, dumping stack: Stack dump not enabled. Aborted
I have no clue what this is. I can assure you that I haven't altered anything on my system after I compiled the client.
Eventually, I am able to start the program, after an x-amount of tries.
I even tried to delete my session directory once. It seems to have helped at one occasion, but several days later, I was in the same trouble.
Going from Fedora 12 to 13. Got to the point where I have to reboot to install, system reboots to 12. This is a triple boot system with Open Suse and Mint, and the grub2 bootloader from Mint is the bootloader for the whole shebang. In the "how to use preupgrade" instructions there's a line that says "dentify the drive and partition of your Fedora /boot folder." How? If that sounds odd, consider that in my set up "computer" shows 4 partitions (and with just three operating systems..?). I can mount them, but have a problem telling which sytem is Fedora, Suse or Mint. And getting the FEDORA bootloader to find the PREUPGRADE kernel ... Momma said there'd be days like this.
cat /etc/fstab just returned /dev/sda1 on /boot. I installed Fedora first, before Suse or Mint, so being on the first drive or partition sounds right, but the multiple drives throws me, and "just guessing" doesn't seem like the way to go.
Application that crashed: kded4 Version of the application: $Id: kded.cpp 1031638 2009-10-05 16:59:11Z lunakl $ KDE Version: 4.3.4 (KDE 4.3.4) Qt Version: 4.5.3 Operating System: Linux 2.6.31.9-174.fc12.i686 i686
I am using RHEL 6. When i use CAP3 software for the first time it successfully resulted. But second time when i used, it's showing "segmentation fault (core dumped)". Even after restarting and reinstalling it showing same error. When i google, i found it some memmory related problem. But no clear information.
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?
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 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).
I am trying to install Fedora 11 from the full DVD iso on a system using an Intel D945GNT motherboard with a dual-core 3.2GHz Pentium D installed. The installation hangs quite quickly and produces the error "Kernel panic - not syncing"... The previous line is something along the lines of "EIP: [something] intel_i915_configure() [something else]". I have tried many different kernel boot options, such as acpi=off, nolapic, nommconf, and the like, but to no avail. It seems as though this has something to do with a memory mapping conflict due to the allocation of video memory for the on-board graphics chip, but I'm not at all certain about that.
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 was able to copy the iso file and tried the installation however I stubbled upon the same problem I had when I tried installing Fedora 11. The message I received was "(1) (0.048001) MP-BIOS bug:8254 timer not connected to IO-APIC (2) (0.064001) Kernel panic-not syncing:IO-APIC + timer doesn't work Book with apic debug and send a report. Then try booting with the 'no apic-option'.
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 study computational systems engineering.. and in my school (itlp) we've got fedora 12 installed in some of the computers.. and we use it to learn network administration and security. the reason of this message.. is that i want to install fedora 12 in my notebook (dv4-1525la vu068la).. but an error keeps poping up.. the error is the next one..
DMAR: No ATSR found DRDH: handling fault status reg f0003d63 Kernel panic - not syncing: DMAR hardware is malfunctioning
and though i have looked in bugzilla.. there is no help for me there.. they say.. "press tab in the welcome bootscreen when you are about to select whether to install or restore an existing system and write intel_iommu=off and press enter" but that does not really helps.. it just does the same.. in some blogs they say "upgrade your bios".. but i say.. then why i can not install the olders distributions with my "old" bios.
Maverick 10.10 is unable to create Japanese locales on my wife's laptop (Acer Aspire 3000). This machine previously had no such problem. The install is a fresh install, since the machine froze during the upgrade (no fault of Ubuntu's). A possible complication is that it froze several times more during the install, and I have gone through many recovery boots and iterations of dpkg configure. All relevant packages are installed, I believe. Everything else works. Through System, Administration, Language Support, I have installed all components of English and Japanese. Currently English is selected. Japanese should appear in the list but does not. Japanese text appears properly, and I can write in Japanese,But all the menus are in English. Fine by me, but my wife will want Japanese when she uses the computer again (not soon).This mostly likely is a glibc/libc6 problem, as far as I can tell. I can't find any other Ubuntu user with this problem recently.And now, some outputs:1. dpkg-reconfigure locales
