Micro freezes on Lenovo IdeaPad Y560p

[Osman Çaylak]

There are micro freezes on system. This don't allow watching a video or playing a game.

Linux 3.11.0-13
There are micro freezes.

CPU0 is always ~85% htop is not showing anything using cpu that much but top is showing kworker. (top output: http://pastebin.com/jz9jwkK0 )

Linux 3.8.13-03081306
There are micro freezes. After adding "noapic" on grub and reinstalling fglrx(while using this kernel) micro freezes disappear.

CPU problem on above exists.

Linux 3.12.0-031200
This is latest mainline kernel. Micro freezes exits.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-13-generic 3.11.0-13.20
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
Uname: Linux 3.11.0-13-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: muhammed 3437 F.... pulseaudio
 /dev/snd/controlC0: muhammed 3437 F.... pulseaudio
Date: Wed Nov 20 11:55:40 2013
HibernationDevice: RESUME=UUID=94297800-4e8e-442b-aa03-afe4303ce50e
InstallationDate: Installed on 2012-07-18 (489 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MachineType: LENOVO IdeaPad Y560p
MarkForUpload: True
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=40951847-faf8-47f0-906e-a43e1accfe5e ro elevator=deadline
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-13-generic N/A
 linux-backports-modules-3.11.0-13-generic N/A
 linux-firmware 1.116
SourcePackage: linux
UpgradeStatus: Upgraded to saucy on 2013-10-19 (32 days ago)
dmi.bios.date: 05/22/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 3FCN22WW
dmi.board.name: KL3
dmi.board.vendor: LENOVO
dmi.board.version: Rev 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Rev 1.0
dmi.modalias: dmi:bvnLENOVO:bvr3FCN22WW:bd05/22/2012:svnLENOVO:pnIdeaPadY560p:pvrRev1.0:rvnLENOVO:rnKL3:rvrRev1.0:cvnLENOVO:ct10:cvrRev1.0:
dmi.product.name: IdeaPad Y560p
dmi.product.version: Rev 1.0
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Osman Çaylak, just to confirm the issue is reproducible on the mainline kernel http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-trusty/ correct?

Also, did this issue not occur in a release prior to Saucy?

[Osman Çaylak (osmancik)]

Yes this is correct: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-trusty/

This issue occurs on previous releases.

[penalvch (penalvch)]

Osman Çaylak, did this problem not occur on a release prior to Saucy?

[Osman Çaylak (osmancik)]

It is occuring from 11.10. Haven't tested any previous.

[Osman Çaylak (osmancik)]

No freezes. Installed fglrx from jockey. After restart it can't find my graphics card. There are errors like unknown graphics card bios id.

[Osman Çaylak (osmancik)]

How can I install Radeon drivers? I only clicked enable on jockey for fglrx.

[Osman Çaylak (osmancik)]

Reinstalled lucid. Didn't installed anything or any update. lspci -nvv output is:

01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Device [1002:68c0]
 Subsystem: Lenovo Device [17aa:3978]
 Flags: bus master, fast devsel, latency 0, IRQ 16
 Memory at d0000000 (64-bit, prefetchable) [size=256M]
 Memory at cfee0000 (64-bit, non-prefetchable) [size=128K]
 I/O ports at 2000 [size=256]
 [virtual] Expansion ROM at cfe00000 [disabled] [size=128K]
 Capabilities: [50] Power Management version 3
 Capabilities: [58] Express Legacy Endpoint, MSI 00
 Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
 Capabilities: [100] Vendor Specific Information <?>

I think my graphics card is unknown for 2010's drivers.

[penalvch (penalvch)]

Osman Çaylak, would either Maverick or Natty provided a testable environment?

[Osman Çaylak (osmancik)]

Installed 10.10
Kernel driver in use: radeon
There are some messy screens while system start and shutdown. Desktop is clear. No freezes. I can't test fglrx because repos aren't available. There is an error like Ubuntu 10.10 not supported any more.

[penalvch (penalvch)]

Osman Çaylak, the next step is to fully commit bisect from Maverick to Oneiric, in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

[Osman Çaylak (osmancik)]

The offending commit is in somewhere between v2.6.35 and v2.6.39. I have used these commands.

git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
cd linux
git checkout v2.6.35
git bisect start
git bisect good v2.6.35
git bisect bad v2.6.39
cp /boot/config-`uname -r` .config
yes '' | make oldconfig
make menuconfig
make clean
make -j `getconf _NPROCESSORS_ONLN` deb-pkg LOCALVERSION=-custom

Finally the .deb files did not created. Last lines of the output:

  CC [M] fs/xfs/linux-2.6/xfs_super.o
  CC [M] fs/xfs/linux-2.6/xfs_sync.o
fs/xfs/linux-2.6/xfs_sync.c: In function ‘xfs_sync_worker’:
fs/xfs/linux-2.6/xfs_sync.c:475:7: warning: variable ‘error’ set but not used [-Wunused-but-set-variable]
  int error;
       ^
  CC [M] fs/xfs/linux-2.6/xfs_xattr.o
  CC [M] fs/xfs/support/debug.o
  CC [M] fs/xfs/support/uuid.o
  LD [M] fs/xfs/xfs.o
  LD fs/built-in.o
make[1]: *** [deb-pkg] Hata 2
make: *** [deb-pkg] Hata 2

What to do?

[penalvch (penalvch)]

Osman Çaylak, sometimes kernels don't build on certain points. The best way to go is to change the commit one is building against. Try narrowing the git bisect to:
git bisect bad v2.6.38

[Osman Çaylak (osmancik)]

Same problem again.

I am on 13.10 while compiling kernel. Because I can't install prerequisites for compiling kernel on 10.10. Repos aren't available.

[Joseph Salisbury (jsalisbury)]

The v3.13-rc1 kernel is now available. Can you give this kernel a test before we continue the bisect?

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc1-trusty/

[Osman Çaylak (osmancik)]

Thanks for your support Joseph Salisbury. I have tested v3.13-rc1-trusty. Not fixing my problem.

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

[penalvch (penalvch)]

Osman Çaylak, as a potential WORKAROUND, if you remove elevator=deadline from your kernel boot parameters, and only have the parameters that came by default with your install, does it change anything?

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]