Debian :: KERNEL PANIC When Cron/anacron Is Runnig?
Apr 6, 2010
I just turn of the services, but there is something wrong about it...How to locate the problem? Maybe its some script in /etc/cron.*? Ive tried running them "manually" but nothing special happened. Is there a log for cron-scripts (or what are they callled)?The kernel panic says something like this: "Kernel panic not syncing, fatal exception in interupt, iwl4965 - irq_tasklet".So it seems to be in the iwl4965 driver, but also strange as it is connected to ana/cron.
It hapens very unregularly sometimes just a minute after starting ana/cron, sometimes it can go longer. It wasnt always like this, first it just happened when I played Warcraft on wine and i thought that was the cause (it might not even be the same problem, but i think so), but then it happened at other times also, so I fiddeled around with the startup services and found that disabling cron and anacron (its about the same thing I figure) keeps the trouble away. Well, its not a big problem, but I just wanted to see what the problem is, Also, is the cron-script doing anything of importance
I have a system that was upgraded from Debian 7 to 8. Unfortunately it is not able to boot from the new kernel 3.16. Only the old 3.2 kernel is able to boot. I could transfer a backup, install it in Virtualbox, redo the upgrade and I can reproduce the error..The last error before "panic" is this line
Code: Select all 59.073579] Freeing unused kernel memory: 216K (ffff8800017ca000 - ffff880001800000) Loading, please wait... [  59.226154] systemd-udevd[53]: starting version 215 [  59.326564] random: systemd-udevd urandom read with 4 bits of entropy available Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... /init: .: line 210: can't open '/scripts/init-premount/ORDER' [  59.552148] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000200
I recently installed Debian squeeze on one of my older pcs. I have had this computer for a long time with windows so I know there is no hardware issue. About half an hour after being turned on in Debian the computer goes to a black screen and the num lock caps lock and scroll lock keys flash.
I am using a kernel with no initrd. I have had this kind of panic before. Usually it means that the kernel can access the hard drive because the driver for the controller or filesystem isn't built into the kernel.
The kernel is 2.6.34 vanilla.
My IDE controller is a Silicon Integrated Systems SiS 5513, and I built the driver for it into the kernel BLK_DEV_SIS5513=y
My /boot (hda1) is ext2, and everything else is ext3
EXT2_FS=y EXT3_FS=y
My grub entry (hda2 is my root partition) kernel (hd0,0)/vmlinuz root=/dev/hda2
i immigrate to Debian Squeeze. So, for each time i want to start debian i have a kernel panic and ( mouse + keyboard blocked ), I can't use anything.Here is my kern.log pastebin
I am currently having issues with system freeze when unmounting portable hard drives. This happens almost every single time. Normal USB sticks are fine and do not produce the freeze. I am using kernel 3.0.0-rc6, however the issue also persists when switching back to 2.6.39. This is the error message i get when freeze occurs, reverting to terminal output:
I am running Debian squeeze. A while ago I upgraded my kernel to 2.6.38 from backports. Just now I thought it would be good to upgrade to 2.6.39 from backports. Upgrade went fine, but after rebooting I get a kernel panics rightaway.
"No filesystem could mount root, tried:" "Kernel panics = not syncing: VFA: Unable to mount root fs on unkown-block(0,0)."
This is the first time one of Linux installations halts/panics on booting, so I don't know what to do now. I tried booting the recovery entry from the grub boot menu, but same result.
I have had a serious problem with my laptop recently. I have been having unexpected reboots and kernel panics and I don't know why. I can't tell if it is hardware or software, and what is causing it.
It has happened on multiple power bricks from different outlets and locations, my slice battery and my main 9-cell battery.
I am running Debian Testing/Stretch with Kernel 4.1 with XFCE4 on a Lenovo T420 with 16 gb of ram, a i5-2540m, USB3 Express Card, OCZ SSD, an intel 7260 ac wifi card and Ericcson F5521GW 3g card. I also have a modded bios for the wireless cards, and I have had that for over half a year without any problems.
I have no clue what the cause is from the logs.
I also booted into Windows for a bit, then it blue screened, but I don't know if it was because of a driver I had tried to put on earlier for the 3g card, because Linux was out of commission and I needed 3g. The driver didn't work, gave a code 10 or something and gave me a blue screen that said something along the lines of device driver attempting to corrupt the system has been caught. Windows also won't boot anymore.
I'm not worried about Windows though, and what I really need is Linux to work, being that this was the first time I booted up into windows in several months.
Memtest runs fine, and passes all tests.
Right when I turned on my computer after one incident, I wrote a script to check the CPU temp and write it to a file every second. Once the computer turned off, I read the file and it said the CPU was at 39 degrees. Not something to turn off over.
I cannot find any indication of a problem in /var/log/kern.log. kern.log was extracted from the computer right after it rebooted randomly. Find it here: [URL] ...
i recently buy an MSI 770-45 motherboard with 4gb (2x2gb) Gskill 1600Mhz Ram. The CPU is an athlon2 x4 620, everything tested and working fine except i can`t get lenny or squeeze 64bit linux running because of kernel panics when creating ext3/ext4 partitions during install or running fsck on the system i installed on another PC and moved to this one. The boot shows a screen related to IOMMU problem saying must enable it in bios but no option related to it and no memory remapping also. The question is how i can get IOEMMU working with 4gb of RAM (if i remove one of the two modules everything is fine). I`ve tryed ioemmu=memapper/off/noagp/soft and any thing i found on the web, moving to test debian installation was my last hope really before starting to use the 32bit one, i am planning to add more RAM which with this version is just can`t be.
Because I am using one of the new WD disks I am trying to aling my root partition with the real sectors, as described here: [url]
So I copied all files to a temp location, deleted my partition (/dev/sda3), recreated it a few cylinders later (same name) and copied the files to the newly created partition. I updated UUIDs in grub's configuration as suggested in this thread:[url]
But now it fails to boot with the following error:
Code:
I checked the filesystem on this partition and its fine. I tried to recreate the initramfs from Knoppix:
Code:
But it didn't change anything.
How can I either fix it or install a different kernel on this drive so I could boot into it and re-install my default kernels?
I have attempted to install kernel 2.6.34 and 2.6.33 kernels with this Debian howto [url] Everything worked without any errors until I went to boot into the new kernel. When I receive this kernel panic output Kernel panic - not syncing VFS: unable to mount root fs on unknown-block(0,0)
It also spits out something about being unable to access ext2 FS. I googled this symptom and have seen that it is fairly common, but everyone's error seems somewhat unrelated. I used the same kernel configuration as the one that is currently working, to keep things simple.
I have recompiled a few kernels, but all on 32bit systems so not sure if that has anything to do with it.
Running Arch Linux 64bit, most recent version.
Kernel Output:
Code:
My first thoughts was that it might be my grub bootloader configuration, so had a big play around with that but it didn't fix it. Also made sure support was built for filesystems. However almost all that Fstab mounts are ext3 anyway, and certainly the root and /boot are. Now thinking it may be a memory error so will run a check when I shutdown.
Dell laptop booting from a USB stick with a CentOS 5.5 minimum installation.
Uncompressing Linux...OK, booting the kernel. Red Hat nash version 4.2.1.13 starting sda: assuming drive cache: write through sda: assuming drive cache: write through mount: error 6 mounting ext3 mount: error 2 mounting none switchroot: mount failed: 22 umount /initrd-dev failed: 2 Kernel panic - no syncing: Attempted to kill init!
1. Does minimum installation not drop on a kernel or initrd with ext3 support? I can't imagine that's true, but have to ask.
2. The USB stick is single partition ext3. Maybe there is some limitation specifically related to USB stick booting that requires boot to be FAT16 or FAT32? Except the CentOS 5.5 installer refuses to let me install on either FAT.
3. How can I do the equivalent of lsmod on a linux installation that will not boot? i.e. I have CentOS x86_64 running in VirtualBox, I can plug the USB stick in there, so how do I get information on the USB stick's kernel and initrd if I can't boot from it?
4. Is it possible to rebuild the i386 based initrd on this USB stick, when the computer is not booted from that stick, with a system that's x86_64 based?
System Info: Dell Latitude i686 Laptop which has run CentOS 5.5 and Fedora 12,13,14 in the past, and boots from Fedora 14 Live CD transferred to a USB stick. So I know USB booting is possible on this machine, and this stick.
The process of creating the stick:
CentOS 5.5 i386 on a USB stick. Old Dell i686 laptop which has previously run CentOS 5.5 installed from DVD, and has successfully booted from this same USB stick holding transferred Fedora 12,13,14 Live CDs. CentOS 5.5 was installed onto the USB drive directly by the CentOS 5.5 DVD installer (running virtualized in VirtualBox 4.02 on Mac OS X 10.6.5.). No errors or complaints during installation.
For whatever reason, the installer did not do some things correctly. First Grub wasn't working correctly, I got that sorted out and have the Grub+CentOS splash screen, it finds vmlinuz and the initrd, and then I get a kernel panic.
Ext3 was built into the kernel and that's why I'm getting this message. I do not know how the installer would have dropped a kernel or initrd during instalation that that don't contain such a basic thing that obviously comes in linux kernel 2.6.18-89 EL.
I have the following strange thing with a RHEL4 installation. Since last week, the system did a reboot and now something is really fucked up. During boot we get the following messages (don't care about 'strange' typo's, my colleague typed it 'blind' from the screen)
Code:
The strange thing is that we never see a 'could not mount blabla' or similar messages. First we thought it was a failing kernel update by plesk, but even after manually updating the kernel with RHN RPM's, still the same message. Booting with rescue mode and then chroot the system works. After that we even can start things like plesk and so on.
We double checked things with another RHEL4 install, and at least two things were odd:
1: the working machine has /dev/dm-0 and /dev/dm-1, the broken one doesn't
2: some files on /dev didn't have group root, but 252
We tried to recreate the /dev/dm-X nodes with [vgmknodes -v], output:
Code:
A fdisk /dev/sda shows: /dev/sda2 XX XXX XXXXX Linux LVM (I removed the numbers because this line is from another machine, but rest was identical)
We have a copy of the boot partition so if one need more info please let me know.
grub.conf:
Code:
last part of init extracted from initrd-2.6.9-78.0.8.ELsmp.img:
I am running an Hp Pavillion dv6000 with the Broadcom card that never seems to work for Linux. I recently talked with my friend who said he found a way to get it work.following his instructions I opened Synaptic and checked the package bmcwl-kernel-source to be installed.I went through the process of it all and it said it had install successfully. I restarted the computer and when I tried to enter my operating system I got this error "Kernel panic - not syncing : VFS : Unable to mount root fs on unknown - block(8,1)" I have previous versions of Linux on my computer so I can still get in to those if need be but I don't know how to undo what I did or why it isn't working for that matter. Does anyone have any ideas as to why I am getting this error and how I can fix it?
I have one machine where I have several versions installed on different partitions. The base partition (/dev/hda1) is Slack 12.1. On a spare partition (/dev/hdc4) I had installed Slackware64-current. Last week I slackpkg upgraded and installed the 2.6.32.2 kernel, and now that partition will not boot. I know that with the new kernels the hd* designation has been removed, and have already redone that fstab (accessing it from a different boot) to reflect the sd*. Here is the slack64 section of my lilo.conf:
Code: # Linux bootable partition config begins image = /other/spare4/boot/vmlinuz
I boot from CD (Tried both debian-506-i386 and the Netinstall) I also tried the flags acpi=off noapic nolapic And when it starts booting the install, it appears: "Kernel panic- not syncing: attempted to kill init"
this is what i did i downloaded the latest stable kernel archive from kernel.org and extracted the archive into the download directory (i don't think that matters though) then i downloaded and installed the ncurses archive (needed for menuconfig) then i opened a terminal and navigated to the directory that was extracted from the archive and issues the floowing commands
I am trying to install debian on my windows PC but am receiving some errors with it. I have downloaded "debian-506-amd64-DVD-1.iso" from debian website and am seeing that the md5 sum is correct. I am getting following error when I choose Graphical Install or install.
[ 1.480788] crc error [ 1.569788] kernel panic -not syncing:VFS: Unable to mount root fs on unknown block(253, 52)
Description of my PC: I have 2 hard disks
1. IDE hard disk (80 GB) -> windows is on this drive 2. SATA hard disk(250GB) -> I intend to install debian on this drive. 3. MSI motherboard & AMD 64 processor with 1 GB RAM. 4. NVidia external graphics card based on AGP slot(256 MB)
EDIT:: This time I got one more error message prior to the 2 shown above [some number] PCI:Cannot allocate resource region 0 of device 0000:00:00.0
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 have a CR-48 running Ubuntu 11.04. I've had some continual issues with it, along with other Linux distros I tried. There are times my laptop freezes completely during mid use. If I power off and back on, 70% of the time it doesn't detect the hard drive upon next boot. If I go into BIOS, no SSD detected. If I pull the battery, hit the power button, put battery back in, it'll run fine for a while.
I'm up in the air if it's a hard drive issue or motherboard issue. Once I got this kernel panic I sat here for a half hour on another system typing it up. I hope somebody can look at it and make sense of it and tell me what essentially is happening.
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?
Edit: The PC is broken and I'll buy a new one. Don' bother reading this thread.
I have Kubuntu 9.10 installed on my Acer 7520g laptop. It used to work fine.
But recently my laptop has often went into kernel panic, sometimes at boot, sometimes after hours of normal usage. Today it has not been able to boot properly from HD a single time.
When I boot it up in recovery mode, it kernel panics and displays this (normal mode displays just the graphical progress bar, no text):
Code: 00010c0f [ 9.620019] TSC f0ed3f8e6 [ 9.620019] PROCESSOR 2:60f82 TIME 1270650316 SOCKET 0 APIC 0 [ 9.620019] This is not a software problem!
[Code]....
I'm sure this is a pure software problem, because Ubuntu 7.10 LiveCD boots up normally and I got X, Gnome and everything working. So CPU must be working perfectly.
I read the logs in /var/log but there were no error messages.
I decided to try Kubuntu (10.4 64bit) again today, it's been a few years since I last tried it. The installation went well, but now I don't seem to be getting past Grub. I get a message that says: Kernel panic - not syncing:VFS:Unable to mount root fs on unknown block(0,0) I tried to use the recovery mode option in grub but that gave me the same message.
I am getting Kernel panic. I was getting is very frequently before, then I re-installed and it starts off fine then after a while it starts happening again.The problem is I have no idea what is causing it. The screen is completely frozen and won't respond to anything. The Alt sysreq combinations don't work, and I have to power off with the button.
I have a Toshiba Satellite laptop, dual-boot with Win7 and Ubuntu 10.10. Everything works as it should in Ubuntu, except when I resume from standby the computer goes into a "kernel panic," the screen freezes and caps lock light blinks.
I travel with my laptop and use standby all the time being a student, so I've been forced to use Windows 7 because it's far more reliable (isn't that funny >_<) when I resume from standby..
After literally searching for DAYS, no solutions have worked for me, and apparently this is a pretty big issue. I would love to get Ubuntu running full-time on my laptop. Also, my display drivers aren't officially supported by Ubuntu, but I'm not sure if that has anything to do with it.
