I am working on Fedora core 4 with kernel verion 2.6.11.. I am running a Manager process which spawns child process. If a child process exits , the SIGCHLD signal is processed in parent process and it is forked again. When the parent process receives a SIGTERM signal it first tries to kill the child process using SIGTERM signal . if the child process dosen't get stopped then kill it using SIGKILL. Now,the Parent process sometimes gets hanged and the strace shows :
futex(0x98535e0, FUTEX_WAIT, 2, NULL <unfinished ...>
Every time I boot up OpenSUSE 11.3 it hangs at the same "position" for approximately 3 minutes and then continues to boot. Unfortunately I see no corresponding error log e.g. in dmesg output. Hence, I don't know what is the reason for that. Here is my dmesg output. The delay occurs at 20 seconds after beginning of boot process (line 1085). I also analyzed the boot process with bootchart. My computer: Notebook Lenovo ThinkPad R400.
I downloaded Ubuntu 10.10 and made created a DVD. When I started installing it, I'm not able to do it. I think its hanging. This is what happening: First I found a screen saying 'ubuntu 10.10' and it loaded for some time then I got a screen with a black color task bar at the top of the screen, then after some time it turned into white color and after some time it disappeared. Nothing else happened. I didn't find any pop-up window to start installation of OS..
But when I tried this in my friends house, I found that instead of 'ubuntu 10.10' there came 'Ubuntu' LOGO and it was little bit slow but a pop-up window opened to start installation.. Why its not coming in my PC.. my computer configuration : Windows XP, SP 2 256 MB RAM, 1.81 Ghz AMD 64 Athlon Processor 1800+ I want to shift my OS to Ubuntu completely.
What is the best method for debugging the booting process? Is there a cheatcode (tried debug and failsafe). Slackware 13.1 with standard linux kernel 2.6.35.8. I having a problem with a dell server 2860 booting my build. It is hanging on
[Code]....
Booting my previous kernel 2.6.27.27(different disk with different initrd.gz) it loads the same as above but continues with
Code: loading iSCSI transport class v2.0-870 iscsi registered transport tcp I'm stumped it the problem is with the ata_piix module or the iSCSI transport module or some firmware I might be missing. I booted other pcs without issue.
I am installling ubuntu on my old (2003) Dell D800 laptop with celeron processor, using a CD (burned at home). The installation process is hanging for about 24 hours now; it says "copying files..." with progress at 63%. The progress has not changed for about 10 hours.
I have a single hard drive on the machine (... noticed issues with dual drives on this forum, so thought I'd mention).
I've some file with .sh extensions that runs some softwares.Now,how do I stop running that filesI know we run the command ./start_tomcat.sh to start the apache.Is there any command to stop that file/process or is it just kill the process to stop the process
My Fedora setup is working great so far, and I don't really have any complaints. I installed it on a portable hard drive, connected over USB. Thing is, I installed my system with the LiveCD, and I wanted to download the full DVD for a friend because of his needs for his system. When I try to download the full DVD (whether over Firefox or Transmission), the system hangs by suddenly showing a screen with the Fedora logo in the middle and a light blue background, the same as in boot up. Also, my caps lock blinks in a consistent fashion like a metronome. The same happens whether I try to download to the portable hard drive or to a FAT32 partition on my laptop's actual hard drive. Is there any way to fix this, or can I be calmed by the fact that it just happens because it's installed on a portable hard drive? This problem isn't happening on Ubuntu (which is installed on my laptop's hard drive), where I am downloading from right now.
I've been having trouble with my desktop ever since I upgraded from F 11 to F 13 last night. Finally, however, I got the proper version of the nVidia drivers installed. However, it's stopped completing boot. I've edited grub at boot to get it to show the boot messages and find that the last thing it reports is success in registering the binary for Windows applications. After that, it just sits there, doing nothing. I can go to an alternate console an d log in, but that's all.
If I log in and run startx, it fails.It reports that it was unable to load the nvidia module and "no screens found." Does anybody know what I should do next?I've removed both kmod-nvidia and akmod and am going strictly with the nouveau drivers.I've booted, used Ctrl-Alt-F2 to get a console, logged in as root and run the setup program to configure X to run that way, then returned to the main console and logged in as myself. Shortly after my wallpaper shows up, and long before I have a working desktop, it goes white and stays that way. Aside from getting a different video card (The old one worked Just Fine right up until I upgraded.) what else can I do?
I installed adobe reader quite some time back. It was working fine. Nowadays it gets stuck up and then the screen fades out and then after some seconds it gets back to normal. What could be the problem.
I'm having problems booting up my Fedora 14 system. I see the Fedora splash screen (the one with the egg-like logo that colorizes as it loads); the logo fills up completely and then everything hangs - all I see is the egg logo, and nothing else is ever displayed. I also can't get to any of the ttys via the CTRL-F1 sequences.
I can boot into single user mode just fine. The install scripts all run just fine. The system itself is actually up an running, so I suspect this is either something in the KDE startup, or after init processes all of the start up scripts.
I'm assuming this isn't a startup script problem, because I see a "started XXX" message for every service in the rc.5 directory - in other words, all the startup scripts ran from rc.5.
So, how do I find out what is hanging? I'm not seeing anything in /var/log/messages, and pstree didn't tell me much about what init was doing.
I used to be able to follow inittab to see all the things it did at boot, but since inittab was stripped of everything it used to do a few releases ago, I don't know what init is doing anymore.
I have just installed Fedora12 x86 64. On booting more often than not it hangs just before completing the login screen.I will try some of the options in the wiki. In the mean time has anyone else experienced this and resolved it.The odd thing is although the keyboard is not on, (num lock light goes out as boot starts and only comes back on if it has fully booted), the mouse will move around the screen but the click has no effect.Note the same behaviour was shown on the x86 64 live cd which I needed to install to enable me to create a bootable usb stick from the x86 64 DVD.
When I went to start up the computer, the kernel usually hung at the same place on boot up, although sometimes it booted just fine. The default kernel is 2.6.31.9-174.fc12.x86_64. It's boot up arguments are:
I also have kernel 2.6.32.7-37.fc12.x86_64, 2.6.31.6-145.fc12.x86_64, 2.6.31.5-127.fc12.x86_64. I have seen the same behavior out of all four of them. Last night I ran Memtest86+ all night. It took eight passes with no memory errors. As far as hard disks go, I have two Seagate Barracuda 1.5 TB drives operating as software RAID 1 (mirroring). One of the drives does have three bad sectors. The motherboard is an Asus P6T6 WS. This morning I plugged in the GP diagnostic chip that came with it, but I'm not seeing a whole lot useful there, except that now it is just displaying "FF" non stop.
I did some poking around on the web, and it looks like "FF" is supposed to mean that the CPU isn't properly seated, which makes no sense because the system monitor software is detecting all four cores perfectly, and I have no other odd behaviors anywhere else. At this point I'm rather at a loss to understand what could be causing the difficulties. Sometimes any of the four kernels boots fine, and sometimes they don't. The funny thing is that on the blue "boot progress bar" all four kernels hang at exactly the same spot if they hang at all. After doing some more poking around, I'm relatively sure that "FF" does NOT mean that the processor isn't seated correctly. I'm going to try contacting Asus and see how far I get towards getting some good info on what the diagnostic codes mean.
I am trying to install Fedora Core 10 64bit on my Desktop... i've been running FC7 on it until now.The installer continues until the Anaconda GUI, and I am able to click next on language select, then when I click to select "U. S. English" as the keyboard layout and press NEXT, the installer hangs. I ran the disk verification at the start and it passed, so can't be a corrupted installation disk.I can move to the other terminals away from the Anaconda GUI Installer, and in one
Code: INFO: moving (1) to step welcome INFO: moving (1) to step language
Almost every other time I run yum update, I'm getting mirror problems - this is losing all my confidence in Fedora for several reasons: a) it's wasting time - what should be 1-2 minute updates are taking 5-10 minutes and often (like tonight) not even completing b) since it keeps hanging and switiching mirrors during downloads I wonder if the updates are coming thru okay c) the fact this is not being seriously addressed makes me wonder re Fedora quality. Add to that the constant and real annoying kernel errors popping up re network manager and sierra wireless (even when my sprint card is not plugged in).
I installed Fedora 12, 64 bit on my Dell Latitude D820 laptop with Core2 Duo processor(7200 speed) and 2 gigabyte Memory.
I have updated the yum. I have enabled the rpm repositories.
It is very weird that my system suddenly works very slowly and hangs. every time I login after a while the CPU usage goes up to the end with out any reason!
Before this I had installed Fedora 12, 32 bit and I had the exact same problem.
I have installed Fedora 6, 7, 8, 9, 10 and 11 on my laptop before and I had non of these problems with them.
The interesting point is that after hanging my system works constantly slow even when I restart my system! It is slow even in booting the BIOS and start up and choosing the kernel page!
The only remedy to get rid of the slow working for a while is to Shut down the system completely and turn it on again. Restarting do not make it work normally just shutting down makes it normal for a while.
A little while ago I moved to F14 from Ubuntu; I've been ok, but recently sudo has been causing me trouble :/It seems to hang, but eventually produces some output indicating that it has been waiting for me to input a password; but it hasn't prompted me for one.
I upgraded to Fedora 12 right after release, everything was working fine until update on previous weekend. Looks like it updated Wacom drivers and kernel. Now what I have. I hotplug my tablet in USB, and everything seems fine, I can position a cursor and press buttons, but after I press some button it hangs (LEDs on tablet are responding) I must remove Stylus from proximity in order to make it respond again (while stylus is away LED on tablet switches off for a fraction of second).
If I move mouse during tablet hanging, applications barely respond and if they are it is like mouse button is pressed (selecting text). I tried wacdump, and it's reporting everything's fine (X,Y, Tilt, Pressure everything shows up). I couldn't find evidence that wacom driver is controlling it, but I assume if wacdump is reporting then it is. I have: Kernel 2.6.31.6-145.fc12.x86_64 linuxwacom.x86_64 0.8.2.2-15.fc12
I didn't touch xorg.conf in sense of tablet, but it worked for me in F11 and until now. I'm trying to make least manual configurations possible. Through exploring /proc/bus/usb/devices and kernel messages I confirmed that wacom drives is handling the tablet. And I noticed that in X's log
(II) config/hal: Adding input device Wacom Intuos3 9x12 (**) Wacom Intuos3 9x12: always reports core events (**) Wacom Intuos3 9x12 device is /dev/input/event8 (**) Wacom Intuos3 9x12 (Wacom Intuos3 9x12) is not a pad (**) Wacom Intuos3 9x12 is in absolute mode (**) WACOM: suppress value is 2 (**) Wacom Intuos3 9x12: reading USB link (**) Wacom Intuos3 9x12: threshold = 61 (**) Wacom Intuos3 9x12: max x = 60960 (**) Wacom Intuos3 9x12: max y = 45720 (**) Wacom Intuos3 9x12: max z = 1023 (**) Option "BaudRate" "9600" (**) Wacom Intuos3 9x12: serial speed 9600 (II) XINPUT: Adding extended input device "Wacom Intuos3 9x12" (type: Wacom Stylus) (EE) Wacom Intuos3 9x12: Top/Bottom area overlaps with another devices. (EE) Couldn't init device "Wacom Intuos3 9x12" (II) UnloadModule: "wacom" (EE) config/hal: NewInputDeviceRequest failed (1)
I've encountered quite similar error in openSUSE when was configuring tablet manually in xorg.conf. As I can see problem is with "pad" device, which I disabled in openSUSE in order to make X running. So why is it not working?
From some time now whenever i start the Package Manager it hangs at the line "Loaded Plugins: refresh-packagekit" I don't know the reason as it doesn't throw up any errors. Even if i reset the terminal. nothing changes. if i force quit then when i start package manager again (in the same boot) it stops and gives the message that other application has yum lock as i cannot auto install any software
I have a high priority service that I start with sudo nice -n -10 process. This process does not need superuser rights though, except for the priority elevation. But nice requires superuser privileges to elevate priority.
Description of what the code does or what i intended to do:
1. Created a child process from parent process using 'fork()'
2. Sent a signal 'SIGALRM' from child process to parent process using 'sigqueue' function.
(The Third parameter of 'siqueue' function contains the message (message msg) which the child process wants to send to the parent process.'msg' is a stucture instance containing a) pid of child and b) string) 5. Print the 'msg' sent by child process inside the signal handler function 'sig_action_function' of the parent process I am getting some junk value when this line is executed
Code:
printf("%d ",msg->cpid);
I expected to get the pid of child process, which the child process sent to parent process through the signal.
as we all know Process Scheduler does Process scheduling and its a process as well. I was just wondering that if this happens then the Process "Process Scheduler" should be a part of Process queue as well.
So if there are 5 process are there in Process queue & process scheduler is administrating them then since its also a process, once it puts a process under RUN state it should itself go inside queue because at one instant only one process can get executed on a processor. This is quite confusing for me. Please help me out. I tried to search on this but could not find any relevant topics.
I have a shell script to identify whether the process is running or not. If the process is not running, then I execute another script file to run my application. Below is my script and saved this script as monitorprocess.sh Code: #!/bin/bash
I have a process running on Linux.When i do ps -eaf | grep <myProcess>, it show muliple entries for <myProcess> with different pids for each entry.Kindly tell me what could be the reason for a process having multiple pids?
Is there any difference in cpu usage for process in init.rc(runs automatic when boot is happened) and manually running process. Will these both have same priority by default...?
I tried googling but didn't get any answer for this.I have a process called "abc" and it is running with PID "123".I have a putty session opened with PID "999".I am giving kill -TERM 123 from putty session.My process "abc" before dying it should catch the PID of the terminal which provided TERM signal to it.Is there any way to find this out
I recently upgraded my Opensuse dom0 from 11.2 to 11.3, and so Xen from 3.x to 4.01.Ever since, Windows HVM domus hang after a random amount of time. Always within 24 hours of starting though.The VMs are XP and W7, and have tried both hvm drivers and gplpv drivers. There are no errors in xend.log, or the qemu-dm logs or xm dmesg. I have tried apic and acpi both on and off.
If I VNC to them, I can see that they have simply stopped.If I force them off and start them again, there is nothing in the event log of the VM, it just stops and becomes unresponsive, with no associated log entry.I have re-installed one of the VMs from scratch, with a slightly different version of W7. No difference. The stalling even happens during installation, so it doesn't seem like any software I have installed or configuration could be related.
