Yes, I have reported several bugs, some of which actually got fixed, but
not because I reported them. 1800 bugs per week is a problem. Some FOSS
developers release buggy apps and hope someone else will fix them. Some
like to wait for the next release. Some are thankfully very
conscientious, like th
No, we are few people against too much bugs and majority of us is not payed.
We do this in free time, and on first obviously we take a look at our package
that we have chose to follow.
On average, over 1,800 bugs are filed every week with more than 600,000 bugs
filed so far. The Bug Squad is alwa
It was likely the kernel scheduler. I did not say this because I did not trust
my judgment.
So your rule is to ignore bugs without a package assigned? And you don't even
ask? Bad rule.
On 08/29/2010 12:35 AM, Fabio Marconi wrote:
> Hello kornelix
> I admit that is not easy to understand, but if
Hello kornelix
I admit that is not easy to understand, but if there was un update that solves
a bug, here in Launchpad we cannot know the root cause, only developers know
that.
Is not the bug that is invalid, but the report, actually solved.
Launchpad is the media to transmit a bug to the right d
That was not my question. Something was fixed and now the problem is gone.
How does that translate into a status "invalid"? I don't think anyone
took a serious look anyway, so it does not matter.
On 08/28/2010 06:35 PM, Fabio Marconi wrote:
> Hello kornelix
> You said:
> The problem appears to be
Hello kornelix
You said:
The problem appears to be gone or almost gone in Lucid.
If you don't agree, simply change the status.
you can manage the status of your own bugs by clicking on the current status in
the yellow line and then choosing a new status in the revealed drop down box.
Fabio
--
e
Why did you change the status to "invalid"? Something in the kernel was
clearly changed to make the improvements noted, we just don't know what.
On 08/27/2010 10:45 PM, Fabio Marconi wrote:
> Thanks for the reply
> This bug report is being closed due to your last comment regarding this being
> f
On 08/27/2010 03:41 PM, Fabio Marconi wrote:
> Hello
> Is this problem present with the latest updated Karmic's or Lucid's packages?
> Thanks in advance
> Fabio
>
> ** Changed in: ubuntu
> Status: New => Incomplete
>
The problem appears to be gone or almost gone in Lucid. I ran benchmark
Thanks for the reply
This bug report is being closed due to your last comment regarding this being
fixed with an update. For future reference you can manage the status of your
own bugs by clicking on the current status in the yellow line and then choosing
a new status in the revealed drop down b
Hello
Is this problem present with the latest updated Karmic's or Lucid's packages?
Thanks in advance
Fabio
** Changed in: ubuntu
Status: New => Incomplete
--
erratic thread scheduling, kernel 2.6.31
https://bugs.launchpad.net/bugs/459628
You received this bug notification because you are
** Tags added: karmic
** Tags added: regression-release
--
erratic thread scheduling, kernel 2.6.31
https://bugs.launchpad.net/bugs/459628
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ub
Maybe this kernel is scheduling a hyper-thread CPU even when a "regular"
CPU is available. This would cause thread performance to go down about
50%. This would not account for the variance in measured CPU time.
--
erratic thread scheduling, kernel 2.6.31
https://bugs.launchpad.net/bugs/459628
You
Information I should have included:
The tests were done on a processor with 4 cores, hence the CPU time
for 4 threads can be 400% of the elapsed time.
--
erratic thread scheduling, kernel 2.6.31
https://bugs.launchpad.net/bugs/459628
You received this bug notification because you are a member o
I wish your bug report system would not mangle formatted inputs.
I have added the entire report as an attachment.
Please view with fixed-width font (e.g. gedit).
** Attachment added: "kernel bug"
http://launchpadlibrarian.net/34311813/kernel%20bug
--
erratic thread scheduling, kernel 2.6.3
14 matches
Mail list logo
