Debian :: After Login Following Warning Popup - Your System Had A Kernel Failure
Jun 26, 2010
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.
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.
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.
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.
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.
I noticed today I downloaded the amd64 netinst ISO for 'testing' and during the installation, it warned me of a the fact that I was installing using the 2.6.30.x kernel and I am now attempting to install a 2.6.32.x kernel. Is this is a common warning because I have never seen it before. I got it with both the netist & the businesscard image. Has anyone seen this before and is this a problem? Just trying to understand whats going on under the hood. I don't have the error in front of me since I am on my phone away from the office.
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 am an old Debian user, ho just reinstalled it again to see how it evolved since my las version (3.2). I am sharing it with Arch Linux, And decided to let bot of them. I am using GDM compiled and configured in Arch, and removed GDM2 from Debian (i just like the easy menu.list from the old GDM). The problem is that when i update the kernel, it didn't fing GDM and drops an error message. I tried removing the distro-preconfigured Kernels, as i compiled my own 3.0.0-rc2 Kerenel, but i cant delete the previous ones. Now everytime i do an install or uptgrade, apt-get drops wastes some time, and drops an error message:
[code]...
What can i do? i googled some similar errors, but where just messed up mirror.lists, or similar, i know it isnt the cause of fail.
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'm testing to log in using openldap authentication on jessie by following article from [URL] ..... and when I try to log in from ldap client (another debian 8 VM), it failed with
Code: Select allFeb 3 09:25:33 clt nscd: nss_ldap: could not connect to any LDAP server as cn=admin,dc=test,dc=lab - Can't contact LDAP server Feb 3 09:25:33 clt nscd: nss_ldap: failed to bind to LDAP server ldap:///192.168.191.120: Can't contact LDAP server Feb 3 09:25:33 clt nscd: nss_ldap: reconnecting to LDAP server... Feb 3 09:25:33 clt nscd: nss_ldap: could not connect to any LDAP server as cn=admin,dc=test,dc=lab - Can't contact LDAP server
I do not know if this is really something I should worry about. I am running Debian testing on my laptop (HP Pavillon dv6). Today, the aptitude update---aptitude upgrade gave me a new kernel (2.6.39). However, if I boot with that kernel, I get a warning (do not know if that is the way I should call this) telling me that the machine failed to get the i915 symbols so turbo graphics will be disabled.I have not done any serious test, but at first sight I do not notice any difference performance-wise with respect to the previous kernel. what am I supposed to do to fix this?
I'm new to Debian and installed it with Cinnamon because I want to learn some OpenCL programming in Linux. I have a Nvidia GT 525M GPU. Once the operating system is installed, I followed [URL] ..... article to install the proprietary Nvidia drivers. As the forum suggested, instead of creating an Xorg server configuration file, I installed Bumblebee according to [URL]..... article.
But when I restarted my machine after completing all the steps when I try to log in I get the follwoing message:
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 had occasion to add a few lines to rc.sysinit. Turns out the lines syntax was wrong. Instead of the booting ignoring those lines and proceeding on, then giving me an error warning or perhaps dumping into the interactive mode it just hung up! After several tries at moving on I discovered ESC dropped me into some sort of unannounced shell I got the installation disk out and with the repair system option using VI I got the lines deleted and all went back to normal. Now my suggestion is that if something does not make sense in terms of syntax while booting then cover it by doing the above and ignoring it with a warning later.
I was testing out Ubuntu 10.04 on both the a desktop and a laptop (both HP...I don't remember the particular models but if asked I will find out). It worked fine on the desktop. When I booted the laptop with Ubuntu it worked fine. When I tried to connect it to the internet it seemed to go okay. I mean it asked for the network password and everything. But as soon as the signal was recognized I got a warning that said "Hard drive failure is imminent."
Now this laptop has gone through problems before. I don't know the extents because it's a family laptop and I rarely use it (it's super slow. It used to run Vista but now it runs XP and it's slow regardless). I think the hard drive may have been replaced at one point of another and it has had to be re installed numerous times before. And the way it is used leads me to believe that there is not a lot of space left in that hard drive. So that may have been the issue.
But I want to make sure it is a hardware problem and not something that will happen on the device I eventually decide to install Ubuntu on. How to understand why the hard drive would fail when the live CD doesn't actively use the hard drive, at least not the way it would if it had been installed in the hard drive.
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.
When trying to do an update or upgrade, I get the following:
Running Transaction Warning: RPMDB has been altered since the last yum transaction. Traceback (most recent call last):
[Code]....
I have tried yum clean all, yum clean metadata, rpm --rebuilddb, and even removing /var/cache/yum. yum info and yum list both work fine. Naturally, this yum problem is preventing me from updating my system.
Things were fine for a couple months until this most recent dist-upgrade. The new grub has an incompatibility with BTRFS which nearly caused me to lose everything, as grub couldn't set up the boot system since it can't see the BTRFS partition. I worked for days trying to get help in the linux-btrfs listserv, but they don't seem to understand Debian/Ubuntu, and they kept referring me to Debian and grub devs. I asked them how those devs will know any more about BTRFS than they do, but there was no reply.
They said the new grub (1.99~rc1-13) will fix it, but unfortunately the Debian package management system was jammed by BTRFS as well and I couldn't install/deinstall anything. I finally had to unpack the grub-pc .deb and manually install it, but guess what? It didn't fix the problem. I've now had to completely rebuild my system without BTRFS. This has cost me days, which I cannot spare. I realize it says 'experimental' on the BTRFS website, but it is in the stable kernel, and there is not a word anywhere about it being completely non-functional in Debian/Ubuntu.
I installed 2.6.38 from backports. It boots OK, and among the start-up messages it says it has started kdm, but then it offers only a console login prompt, no GUI. I assumed (perhaps optimistically?) that newer kernels would be backward-compatible, and that any dependencies on other software would be enforced by the package mechanisms. Running amd64, Squeeze, KDE.
I am running debian unstable on my netbook lenovo s10-3t. after updating system yesterday i can't login. when i turn laptop on i get gdm login screen. when i enter my username and password it is loading for 30 seconds or so and then i get back to login screen. alt+ctrl+Fn doesn't work after that (but works before). there is no errors in x server log (cat /var/log/Xorg.0.log | grep EE gives nothing). in xsession-errors there is something about "_Polkit". also before fatal io error 11 i have nautilus-gdu extension going to be initializing. i tried to remove /etc/X11/xorg.conf and get new by X -configure, but there was no change in behaviour of gdm. i also tried to add new user, but again, no changes.
i have to reinstall my pc with a testing version. The installation almost is the same as stable version (lenny). But, the problem is that, i can't login it after the installation completed. The new user i created during installation is invalid! So, i have to enter the single user mode, to my surprise, the new user(i created before) doesn't exist! So, i add a user here.But, i still can't login to my system as the normal mode.How should i resolve such a problem?
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:
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.
