v4.8.0-42 passed
uname -a
Linux kjell-Aspire-V5-551G 4.8.0-42-generic #45-Ubuntu SMP Wed Mar 8 20:06:06
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659340
I use Ubuntu 16.10. v4.8.0-41 is the only kernel that has so far been
delivered by Update Manager after 4.8.0-40.
Right now I'll just wait and see what happens. v4.10-rc7 and the newer
4.10.1 from the upstream kernels archive work. So I guess Linux kernels
from Update Manager will start working whe
v4.8.0-40 passed
v4.8.0-41 failed !!!
I just got the 4.8.0-41 version of Ubuntu's Linux kernel. It does not work.
The bug that was fixed in 4.8.0-40 re-appears in 4.8.0-41. At least the
symptom is the same.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
v4.8.0-40 passed
Great! The kernel in yakkety-proposed works.
uname -a
Linux kjell-Aspire-V5-551G 4.8.0-40-generic #43-Ubuntu SMP Thu Feb 23 16:01:19
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
** Tags removed: verification-needed-yakkety
** Tags added: verification-done-yakkety
--
You received
v4.10-rc7 passed
uname -a
Linux kjell-Aspire-V5-551G 4.10.0-041000rc7-generic #201702051931 SMP Mon Feb 6
00:33:39 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
v4.8.0-34.36-lp1659340Patched passed
uname -a
Linux kjell-Aspire-V5-551G 4.8.0-34-generic #36~lp1659340Patched SMP Thu Feb 2
21:04:45 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Correction:
v4.8.0-34.36-commit129766708reverted passed
Yes, it was linux-signed-image-4.8.0-34-generic that made the test fail.
When I temporarily changed
linux /boot/vmlinuz-4.8.0-34-generic.efi.signed .
to
linux /boot/vmlinuz-4.8.0-34-generic ..
in grub's startup script, the test pa
v4.8-rc7-201702011104 passed
v4.8.0-34.36-commit129766708reverted failed
For the first time my result is not the same as lotek's. I installed the same
4 packages. Do you think it's worthwhile to uninstall and then reinstall?
"dpkg -l" reports that there is also a linux-signed-image-4.8.0-34-generi
v4.8-rc7-201701311339 failed
v4.8-rc7-201701311526 failed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659340
Title:
Linux kernel 4.8 hangs at boot up
To manage notifications about this bug go to
v4.8-rc7-201701311126 failed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659340
Title:
Linux kernel 4.8 hangs at boot up
To manage notifications about this bug go to:
https://bugs.launchpad.net/
v4.8-rc7-201701301041 don't know
v4.8-rc7-201701301734 passed (on Acer Aspire V5-551G)
v4.8-rc7-201701301041 disappeared before I had a chance to test it. But it
doesn't matter. I'm more than 98% certain that lotek and I will always get
the same results.
--
You received this bug notification bec
v4.8-rc7-201701271606 passed (i.e. no bug in this version)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659340
Title:
Linux kernel 4.8 hangs at boot up
To manage notifications about this bug go t
v4.8-rc7-201701261200 passed
When I installed this kernel with "sudo dpkg -i *.deb" it replaced the
previously installed v4.8-rc7. Was that alright? Should I have uninstalled
the previous v4.8-rc7 before I installed the new one? Or isn't it necessary?
--
You received this bug notification becaus
v4.7.5 passed
v4.7.6 failed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659340
Title:
Linux kernel 4.8 hangs at boot up
To manage notifications about this bug go to:
https://bugs.launchpad.net/u
v4.10-rc5 failed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659340
Title:
Linux kernel 4.8 hangs at boot up
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sour
I also tested 4.8-rc7 and 4.8-rc8 with the same results as lotek:
4.8-rc7 passed
4.8-rc8 failed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659340
Title:
Linux kernel 4.8 hangs at boot up
To man
4.5 final: Passed (boots up and works ok)
4.6 final: Passed
4.7 final: Passed
4.8-rc1: Passed
4.8.0-26: Failed
@Joseph, all the 4 kernel versions that you wanted me to test, work. My PC
boots up, and Ubuntu can be used as usual.
4.8.0-26 and all the later 4.8.0-xx versions hang at the grub scre
When I collected information with "apport-collect 1659340" I had booted
with the 4.4.0-45 kernel, which works for me. Therefore I suppose that some
of the collected information is irrelevant.
I can't boot with any later kernel that I've tried.
** Changed in: linux (Ubuntu)
Status: Incomple
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1659340/+attachment/4809045/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/165
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1659340/+attachment/4809047/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659340
Titl
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1659340/+attachment/4809048/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659340
Title:
Li
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1659340/+attachment/4809050/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659340
Ti
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1659340/+attachment/4809049/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659340
Title:
Li
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1659340/+attachment/4809042/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659340
Title:
Linu
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1659340/+attachment/4809043/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659340
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1659340/+attachment/4809046/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659340
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1659340/+attachment/4809044/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659340
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1659340/+attachment/4809041/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659340
Title:
Linu
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1659340/+attachment/4809039/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659340
Title:
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1659340/+attachment/4809037/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659340
Title:
Linux
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1659340/+attachment/4809040/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/16593
apport information
** Tags added: apport-collected yakkety
** Description changed:
I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot,
Windows 10 and Ubuntu 16.10.
Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45.
When I try to start w
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1659340/+attachment/4809038/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659340
Public bug reported:
I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot,
Windows 10 and Ubuntu 16.10.
Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45.
When I try to start with any of the 4.8.0 kernels delivered with regular
Ubuntu updates, they a
Kernel v4.10-rc3 does not boot up for me. Now I've also tested with
acpi=off. Neither v4.10-rc3 nor v4.8.0-34 boots up with acpi=off.
Perhaps my case does not fit in this bug report. It's probably not the
same problem as renm's, although the symptoms are similar.
--
You received this bug notifica
The newest kernel, 4.8.0-32, behaves just like the other 4.8.0 versions.
Ubuntu never starts up.
After I've tried in vain to start with Linux 4.8.0-xx, and then starts
with 4.4.0-45, the following errors are printed:
[ 2.511733] usb 4-3: string descriptor 0 read error: -22
[ 3.841872] [drm:rade
This looks very much like what's happening to me.
I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot,
Windows 10 and Ubuntu 16.10.
Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45.
When I try to start with any of the 4.8.0 kernels delivered with re
37 matches
Mail list logo
