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
View 6 Replies
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
The directory is indeed empty. I have reinstalled
Code: Select allapt-get install -reinstall initramfs-tools
and rerun initramfs
Code: Select allupdate-initramfs -c -u
I tried running Ubuntu Linux 9.10 on my computer directly from the CD, without installing, and when it had finished loading neither the keyboard nor the mouse would work. I got a message saying that restricted drivers had been blocked. I can't press what I think to be the unblock command because both the keyboard and mouse had been blocked.
View 2 Replies View RelatedI recently tried to install php5-gd package on my debian vmware server and it failed at libc6 - i386.
Afterwards every command other than CD caused a Segmentation fault and the server would no long boot, showing the following error
[ 4.808086] init[1]: segfault at 0 ip (null) sp bff4645c error 14 in init[8048000+8000]
[ 4.808372] Kernel panic - not syncing: Attempted to kill init!
[ 4.808442] Pid: 1, comm: init Not tainted 3.2.0-4-686-pae #1 Debian 3.2.65-1
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 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:
WARNING! power/level is deprecated use power/control instead
Jul 13 18:26:49 destiny kernel: [ 6196.892776] Call Trace:
Jul 13 18:26:49 destiny kernel: [ 6196.892803] [<ffffffffa008feec>] ? scsi_setup_blk_pc_cmnd+0x15/0x104 [scsi_mod]
[Code]...
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.
So it's a beautiful day and I'll be happily using my computer when I realise that the screen is no longer showing that I'm typing or moving my mouse (or finger across a touch-pad). I can leave my computer in this frozen/crashed state for hours. My only recourse is to drain the battery or hold down the power button until the computer shuts down. The computer is a Dell Inspiron 6400 laptop/notebook. As my memory serves, it has an ATI graphics thingy. Radeon 1400, maybe. But I've had the computer for years and this behaviour has emerged only the past couple of months, with seemingly increasing frequency.
The OS is
# uname -a
Linux polaris 2.6.32-trunk-amd64 #1 SMP Sun Jan 10 22:40:40 UTC 2010 x86_64 GNU/Linux
(aka Squeeze?)
Sometimes this happens within minutes of turning the computer on and logging into Gnome. Sometimes this happens only hours after I've started using the computer (mainly just surfing the web). Sometimes it is preceded by a loud boop sound and the following if I have console open, sometimes not. So maybe that's unrelated. But that happened just now so I thought I'd throw it in.
One weird thing: Usually this happens within an hour of starting to use the computer, but one occasion I noticed I had not had the problem for several hours. On that occasion, the only thing I noticed I was doing that was also unusual: I had turned on and forgotten about a kvm virtual machine. After I shut down the vm, I had about only a minute before the freeze. I'm surprised now that it hasn't frozen since I started typing thing. Maybe I should always keep this forum open in a browser window.
A couple of weeks ago I installed a new 4-core Lenovo PC and installed Squeeze on it - keeping it updated every day. When kdm or gnome display the login screen, my USB-connected keyboard and mouse don't react. When I then unplug and re-attach them into the same socket everything ist fine. Surely this can't be working as intended? I can however get into BIOS-Setup as usual during the initial boot-phase by pressing Crtl-S and F1. Things also are fine when selecting the debian version to run from the multi-boot screen.
I am enclosing the kern.log of the last boot below (don't know how to attach files!). In that I can see that on line 530 ist says New USB device found, idVendor=046d, idProduct=c03e (address: 5; optical Logitech mouse) and then on line 542 New USB device found, idVendor=046d, idProduct=c31c (address: 6; keyboard).
It seems to get "interesting again on line 632 etc. with the message usb 2-1.8: USB disconnect, address 6.
-------------------------------------
2.754607] usb 2-1.5: new full speed USB device using ehci_hcd and address 4
2.855589] usb 2-1.5: New USB device found, idVendor=046d, idProduct=0a0c
2.855594] usb 2-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
2.855598] usb 2-1.5: Product: Logitech USB Headset
[Code]....
I have gone through all the kernel config options repeatedly, but everytime I get the same error after running my configured kernel.
To begin with, after unpacking the kernel I get Undefined video mode numer: 305 and then a selection of video modes appears.
Why are the standard settings in my lilo 1024x768x256 (vga 773) not accepted?
VFS: Cannot open root device "808" or unknown block(8,8) Please append a correct "root"=" boot option; here are the available partitions: Kernel panic- not syncing :VFS: Unable to mount root fs on unknown block(8,8)
My partitions are ext2, and this format (as well as other formats) are compiled in the kernel.
I'm trying to install slackware 32 bit 13.1.After loading kernel it asks for keyboard configuration, but keyboard (usb wireless) doesn't work.
Keyboard works on the old 13.0 installation, on bios and also in the boot options of 13.1 installation cd.
I've tried removing legacy usb support and changing usb2.0 speed from high to full. Nothing changed.
Anybody with this strange problem? (kernel of setup seems also to detect it correctly as a trust keyboard).
we are getting Out of memory issue in web server log & kern.log at same time cpu load is comming very high....
top - 13:37:10 up 221 days, 12:43, 0 users, load average: 90.56, 61.63, 31.44
Tasks: 229 total, 64 running, 165 sleeping, 0 stopped, 0 zombie
Cpu(s): 1.6%us, 0.3%sy, 0.0%ni, 97.2%id, 0.8%wa, 0.0%hi, 0.1%si, 0.0%st
[code]....
I am having some troubles with my networking. I have a fresh install of Debian 4.0.4-1. My problem is: I boot up and everything is great.
Code: Select all~# ifconfig
eth0   Link encap:Ethernet HWaddr 00:1e:68:46:4b:aeÂ
    Â
   UP BROADCAST MULTICAST MTU:1500 Metric:1
   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
     TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    Â
[Code] ...
I try to switch the hardware switch on and off with no avail. The only way to fix it is to reboot. But then when I ifconfig down and up I'm stuck in airplane mode again.
I just upgraded (via backup and install) from 11.1 to 11.2. SaX2 was perfect for configuring my IBM SpaceSaver (Trackpoint) USB keyboard, and my Logitech Marble Mouse. Now that SaX2 doesn't have the keyboard or mouse, eh... modules?, I don't know how I can configure them the way I'd like.
What now? I'd rather not have to use the on-screen keyboard every time I start up openSUSE to turn off NumLock... Do I have to manually edit /etc/xorg.conf now?
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'm having some issues creating output from kdump-tools. (Initially to diagnose some system freezes when using wine, but now I can't a staged panic to work and provide proper output.)
I initially started following what is stated at this link: https://www.bentasker.co.uk/documentati ... ian-jessie
Where basically the author says:
Code: Select allapt-get install kdump-tools crash kexec-tools makedumpfile `uname -r`-dbg
to get all relevant tools.
Then in /etc/default/kdump-tools edit the following to :
Code: Select allUSE_KDUMP=1
in /etc/default/grub I edit the following line to the following :
Code: Select allGRUB_CMDLINE_LINUX_DEFAULT="quiet crashkernel=128M"
followed by update-grub. Then I get the pleasure of rebooting.
once I'm back in my system, I do the following.
Code: Select allecho 1 > /proc/sys/kernel/sysrq
echo c > /proc/sysrq-trigger
The system freezes, but does not dump any relevant information or reboot. It just hangs.
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.
View 1 Replies View RelatedI 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.
View 3 Replies View RelatedBecause 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?
For some reason I am unable to use either my keyboard or my mouse. No problem in etch up until now, even after rebooting.
View 1 Replies View RelatedAs the title says i have this error on both my main computer and my laptop. For my main computer see this post, that is when it happened. viewtopic.php?f=30&t=65743
I run the updates on my laptop a while ago and decided to restart it to check if everything went okay. It seems not.
The only way i can get on the desktop, is to choose the recovery mode, su to user and startx.
This is a common error during booting on both computers. Starting the hotplug events dispatcher: udevderror binding control socket, seems udevd is already running
It seems a little strange, same error on both computers.
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.
And here is what my menu.list looks like:
I use a set of keyboard + mouse Logitech MK330. So, they are wireless in five minutes of inactivity have to sleep. But sleep only the keyboard. The mouse does not fall asleep. On distro Ubuntu and Windows goes into standby mode, both devices. How can I fix it to Debian?
During installation Debian distro, mouse goes to sleep, but on the installed system will not go into standby mode.
I've just installed Debian Testing XFCE, and mouse & keyboard don't respond to any inputs. The keyboard works just fine in the Recovery Shell, that's why I suspect a problem with the XServer.
View 9 Replies View RelatedI have debian with kde on a laptop with a built in ps/2 keyboard and touch pad mouse which have been working without problem since i bought the computer. However, recently i booted the computer up and all of a sudden the mouse and keyboard are not functioning. I know it is not a hardware problem because i can type in the BIOS password, make the selection between normal and recovery mode in grub, and can type in all of my passwords to unencrypt my hard drive.
Also, it recognizes the keyboard all the way up until the point where kde starts, at which point it loads a login screen with the mouse and cursor on the screen, but no ability to type, not even caps lock or ctrl+alt+f1 to switch to console mode. does anyone know why this is? I have performed not updates and have not changed the configuration of my computer so i am not sure why this would happen.
P.S.1 out 15 times when i load the part where i need to type in the passwords to unencrypt the hard drive the keyboard will stop working then instaed of with kde.
I am using Debian with a gnome desktop.
Code: Select alluname -a
returns
Code: Select allLinux app-server 3.2.0-4-amd64 #1 SMP Debian 3.2.65-1+deb7u1 x86_64 GNU/Linux
My desktop sometimes freezes and does not respond to keyboard or mouse. I initially thought the CPU was overheating but it froze tonight when my CPU temperature was 32C and it has been up to 50C without freezing. I am beginning to think it is a software issue rather than a hardware issue but do not know. I looked at the pm-powersave.log and user.log but did not see anything suspicious.
I was trying to tweak my video card's performance by configuring the xorg.conf file. There were many lines unrelated to the card there; so, to make the file cleaner, I decided to delete all the sections except the one I was dealing with. Obviously I shouldn't have done that. After rebooting the system, all the hardware that provided human interface stopped working. Now I have to find a way to delete that xorg.conf file. The computer is still connecting to the internet, and I have another computer running Debian available. Is there a way to access the broken computer with the other one?
View 4 Replies View RelatedAfter installing KDE USB keyboard and mouse won't work. They are added to /proc/bus/input/devices though.
I also tried to install Gnome; same thing.
I took #usb-devices and they were there also..
But #usbhid-dump did not generate anything to screen.
I have Asus Z87-PRO motherboard with i5-4670k and I'm trying to install Debian Testing with 64-bit architecture. My problem is mouse and keyboard (I guess USB in general) stop working after installer get loaded (the last thing I do is choose between text and graphical install). I found a few topics on different forums indicating that I should enable IOMMU (Intel VT-d) option in my bios.
The problem is that Intel k-series processors didn't use to have IOMMU support, so there's nothing I can do about it. I tried changing different bios options like disabling UEFI, enabling xHCI and EHCI with no luck. Passing "iommu=off" or "iommu=soft" to the boot command also doesn't work. However, I have LMDE 2 64-bit live cd (based on Debian Jessie) and it works fine, so I guess my problem may be related to some changes in 4.2 kernel.
