General :: Your Debian System Suffered A Kernel Failure
Feb 10, 2010
This error message appears in the varlog
The situation is I removed the ADSL card from my desktop as I have no use for it for the moment. I am guessing that the motherboard is still trying to detect the Sangoma ADSL card. What is the best way to resolve this problem, uninstall the drivers for the ADSL card or change the settings in the system configuration files?
The system is not affected by this removal, just get prompted regularly about this error as configured in the kerneloops client.
Debian 5.0. Lately after login following warning popup;Your system had a kernel failure
There is diagnostic information availiable for this failure. Do you want to submit this infomation to the www.kerneloops.org
-> Yes
$ uname -aLinux vm0.debian50 2.6.26-2-686 #1 SMP Wed May 12 21:56:10 UTC 2010 i686 GNU/Linux
Reboot to old kernel 2.6.26-1 the said warning doesn't popup. Reboot again to kernel 2.6.26-2 and after login no kernel failure warning popup. I did it twice. IIRC I encountered this problem before.
I have a flash drive that I regularly use on my laptop. If I unplug the flash drive without first unmounting it, I get a popup notification of a kernel failure (with diagnostics sent to kerneloops.org). Then, if I attempt to shut down the system via the console, it hangs on "The system is going down for halt/reboot NOW!" and doesn't actually shut down. Using Gnome's graphical System > Shut Down feature just logs me out and sends me to the login screen; the shutdown feature from there does nothing. I have to disconnect the power cord on the laptop in order to shut it down, and I don't like doing this.
System: 32-bit Debian Squeeze stable with kernel version 2.6.32-5-686, running Gnome 2.30.2, on an Acer Aspire 5570z.
I use Keepassx to store my passwords and keep the keyfile for my password database on the flash drive in question. I mention this just in case it helps determine what's causing the failure.
The 486 kernel works just fine, and while I have only 1GB of RAM at the moment I hope to have 2GB someday and would like to take advantage of the dual core CPU, so I would like to configure grub to run the 686 kernel by default. For whatever reason, it runs the 486 right now and the 686 fails in a major way: there is no network connectivity at all. It could be plugged into my cable modem router and it shows no wired connections. The fact that one works and the other doesn't puzzles me since I haven't touched either since the install and a few rounds of upgrades.
I should mention I'm newbie but getting better; I managed to install debian on this x60, yet while preserving the factory install rescue & recovery partition and preserving the factory install MBR so that ibm-specific hardware functions (thinkvantage button, etc.) still work. This required me to use dd to copy the first 512 bytes of my debian partition to a file in the windows partition, etc., and modifying the windows bootloader. (I wish I had learned dd long ago--it rocks). I did this because if I ever resell the X60, the fact is most people use MS Windows and having that partition adds a perception of value to some potential buyers; not to mention I paid $ for it (I was young & stupid) so why should I delete it. I also backed up the recovery partition on another drive using dd over NFS in case the hd ever heads south.
Anyway, I've never been comfy with messing with the kernel. I did once recompile a module for ALSA because it had a bug in it for an old Yamaha integrated sound card on an old PIII and the newer version worked [alsa fails on this x60 too but I think I found a post on here that has a solution I will try later]. But I'm clueless as to networking modules, not to mention the correct module is installed already from Intel for this chipset. So what is there to do?
Here's a clue: the ifconfig output is radically different from the 686 and 486 kernels. Looks like hardware is not being detected since eth0 fails to show:
I would show the diff output below if it weren't so long--and not allowed--upon 2 text files, the first holding the output of modprobe -l under the 486 kernel and the second under the 686 kernel.
Lately I'm encountering a somewhat annoying malfunction: almost every boot, my desktop is stuck, HD red led is constatnly on, and i get a message from kerneloops that I had a kernel failure. I can move the cursor a little and slowly or not at all. Few violent reboots and I get a clean boot. Running Debian Lenny kernel 2.6.26-2-686 on a Pentium 4 2.0 GHz with 250 MiB ram.
I just installed the lenny (amd64) on my new core i7 870 computer (with netinst), but the kernel failure message appeared everytime I booted into gnome. I don't know how to solve this problem. Sorry I don't have much experience with installing linux, though I have been its user for a few years.
I have (had) Debian Testing running on a 250GB IDE hard drive, partitioned normally.
I also have 4x 1TB drives in a raid 5 using mdadm, and 2x 500GB drives in a raid 1 also with mdadm.
I put the two arrays in lvm using:
I then used "lvcreate" to make storage/backup 300GB, and the rest went to storage/media (approx. 2TB usable). I put an xfs filesystem on both and mounted them.
All was working fine until the system drive shorted out and died on me this morning. As far as I can tell, all my other drives and everything else is fine. I do a daily rsnapshot of the filesystem, which of course is residing on storage/backup (stupid, I know). So I have full backups of everything, but I'll have to put a new hard drive in and reinstall Debian before I can restore everything.
I've reinstalled before and simply reassembled mdadm arrays and remounted them before with no problems, but this is the first time I've used lvm, so I'm not sure what I have to do to restore everything. Is it as simple as reinstalling the system then doing a:
It all started about a week after upgrading to Jessie and I had an unusual system failure, in that the CPU went to 100% usage and the hard drive light was on constantly. The keyboard and mouse were were non-responsive. Not having REISUB enabled I did the "stupid" thing and pushed the reset button on the computer. BAD BOY! As a result the computer would not boot and I had to use a live CD to format the drive and install Wheezy (I had the CD).
After installing Wheezy, everything worked well for about 3 days and then it did the same thing. Fortunately I had REISUB enabled and was able to reboot. I looked at the syslog and found a segfault with colord-sane and, after some research that suggested colord-sane might be a problem, I set UseSane=1 in colord.conf . Things seemed to be okay for about 4 days.
Well, after all that I had another problem today with booting. During boot I got an error message saying that there was some hard drive problem and that I needed to log in and run fsck, which I did . There were I believe 4 INODE errors that I was asked if I wanted to repair, to which I responded yes. After that the system booted correctly. After booting and entering the Gnome Classic desktop I looked at the Disk Utility and checked the SMART data. There is now 1 bad sector where before there were none. The drive is a one year old WD 500GB Velociraptor.
Don't know if this is relevant, but in the days before this latest "crash" I had downloaded about 8 movies using bittorrent. Could this have overtaxed the HDD?
I guess my questions are: When fsck "repaired" the disk would it have moved any data from the bad sector to a new location? What may have caused the sector to go bad ? Should I be buying a new hard drive?
The system seems to boot okay,at this time, so I assume that no critical system files were affected. Just curious as to how I should proceed. First is BACK UP my data. Got that !
One more thing I just thought of is that every time it "crashed", I was using LXDE.
I need to know: how do not automatically restart GNU/Linux after a critical system failure(kernel panic). For some reason the pc is rebooted, actually throws the error screen Reboot just moments before, but I can't to read it before you reboot.
I'm trying to come up with a startup init script that will check to see if the system was shut down gracefully, or if it is rebooting from a poweroff or something similar?Anyone know of a way to check for this condition with the least amount of room for false positives or vice versa?My intial thought is just a startup script that will will check for a file on startup, and on a proper reboot/shutdown just touch the file. But id like to avoid that type of script if possible,
I am using Linux operating system fedora 6 .Before today everything is going well. But today internet connection gets failed. It can not connect to the server for the internet connection. But in the same computer,installed windows operating system shows the internet connection.Please try to answer my question why the Linux operating system can not connect to the internet?
An error occurred during the filesystem check. Dropping you to the shell; the system will reboot when you leave the shell. Warning -- SELinux is active Disabling security enforcement for system recovery Run 'setenforce 1' to reenable
I was having a problem with the keyring asking me for a password after I changed my user password. I googled it and found that since the password changed, I will get asked for the keyring password until I delete ~/.gnome2/keyrings/login.keyring. What happened was that I wasn't paying attention that you had to generate a new keyring password before rebooting.
Now, whenever I try to login via gdm, I get this message: error initiating conversation with authentication system - general failure
How do I get it working again? I can still login from the terminal.
I have tried many times to load Debian on a new HD without any success. I used bittorrent to download it to my windows vista laptop and preceded to burn the image to a cd using Active@isoburner. But it only gets to where it says boot failure.
AMD 64X2 3800 CPU 1.5 G RAM ASUS A8N5X MOTHERBOARD ATI RADEON HD 545O GRAPHICS HITACHI DESKSTAR SATA 500G HD
I am on Squeeze I just updated with a new kernel 32-5-686. I have installed the Nvidia driver with kernel 32-3-686. After the update I can't log with kernel 32-5-686. I tried installing another Nvidia driver but I ran into some trouble. This is the first time I am doing this. how to go by and install an Nvidia driver with the new kernel. Should I remove the old driver first? If I do this I won't be able to log into the system using the old kernel from which I am typing this message.
I got a rather big problem since an attempt to upgrade.My debian version is 8.0.I upgraded when apt proposed the change. I did that in two steps, with apt-get upgrade and then apt-get dist-upgrade, with the installation of a new kernel. I moved from 3.2.0-4-686-pae to 3.16.0-4-686-pae.Since the upgrade, I can't boot my system any longer.During the boot sequence, this message appears with a countdown (it's copied by hand) :
Code: Select all(1 of 4) a start job is running for dev-disk-byX2du
At the end of the countdown, the boot sequence starts again, and ends up on an invite to log in as root in rescue mode. I can't connect (maybe due to some azerty/qwerty issue, I got a French keyboard. I tried to type in "qwerty mode", with no success (the password is not prompted)).I can connect with the 3.2 kernel however, selecting it form the grub interface. I can't log in in rescue mode either, but with this kernel the boot sequence goes on and I can log as a regular user or as root, at the end of the boot sequence. There is no X, but the system seems to work.What could I do to make the system boot properly with the new kernel, or to go back to the 3.2 version ?
Tried to make the /etc/pam.d/gdm mod to auto-auth keyring. Now when I boot up it says "error initiating conversation with authentication system - general failure" preventing me from logging in.
So I read that I can enter recovery mode by pressing Esc on boot up to boot to a root shell. However no amount of button mashing Esc on boot up seems to have any effect, always bringing me to the graphical login. I could boot to a liveUSB but this has all started when I got to work this morning, and don't have a USB key handy, and I'd like to get this sorted so I can do some work today!
And why does the /etc/pam.d/gdm tweak seem to be causing so many issues (googling reveals the technique has a lot of other users finding the same problem as me, however they seem to be able to get to recovery mode)?
EDIT: If I hold down or mash Esc fast enough, the computer will beep at me once or twice, but nothing changes on screen
EDIT 2: Ok found out that holding SHIFT is the new way of doing things, reverted pam.d/gdm to the backup and things are back to normal!
I have just installed Fedora 11 to my laptop and it appears I am in trouble. I have received two kernel failure messages, which I post below. What are the consequences of these issues and how can I solve them ?
I just installed OpenSUSE 11.4 x64 as a fresh full-install last week. Seems to be running great, up until the last couple days when I installed AVG. Every time I do a avgscan, it runs for 20 to 60 min, and then causes the PC to reboot. The only thing I can find is the following event in the /var/log/messages:
Code: May 1 11:45:01 linuxbox sntp[7653]: Started sntp May 1 11:45:59 linuxbox kernel: [38429.349995] iTCO_wdt: Unexpected close, not stopping watchdog! May 1 11:46:00 linuxbox kernel: [38430.111688] PM: Marking nosave pages: 000000000009d000 - 0000000000100000
[Code].....
I get this result every time I try to do a virus scan. I also have seen this result once when doing a large scp transfer from another Suse box. The AVG log just terminates and gives no warnings as to what's going wrong.
Are there any other logs I can check out to try to troubleshoot this further???
I'm running the 64 bit version of Ubuntu 9.10 on an AMD64 dual core platform with all the most recent upgrades installed. After the most recent Kernel upgrade version 2.6.31.20 the computer failed to boot correctly. Extremely slow getting to the desktop and a general failure to preload any programs that I load on boot. I had to uninstall and revert back to the previous Linux headers which solved the problem. If it makes any difference I have the machine setup as an apache2 server along with my standard desktop environment.
I have just updated my kernel and immediately struck trouble. The kernel update is marked as security update. When booting I get a multiple warnings " deprecated config file /etc/modprobe...", then "no root device found" followed by "boot has failed, sleeping forever"!Clearly something is amiss with this update, so figured the best thing might be to remove it and wait on a fix, but attempting to remove the kernel via the package manager would cause a whole lot of other packages to be removed as well.Instead, I edited grub.conf, commenting out all the kernel-2.6.34.7-63 lines, so that the default is now the previous kernel (2.6.34.7-61).
I am getting a problem when login into FC10. It boots correctly an shows the login screen; then, when typing my user and passwd goes to the desktop and shows a KERNEL FAILURE. At this moment, most of the times the PC is blocked and doesnt works any more. One time has continued working without problems.
After the las failure, my system log has this info:
Code:
I have checked my hard disks (fsck) y every thing looks fine. However, i dont know how to fsck the VolGroup0. I cant'get it unmounted.
I upgraded the kernel of my machine with a yum update, and now it will not boot. I am running Fedora 14 on a 64 bit machine. I really really need it to boot. Help!
I did Ctrl+Alt+F2 and managed to log in. I have kernel x86_64 2.6.35.12-90.fc14 installed. How do I log in as usual? I never get to a login screen.
I successfully installed Ubuntu 9.10 Netbook Remix on an Asus EeePC in a dual boot mode with Windows XP. Because the computer has no CD drive, I used a USB stick to download the files for installation. Twice now, after upgrading to a new kernel (2.6.31-17 and 2.6.31-19 I think), when rebooting after the upgrade and selecting Ubuntu from the operating system menu, I get a message:
sh:grub>
along with a notice about limited shell commands being available. The ls command results in:
(loop0) (hd0,3) (hd0,2) (hd0,1)
In trying some of the other commands, I get a message that a linux kernel isn't loaded. The computer still runs Windows fine - or at least as fine as Windows ever runs. I'd like to recover Ubuntu without doing another full installation.
