@jsalisbury thanks for offering assistance and willing to help.
I've finished the process of reverse bisecting and I have spotted some good(bad) commits. With the **priceless** help of @apw in IRC I have learned the correct procedure of reverse bisecting (it was a real learning curve!) Here is the new log git bisect start # good: [fe82dcec644244676d55a1384c958d5f67979adb] Linux 3.17-rc7 git bisect good fe82dcec644244676d55a1384c958d5f67979adb # bad: [bfe01a5ba2490f299e1d2d5508cbbbadd897bbe9] Linux 3.17 git bisect bad bfe01a5ba2490f299e1d2d5508cbbbadd897bbe9 # good: [abc40bd2eeb77eb7c2effcaf63154aad929a1d5f] mm: numa: Do not mark PTEs pte_numa when splitting huge pages git bisect good abc40bd2eeb77eb7c2effcaf63154aad929a1d5f # good: [58586869599f6bb38aeca71a847cd77bfea74808] Merge tag 'pm+acpi-3.17-final' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm git bisect good 58586869599f6bb38aeca71a847cd77bfea74808 # bad: [7d1419f30cc5106196e54a282d7e115e698c95f6] Merge branch 'for-linus' of git://git.samba.org/sfrench/cifs-2.6 git bisect bad 7d1419f30cc5106196e54a282d7e115e698c95f6 # bad: [eee0815dabbdd7d584bea8275f5758d25c97cb9b] Merge tag 'drm-intel-fixes-2014-10-02' of git://anongit.freedesktop.org/drm-intel into drm-fixes git bisect bad eee0815dabbdd7d584bea8275f5758d25c97cb9b # bad: [634ffcccfbe59d77652804e1beb415d3329b1bc6] drm/nouveau: punt fbcon resume out to a workqueue git bisect bad 634ffcccfbe59d77652804e1beb415d3329b1bc6 # bad: [f2f9a2cbaf019481feefe231f996d3602612fa99] drm/nouveau: fix regression on original nv50 board git bisect bad f2f9a2cbaf019481feefe231f996d3602612fa99 # bad: [5838ae610ff36777b8fce6f353c2417980c1a1fa] drm/nv50/disp: fix dpms regression on certain boards git bisect bad 5838ae610ff36777b8fce6f353c2417980c1a1fa # first bad commit: [5838ae610ff36777b8fce6f353c2417980c1a1fa] drm/nv50/disp: fix dpms regression on certain boards Now I have to test the commits beginning by the first bad (good) and building-installing-testing the kernel(s). But is it possible that in a case, 2 or 3 commits combined would be needed, in order to fix a problem? The only commits relevant with my problem, as I can understand, are 3 (drm/nouveau/fbcon /nv50 /nv50/disp). But maybe I need to combine them all together in order to fix the resume problem, I'm not sure. -- 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/1386695 Title: [3.16.0-23] Resume from suspend/hibernation, GPU lock - possible regression Status in The Linux Kernel: Confirmed Status in “linux” package in Ubuntu: Triaged Bug description: I'm testing the new development branch (Vivid Vervet), which currently has the Utopic kernel 3.16.0-23-generic installed (proposed repositories are enabled). This problem might be a regression, and it has been reported upstream: https://bugs.freedesktop.org/show_bug.cgi?id=81136 Problem: When I try to resume from hibernation the screen hangs and the GPU is locked. It cannot load the graphics properly. Testing: Unloading or blacklisting the nouveau driver and perform the following test, seems to indicate that the problem is nouveau: # echo platform > /sys/power/disk # echo devices > /sys/power/pm_test # echo disk > /sys/power/state Mainline: The problem seems to be fixed in latest stable mainline kernel, for now 3.17.1-031701-generic (Utopic). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.16.0-23-generic 3.16.0-23.31 [modified: boot/vmlinuz-3.16.0-23-generic] ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC3: nikos 1690 F.... pulseaudio /dev/snd/controlC1: nikos 1690 F.... pulseaudio /dev/snd/controlC2: nikos 1690 F.... pulseaudio /dev/snd/controlC0: nikos 1690 F.... pulseaudio CurrentDesktop: Unity Date: Tue Oct 28 15:24:09 2014 HibernationDevice: RESUME=UUID=f0688f3d-9938-4cb3-b79e-7c67f7593350 InstallationDate: Installed on 2014-10-24 (4 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IwConfig: eth0 no wireless extensions. lo no wireless extensions. MachineType: MSI MS-7623 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=170bb898-7aa9-4678-8e80-58a445647f93 ro resume=/dev/disk/by-uuid/f0688f3d-9938-4cb3-b79e-7c67f7593350 RelatedPackageVersions: linux-restricted-modules-3.16.0-23-generic N/A linux-backports-modules-3.16.0-23-generic N/A linux-firmware 1.138 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V17.9 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 880GMA-E45 (MS-7623) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV17.9:bd12/06/2010:svnMSI:pnMS-7623:pvr3.0:rvnMSI:rn880GMA-E45(MS-7623):rvr3.0:cvnMSI:ct3:cvr3.0: dmi.product.name: MS-7623 dmi.product.version: 3.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1386695/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
