Do we have a plan when this will be fixed?
--
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/1530405
Title:
NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]
Status in
** Changed in: hwe-next
Status: New => 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/1622469
Title:
New device ID for Kabypoint
Status in HWE Next:
Fix Committed
All kernels after 4.7.4 have this exact same issue with Broadwell
integrated graphics, including the official 4.8 release and the previous
rc builds.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
Yes, this is with the kernel from #26
--
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/1602577
Title:
[arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel
Status in linux
Dear Joseph
I download (http on firefox) and installed using Ubuntu Software
the
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8/linux-
headers-4.8.0-040800_4.8.0-040800.201610022031_all.deb
and
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8/linux-
headers-4.8.0-040800-generic_4.8.0-040
It's not fixed in the 4.8.0-generic kernel. Additionally, that kernel
shows flickering artefact windows when using two monitors, as reported
here: https://bugs.freedesktop.org/show_bug.cgi?id=97596
** Bug watch added: freedesktop.org Bugzilla #97596
https://bugs.freedesktop.org/show_bug.cgi?id=
Tested against 4.8.0-040800-generic_4.8.0-040800.201610022031_amd64.deb
and the touchpad is still unresponsive and is bot recognized (doesn't
exist in proc/bus/input/devices)
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You re
I tried kernel 4.8, but i have same error as in v4.4.
I switched back to v4.4 as my graphics driver (nvidia) not working with
new kernel (on login, i get logged off to login screen again and low
resolution).
root@hon-pc-01:~# dpkg -l | grep linux-image | grep ii
ii linux-image-4.4.0-36-generic
** 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/1589997
Title:
The device on /dev/sdx is not created when inserting ne
Michael H Wilson, if the WORKAROUND doesn't help you, then you have a
different problem that this report is not scoped to.
Hence, it will help immensely if you filed a new report with the Ubuntu
repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux
Please feel free to subscr
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Xenial)
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/b
The kernel was up for 4:44 without rebooting, so I deem it a success.
** Tags added: kernel-fixed-upstream
--
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/1629482
Title:
4.4.0-38-generic
Hi Joseph, I tested 4.4.23 from mainline, WiFi and Bluetooth remain
undetected, I'm currently on 4.8 RC8 where both work fine (only battery
life is bad). Let me know in case you want output of certain commands on
4.4.23. Meanwhile, I'm adding the tag as you said. Thanks!
** Tags added: kernel-bug-
tests ran: 35, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-41.61/onza__4.4.0-41.61__2016-10-04_02-51-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/bugs/1628204
Hmm, looking at the kernel source this seems intentional. See commit
76bc8e2843b66f8205026365966b49ec6da39ae7.
--
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/1629509
Title:
Cannot mount
Yes, exists in 4.4.23-040423-generic as well.
--
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/1629509
Title:
Cannot mount overlay with upperdir on overlay
Status in linux package in Ubun
The attached JournalErrors.txt file shows the kernel call trace for the
error that occurs.
** 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.
@pitti, the ID_FS_TYPE is zfs_member, not zfs. The service is, as you
listed, zed.service. Modifying your rule then is:
ACTION!="remove", SUBSYSTEM=="block", ENV{ID_FS_TYPE}=="zfs_member",
ENV{SYSTEMD_WANTS}+="zed.service"
However, if zed.service is going to exit if there is no pool imported,
thi
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1630063/+attachment/4753779/+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: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1630063/+attachment/4753778/+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/1630063
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1630063/+attachment/4753773/+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/1630063
Ti
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1630063/+attachment/4753783/+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/1630063/+attachment/4753774/+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
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1630063/+attachment/4753776/+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: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1630063/+attachment/4753781/+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: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1630063/+attachment/4753780/+files/ProcEnviron.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: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1630063/+attachment/4753775/+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/16
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1630063/+attachment/4753785/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1630063/+attachment/4753777/+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/1630063
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1630063/+attachment/4753784/+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/1630063
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1630063/+attachment/4753782/+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
** Tags added: apport-collected yakkety
** Description changed:
2 USB ports randomly disconnect and don't reconnect (it's always the
same two), and in dmesg all I get is
"
[ 1276.916458] ohci-pci :00:12.0: HcDoneHead not written back; disabled
[ 1276.916467] o
Todays (03.10.2016) daily iso is still unbootable on my G5, though it is
a lot more verbose about not finding a media containing a live
filesystem. See attatched screenshot.
Now as I see theres error messenges I rememember the same error happened
during the beta phase of Ubuntu MATE 16.04 too, at
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1630063
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
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1630069
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
Public bug reported:
The regression tests are currently hard coded to the semantics of mmap
in binfmt_elf
With the recent upstream commit 9f834ec18defc369d73ccf9e87a2790bfa05bf46
the cred used for the mmap changed resulting in test failures. The tests
have been patched for this change but it resu
Downloaded kernel 4.4.23, rebooted in it, compiled in zfs, waiting now
to see if it reboots or not. So far it was up for 40 minutes. If
everything goes well, I'll wait several hours, and mark the ticket as
instructed. If not, I'll mark ticket as instructed faster. :-)
--
You received this bug not
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-armadaxp in
** Package changed: linux-meta (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/1630063
Title:
specific USB devices disconnect and don't reconnect
Status in lin
Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-testing/precise/3.2.0-111.153
/precise-proposed-frozen.html
** Tags added: certification-testing-passed
** Changed in: kernel-sru-
Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-
testing/precise/3.13.0-97.144~precise1/precise-3.13-proposed-frozen.html
** Tags added: certification-testing-passed
** Changed i
Public bug reported:
2 USB ports randomly disconnect and don't reconnect (it's always the
same two), and in dmesg all I get is
"
[ 1276.916458] ohci-pci :00:12.0: HcDoneHead not written back; disabled
[ 1276.916467] ohci-pci :00:12.0: HC died; cleaning up
[ 1276.916553] usb 3-1: USB disco
Just ran Memcheck86 that is included with 16.04. Passed.
--
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/1627217
Title:
ipv6 forwarding kernel oops
Status in linux package in Ubuntu:
I still get a panic as shown in the last 2 included files on 4.8.0.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags removed: staging
** Tags added: stagingkernel-bug-exists-upstream
--
You received this bug notification because you are a member of Kernel
Packages, w
all is good on yakkety too
** Changed in: dpkg (Ubuntu Yakkety)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Yakkety)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I have the same problem that Brian described as "Broken recovery mode
(the main issue)". I'm not aware of anything being wrong with my UEFI-
boot or my partitions, so I don't think this is directly related.
I'd really appreciate a working recovery-mode, too. If there's any
information I could prov
** Changed in: dpkg (Ubuntu Yakkety)
Assignee: Dimitri John Ledkov (xnox) => (unassigned)
--
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/1620525
Title:
sbuild with overlayfs fails i
Second Crash (took longer)
** Attachment added: "wormhole_crash_4.8.0-2.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627217/+attachment/4753723/+files/wormhole_crash_4.8.0-2.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
Public bug reported:
[Impact]
Link establishment is delayed during initialization, possibly resulting in
remote fault conditions that may cause the interface to fail to come up.
[Test Case]
Put the system in a reboot loop and watch for a remote fault condition, or a
failure to bring up the link
One crash
** Attachment added: "wormhole_crash_4.8.0.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627217/+attachment/4753722/+files/wormhole_crash_4.8.0.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
4.4.0-38.57 overlayfs sbuild appears to be good.
** Changed in: dpkg (Ubuntu Yakkety)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
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 to do it tommorrow.. 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/1626970
Title:
Graphics not working after upgrade
Status in linux package in Ubuntu:
Incomplete
B
ubuntu@ubuntu:/tmp/x$ gunzip < /boot/initrd.img-4.4.0-41-generic | cpio -i -d
197785 blocks
ubuntu@ubuntu:/tmp/x$ find | grep qed
./lib/firmware/qed
./lib/firmware/qed/qed_init_values_zipped-8.4.2.0.bin
./lib/modules/4.4.0-41-generic/kernel/drivers/net/ethernet/qlogic/qede
./lib/modules/4.4.0-41-ge
** Bug watch added: Linux Kernel Bug Tracker #153171
http://bugzilla.kernel.org/show_bug.cgi?id=153171
** Changed in: linux
Remote watch: Linux Kernel Bug Tracker #175431 => Linux Kernel Bug Tracker
#153171
--
You received this bug notification because you are a member of Kernel
Packages, w
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1621719
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
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: High => Low
** Changed
Can you test the Yakkety proposed kernel and post back if it resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.
Thank you in advance!
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => High
** Tags added: kernel-d
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: High => Low
** Changed
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
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.8 kernel[0
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.8 kernel[0
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** 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/1625675
Title:
Trusty 'linux-virtual' kernel m
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.8 kernel[0
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: High => Low
** Changed
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.8 kernel[0
Built a custom linux 4.8-rc8 kernel and I have not seen this problem
since. This is most likely a kernel bug.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
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.8 kernel[0
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.8 kernel
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: High => Low
** Changed
Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v4.4 stable kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel d
** 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/1625177
Title:
OOPS on beaglebone on boot of 4.4.0-36-generic under snappy
** Changed in: linux-firmware (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1625157
Title:
QLogic qla2xxx firmware fails
Status in
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)
Status: Confirmed => Incomplete
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.8 kernel[0
Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v4.4 stable kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel d
This fix for this bug was cc'd to upstream stable. The fix should make
it's way into Xenial through the normal stable updates.
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
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.8 kernel[0
Can you see if this issue also happens with the latest daily image? It can be
downloaded from:
Desktop
http://cdimage.ubuntu.com/daily-live/current/
Server:
http://cdimage.ubuntu.com/ubuntu-server/daily/current/
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Tags added: kerne
Can you see if this issue also happens with the latest daily image? It can be
downloaded from:
Desktop
http://cdimage.ubuntu.com/daily-live/current/
Server:
http://cdimage.ubuntu.com/ubuntu-server/daily/current/
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Tags added: kern
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8 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 th
** 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/1626460
Title:
usb-devices | awk '/13d3/' RS=
Status in linux package in
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.8 kernel[0
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.8 kernel[0
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8 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 th
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.8 kernel[0
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.8 kernel[0
Can you test the Yakkety proposed kernel and post back if it resolves
this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed.
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Tags added: kernel-da-key
--
You received t
** Changed in: linux (Ubuntu Trusty)
Status: New => Confirmed
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) => Marcelo Cerri (mhcerri)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs
No, the only thing that affected the operation of the usb ports was the
vmware horizon software. I conjectured other things before finding the
root cause.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
So the problem is that zfs does its own loop mount handling without
using a loop device so without a block uevent...
Triggering on a uevent would only work for pools that are using physical
devices, not for those using file as loops, which is unfortunately a
rather common setup for LXD users who d
now it is about 23 mbit\s, but actually my wifi signal is about 100
mbit\s and my IPAD gets about 80 \ 100 (download\upload). I consider
that fix as good but there is a room for an improvement
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Con
So I tested linux 4.8 final and the regression still exists. On another
note I also tested linux 4.7 and the issue does not exist there.
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu Yakkety)
Status: Incomplete => Confirmed
--
You received this bug notification b
** Description changed:
/proc/$pid/maps experienced a significant performance regression for
processes with large numbers of threads between Precise and Trusty due
to an upstream bug. This behavior is currently blocking my ability to
upgrade to Trusty, as we depend on applications with wit
** Tags added: regression-testing-passed
** Changed in: kernel-sru-workflow/regression-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/16261
Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v4.4 stable kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel d
Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v4.4 stable kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel d
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.8 kernel[0
Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v4.4 stable kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel d
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.8 kernel[0
1 - 100 of 235 matches
Mail list logo
