@Eden bar: If you are asking me:
I got it fixed by local computer shop. By local I mean I found 3 in
Slovakia capable of changing BIOS chip and this one was the cheapest and
able to send courier to pick it up at bring it back with no hassle...
I beleive you can find a guy capable of replacing BIO
Does the issue happen after a system suspend?
--
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/1737934
Title:
Samsung SM961 NVMe SSD randomly unmounts/loses connection/unavailable
Status
Yes I understand you and most people are asking for a resolution to "Not
enough free handles to register service". However it is better for a
bug's resolution if we focus on the problem that the original reporter
was trying to describe. And that's a very different, unrelated problem.
We certainly
*** This bug is a duplicate of bug 1706033 ***
https://bugs.launchpad.net/bugs/1706033
--- Comment From shriy...@in.ibm.com 2017-12-13 23:26 EDT---
Verified with latest kernel on Ubuntu 16.04.03 and it works as expected
=
root@ltc-wspoon12:/
Complement to #56, Ubuntu 16.04.3, Kernel 4.14.4, journalctl -b:
Dec 13 20:44:33 alien bluetoothd[928]: Failed to obtain handles for "Service
Changed" characteristic
Dec 13 20:44:33 alien bluetoothd[928]: Not enough free handles to register
service
Dec 13 20:44:33 alien bluetoothd[928]: Error ad
This bug effects 128 people and closing it because you don't like the
title feels wrong. Two Ask Ubuntu questions point to this Lanuchpad bug
report in the hopes it will be solved:
https://askubuntu.com/questions/757396/bluetooth-how-to-solve-not-
enough-free-handles-to-register-service-error
and
This is also affecting Alpha Litebooks. After installed Ubuntu 17.10 I
now get UEFI errors every time my computer starts and cannot restore
UEFI boot entries from command line, it's bricked. Luckily I can still
boot if I manually choose the grubx64 file on the EFI partition. My USB,
PXE boot option
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-zesty
** Tags added: block-proposed
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upl
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1738105/+attachment/5022439/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1738105/+attachment/5022437/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1738105/+attachment/5022438/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1738105/+attachment/5022440/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1738105/+attachment/5022441/+files/PulseList.txt
--
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/
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1738105/+attachment/5022432/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
I was able to boot into ubuntu using recover mode (modeset listed in
line beginning with 'linux' after choosing advanced ubuntu in grub menu)
ran apport as requested in email sent to me after creating ticket.
--
You received this bug notification because you are a member of Kernel
Packages, whic
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1738105/+attachment/5022436/+files/Lsusb.txt
--
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/1738105
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1738105/+attachment/5022435/+files/Lspci.txt
--
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/1738105
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1738105/+attachment/5022433/+files/IwConfig.txt
--
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/17
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1738105/+attachment/5022443/+files/UdevDb.txt
--
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/1738105
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1738105/+attachment/5022434/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1738105/+attachment/5022442/+files/RfKill.txt
--
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/1738105
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1738105/+attachment/5022431/+files/CRDA.txt
--
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/1738105
Ti
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1738105/+attachment/5022444/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Tags added: apport-collected artful
** Description changed:
Getting
A start job is running for detect the available GPUs and deal with any system
changes
This looks like a reprise of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692305?comments=all
> #15 says problem went away but is on Kernel 4.4 and Kerne 4.8
> where message was "hacked" to not display. With kernels 4.9, 4.10,
> etc...
That's not the first time the kernel folks have done that. They do it in
the crypto subsystem to hide messages that folks would want to see and
fix, like th
#15 says problem went away but is on Kernel 4.4 and Kerne 4.8 where
message was "hacked" to not display. With kernels 4.9, 4.10, etc. the
message reappears as per bug report here:
https://bugzilla.kernel.org/show_bug.cgi?id=193531
#17 closing this bug based upon #15 should be reconsidered.
Also n
Yoga 33-11 IBR affected - result is absolute brick without any signs of
life. Totally dead.
--
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 - m
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 1738105
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Public bug reported:
Getting
A start job is running for detect the available GPUs and deal with any system
changes
This looks like a reprise of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692305?comments=all
'I disabled the splashscreen and I could see that the system hangs when
tryin
I am seeing the same issue for
asus zen ultrabook UX550VE-DB71T with 1050Ti graphics card
https://www.amazon.com/gp/product/B07532Y2LL/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1
I am trying to install the official ubuntu 17.10-desktop-amd64.iso
downloaded Dec 13th 2017
sha256 = aaf4ba1809e08f610
I installed trisquel_7.0_amd64.iso
The touchpad works.
I have includes devices under trisquel, with the touchpad below:
I: Bus=0011 Vendor=0002 Product=0007 Version=01b1
N: Name="SynPS/2 Synaptics TouchPad"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input6
U: Un
I installed trisquel_7.0_amd64.iso
The touchpad works.
I have includes devices under trisquel, with the touchpad below:
I: Bus=0011 Vendor=0002 Product=0007 Version=01b1
N: Name="SynPS/2 Synaptics TouchPad"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input6
U: Un
I installed trisquel_7.0_amd64.iso
The touchpad works.
I have includes devices under trisquel, with the touchpad below:
I: Bus=0011 Vendor=0002 Product=0007 Version=01b1
N: Name="SynPS/2 Synaptics TouchPad"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input6
U: Un
Upstream kernel test - kernel 4.15-rc3
Test results:
https://bugs.freedesktop.org/show_bug.cgi?id=101483#c32
Bug fixed in this upstream kernel!
** Tags removed: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.13-rc4
latest-bios-f.41
** Tags added: kernel-fixed-upstream kernel-fixed-upstr
I had this problem using
sudo apt-get upgrade
apparently, with Nvidia's card activated, the problem persists even if you
re-configure dpkg.
The solution was to change to Intel's card, perhaps with sudo prime-select
intel.
Worked for me :)
--
You received this bug notification because you
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
+ boot
Sorry for my late reply.
Linux v4.17 gave me the same identical issue. I could not easily post
here at the time because of the AppArmor bug.
Now I reinstalled (x)ubuntu 17.10 on my laptop, and after I upgraded
Linux to the v4.15-rc3 from the mainline, the trackpad works perfectly.
--
You receiv
Hi there.
I'm back to 17.10 failing to boot cleanly at all.
16.4LTS boots fine no problem.
On 11 December 2017 20:19:24 GMT+00:00, Joseph Salisbury
wrote:
>Would it be possible for you to test the latest upstream kernel? Refer
>to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
*** This bug is a duplicate of bug 1737234 ***
https://bugs.launchpad.net/bugs/1737234
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1737234, so is being marked as such.
Public bug reported:
problem : Package broken
cause : .../linux-image-4.4.0-103-generic_4.4.0-103.126_i386.deb ... This
kernel does not support a non-PAE CPU.
Installation : Xubuntu 16.04 with option forcepae
Material : laptop IBM T41
Similar problem : [Kernel-packages] [Bug 1737234
(https://ww
Testing on arm64, the workaround of adding xenial-proposed via maas
doesn't work - the newer ubuntu-fan package isn't being installed
http://paste.ubuntu.com/26178859/
I don't know how that can be, since the repo is being added (or should
be added) before juju installs ubuntu-fan.
--
You receiv
I got same problem using latest 4.15rc-3
ec 13 20:57:59 bigone kernel: [ 23.575115] ata10.00: status: { DRDY }
Dec 13 20:57:59 bigone kernel: [ 23.577829] ata10.00: failed command: WRITE
FPDMA QUEUED
Dec 13 20:57:59 bigone kernel: [ 23.580536] ata10.00: cmd
61/08:f0:00:08:00/00:00:02:00:00
Public bug reported:
[Impact]
The i2c input frequency is currently hardcoded in the driver. This may not
match the actual frequency used by the platform. Upstream has updated the
driver to pull the frequency from firmware.
[Test Case]
The updated driver will detect the CAV9007 ACPI ID:
ubuntu@
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => 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/1737511
Title:
linux: 4.4.0-104.127 -proposed t
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1737515
Title:
linux-aws: 4.4.0-1044.53 -pr
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Description changed:
This bug is for tracking the upload package. This
bug will contain status
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
--
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/1737942
Title:
linux: 4.10.0-43.47 -proposed
+1 for this. Tried the BIOS recovery process for bricked laptop (Fn - R
with BIOS in USB) completed successfully but settings still remained and
can not be modified. Laptop is bricked. Device details below:
Product Name: Lenovo Y50-70
BIOS Version: 9ECN43WW(v3.03)
EC Version: 9EEC43WW(v3.03)
MTM
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/1738060
Title:
Cherry Trail Support
Status i
Public bug reported:
Cherry Trail USb 3.0 support not stable
Getting IO error, but with the hub it works.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-19-generic 4.13.0-19.22
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Released
** Description changed:
This bug is for tracking the upload package. This
bug will contain
--- Comment From shriy...@in.ibm.com 2017-12-13 13:32 EDT---
(In reply to comment #17)
> Yes, that commit is in the test kernel posted at:
> http://kernel.ubuntu.com/~jsalisbury/lp1711104/
Tested the kernel given in the above link :
uname -a : Linux ltc-wspoon12 4.10.0-33-generic #37~lp17
I take this back, it is still an issue with the amd64 ISO:
https://paste.ubuntu.com/26178135/
--
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/1736770
Title:
debian-installer/main-menu cha
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Incomplete
** Changed in: linux (Ubuntu Zesty)
Status: In Progress => Incomplete
** Changed in: linux (Ubuntu Artful)
Status: In Progress => Incomplete
** Changed in: linux (Ubuntu)
Status: In Progress => Inc
I can verify the fix works in my environment using whats in xenial-
proposed http://paste.ubuntu.com/26178059/
Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1737640
Title:
Default Comment by Bridge
** Attachment added: "target fix for artful"
https://bugs.launchpad.net/bugs/1658733/+attachment/5022248/+files/makedumpfile_1.6.1-2ubuntu0.1.diff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools i
** Changed in: linux (Ubuntu Zesty)
Status: In Progress => Incomplete
** Changed in: linux (Ubuntu)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
** Changed in: linux (Ubuntu)
Status: In Progress => Incomplete
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Incomplete
** Changed in: linux (Ubuntu Zesty)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ker
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Incomplete
** Changed in: linux (Ubuntu)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
Can you see if the bug happens with 4.13-rc1:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc1/
--
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.1
** Changed in: linux (Ubuntu Zesty)
Status: In Progress => Incomplete
** Changed in: linux (Ubuntu)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
> So if there is something to test or debug, I would be happy to help
fixing this issue.
yes, I'm hoping to have a kernel build with some added debug to
track/list exactly what socket(s) are still holding lo device references
when the container is killed/shutdown, so testing with that would help
c
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu Artful)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
** Tags added: kernel-da-key
--
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/1730958
Title:
nuvoton-cir not working after boot
Status in linux package in Ubuntu:
Incomplete
Bug descri
Would you be able to test some test kernels? If so, we can try to
bisect down to which commit introduced the regression.
--
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/1736390
Title:
op
thinking this is the same bug/duplicate I'm hitting here
https://bugs.launchpad.net/juju/+bug/1736022
I'm deploying a few nodes to test the fix in proposed now
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://
This bug was fixed in the package makedumpfile - 1:1.6.2-1ubuntu1
---
makedumpfile (1:1.6.2-1ubuntu1) bionic; urgency=medium
* KDUMP_CMDLINE_APPEND: add noirqdistrib to default command line. As it's
only used by ppc64el, it's not required to be conditionally added.
(LP: #165
Just a note that I'm seeing far less skb_warn_bad_offload warnings in
Xenial with the last 3 or 4 official 4.10 kernels (4.10.0-42, 4.10.0-40,
4.10.0-38, etc). Sometimes I don't see any warnings for a week or so,
sometimes a few pop out. So it looks much better now, I'm just not sure
it is fixed co
This bug was fixed in the package makedumpfile - 1:1.6.2-1ubuntu1
---
makedumpfile (1:1.6.2-1ubuntu1) bionic; urgency=medium
* KDUMP_CMDLINE_APPEND: add noirqdistrib to default command line. As it's
only used by ppc64el, it's not required to be conditionally added.
(LP: #165
Hello Anthony,
My situation is:
Lenovo Ideapad Flex 10. Came with windows 8 installed and updated to windows
10. I then installed Ubuntu 14.04 as dual boot and had each release of Ubuntu
updated since 14.04.
I was dual booting using legacy for Ubuntu and UEFI for occasional access to
windows 1
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1737515
Title:
linux-aws: 4.4.0-1044.5
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1737512
Title:
linux-aws: 4.4.0-1006.6
Looking at the test history - artful passed tests with 4.11 and 4.12
kernels with 2.8.0, but appears to have started failing sporadically
when 4.13 entered the archive.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https
** Changed in: kernel-sru-workflow/snap-release-to-beta
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/snap-release-to-edge
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/snap-certification-testing
Status: New => Confirmed
--
You
** Changed in: kernel-sru-workflow/snap-release-to-beta
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/snap-release-to-candidate
Status: New => Confirmed
** Changed in: kernel-sru-workflow/snap-release-to-edge
Status: Confirmed => Fix Released
--
You r
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Fix Released
--
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/1737511
Title:
linux: 4.4.0-104.127 -propo
** Summary changed:
- linux: -proposed tracker
+ linux: 4.4.0-105.128 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-team) => T
I just tested this also and can verify it fixed it in the
environment/test where it was originally reported as broken.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1737640
Title:
** Summary changed:
- linux: -proposed tracker
+ linux: 4.13.0-20.23 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-team) => Kh
Changing tag to verified as per comments #13 & #14.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/
It already uses gtk3. It builds in this complicated way where it can use
either gtk3 or gtk2 at runtime, but presumably you can just stop
building the gtk2 support in.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubun
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in Ubuntu.
https://bugs.launchpad.net/bugs/1737913
Title:
linux-lts-trus
Thanks @davecore and @benjamin-long for verifying the fix!
--
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/1737033
Title:
upgrading linux-image package to 4.4.0-103.126 breaks Ceph networ
I also confirm the kernel 4.4.0-104.127 in xenial-proposed fixes the
issue. I am able to mount my CephFS filesystem normally. Benjamin also
confirmed the kernel works for him in comments #26 and #27. I am
changing the tag to verification-done-xenial. Thanks!
** Tags removed: verification-needed-xe
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Released
** Description changed:
This bug is for tracking the upload package. This
bug will contain statu
I don't have a data point for 4.11, but at 4.10 (as shipped in zesty)
ovs 2.8.1 tests are OK.
--
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/1736390
Title:
openvswitch: kernel opps destr
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
--
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/1737911
Title:
linux: 3.13.0-138.187 -propose
Can you see if using earlier kernel versions makes the bug go away?
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
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/1736593
Title:
ThunderX: IPv6 TX failure unless checksum offload
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.15 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
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/1736774
Title:
arm64/thunderx: Unhandled context faults in ACPI m
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.15 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from
Hi,
We can confirm that this issue still persists as of 4.4.0-103-generic
#126-Ubuntu SMP Mon Dec 4 16:23:28 UTC 2017 x86_64 x86_64 x86_64
GNU/Linux this update.
It only happens on a soft reboot, i.e. 'sudo reboot'.
Not sure if there is a work around for it.
--
You received this bug notificati
** Summary changed:
- linux-lts-trusty: -proposed tracker
+ linux-lts-trusty: 3.13.0-138.187~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (c
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Released
** Description changed:
This bug is for tracking the upload package. This
bug will contain
Fix committed to bionic.
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Seth Forshee (sforshee)
--
You received this bug n
root 16037 1 0 12:39 ?00:00:00 ovsdb-server: monitoring pid
16038 (healthy)
root 16038 16037 0 12:39 ?00:00:00 ovsdb-server
/etc/openvswitch/conf.db -vconsole:emer -vsyslog:err -vfile:info
--remote=punix:/var/run/openvswitch/db.sock --private-key=db:Open_vSwitch
roo
More log output from ovs:
2017-12-13T12:40:23.502Z|5|dpif(revalidator20)|WARN|system@ovs-system:
failed to put[modify] (Invalid argument)
ufid:684991e8-860e-44eb-ab44-bd8bd41520e1
recirc_id(0),dp_hash(0/0),skb_priority(0/0),in_port(3),skb_mark(0/0),ct_state(0/0),ct_zone(0/0),ct_mark(0/0),ct
And some more testing:
xenial: ovs 2.8.1 + 4.4 - OK
xenial: ovs 2.8.1 + 4.10 - OK
so the issue appears to be the combination of ovs 2.8.1 (and 2.8.0) with
the 4.13 kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
1 - 100 of 155 matches
Mail list logo