kernel-packages team mailing list archive

[Sergio Callegari <sergio.callegari@xxxxxxxxx>]

I have tried to look into the issue, but I am encountering a situation
that is extremely weird. Hence I hope that someone might be able to
help.

The latest kernel that works from the ubuntu mainline ppa repo is 3.16.7-031607_3.16.7-031607.201410301735
Kernel 3.17.0-031700_3.17.0-031700.201410060605 already shows the issue.

However, if I try to compile myself 3.17 from Linus following the
instructions in https://wiki.ubuntu.com/KernelTeam/GitKernelBuild

I get:

- a kernel that is clearly completely different in configuration from that in the ubuntu ppa mainline (different package names, much much larger kernel image package) and, most important,
- a kernel that apparently does not show the IOWAIT issue.

At the same time, I am recently experiencing all sort of issues with
nvidia 304 and kde plasma 5 causing continuous hangs in plasmashell even
if compositing is off, so it is quite difficult to properly test for me.

-- 
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/1451277

Title:
  Extremely high IOWait and processes hungs after utopic->vivid upgrade
  with Iomega Zip drive (IDE)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Kubuntu, 64 bit AMD Phenom2 machine with 4 cores, and old (Geoforge 7025) Nvidia graphics.
  Using LVM. Machine also has a 2 disk software raid (mirroring).

  The machine was working fine before the upgrade, now it is almost
  impossible to use it... I see Wait in Top always above 60%; in dmesg
  after a few minutes that the machine is up even if the machine does
  nothing. I see hung processes (typically vgs, but occasionally also
  others).  LVM related commands (e.g. lvdisplay) almost always hung at
  the terminal. I also see in ps some kernel workers almost constantly
  stuck in D state. Also, the machine takes ages to shutdown.

  Issue remains there also if I disable X (switch off the X login
  manager, sddm) and check at the console.

  Sorry I cannot provide details with apport, but the machine has been
  switched off and I will not be able to take it up again before a few
  days from now.

  The symptom I am observing may also be a sign of failing hardware, so
  please leave the bug as unconfirmed until I make some more tests or
  someone provide details on similar issues. In the meantime I would
  like to see if others are experiencing a similar serious issue. Is
  there anything specific that has changed between utopic and vivid, I
  should look into?

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