tests ran: 19, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-77.98-generic/daedalus__4.4.0-77.98__2017-05-02_05-57-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
@jsalisbury: I figured it out...
We're talking about two issues here.
The first one is unable to set MTU larger than 1500 on some devices.
Commit e84f31d (yakkety), "net: centralize net_device min/max MTU
checking", introduced net_device.min_mtu and net_device.max_mtu. These
values will be check
tests ran: 16, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-77.98-generic/daedalus__4.4.0-77.98__2017-05-02_05-34-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
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/1687534
Title:
Mainline kernels no longer bui
Public bug reported:
>From 2017-04-27 onwards, the mainline kernels are failing to build, eg
see http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2017-05-02/
The error logged is:
dpkg-deb: error: obsolete compression type 'bzip2'; use xz or gzip
instead
ProblemType: Bug
DistroRelease: Ubun
Ya it's working for touchpad
--
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/1598637
Title:
Dell Inspiron touchpad not working
Status in linux package in Ubuntu:
Confirmed
Bug de
[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.
https://bugs.launchpad.net/bu
Here's what we need to do:
1. Install Ubuntu with 'nomodeset'.
2. Install and try latest mainline kernel.
3. If the issue happens, file an upstream bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
** Changed in: linux
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/1686099
Title:
connection flood to port 445 on mounting cifs volume under kernel
Stat
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: hwe-next
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
** Changed in: hwe-next
Status: New => Fix Released
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: hwe-next
Importance: Undecided => Critical
** Changed in: hwe-next
Assignee: (unassigned) => Shrirang Bagul (shrirang-bagul)
--
You received
** Changed in: hwe-next
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/1675327
Title:
Fix line-out port noise on Baytrail-I with RT5660 based s
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: hwe-next
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/16851
** Changed in: hwe-next
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/1676356
Title:
Channel data values for IIO based st_sensors (st_accel, st_
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: hwe-next
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.launchpad.net/bu
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: hwe-next
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.launchpad.net/bu
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: hwe-next
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.launchpad.net/bu
Will try the mainline kernel 4.10.12 With the load failure usually <45
minutes. Will let you know. 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/1674838
Title:
kernel BUG at
Thanks, Jesse. I'll investigate further. I'll probably try to
reproduce the bug to make debugging faster.
--
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/1679823
Title:
bond0: Invalid M
@David, maybe test 4.10.12 while I review that build failure:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10.12/
Others have reported this bug is fixed in mainline, so I was just
curious if the fix was also cc'd to upstream stable.
--
You received this bug notification because you are a mem
@Joseph Salisbury, the 4.10.0-21 kernel crapped out on me but with a
different error:
May 1 18:42:25 vancouver kernel: [28120.190864] BUG: unable to handle kernel
NULL pointer dereference at 0021
May 1 18:42:25 vancouver kernel: [28120.190895] IP:
dma_fence_wait_timeout+0x36/0xf0
M
It still fails with the kernel in #31.
$ uname -a
Linux cola 4.8.0-49-generic #52~lp1679823v2 SMP Mon May 1 21:32:12 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
$ dmesg | grep enp4s0
[1.197150] e1000e :04:00.0 enp4s0: renamed from eth0
[ 52.924244] enp4s0: Invalid MTU 9000 requested, hw max
Public bug reported:
We see a number of kernel panics on servers running Apache Mesos using
cgroups with small (0.1-0.2) cpu limits.
These all appear as NULL pointer dereferences in and around
pick_next_entity and pick_next_task_fair, for example:
[24334.493331] BUG: unable to handle kernel NULL
Looks like those builds are failing.
--
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/1674838
Title:
kernel BUG at /build/linux-
7LGLH_/linux-4.10.0/include/linux/swapops.h:129
Status i
Just attempting to install package results in:
root@edwardnewman-MacBookPro:~# dpkg -i
/var/cache/apt/archives/linux-headers-4.10.0-20_4.10.0-20.22_all.deb
(Reading database ... 194747 files and directories currently installed.)
Preparing to unpack .../linux-headers-4.10.0-20_4.10.0-20.22_all.deb
@jsalisbury
Ran steps with same result
root@edwardnewman-MacBookPro:~# apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
linux-headers-4.10.0-20
@David Bierce, can you give the 4.10.13 kernel a test? It is available
from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10.13/
--
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/1674838
After a review, Yakkety did get the following commits via other bug
reports:
d37117d ethernet: use net core MTU range checking in more drivers
6426a88 net: use core MTU range checking in virt drivers
89110d9 net: use core MTU range checking in virt drivers
e84f31d net: centralize net_device min/ma
** 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/1685373
Title:
package linux-headers-4.4.0-75-generic 4.4.0-75.96 failed to
install/upgrade: unable
** 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/1686053
Title:
package linux-headers-4.10.0-20 (not installed) failed to
install/upgrade: unable to
** 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/1687241
Title:
package linux-headers-4.10.0-20 (not installed) failed to
install/upgrade: unable to
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1685849
Title:
package linux-signed-image-4.10.0-19-generic 4.10.0-19.21 failed to
install/u
Using Joseph's kernel, I'm still running into the same issue.
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+attachment/4870532/+files/dmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscr
The issue started happening as soon as I started using the bluetooth
dongle on this laptop some days ago.
I have tested with latest upstream kernel, both lowlatency and generic,
and the issue is still there: it even happens sooner, just after I
reboot the laptop, no need to enter sleep mode.
So,
It appears commit 3331aa378e9 fixes commit 91572088e3fd. However,
commit 91572088e3fd was introduced in v4.10-rc1 and not cc'd to stable.
The Yakkety 4.8 kernel never had commit 91572088e3fd applied. That
explains why my test kernel did not fix this bug.
Comment #6 says that this same issue happ
Thanks for the testing feedback on my test kernel. I suspect more than
just commit 3331aa378e9bcbd0d16de9034b0c20f4050e26b4 is needed.
dev->max_mtu being set to ETH_MAX_MTU must be needed in other spots.
I'll investigate and post another test kernel shortly.
--
You received this bug notification
Of the kernels in the mainline ppa i can at the moment confirm that none above
v4.8.17 works (ie 4.8.17-040817-generic), and all of
- v4.9.24
- v4.9.25
- v4.10-rc1
- v4.10.8
- v4.10.12
- v4.10.13
have the bug present.
I'll come back with an update after I've tested the proposed v4.11-rc8 (
http:
kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1687256
Title:
byd touchpad no longer dete
** Description changed:
- When running on kernel 4.8.0-34 my Lafite byd touchpad is recognised
correctly and shows with xinput --list as BYDPS/2 BYD Touchpad.
+ When running on kernel 4.8.0-34 my Lafite byd touchpad is recognised
correctly and shows with xinput --list as BYDPS/2 BYD Touchpad.
Thanks for extracting the commit. And thanks for caring for this bug
report!
--
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/1685865
Title:
Can't login after boot with Kernel 4.11.0-rc7,
Thanks for testing. I'll ping upstream and the patch author for
feedback.
--
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/1685865
Title:
Can't login after boot with Kernel 4.11.0-rc7, so
I finally got time to get access to the computer again. I tried the
4.4.0-62 kernel from xenial-proposed and received "host adapter dead".
Since I last tested I see that 4.4.0-75 is available, so I tried that.
The system booted. It gave me some messages about scsi adapter reset and
a messag about
I downgraded to linux-image-4.4.0-66-generic and no longer have the
flooding issue.
--
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/1686099
Title:
connection flood to port 445 on mounting
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.11 kernel[
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
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/1686828
T
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
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/1686836
Title:
This kernel seems to fix the issue. I am able to login via the login
screen.
This is the output of "uname -a"
tisch@tisch-XPS-15-9560:~$ uname -a
Linux tisch-XPS-15-9560 4.11.0-041100-generic #201705010951 SMP Mon May 1
13:53:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: New => Triaged
--
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/1686838
Title:
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.11 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
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.11 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
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.11 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
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.11 kernel[
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.11 kernel[
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Also affects: linux (Ubuntu Zesty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Zesty)
Status: New => Triaged
** Changed in: linux (Ubuntu Zesty)
Importance: Undecided => Medium
--
You re
You have been subscribed to a public bug:
On ASRock QC5000M-ITX/PH P1.10 and BIOSTAR Group A68N-2100 4.6.5 the
mouse cursor is displayed distorted since we upgraded to kernel linux-
image-4.4.0-75-generic:amd64
We use 32bit Xubuntu 14.04.5 with 64bit Kernel on about 150 machines.
Core2Duo, Celero
Do you have a way to reproduce the oops, or was it a one time event?
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.11 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
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
** Ch
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** 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/1680904
Title:
zesty unable to handle kernel
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.11 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
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.11 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
Can you see if this bug still exists if you install the latest 17.04
kernel, which can be downloaded from:
https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/+build/12451317
To test this kernel, you need to install both the linux-image and linux-
image-extra .deb packages.
** Chan
Do you have a way to reproduce the bug, or was it a one time event?
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
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/1687383
T
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.11 kernel[
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for tra
Yes, the bisect reported commit da2ba564a6dcf46df4f828624ff55531ff11d5b0
as the culprit. To see if that is the case, I built a kernel with that
commit reverted.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1685865/
Can you test that kernel and report back if it
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for tra
FYI, I switched to the mainline build of 4.10.11 and did *not*
experience this issue. Today I tried to switch back to linux-
image-4.10.0-20-generic (4.10.0-20.22) to see if it had been fixed, and
hit the bug again within a few minutes. Trying out jsalisbury's -21
build now.
Running the mainline
This bug was fixed in the package linux - 4.8.0-51.54
---
linux (4.8.0-51.54) yakkety; urgency=low
* linux: 4.8.0-51.54 -proposed tracker (LP: #1686070)
* [Hyper-V][SAUCE] pci-hyperv: Use only 16 bit integer for PCI domain
(LP: #1684971)
- SAUCE: pci-hyperv: Use only 16 b
This bug was fixed in the package linux - 4.4.0-77.98
---
linux (4.4.0-77.98) xenial; urgency=low
* linux: 4.4.0-77.98 -proposed tracker (LP: #1686040)
* [Hyper-V][SAUCE] pci-hyperv: Use only 16 bit integer for PCI domain
(LP: #1684971)
- SAUCE: pci-hyperv: Use only 16 bi
This bug was fixed in the package linux - 4.8.0-51.54
---
linux (4.8.0-51.54) yakkety; urgency=low
* linux: 4.8.0-51.54 -proposed tracker (LP: #1686070)
* [Hyper-V][SAUCE] pci-hyperv: Use only 16 bit integer for PCI domain
(LP: #1684971)
- SAUCE: pci-hyperv: Use only 16 b
This bug was fixed in the package linux - 4.8.0-51.54
---
linux (4.8.0-51.54) yakkety; urgency=low
* linux: 4.8.0-51.54 -proposed tracker (LP: #1686070)
* [Hyper-V][SAUCE] pci-hyperv: Use only 16 bit integer for PCI domain
(LP: #1684971)
- SAUCE: pci-hyperv: Use only 16 b
This bug was fixed in the package linux - 4.4.0-77.98
---
linux (4.4.0-77.98) xenial; urgency=low
* linux: 4.4.0-77.98 -proposed tracker (LP: #1686040)
* [Hyper-V][SAUCE] pci-hyperv: Use only 16 bit integer for PCI domain
(LP: #1684971)
- SAUCE: pci-hyperv: Use only 16 bi
This bug was fixed in the package linux - 4.4.0-77.98
---
linux (4.4.0-77.98) xenial; urgency=low
* linux: 4.4.0-77.98 -proposed tracker (LP: #1686040)
* [Hyper-V][SAUCE] pci-hyperv: Use only 16 bit integer for PCI domain
(LP: #1684971)
- SAUCE: pci-hyperv: Use only 16 bi
This bug was fixed in the package linux - 4.4.0-77.98
---
linux (4.4.0-77.98) xenial; urgency=low
* linux: 4.4.0-77.98 -proposed tracker (LP: #1686040)
* [Hyper-V][SAUCE] pci-hyperv: Use only 16 bit integer for PCI domain
(LP: #1684971)
- SAUCE: pci-hyperv: Use only 16 bi
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve
Langasek (vorlon)
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1686070 ***
https://bugs.launchpad.net/bugs/1686070
This bug was fixed in the package linux - 4.8.0-51.54
---
linux (4.8.0-51.54) yakkety; urgency=low
* linux: 4.8.0-51.54 -proposed tracker (LP: #1686070)
* [Hyper-V][SAUCE] pci-hyperv: Use
** Changed in: kernel-sru-workflow/promote-to-security
Status: Confirmed => 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/1686040
Title:
linux: 4.4.0-77.98 -proposed trac
** Changed in: kernel-sru-workflow/promote-to-security
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubunt
*** This bug is a duplicate of bug 1679823 ***
https://bugs.launchpad.net/bugs/1679823
** This bug has been marked a duplicate of bug 1679823
bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49)
--
You received this bug notification because you are a member of Ker
Sorry, I mis-read the git commit history for this kernel, it does NOT
need to go to the yakkety-security pocket. I am unable to change the
status of the security-signoff task to Invalid.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
Does not need to be copied to security pocket.
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => 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/1686
@Joseph Salisbury, I'm running the 4.10.0-21 kernel now. Let's see what
happens.
--
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/1674838
Title:
kernel BUG at /build/linux-
7LGLH_/linux
Needs to be copied to the yakkety security pocket.
** Changed in: kernel-sru-workflow/security-signoff
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/
Cannot run:
apport-collect 1687113
As described in the initial bug report, Ubuntu Desktop 17.04 is no
longer installed on the subject machine.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
This is a quick respin and no need for Cert. testing
** Tags added: regression-testing-passed
** Changed in: kernel-sru-workflow/certification-testing
Status: In Progress => Invalid
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Fix Released
** Change
Respin, no need for Cert. testing
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/certification-testing
Status: In Progress => Invalid
** Tags added: regression-testing-passed
** Changed in: kernel-sru-wo
any news about kernel 4.10.0-20 to fix also openvswitch interfaces (bug
1685742) ?
--
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/1679823
Title:
bond0: Invalid MTU 9000 requested, hw max
Can folks affected by this bug test the 4.10.0-21 kernel? It can be
downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1674838/
--
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/1674838
If you reboot (or unmount/remount) with the "ls every minute" cron job
active, it should prevent the timeout on the share and not reach the
keep-alive echo that starts the flood. I think it is about the
15-minute mark (of inactivity) where the client starts the echo flood.
--
You received this b
I did try to install the upstream kernel linux-
image-4.11.0-041100rc8-generic_4.11.0-041100rc8.201704232131_amd64.deb
and linux-
headers-4.11.0-041100rc8-generic_4.11.0-041100rc8.201704232131_amd64.deb
but unfortunately the system barely boots and the networking is messed
up after the change. I c
It seems I can reproduce this bug now. I'm in the process of "Reverse"
bisecting now, which will identify the commit(s) in mainline that fix
this and are needed in Zesty.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ht
*** This bug is a duplicate of bug 1674838 ***
https://bugs.launchpad.net/bugs/1674838
** This bug has been marked a duplicate of bug 1674838
kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129
--
You received this bug notification because you are a member of Kernel
@jsalisbury: I can still reproduce this issue with the kernel in #12...
$ uname -a
Linux cola 4.8.0-49-generic #52~lp1679823 SMP Tue Apr 25 17:29:26 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
$ dmesg | grep enp4s0
[1.194350] e1000e :04:00.0 enp4s0: renamed from eth0
[ 53.469795] enp4s0: In
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1687113
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a commen
** Package changed: ubiquity (Ubuntu) => linux (Ubuntu)
--
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/1687113
Title:
Ubuntu 17.04 install cannot connect to internet
Status in linux pac
You have been subscribed to a public bug:
I encountered a problem when trying to install Ubuntu Desktop 17.04 on a
HP Pavilion g7 Notebook with 8 Gigs of memory, on a disk that had been
completely wiped clean. Basically, the installation CD could not connect
to the Internet. I tried both a wired E
I think I encountered the same thing. The screen would not wake up
though I could still ssh to the system, a lot of commands were not
working, they would just hang or do nothing. Had to resort to a hard
reset. The crash just continued to loop over and over again in the logs
4/30/17 11:11 PM
Can folks affected by this bug see if it is fixed with the kernel posted
in comment #12? To test that kernel you would need to install both the
linux-image and linux-image-extra .deb packages. You should see this
bug number in the output of uname -a if it the kernel is installed and
booted.
--
My workaround may have added some time, but eventually the share
dismounted :(
--
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/1686099
Title:
connection flood to port 445 on mounting cifs
1 - 100 of 132 matches
Mail list logo