I was asked to also recheck:
Working on artful for me as well:
[...]
root@cpaelzer-artful:/home/ubuntu/xfstests-dev# ./check tests/xfs/073
FSTYP -- xfs (non-debug)
PLATFORM -- Linux/ppc64le cpaelzer-artful 4.11.0-10-generic
MKFS_OPTIONS -- -f -bsize=4096 /dev/loop1
MOUNT_OPTIONS
I have the same issue on my Dell XPS 9560. It has been running fine in
"intel" graphics mode up until and including kernel 4.8. With 4.10 and
4.11 it either freezes pre-boot, before I even reach the FDE password
prompt, or, if I uninstall the nvidia drivers, it freezes at some point
after.
Try it here:
http://people.canonical.com/~khfeng/pm961-quirks/
--
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/1705748
Title:
Samsung SSD 960 EVO 500GB refused to change power state
4.4.0-1033.42 - aws
Regression test CMPL.
http://kernel.ubuntu.com/testing/tracker-index.html
Issue to note in x86_64 (aws):
libhugetlbfs - 1 failed (brk_near_huge), Killed by signal 15, bad
configuration 3
ubuntu_lxc - Failed to start networking in ubuntu-cloud container
** Changed in:
Public bug reported:
>From the test log, it looks like this test get stuck on s390x zVM and
zKVM (kernel03, s2lp6g003) for a couple hours with zesty kernel.
01:14:28 DEBUG| Running
'/home/ubuntu/autotest/client/tests/ubuntu_sysdig_smoke_test/ubuntu_sysdig_smoke_test.sh'
01:14:28 DEBUG| [stdout]
Public bug reported:
Numatop now supports ppc64el functionality, however the packaging does
not enable this.
** Affects: linux (Ubuntu)
Importance: High
Assignee: Colin Ian King (colin-king)
Status: In Progress
** Changed in: linux (Ubuntu)
Status: New => In Progress
Why should this have changed. This anoying bug is existing since 15.10
and even if there are several tickets nobody funkin cares!
https://bugs.launchpad.net/ubuntu/+source/linux-lts-wily/+bug/1583191
https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1579803
And yes i'm not dump. I
** Tags added: zesty
--
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/1714190
Title:
ubuntu_sysdig_smoke_test stuck on Zesty s390x zKVM / zVM
Status in linux package in Ubuntu:
In
** 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/1714190
Title:
ubuntu_sysdig_smoke_test stuck on Zesty s390x zKVM / zVM
** Changed in: linux (Ubuntu)
Status: New => In Progress
--
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/1714190
Title:
ubuntu_sysdig_smoke_test stuck on Zesty s390x zKVM / zVM
--- Comment From hbath...@in.ibm.com 2017-08-31 04:54 EDT---
(In reply to comment #22)
> Hi, Hari.
Hello Cascardo,
>
> My understanding is that the kernel should handle that. Otherwise, whenever
Sadly, it can't as kexec-tools is the one that creates elf headers for
/proc/vmcore.
So,
I would say this issue might be difficult to reproduce.
For kernel03, it has failed for 2 times and passed on the third run.
For s2lp6g003 it has passed on the first run, but stuck on the second.
--
You received this bug notification because you are a member of Kernel
Packages, which is
** 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/1713467
Title:
linux-aws: 4.4.0-1033.42
I think the hang is because the sysdig trace log fills the drive and
there is no more free space for the test run continue. I'll try and
limit this somehow and see if that helps
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Originally can't read PCI status:
Aug 15 14:14:02 phs08 kernel: [ 2477.191603] nvme :01:00.0: controller is
down; will reset: CSTS=0x, PCI_STATUS=0x
Now only controller is dead:
Aug 30 09:35:19 phs08 kernel: [71904.271956] nvme nvme0: controller is down;
will reset:
Artful 4.12 kernel still display these errors:
kernel: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure,
AE_NOT_FOUND (20170303/dswload-210)
kernel: ACPI Exception: AE_NOT_FOUND, During name lookup/catalog
(20170303/psobject-241)
kernel: ACPI Exception: AE_NOT_FOUND,
So instead of downgrading my BIOS, I've updated it from 1.2.29 to
version 1.3.0 which was released two days ago by DELL for the XPS15
9550. USB ports at the TB16 is now working without issues again.
I don't get any checksum errors, too:
for i in 1 2 3 4; do curl -s
When you had the nvidia drivers installed, can you confirm how you
installed them?
--
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/1697556
Title:
Computer freezes after login -
Well, I'm running 4.10.0-33-generic, and although sometimes I have to
login twice, and it has frozen on a couple of occasions, it's pretty
much okay. So I'm not sure what exactly is different about my combo than
yours, except maybe the firmware version I'm running on the 9560.
--
You received
@Sam, is this still an issue now? Can we close this bug?
--
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/1704720
Title:
ubuntu_lttng_smoke_test failed on Artful 4.11.0-11
Status in
Public bug reported:
On node lodygin, run:
sudo /sbin/hwclock --set --date "2/2/80 03:04:00"
Will set the date to 2/2/2080. Thus it failed the hwclock test, which
expect the output of 1980
This only happen on lodygin, other testing nodes (hainzel, rumford,
rizzo, fozzie) are good.
This issue
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/1714229
Title:
hwclock will set the date to
Hey Joseph,
after we switched to Kernel 4.4.0-31-generic everything is working fine
for now. I think we can close this bugreport because the bug is related
to the GPFS Kernel Modules which weren't tested properly on
4.4.0-87-generic.
Thanks for your support!
Regards,
Erik
--
You received this
** Package changed: linux (Ubuntu) => linux-azure (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/1690136
Title:
Azure: make it possible to boot without initrd
Status in
Proprietary driver (as well as simply disabling Wayland and using X with
Nouveau) fixes this issue. Perhaps for now Wayland should be blacklisted
for this card (and other cards that have this same issue).
--
You received this bug notification because you are a member of Kernel
Packages, which is
With https://github.com/fho/docker-samba-loop I was able to reproduce
kernel Oopses on a clean Ubuntu 16.0.4 installation with:
- linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1
- linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1
On 4.11.0-14 it was much harder to reproduce. Sometimes only a
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
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Stefan Bader (smb)
** Changed in: linux (Ubuntu)
Status: New => Invalid
**
** Attachment removed: "4827E1007C3C6FEF.jpg"
https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/711397/+attachment/4928025/+files/4827E1007C3C6FEF.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to b43-fwcutter in Ubuntu.
*** This bug is a duplicate of bug 1711535 ***
https://bugs.launchpad.net/bugs/1711535
4.4.0-94.117 has solved the problem so I'll mark this as a duplicate of
LP: #1711535 (update to stable kernel 4.4.82).
** This bug has been marked a duplicate of bug 1711535
Xenial update to 4.4.82
This bug was fixed in the package makedumpfile - 1:1.5.9-5ubuntu0.5
---
makedumpfile (1:1.5.9-5ubuntu0.5) xenial; urgency=medium
* Build on arm64. While this version of makedumpfile doesn't support
creating filtered dumps of Ubuntu arm64 kernels, it does satisfy
the
At first glance, it seems the problem seems to be introduce with
commit[1].
I notice the problem while running the sosreport kernel plugin[2] on a
system with apparmor disable (apparmor=0).
[1] - commit
commit a3c6147c6f4132e943db2cff4e1a85887277fc2a
Author: John Johansen
I was also able to reproduce using the above reproducer[1]
[1] - cat /sys/module/apparmor/parameters/audit
I think the problem here is that files in apparmor shouldn't be writable
while apparmor is disable.
-rw---
If I do :
# chmod 400 /sys/module/apparmor/parameters/audit (-r--)
I was also able to reproduce using the above reproducer[1]
[1] - cat /sys/module/apparmor/parameters/audit
I think the problem here is that files in apparmor shouldn't be writable while
apparmor is disable.
(-rw---)
If I do :
# chmod 400 /sys/module/apparmor/parameters/audit (-r)
This bug was fixed in the package makedumpfile - 1:1.5.9-5ubuntu0.5
---
makedumpfile (1:1.5.9-5ubuntu0.5) xenial; urgency=medium
* Build on arm64. While this version of makedumpfile doesn't support
creating filtered dumps of Ubuntu arm64 kernels, it does satisfy
the
The verification of the Stable Release Update for makedumpfile has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
** Changed in: linux (Ubuntu)
Status: Triaged => 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/1713103
Title:
snapd 2.27.3+17.10 ADT test failure with linux
Public bug reported:
Issues with doing initial system updates.
ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu11
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.7
** 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/1713821
Title:
arm64 arch_timer fixes
Status in linux package
Has this also been verified with Ubuntu 17.04? While its unlikely people
are upgrading from 16.04 to 17.04 it is an upgrade path and we should
ensure this fix does not regress and release these updates together.
--
You received this bug notification because you are a member of Kernel
Packages,
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1714317
Title:
package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu11 failed to
install/upgrade:
Attached are the logs for an Oops on Ubuntu 14.04 on kernel linux-
image-4.4.0-93-generic=4.4.0-93.116~14.04.1
** Attachment added: "kernoops-4.4.0-93.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407/+attachment/4941963/+files/kernoops-4.4.0-93.txt
--
You received this bug
@Brian, Yes indeed I have performed exhaustive testing on this on
Xenial, Zesty, Artful. A full exhaustive test takes 5 hours and I have
performed the upgrade steps and checked this out.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
--- Comment From gwal...@br.ibm.com 2017-08-31 16:01 EDT---
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709171/comments/6
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I built a Zesty test kernel with the requested two commits,
03e262798884b0a5f948b17433afd80606cb3497 and
f759741d9d913eb57784a94b9bca78b376fc26a9. The also required a prereq
commit to built properly: b1d2dc5659b41741f5a29b2ade76ffb4e5bb13d8.
The test kernel can be downloaded from:
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin1710
--
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/1707875
Title:
include support for Python bindings in
** Tags removed: targetmilestone-inin1610
** Tags added: targetmilestone-inin1710
--
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/1630304
Title:
Ubuntu 16.10 KVM: Issue doing hotplug
Public bug reported:
bcmwl-kernel-source worked correctly on the original 16.04 LTS kernel,
but no longer works on the hwe kernel (4.10.0-33). I am using the b43
open source driver temporarily in order to file this report.
Description:Ubuntu 16.04.3 LTS
Release:16.04
--- Comment From ru...@us.ibm.com 2017-08-31 17:54 EDT---
Closing this bug against 16.10 as it is EOL and linux-crashdump has been
updated for zesty.
** Tags removed: targetmilestone-inin1610
** Tags added: targetmilestone-inin1704
--
You received this bug notification because you are
Laptop info:
description: Notebook
product: 0769AK8 (Lenovo)
vendor: LENOVO
version: 3000 N200
serial: redacted
width: 64 bits
capabilities: smbios-2.4 dmi-2.4 vsyscall32
configuration: boot=oem-specific chassis=notebook family=Lenovo sku=Lenovo
uuid=redacted
*-core
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
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** No longer affects: gnome-shell (Ubuntu)
** Tags added: nouveau
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages,
That does seem to make the problem go away.
--
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/1701486
Title:
System brightness slider doesn't work any more
Status in linux package in
Public bug reported:
[0.00] Linux version 4.4.0-93-generic (buildd@bos01-ppc64el-025)
(gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) )
#116-Ubuntu SMP Fri Aug 11 16:30:16 UTC 2017 (Ubuntu
4.4.0-93.116-generic 4.4.79)
...
[ 380.184554] KVM guest htab at c0799900
Feel free to do so. Currently I don't have enough time to investigate
which specific parameter(s) caused the issue. Thanks for your help!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
So I guess we can close the 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/1701486
Title:
System brightness slider doesn't work any more
Status in linux package in Ubuntu:
** Changed in: linux (Ubuntu)
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/1701486
Title:
System brightness slider doesn't work any more
Status in
--- Comment From furma...@us.ibm.com 2017-09-01 00:40 EDT---
I tested the test kernel made available by jsalisbury and it worked for me as
well.
This is a pretty big blocker - very much hoping this makes it into a new
kernel soon.
--
You received this bug notification because you are a
58 matches
Mail list logo
