kern/164705: inability to terminate process in D state
avg at FreeBSD.org
Thu Feb 2 18:10:31 UTC 2012
on 02/02/2012 20:02 Коньков Евгений said the following:
> Здравствуйте, Andriy.
> Вы писали 2 февраля 2012 г., 15:04:04:
> AG> on 02/02/2012 12:10 Eugene M. Zheganin said the following:
>>> On 02.02.2012 16:00, Andriy Gapon wrote:
>>>> on 02/02/2012 11:37 Коньков Евгений said the following:
>>>>> why close? keep the problem open until resolve.
>>>> Resolve exactly what?
>>> Yeah, someone's enormous ego is not exactly a FreeBSD problem.
>>> I can see it's grown up to an unresolvable size.
> AG> Anything on the technical side you might want to add?
> people with sufficiant knowledge looking through opened PRs maybe will
> notice this, take attention of it and fix.
> I do not have any knowledge of kernel design I just report a PR
> and if this is really problem it must be opened until fix. IMHO.
> this PR and PR bin/164526 may be related and this one
> may be closed as 'dublicate' but not as:
> 'this problem can not be resolved'
PR 164526 reports a concrete problem that can be diagnosed and hopefully fixed.
This PR is equivalent to "when FreeBSD has bugs it sucks", only about a sub-class
of bugs with some specific symptoms (process being stuck and unkillable). There
could be different actual underlying bugs and bug classes - driver bugs,
deadlocks, etc. Hence, this PR can not be diagnosed and fixed.
A new (concrete/useful) PR can be opened at any time, it's a low cost operation.
> thank you about your explanation of "bad and good news"
More information about the freebsd-bugs