Maxim Kizub, please disregard my last comment. Instead, given the
regression commit, could you please report this problem following the
instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel to
the appropriate mailing list (TO Zhang Rui, Bob Moore, Lv Zheng, Rafael
J. Wysocki, and Ji
https://bugs.freedesktop.org/show_bug.cgi?id=92049
** Bug watch added: freedesktop.org Bugzilla #92049
https://bugs.freedesktop.org/show_bug.cgi?id=92049
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Maxim Kizub, the issue you are reporting is an upstream one. Could you
please report this problem following the instructions verbatim at
https://wiki.ubuntu.com/Bugs/Upstream/kernel and
http://nouveau.freedesktop.org/wiki/Bugs/ ?
Please provide a direct URL to your report once you have made it so
I was talking about
01:00.0 3D controller: NVIDIA Corporation GK107M
Anyway, here's attached the output of lspci -vvvnn
** Attachment added: "lspci-vvvnn.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1483467/+attachment/4468778/+files/lspci-vvvnn.txt
** Changed in: linux (Ubunt
same with sudo
sudo sh -c "lspci -vvvnn >sudo-lspci-vvvnn.txt"
** Attachment added: "sudo-lspci-vvvnn.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1483467/+attachment/4468789/+files/sudo-lspci-vvvnn.txt
--
You received this bug notification because you are a member of Ubuntu
Bug
Maxim Kizub:
>"and lspci points to NVIDIA card, if I understand correctly:"
:01:00.0 is completely different from 00:02.0. Hence, could you please post
the results of the following terminal command:
lscpi -vvvnn
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You re
"resume-trace" debugging procedure for finding buggy drivers is attached.
It has logged
[0.797599] Magic number: 0:235:725
[0.797601] hash matches
/home/kernel/COD/linux/drivers/base/power/main.c:515
[0.797603] hash matches
/home/kernel/COD/linux/drivers/base/power/main.c:740
[
1. Any way to suspend leads to the same problem with resume - computer hangs.
If screen is set to not lock on resume - then screen is restored, but computer
does not respond. Any way of suspension (gui, pm-suspend and others) blocks in
the same way.
2. Content of /proc/acpi/wakeup is attached
3.
Maxim Kizub, could you please provide the missing information following
https://wiki.ubuntu.com/DebuggingKernelSuspend ?
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Christopher, I've just tested 4.3-rc1 and the result is the same, my
notebook hangs on resume.
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.3-rc1
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are
Maxim Kizub, no problem.
Could you please test 4.3-rc1 precisely and advise to the results?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1483467
Title:
[Acer Aspire V5-573G] suspend/resume failure
Sorry, 4.2 (not 4.3-rc1) and from daily folder (I missed the comment to
not test daily builds).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1483467
Title:
[Acer Aspire V5-573G] suspend/resume fail
Maxim Kizub, to advise, using a WORKAROUND is not considered "kernel-
fixed-upstream".
To clarify, did you test the latest mainline kernel (4.3-rc1), or the
daily folder (which was specifically requested not to test)?
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Tags r
Tested upstream kernel 4.2-unstable and 4.3 daily builds (current) - the
bug is still there (my notebook hangs on resume) and fix (boot kernel
param acpi_osi="!Windows 2013") still helps.
** Tags added: kernel-fixed-upstream kernel-fixed-upstream-4.2 kernel-
fixed-upstream-4.3-daily
** Changed i
Maxim Kizub, could you please test the latest upstream kernel available
from the very top line at the top of the page from
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release
names are irrelevant for testing, and please do not test the daily
folder)? Install instructions are availab
apport information
** Tags added: apport-collected
** Description changed:
It looks to be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1416557 bug (which
was closed because it has expired).
I made kernel bisection (log attached) as was requested in bug 1416557 a
Maxim Kizub, thank you for reporting this and helping make Ubuntu better.
Please execute the following command, as it will automatically gather debugging
information, in a terminal:
apport-collect 1483467
** Package changed: linux-lts-utopic (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubun
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-lts-utopic (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1483467
Ti
18 matches
Mail list logo
