kernel-packages team mailing list archive

[Ronan Jouchet <131094@xxxxxxxxxxxxxxxxxx>]

Adam Niedling wrote:
  "I'm just somebody who is affected by this bug which you are trying to close in a very crafty way. It's not a speculation that you're doing this all the time, you did this to 2 or 3 of my own bugs. I'm getting tired of you pasting the same text everywhere. Maybe you're pasting it to hundreds of bugs. There is no effort in pasting some text. However you are asking people to do a lot of work which takes huge effort. Most of the time it's completely unnecessary cause no one has made anything to fix the issue.
  "Hey! No developer has ever touched this bug but let's ask the poor user who is suffering from it a ton of questions and half day of working and testing the latest mainline kernel maybe he won't be able to do it or just simply has no idea how to do it so we can close this completely valid bug! And let's just ignore the bug even if the poor user does all that work ha ha ha..... Oh yeah and make sure to paste lots of links about etiquette and what not so I will look official even though I'm not working for Canonical I'm just messing around with people's bugs."

>> I can definitely recognize some of the behavior described here by
Adam, and also suffered from it in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/908691 . In my case
I could even pinpoint a specific mainline commit, but my inability to do
the non-mainline git bisect requested by M. Penalver meant my request
fell in deaf ears. I closed my own bug diplomatically, but it was
extremely disappointing experience to see so little response for all the
effort I put.

I understand Canonical must have lots of bug triage to do, but I'd too
love a little more humanity in processing them. Canned answers and
strict protocol don't show a lot of empathy, and don't echo into much
user love.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/131094

Title:
  Heavy Disk I/O harms desktop responsiveness

Status in The Linux Kernel:
  Fix Released
Status in The Linux Mint Distribution:
  New
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: linux-source-2.6.22

  When compared with 2.6.15 in feisty, heavy disk I/O causes increased
  iowait times and affects desktop responsiveness in 2.6.22

  this appears to be a regression from 2.6.15 where iowait is much lower
  and desktop responsiveness is unaffected with the same I/O load

  Easy to reproduce with tracker - index the same set of files with
  2.6.15 kernel and 2.6.22 kernel and the difference in desktop
  responsiveness is massive

  I have not confirmed if a non-tracker process which does heavy disk
  i/o (especially writing) replicates this yet - will do further
  investigation soon

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/131094/+subscriptions