* Julian Elischer <[EMAIL PROTECTED]> [030624 19:01]:
> As of last testing (yesterday my laptop (non SMP) acted the same..
>
> I'm not sure what to suggest.
> can you confirm that you are running the newest of everything..
> (though as far as I know it was ok, even several weeks ago).
I'll re-cv
On Tue, 24 Jun 2003, Julian Elischer wrote:
> I can not duplicate this..
> ON a system (SMP) compiled this afternoon (checked out this afternoon
> too), ksetest responds immediatly to ^C and ^Z in the expected manner.
>
> I am using the csh as my shell and was running as root AND as myself
> for t
On Tue, 24 Jun 2003, Michael Edenfield wrote:
[...]
> thread_start() : 0x84af000 84af000
> kse_create() -> 0
> A*.kse_create() -> -1
> [...]
> *R*.S.*T*.^C^D^Z
>
> (no response on this tty, so I close it).
I can not duplicate this..
ON a system (SMP) compiled this afternoon (checked out this a
If it's duplicatable on recent systems I'll see it on my test system...
thanks..
On Tue, 24 Jun 2003, Michael Edenfield wrote:
> * Julian Elischer <[EMAIL PROTECTED]> [030624 14:47]:
>
> > > I had the same experience just running the KSE test application from
> > > /usr/src/tools last night.
* Julian Elischer <[EMAIL PROTECTED]> [030624 14:47]:
> > I had the same experience just running the KSE test application from
> > /usr/src/tools last night. I ended up with three unkillable ksetest
> > applications and ultimately rebooted to get rid of them. I was
> > planning to report it a
On Tue, 24 Jun 2003, Julian Elischer wrote:
> what about kill -9 887
> ?
> The signals in libKSE are known to be 'delicate'.
> We are working on (well, actually David Xu is working on)
> a set of code to make the signal more robust.
> Hopefully this will fix the problem you are seeing..
Kill -9 d
On Tue, 24 Jun 2003, Michael Edenfield wrote:
> * Wesley Morgan <[EMAIL PROTECTED]> [030624 12:45]:
>
> > Thought I would give libKSE a try making use of the 'libmap.conf' library
> > translations. KDE loads fine, but when I tried to run Firebird I get a
> > process with 3 threads, and it is co
what about kill -9 887
?
The signals in libKSE are known to be 'delicate'.
We are working on (well, actually David Xu is working on)
a set of code to make the signal more robust.
Hopefully this will fix the problem you are seeing..
Any other comments?
Other than not being able to kill it, how as t
* Wesley Morgan <[EMAIL PROTECTED]> [030624 12:45]:
> Thought I would give libKSE a try making use of the 'libmap.conf' library
> translations. KDE loads fine, but when I tried to run Firebird I get a
> process with 3 threads, and it is completely unkillable. It also is
I had the same experience
Thought I would give libKSE a try making use of the 'libmap.conf' library
translations. KDE loads fine, but when I tried to run Firebird I get a
process with 3 threads, and it is completely unkillable. It also is
holding some kind of lock on it's own directory that has caused a couple
of ls's to ha
>
> No. You can't kill a process which is in kernel mode. If it doesn't
> come out, you won't be able to stop it. It seems rather unlikely that
> that's the case here, though.
It seems to me that a process can only suicide after it detects somebody
wants to kill it. Anyway, it is the process
Kris Kennaway wrote:
>
> Nope. I did attach to it with gdb at one point to try and figure out what
> it was running, but because it was compiled w/o debugging symbols I didn't
> get anything out of a backtrace except for something similar to:
You *can* compile it again, just adding the -g and _w
> On Sun, 25 Jul 1999, Amancio Hasty wrote:
>
> > while you are at it try to compile a kernel with symbols ...
>
> I already have (this is my standard practice). What should I do with it
> here?
>
> Kris
>
Well, if the process is not in a zombie state and you can't kill it . We may
need
to e
On Sun, 25 Jul 1999, Amancio Hasty wrote:
> while you are at it try to compile a kernel with symbols ...
I already have (this is my standard practice). What should I do with it
here?
Kris
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the mes
while you are at it try to compile a kernel with symbols ...
--
Amancio Hasty
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Sun, 25 Jul 1999, Greg Lehey wrote:
> > The tcsh listed below that is a zombie of the running kvt.
>
> There aren't any zombies here.
Right, they'd show up as 'Z' in the state field, I'd guess.
> > This seems to be more of a kvt bug than a freebsd bug. :)
>
> I don't see that either. T
On Sunday, 25 July 1999 at 1:21:03 -0500, Kevin Day wrote:
>> On Saturday, 24 July 1999 at 20:51:37 -0500, Kevin Day wrote:
On Sat, 24 Jul 1999, Kevin Day wrote:
> For one, do another 'ps' with the 'l' option, so you can see what it's stuck
> on.
UID PID PPID CPU
> On Saturday, 24 July 1999 at 20:51:37 -0500, Kevin Day wrote:
> >> On Sat, 24 Jul 1999, Kevin Day wrote:
> >>
> >>> For one, do another 'ps' with the 'l' option, so you can see what it's stuck
> >>> on.
> >>
> >> UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND
> >> 10
On Saturday, 24 July 1999 at 20:51:37 -0500, Kevin Day wrote:
>> On Sat, 24 Jul 1999, Kevin Day wrote:
>>
>>> For one, do another 'ps' with the 'l' option, so you can see what it's stuck
>>> on.
>>
>> UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND
>> 1000 1103 1086
On Sat, 24 Jul 1999, Kevin Day wrote:
> > > For one, do another 'ps' with the 'l' option, so you can see what it's stuck
> > > on.
> >
> > UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND
> > 1000 1103 1086 29 75 20 5740 384 - TWN ??0:00.00 (kvt)
> >
> On Sat, 24 Jul 1999, Kevin Day wrote:
>
> > For one, do another 'ps' with the 'l' option, so you can see what it's stuck
> > on.
>
> UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND
> 1000 1103 1086 29 75 20 5740 384 - TWN ??0:00.00 (kvt)
> 1000 11
On Sat, 24 Jul 1999, Kevin Day wrote:
> For one, do another 'ps' with the 'l' option, so you can see what it's stuck
> on.
UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND
1000 1103 1086 29 75 20 5740 384 - TWN ??0:00.00 (kvt)
1000 1109 1103 0 4
> I've got myself two processes which can't be gotten rid of by SIGKILL:
>
> kkenn 92724 32.0 0.8 5736 356 ?? RN6:25PM 136:52.96 kvt -T Terminal -
> kkenn 1103 0.0 0.0 5740 388 ?? TWN - 0:00.00 (kvt)
>
> (kvt is the KDE 1.1.1 xterm)
>
> I am able to trigger this by at
I've got myself two processes which can't be gotten rid of by SIGKILL:
kkenn 92724 32.0 0.8 5736 356 ?? RN6:25PM 136:52.96 kvt -T Terminal -
kkenn 1103 0.0 0.0 5740 388 ?? TWN - 0:00.00 (kvt)
(kvt is the KDE 1.1.1 xterm)
I am able to trigger this by attempting to past
24 matches
Mail list logo
