No bug was tagged with verification-needed this cycle.
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/verification-testing
Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin
(cypressyew)
*** This bug is a duplicate of bug 1712176 ***
https://bugs.launchpad.net/bugs/1712176
Me too.
$ dmesg | tail -n15
[47625.666560] hid-generic 0003:0451:E012.0017: unknown main item tag 0x0
[47625.666582] hid-generic 0003:0451:E012.0017: unknown main item tag 0x0
[47625.06] hid-generic
3.13.0-138.187 - generic
Regression test CMPL.
Issue to note in amd64:
ubuntu_kvm_smoke_test - uvt-kvm wait issue, bug 1732883
ubuntu_kvm_unit_tests - 43 failed on pepe, 44 failed on amaura
Issue to note in arm64:
hwclock - issue for HP m400, bug 1716603
libhugetlbfs - timed out on
** Also affects: sbsigntool (Ubuntu)
Importance: Undecided
Status: New
** Also affects: sbtools
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
** Summary changed:
- linux-signed-image warning messages: checksum areas are greater than image
size and file-aligned section .text extends beyond end of file
+ linux-signed-image-4.13.0-21-generic warning messages: checksum areas are
greater than image size and file-aligned section .text
Public bug reported:
The new kernel update 4.13.0-21-generic while installing the linux-
signed-image-4.13.0-21-generic produced below warning messages:
warning: file-aligned section .text extends beyond end of file
warning: checksum areas are greater than image size. Invalid section table?
*** This bug is a duplicate of bug 1734147 ***
https://bugs.launchpad.net/bugs/1734147
** This bug has been marked a duplicate of bug 1734147
Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
--
You received this bug notification because you are a member of Kernel
Packages, which
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
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/1711936
Title:
Severe graphical corruption in gnome-shell with
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1711936
and then change the status of the bug to 'Confirmed'.
If, due to the
On Fri, Dec 22, 2017 at 04:18:31AM -, Jared Dominguez wrote:
> (NB: superm1 and I work for Dell)
> Can anyone provide confirmation on this affecting them with the Dell XPS
> 13 (9350) with Intel i7? That's actually exactly what I'm running with
> Artful without issue, and we have not seen any
** Changed in: gnome-shell (Ubuntu)
Status: Expired => New
** Changed in: linux (Ubuntu)
Status: Expired => New
--
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/1711936
Damn. Yesterday I updated a Lenovo G40-70 from 17.04 to 17.10 (but not
restarted it yet) and today I stumbled on this horrible news/bug. Still
not sure if the model is affected.
My two cents would be -now that the ISO was pulled- that a warning with
big red letters or something shows up when you
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
(NB: superm1 and I work for Dell)
Can anyone provide confirmation on this affecting them with the Dell XPS
13 (9350) with Intel i7? That's actually exactly what I'm running with
Artful without issue, and we have not seen any escalations from Dell
support on this issue on any Dell systems.
>From HP forums, I read HP envy x360 u000 is also affected. So, not alone
>Lenovo/Acer/Toshiba, some HPs and Dells are also affected, most probably
>having Insyde UEFI/BIOS.
Here is the link:
FWIW this bug was fixed upstream already.
https://github.com/torvalds/linux/commit/d9018976cdb6eefc62a7ba79a405f6c9661b08a7
https://bugzilla.kernel.org/show_bug.cgi?id=195951
** Bug watch added: Linux Kernel Bug Tracker #195951
https://bugzilla.kernel.org/show_bug.cgi?id=195951
** Also
That one hung much like the others, with the system responding only to
very basic commands (mostly bash internals), although the dmesg output
continued further after the kernel bug message. Here's the dmesg output:
[ 107.652875] EDAC MC0: Giving out device to module sb_edac.c controller
Haswell
There is probably a Solution which could be found here
https://github.com/vmp32k/akoya-fixup
I yet not managed to get around SecureBoot to test this Solution
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags added: patch
--
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/1739107
Title:
linux-cloud-tools-common: Ensure hv-kvp-daemon.service starts before
walinuxagent.service
Status in
** Description changed:
SRU Justification
Impact: Many users are reporting issues with bios corruption with 17.10.
This seems to stem from enabling the intel-spi-* drivers in the kernel,
which don't appear to be ready for use on end-user machines.
Fix: Disable this driver.
** Description changed:
When testing MAAS on Bionic, we noticed sluggish performance that we
could not immediately explain.
After comparing the results from a run of the test suite on Xenial to a
run on Bionic, we determined that the slowdowns had to do with DNS
lookups. In
I just tested with the Xenial kernel and Bionic userspace and observed
that the bug still occurs, so marked Invalid for 'linux'.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is
Lenovo y40-80 also corrupted. I've tried so many things. It really seems
like a BIOS flash from usb, or a BIOS flash from an eeprogrammer is our
best bet..
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Toshiba satellite s50-b-13g is corrupted as well i cant enter bios or
boot selection menu , and can't boot from usb, but ubuntu system works
fine
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Thanks for testing. I'll mark that kernel as good. I think it's safe
to ignore the "error -19" messages during the bisect. We just need to
tell the bisect whether the kernel exhibits the original bug or not.
I built the next test kernel, up to the following commit:
I would like to report the same issue on a Zotac ZBOX-SN970-P.
The issue prevents booting from any Live USB install of the following
distros :
Ubuntu 16.04.3 LTS, Ubuntu 17.10, Mint 18.3, Arch Linux 2017.12.01
The BIOS is as up to date as possible.
--
You received this bug notification
One way to tell if this bug is due to the kernel, is to boot with some
prior kernel versions and see if the bug goes away.
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Kernel
Hi Dan,
How do we know when we hit the bug with your patched kernel? is it still
logging "waiting for lo to become free" or is there any other signature
we can use to detect the original problem and still say "Wow! it works,
Dan rocks"
I have been scavenging the internet looking for your linux
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1739678
Title:
HDMI audio makes loud popping
I created a boot usb stick today and used that to boot the laptop.
Still getting the same initial error on boot. 16.04 LTS still boots
without error so it does appear to be the newer kernels causing the
Ubuntu.
On 14 December 2017 14:17:26 GMT+00:00, Joseph Salisbury
Public bug reported:
When playing audio via HDMI, I get very loud pops and/or periods of
silence. The frequency of this behaviour seems to go way up while
playing video with a lot of motion, and especially YouTube videos. I can
reliably reproduce the problem by playing the video
Note: I doubt this bug is in the kernel itself; I initially attempted to
file it under glibc at first, but for some reason the `linux` package
was selected.
I also added `systemd` in case the difference in behavior can be
explained by the addition of resolved.
Note that these tests were run on
I can confirm that Lenovo Z70-80 laptops are affected as well. Refuses
to remember new BIOS settings.
--
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/1734147
Title:
Ubuntu 17.10
The build from http://kernel.ubuntu.com/~jsalisbury/lp1733662/
successfully completed about six runs of the test script, albeit with
the verbose dmesg output that includes the "EDAC sbridge: Failed to
register device with error -19" messages.
--
You received this bug notification because you are
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1739672
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
When testing MAAS on Bionic, we noticed sluggish performance that we
could not immediately explain.
After comparing the results from a run of the test suite on Xenial to a
run on Bionic, we determined that the slowdowns had to do with DNS
lookups. In particular, if MAAS
0001-UBUNTU-Debian-hyper-v-Ensure-that-hv-kvp-daemon.serv.patch
** Patch removed:
"0001-UBUNTU-Debian-hyper-v-Ensure-that-hv-kvp-daemon.serv.patch"
Waiting for a confirmation from Azure team to validate that the proposal
fix for all Ubuntu stable releases works as expected with their internal
validation before submitting to kernel-team ML.
Regards,
Eric
** Patch removed: "UBUNTU-Debian-hyper-v-Ensure-that-hv-kvp-daemon.serv.patch"
UBUNTU-Debian-hyper-v-Ensure-that-hv-kvp-daemon.serv.patch
** Patch added:
"0001-UBUNTU-Debian-hyper-v-Ensure-that-hv-kvp-daemon.serv.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739107/+attachment/5025786/+files/0001-UBUNTU-Debian-hyper-v-Ensure-that-hv-kvp-daemon.serv.patch
Proposal patch
** Also affects: linux (Ubuntu Bionic)
Importance: Medium
Status: Triaged
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: linux
One note on the test kernels, I'm still updating the patch as the change
in the current test kernels will leave sockets open which leaks memory
due to the netns not fully closing/exiting. I'll update this bug when I
have an updated patch and test kernels.
I would not recommend the current test
I have also coruppted bios on Lenovo y50-70. I cant do any chnages. Do
you think that will be a software solution ? I hope i wont to change MB.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Just in case anyone is actually reading the comments before they post in
this bug. If you're unaffected, there's no need to post. Live your life
happily. That goes doubly if your device isn't even listed in the
initial bug post.
--
You received this bug notification because you are a member of
Lenovo Flex 2-14 (i5) whith Phoenix BIOS - no issue so far.
--
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/1734147
Title:
Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
@toxicpublic
If you dare, you can download the BIOS exe from Lenovo site, extract the
content and take the binary firmware file and next follow the service recovery
guide:
https://www.bios-mods.com/bios-recovery/insyde-bios-recovery/
However, I doubt this will help. This is not touching the
I built the next test kernel, up to the following commit:
83d4a97746e5fac08e2a1498c3649586bab953a3
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1733662
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
@peti634 , with what computer does this solution work? and how can I do
it?
--
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/1734147
Title:
Ubuntu 17.10 corrupting BIOS - many LENOVO
This bug certainly needs to be treated as urgent. It's being tracked as
part of the critical SLA process and blocks deployments of foundation
bundles in the QA lab and in the field.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
@toxicpublic
It depends on your model number. My sequence was:
1) Go to support.lenovo.com
2) Type your serial number in the box
3) Click "Drivers and Software" in the blue bar
4) Select Windows 10 64-bit in the "Operating Systems" drop down menu
5) Select BIOS/UEFI in the "Components" drop
@christopherreis
There is no iso for a lot of Lenovo models. For instance, for Lenovo
G40-30, there is only an .exe file, that is only compatible with Windows
8.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
It can affect HP notebooks too.
My HP Pavilion 14n050BR BIOS cant save settings. Tried setting efivars
from efibootmgr, UEFI shell v1 and v2 without success. Also tried
updating BIOS, with no luck.
Happened after installing Opensuse Tumbleweed, some months ago.
But here its possible to install
Yes, i believe All the Insyde Bios Are getting infected Nice point by whoever
pointed it out.
I have Hp p206tx and i also suffered with same issues as mentioned above with
an extra Suspend problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is
I am not affected; I have a Lenovo X1 Carbon (5th Gen), running Lubuntu
17.10.
Kernel info:
4.13.0-21-generic #24-Ubuntu SMP Mon Dec 18 17:29:16 UTC 2017 x86_64
x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Tags added: sts
** Tags added: azure
--
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/1739107
Title:
linux-cloud-tools-common: Ensure hv-kvp-daemon.service starts before
Dell XPS 13 9360 seems to be fine. Still can save bios settings and boot
from usb.
--
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/1734147
Title:
Ubuntu 17.10 corrupting BIOS - many
I currently don't have this problem on my Lenovo Ideapad 310, I want to
ask if this problem may still affect my computer anytime soon. I also
want to know if my computer will be affected if my computer is UEFI.
Thank you very much.
--
You received this bug notification because you are a member
That one completed one run of the test OK, but then crashed on the
second one, when bringing CPU 15 back online, with the following dmesg
output:
[ 160.596312] EDAC MC0: Giving out device to module sb_edac.c controller
Haswell SrcID#1_Ha#0: DEV :ff:12.0 (INTERRUPT)
[ 160.596537] EDAC MC1:
I built the next test kernel, up to the following commit:
8d9d2235a82ea41e65eff607005ea4f334e2e503
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1733662
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
Andres,
I'm not going to be at the sprint but the problems described need a
proper solution in MAAS and Juju at least from the end host perspective.
Similar to how VLANs are supported natively in MAAS & Juju, L3
virtualization technologies like VRF should be as well. I hope the
information I will
Hello, It affects also the Lenovo G40-80 Model.
After installation, reboot didn't complete, BIOS settings were readonly,
the only viable boot option was with a Ubuntu 17.04 Bootable USB.
The only solution was to change the bios chip. Now, with the new bios
chip, boot time has increased before
Christopher, I was not able to find the iso you're talking about on
Lenovo website, not even for the model you described. Can you please
give a more precise link to where it can be found? Thanks in advance.
--
You received this bug notification because you are a member of Kernel
Packages, which
I have now kernel 4.14 and this issue is still not solved.
--
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/1661876
Title:
[Asus UX360UA] battery status in unity-panel is not changing
An update on this issue now that I have kernel 4.14:
After executing `uname -a`, I have the following output:
`Linux tjiagom-UX360UA 4.14.0-041400-generic #201711122031 SMP Sun Nov 12
20:32:29 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux`
So, with kernel 4.14, the hardware buttons are now working,
An update on this issue now that I have kernel 4.14:
After executing `uname -a`, I have the following output:
`Linux tjiagom-UX360UA 4.14.0-041400-generic #201711122031 SMP Sun Nov 12
20:32:29 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux`
If I rotate the screen the keyboard is blocked, but the
I had this issue (corrupted BIOS) with a Lenovo Yoga 460. Lenovo
publishes an ISO that can be used to update the BIOS (you can burn the
ISO to a disc and boot it). The ISO for your specific machine (if
available) can be found at support.lenovo.com. I was able to restore my
BIOS from the ISO.
** Description changed:
SRU Justification
Impact: Many users are reporting issues with bios corruption with 17.10.
This seems to stem from enabling the intel-spi-* drivers in the kernel,
which don't appear to be ready for use on end-user machines.
Fix: Disable this driver.
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1739615
Title:
package
Public bug reported:
postinstall does not end (infinite loop ? )
ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: linux-headers-4.13.0-17-generic 4.13.0-17.20
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
I am travelling right now, and I won't be able to try the test kernel
until after Christmas.
--
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/1731031
Title:
Kernel Oops with 17.10
Status
turned out to be something else, closing
** Changed in: linux (Ubuntu Xenial)
Status: Triaged => Invalid
--
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/1702061
Title:
[i915_bpo]
--- Comment From frede...@fr.ibm.com 2017-12-21 06:42 EDT---
Hi,
FYI I tried to patch kernel 4.13 of 17.10 with the patch that Aneesh mentioned
but this error still happens at boot time.
F.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Comment #5 worked for me. Thank you aroman-a, You saved me hours!
--
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/1731060
Title:
package linux-image-extra-4.13.0-17-generic 4.13.0-17.20
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in:
This bug was fixed in the package linux-oem - 4.13.0-1012.13
---
linux-oem (4.13.0-1012.13) xenial; urgency=low
* linux-oem: 4.13.0-1012.13 -proposed tracker (LP: #1738862)
* Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models (LP: #1734147)
- [Config]
This bug was fixed in the package linux-oem - 4.13.0-1012.13
---
linux-oem (4.13.0-1012.13) xenial; urgency=low
* linux-oem: 4.13.0-1012.13 -proposed tracker (LP: #1738862)
* Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models (LP: #1734147)
- [Config]
This bug was fixed in the package linux-hwe-edge - 4.13.0-21.24~16.04.1
---
linux-hwe-edge (4.13.0-21.24~16.04.1) xenial; urgency=low
* linux-hwe-edge: 4.13.0-21.24~16.04.1 -proposed tracker (LP:
#1738842)
* linux: 4.13.0-21.24 -proposed tracker (LP: #1738823)
* Ubuntu 17.10
This bug was fixed in the package linux-hwe-edge - 4.13.0-21.24~16.04.1
---
linux-hwe-edge (4.13.0-21.24~16.04.1) xenial; urgency=low
* linux-hwe-edge: 4.13.0-21.24~16.04.1 -proposed tracker (LP:
#1738842)
* linux: 4.13.0-21.24 -proposed tracker (LP: #1738823)
* Ubuntu 17.10
** Description changed:
SRU Justification
Impact: Many users are reporting issues with bios corruption with 17.10.
This seems to stem from enabling the intel-spi-* drivers in the kernel,
which don't appear to be ready for use on end-user machines.
Fix: Disable this driver.
As I said in a previous comment we were experiencing this very
infrequently during nightly dumps on a database, it was happening about
once per month, but the issue became more frequent and persistent this
week.
So, after experiencing the issue 3 nights in a row during nightly
database dumps, we
Only two days ago this was posted by Canonical employee Anthony Wong:
'@britgreek Even though we now have a kernel that can prevent the issue
happening, we are still finding the root cause with Lenovo, please be
patient.'
Saying 'me too' 'any more news' and 'what's the ETA on this' will not
help
Hi
FIX:
If you have GD25q64 BIOS flash:
You should change the CMP bit (13.) of Status register.
The problem is CMP=1 and BP0-4=0,0,0,0 then all flash area protected.
Changed the CMP bit to 0 with SPI writer!
Enjoy!
--
You received this bug notification because you are a member of Kernel
Hi, I have a Toshiba Satellite L50-B-1R7 and I have the same problem. I
thought it was related with the CMOS battery, but this model doesn't
have it and I couldn't find what was the cause until I read about this
bug today.
--
You received this bug notification because you are a member of Kernel
To enlighten this: i have written to ELAN Microelectronics Corp. at
'http://www.emc.com.tw/' which is not Medion. Whereupon ELAN answered
the above content, see #117
My Text:
Hello,
this is P*** from requesting help to make one of you Touchpads run
under Linux(Ubuntu). Do you provide any
probably yes, because my thinkpad doesn't have Insyde but y50-70 does
--
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/1734147
Title:
Ubuntu 17.10 corrupting BIOS - many LENOVO laptops
I don't know if anyone has reported the issue on my laptop, but I
confirm that my Toshiba L50-B-17V is now hanging on a tread because of
this issue. I installed 17.10 a while ago, noticed the issue of the
locked BIOS, but I didn't think Ubuntu could've caused it. I honestly
thought my CMOS battery
Please could you clarify how can I add more logs, which logs are
relevant, any other information so you can have a full picture...
--
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/1738921
Can anyone confirm that only laptops with Insyde BIOS are affected?
I have Lenovo Yoga X1 2nd gen with Phoenix BIOS and booted it into
17.10. Fortunately, I do not observe the symptoms.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Register map documentation for the SPI (Serial Peripheral Interface) in
recent Intels begins on page 5626
https://www.intel.com/content/dam/www/public/us/en/documents/datasheets/atom-z8000
-datasheet-vol-2.pdf
HSFSTS (Hardware Sequencer Status) + HSFCTL (Hardware Sequencer Control)
are covered
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1739579
Title:
package
I tried it and it worked for 1 day, but it just happened again.
Maybe this isn't a problem with Ubuntu/Linux after all?
I have already checked the physical connection of the drive and as far as I
could find out the drive itself is healthy too, so I have no idea what the
problem might be...
Any
** Tags removed: need-duplicate-check
--
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/1739579
Title:
package linux-image-extra-4.13.0-21-generic (not installed) failed to
Public bug reported:
1
ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: linux-image-extra-4.13.0-21-generic (not installed)
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
Hi, I have a HP 15-BS000 series laptop notebook with Insyde BIOS and
using Ubuntu 17.10. So, far I have not observed any issues as reported
by others. Can anyone confirm if HP models are safe from this bug. Thank
you.
--
You received this bug notification because you are a member of Kernel
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1739570
Title:
package
** Tags removed: need-duplicate-check
--
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/1739570
Title:
package linux-image-4.13.0-21-generic 4.13.0-21.24 failed to
install/upgrade:
Public bug reported:
Issue appears as part of a usual update. It manifest as a freezing at
the dkms stage of the update.
ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-21-generic 4.13.0-21.24
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux
Hi, I'm owner of lenovo y50-70 and thinkpad x250. On x250 I have ubuntu
17.10 and this machine is not affected. But on y50 I have ubuntu 17.04
with upgraded kernel through ukuu and guess what, I'm affected.
--
You received this bug notification because you are a member of Kernel
Packages, which
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1739560
Title:
Trusty arm64 system will hang
Looks good so far. Docker is still usable after 5000 runs, no "waiting
for lo to become free" in syslog.
Linux docker 4.4.0-104-generic #127+hf1711407v20171220b1-Ubuntu SMP Wed
Dec 20 12:31:13 UTC 201 x86_64 x86_64 x86_64 GNU/Linux
$ docker version
Client:
Version: 17.09.1-ce
API version:
1 - 100 of 102 matches
Mail list logo
