** Changed in: linux
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386695
Title:
[3.16.0-23] Resume from suspend/hibernation, GPU lock - possible
This bug was fixed in the package linux - 3.16.0-28.38
---
linux (3.16.0-28.38) utopic; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1401966
[ Upstream Kernel Changes ]
* net: skb_fclone_busy() needs to detect orphaned skb
- LP: #1401079
-- Brad Figg
This bug was fixed in the package linux - 3.16.0-26.35
---
linux (3.16.0-26.35) utopic; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1398118
[ Upstream Kernel Changes ]
* Revert drm/nouveau: punt fbcon resume out to a workqueue
* Revert drm/nouveau/kms:
For total clarity. The fixes here were not verified (as they did not
fix the issue possibly after a BIOS update) and are therefore reverted
in the kernel. When this closed shortly on release of the reverted
kernel, that will be an error, and the bug will need reopening. We will
retest against
Andy Whitcroft, thanks for your comment. As per the original reporter
Nik.Th. the kernel that fixes this problem is
http://people.canonical.com/~apw/lp1386695-utopic/ , both before and
after the BIOS update. So, while it's unfortunate a BIOS update didn't
fix this issue, it certainly didn't
more/less = more or less of the intending fix commits released recently
in Utopic Proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386695
Title:
[3.16.0-23] Resume from suspend/hibernation,
Sorry but I cannot confirm the fix. The latest kernel available
(3.16.0-25-33) is not working. Of course the -proposed repositories are
always enabled in my testing system.
I really don't know what happened, but I can assume that the latest BIOS
update changed something. Yes, I have updated my
Nik.Th., just to advise, as per
https://launchpad.net/ubuntu/+source/linux the Proposed kernel is
3.16.0-26.34 since 2014-11-25. If you have 3.16.0-25-33, then either you
didn't setup the Proposed repository correctly, or you have the software
pinned so that you aren't pulling down the Proposed
Nik.Th., could you please provide the output of the following terminal command:
sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date
** Tags added: bios-outdated-17.a
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@penalvch I just got the latest Kernel (linux-image-3.16.0-26.34) but
unfortunately it does not work either.
The only kernel that still works is listed in comment #33 above.
I have attached the results.
** Attachment added: dmidecode-biosver.txt
** Tags removed: bios-outdated-17.a performing-bisect
** Tags added: latest-bios-v17.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386695
Title:
[3.16.0-23] Resume from suspend/hibernation, GPU
Not Fix Released as per
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386695/comments/33
and
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386695/comments/36
. Hence, this bug report will not be closed as advised in
** Tags removed: reverse-bisect-done
** Tags added: bisect-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386695
Title:
[3.16.0-23] Resume from suspend/hibernation, GPU lock - possible
As per
https://bugs.launchpad.net/ubuntu/vivid/+source/linux/+bug/1386695/comments/37
.
** Changed in: linux (Ubuntu Utopic)
Status: Fix Committed = Triaged
** Tags removed: bisect-done
** Tags added: reverse-bisect-done
** Tags removed: verification-needed-utopic
** Tags added:
** Changed in: linux (Ubuntu Utopic)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386695
Title:
[3.16.0-23] Resume from suspend/hibernation, GPU lock - possible
@Christopher M. Penalver
sorry, I'll let you hande the tags, it seems we edit them at the same time.
Please fix any errors.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386695
Title:
** Tags removed: bisect-done
** Tags added: reverse-bisect-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386695
Title:
[3.16.0-23] Resume from suspend/hibernation, GPU lock - possible
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.
If verification is not done by 5 working days from
** Branch linked: lp:ubuntu/trusty-proposed/linux-lts-utopic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386695
Title:
[3.16.0-23] Resume from suspend/hibernation, GPU lock - possible
** Also affects: linux (Ubuntu Vivid)
Importance: Medium
Assignee: Andy Whitcroft (apw)
Status: Triaged
** Also affects: linux (Ubuntu Utopic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Utopic)
Status: New = Incomplete
** Changed in: linux
After another exhausting searching and testing, and again with the
**priceless** help of @apw in IRC,
I(we) may have detect the three responsible commits for the fix.
Probably they are three and not one, and certainly the MERGE in which I
refer on the above comment #27, it cannot be merged into
After another exhausting searching and testing, and again with the
**priceless** help of @apw in IRC,
I(we) may have detect the three commits which are responsible for the
fix. Yes, probably they are three and not one, and certainly the MERGE
in which I refer on the above comment #27, it cannot
** Description changed:
- 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).
+ I'm testing the new development branch (Vivid Vervet), which currently has
the Utopic kernel
Ok I looked at backporting these three commits. To cut a long story
short one of these is not needed because it is only applicable at the
higher level (though needed there) and one is actually for dpms issues.
This leaves the commit below:
commit 63621dafc8e140afdfa12c8deadb41af818e455d
git bisect looks for a commit which introduces an issue. You are trying
to find a commit which _fixes_ and issue. This makes it a reverse
bisect, and for reasons that means you have to use good and bad
backwards, non-intuitive and confusing I know. In your log you seem to
have correctly swapped
** Tags removed: needs-reverse-bisect
** Tags added: unable-to-reverse-bisect
** Tags added: cherry-pick
** Changed in: linux (Ubuntu)
Status: Incomplete = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Would you like me to assist you with the reverse bisect? I can perform
the bisect and build the test kernel, which you can use to test.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386695
Title:
** Tags added: performing-bisect
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386695
Title:
[3.16.0-23] Resume from suspend/hibernation, GPU lock - possible
regression
To manage notifications
@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
** Tags removed: unable-to-reverse-bisect
** Tags added: bisect-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386695
Title:
[3.16.0-23] Resume from suspend/hibernation, GPU lock - possible
Ok, further searching showed that the commit that actually solves this
problem is a merge branch 'for-linus' .
Specifically this one:
[7d1419f30cc5106196e54a282d7e115e698c95f6] Merge branch 'for-linus' of
git://git.samba.org/sfrench/cifs-2.6
I will say the truth that this one tricked me a lot.
It seems I'm unable to narrow down the commit.
I can assure (because I have tested this twice) the last bad kernel is
3.17.0-rc7-utopic (http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.17-rc7-utopic/)
and the first good one
3.17.0-utopic (http://kernel.ubuntu.com/~kernel-
It seems I'm unable to narrow down the commit.
I can assure (because I have tested this twice) the last bad kernel is
3.17.0-rc7-utopic (http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.17-rc7-utopic/)
and the first good one
3.17.0-utopic (http://kernel.ubuntu.com/~kernel-
Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v3.13 stable kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel
Actually could you test the latest 3.16 upstream stable kernel, which is 3.13.6:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16.6-utopic/
The 3.13 kernel would be for Trusty, but you reported this against
Utopic. Sorry for the confusion.
** Changed in: linux (Ubuntu)
Status:
Unfortunately it does not work with 3.16.6 . I've tested with and
without the nouveau.nofbaccel=1 parameter, but in both cases I had the
same behavior as of 3.16.4 (Ubuntu 3.16.0-23-generic).
I'm attaching the part of the log with the hibernation and resume
messages.
** Attachment added:
I really cannot spot any difference in logs, but maybe it's just me.
Here is the log from the 3.17.1 kernel, where resume works as it should.
** Attachment added: 3.17.1-resume-succeeded.txt
Nik. Th. the next step is to fully reverse commit bisect the kernel in
order to identify the fix commit. Could you please do this following
https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F
?
** Tags removed: kernel-bug-fixed-upstream
** Tags added:
Launchpad has imported 14 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=81136.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
39 matches
Mail list logo
