On Apr 17, 2015 4:18 PM, "jd1008" <jd1008@gmail.com> wrote:
>
>
>
> On 04/17/2015 03:05 PM, Rick Stevens wrote:
>>
>> On 04/17/2015 12:55 PM, jd1008 wrote:
>>>
>>> Would appreciate some timelines on this problem.
>>
>>
>> If you've filed a BZ on it, there should be activity on that entry.
>
> Sorry Rick,
> I must not be the only one experiencing this problem.
> I am certain many others are having the same problem.
> My exprience with filing bugs with bugzilla.redhat.com
> and with bugzilla.kernel.com (upstream) has been very
> unrewarding and unproductive, and problems I report
> have largely gone unresolved or dismissed as either
> will not fix, insufficient information, or unreproducible,
> or duplicates of some other bugs files long before I files mine.
> When I read the supposed bug for which mine was deemed
> a duplicate, I have seen the problem is not what I
> was reporting or was only slightly similar, with different
> symptoms and side effects.
> So, I have gotten very weary of this B*11**it.
>
>
> --

If you're having trouble providing requested information or sufficient context for a bug, the qa list (test@lists.fp.o) might be a good place to ask for help.  Also remember that different symptoms may share and underlying cause, wrt duplicate marked bugs. 

Basically, problems that are not reported are less likely to be fixed.  What you do with that is up to you.  The best way to have an answer to your question is to file a bug and see it through, or if it's a common problem, find a bug already filed and CC yourself.  You could ask for help here in remedying the issue, and determining if configuration or code are at fault. 

If you don't want to file a bug, fine; if you don't want to continue the discussion about configuration, that's fine too.  Do consider the audience you sent this mail to, though.  It isn't the power management subsystem developer community, and even if it were, I don't think what you're doing would be motivating.

--Pete