F11: kill -9 doesn't work
Hi, I have noticed on several occasions, that running "kill -9 " on a GUI 3D process that is locked at 100% CPU usage (X-Server 100% also) does not work. The 100% lockup I'm sure is due to the currently buggy 3D support (ATI in my case), but I am surprised that I cannot kill either the GUI or X processes. Only a reboot appears to work. Has something changed here ?? Cheers Terry -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F11: kill -9 doesn't work
Terry Barnaby wrote: On 07/24/2009 10:40 PM, Bill Davidsen wrote: Currently if I run paraview, X goes to 100% and I can no longer operate the system via mouse/keyboard. Via a network login I can "killall -9 X" but that does nothing to X. I have also tried killing paraview in the same way with no effect (possibly after trying to kill X). I hope this is a typo, process "X" is long gone, the X process is called "Xorg" now. I assume you had a finger check and actually killed the real X process. On F11 "Xorg" is hard linked to "X" and "X" is the program started. So in "ps" listings the XServer process is named "X" and to kill it with "killall" you need to do a "killall -9 X" ... On my system both top and ps show it as Xorg, FC9 and FC10. I don't have an FC11 machine handy right now, so I can't swear to that, but 'killall Xorg' sure kills X in a VM! Anyway, since your problem is solved it's not an issue. -- Bill Davidsen "We have more to fear from the bungling of the incompetent than from the machinations of the wicked." - from Slashdot -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F11: kill -9 doesn't work
On Wed, Jul 22, 2009 at 01:02:09PM +0100, Terry Barnaby wrote: > Hi, > > I have noticed on several occasions, that running "kill -9 " on > a GUI 3D process that is locked at 100% CPU usage (X-Server 100% also) > does not work. The 100% lockup I'm sure is due to the currently buggy > 3D support (ATI in my case), but I am surprised that I cannot kill > either the GUI or X processes. Only a reboot appears to work. > > Has something changed here ?? If you provide more details, such as the actual process you're running, people might be able to try to duplicate the problem. I've never seen an occasion where kill -9 didn't work, but that doesn't mean it's not possible with some horribly written code. -- Paul W. Frieldshttp://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F11: kill -9 doesn't work
On 07/22/2009 02:07 PM, Paul W. Frields wrote: On Wed, Jul 22, 2009 at 01:02:09PM +0100, Terry Barnaby wrote: Hi, I have noticed on several occasions, that running "kill -9" on a GUI 3D process that is locked at 100% CPU usage (X-Server 100% also) does not work. The 100% lockup I'm sure is due to the currently buggy 3D support (ATI in my case), but I am surprised that I cannot kill either the GUI or X processes. Only a reboot appears to work. Has something changed here ?? If you provide more details, such as the actual process you're running, people might be able to try to duplicate the problem. I've never seen an occasion where kill -9 didn't work, but that doesn't mean it's not possible with some horribly written code. The system in question is a dual Xeon system running Fedora-11 with all updates to 2009-07-22. Graphics board is an ATI RV280 [Radeon 9200 PRO]. I have some applications installed from rpmfusion including paraview. Currently if I run paraview, X goes to 100% and I can no longer operate the system via mouse/keyboard. Via a network login I can "killall -9 X" but that does nothing to X. I have also tried killing paraview in the same way with no effect (possibly after trying to kill X). I know 3D is horribly broken in F11 :( as well as many other things, but I would have thought that kill -9 should still work ... Cheers Terry -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F11: kill -9 doesn't work
On Wed, Jul 22, 2009 at 03:01:50PM +0100, Terry Barnaby wrote: > On 07/22/2009 02:07 PM, Paul W. Frields wrote: >> On Wed, Jul 22, 2009 at 01:02:09PM +0100, Terry Barnaby wrote: >>> Hi, >>> >>> I have noticed on several occasions, that running "kill -9" on >>> a GUI 3D process that is locked at 100% CPU usage (X-Server 100% also) >>> does not work. The 100% lockup I'm sure is due to the currently buggy >>> 3D support (ATI in my case), but I am surprised that I cannot kill >>> either the GUI or X processes. Only a reboot appears to work. >>> >>> Has something changed here ?? >> >> If you provide more details, such as the actual process you're >> running, people might be able to try to duplicate the problem. I've >> never seen an occasion where kill -9 didn't work, but that doesn't >> mean it's not possible with some horribly written code. >> > The system in question is a dual Xeon system running Fedora-11 with all > updates > to 2009-07-22. Graphics board is an ATI RV280 [Radeon 9200 PRO]. > I have some applications installed from rpmfusion including paraview. > > Currently if I run paraview, X goes to 100% and I can no longer > operate the system via mouse/keyboard. Via a network login I > can "killall -9 X" but that does nothing to X. I have also > tried killing paraview in the same way with no effect (possibly > after trying to kill X). > > I know 3D is horribly broken in F11 :( as well as many other things, > but I would have thought that kill -9 should still work ... Isn't it 'killall -9 Xorg'? And you'd probably need to issue that command as root, otherwise permission denied. -- Paul W. Frieldshttp://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F11: kill -9 doesn't work
On Wed, 22 Jul 2009 15:01:50 +0100 Terry Barnaby wrote: > I know 3D is horribly broken in F11 :( as well as many other things, > but I would have thought that kill -9 should still work ... Not if it is stuck inside the kernel, kill -9 only kills things as they come out of the kernel. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F11: kill -9 doesn't work
On Wed, Jul 22, 2009 at 10:23:46AM -0400, Tom Horsley wrote: > On Wed, 22 Jul 2009 15:01:50 +0100 > Terry Barnaby wrote: > > > I know 3D is horribly broken in F11 :( as well as many other things, > > but I would have thought that kill -9 should still work ... > > Not if it is stuck inside the kernel, kill -9 only kills things > as they come out of the kernel. And since the OP indicated he was using the ATI driver, I'd say this might be a classic case study in why proprietary, closed-source drivers are bad from the user's perspective too, not just the distro's. -- Paul W. Frieldshttp://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F11: kill -9 doesn't work
On Wed, 2009-07-22 at 10:23 -0400, Tom Horsley wrote: > On Wed, 22 Jul 2009 15:01:50 +0100 > Terry Barnaby wrote: > > > I know 3D is horribly broken in F11 :( as well as many other things, > > but I would have thought that kill -9 should still work ... > > Not if it is stuck inside the kernel, kill -9 only kills things > as they come out of the kernel. Indeed. I have a bug in the Intel video driver, tickled by running the foobillard game. The only solution is to reboot. I've reported it (https://bugzilla.redhat.com/show_bug.cgi?id=510948) and someone else also reported a similar one (https://bugzilla.redhat.com/show_bug.cgi?id=509598) but I've seen absolutely no feedback on either of these. Is no-one else running OpenGl apps under F11? Should I report this bug upstream? poc -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F11: kill -9 doesn't work
On Wed, 22 Jul 2009 10:32:52 -0400 Paul W. Frields wrote: > And since the OP indicated he was using the ATI driver, I'd say this > might be a classic case study in why proprietary, closed-source > drivers are bad from the user's perspective too, not just the > distro's. I think he meant the xorg ati driver. As far as I know there is no binary from ati that works on f11's version of xorg yet. I certainly had the xorg ati driver puking its guts all over at least one machine at work till I figured out how to make it switch to the vesa driver. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F11: kill -9 doesn't work
On Wed, 2009-07-22 at 10:32 -0400, Paul W. Frields wrote: > On Wed, Jul 22, 2009 at 10:23:46AM -0400, Tom Horsley wrote: > > On Wed, 22 Jul 2009 15:01:50 +0100 > > Terry Barnaby wrote: > > > > > I know 3D is horribly broken in F11 :( as well as many other things, > > > but I would have thought that kill -9 should still work ... > > > > Not if it is stuck inside the kernel, kill -9 only kills things > > as they come out of the kernel. > > And since the OP indicated he was using the ATI driver, I'd say this > might be a classic case study in why proprietary, closed-source > drivers are bad from the user's perspective too, not just the > distro's. Unfortunately a similar situation with the Intel driver is getting no attention whatsoever. See my reply elsewhere on this thread. poc -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F11: kill -9 doesn't work
On 07/22/2009 03:23 PM, Tom Horsley wrote: On Wed, 22 Jul 2009 15:01:50 +0100 Terry Barnaby wrote: I know 3D is horribly broken in F11 :( as well as many other things, but I would have thought that kill -9 should still work ... Not if it is stuck inside the kernel, kill -9 only kills things as they come out of the kernel. Kernel code should be written so that it aborts any possible infinite loop when signals are awaiting processing. At least the drivers I have written do (I hope :) )... -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F11: kill -9 doesn't work
On Wed, Jul 22, 2009 at 10:38:49AM -0400, Tom Horsley wrote: > On Wed, 22 Jul 2009 10:32:52 -0400 > Paul W. Frields wrote: > > > And since the OP indicated he was using the ATI driver, I'd say this > > might be a classic case study in why proprietary, closed-source > > drivers are bad from the user's perspective too, not just the > > distro's. > > I think he meant the xorg ati driver. As far as I know there is no > binary from ati that works on f11's version of xorg yet. I certainly > had the xorg ati driver puking its guts all over at least one > machine at work till I figured out how to make it switch > to the vesa driver. I guess it was unclear from the post, I ASSUMEd too much. ;-) Did you use the following command to do that? system-config-display --verbose --noui --reconfig --set-driver=vesa Or something else? -- Paul W. Frieldshttp://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F11: kill -9 doesn't work
On Wed, Jul 22, 2009 at 10:05:17AM -0430, Patrick O'Callaghan wrote: > On Wed, 2009-07-22 at 10:32 -0400, Paul W. Frields wrote: > > On Wed, Jul 22, 2009 at 10:23:46AM -0400, Tom Horsley wrote: > > > On Wed, 22 Jul 2009 15:01:50 +0100 > > > Terry Barnaby wrote: > > > > > > > I know 3D is horribly broken in F11 :( as well as many other things, > > > > but I would have thought that kill -9 should still work ... > > > > > > Not if it is stuck inside the kernel, kill -9 only kills things > > > as they come out of the kernel. > > > > And since the OP indicated he was using the ATI driver, I'd say this > > might be a classic case study in why proprietary, closed-source > > drivers are bad from the user's perspective too, not just the > > distro's. > > Unfortunately a similar situation with the Intel driver is getting no > attention whatsoever. See my reply elsewhere on this thread. I looked in this thread and didn't see it, but maybe the thread was broken a while back. If you have a URL in the archives, much appreciated. -- Paul W. Frieldshttp://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F11: kill -9 doesn't work
On 07/22/2009 03:32 PM, Paul W. Frields wrote: On Wed, Jul 22, 2009 at 10:23:46AM -0400, Tom Horsley wrote: On Wed, 22 Jul 2009 15:01:50 +0100 Terry Barnaby wrote: I know 3D is horribly broken in F11 :( as well as many other things, but I would have thought that kill -9 should still work ... Not if it is stuck inside the kernel, kill -9 only kills things as they come out of the kernel. And since the OP indicated he was using the ATI driver, I'd say this might be a classic case study in why proprietary, closed-source drivers are bad from the user's perspective too, not just the distro's. I am using the standard OpenSource XOrg ATI driver "radeon" with the appropriate DRM/Mesa bits as per a standard F11 release. I have three other systems with F11 on them, some various ATI chipsets and some Intel, all of these have 3D issues mainly major ones with F11. Certainly, in my opinion, F11 not suitable for 3D apps at the moment ... -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F11: kill -9 doesn't work
On Wed, 2009-07-22 at 10:55 -0400, Paul W. Frields wrote: > On Wed, Jul 22, 2009 at 10:05:17AM -0430, Patrick O'Callaghan wrote: > > On Wed, 2009-07-22 at 10:32 -0400, Paul W. Frields wrote: > > > On Wed, Jul 22, 2009 at 10:23:46AM -0400, Tom Horsley wrote: > > > > On Wed, 22 Jul 2009 15:01:50 +0100 > > > > Terry Barnaby wrote: > > > > > > > > > I know 3D is horribly broken in F11 :( as well as many other things, > > > > > but I would have thought that kill -9 should still work ... > > > > > > > > Not if it is stuck inside the kernel, kill -9 only kills things > > > > as they come out of the kernel. > > > > > > And since the OP indicated he was using the ATI driver, I'd say this > > > might be a classic case study in why proprietary, closed-source > > > drivers are bad from the user's perspective too, not just the > > > distro's. > > > > Unfortunately a similar situation with the Intel driver is getting no > > attention whatsoever. See my reply elsewhere on this thread. > > I looked in this thread and didn't see it, but maybe the thread was > broken a while back. If you have a URL in the archives, much > appreciated. https://bugzilla.redhat.com/show_bug.cgi?id=510948 poc -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F11: kill -9 doesn't work
On Wed, 22 Jul 2009 10:53:42 -0400 Paul W. Frields wrote: > system-config-display --verbose --noui --reconfig --set-driver=vesa It was puking during the install, I eventually added the "vesa" kernel option (which perhaps should have been xdriver=vesa, but vesa seemed to work all by itself). -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F11: kill -9 doesn't work
On Wed, 22 Jul 2009 15:58:32 +0100 Terry Barnaby wrote: > Certainly, in my opinion, F11 not suitable for 3D apps at the moment ... As near as I can tell, what it really means is that DRI2 is not ready for prime time yet (except the much hated binary nvidia drivers seem to be very stable :-). -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F11: kill -9 doesn't work
Terry Barnaby wrote: On 07/22/2009 02:07 PM, Paul W. Frields wrote: On Wed, Jul 22, 2009 at 01:02:09PM +0100, Terry Barnaby wrote: Hi, I have noticed on several occasions, that running "kill -9" on a GUI 3D process that is locked at 100% CPU usage (X-Server 100% also) does not work. The 100% lockup I'm sure is due to the currently buggy 3D support (ATI in my case), but I am surprised that I cannot kill either the GUI or X processes. Only a reboot appears to work. Has something changed here ?? If you provide more details, such as the actual process you're running, people might be able to try to duplicate the problem. I've never seen an occasion where kill -9 didn't work, but that doesn't mean it's not possible with some horribly written code. The system in question is a dual Xeon system running Fedora-11 with all updates to 2009-07-22. Graphics board is an ATI RV280 [Radeon 9200 PRO]. I have some applications installed from rpmfusion including paraview. Currently if I run paraview, X goes to 100% and I can no longer operate the system via mouse/keyboard. Via a network login I can "killall -9 X" but that does nothing to X. I have also tried killing paraview in the same way with no effect (possibly after trying to kill X). I hope this is a typo, process "X" is long gone, the X process is called "Xorg" now. I assume you had a finger check and actually killed the real X process. -- Bill Davidsen "We have more to fear from the bungling of the incompetent than from the machinations of the wicked." - from Slashdot -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F11: kill -9 doesn't work
On 07/24/2009 10:40 PM, Bill Davidsen wrote: Terry Barnaby wrote: On 07/22/2009 02:07 PM, Paul W. Frields wrote: On Wed, Jul 22, 2009 at 01:02:09PM +0100, Terry Barnaby wrote: Hi, I have noticed on several occasions, that running "kill -9" on a GUI 3D process that is locked at 100% CPU usage (X-Server 100% also) does not work. The 100% lockup I'm sure is due to the currently buggy 3D support (ATI in my case), but I am surprised that I cannot kill either the GUI or X processes. Only a reboot appears to work. Has something changed here ?? If you provide more details, such as the actual process you're running, people might be able to try to duplicate the problem. I've never seen an occasion where kill -9 didn't work, but that doesn't mean it's not possible with some horribly written code. The system in question is a dual Xeon system running Fedora-11 with all updates to 2009-07-22. Graphics board is an ATI RV280 [Radeon 9200 PRO]. I have some applications installed from rpmfusion including paraview. Currently if I run paraview, X goes to 100% and I can no longer operate the system via mouse/keyboard. Via a network login I can "killall -9 X" but that does nothing to X. I have also tried killing paraview in the same way with no effect (possibly after trying to kill X). I hope this is a typo, process "X" is long gone, the X process is called "Xorg" now. I assume you had a finger check and actually killed the real X process. On F11 "Xorg" is hard linked to "X" and "X" is the program started. So in "ps" listings the XServer process is named "X" and to kill it with "killall" you need to do a "killall -9 X" ... -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F11: kill -9 doesn't work
On Saturday 25 July 2009 08:52:43 Terry Barnaby wrote: > On 07/24/2009 10:40 PM, Bill Davidsen wrote: > > Terry Barnaby wrote: > >> On 07/22/2009 02:07 PM, Paul W. Frields wrote: > >>> On Wed, Jul 22, 2009 at 01:02:09PM +0100, Terry Barnaby wrote: > Hi, > > I have noticed on several occasions, that running "kill -9" on > a GUI 3D process that is locked at 100% CPU usage (X-Server 100% also) > does not work. The 100% lockup I'm sure is due to the currently buggy > 3D support (ATI in my case), but I am surprised that I cannot kill > either the GUI or X processes. Only a reboot appears to work. > > Has something changed here ?? > >>> > >>> If you provide more details, such as the actual process you're > >>> running, people might be able to try to duplicate the problem. I've > >>> never seen an occasion where kill -9 didn't work, but that doesn't > >>> mean it's not possible with some horribly written code. > >> > >> The system in question is a dual Xeon system running Fedora-11 with > >> all updates > >> to 2009-07-22. Graphics board is an ATI RV280 [Radeon 9200 PRO]. > >> I have some applications installed from rpmfusion including paraview. > >> > >> Currently if I run paraview, X goes to 100% and I can no longer > >> operate the system via mouse/keyboard. Via a network login I > >> can "killall -9 X" but that does nothing to X. I have also > >> tried killing paraview in the same way with no effect (possibly > >> after trying to kill X). > > > > I hope this is a typo, process "X" is long gone, the X process is called > > "Xorg" now. I assume you had a finger check and actually killed the real > > X process. > > On F11 "Xorg" is hard linked to "X" and "X" is the program started. > So in "ps" listings the XServer process is named "X" and to kill it > with "killall" you need to do a "killall -9 X" ... Or is it the other way around? :-) I don't have F11 handy here, but on F10: $ ll /usr/bin/X* lrwxrwxrwx 1 root root 4 2009-06-20 04:04 X -> Xorg -rws--x--x 1 root root 1844872 2009-05-25 00:45 Xorg clearly says that X is the link to Xorg, which is the actual binary. Maybe this is different in F11, but I don't see why would it be changed. However, $ ps aux | grep X root 3383 6.3 27.6 1097836 568064 tty1 Ss+ Jul24 132:32 /usr/bin/X - br -nolisten tcp :0 vt1 -auth /var/run/xauth/A:0-4v23CU means that ps lists out the name of the *link* rather than the name of the actual binary. What I would do is prefer kill over killall, like $ kill -9 3383 since PID is always unique. All that said, forcibly killing a locked-up X usually *doesn't* give you back control over the system, since main things that get locked up along with X are graphics card, keyboard and mouse drivers. And those are typically part of the kernel, and cannot be killed just so easy. Also, one cannot expect that -9 killing of X would gracefully reset all these drivers, and my experience is that they remain hosed until a reboot. What I believe the OP issue is about, it is not X that is locked up, it is the radeon driver itself. I don't know if this is a kernel module and if it could be reinitiated with modprobe or something similar, but my experience is that if it locks up, nothing short of reboot can help. HTH, :-) Marko -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F11: kill -9 doesn't work
On 07/25/2009 12:12 PM, Marko Vojinovic wrote: On Saturday 25 July 2009 08:52:43 Terry Barnaby wrote: On 07/24/2009 10:40 PM, Bill Davidsen wrote: Terry Barnaby wrote: On 07/22/2009 02:07 PM, Paul W. Frields wrote: On Wed, Jul 22, 2009 at 01:02:09PM +0100, Terry Barnaby wrote: Hi, I have noticed on several occasions, that running "kill -9" on a GUI 3D process that is locked at 100% CPU usage (X-Server 100% also) does not work. The 100% lockup I'm sure is due to the currently buggy 3D support (ATI in my case), but I am surprised that I cannot kill either the GUI or X processes. Only a reboot appears to work. Has something changed here ?? If you provide more details, such as the actual process you're running, people might be able to try to duplicate the problem. I've never seen an occasion where kill -9 didn't work, but that doesn't mean it's not possible with some horribly written code. The system in question is a dual Xeon system running Fedora-11 with all updates to 2009-07-22. Graphics board is an ATI RV280 [Radeon 9200 PRO]. I have some applications installed from rpmfusion including paraview. Currently if I run paraview, X goes to 100% and I can no longer operate the system via mouse/keyboard. Via a network login I can "killall -9 X" but that does nothing to X. I have also tried killing paraview in the same way with no effect (possibly after trying to kill X). I hope this is a typo, process "X" is long gone, the X process is called "Xorg" now. I assume you had a finger check and actually killed the real X process. On F11 "Xorg" is hard linked to "X" and "X" is the program started. So in "ps" listings the XServer process is named "X" and to kill it with "killall" you need to do a "killall -9 X" ... Or is it the other way around? :-) I don't have F11 handy here, but on F10: $ ll /usr/bin/X* lrwxrwxrwx 1 root root 4 2009-06-20 04:04 X -> Xorg -rws--x--x 1 root root 1844872 2009-05-25 00:45 Xorg clearly says that X is the link to Xorg, which is the actual binary. Maybe this is different in F11, but I don't see why would it be changed. However, $ ps aux | grep X root 3383 6.3 27.6 1097836 568064 tty1 Ss+ Jul24 132:32 /usr/bin/X - br -nolisten tcp :0 vt1 -auth /var/run/xauth/A:0-4v23CU means that ps lists out the name of the *link* rather than the name of the actual binary. What I would do is prefer kill over killall, like $ kill -9 3383 since PID is always unique. All that said, forcibly killing a locked-up X usually *doesn't* give you back control over the system, since main things that get locked up along with X are graphics card, keyboard and mouse drivers. And those are typically part of the kernel, and cannot be killed just so easy. Also, one cannot expect that -9 killing of X would gracefully reset all these drivers, and my experience is that they remain hosed until a reboot. What I believe the OP issue is about, it is not X that is locked up, it is the radeon driver itself. I don't know if this is a kernel module and if it could be reinitiated with modprobe or something similar, but my experience is that if it locks up, nothing short of reboot can help. HTH, :-) Marko Yes, Xorg is the original binary which ever way you name the links :) I know in this case the lock up has probably has happened due to a bug in the Radeon DRI graphics driver, but all kernel code should be written so that a pending kill signal should terminate any loops and thence the process. I don't don't consider it acceptable that you can't kill a process, even when in the kernel and then have to reboot to recover. In my eyes as an old Unix developer standards are slipping ... Cheers Terry -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F11: kill -9 doesn't work
On Sat, 25 Jul 2009 20:57:14 +0100 Terry Barnaby wrote: > In my eyes as an old Unix > developer standards are slipping ... I dunno. Perhaps the oldest code in Unix is the code that generates corefile, and you've never been able to kill -9 that once a process starts coredumping multiple gigabytes over a slow NFS link. I wish they'd put a check in there :-). -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F11: kill -9 doesn't work
On 07/25/2009 09:03 PM, Tom Horsley wrote: On Sat, 25 Jul 2009 20:57:14 +0100 Terry Barnaby wrote: In my eyes as an old Unix developer standards are slipping ... I dunno. Perhaps the oldest code in Unix is the code that generates corefile, and you've never been able to kill -9 that once a process starts coredumping multiple gigabytes over a slow NFS link. I wish they'd put a check in there :-). At least that would finish eventually and the system would continue running :) -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F11: kill -9 doesn't work
On Sat, 25 Jul 2009 22:24:57 +0100 Terry Barnaby wrote: > At least that would finish eventually and the system > would continue running :) I once calculated that it would take 6 weeks for a core dump to finish at the rate it was going. I rebooted the system instead :-). -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F11: kill -9 doesn't work
On Sat, 25 Jul 2009 22:24:57 +0100 Terry Barnaby wrote: > On 07/25/2009 09:03 PM, Tom Horsley wrote: > > On Sat, 25 Jul 2009 20:57:14 +0100 > > Terry Barnaby wrote: > > > >> In my eyes as an old Unix > >> developer standards are slipping ... > > > > I dunno. Perhaps the oldest code in Unix is the code that > > generates corefile, and you've never been able to kill -9 > > that once a process starts coredumping multiple gigabytes > > over a slow NFS link. I wish they'd put a check in there :-). > > > At least that would finish eventually and the system > would continue running :) Linux fixed that one. You can also core dump to dump directory, or through a core dumper helper application. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F11: kill -9 doesn't work
On 07/26/2009 12:46 AM, Alan Cox wrote: On Sat, 25 Jul 2009 22:24:57 +0100 Terry Barnaby wrote: On 07/25/2009 09:03 PM, Tom Horsley wrote: On Sat, 25 Jul 2009 20:57:14 +0100 Terry Barnaby wrote: In my eyes as an old Unix developer standards are slipping ... I dunno. Perhaps the oldest code in Unix is the code that generates corefile, and you've never been able to kill -9 that once a process starts coredumping multiple gigabytes over a slow NFS link. I wish they'd put a check in there :-). At least that would finish eventually and the system would continue running :) Linux fixed that one. You can also core dump to dump directory, or through a core dumper helper application. I must admit the state of the Fedora 11 release has pushed me further to the point of view that we need a sea change in OS/programming design. Things seem to have got over complicated and convoluted with to many undocumented layers and many ways of doing the same thing adding to the complexity. The state of a Linux release to the end user (and developer) does not seem to have improved much in the last 4 years. It seems, to me, that a plateau has been reached, with many changes occurring, but things not improving Mind you it does look visually different (if you like that sort of thing) :) -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
