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 BIO
@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"
https://bugs.launchpad.net/linux/+bug/13866
** Tags removed: reverse-bisect-done
** Tags added: bisect-done
--
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 - poss
@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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/138669
Public bug reported:
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=
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: "3.1
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"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386695/+attachment/4247637/+files/3.17.1-resu
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-
ppa/mainline/v3.17-u
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-
ppa/mainline/v3.17-u
@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 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 -
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. I
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 Ub
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 3.16.0-23-gene
If the bluetooth is working and recognizes your phone, then probably
this bug should be reported against nautilus (browsing files via
bluetooth.)
** Package changed: bluez (Ubuntu) => nautilus (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is su
Hello,
it seems a bit strange because the CurrentDmesg.txt (comment #9) doesn't
show the problem. Also I have Trusty Tahr installed and a WD USB3.0
external HDD and I haven't such problems. Either I connect it to USB2.0
or 3.0 port.
It would be helpful if you provide additional information during
Hello,
have you tried the latest kernel ?
These are my results from the fresh updated Trusty Tahr. (kernel-3.12.0-4)
** Attachment added: "dmesg-usb3.0-success-kernel-3.12.0-4.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1254261/+attachment/3915510/+files/dmesg-usb3.0-success-
Can you please confirm that the filesystem of that disk is in a good
condition ?
If it's NTFS then it would be better to check it with a Windows tool.
If it's linux filesystem (e.g. ext4) the you can use fsck tool.
Best Regards
NikTh
** Changed in: linux (Ubuntu)
Status: Confirmed =>
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs
Hello,
it would be good for the bug's life-cycle to open a report upstream in
order to inform the USB 3.0 developers
https://bugzilla.kernel.org/
Add a link here (when this done) and also add a link in the upstream
report to point in this bug report.
My disk (comment #22) it's NTFS filesystem,
*** This bug is a duplicate of bug 1253498 ***
https://bugs.launchpad.net/bugs/1253498
** This bug has been marked a duplicate of bug 1253498
package linux-image-3.12.0-3-generic 3.12.0-3.8 failed to install/upgrade:
intentando sobreescribir
`/lib/modules/3.12.0-3-generic/kernel/net/openv
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=65631
Importance: Unknown
Status: Unknown
--
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/1254261
Title:
Thank you for taking the time to report this bug and helping to make Ubuntu
better.
Could you please test the latest upstream kernel available (not the daily
folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow
additional upstream developers to examine the issue. Once y
24 matches
Mail list logo
