[Kernel-packages] [Bug 1864164] virt-customize debug log on vanilla ubuntu 19.10
Default Comment by Bridge ** Attachment added: "virt-customize debug log on vanilla ubuntu 19.10" https://bugs.launchpad.net/bugs/1864164/+attachment/5330003/+files/virt-customize.debug.log ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: 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/1864164 Title: virt-customize fails with "host cpu (x86_64) and guest arch (s390x) are not compatible" when running on s390x host Status in linux package in Ubuntu: New Bug description: Problem was created vanilla ubuntu 19.10 kernel and release level qemu and libguestfs-tools. I tried a few different qcows and the result was the same. See attached for complete debug output. root@linux01:~# cat /etc/os-release | grep VERSION= VERSION="19.10 (Eoan Ermine)" root@linux01:~# uname -r 5.3.0-40-generic root@linux01:~# qemu-system-s390x --version QEMU emulator version 4.0.0 (Debian 1:4.0+dfsg-0ubuntu9.4) Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers root@linux01:~# apt show libguestfs-tools Package: libguestfs-tools Version: 1:1.40.2-2ubuntu6 root@linux01:~# virt-customize --version virt-customize 1.40.2 root@linux01:~# virt-customize -a rhel-guest-image-8.1-263.s390x.qcow2 --run-command 'touch virt-hello.txt' [ 0.0] Examining the guest ... [ 1.6] Setting a random seed [ 1.6] Running: touch virt-hello.txt virt-customize: error: host cpu (x86_64) and guest arch (s390x) are not compatible, so you cannot use command line options that involve running commands in the guest. Use --firstboot scripts instead. If reporting bugs, run virt-customize with debugging enabled and include the complete output: virt-customize -v -x [...] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864163] [NEW] Ubuntu 18.04.4. with Podman getting OCI runtime permission denied error
Public bug reported:
Ubuntu 18.04.4. with Podman getting OCI runtime permission denied error
While installing podman on Ubuntu 18.04.1 I get this error msg:
STEP 19: CMD ["batch"]
--> Using cache 6a4998c7b02676feaa68a0865618312b635a648a062d21600b1fd7646f645377
STEP 20: COMMIT opensslspeed
6a4998c7b02676feaa68a0865618312b635a648a062d21600b1fd7646f645377
Your kernel does not support swap limit capabilities,or the cgroup is not
mounted. Memory limited without swap.
Error: container_linux.go:346: starting container process caused
"process_linux.go:449: container init caused \"process_linux.go:415: setting
cgroup config for procHooks process caused \\\"failed to write -1 to
memory.memsw.limit_in_bytes: open
/sys/fs/cgroup/memory/machine.slice/libpod-100fc7a4b680e23e1050b2b00a2adaf58ac44bb68910637e0e47b895dd61f75d.scope/memory.memsw.limit_in_bytes:
permission denied\\\"\"": OCI runtime permission denied error
uname -a
Linux m42lp19 4.15.0-29-generic #31-Ubuntu SMP Tue Jul 17 15:42:24 UTC 2018
s390x s390x s390x GNU/Linux
podman info
host:
BuildahVersion: 1.11.3
CgroupVersion: v1
Conmon:
package: 'conmon: /usr/bin/conmon'
path: /usr/bin/conmon
version: 'conmon version 2.0.3, commit: unknown'
Distribution:
distribution: ubuntu
version: "18.04"
MemFree: 14549913600
MemTotal: 16869208064
OCIRuntime:
name: runc
package: 'cri-o-runc: /usr/lib/cri-o-runc/sbin/runc'
path: /usr/lib/cri-o-runc/sbin/runc
version: 'runc version spec: 1.0.1-dev'
SwapFree: 0
SwapTotal: 0
arch: s390x
cpus: 20
eventlogger: journald
hostname: m42lp19
kernel: 4.15.0-29-generic
os: linux
rootless: false
uptime: 6h 47m 47.24s (Approximately 0.25 days)
registries:
blocked: null
insecure: null
search:
- docker.io
- registry.fedoraproject.org
- registry.access.redhat.com
store:
ConfigFile: /etc/containers/storage.conf
ContainerStore:
number: 0
GraphDriverName: overlay
GraphOptions: {}
GraphRoot: /var/lib/containers/storage
GraphStatus:
Backing Filesystem: extfs
Native Overlay Diff: "true"
Supports d_type: "true"
Using metacopy: "false"
ImageStore:
number: 36
RunRoot: /var/run/containers/storage
VolumePath: /var/lib/containers/storage/volumes
Contact Information = danijel.so...@de.ibm.com
---uname output---
Linux m42lp19 4.15.0-29-generic #31-Ubuntu SMP Tue Jul 17 15:42:24 UTC 2018
s390x s390x s390x GNU/Linux
Machine Type = z14 lpar
---Debugger---
A debugger is not configured
---Steps to Reproduce---
sudo apt update && sudo apt upgrade
apt -y install software-properties-common
add-apt-repository -y ppa:projectatomic/ppa
apt -y install podman
curl
https://raw.githubusercontent.com/projectatomic/registries/master/registries.fedora
-o /etc/containers/registries.conf
sudo curl
https://raw.githubusercontent.com/containers/skopeo/master/default-policy.json
-o /etc/containers/policy.json
podman build --tag opensslspeed -f opensslspeed/Dockerfile && podman run -m
1024m --cpus=2 --rm -it opensslspeed
All steps from the Dockerfile are executed fine, the "Commit" steps
breaks.
Userspace tool common name: podman
The userspace tool has the following bit modes: 64
Userspace rpm: podman/bionic,now 1.6.2-1~ubuntu18.04~ppa1 s390x
Userspace tool obtained from project website: na
*Additional Instructions for danijel.so...@de.ibm.com:
-Attach ltrace and strace of userspace application.
This looks to be the same issue as
https://github.com/containers/crun/issues/187
i.e. Ubuntu needs to update to at least podman 1.6.3 or later.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Tags: architecture-s39064 bugnameltc-184012 severity-medium
targetmilestone-inin---
** Tags added: architecture-s39064 bugnameltc-184012 severity-medium
targetmilestone-inin---
** Changed in: ubuntu
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Package changed: 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/1864163
Title:
Ubuntu 18.04.4. with Podman getting OCI runtime permission denied
error
Status in linux package in Ubuntu:
New
Bug description:
Ubuntu 18.04.4. with Podman getting OCI runtime permission denied
error
While installing podman on Ubuntu 18.04.1 I get this error msg:
STEP 19: CMD ["batch"]
--> Using cache
6a4998c7b02676feaa68a0865618312b635a648a062d21600b1fd7646f645377
STEP 20: COMMIT opensslspeed
6a4998c7b02676feaa68a0865618312b635a648a062d21600b1fd7646f645377
Your kernel does not support swap limit capabilities,or the cgroup is not
mounted. Memory limited without swap.
Error: container_linux.go:346: starting container process caused
"process_linux.go:449: container init caused \"process_linux.go:415: setting
cgroup config
[Kernel-packages] [Bug 1864164] [NEW] virt-customize fails with "host cpu (x86_64) and guest arch (s390x) are not compatible" when running on s390x host
You have been subscribed to a public bug: Problem was created vanilla ubuntu 19.10 kernel and release level qemu and libguestfs-tools. I tried a few different qcows and the result was the same. See attached for complete debug output. root@linux01:~# cat /etc/os-release | grep VERSION= VERSION="19.10 (Eoan Ermine)" root@linux01:~# uname -r 5.3.0-40-generic root@linux01:~# qemu-system-s390x --version QEMU emulator version 4.0.0 (Debian 1:4.0+dfsg-0ubuntu9.4) Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers root@linux01:~# apt show libguestfs-tools Package: libguestfs-tools Version: 1:1.40.2-2ubuntu6 root@linux01:~# virt-customize --version virt-customize 1.40.2 root@linux01:~# virt-customize -a rhel-guest-image-8.1-263.s390x.qcow2 --run-command 'touch virt-hello.txt' [ 0.0] Examining the guest ... [ 1.6] Setting a random seed [ 1.6] Running: touch virt-hello.txt virt-customize: error: host cpu (x86_64) and guest arch (s390x) are not compatible, so you cannot use command line options that involve running commands in the guest. Use --firstboot scripts instead. If reporting bugs, run virt-customize with debugging enabled and include the complete output: virt-customize -v -x [...] ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-184002 severity-medium targetmilestone-inin2004 -- virt-customize fails with "host cpu (x86_64) and guest arch (s390x) are not compatible" when running on s390x host https://bugs.launchpad.net/bugs/1864164 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864163] [NEW] Ubuntu 18.04.4. with Podman getting OCI runtime permission denied error
You have been subscribed to a public bug:
Ubuntu 18.04.4. with Podman getting OCI runtime permission denied error
While installing podman on Ubuntu 18.04.1 I get this error msg:
STEP 19: CMD ["batch"]
--> Using cache 6a4998c7b02676feaa68a0865618312b635a648a062d21600b1fd7646f645377
STEP 20: COMMIT opensslspeed
6a4998c7b02676feaa68a0865618312b635a648a062d21600b1fd7646f645377
Your kernel does not support swap limit capabilities,or the cgroup is not
mounted. Memory limited without swap.
Error: container_linux.go:346: starting container process caused
"process_linux.go:449: container init caused \"process_linux.go:415: setting
cgroup config for procHooks process caused \\\"failed to write -1 to
memory.memsw.limit_in_bytes: open
/sys/fs/cgroup/memory/machine.slice/libpod-100fc7a4b680e23e1050b2b00a2adaf58ac44bb68910637e0e47b895dd61f75d.scope/memory.memsw.limit_in_bytes:
permission denied\\\"\"": OCI runtime permission denied error
uname -a
Linux m42lp19 4.15.0-29-generic #31-Ubuntu SMP Tue Jul 17 15:42:24 UTC 2018
s390x s390x s390x GNU/Linux
podman info
host:
BuildahVersion: 1.11.3
CgroupVersion: v1
Conmon:
package: 'conmon: /usr/bin/conmon'
path: /usr/bin/conmon
version: 'conmon version 2.0.3, commit: unknown'
Distribution:
distribution: ubuntu
version: "18.04"
MemFree: 14549913600
MemTotal: 16869208064
OCIRuntime:
name: runc
package: 'cri-o-runc: /usr/lib/cri-o-runc/sbin/runc'
path: /usr/lib/cri-o-runc/sbin/runc
version: 'runc version spec: 1.0.1-dev'
SwapFree: 0
SwapTotal: 0
arch: s390x
cpus: 20
eventlogger: journald
hostname: m42lp19
kernel: 4.15.0-29-generic
os: linux
rootless: false
uptime: 6h 47m 47.24s (Approximately 0.25 days)
registries:
blocked: null
insecure: null
search:
- docker.io
- registry.fedoraproject.org
- registry.access.redhat.com
store:
ConfigFile: /etc/containers/storage.conf
ContainerStore:
number: 0
GraphDriverName: overlay
GraphOptions: {}
GraphRoot: /var/lib/containers/storage
GraphStatus:
Backing Filesystem: extfs
Native Overlay Diff: "true"
Supports d_type: "true"
Using metacopy: "false"
ImageStore:
number: 36
RunRoot: /var/run/containers/storage
VolumePath: /var/lib/containers/storage/volumes
Contact Information = danijel.so...@de.ibm.com
---uname output---
Linux m42lp19 4.15.0-29-generic #31-Ubuntu SMP Tue Jul 17 15:42:24 UTC 2018
s390x s390x s390x GNU/Linux
Machine Type = z14 lpar
---Debugger---
A debugger is not configured
---Steps to Reproduce---
sudo apt update && sudo apt upgrade
apt -y install software-properties-common
add-apt-repository -y ppa:projectatomic/ppa
apt -y install podman
curl
https://raw.githubusercontent.com/projectatomic/registries/master/registries.fedora
-o /etc/containers/registries.conf
sudo curl
https://raw.githubusercontent.com/containers/skopeo/master/default-policy.json
-o /etc/containers/policy.json
podman build --tag opensslspeed -f opensslspeed/Dockerfile && podman run -m
1024m --cpus=2 --rm -it opensslspeed
All steps from the Dockerfile are executed fine, the "Commit" steps
breaks.
Userspace tool common name: podman
The userspace tool has the following bit modes: 64
Userspace rpm: podman/bionic,now 1.6.2-1~ubuntu18.04~ppa1 s390x
Userspace tool obtained from project website: na
*Additional Instructions for danijel.so...@de.ibm.com:
-Attach ltrace and strace of userspace application.
This looks to be the same issue as
https://github.com/containers/crun/issues/187
i.e. Ubuntu needs to update to at least podman 1.6.3 or later.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Tags: architecture-s39064 bugnameltc-184012 severity-medium
targetmilestone-inin---
--
Ubuntu 18.04.4. with Podman getting OCI runtime permission denied error
https://bugs.launchpad.net/bugs/1864163
You received this bug notification because you are a member of Kernel Packages,
which is subscribed to linux in Ubuntu.
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862776] Re: [MIR] alsa-ucm-conf & alsa-topology-conf (b-d of alsa-lib)
1.2.1.2-2 is old now. The latest version is 1.2.2. Hello all, new ALSA userspace packages were released. You may download them from the ALSA website http://www.alsa-project.org or directly from the FTP server ftp://ftp.alsa-project.org/pub . Full list of changes: http://www.alsa-project.org/main/index.php/Changes_v1.2.1.2_v1.2.2 Have fun, Jaroslav -- You received this bug notification because you are a member of Kernel Packages, which is a bug assignee. https://bugs.launchpad.net/bugs/1862776 Title: [MIR] alsa-ucm-conf & alsa-topology-conf (b-d of alsa-lib) Status in alsa-topology-conf package in Ubuntu: New Status in alsa-ucm-conf package in Ubuntu: New Bug description: * alsa-ucm-conf = Availability = Built for all supported architectures as it's an arch all binary. In sync with Debian. https://launchpad.net/ubuntu/+source/alsa-ucm-conf/1.2.1.2-2 = Rationale = It's providing data useful to alsa to know how to handle hardware = Security = No known CVEs. https://security-tracker.debian.org/tracker/source-package/alsa-ucm-conf https://launchpad.net/ubuntu/+source/alsa-ucm-conf/+cve = Quality assurance = - Kernel Packages team needs to be subscribed. - no tests, the package provides data file only https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=alsa-ucm-conf = Dependencies = No universe binary dependencies, the package has no depends = Standards compliance = standard dh12 packaging = Maintenance = Maintained with alsa upstream and in Debian * alsa-topology-conf = Availability = Built for all supported architectures as it's an arch all binary. In sync with Debian. https://launchpad.net/ubuntu/+source/alsa-topology-conf/1.2.1-2 = Rationale = It's providing data useful to alsa to know how to handle hardware = Security = No known CVEs. https://security-tracker.debian.org/tracker/source-package/alsa-topology-conf https://launchpad.net/ubuntu/+source/alsa-topology-conff/+cve = Quality assurance = - Kernel Packages team needs to be subscribed. - no tests, the package provides data file only https://bugs.launchpad.net/ubuntu/+source/alsa-topology-conf https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=alsa-topology-conf = Dependencies = No universe binary dependencies, the package has no depends = Standards compliance = standard dh12 packaging = Maintenance = Maintained with alsa upstream and in Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-topology-conf/+bug/1862776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862776] Re: [MIR] alsa-ucm-conf & alsa-topology-conf (b-d of alsa-lib)
And to support the ucm2 well, the v1.2.2 is needed. -- You received this bug notification because you are a member of Kernel Packages, which is a bug assignee. https://bugs.launchpad.net/bugs/1862776 Title: [MIR] alsa-ucm-conf & alsa-topology-conf (b-d of alsa-lib) Status in alsa-topology-conf package in Ubuntu: New Status in alsa-ucm-conf package in Ubuntu: New Bug description: * alsa-ucm-conf = Availability = Built for all supported architectures as it's an arch all binary. In sync with Debian. https://launchpad.net/ubuntu/+source/alsa-ucm-conf/1.2.1.2-2 = Rationale = It's providing data useful to alsa to know how to handle hardware = Security = No known CVEs. https://security-tracker.debian.org/tracker/source-package/alsa-ucm-conf https://launchpad.net/ubuntu/+source/alsa-ucm-conf/+cve = Quality assurance = - Kernel Packages team needs to be subscribed. - no tests, the package provides data file only https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=alsa-ucm-conf = Dependencies = No universe binary dependencies, the package has no depends = Standards compliance = standard dh12 packaging = Maintenance = Maintained with alsa upstream and in Debian * alsa-topology-conf = Availability = Built for all supported architectures as it's an arch all binary. In sync with Debian. https://launchpad.net/ubuntu/+source/alsa-topology-conf/1.2.1-2 = Rationale = It's providing data useful to alsa to know how to handle hardware = Security = No known CVEs. https://security-tracker.debian.org/tracker/source-package/alsa-topology-conf https://launchpad.net/ubuntu/+source/alsa-topology-conff/+cve = Quality assurance = - Kernel Packages team needs to be subscribed. - no tests, the package provides data file only https://bugs.launchpad.net/ubuntu/+source/alsa-topology-conf https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=alsa-topology-conf = Dependencies = No universe binary dependencies, the package has no depends = Standards compliance = standard dh12 packaging = Maintenance = Maintained with alsa upstream and in Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-topology-conf/+bug/1862776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864092] Re: quotactl07 fails ubuntu_ltp_syscalls in 5.0 linux-gcp
** Description changed: - Initially Found: + == SRU Justification == + This quotactl07 is a new test case added in LTP test suite, + + The test will fail with: + <<>> + incrementing stop + tst_kconfig.c:62: INFO: Parsing kernel config '/boot/config-5.0.0-38-generic' + tst_device.c:244: INFO: Using test device LTP_DEV='/dev/loop4' + tst_mkfs.c:90: INFO: Formatting /dev/loop4 with xfs opts='' extra opts='' + tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s + quotactl07.c:34: FAIL: Q_XQUOTARM doesn't have quota type check + + HINT: You _MAY_ be missing kernel fixes, see: + + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3dd4d40b4208 + + == Fix == + * 3dd4d40b (xfs: Sanity check flags of Q_XQUOTARM call) + + Focal got this patch from stable update. This patch can be cherry-picked + into all the other kernels. + + == Test == + Test kernels could be found here: + https://people.canonical.com/~phlin/kernel/lp-1864092-quotactl07/ + + All patched kernels are working as expected, + + == Regression Potential == + Low, change limited to quota on XFS, and it's just adding a check for the flags. + + + == Original Bug Report == + Initially Found: Cloud: GCP Kernel: 5.0.0-1032.33 Test: ubuntu_ltp_syscalls - 02/20 15:04:55 DEBUG| utils:0153| [stdout] startup='Thu Feb 20 14:49:24 2020' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_kconfig.c:62: INFO: Parsing kernel config '/boot/config-5.0.0-1032-gcp' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_device.c:244: INFO: Using test device LTP_DEV='/dev/loop2' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_mkfs.c:90: INFO: Formatting /dev/loop2 with xfs opts='' extra opts='' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s 02/20 15:04:55 DEBUG| utils:0153| [stdout] quotactl07.c:34: FAIL: Q_XQUOTARM doesn't have quota type check - 02/20 15:04:55 DEBUG| utils:0153| [stdout] + 02/20 15:04:55 DEBUG| utils:0153| [stdout] 02/20 15:04:55 DEBUG| utils:0153| [stdout] HINT: You _MAY_ be missing kernel fixes, see: - 02/20 15:04:55 DEBUG| utils:0153| [stdout] + 02/20 15:04:55 DEBUG| utils:0153| [stdout] 02/20 15:04:55 DEBUG| utils:0153| [stdout] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3dd4d40b4208 - 02/20 15:04:55 DEBUG| utils:0153| [stdout] + 02/20 15:04:55 DEBUG| utils:0153| [stdout] 02/20 15:04:55 DEBUG| utils:0153| [stdout] Summary: 02/20 15:04:55 DEBUG| utils:0153| [stdout] passed 0 02/20 15:04:55 DEBUG| utils:0153| [stdout] failed 1 02/20 15:04:55 DEBUG| utils:0153| [stdout] skipped 0 02/20 15:04:55 DEBUG| utils:0153| [stdout] warnings 0 02/20 15:04:55 DEBUG| utils:0153| [stdout] tag=quotactl07 stime=1582210164 dur=4 exit=exited stat=1 core=no cu=0 cs=0 02/20 15:04:55 DEBUG| utils:0153| [stdout] startup='Thu Feb 20 14:49:29 2020' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s 02/20 15:04:55 DEBUG| utils:0153| [stdout] read01.c:24: PASS: read(2) returned 512 ** Changed in: linux (Ubuntu Eoan) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Summary changed: - quotactl07 fails ubuntu_ltp_syscalls in 5.0 linux-gcp + quotactl07 from ubuntu_ltp_syscalls failed -- 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/1864092 Title: quotactl07 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Bug description: == SRU Justification == This quotactl07 is a new test case added in LTP test suite, The test will fail with: <<>> incrementing stop tst_kconfig.c:62: INFO: Parsing kernel config '/boot/config-5.0.0-38-generic' tst_device.c:244: INFO: Using test device LTP_DEV='/dev/loop4' tst_mkfs.c:90: INFO: Formatting /dev/loop4 with xfs opts='' extra opts='' tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s quotactl07.c:34: FAIL: Q_XQUOTARM doesn't have quota type check HINT: You _MAY_ be missing kernel fixes, see: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3dd4d40b4208 == Fix == * 3dd4d40b (xfs: Sanity check flags of Q_XQUOTARM call) Focal got this patch from stable update. This patch can be cherry- picked into all the other kernels. == Test == Test kernels could be found
[Kernel-packages] [Bug 1864157] Re: [bionic] Add HMS CAN driver for Dell Edge Gateways
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** 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/1864157 Title: [bionic] Add HMS CAN driver for Dell Edge Gateways Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: == Impact == The HMS CAN device on Dell Edge Gateways doesn't work with linux-oem in Bionic. We used to have a driver for 4.4 from IHV integrated in Xenial. For 4.15 there's a new release for that. == Fix == Integrate the new release from IHV. == Test Case == Check if the device binds to a driver. == Risk of Regression == The driver binds to certain USB IDs thus should be reasonably low. linux-oem bug: https://launchpad.net/bugs/1807339 This bug is for tracking only, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864157/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864157] Missing required logs.
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 1864157 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 comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: bionic -- 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/1864157 Title: [bionic] Add HMS CAN driver for Dell Edge Gateways Status in linux package in Ubuntu: Incomplete Bug description: == Impact == The HMS CAN device on Dell Edge Gateways doesn't work with linux-oem in Bionic. We used to have a driver for 4.4 from IHV integrated in Xenial. For 4.15 there's a new release for that. == Fix == Integrate the new release from IHV. == Test Case == Check if the device binds to a driver. == Risk of Regression == The driver binds to certain USB IDs thus should be reasonably low. linux-oem bug: https://launchpad.net/bugs/1807339 This bug is for tracking only, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864157/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864157] [NEW] [bionic] Add HMS CAN driver for Dell Edge Gateways
Public bug reported: == Impact == The HMS CAN device on Dell Edge Gateways doesn't work with linux-oem in Bionic. We used to have a driver for 4.4 from IHV integrated in Xenial. For 4.15 there's a new release for that. == Fix == Integrate the new release from IHV. == Test Case == Check if the device binds to a driver. == Risk of Regression == The driver binds to certain USB IDs thus should be reasonably low. linux-oem bug: https://launchpad.net/bugs/1807339 This bug is for tracking only, please don't triage. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864157 Title: [bionic] Add HMS CAN driver for Dell Edge Gateways Status in linux package in Ubuntu: New Bug description: == Impact == The HMS CAN device on Dell Edge Gateways doesn't work with linux-oem in Bionic. We used to have a driver for 4.4 from IHV integrated in Xenial. For 4.15 there's a new release for that. == Fix == Integrate the new release from IHV. == Test Case == Check if the device binds to a driver. == Risk of Regression == The driver binds to certain USB IDs thus should be reasonably low. linux-oem bug: https://launchpad.net/bugs/1807339 This bug is for tracking only, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864157/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864147] Re: [bionic] Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty
** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** 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/1864147 Title: [bionic] Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: [SRU Justification] [Impact] Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty On systems using Intel Atom (Baytrail-I) SoC's, slave devices connected on HSUART1/2 ports are described by the ACPI BIOS as virtual hardware using HID's INT3511/INT3512. As a consequence, HW manufacturers have complete freedom to install any devices on-board as long as they can be accessed over serial tty interface. Once such device is Dell Edge 3002 IoT Gateway which sports ZigBee & GPS devices on the HS-UART ports 1 & 2 respectively. Post 4.15, with CONFIG_SERIAL_DEV_BUS=y, serdev port controller driver handles the enumeration for the slaves connected on these ports. Also, /dev/ttySx device nodes for these ports are no longer exposed to the userspace. [Fixes] This patchset allows the skipped virtual UART's with ACPI HID's mentioned above to be enumerated as ttyHSx port. [Regression Potential] Low. This driver binds only to Intel Atom E38XX (Baytrail-I) virtual serial ports on the Dell Edge 300x GW. These updates are being carried in the linux-oem (4.15.y) kernel for more than 2 years without any regressions. [Note] This driver has been submitted upstream and is under review. This issue has been identified as a regression in 4.15 and multiple solutions are being explored. Meanwhile, to support customer and maintain release schedule, this driver needs to be in Ubuntu 4.15 based kernels. More info: https://marc.info/?t=15245587167=1=2 linux-oem buglink: http://bugs.launchpad.net/bugs/1690362 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864147] Missing required logs.
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 1864147 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 comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Bionic) Status: New => Incomplete ** Tags added: bionic -- 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/1864147 Title: [bionic] Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: [SRU Justification] [Impact] Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty On systems using Intel Atom (Baytrail-I) SoC's, slave devices connected on HSUART1/2 ports are described by the ACPI BIOS as virtual hardware using HID's INT3511/INT3512. As a consequence, HW manufacturers have complete freedom to install any devices on-board as long as they can be accessed over serial tty interface. Once such device is Dell Edge 3002 IoT Gateway which sports ZigBee & GPS devices on the HS-UART ports 1 & 2 respectively. Post 4.15, with CONFIG_SERIAL_DEV_BUS=y, serdev port controller driver handles the enumeration for the slaves connected on these ports. Also, /dev/ttySx device nodes for these ports are no longer exposed to the userspace. [Fixes] This patchset allows the skipped virtual UART's with ACPI HID's mentioned above to be enumerated as ttyHSx port. [Regression Potential] Low. This driver binds only to Intel Atom E38XX (Baytrail-I) virtual serial ports on the Dell Edge 300x GW. These updates are being carried in the linux-oem (4.15.y) kernel for more than 2 years without any regressions. [Note] This driver has been submitted upstream and is under review. This issue has been identified as a regression in 4.15 and multiple solutions are being explored. Meanwhile, to support customer and maintain release schedule, this driver needs to be in Ubuntu 4.15 based kernels. More info: https://marc.info/?t=15245587167=1=2 linux-oem buglink: http://bugs.launchpad.net/bugs/1690362 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864092] Re: quotactl07 fails ubuntu_ltp_syscalls in 5.0 linux-gcp
Patch already applied to Focal. ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Tags added: 4.15 4.4 bionic disco eoan xenial ** Tags added: 5.3 ubuntu-ltp-syscalls -- 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/1864092 Title: quotactl07 fails ubuntu_ltp_syscalls in 5.0 linux-gcp Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: Incomplete Bug description: Initially Found: Cloud: GCP Kernel: 5.0.0-1032.33 Test: ubuntu_ltp_syscalls 02/20 15:04:55 DEBUG| utils:0153| [stdout] startup='Thu Feb 20 14:49:24 2020' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_kconfig.c:62: INFO: Parsing kernel config '/boot/config-5.0.0-1032-gcp' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_device.c:244: INFO: Using test device LTP_DEV='/dev/loop2' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_mkfs.c:90: INFO: Formatting /dev/loop2 with xfs opts='' extra opts='' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s 02/20 15:04:55 DEBUG| utils:0153| [stdout] quotactl07.c:34: FAIL: Q_XQUOTARM doesn't have quota type check 02/20 15:04:55 DEBUG| utils:0153| [stdout] 02/20 15:04:55 DEBUG| utils:0153| [stdout] HINT: You _MAY_ be missing kernel fixes, see: 02/20 15:04:55 DEBUG| utils:0153| [stdout] 02/20 15:04:55 DEBUG| utils:0153| [stdout] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3dd4d40b4208 02/20 15:04:55 DEBUG| utils:0153| [stdout] 02/20 15:04:55 DEBUG| utils:0153| [stdout] Summary: 02/20 15:04:55 DEBUG| utils:0153| [stdout] passed 0 02/20 15:04:55 DEBUG| utils:0153| [stdout] failed 1 02/20 15:04:55 DEBUG| utils:0153| [stdout] skipped 0 02/20 15:04:55 DEBUG| utils:0153| [stdout] warnings 0 02/20 15:04:55 DEBUG| utils:0153| [stdout] tag=quotactl07 stime=1582210164 dur=4 exit=exited stat=1 core=no cu=0 cs=0 02/20 15:04:55 DEBUG| utils:0153| [stdout] startup='Thu Feb 20 14:49:29 2020' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s 02/20 15:04:55 DEBUG| utils:0153| [stdout] read01.c:24: PASS: read(2) returned 512 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1864092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858166] Re: Support ath10k hardware rfkill
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1858166 Title: Support ath10k hardware rfkill Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Focal: In Progress Status in linux-firmware source package in Focal: Fix Released Bug description: [Impact] Wifi should be turned off if ethernet cable is plugged in. [Fix] Below commit from v5.5-rc1 provides this feature 1382993f882b ath10k: add support for hardware rfkill [Test] With latest firmware, this issue has been fixed. 6d191544 ath10k: QCA6174 hw3.0: update board-2.bin [Regression Potential] Low, we've been using this patch and firmware since Mar. 2019 in our production image. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1858166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864085] Re: focal/linux: 5.4.0-15.18 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-focal ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Holding before Promote to Proposed - phase-changed: Friday, 21. February 2020 04:56 UTC + phase: Ready for Promote to Proposed + phase-changed: Friday, 21. February 2020 05:36 UTC + reason: + promote-to-proposed: Pending -- ready for review trackers: focal/linux-aws: bug 1864080 focal/linux-azure: bug 1864081 focal/linux-gcp: bug 1864082 focal/linux-kvm: bug 1864083 focal/linux-oem-5.4: bug 1864079 focal/linux-oracle: bug 1864084 focal/linux-raspi2: bug 1864078 focal/linux/pc-kernel: bug 1864075 focal/linux/pc-lowlatency-kernel: bug 1864076 variant: debs -- 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/1864085 Title: focal/linux: 5.4.0-15.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Promote to Proposed phase-changed: Friday, 21. February 2020 05:36 UTC reason: promote-to-proposed: Pending -- ready for review trackers: focal/linux-aws: bug 1864080 focal/linux-azure: bug 1864081 focal/linux-gcp: bug 1864082 focal/linux-kvm: bug 1864083 focal/linux-oem-5.4: bug 1864079 focal/linux-oracle: bug 1864084 focal/linux-raspi2: bug 1864078 focal/linux/pc-kernel: bug 1864075 focal/linux/pc-lowlatency-kernel: bug 1864076 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864085/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858166] Re: Support ath10k hardware rfkill
** Tags added: verification-needed verification-needed-bionic -- 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/1858166 Title: Support ath10k hardware rfkill Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Focal: In Progress Status in linux-firmware source package in Focal: Fix Released Bug description: [Impact] Wifi should be turned off if ethernet cable is plugged in. [Fix] Below commit from v5.5-rc1 provides this feature 1382993f882b ath10k: add support for hardware rfkill [Test] With latest firmware, this issue has been fixed. 6d191544 ath10k: QCA6174 hw3.0: update board-2.bin [Regression Potential] Low, we've been using this patch and firmware since Mar. 2019 in our production image. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1858166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864080] Re: focal/linux-aws: 5.4.0-1002.2 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1864085 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Holding before Promote to Proposed phase-changed: Thursday, 20. February 2020 22:22 UTC reason: - promote-to-proposed: Holding -- master bug not ready for proposed + promote-to-proposed: 'Stalled -- WorkflowBugError: Source not found in kernel-series' variant: debs -- 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/1864080 Title: focal/linux-aws: 5.4.0-1002.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-aws package in Ubuntu: Confirmed Status in linux-aws source package in Focal: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1864085 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Holding before Promote to Proposed phase-changed: Thursday, 20. February 2020 22:22 UTC reason: promote-to-proposed: 'Stalled -- WorkflowBugError: Source not found in kernel-series' variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864147] [NEW] [bionic] Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty
Public bug reported: [SRU Justification] [Impact] Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty On systems using Intel Atom (Baytrail-I) SoC's, slave devices connected on HSUART1/2 ports are described by the ACPI BIOS as virtual hardware using HID's INT3511/INT3512. As a consequence, HW manufacturers have complete freedom to install any devices on-board as long as they can be accessed over serial tty interface. Once such device is Dell Edge 3002 IoT Gateway which sports ZigBee & GPS devices on the HS-UART ports 1 & 2 respectively. Post 4.15, with CONFIG_SERIAL_DEV_BUS=y, serdev port controller driver handles the enumeration for the slaves connected on these ports. Also, /dev/ttySx device nodes for these ports are no longer exposed to the userspace. [Fixes] This patchset allows the skipped virtual UART's with ACPI HID's mentioned above to be enumerated as ttyHSx port. [Regression Potential] Low. This driver binds only to Intel Atom E38XX (Baytrail-I) virtual serial ports on the Dell Edge 300x GW. These updates are being carried in the linux-oem (4.15.y) kernel for more than 2 years without any regressions. [Note] This driver has been submitted upstream and is under review. This issue has been identified as a regression in 4.15 and multiple solutions are being explored. Meanwhile, to support customer and maintain release schedule, this driver needs to be in Ubuntu 4.15 based kernels. More info: https://marc.info/?t=15245587167=1=2 linux-oem buglink: http://bugs.launchpad.net/bugs/1690362 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Description changed: [SRU Justification] [Impact] Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty On systems using Intel Atom (Baytrail-I) SoC's, slave devices connected on HSUART1/2 ports are described by the ACPI BIOS as virtual hardware using HID's INT3511/INT3512. As a consequence, HW manufacturers have complete freedom to install any devices on-board as long as they can be accessed over serial tty interface. Once such device is Dell Edge 3002 IoT Gateway which sports ZigBee & GPS devices on the HS-UART ports 1 & 2 respectively. Post 4.15, with CONFIG_SERIAL_DEV_BUS=y, serdev port controller driver handles the enumeration for the slaves connected on these ports. Also, /dev/ttySx device nodes for these ports are no longer exposed to the userspace. [Fixes] This patchset allows the skipped virtual UART's with ACPI HID's mentioned above to be enumerated as ttyHSx port. [Regression Potential] Low. This driver binds only to Intel Atom E38XX (Baytrail-I) virtual serial ports on the Dell Edge 300x GW. These updates are being carried in the linux-oem (4.15.y) kernel for more than 2 years without any regressions. [Note] This driver has been submitted upstream and is under review. This issue has been identified as a regression in 4.15 and multiple solutions are being explored. Meanwhile, to support customer and maintain release schedule, this driver needs to be in Ubuntu 4.15 based kernels. More info: https://marc.info/?t=15245587167=1=2 - linux-oem buglink: http://bugs.launchpad.net/bugs/ 1690362 + linux-oem buglink: http://bugs.launchpad.net/bugs/1690362 -- 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/1864147 Title: [bionic] Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Bug description: [SRU Justification] [Impact] Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty On systems using Intel Atom (Baytrail-I) SoC's, slave devices connected on HSUART1/2 ports are described by the ACPI BIOS as virtual hardware using HID's INT3511/INT3512. As a consequence, HW manufacturers have complete freedom to install any devices on-board as long as they can be accessed over serial tty interface. Once such device is Dell Edge 3002 IoT Gateway which sports ZigBee & GPS devices on the HS-UART ports 1 & 2 respectively. Post 4.15, with CONFIG_SERIAL_DEV_BUS=y, serdev port controller driver handles the enumeration for the slaves connected on these ports. Also, /dev/ttySx device nodes for these ports are no longer exposed to the userspace. [Fixes] This patchset allows the skipped virtual UART's with ACPI HID's mentioned above to be enumerated as ttyHSx port. [Regression Potential] Low. This driver binds only to Intel Atom E38XX (Baytrail-I) virtual serial ports on the Dell Edge 300x GW. These updates are being carried in the linux-oem (4.15.y) kernel for more than 2 years without any regressions. [Note]
[Kernel-packages] [Bug 1864092] Re: quotactl07 fails ubuntu_ltp_syscalls in 5.0 linux-gcp
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) 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/1864092 Title: quotactl07 fails ubuntu_ltp_syscalls in 5.0 linux-gcp Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: Incomplete Bug description: Initially Found: Cloud: GCP Kernel: 5.0.0-1032.33 Test: ubuntu_ltp_syscalls 02/20 15:04:55 DEBUG| utils:0153| [stdout] startup='Thu Feb 20 14:49:24 2020' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_kconfig.c:62: INFO: Parsing kernel config '/boot/config-5.0.0-1032-gcp' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_device.c:244: INFO: Using test device LTP_DEV='/dev/loop2' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_mkfs.c:90: INFO: Formatting /dev/loop2 with xfs opts='' extra opts='' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s 02/20 15:04:55 DEBUG| utils:0153| [stdout] quotactl07.c:34: FAIL: Q_XQUOTARM doesn't have quota type check 02/20 15:04:55 DEBUG| utils:0153| [stdout] 02/20 15:04:55 DEBUG| utils:0153| [stdout] HINT: You _MAY_ be missing kernel fixes, see: 02/20 15:04:55 DEBUG| utils:0153| [stdout] 02/20 15:04:55 DEBUG| utils:0153| [stdout] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3dd4d40b4208 02/20 15:04:55 DEBUG| utils:0153| [stdout] 02/20 15:04:55 DEBUG| utils:0153| [stdout] Summary: 02/20 15:04:55 DEBUG| utils:0153| [stdout] passed 0 02/20 15:04:55 DEBUG| utils:0153| [stdout] failed 1 02/20 15:04:55 DEBUG| utils:0153| [stdout] skipped 0 02/20 15:04:55 DEBUG| utils:0153| [stdout] warnings 0 02/20 15:04:55 DEBUG| utils:0153| [stdout] tag=quotactl07 stime=1582210164 dur=4 exit=exited stat=1 core=no cu=0 cs=0 02/20 15:04:55 DEBUG| utils:0153| [stdout] startup='Thu Feb 20 14:49:29 2020' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s 02/20 15:04:55 DEBUG| utils:0153| [stdout] read01.c:24: PASS: read(2) returned 512 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1864092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864092] Missing required logs.
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 1864092 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 comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Eoan) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864092 Title: quotactl07 fails ubuntu_ltp_syscalls in 5.0 linux-gcp Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: Incomplete Bug description: Initially Found: Cloud: GCP Kernel: 5.0.0-1032.33 Test: ubuntu_ltp_syscalls 02/20 15:04:55 DEBUG| utils:0153| [stdout] startup='Thu Feb 20 14:49:24 2020' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_kconfig.c:62: INFO: Parsing kernel config '/boot/config-5.0.0-1032-gcp' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_device.c:244: INFO: Using test device LTP_DEV='/dev/loop2' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_mkfs.c:90: INFO: Formatting /dev/loop2 with xfs opts='' extra opts='' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s 02/20 15:04:55 DEBUG| utils:0153| [stdout] quotactl07.c:34: FAIL: Q_XQUOTARM doesn't have quota type check 02/20 15:04:55 DEBUG| utils:0153| [stdout] 02/20 15:04:55 DEBUG| utils:0153| [stdout] HINT: You _MAY_ be missing kernel fixes, see: 02/20 15:04:55 DEBUG| utils:0153| [stdout] 02/20 15:04:55 DEBUG| utils:0153| [stdout] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3dd4d40b4208 02/20 15:04:55 DEBUG| utils:0153| [stdout] 02/20 15:04:55 DEBUG| utils:0153| [stdout] Summary: 02/20 15:04:55 DEBUG| utils:0153| [stdout] passed 0 02/20 15:04:55 DEBUG| utils:0153| [stdout] failed 1 02/20 15:04:55 DEBUG| utils:0153| [stdout] skipped 0 02/20 15:04:55 DEBUG| utils:0153| [stdout] warnings 0 02/20 15:04:55 DEBUG| utils:0153| [stdout] tag=quotactl07 stime=1582210164 dur=4 exit=exited stat=1 core=no cu=0 cs=0 02/20 15:04:55 DEBUG| utils:0153| [stdout] startup='Thu Feb 20 14:49:29 2020' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s 02/20 15:04:55 DEBUG| utils:0153| [stdout] read01.c:24: PASS: read(2) returned 512 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1864092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864092] Re: quotactl07 fails ubuntu_ltp_syscalls in 5.0 linux-gcp
** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864092 Title: quotactl07 fails ubuntu_ltp_syscalls in 5.0 linux-gcp Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: Incomplete Bug description: Initially Found: Cloud: GCP Kernel: 5.0.0-1032.33 Test: ubuntu_ltp_syscalls 02/20 15:04:55 DEBUG| utils:0153| [stdout] startup='Thu Feb 20 14:49:24 2020' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_kconfig.c:62: INFO: Parsing kernel config '/boot/config-5.0.0-1032-gcp' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_device.c:244: INFO: Using test device LTP_DEV='/dev/loop2' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_mkfs.c:90: INFO: Formatting /dev/loop2 with xfs opts='' extra opts='' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s 02/20 15:04:55 DEBUG| utils:0153| [stdout] quotactl07.c:34: FAIL: Q_XQUOTARM doesn't have quota type check 02/20 15:04:55 DEBUG| utils:0153| [stdout] 02/20 15:04:55 DEBUG| utils:0153| [stdout] HINT: You _MAY_ be missing kernel fixes, see: 02/20 15:04:55 DEBUG| utils:0153| [stdout] 02/20 15:04:55 DEBUG| utils:0153| [stdout] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3dd4d40b4208 02/20 15:04:55 DEBUG| utils:0153| [stdout] 02/20 15:04:55 DEBUG| utils:0153| [stdout] Summary: 02/20 15:04:55 DEBUG| utils:0153| [stdout] passed 0 02/20 15:04:55 DEBUG| utils:0153| [stdout] failed 1 02/20 15:04:55 DEBUG| utils:0153| [stdout] skipped 0 02/20 15:04:55 DEBUG| utils:0153| [stdout] warnings 0 02/20 15:04:55 DEBUG| utils:0153| [stdout] tag=quotactl07 stime=1582210164 dur=4 exit=exited stat=1 core=no cu=0 cs=0 02/20 15:04:55 DEBUG| utils:0153| [stdout] startup='Thu Feb 20 14:49:29 2020' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s 02/20 15:04:55 DEBUG| utils:0153| [stdout] read01.c:24: PASS: read(2) returned 512 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1864092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864092] Re: quotactl07 fails ubuntu_ltp_syscalls in 5.0 linux-gcp
** Package changed: linux-gcp (Ubuntu) => linux (Ubuntu) ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: ubuntu-kernel-tests Status: Triaged => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Disco) Status: New => In Progress ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) -- 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/1864092 Title: quotactl07 fails ubuntu_ltp_syscalls in 5.0 linux-gcp Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: New Status in linux source package in Bionic: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: New Bug description: Initially Found: Cloud: GCP Kernel: 5.0.0-1032.33 Test: ubuntu_ltp_syscalls 02/20 15:04:55 DEBUG| utils:0153| [stdout] startup='Thu Feb 20 14:49:24 2020' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_kconfig.c:62: INFO: Parsing kernel config '/boot/config-5.0.0-1032-gcp' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_device.c:244: INFO: Using test device LTP_DEV='/dev/loop2' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_mkfs.c:90: INFO: Formatting /dev/loop2 with xfs opts='' extra opts='' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s 02/20 15:04:55 DEBUG| utils:0153| [stdout] quotactl07.c:34: FAIL: Q_XQUOTARM doesn't have quota type check 02/20 15:04:55 DEBUG| utils:0153| [stdout] 02/20 15:04:55 DEBUG| utils:0153| [stdout] HINT: You _MAY_ be missing kernel fixes, see: 02/20 15:04:55 DEBUG| utils:0153| [stdout] 02/20 15:04:55 DEBUG| utils:0153| [stdout] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3dd4d40b4208 02/20 15:04:55 DEBUG| utils:0153| [stdout] 02/20 15:04:55 DEBUG| utils:0153| [stdout] Summary: 02/20 15:04:55 DEBUG| utils:0153| [stdout] passed 0 02/20 15:04:55 DEBUG| utils:0153| [stdout] failed 1 02/20 15:04:55 DEBUG| utils:0153| [stdout] skipped 0 02/20 15:04:55 DEBUG| utils:0153| [stdout] warnings 0 02/20 15:04:55 DEBUG| utils:0153| [stdout] tag=quotactl07 stime=1582210164 dur=4 exit=exited stat=1 core=no cu=0 cs=0 02/20 15:04:55 DEBUG| utils:0153| [stdout] startup='Thu Feb 20 14:49:29 2020' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s 02/20 15:04:55 DEBUG| utils:0153| [stdout] read01.c:24: PASS: read(2) returned 512 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1864092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864081] Re: focal/linux-azure: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1864085 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Holding before Packaging - phase-changed: Thursday, 20. February 2020 17:22 UTC + phase: Ready for Packaging + phase-changed: Friday, 21. February 2020 04:57 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1864081 Title: focal/linux-azure: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in linux-azure package in Ubuntu: Confirmed Status in linux-azure source package in Focal: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1864085 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Packaging phase-changed: Friday, 21. February 2020 04:57 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864081/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864078] Re: focal/linux-raspi2: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1864085 packages: main: linux-raspi2 meta: linux-meta-raspi2 - phase: Holding before Packaging - phase-changed: Thursday, 20. February 2020 17:22 UTC + phase: Ready for Packaging + phase-changed: Friday, 21. February 2020 04:57 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified trackers: focal/linux-raspi2/pi-kernel: bug 1864077 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1864078 Title: focal/linux-raspi2: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Focal: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1864085 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Ready for Packaging phase-changed: Friday, 21. February 2020 04:57 UTC reason: prepare-package: Pending -- version not specified trackers: focal/linux-raspi2/pi-kernel: bug 1864077 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864078/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864084] Re: focal/linux-oracle: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1864085 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle - phase: Holding before Packaging - phase-changed: Thursday, 20. February 2020 17:23 UTC + phase: Ready for Packaging + phase-changed: Friday, 21. February 2020 04:58 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1864084 Title: focal/linux-oracle: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-oracle package in Ubuntu: Confirmed Status in linux-oracle source package in Focal: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1864085 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Ready for Packaging phase-changed: Friday, 21. February 2020 04:58 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864084/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864083] Re: focal/linux-kvm: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1864085 packages: main: linux-kvm meta: linux-meta-kvm - phase: Holding before Packaging - phase-changed: Thursday, 20. February 2020 17:23 UTC + phase: Ready for Packaging + phase-changed: Friday, 21. February 2020 04:57 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1864083 Title: focal/linux-kvm: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-kvm package in Ubuntu: Confirmed Status in linux-kvm source package in Focal: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1864085 packages: main: linux-kvm meta: linux-meta-kvm phase: Ready for Packaging phase-changed: Friday, 21. February 2020 04:57 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864079] Re: focal/linux-oem-5.4: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1864085 packages: lrm: linux-restricted-modules-oem-5.4 main: linux-oem-5.4 meta: linux-meta-oem-5.4 signed: linux-signed-oem-5.4 - phase: Holding before Packaging - phase-changed: Thursday, 20. February 2020 17:22 UTC + phase: Ready for Packaging + phase-changed: Friday, 21. February 2020 04:57 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1864079 Title: focal/linux-oem-5.4: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-oem-5.4 package in Ubuntu: Confirmed Status in linux-oem-5.4 source package in Focal: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1864085 packages: lrm: linux-restricted-modules-oem-5.4 main: linux-oem-5.4 meta: linux-meta-oem-5.4 signed: linux-signed-oem-5.4 phase: Ready for Packaging phase-changed: Friday, 21. February 2020 04:57 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864079/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864085] Re: focal/linux: 5.4.0-15.18 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Fix Committed => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
- phase: Packaging
- phase-changed: Thursday, 20. February 2020 17:42 UTC
- reason:
- prepare-package: Ongoing -- {} package not yet fully built
+ phase: Holding before Promote to Proposed
+ phase-changed: Friday, 21. February 2020 04:56 UTC
trackers:
focal/linux-aws: bug 1864080
focal/linux-azure: bug 1864081
focal/linux-gcp: bug 1864082
focal/linux-kvm: bug 1864083
focal/linux-oem-5.4: bug 1864079
focal/linux-oracle: bug 1864084
focal/linux-raspi2: bug 1864078
focal/linux/pc-kernel: bug 1864075
focal/linux/pc-lowlatency-kernel: bug 1864076
variant: debs
--
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/1864085
Title:
focal/linux: 5.4.0-15.18 -proposed tracker
Status in Kernel SRU Workflow:
In Progress
Status in Kernel SRU Workflow automated-testing series:
New
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
New
Status in Kernel SRU Workflow promote-to-release series:
New
Status in Kernel SRU Workflow regression-testing series:
New
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Focal:
Confirmed
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
phase: Holding before Promote to Proposed
phase-changed: Friday, 21. February 2020 04:56 UTC
trackers:
focal/linux-aws: bug 1864080
focal/linux-azure: bug 1864081
focal/linux-gcp: bug 1864082
focal/linux-kvm: bug 1864083
focal/linux-oem-5.4: bug 1864079
focal/linux-oracle: bug 1864084
focal/linux-raspi2: bug 1864078
focal/linux/pc-kernel: bug 1864075
focal/linux/pc-lowlatency-kernel: bug 1864076
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864085/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864082] Re: focal/linux-gcp: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1864085 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Holding before Packaging - phase-changed: Thursday, 20. February 2020 17:23 UTC + phase: Ready for Packaging + phase-changed: Friday, 21. February 2020 04:57 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1864082 Title: focal/linux-gcp: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-gcp package in Ubuntu: Confirmed Status in linux-gcp source package in Focal: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1864085 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Ready for Packaging phase-changed: Friday, 21. February 2020 04:57 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864080] Re: focal/linux-aws: 5.4.0-1002.2 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1864085 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Holding before Promote to Proposed phase-changed: Thursday, 20. February 2020 22:22 UTC + reason: + promote-to-proposed: Holding -- master bug not ready for proposed variant: debs -- 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/1864080 Title: focal/linux-aws: 5.4.0-1002.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-aws package in Ubuntu: Confirmed Status in linux-aws source package in Focal: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1864085 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Holding before Promote to Proposed phase-changed: Thursday, 20. February 2020 22:22 UTC reason: promote-to-proposed: Holding -- master bug not ready for proposed variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1664072]
I see it Linux 5.5.4 with a OpenVPN(UDP)/tun/VPN tunnel. TCP: tun0: Driver has suspect GRO implementation, TCP performance may be compromised. Is this the same bug? Something different? -- 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/1664072 Title: TCP: wlp1s0: Driver has suspect GRO implementation, TCP performance may be compromised. Status in Linux: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux package in Debian: Confirmed Bug description: dmesg: [ 7578.057461] TCP: wlp1s0: Driver has suspect GRO implementation, TCP performance may be compromised. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.9.0-15-generic 4.9.0-15.16 ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5 Uname: Linux 4.9.0-15-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caravena 2378 F...m pulseaudio /dev/snd/controlC0: caravena 2378 F pulseaudio CurrentDesktop: GNOME Date: Sun Feb 12 19:34:40 2017 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2015-07-26 (567 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-15-generic root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.9.0-15-generic N/A linux-backports-modules-4.9.0-15-generic N/A linux-firmware1.162 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2016-10-29 (106 days ago) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1664072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837683] Re: Screen stops updating after about 8 hours - (EE) modeset(0): present flip failed
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (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/bugs/1837683 Title: Screen stops updating after about 8 hours - (EE) modeset(0): present flip failed Status in linux package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: environment: - XPS-13-938 - connect 5G ac wifi - disabled suspend in power setting - disabled blank screen in power setting steps: - play 4k video by chrome on youtube[1] overnight symptom: - after about 8 hours, the screen is black and keyboard and mouse can not wake up screen. - the audio of 4K video is still playing, I can hear that when screen is black. - magic key still work, so I can reboot system by magic key. - a repeat error message in syslog: " Jul 24 01:25:49 u-XPS-13-9380 /usr/lib/gdm3/gdm-x-session[2217]: (WW) modeset(0): Page flip failed: Invalid argument Jul 24 01:25:49 u-XPS-13-9380 /usr/lib/gdm3/gdm-x-session[2217]: (EE) modeset(0): present flip failed " [1] https://www.youtube.com/watch?v=pkKBXH2qc_I=11701s ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-1047.52-oem 4.15.18 Uname: Linux 4.15.0-1047-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 24 09:47:59 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:08af] InstallationDate: Installed on 2019-07-20 (3 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1047-oem root=UUID=77efb06b-1ce6-4749-a131-67f57aa8b21b ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837683] Re: Screen stops updating after about 8 hours - (EE) modeset(0): present flip failed
[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/bugs/1837683 Title: Screen stops updating after about 8 hours - (EE) modeset(0): present flip failed Status in linux package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: environment: - XPS-13-938 - connect 5G ac wifi - disabled suspend in power setting - disabled blank screen in power setting steps: - play 4k video by chrome on youtube[1] overnight symptom: - after about 8 hours, the screen is black and keyboard and mouse can not wake up screen. - the audio of 4K video is still playing, I can hear that when screen is black. - magic key still work, so I can reboot system by magic key. - a repeat error message in syslog: " Jul 24 01:25:49 u-XPS-13-9380 /usr/lib/gdm3/gdm-x-session[2217]: (WW) modeset(0): Page flip failed: Invalid argument Jul 24 01:25:49 u-XPS-13-9380 /usr/lib/gdm3/gdm-x-session[2217]: (EE) modeset(0): present flip failed " [1] https://www.youtube.com/watch?v=pkKBXH2qc_I=11701s ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-1047.52-oem 4.15.18 Uname: Linux 4.15.0-1047-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 24 09:47:59 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:08af] InstallationDate: Installed on 2019-07-20 (3 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1047-oem root=UUID=77efb06b-1ce6-4749-a131-67f57aa8b21b ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864140] Missing required logs.
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 1864140 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 comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864140 Title: ubuntu_fan_smoke_test failed with unable to fetch file from http://ports.ubuntu.com on PowerPC Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue found on PowerPC nodes across different kernels. (It works on other arches in different MAAS server, so it looks like some network config issue) Running in the Canonical CI environment Testing Fan Networking (pre-0.13.0 API) docker pull ppc64le/ubuntu: PASSED enable disable fan test: PASSED fanctl show test: PASSED fanctl check bridge config test: PASSED fanatic docker test: FAILED: (docker run returned 100) stderr: W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic/InRelease Could not connect to ports.ubuntu.com:80 (91.189.88.150), connection timed out W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-updates/InRelease Unable to connect to ports.ubuntu.com:http: W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-backports/InRelease Unable to connect to ports.ubuntu.com:http: W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-security/InRelease Unable to connect to ports.ubuntu.com:http: W: Some index files failed to download. They have been ignored, or old ones used instead. E: Unable to locate package iputils-ping ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-174-generic 4.4.0-174.204 ProcVersionSignature: Ubuntu 4.4.0-174.204-generic 4.4.211 Uname: Linux 4.4.0-174-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 21 03:32 seq crw-rw 1 root audio 116, 33 Feb 21 03:32 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.21 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Feb 21 03:47:15 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=faf7d4a6-6836-4496-bc64-15f33ec9e43d ro console=hvc0 ProcLoadAvg: 1.28 1.27 0.97 1/1305 17149 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-174-generic (buildd@bos02-ppc64el-008) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.12) ) #204-Ubuntu SMP Wed Jan 29 06:41:38 UTC 2020 RelatedPackageVersions: linux-restricted-modules-4.4.0-174-generic N/A linux-backports-modules-4.4.0-174-generic N/A linux-firmware 1.157.22 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.694 GHz (cpu 120) max: 3.694 GHz (cpu 37) avg: 3.694 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1864140/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864140] [NEW] ubuntu_fan_smoke_test failed with unable to fetch file from http://ports.ubuntu.com on PowerPC
Public bug reported: Issue found on PowerPC nodes across different kernels. (It works on other arches in different MAAS server, so it looks like some network config issue) Running in the Canonical CI environment Testing Fan Networking (pre-0.13.0 API) docker pull ppc64le/ubuntu: PASSED enable disable fan test: PASSED fanctl show test: PASSED fanctl check bridge config test: PASSED fanatic docker test: FAILED: (docker run returned 100) stderr: W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic/InRelease Could not connect to ports.ubuntu.com:80 (91.189.88.150), connection timed out W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-updates/InRelease Unable to connect to ports.ubuntu.com:http: W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-backports/InRelease Unable to connect to ports.ubuntu.com:http: W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-security/InRelease Unable to connect to ports.ubuntu.com:http: W: Some index files failed to download. They have been ignored, or old ones used instead. E: Unable to locate package iputils-ping ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-174-generic 4.4.0-174.204 ProcVersionSignature: Ubuntu 4.4.0-174.204-generic 4.4.211 Uname: Linux 4.4.0-174-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 21 03:32 seq crw-rw 1 root audio 116, 33 Feb 21 03:32 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.21 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Feb 21 03:47:15 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=faf7d4a6-6836-4496-bc64-15f33ec9e43d ro console=hvc0 ProcLoadAvg: 1.28 1.27 0.97 1/1305 17149 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-174-generic (buildd@bos02-ppc64el-008) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.12) ) #204-Ubuntu SMP Wed Jan 29 06:41:38 UTC 2020 RelatedPackageVersions: linux-restricted-modules-4.4.0-174-generic N/A linux-backports-modules-4.4.0-174-generic N/A linux-firmware 1.157.22 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.694 GHz (cpu 120) max: 3.694 GHz (cpu 37) avg: 3.694 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: apport-bug ppc64el sru-20200217 ubuntu-fan-smoke-test uec-images xenial ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Tags added: sru-20200217 ** Tags added: ubuntu-fan-smoke-test -- 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/1864140 Title: ubuntu_fan_smoke_test failed with unable to fetch file from http://ports.ubuntu.com on PowerPC Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue found on PowerPC nodes across different kernels. (It works on other arches in different MAAS server, so it looks like some network config issue) Running in the Canonical CI environment Testing Fan Networking (pre-0.13.0 API) docker pull ppc64le/ubuntu: PASSED enable disable fan test: PASSED fanctl show test: PASSED fanctl check bridge config test: PASSED fanatic docker test: FAILED: (docker run returned 100) stderr: W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic/InRelease Could not connect to ports.ubuntu.com:80 (91.189.88.150), connection timed out W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-updates/InRelease Unable to connect to ports.ubuntu.com:http: W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-backports/InRelease Unable to connect to ports.ubuntu.com:http: W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-security/InRelease Unable to connect to
[Kernel-packages] [Bug 1768211] Re: norton setup
https://www.facebook.com/madukuatkesagi/ http://bit.ly/hargaobatasmamadulicasma http://bit.ly/hargamadukosagikesagiobatkuatpria http://bit.ly/limefitreviewtestimonipelangsing -- 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/1768211 Title: norton setup Status in linux package in Ubuntu: Invalid Bug description: Online Norton Help and Support by PC Planet PCPlanet's Certified Technicians can help you scan, detect, and remove all types of viruses and malware in your computer. Our techies have years of experience and the expertise in providing support for antivirus and fixing computer virus problems online through remote connection. Our support services are available through phone, chat and email. Just call us at 1-888-406-4114 to chat with a certified expert and get instant support for Norton Antivirus to make your computer virus free.http://pcplanet247.com/www-norton-com-setup//;>Norton Support Get Started http://pcplanet247.com/www-norton-com-setup//;>Norton Support http://pcplanet247.com/www-norton-com-setup//;>Norton Support 2016 is a version of Norton Setup productivity suite came after Norton 2013. This version is available for PCs (such as Norton Security & 360 2016) and Macs (such as Norton Delux & Premier Edition 2016 for Mac). Along with all the features of previous versions, Norton includes additional ribbon buttons, enhanced collaboration, mentions, new & improved connection options, publish to docs.com, publish to power BI, researcher, suggest a feature, text highlighter, zoom for Norton and staying in the loop. To get Norton 2016, you need to buy, download, install and then activate it. To perform these processes, there is a series of steps that needs to be followed. You can purchase Norton Antivirus setup offline or online. Upon online purchase via norton.com/setup, you will receive a 25-digit product key on your registered email ID. Upon offline purchase, you will receive an Norton retail card, on the back of which this 25-digit key is mentioned. Keep this key secure with you, as you will need it later at the time of Norton subscription activation or while logging in to your account. http://pcplanet247.com/www-norton-com-setup//;>Norton Support http://pcplanet247.com/www-norton-com-setup//;>Norton Support Norton Support NORTON SETUP Visithttp://pcplanet247.com/www-norton-com-setup//;>Norton Support and sign in to your Norton account or create a new account (new users) Enter Norton product key Select your subscription and click download button to begin the downloading process There, you will get the choice to choose from different versions and languages Depending upon your browser, run the downloaded setup Click Run (in Edge or Internet Explorer), Setup (in Chrome), or Save File (in Firefox) After installation, open any of the application of MS Office 2016 Here, you will be see a Norton Antivirus activation wizard Click activate and enter the same product key, if asked Follow the on-screen instructions to complete activation NORTON SETUP FOR MAC First two steps as same with those listed in PC Now, log in to your Norton account and install Norton setup 2016 For this, you have to open My Account and under the name of your subscription, choose Install On the next window, select install under Install information This will begin downloading the installation package Once the download completes, open Finder and go to Downloads Double-click Norton_Setup_2016_Installer.pkg Click continue Review the software license agreement Choose agree to the terms of the software license agreement Select how you want to install the Norton2016 and click continue Change your install location, if you want and then click Install Enter your Mac login password and click Install software Click the Launchpad icon in the dock to display all your applications Click the Norton icon and then click Get Started followed by What’s new This will begin activation process Enter the product key, if asked Follow the on-screen instructions to finish activation It’s good to go! Norton Setup 2016 for Business NORTON SETUP FOR PC Sign in with your work or school account by visiting http://pcplanet247.com/www-norton-com-setup//;>Norton Support From the drop-down list, choose your preferred language and accept the default to install 32-bit or select Advanced and choose 4-bit Choose Install Click Run, Setup or Save file option, depending upon your browser You will be prompted “Do you want to allow this app to make changes to your device?” Click Yes This will begin the installation You’re all set! Activate it and you will be able to access all its applications For Mac Log in with your School or work account at norton setup On the Norton page, select Install option available under
[Kernel-packages] [Bug 1860166] Re: Touchpad not supported
Could you try this kernel: $ sudo add-apt-repository ppa:mapengyu/kernel-mainline $ sudo apt install linux-image-unsigned-5.6.0-050600rc2-generic linux-modules-5.6.0-050600rc2-generic linux-modules-extra-5.6.0-050600rc2-generic -- 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/1860166 Title: Touchpad not supported Status in linux package in Ubuntu: Confirmed Bug description: My touchpad is not supported by kernal of Ubuntu 18.04. It is a lenovo G50-80 laptop. The below is the response of xinput. ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ ETPS/2 Elantech Touchpadid=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Lenovo EasyCamera: Lenovo EasyC id=10 [slave keyboard (3)] ↳ Ideapad extra buttons id=11 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.36 Uname: Linux 5.0.0-05-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Jan 18 00:10:51 2020 InstallationDate: Installed on 2020-01-17 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sridhar1704 F pulseaudio /dev/snd/controlC0: sridhar1704 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-18 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 80E5 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=b6cf46e6-9187-4b99-9327-6126097a94aa ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-74-generic N/A linux-backports-modules-4.15.0-74-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-74-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: B0CN96WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo G50-80 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-80 dmi.modalias: dmi:bvnLENOVO:bvrB0CN96WW:bd09/22/2015:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoG50-80: dmi.product.family: IDEAPAD dmi.product.name: 80E5 dmi.product.version: Lenovo G50-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864132] Re: g_ether missing eem support
** Changed in: linux-raspi2 (Ubuntu) Importance: Undecided => High ** Changed in: linux-raspi2 (Ubuntu) Assignee: (unassigned) => Hui Wang (hui.wang) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1864132 Title: g_ether missing eem support Status in linux-raspi2 package in Ubuntu: New Bug description: I am looking into enabling EEM with g_ether by module option use_eem=1, and g_ether won't be loaded because it has no EEM support compiled. Expected: EEM is compiled with g_ether (no such option for g_cdc) so that it can be enabled by use_eem=1. My "/sys/module/g_ether/parameters": -r--r--r-- 1 root root 4096 Feb 20 13:40 bcdDevice -r--r--r-- 1 root root 4096 Feb 20 13:40 dev_addr -r--r--r-- 1 root root 4096 Feb 20 13:40 host_addr -r--r--r-- 1 root root 4096 Feb 20 13:40 iManufacturer -r--r--r-- 1 root root 4096 Feb 20 13:40 iProduct -r--r--r-- 1 root root 4096 Feb 20 13:40 iSerialNumber -r--r--r-- 1 root root 4096 Feb 20 13:40 idProduct -r--r--r-- 1 root root 4096 Feb 20 13:40 idVendor -rw-r--r-- 1 root root 4096 Feb 20 14:08 qmult modinfo g_ether: parm: idVendor:USB Vendor ID (ushort) parm: idProduct:USB Product ID (ushort) parm: bcdDevice:USB Device version (BCD) (ushort) parm: iSerialNumber:SerialNumber string (charp) parm: iManufacturer:USB Manufacturer string (charp) parm: iProduct:USB Product string (charp) parm: qmult:queue length multiplier at high/super speed (uint) parm: dev_addr:Device Ethernet Address (charp) parm: host_addr:Host Ethernet Address (charp) parm: use_eem:use CDC EEM mode (bool) dmesg: ... [4.474689] udc-core: couldn't find an available UDC - added [g_ether] to list of pending drivers ... [5.768660] dwc2 fe98.usb: EPs: 8, dedicated fifos, 4080 entries in SPRAM [5.772414] g_ether fe98.usb: failed to start g_ether: -2 ... should it be another bug? - There is another issue that when my laptop is connected and the with my Pi 4 reboot, the cdc_ether function provided to my laptop will not be available again until I reconnect the cable (I have USB Y-cable + type-c adapter so I can unplug on laptop side w/o Pi 4 losing power). I remember it was working as expected when I was testing out OTG function. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1864132/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859261] Re: [hns3-0111]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE kernel branch Edit
Patches sent. https://lists.ubuntu.com/archives/kernel-team/2020-February/107657.html ** Changed in: linux (Ubuntu) Status: Fix Committed => 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/1859261 Title: [hns3-0111]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE kernel branch Edit Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] hns3 patchset have merged into mainline 5.4rc5 kernel. Pls backport ubuntu 18.04.5 kernel version [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] net: hns3: support tx-scatter-gather-fraglist feature net: hns3: add support for configuring VF MAC from the host net: hns3: add support for configuring bandwidth of VF on the host net: hns3: add support for setting VF trust net: hns3: add support for spoof check setting net: hns3: add support for setting VF link status on the host net: hns3: make array tick_array static, makes object smaller net: hns3: fix a wrong reset interrupt status mask net: hns3: cleanup of stray struct hns3_link_mode_mapping net: hns3: fix ETS bandwidth validation bug net: hns3: reallocate SSU' buffer size when pfc_en changes net: hns3: add compatible handling for MAC VLAN switch parameter configuration net: hns3: add compatible handling for command HCLGE_OPC_PF_RST_DONE net: hns3: remove unused macros net: hns3: Use the correct style for SPDX License Identifier net: hns3: cleanup byte order issues when printed net: hns3: cleanup some print format warning net: hns3: add or modify some comments net: hns3: optimize local variable initialization net: hns3: cleanup a format-truncation warning net: hns3: cleanup some coding style issues net: hns3: cleanup some magic numbers net: hns3: add struct netdev_queue debug info for TX timeout net: hns3: dump some debug information when reset fail treewide: Use sizeof_member() macro net: hns3: log and clear hardware error after reset complete net: hns3: do not allocate linear data for fraglist skb net: hns3: minor cleanup for hns3_handle_rx_bd() net: hns3: make struct hns3_enet_ring cacheline aligned net: hns3: introduce ring_to_netdev() in enet module net: hns3: minor optimization for barrier in IO path net: hns3: optimized MAC address in management table. net: hns3: remove struct hns3_nic_ring_data in hns3_enet module net: hns3: fix mis-counting IRQ vector numbers issue net: hns3: fix VF ID issue for setting VF VLAN net: hns3: fix a use after free problem in hns3_nic_maybe_stop_tx() net: hns3: fix for TX queue not restarted problem net: hns3: only print misc interrupt status when handling fails net: hns3: add a log for getting chain failure in hns3_nic_uninit_vector_data() net: hns3: add some VF VLAN information for command "ip link show" net: hns3: implement ndo_features_check ops for hns3 driver net: hns3: get FD rules location before dump in debugfs net: hns3: optimization for CMDQ uninitialization net: hns3: remove useless mutex vport_cfg_mutex in the struct hclge_dev net: hns3: check FE bit before calling hns3_add_frag() net: hns3: do not schedule the periodic task when reset fail net: hns3: allocate WQ with WQ_MEM_RECLAIM flag net: hns3: remove unnecessary work in hclgevf_main net: hns3: remove mailbox and reset work in hclge_main net: hns3: schedule hclgevf_service by using delayed workqueue net: hns3: refactor the notification scheme of PF reset net: hns3: refactor the procedure of VF FLR net: hns3: modify hclge_func_reset_sync_vf()'s return type to void net: hns3: enlarge HCLGE_RESET_WAIT_CNT net: hns3: refactor the precedure of PF FLR net: hns3: split hclgevf_reset() into preparing and rebuilding part net: hns3: split hclge_reset() into preparing and rebuilding part net: hns3: modify an unsuitable reset level for hardware error net: hns3: replace an unsuitable variable type in hclge_inform_reset_assert_to_vf() net: hns3: add protection when get SFP speed as 0 net: hns3: modify the IRQ name of misc vectors net: hns3: modify an unsuitable log in hclge_map_ring_to_vector() net: hns3: modify the IRQ name of TQP vector net: hns3: re-organize vector handle net: hns3: add trace event support for HNS3 driver update 0120 net: hns3: pad the short frame before sending to the hardware [Status] (Fix committed): net: hns3: support tx-scatter-gather-fraglist feature (Fix committed): net: hns3: add support for
[Kernel-packages] [Bug 1863575] Re: [hns3-0217]sync mainline kernel 5.6rc1 hns3 patchset into ubuntu HWE kernel branch
Patches sent. https://lists.ubuntu.com/archives/kernel-team/2020-February/107657.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/1863575 Title: [hns3-0217]sync mainline kernel 5.6rc1 hns3 patchset into ubuntu HWE kernel branch Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] hns3 patchset have merged into mainline 5.6rc1 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] net: hns3: fix a copying IPv6 address error in hclge_fd_get_flow_tuples() net: hns3: fix VF bandwidth does not take effect in some case net: hns3: add management table after IMP reset [Status] (In progress) 47327c9315b2 net: hns3: fix a copying IPv6 address error in hclge_fd_get_flow_tuples() (In progress) 19eb1123b4e9 net: hns3: fix VF bandwidth does not take effect in some case (In progress) d0db7ed39751 net: hns3: add management table after IMP reset To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1863575/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864132] Re: g_ether missing eem support
** Package changed: libvirt (Ubuntu) => linux-raspi2 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1864132 Title: g_ether missing eem support Status in linux-raspi2 package in Ubuntu: New Bug description: I am looking into enabling EEM with g_ether by module option use_eem=1, and g_ether won't be loaded because it has no EEM support compiled. Expected: EEM is compiled with g_ether (no such option for g_cdc) so that it can be enabled by use_eem=1. My "/sys/module/g_ether/parameters": -r--r--r-- 1 root root 4096 Feb 20 13:40 bcdDevice -r--r--r-- 1 root root 4096 Feb 20 13:40 dev_addr -r--r--r-- 1 root root 4096 Feb 20 13:40 host_addr -r--r--r-- 1 root root 4096 Feb 20 13:40 iManufacturer -r--r--r-- 1 root root 4096 Feb 20 13:40 iProduct -r--r--r-- 1 root root 4096 Feb 20 13:40 iSerialNumber -r--r--r-- 1 root root 4096 Feb 20 13:40 idProduct -r--r--r-- 1 root root 4096 Feb 20 13:40 idVendor -rw-r--r-- 1 root root 4096 Feb 20 14:08 qmult modinfo g_ether: parm: idVendor:USB Vendor ID (ushort) parm: idProduct:USB Product ID (ushort) parm: bcdDevice:USB Device version (BCD) (ushort) parm: iSerialNumber:SerialNumber string (charp) parm: iManufacturer:USB Manufacturer string (charp) parm: iProduct:USB Product string (charp) parm: qmult:queue length multiplier at high/super speed (uint) parm: dev_addr:Device Ethernet Address (charp) parm: host_addr:Host Ethernet Address (charp) parm: use_eem:use CDC EEM mode (bool) dmesg: ... [4.474689] udc-core: couldn't find an available UDC - added [g_ether] to list of pending drivers ... [5.768660] dwc2 fe98.usb: EPs: 8, dedicated fifos, 4080 entries in SPRAM [5.772414] g_ether fe98.usb: failed to start g_ether: -2 ... should it be another bug? - There is another issue that when my laptop is connected and the with my Pi 4 reboot, the cdc_ether function provided to my laptop will not be available again until I reconnect the cable (I have USB Y-cable + type-c adapter so I can unplug on laptop side w/o Pi 4 losing power). I remember it was working as expected when I was testing out OTG function. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1864132/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864132] [NEW] g_ether missing eem support
You have been subscribed to a public bug: I am looking into enabling EEM with g_ether by module option use_eem=1, and g_ether won't be loaded because it has no EEM support compiled. Expected: EEM is compiled with g_ether (no such option for g_cdc) so that it can be enabled by use_eem=1. My "/sys/module/g_ether/parameters": -r--r--r-- 1 root root 4096 Feb 20 13:40 bcdDevice -r--r--r-- 1 root root 4096 Feb 20 13:40 dev_addr -r--r--r-- 1 root root 4096 Feb 20 13:40 host_addr -r--r--r-- 1 root root 4096 Feb 20 13:40 iManufacturer -r--r--r-- 1 root root 4096 Feb 20 13:40 iProduct -r--r--r-- 1 root root 4096 Feb 20 13:40 iSerialNumber -r--r--r-- 1 root root 4096 Feb 20 13:40 idProduct -r--r--r-- 1 root root 4096 Feb 20 13:40 idVendor -rw-r--r-- 1 root root 4096 Feb 20 14:08 qmult modinfo g_ether: parm: idVendor:USB Vendor ID (ushort) parm: idProduct:USB Product ID (ushort) parm: bcdDevice:USB Device version (BCD) (ushort) parm: iSerialNumber:SerialNumber string (charp) parm: iManufacturer:USB Manufacturer string (charp) parm: iProduct:USB Product string (charp) parm: qmult:queue length multiplier at high/super speed (uint) parm: dev_addr:Device Ethernet Address (charp) parm: host_addr:Host Ethernet Address (charp) parm: use_eem:use CDC EEM mode (bool) dmesg: ... [4.474689] udc-core: couldn't find an available UDC - added [g_ether] to list of pending drivers ... [5.768660] dwc2 fe98.usb: EPs: 8, dedicated fifos, 4080 entries in SPRAM [5.772414] g_ether fe98.usb: failed to start g_ether: -2 ... should it be another bug? - There is another issue that when my laptop is connected and the with my Pi 4 reboot, the cdc_ether function provided to my laptop will not be available again until I reconnect the cable (I have USB Y-cable + type-c adapter so I can unplug on laptop side w/o Pi 4 losing power). I remember it was working as expected when I was testing out OTG function. ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New -- g_ether missing eem support https://bugs.launchpad.net/bugs/1864132 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798400]
Thanks for the analysis! >From it, I still wonder whether this is a pulseaudio bug, though. Why is pulseaudio ever binding to RFCOMM channel 3 *before* there is any need to do so? That is, until I am not connected to any device using channel 3, why is pulseaudio already using it up? In other words, it seems reasonable to me to have the laptop connected to the phone as a headset and in this case not to have the impress remote working. But in case I start impress before setting up a bluetooth connection to the phone, why should be the pulseaudio binding already there? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: [upstream] Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: Confirmed Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798400]
This issue was annoying me for a while too. So I sat down and debugged bluez to see why the bind fails: LO is using the default channel (3) for the RFCOMM protocol as it should be. However, the bind call fails, because another process has already bound that channel via DBUS. Changing the default RFCOMM channel in the bluez source temporaliy to 2 (UDP, unused) and recompiling bluez made remote impress work immediately! So I inspected the DBUS users via the old mdbus tool from openmoko and it turned out that the other process is PulseAudio: The HS profile needs the RFCOMM for the AT Commands and registers channel 3. Stop PA and impress remote works again. So now we have two programs that need RFCOMM for the mobile phone. :-( One solution would be that LO explicitly requests channel 2 instead of the default one. Channel 2 is UDP and unused to my knowledge. This will work until another programm needs RFCOMM and chooses 2 as a free channel... Or, in the long run, there needs to be some kind of multipexing between the apps that use the RFCOMM protocol. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: [upstream] Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: Confirmed Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1864131] [NEW] CIFS VFS: error -22 on ioctl to get interface list
Public bug reported:
Problem:
Following error logged when mounting Azure file share with CIFS 3.0 protocol.
[ 4856.227895] CIFS VFS: error -22 on ioctl to get interface list
It looks like linux-azure kernel > 5 has some cifs bug. (It might be
reproducible with a upstream kernel as well.)
This is not reproducible with -o 2.1 mount option or linux-azure 4.15.
And It can be easily reproducible with platform image like
Canonical:UbuntuServer:18.04-LTS:18.04.202002180.
What I have done to reproduce:
VM create CLI command
$ az vm create --resource-group rgname --name cifsubuntu --image
Canonical:UbuntuServer:18.04-LTS:18.04.202002180
mount command
# mount -t cifs //accountname.file.core.windows.net/test /mnt/somewhere
-o vers=3.0,credentials=/etc/smbcredentials/cred.cred --verbose
Do you have any knowledge about this?
As far as I research, SMB2_ioctl which is in cifs kernel module send some
invalid parameter to the server.
Here is a debug log.
[ 156.667830] SMB2_ioctl:2506:
/build/linux-azure-ZlnYF6/linux-azure-5.0.0/fs/cifs/smb2pdu.c: SMB2 IOCTL
[ 156.667836] smb3_init_transform_rq:3164:
/build/linux-azure-ZlnYF6/linux-azure-5.0.0/fs/cifs/smb2ops.c: encrypt message
returned 0
[ 156.667840] __smb_send_rqst:341:
/build/linux-azure-ZlnYF6/linux-azure-5.0.0/fs/cifs/transport.c: Sending smb:
smb_len=177
[ 156.668906] cifs_demultiplex_thread:1184:
/build/linux-azure-ZlnYF6/linux-azure-5.0.0/fs/cifs/connect.c: RFC1002 header
0x7d
[ 156.668914] decrypt_raw_data:3205:
/build/linux-azure-ZlnYF6/linux-azure-5.0.0/fs/cifs/smb2ops.c: decrypt message
returned 0
[ 156.668915] receive_encrypted_standard:3533:
/build/linux-azure-ZlnYF6/linux-azure-5.0.0/fs/cifs/smb2ops.c: mid found
[ 156.668916] smb2_calc_size:421:
/build/linux-azure-ZlnYF6/linux-azure-5.0.0/fs/cifs/smb2misc.c: SMB2 data
length 0 offset 0
[ 156.668917] smb2_calc_size:439:
/build/linux-azure-ZlnYF6/linux-azure-5.0.0/fs/cifs/smb2misc.c: SMB2 len 73
[ 156.668918] smb2_add_credits:122:
/build/linux-azure-ZlnYF6/linux-azure-5.0.0/fs/cifs/smb2ops.c: add 2 credits
total=39
[ 156.668924] cifs_sync_mid_result:708:
/build/linux-azure-ZlnYF6/linux-azure-5.0.0/fs/cifs/transport.c:
cifs_sync_mid_result: cmd=11 mid=8 state=4
[ 156.668925] Status code returned 0xc00d STATUS_INVALID_PARAMETER
[ 156.668929] map_smb2_to_linux_error:2484:
/build/linux-azure-ZlnYF6/linux-azure-5.0.0/fs/cifs/smb2maperror.c: Mapping
SMB2 status code 0xc00d to POSIX err -22
[ 156.668930] cifs_small_buf_release:222:
/build/linux-azure-ZlnYF6/linux-azure-5.0.0/fs/cifs/misc.c: Null buffer passed
to cifs_small_buf_release
[ 156.668931] CIFS VFS: error -22 on ioctl to get interface list
To enable the debug, I have done following command before mount.
# modprobe cifs
# echo 'module cifs +lfp' > /sys/kernel/debug/dynamic_debug/control
# echo 'file fs/cifs/* +lfp' > /sys/kernel/debug/dynamic_debug/control
# echo 7 > /proc/fs/cifs/cifsFYI
I am not sure but it looks like following SMB2_ioctl has some invalid argument.
"fs/cifs/smb2ops.c"
516 static int
517 SMB3_request_interfaces(const unsigned int xid, struct cifs_tcon *tcon)
518 {
519 int rc;
520 unsigned int ret_data_len = 0;
521 struct network_interface_info_ioctl_rsp *out_buf = NULL;
522 struct cifs_server_iface *iface_list;
523 size_t iface_count;
524 struct cifs_ses *ses = tcon->ses;
525
526 rc = SMB2_ioctl(xid, tcon, NO_FILE_ID, NO_FILE_ID,
527 FSCTL_QUERY_NETWORK_INTERFACE_INFO, true /*
is_fsctl */,
528 NULL /* no data input */, 0 /* no data input */,
529 (char **)_buf, _data_len);
530 if (rc == -EOPNOTSUPP) {
531 cifs_dbg(FYI,
532 "server does not support query network
interfaces\n");
533 goto out;
534 } else if (rc != 0) {
535 cifs_dbg(VFS, "error %d on ioctl to get interface list\n",
rc);
536 goto out;
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1864131
Title:
CIFS VFS: error -22 on ioctl to get interface list
Status in linux-azure package in Ubuntu:
New
Bug description:
Problem:
Following error logged when mounting Azure file share with CIFS 3.0 protocol.
[ 4856.227895] CIFS VFS: error -22 on ioctl to get interface list
It looks like linux-azure kernel > 5 has some cifs bug. (It might be
reproducible with a upstream kernel as well.)
This is not reproducible with -o 2.1 mount option or linux-azure 4.15.
And It can be easily reproducible with platform image like
Canonical:UbuntuServer:18.04-LTS:18.04.202002180.
What I have done to reproduce:
VM create CLI command
$ az vm
[Kernel-packages] [Bug 1838796] Re: TPM event log does not contain events measured after ExitBootServices
Hi Marcelo, I am facing the same issue as I was with the .deb packages. When I run "sudo apt install Linux-azure-edge" and reboot, the kernel does not boot. I am able to boot into the Linux 5.3.040-generic kernel but not the azure edge kernel. That said, I tried it on both the physical machine and Hyper v with secure boot enabled. The kernel boots fine on Hyper V but not on the physical machine. Did you get a chance to test it on a physical machine? -Vinay -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1838796 Title: TPM event log does not contain events measured after ExitBootServices Status in linux package in Ubuntu: Won't Fix Status in linux-azure package in Ubuntu: In Progress Status in linux source package in Xenial: Won't Fix Status in linux-azure source package in Xenial: In Progress Status in linux source package in Disco: Won't Fix Status in linux-azure source package in Disco: In Progress Bug description: The TPM event log (/sys/kernel/security/tpm0/binary_bios_measurements) does not contain any events that are measured by UEFI after the kernel's EFI Boot stub calls ExitBootServices(). This means that PCR values calculated from the event log will not match the actual PCR values on the machine for PCR indices into which these events are measured. There are upstream patches to fix this in the mainline kernel tree: https://lore.kernel.org/lkml/20190520205501.177637-1-matthewgarr...@google.com/ --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-06-20 (43 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=fcb8dc9d-4dd3-490f-9f1c-fa6364770bb0 ro ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-22-generic N/A linux-backports-modules-4.18.0-22-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/30/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 8486-4870-7514-9524-5524-7794-69 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863276] Re: bionic/linux-hwe-5.0: 5.0.0-42.46~18.04.1 -proposed tracker
The following packages ended up in the wrong component in the Proposed pocket: linux-source-5.0.0 5.0.0-42.46~18.04.1 - is in main instead of universe linux-source-5.0.0 5.0.0-42.46~18.04.1 - is in main instead of universe linux-source-5.0.0 5.0.0-42.46~18.04.1 - is in main instead of universe linux-source-5.0.0 5.0.0-42.46~18.04.1 - is in main instead of universe linux-source-5.0.0 5.0.0-42.46~18.04.1 - is in main instead of universe linux-source-5.0.0 5.0.0-42.46~18.04.1 - is in main instead of universe Once this is fixed, set the promote-to-proposed to Fix Released again ** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Incomplete ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863297 packages: main: linux-hwe-5.0 meta: linux-meta-hwe-5.0 signed: linux-signed-hwe-5.0 phase: Promote to Proposed phase-changed: Tuesday, 18. February 2020 09:59 UTC reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + certification-testing: Ongoing -- testing in progress + promote-to-proposed: Stalled -- copy FAILED + regression-testing: Ongoing -- testing in progress + verification-testing: Ongoing -- testing in progress variant: debs -- 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/1863276 Title: bionic/linux-hwe-5.0: 5.0.0-42.46~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Incomplete Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863297 packages: main: linux-hwe-5.0 meta: linux-meta-hwe-5.0 signed: linux-signed-hwe-5.0 phase: Promote to Proposed phase-changed: Tuesday, 18. February 2020 09:59 UTC reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress promote-to-proposed: Stalled -- copy FAILED regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863276/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837828] Re: alsa/sof: let legacy hda driver and sof driver co-exist
@roland please refer to: https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1864061/comments/3 -- 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/1837828 Title: alsa/sof: let legacy hda driver and sof driver co-exist Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Eoan: Fix Committed Status in linux-oem-osp1 source package in Eoan: Invalid Bug description: [Impact] So far, if we want the sof driver to work, we need to blacklist snd_hda_intel.ko, but on some paltforms with nv hdmi or amd hdmi, we need these two driver co-exist. [Fix] Intel sent the patches to fix this issue, although it is not merged yet, but I guess they will pass the review and be merged. So i backported them first. [Test Case] remove snd_hda_intel.ko from blacklist, the two drivers (sof and hda) worked well. [Regression Risk] Low. We already tested these patches on some Dell machines. and comunity including endlessm and goole all tested these patches. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1837828/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863272] Re: eoan/linux-aws: 5.3.0-1012.13 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863294 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Tuesday, 18. February 2020 08:55 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.3: bug 1863270 variant: debs -- 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/1863272 Title: eoan/linux-aws: 5.3.0-1012.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863294 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Tuesday, 18. February 2020 08:55 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.3: bug 1863270 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863272/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863234] Re: Disabling bpf() syscall on kernel lockdown break apps when secure boot is on
Hi Brendan - What you're asking for is very different than the intent
behind this bug report. It'll be best if you open a new 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/1863234
Title:
Disabling bpf() syscall on kernel lockdown break apps when secure boot
is on
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Bug description:
[Impact]
The bpf(2) system call is completely blocked in Disco and Eoan when
Secure Boot is enabled due to overly restrictive Lockdown policies.
This makes it so that all bpf related tools are not usable on those
releases.
[Test Case]
Set up test BPF programs:
$ cat hello.bt
BEGIN { printf("hello\n"); exit(); }
$ cat kprobe.bt
kprobe:do_nanosleep { printf("task sleeping...\n"); exit(); }
$ cat open.bt
tracepoint:syscalls:sys_enter_openat {
printf("filename: [%s]; flags: [%d]\n",
str(args->filename), args->flags);
}
Disable Secure Boot:
$ sudo mokutil --disable-validation
...
$ sudo reboot
Ensure that hello.bt can run:
$ sudo bpftrace hello.bt
Attaching 1 probe...
hello
Ensure that a BPF program triggered by a kprobe works (run `sleep 1` in
another terminal):
$ sudo bpftrace kprobe.bt
Attaching 1 probe...
task sleeping...
Ensure that a BPF program triggered by a tracepoint can access the filename
and flags of openat(2):
$ sudo bpftrace open.bt
Attaching 1 probe...
filename: [/proc/2317/cmdline]; flags: [0]
filename: [/dev/iio:device1]; flags: [2048]
...
Enable Secure Boot
$ sudo mokutil --enable-validation
...
$ sudo reboot
Ensure that a basic BPF program can run:
$ sudo bpftrace hello.bt
Attaching 1 probe...
hello
Ensure that a BPF program triggered by a kprobe is blocked (kprobes aren't
allowed under Secure Boot):
$ sudo bpftrace kprobe.bt
Attaching 1 probe...
cannot attach kprobe, Operation not permitted
Error attaching probe: 'kprobe:do_nanosleep'
You should see the following kernel message logged:
Lockdown: bpftrace: Use of kprobes is restricted; see man
kernel_lockdown.7
Ensure that a BPF program triggered by a tracepoint can NOT access the
filename and flags of openat(2) (all filenames should be empty and all flags
should be 0):
$ sudo bpftrace open.bt
Attaching 1 probe...
filename: []; flags: [0]
filename: []; flags: [0]
...
You should see the following kernel message logged:
Lockdown: iio-sensor-prox: BPF is restricted; see man
kernel_lockdown.7
[Regression Potential]
Low. This is opening up the use of bpf(2) while under Lockdown. There
should be no new restrictions put in place.
[Original Report]
In disco and eoan, lockdown is automatically enforced when secure boot
is on [0]. Because lockdown was not in the mailine kernel at the time,
some disrto-specific patches were added to the kernel, including one
that drastically restricts BPF usage by completely disabling the use
of the `bpf()` system call when lockdown is on [1].
A consequence of that decision is that no application relying on eBPF
can run on 19.04/19.10, unless secure boot / lockdown is disabled. For
example, Cilium (cilium.io) strongly relies on BPF programs to
implement its datapath and securing network connectivity between
containers. Other applications like Suricata or Sysdig also rely on
BPF to some extent. None of which will work by default on a EFI
machine with secure boot activated.
If I understand correctly, kernel 5.4 (to be used in focal) will have
a different, lighter restricton (comming from mainline Linux kernel)
[2], so `bpf()` for networking use cases should mostly work on 20.04.
Is my understanding correct? If so, could this patch be backported to
19.10 (and 19.04, if still supported) instead of completely disabling
the syscall on lockdown?
Links:
[0]
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/disco/commit/?id=d0db99473fc3bb8a5d03f99ed454ac7ca5e7d517
[1]
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/disco/commit/?id=2a68c65abae66d28e2acb3245cb156ae2ea6eb1d
[2]
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/commit/?id=9d1f8be5cf42b497a3bddf1d523f2bb142e9318c
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863234/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860806] Re: Ubuntu 18.04 and 19.04 new ethernet problem
*** This bug is a duplicate of bug 1576953 *** https://bugs.launchpad.net/bugs/1576953 I don't think that apport-collect will work while I am offline. Please let me know how I can run this command and send the data after I have done the restart. Remember, after restart the problem goes away. I can't run diagnostics on Internet access that requires Internet access to run. As it looks like I am talking to an automated script rather than a real person perhaps this is now a dead thread. -- 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/1860806 Title: Ubuntu 18.04 and 19.04 new ethernet problem Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Ubuntu 19.04 (64 bit) on OptiPlex-7010 On every power on I have no wired Ethernet connection or even an icon to enable it. After a restart (soft boot) it comes back again. This appears to be different from another bug reported which states that the Ethernet cable has to be unplugged during power on. In my issue, I can leave the Ethernet cable plugged in and it works fine. It just doesn't work during first power on boot. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-01-26 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.156 metric 100 IwConfig: lono wireless extensions. eno1 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 RfKill: Tags: bionic Uname: Linux 4.15.0-74-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 ethernet 1580229876 Tue 28 Jan 2020 08:44:36 AM PST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860806/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863274] Re: eoan/linux-azure: 5.3.0-1014.15 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863294 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 18. February 2020 07:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-5.3: bug 1863273 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1863274 Title: eoan/linux-azure: 5.3.0-1014.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863294 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 18. February 2020 07:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-5.3: bug 1863273 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863274/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863978] Re: boot failing - unable to handle kernel paging request - followed by oops
Seeing something very similar with Ubuntu 16.04 machines upgraded to linux-image-4.15.0-1071-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1863978 Title: boot failing - unable to handle kernel paging request - followed by oops Status in linux-azure package in Ubuntu: Confirmed Bug description: After update to Ubuntu 5.0.0-1032.34-azure 5.0.21, VM is not able to boot anymore. Keeps stuck in logging "soft lockup - CPU#xxx stuck for xxs" with random process (different on each startup). Full logs below. Relevant boot logs: (...) [[0;32m OK [0m] Started /var/lib/waagent/Microsoft.…0.0.7820/scripts/enableHandler.py. [ 14.836987] PKCS#7 signature not signed with a trusted key [ 14.856290] PKCS#7 signature not signed with a trusted key [ 15.123087] BUG: unable to handle kernel paging request at 3fa9 [ 15.123905] #PF error: [normal kernel read fault] [ 15.123905] PGD 80084ab2c067 P4D 80084ab2c067 PUD 8586cb067 PMD 0 [ 15.135982] Oops: [#1] SMP PTI [ 15.135982] CPU: 4 PID: 3561 Comm: microsoft-depen Tainted: P OE 5.0.0-1032-azure #34-Ubuntu [ 15.135982] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [ 15.135982] RIP: 0010:iterate_extants+0x155/0x380 [microsoft_dependency_agent] [ 15.135982] Code: ab c0 4c 89 e7 e8 bb 9b 0c e8 49 8b 44 24 08 48 85 c0 74 71 4d 8b 7c 24 08 49 83 ef 68 75 0b eb 64 49 83 ea 68 4d 89 d7 74 5b <41> 0f b7 47 10 83 e0 f7 66 83 f8 02 75 44 41 80 bf 01 02 00 00 06 [ 15.171900] RSP: 0018:bd46489cbb10 EFLAGS: 00010216 [ 15.171900] RAX: 4001 RBX: bd46489cbb30 RCX: 0de9 [ 15.171900] RDX: 0001 RSI: 0008 RDI: a9ae5280 [ 15.171900] RBP: bd46489cbb80 R08: 0001 R09: 024f [ 15.171900] R10: bd46489cbb98 R11: R12: a9ae5280 [ 15.171900] R13: c0ab59d0 R14: R15: 3f99 [ 15.171900] FS: 7f365b7e1440() GS:98541dd0() knlGS: [ 15.171900] CS: 0010 DS: ES: CR0: 80050033 [ 15.171900] CR2: 3fa9 CR3: 00084c1c6002 CR4: 003606e0 [ 15.171900] DR0: DR1: DR2: [ 15.171900] DR3: DR6: fffe0ff0 DR7: 0400 [ 15.171900] Call Trace: [ 15.171900] ? bs_release+0x1b0/0x1b0 [microsoft_dependency_agent] [ 15.171900] bs_open+0x2fd/0x580 [microsoft_dependency_agent] [ 15.171900] ? bs_open+0x2fd/0x580 [microsoft_dependency_agent] [ 15.171900] ? bs_write+0x90/0x90 [microsoft_dependency_agent] (...) [ 45.331952] watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [nginx:4876] [ 45.336115] Modules linked in: microsoft_dependency_agent(POE) bluechannel(POE) veth ipt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype br_netfilter bridge stp llc xt_owner iptable_security aufs overlay xt_conntrack xt_tcpudp iptable_filter xt_nat iptable_nat nf_nat_ipv4 nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 bpfilter nls_iso8859_1 kvm_intel kvm irqbypass serio_raw hv_balloon joydev sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel hid_generic aes_x86_64 hid_hyperv crypto_simd cryptd hyperv_fb glue_helper cfbfillrect pata_acpi hyperv_keyboard hid hv_netvsc cfbimgblt cfbcopyarea hv_utils [ 45.395981] CPU: 2 PID: 4876 Comm: nginx Tainted: P DOE 5.0.0-1032-azure #34-Ubuntu [ 45.400558] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [ 45.408757] RIP: 0010:hv_qlock_wait+0x25/0x60 [ 45.411928] Code: 38 be 00 5d c3 0f 1f 44 00 00 55 48 89 e5 53 65 8b 05 2f 75 df 57 a9 00 00 10 00 75 0d 9c 5b fa 0f b6 07 40 38 c6 74 05 53 9d <5b> 5d c3 b9 f0 00 00 40 0f 32 0f 1f 44 00 00 eb ed 48 c1 e2 20 bf [ 45.424104] RSP: 0018:bd46493a3d60 EFLAGS: 0246 ORIG_RAX: ff12 [ 45.431986] RAX: RBX: 0246 RCX: 40f0 [ 45.437191] RDX: RSI: 0003 RDI: a9ae5280 [ 45.440905] RBP: bd46493a3d68 R08: 0009 R09: 00d8 [ 45.447992] R10: R11: R12: 98541dca2000 [ 45.452055] R13: 0001 R14: 0100 R15: [ 45.457386] FS: 7faee231fd48() GS:98541dc8()
[Kernel-packages] [Bug 1863978] Re: boot failing - unable to handle kernel paging request - followed by oops
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-azure (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1863978 Title: boot failing - unable to handle kernel paging request - followed by oops Status in linux-azure package in Ubuntu: Confirmed Bug description: After update to Ubuntu 5.0.0-1032.34-azure 5.0.21, VM is not able to boot anymore. Keeps stuck in logging "soft lockup - CPU#xxx stuck for xxs" with random process (different on each startup). Full logs below. Relevant boot logs: (...) [[0;32m OK [0m] Started /var/lib/waagent/Microsoft.…0.0.7820/scripts/enableHandler.py. [ 14.836987] PKCS#7 signature not signed with a trusted key [ 14.856290] PKCS#7 signature not signed with a trusted key [ 15.123087] BUG: unable to handle kernel paging request at 3fa9 [ 15.123905] #PF error: [normal kernel read fault] [ 15.123905] PGD 80084ab2c067 P4D 80084ab2c067 PUD 8586cb067 PMD 0 [ 15.135982] Oops: [#1] SMP PTI [ 15.135982] CPU: 4 PID: 3561 Comm: microsoft-depen Tainted: P OE 5.0.0-1032-azure #34-Ubuntu [ 15.135982] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [ 15.135982] RIP: 0010:iterate_extants+0x155/0x380 [microsoft_dependency_agent] [ 15.135982] Code: ab c0 4c 89 e7 e8 bb 9b 0c e8 49 8b 44 24 08 48 85 c0 74 71 4d 8b 7c 24 08 49 83 ef 68 75 0b eb 64 49 83 ea 68 4d 89 d7 74 5b <41> 0f b7 47 10 83 e0 f7 66 83 f8 02 75 44 41 80 bf 01 02 00 00 06 [ 15.171900] RSP: 0018:bd46489cbb10 EFLAGS: 00010216 [ 15.171900] RAX: 4001 RBX: bd46489cbb30 RCX: 0de9 [ 15.171900] RDX: 0001 RSI: 0008 RDI: a9ae5280 [ 15.171900] RBP: bd46489cbb80 R08: 0001 R09: 024f [ 15.171900] R10: bd46489cbb98 R11: R12: a9ae5280 [ 15.171900] R13: c0ab59d0 R14: R15: 3f99 [ 15.171900] FS: 7f365b7e1440() GS:98541dd0() knlGS: [ 15.171900] CS: 0010 DS: ES: CR0: 80050033 [ 15.171900] CR2: 3fa9 CR3: 00084c1c6002 CR4: 003606e0 [ 15.171900] DR0: DR1: DR2: [ 15.171900] DR3: DR6: fffe0ff0 DR7: 0400 [ 15.171900] Call Trace: [ 15.171900] ? bs_release+0x1b0/0x1b0 [microsoft_dependency_agent] [ 15.171900] bs_open+0x2fd/0x580 [microsoft_dependency_agent] [ 15.171900] ? bs_open+0x2fd/0x580 [microsoft_dependency_agent] [ 15.171900] ? bs_write+0x90/0x90 [microsoft_dependency_agent] (...) [ 45.331952] watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [nginx:4876] [ 45.336115] Modules linked in: microsoft_dependency_agent(POE) bluechannel(POE) veth ipt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype br_netfilter bridge stp llc xt_owner iptable_security aufs overlay xt_conntrack xt_tcpudp iptable_filter xt_nat iptable_nat nf_nat_ipv4 nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 bpfilter nls_iso8859_1 kvm_intel kvm irqbypass serio_raw hv_balloon joydev sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel hid_generic aes_x86_64 hid_hyperv crypto_simd cryptd hyperv_fb glue_helper cfbfillrect pata_acpi hyperv_keyboard hid hv_netvsc cfbimgblt cfbcopyarea hv_utils [ 45.395981] CPU: 2 PID: 4876 Comm: nginx Tainted: P DOE 5.0.0-1032-azure #34-Ubuntu [ 45.400558] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [ 45.408757] RIP: 0010:hv_qlock_wait+0x25/0x60 [ 45.411928] Code: 38 be 00 5d c3 0f 1f 44 00 00 55 48 89 e5 53 65 8b 05 2f 75 df 57 a9 00 00 10 00 75 0d 9c 5b fa 0f b6 07 40 38 c6 74 05 53 9d <5b> 5d c3 b9 f0 00 00 40 0f 32 0f 1f 44 00 00 eb ed 48 c1 e2 20 bf [ 45.424104] RSP: 0018:bd46493a3d60 EFLAGS: 0246 ORIG_RAX: ff12 [ 45.431986] RAX: RBX: 0246 RCX: 40f0 [ 45.437191] RDX: RSI: 0003 RDI: a9ae5280 [ 45.440905] RBP: bd46493a3d68 R08: 0009 R09: 00d8 [ 45.447992] R10: R11: R12: 98541dca2000 [ 45.452055] R13: 0001 R14: 0100 R15: [ 45.457386] FS: 7faee231fd48()
[Kernel-packages] [Bug 1863276] Re: bionic/linux-hwe-5.0: 5.0.0-42.46~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863297 packages: main: linux-hwe-5.0 meta: linux-meta-hwe-5.0 signed: linux-signed-hwe-5.0 phase: Promote to Proposed phase-changed: Tuesday, 18. February 2020 09:59 UTC reason: - promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs -- 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/1863276 Title: bionic/linux-hwe-5.0: 5.0.0-42.46~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863297 packages: main: linux-hwe-5.0 meta: linux-meta-hwe-5.0 signed: linux-signed-hwe-5.0 phase: Promote to Proposed phase-changed: Tuesday, 18. February 2020 09:59 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863276/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849947] Re: Dell XPS 13 (7390) Display Flickering - 19.10
The patch to disable PSR fixes these glitches on my XPS laptops. Marking the bug as verified. ** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan -- 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/1849947 Title: Dell XPS 13 (7390) Display Flickering - 19.10 Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: In Progress Bug description: Hi there, I recently purchased a Dell XPS 13 7390 (Developer Edition). I decided to replace 18.4 LTS with 19.10 and so far it has been pretty smooth. However, there is one issue which occurs frequently whereby the display flickers and becomes unusable. The best way to describe the appearance is that the image becomes heavily distorted. Sometimes it only happens for a split second, other times it is permanently distorted. When this happens, simply closing the laptop lip and re-opening seems to put the display back into it's correct state. I didn't experience this issue on 18.04 LTS which is why I believe it's a Software Bug within 19.10. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 11:11:43 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2019-10-25 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 7390 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0G2D0W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd08/23/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849947/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863344] Re: xenial/linux-azure: 4.15.0-1072.77 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863350 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Promote to Proposed - phase-changed: Thursday, 20. February 2020 16:06 UTC + phase: Testing + phase-changed: Thursday, 20. February 2020 23:02 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + stakeholder-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1863343 xenial/linux-azure/azure-kernel: bug 1863342 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1863344 Title: xenial/linux-azure: 4.15.0-1072.77 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863350 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 20. February 2020 23:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1863343 xenial/linux-azure/azure-kernel: bug 1863342 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863344/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863347] Re: xenial/linux-gcp: 4.15.0-1056.60 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863350 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Promote to Proposed - phase-changed: Thursday, 20. February 2020 16:36 UTC + phase: Testing + phase-changed: Thursday, 20. February 2020 23:02 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress trackers: xenial/linux-gcp/gcp-kernel: bug 1863345 xenial/linux-gcp/gke-kernel: bug 1863346 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1863347 Title: xenial/linux-gcp: 4.15.0-1056.60 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863350 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Thursday, 20. February 2020 23:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-gcp/gcp-kernel: bug 1863345 xenial/linux-gcp/gke-kernel: bug 1863346 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863341] Re: bionic/linux-fips: 4.15.0-1024.29 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863350 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips - phase: Promote to Proposed - phase-changed: Thursday, 20. February 2020 21:56 UTC + phase: Ready for Promote to Proposed + phase-changed: Thursday, 20. February 2020 22:46 UTC reason: - promote-to-proposed: Pending -- package copied to Signing signed:queued + promote-signing-to-proposed: Pending -- ready for review variant: debs -- 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/1863341 Title: bionic/linux-fips: 4.15.0-1024.29 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863350 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Ready for Promote to Proposed phase-changed: Thursday, 20. February 2020 22:46 UTC reason: promote-signing-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863343] Re: trusty/linux-azure: 4.15.0-1072.77~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863344 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Promote to Proposed - phase-changed: Thursday, 20. February 2020 21:06 UTC + phase: Holding before Promote to Proposed + phase-changed: Thursday, 20. February 2020 22:28 UTC reason: - promote-to-proposed: Ongoing -- package copied to Signing signed:building + promote-signing-to-proposed: Stalled -- another kernel is currently pending in Proposed variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1863343 Title: trusty/linux-azure: 4.15.0-1072.77~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863344 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Thursday, 20. February 2020 22:28 UTC reason: promote-signing-to-proposed: Stalled -- another kernel is currently pending in Proposed variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863343/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838796] Re: TPM event log does not contain events measured after ExitBootServices
Hi Marcelo, Thanks for the information. I will try and validate the Linux-azure-edge kernel. Regarding your test environment, there are no issues. This is the expected environment for the guest OS. -Vinay -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1838796 Title: TPM event log does not contain events measured after ExitBootServices Status in linux package in Ubuntu: Won't Fix Status in linux-azure package in Ubuntu: In Progress Status in linux source package in Xenial: Won't Fix Status in linux-azure source package in Xenial: In Progress Status in linux source package in Disco: Won't Fix Status in linux-azure source package in Disco: In Progress Bug description: The TPM event log (/sys/kernel/security/tpm0/binary_bios_measurements) does not contain any events that are measured by UEFI after the kernel's EFI Boot stub calls ExitBootServices(). This means that PCR values calculated from the event log will not match the actual PCR values on the machine for PCR indices into which these events are measured. There are upstream patches to fix this in the mainline kernel tree: https://lore.kernel.org/lkml/20190520205501.177637-1-matthewgarr...@google.com/ --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-06-20 (43 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=fcb8dc9d-4dd3-490f-9f1c-fa6364770bb0 ro ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-22-generic N/A linux-backports-modules-4.18.0-22-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/30/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 8486-4870-7514-9524-5524-7794-69 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863778] Re: focal/linux-aws-5.4: 5.4.0-1001.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Canonical Kernel Team (canonical-kernel-team) => Andy Whitcroft (apw) -- 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/1863778 Title: focal/linux-aws-5.4: 5.4.0-1001.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1862255 packages: lrm: linux-restricted-modules-aws-5.4 main: linux-aws-5.4 meta: linux-meta-aws-5.4 phase: Ready for Promote to Proposed phase-changed: Tuesday, 18. February 2020 16:17 UTC reason: promote-to-proposed: Stalled -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863778/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863650] Re: focal/linux-oem-5.4: 5.4.0-1004.6 -proposed tracker
*** This bug is a duplicate of bug 1864079 *** https://bugs.launchpad.net/bugs/1864079 ** This bug has been marked a duplicate of bug 1864079 focal/linux-oem-5.4: -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1863650 Title: focal/linux-oem-5.4: 5.4.0-1004.6 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-oem-5.4 package in Ubuntu: Confirmed Status in linux-oem-5.4 source package in Focal: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1863657 packages: lrm: linux-restricted-modules-oem-5.4 main: linux-oem-5.4 meta: linux-meta-oem-5.4 signed: linux-signed-oem-5.4 phase: Packaging phase-changed: Wednesday, 19. February 2020 14:21 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863650/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863898] Re: More i915 fixes to cherry-pick
the patches from upstream #1201 are only for 5.5.x, not 5.4
but the first commit from #1164 is now sent to the stable list
--
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/1863898
Title:
More i915 fixes to cherry-pick
Status in linux package in Ubuntu:
Confirmed
Bug description:
The kernel is still a bit unstable, according to upstream this should
fix my recent hangs:
drm/i915/execlists: Always force a context reload when rewinding
RING_TAIL
https://gitlab.freedesktop.org/drm/intel/issues/1164
https://gitlab.freedesktop.org/drm/intel/issues/1150
Also there are some more crash patches in 5.6-rc1 that could be
cherry-picked back:
76f9764cc3d5 ("drm/i915: Introduce a vma.kref")
bbca083de291 ("drm/i915: Serialise i915_active_acquire() with
__active_retire()")
from https://gitlab.freedesktop.org/drm/intel/issues/1201
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863898/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863341] Re: bionic/linux-fips: 4.15.0-1024.29 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863350 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Promote to Proposed phase-changed: Thursday, 20. February 2020 21:56 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Pending -- package copied to Signing signed:queued variant: debs -- 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/1863341 Title: bionic/linux-fips: 4.15.0-1024.29 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863350 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Promote to Proposed phase-changed: Thursday, 20. February 2020 21:56 UTC reason: promote-to-proposed: Pending -- package copied to Signing signed:queued variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864080] Re: focal/linux-aws: 5.4.0-1002.2 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1864085 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws - phase: Packaging - phase-changed: Thursday, 20. February 2020 20:53 UTC - reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded + phase: Holding before Promote to Proposed + phase-changed: Thursday, 20. February 2020 22:22 UTC variant: debs -- 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/1864080 Title: focal/linux-aws: 5.4.0-1002.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-aws package in Ubuntu: Confirmed Status in linux-aws source package in Focal: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1864085 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Holding before Promote to Proposed phase-changed: Thursday, 20. February 2020 22:22 UTC variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861462] Re: Lenovo Thinkpad X1 Carbon 7th Gen doesn't suspend and resume
Seth - suspend does not work with dmic_detect disabled so it looks like it's something else. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1861462 Title: Lenovo Thinkpad X1 Carbon 7th Gen doesn't suspend and resume Status in linux-5.4 package in Ubuntu: Confirmed Status in linux-5.4 source package in Focal: Confirmed Bug description: Steps: 1. Install Ubuntu 20.04 daily image (tested Jan 29th, 2020 image) using default options. 2. apt update 3. apt upgrade 4. reboot so the machine is in pristine state 5. Close lid 6. Machine doesn't suspend (the light on the laptop power button doesn't pulsate) 7. Open the lid. The system doesn't respond and display is off 8. the only option is to power down the laptop and restart it. 9. upon restarting, Apport doesn't complain (this report was filed manually using ubuntu-bug) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Jan 30 18:56:41 2020 InstallationDate: Installed on 2020-01-30 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1861462/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863335] Re: bionic/linux-ibm-gt: 4.15.0-1049.55 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863350 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt - phase: Promote to Proposed - phase-changed: Thursday, 20. February 2020 21:51 UTC + phase: Testing + phase-changed: Thursday, 20. February 2020 22:02 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- review in progress + regression-testing: Ongoing -- testing in progress + verification-testing: Ongoing -- testing in progress variant: debs -- 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/1863335 Title: bionic/linux-ibm-gt: 4.15.0-1049.55 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863350 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Testing phase-changed: Thursday, 20. February 2020 22:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863341] Re: bionic/linux-fips: 4.15.0-1024.29 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863350 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips - phase: Ready for Promote to Proposed - phase-changed: Thursday, 20. February 2020 21:38 UTC + phase: Promote to Proposed + phase-changed: Thursday, 20. February 2020 21:56 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review in progress variant: debs -- 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/1863341 Title: bionic/linux-fips: 4.15.0-1024.29 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863350 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Promote to Proposed phase-changed: Thursday, 20. February 2020 21:56 UTC reason: promote-to-proposed: Ongoing -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863335] Re: bionic/linux-ibm-gt: 4.15.0-1049.55 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- 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/1863335 Title: bionic/linux-ibm-gt: 4.15.0-1049.55 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863350 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Promote to Proposed phase-changed: Thursday, 20. February 2020 21:51 UTC reason: promote-to-proposed: Ongoing -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863335] Re: bionic/linux-ibm-gt: 4.15.0-1049.55 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863350 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt - phase: Ready for Promote to Proposed - phase-changed: Thursday, 20. February 2020 21:37 UTC + phase: Promote to Proposed + phase-changed: Thursday, 20. February 2020 21:51 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review in progress variant: debs -- 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/1863335 Title: bionic/linux-ibm-gt: 4.15.0-1049.55 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863350 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Promote to Proposed phase-changed: Thursday, 20. February 2020 21:51 UTC reason: promote-to-proposed: Ongoing -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862776] Re: [MIR] alsa-ucm-conf & alsa-topology-conf (b-d of alsa-lib)
** Description changed: - [MIR] alsa-ucm-conf & alsa-topology-conf (b-d of alsa-lib) + * alsa-ucm-conf + + = Availability = + Built for all supported architectures as it's an arch all binary. + In sync with Debian. + https://launchpad.net/ubuntu/+source/alsa-ucm-conf/1.2.1.2-2 + + = Rationale = + It's providing data useful to alsa to know how to handle hardware + + = Security = + No known CVEs. + + https://security-tracker.debian.org/tracker/source-package/alsa-ucm-conf + https://launchpad.net/ubuntu/+source/alsa-ucm-conf/+cve + + = Quality assurance = + - Kernel Packages team needs to be subscribed. + - no tests, the package provides data file only + + https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf + https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=alsa-ucm-conf + + = Dependencies = + No universe binary dependencies, the package has no depends + + = Standards compliance = + standard dh12 packaging + + = Maintenance = + === + Maintainer with alsa upstream and in Debian + + + * alsa-topology-conf ** Changed in: alsa-ucm-conf (Ubuntu) Status: Incomplete => New ** Description changed: * alsa-ucm-conf = Availability = - Built for all supported architectures as it's an arch all binary. + Built for all supported architectures as it's an arch all binary. In sync with Debian. https://launchpad.net/ubuntu/+source/alsa-ucm-conf/1.2.1.2-2 - = Rationale = + = Rationale = It's providing data useful to alsa to know how to handle hardware - = Security = + = Security = No known CVEs. https://security-tracker.debian.org/tracker/source-package/alsa-ucm-conf https://launchpad.net/ubuntu/+source/alsa-ucm-conf/+cve = Quality assurance = - Kernel Packages team needs to be subscribed. - no tests, the package provides data file only https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=alsa-ucm-conf = Dependencies = No universe binary dependencies, the package has no depends = Standards compliance = standard dh12 packaging = Maintenance = - === Maintainer with alsa upstream and in Debian * alsa-topology-conf + + = Availability = + Built for all supported architectures as it's an arch all binary. + In sync with Debian. + https://launchpad.net/ubuntu/+source/alsa-topology-conf/1.2.1-2 + + = Rationale = + It's providing data useful to alsa to know how to handle hardware + + = Security = + No known CVEs. + + https://security-tracker.debian.org/tracker/source-package/alsa-topology-conf + https://launchpad.net/ubuntu/+source/alsa-topology-conff/+cve + + = Quality assurance = + - Kernel Packages team needs to be subscribed. + - no tests, the package provides data file only + + https://bugs.launchpad.net/ubuntu/+source/alsa-topology-conf + https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=alsa-topology-conf + + = Dependencies = + No universe binary dependencies, the package has no depends + + = Standards compliance = + standard dh12 packaging + + = Maintenance = + Maintainer with alsa upstream and in Debian ** Changed in: alsa-topology-conf (Ubuntu) Status: Incomplete => New ** Description changed: * alsa-ucm-conf = Availability = Built for all supported architectures as it's an arch all binary. In sync with Debian. https://launchpad.net/ubuntu/+source/alsa-ucm-conf/1.2.1.2-2 = Rationale = It's providing data useful to alsa to know how to handle hardware = Security = No known CVEs. https://security-tracker.debian.org/tracker/source-package/alsa-ucm-conf https://launchpad.net/ubuntu/+source/alsa-ucm-conf/+cve = Quality assurance = - Kernel Packages team needs to be subscribed. - no tests, the package provides data file only https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=alsa-ucm-conf = Dependencies = No universe binary dependencies, the package has no depends = Standards compliance = standard dh12 packaging = Maintenance = - Maintainer with alsa upstream and in Debian - + Maintained with alsa upstream and in Debian * alsa-topology-conf = Availability = Built for all supported architectures as it's an arch all binary. In sync with Debian. https://launchpad.net/ubuntu/+source/alsa-topology-conf/1.2.1-2 = Rationale = It's providing data useful to alsa to know how to handle hardware = Security = No known CVEs. https://security-tracker.debian.org/tracker/source-package/alsa-topology-conf https://launchpad.net/ubuntu/+source/alsa-topology-conff/+cve = Quality assurance = - Kernel Packages team needs to be subscribed. - no tests, the package provides data file only https://bugs.launchpad.net/ubuntu/+source/alsa-topology-conf https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=alsa-topology-conf = Dependencies = No universe binary dependencies, the package has no
[Kernel-packages] [Bug 1863341] Re: bionic/linux-fips: 4.15.0-1024.29 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- 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/1863341 Title: bionic/linux-fips: 4.15.0-1024.29 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863350 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Promote to Proposed phase-changed: Thursday, 20. February 2020 21:56 UTC reason: promote-to-proposed: Ongoing -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863341] Re: bionic/linux-fips: 4.15.0-1024.29 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1863350 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips - phase: Holding before Promote to Proposed - phase-changed: Thursday, 20. February 2020 18:06 UTC + phase: Ready for Promote to Proposed + phase-changed: Thursday, 20. February 2020 21:38 UTC + reason: + promote-to-proposed: Pending -- ready for review variant: debs -- 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/1863341 Title: bionic/linux-fips: 4.15.0-1024.29 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863350 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Ready for Promote to Proposed phase-changed: Thursday, 20. February 2020 21:38 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863335] Re: bionic/linux-ibm-gt: 4.15.0-1049.55 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1863350 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt - phase: Holding before Promote to Proposed - phase-changed: Thursday, 20. February 2020 17:57 UTC + phase: Ready for Promote to Proposed + phase-changed: Thursday, 20. February 2020 21:37 UTC + reason: + promote-to-proposed: Pending -- ready for review variant: debs -- 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/1863335 Title: bionic/linux-ibm-gt: 4.15.0-1049.55 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863350 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Ready for Promote to Proposed phase-changed: Thursday, 20. February 2020 21:37 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863276] Re: bionic/linux-hwe-5.0: 5.0.0-42.46~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863297 packages: main: linux-hwe-5.0 meta: linux-meta-hwe-5.0 signed: linux-signed-hwe-5.0 phase: Promote to Proposed phase-changed: Tuesday, 18. February 2020 09:59 UTC reason: - promote-to-proposed: Stalled -- review in progress + promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait variant: debs -- 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/1863276 Title: bionic/linux-hwe-5.0: 5.0.0-42.46~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863297 packages: main: linux-hwe-5.0 meta: linux-meta-hwe-5.0 signed: linux-signed-hwe-5.0 phase: Promote to Proposed phase-changed: Tuesday, 18. February 2020 09:59 UTC reason: promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863276/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863343] Re: trusty/linux-azure: 4.15.0-1072.77~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863344 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Promote to Proposed phase-changed: Thursday, 20. February 2020 21:06 UTC reason: - promote-to-proposed: Stalled -- review in progress + promote-to-proposed: Pending -- package copied to Signing signed:retry-needed variant: debs ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863344 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Promote to Proposed phase-changed: Thursday, 20. February 2020 21:06 UTC reason: - promote-to-proposed: Pending -- package copied to Signing signed:retry-needed + promote-to-proposed: Ongoing -- package copied to Signing signed:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1863343 Title: trusty/linux-azure: 4.15.0-1072.77~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863344 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Promote to Proposed phase-changed: Thursday, 20. February 2020 21:06 UTC reason: promote-to-proposed: Ongoing -- package copied to Signing signed:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863343/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863344] Re: xenial/linux-azure: 4.15.0-1072.77 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863350 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Promote to Proposed phase-changed: Thursday, 20. February 2020 16:06 UTC reason: - promote-to-proposed: Pending -- package copied to Proposed signed:queued + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: trusty/linux-azure: bug 1863343 xenial/linux-azure/azure-kernel: bug 1863342 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1863344 Title: xenial/linux-azure: 4.15.0-1072.77 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863350 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Promote to Proposed phase-changed: Thursday, 20. February 2020 16:06 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: trusty/linux-azure: bug 1863343 xenial/linux-azure/azure-kernel: bug 1863342 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863344/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863347] Re: xenial/linux-gcp: 4.15.0-1056.60 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863350 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Proposed phase-changed: Thursday, 20. February 2020 16:36 UTC reason: - promote-to-proposed: Pending -- package copied to Proposed signed:queued + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: xenial/linux-gcp/gcp-kernel: bug 1863345 xenial/linux-gcp/gke-kernel: bug 1863346 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1863347 Title: xenial/linux-gcp: 4.15.0-1056.60 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863350 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Proposed phase-changed: Thursday, 20. February 2020 16:36 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: xenial/linux-gcp/gcp-kernel: bug 1863345 xenial/linux-gcp/gke-kernel: bug 1863346 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863489] Re: intel grafic i915 driver no power saving states rc6
I am pretty sure, that these mentioned bugs are same issue. Thanks. I found this enable_rc6 has been removed due to stability issues. Do you think Ubuntu will backport 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/1863489 Title: intel grafic i915 driver no power saving states rc6 Status in linux package in Ubuntu: Incomplete Bug description: It seems that the i915 intel graphic driver in newer kernels (observed with 5.3) doesn't support energy saving. How do I know that? Using powertop shows in idle tab the GPU - and this shows only : GPU power on 100% - no rc6 or deeper states are used. For some strange reason also the packet (summery?) shows in all states 0%, although I can observe the individual CPU cores are in different power states. The previous parameter enable_rc6 is not existing anymore. The other possible energy saving parameter enable_dc (if set to 1 or 2) results in log with: setting dangerous option enable_dc - tainting kernel. Any idea what might go wrong there? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863489/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863343] Re: trusty/linux-azure: 4.15.0-1072.77~14.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863344 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Ready for Promote to Proposed - phase-changed: Wednesday, 19. February 2020 06:42 UTC + phase: Promote to Proposed + phase-changed: Thursday, 20. February 2020 21:06 UTC reason: - promote-to-proposed: Stalled -- ready for review + promote-to-proposed: Stalled -- review in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1863343 Title: trusty/linux-azure: 4.15.0-1072.77~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863344 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Promote to Proposed phase-changed: Thursday, 20. February 2020 21:06 UTC reason: promote-to-proposed: Stalled -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863343/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863343] Re: trusty/linux-azure: 4.15.0-1072.77~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1863343 Title: trusty/linux-azure: 4.15.0-1072.77~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863344 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Promote to Proposed phase-changed: Thursday, 20. February 2020 21:06 UTC reason: promote-to-proposed: Stalled -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863343/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863347] Re: xenial/linux-gcp: 4.15.0-1056.60 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863350 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Proposed phase-changed: Thursday, 20. February 2020 16:36 UTC reason: - promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait + promote-to-proposed: Pending -- package copied to Proposed signed:queued trackers: xenial/linux-gcp/gcp-kernel: bug 1863345 xenial/linux-gcp/gke-kernel: bug 1863346 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1863347 Title: xenial/linux-gcp: 4.15.0-1056.60 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863350 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Proposed phase-changed: Thursday, 20. February 2020 16:36 UTC reason: promote-to-proposed: Pending -- package copied to Proposed signed:queued trackers: xenial/linux-gcp/gcp-kernel: bug 1863345 xenial/linux-gcp/gke-kernel: bug 1863346 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864080] Re: focal/linux-aws: 5.4.0-1002.2 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1864085 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws - phase: Holding before Packaging - phase-changed: Thursday, 20. February 2020 17:22 UTC + phase: Packaging + phase-changed: Thursday, 20. February 2020 20:53 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded variant: debs -- 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/1864080 Title: focal/linux-aws: 5.4.0-1002.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-aws package in Ubuntu: Confirmed Status in linux-aws source package in Focal: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1864085 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Packaging phase-changed: Thursday, 20. February 2020 20:53 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863310] Re: bionic/linux-snapdragon: 4.15.0-1073.80 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1863310 Title: bionic/linux-snapdragon: 4.15.0-1073.80 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863350 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Thursday, 20. February 2020 15:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1863308 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863310/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863324] Re: xenial/linux-raspi2: 4.4.0-1130.139 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1863324 Title: xenial/linux-raspi2: 4.4.0-1130.139 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863338 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Thursday, 20. February 2020 16:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-raspi2/pi2-kernel: bug 1863322 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863311] Re: xenial/linux-aws: 4.4.0-1103.114 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- 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/1863311 Title: xenial/linux-aws: 4.4.0-1103.114 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863338 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Thursday, 20. February 2020 16:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-aws/aws-kernel: bug 1863309 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863311/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863329] Re: xenial/linux-snapdragon: 4.4.0-1134.142 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1863329 Title: xenial/linux-snapdragon: 4.4.0-1134.142 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863338 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Thursday, 20. February 2020 17:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1863326 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863329/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864080] Re: focal/linux-aws: 5.4.0-1002.2 -proposed tracker
** Summary changed: - focal/linux-aws: -proposed tracker + focal/linux-aws: 5.4.0-1002.2 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee (sforshee) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee (sforshee) -- 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/1864080 Title: focal/linux-aws: 5.4.0-1002.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-aws package in Ubuntu: Confirmed Status in linux-aws source package in Focal: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1864085 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Packaging phase-changed: Thursday, 20. February 2020 20:53 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837828] Re: alsa/sof: let legacy hda driver and sof driver co-exist
It seems this fix breaks the sound on my machine. Here's the bug report: https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1864061 -- 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/1837828 Title: alsa/sof: let legacy hda driver and sof driver co-exist Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Eoan: Fix Committed Status in linux-oem-osp1 source package in Eoan: Invalid Bug description: [Impact] So far, if we want the sof driver to work, we need to blacklist snd_hda_intel.ko, but on some paltforms with nv hdmi or amd hdmi, we need these two driver co-exist. [Fix] Intel sent the patches to fix this issue, although it is not merged yet, but I guess they will pass the review and be merged. So i backported them first. [Test Case] remove snd_hda_intel.ko from blacklist, the two drivers (sof and hda) worked well. [Regression Risk] Low. We already tested these patches on some Dell machines. and comunity including endlessm and goole all tested these patches. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1837828/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860800] Re: Ubuntu 19.10 doesn't shutdown
Now my laptop sometimes doesn't reboot. When it should boot, it tries to but soon breaks down. When I unplag the charger and a wait a few seconds it will boot. Can anyone explain this? I will test if the same problem appears with other distributions and write it here. -- 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/1860800 Title: Ubuntu 19.10 doesn't shutdown Status in linux package in Ubuntu: Confirmed Bug description: Hello guys, I can't shutdown Ubuntu 19.10. When I try, the shutdown screen appears. The first two dots below the ubuntu logo, turn orange and then it freezes. Reboot works fine. The debug-shell is no use, because at the freeze point I can't type in commands. When I press ESC to see what's going on during shutdown, the last message to appear ist "[Some weird number] reboot: power down. Last time I pressed ESC during shutdown the "weird number" was 85.270119. I also tried to shutdown with the terminal commands "sudo shutdown now", "sudo shutdown -P now", "sudo shutdown -h now", "poweroff" and "sudo poweroff -f". All of them had the effect as describe above except the command "sudo poweroff -f". After I typed in the command, I authenticated and following messages appeared: "Powering off...". At this point it freezed. I could still see the desktop and every visible window, but I couldn't perform any actions; not even keyboard shortcuts worked. It also did not help to change 'GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"' in /etc/default/grub to 'GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force"' and run "update-grub". Once the following command combo did work: "sudo swapoff -a && systemctl poweroff", but the I reinstalled Ubuntu and now it doesn't work any more. In the application "Additional Drivers" I selected the proprietary and tested driver of NVIDIA, but I can't to this for my WLAN-Card (correct word?), because the "Additional Drivers" says it's not working, but my WLAN works fine. I've got only Bluetooth problems. The displayed name of the WLAN-Card is: "Intel Corporation: Wireless 7260 (Dual Band Wireless-AC 7260)". I also tried to manually install a driver it didn't help. When I wake up the laptop, a black screen appears with some error messages, but only for a very short time so I can't make a photo of it. I tried once and the text was unreadable. I have the latest BIOS and my Computer model is MSI PX60 2QD. It doesn't work with Arch Linux either. Thanks for your help :) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leonard1724 F pulseaudio /dev/snd/controlC1: leonard1724 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-18 (7 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. PX60 2QD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=04df7493-393f-447e-bfb3-3dc43c2ee645 ro quiet splash acpi=force vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16H6IMS.110 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16H6 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16H6IMS.110:bd11/03/2015:svnMicro-StarInternationalCo.,Ltd.:pnPX602QD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H6:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: PX60 2QD dmi.product.sku: To be filled by O.E.M. dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860800/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
I've never written drivers before but if someone wants to work on this with me, I'd love to help out. -- 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/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851987] Re: Long boot times, ACPI error messages in dmesg
I'm a complete noob so sorry for no logs, but I have the exact same configuration "I have a lenovo legion Y540 15IRH with nvidia 1660 ti" (don't know how to check motherboard) and the exact same message. Tried booting Kali Linux and Ubuntu. Worked for me the week previous, I think but after I updated BIOS drivers booting no longer works. Kai-Heng, you're saying they're harmless but for me booting stops and there is a weird, not moving, glitch on the screen. ** Attachment added: "IMG_0062.JPG" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851987/+attachment/5329862/+files/IMG_0062.JPG -- 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/1851987 Title: Long boot times, ACPI error messages in dmesg Status in linux package in Ubuntu: Incomplete Bug description: I have a lenovo legion Y540 15IRH with nvidia 1660 ti and LNVNB161216 mother board and when i type (dmesg) command i get this [0.212539] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.TPLD], AE_ALREADY_EXISTS (20190703/dswload2-323) [0.212546] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190703/psobject-220) [0.212548] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.212597] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323) [0.212601] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190703/psobject-220) [0.212603] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.212604] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323) [0.212607] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190703/psobject-220) [0.212608] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.215043] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS02._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323) [0.215047] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190703/psobject-220) [0.215049] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.215050] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS02._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323) [0.215053] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190703/psobject-220) [0.215054] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.217473] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS03._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323) [0.217476] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190703/psobject-220) [0.217478] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.217480] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS03._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323) [0.217482] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190703/psobject-220) [0.217483] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.219901] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS04._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323) [0.219905] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190703/psobject-220) [0.219906] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.219908] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS04._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323) [0.219910] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190703/psobject-220) [0.219912] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.222324] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS05._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323) [0.222327] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190703/psobject-220) [0.222329] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.224748] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS06._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323) [0.224752] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190703/psobject-220) [0.224753] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.224755] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS06._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323) [0.224757] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190703/psobject-220) [0.224759] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.227173] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS07._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323) [0.227176] ACPI Error: AE_ALREADY_EXISTS, During name
[Kernel-packages] [Bug 1864085] Re: focal/linux: 5.4.0-15.18 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: Fix Committed => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Thursday, 20. February 2020 17:42 UTC
reason:
- prepare-package: Pending -- package not yet uploaded
- prepare-package-meta: Pending -- package not yet uploaded
- prepare-package-signed: Pending -- package not yet uploaded
+ prepare-package: Ongoing -- {} package not yet fully built
trackers:
focal/linux-aws: bug 1864080
focal/linux-azure: bug 1864081
focal/linux-gcp: bug 1864082
focal/linux-kvm: bug 1864083
focal/linux-oem-5.4: bug 1864079
focal/linux-oracle: bug 1864084
focal/linux-raspi2: bug 1864078
focal/linux/pc-kernel: bug 1864075
focal/linux/pc-lowlatency-kernel: bug 1864076
variant: debs
--
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/1864085
Title:
focal/linux: 5.4.0-15.18 -proposed tracker
Status in Kernel SRU Workflow:
In Progress
Status in Kernel SRU Workflow automated-testing series:
New
Status in Kernel SRU Workflow prepare-package series:
Fix Committed
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
New
Status in Kernel SRU Workflow promote-to-release series:
New
Status in Kernel SRU Workflow regression-testing series:
New
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Focal:
Confirmed
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Thursday, 20. February 2020 17:42 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
trackers:
focal/linux-aws: bug 1864080
focal/linux-azure: bug 1864081
focal/linux-gcp: bug 1864082
focal/linux-kvm: bug 1864083
focal/linux-oem-5.4: bug 1864079
focal/linux-oracle: bug 1864084
focal/linux-raspi2: bug 1864078
focal/linux/pc-kernel: bug 1864075
focal/linux/pc-lowlatency-kernel: bug 1864076
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864085/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829983] Re: memcg_stat from controllers test suite in LTP failed
** Tags added: sru-20200217 -- 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/1829983 Title: memcg_stat from controllers test suite in LTP failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-aws source package in Xenial: New Status in linux source package in Bionic: Confirmed Status in linux-aws source package in Bionic: New Status in linux source package in Cosmic: Confirmed Status in linux-aws source package in Cosmic: New Bug description: memcg_stat_test 1 TINFO: Starting test 1 sh: echo: I/O error memcg_stat_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 1 TINFO: Running memcg_process --shm -k 3 -s 135168 memcg_stat_test 1 TINFO: Warming up pid: 31352 memcg_stat_test 1 TINFO: Process is still here after warm up: 31352 memcg_stat_test 1 TPASS: cache is 135168 as expected memcg_stat_test 2 TINFO: Starting test 2 sh: echo: I/O error memcg_stat_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 2 TINFO: Running memcg_process --mmap-file -s 135168 memcg_stat_test 2 TINFO: Warming up pid: 31380 memcg_stat_test 2 TINFO: Process is still here after warm up: 31380 memcg_stat_test 2 TPASS: mapped_file is 135168 as expected memcg_stat_test 3 TINFO: Starting test 3 sh: echo: I/O error memcg_stat_test 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 3 TINFO: Running memcg_process --mmap-lock1 -s 4096 memcg_stat_test 3 TINFO: Warming up pid: 31409 memcg_stat_test 3 TINFO: Process is still here after warm up: 31409 memcg_stat_test 3 TPASS: unevictable is 4096 as expected memcg_stat_test 4 TINFO: Starting test 4 sh: echo: I/O error memcg_stat_test 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 4 TINFO: Running memcg_process --mmap-lock2 -s 4096 memcg_stat_test 4 TINFO: Warming up pid: 31434 memcg_stat_test 4 TINFO: Process is still here after warm up: 31434 memcg_stat_test 4 TPASS: unevictable is 4096 as expected memcg_stat_test 5 TINFO: Starting test 5 sh: echo: I/O error memcg_stat_test 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 5 TPASS: hierarchical_memory_limit is 4096 as expected memcg_stat_test 6 TINFO: Starting test 6 sh: echo: I/O error memcg_stat_test 6 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed sh: echo: I/O error memcg_stat_test 6 TFAIL: hierarchical_memory_limit is 4096, 8192 expected memcg_stat_test 7 TINFO: Starting test 7 sh: echo: I/O error memcg_stat_test 7 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 7 TCONF: mem+swap is not enabled memcg_stat_test 7 TINFO: Starting test 8 sh: echo: I/O error memcg_stat_test 7 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 7 TCONF: mem+swap is not enabled tag=memcg_stat stime=1558504742 dur=4 exit=exited stat=33 core=no cu=16 cs=10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [14538.862950] cfg80211: Loading compiled-in X.509 certificates for regulatory database [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Date: Wed May 22 07:17:43 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version:
[Kernel-packages] [Bug 1829989] Re: memcg_use_hierarchy from controllers test suite in LTP failed
** Tags added: sru-20200217 -- 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/1829989 Title: memcg_use_hierarchy from controllers test suite in LTP failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: Triaged Status in linux source package in Bionic: Confirmed Status in linux-aws source package in Bionic: New Status in linux source package in Cosmic: Confirmed Status in linux-aws source package in Cosmic: New Bug description: startup='Wed May 22 05:59:07 2019' memcg_use_hierarchy_test 1 TINFO: Starting test 1 sh: echo: I/O error memcg_use_hierarchy_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_use_hierarchy_test 1 TPASS: process 31577 is killed memcg_use_hierarchy_test 2 TINFO: Starting test 2 sh: echo: I/O error memcg_use_hierarchy_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_use_hierarchy_test 2 TFAIL: echo 1 > memory.use_hierarchy passed unexpectedly memcg_use_hierarchy_test 3 TINFO: Starting test 3 sh: echo: I/O error memcg_use_hierarchy_test 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_use_hierarchy_test 3 TPASS: echo 0 > subgroup/memory.use_hierarchy failed as expected tag=memcg_use_hierarchy stime=1558504747 dur=1 exit=exited stat=1 core=no cu=5 cs=5 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [14538.862950] cfg80211: Loading compiled-in X.509 certificates for regulatory database [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Date: Wed May 22 07:33:33 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829989/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829979] Re: memcg_max_usage_in_bytes from controllers test suite in LTP failed
*** This bug is a duplicate of bug 1829984 *** https://bugs.launchpad.net/bugs/1829984 ** Tags added: sru-20200217 ** This bug has been marked a duplicate of bug 1829984 memcg_usage_in_bytes from controllers test suite in LTP failed -- 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/1829979 Title: memcg_max_usage_in_bytes from controllers test suite in LTP failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-aws source package in Bionic: New Bug description: startup='Wed May 22 05:58:50 2019' memcg_max_usage_in_bytes_test 1 TINFO: Starting test 1 sh: echo: I/O error memcg_max_usage_in_bytes_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_max_usage_in_bytes_test 1 TINFO: Running memcg_process --mmap-anon -s 4194304 memcg_max_usage_in_bytes_test 1 TINFO: Warming up pid: 30821 memcg_max_usage_in_bytes_test 1 TINFO: Process is still here after warm up: 30821 memcg_max_usage_in_bytes_test 1 TFAIL: memory.max_usage_in_bytes is 4325376, 4194304 expected memcg_max_usage_in_bytes_test 2 TINFO: Starting test 2 sh: echo: I/O error memcg_max_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_max_usage_in_bytes_test 2 TCONF: mem+swap is not enabled memcg_max_usage_in_bytes_test 2 TINFO: Starting test 3 sh: echo: I/O error memcg_max_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_max_usage_in_bytes_test 2 TINFO: Running memcg_process --mmap-anon -s 4194304 memcg_max_usage_in_bytes_test 2 TINFO: Warming up pid: 30855 memcg_max_usage_in_bytes_test 2 TINFO: Process is still here after warm up: 30855 memcg_max_usage_in_bytes_test 2 TFAIL: memory.max_usage_in_bytes is 4329472, 4194304 expected memcg_max_usage_in_bytes_test 3 TFAIL: memory.max_usage_in_bytes is 8192, 0 expected memcg_max_usage_in_bytes_test 4 TINFO: Starting test 4 sh: echo: I/O error memcg_max_usage_in_bytes_test 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_max_usage_in_bytes_test 4 TCONF: mem+swap is not enabled tag=memcg_max_usage_in_bytes stime=1558504730 dur=3 exit=exited stat=33 core=no cu=8 cs=7 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [14538.862950] cfg80211: Loading compiled-in X.509 certificates for regulatory database [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Date: Wed May 22 07:06:31 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829979/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829984] Re: memcg_usage_in_bytes from controllers test suite in LTP failed
** Tags added: sru-20200217 -- 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/1829984 Title: memcg_usage_in_bytes from controllers test suite in LTP failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-aws source package in Xenial: New Status in linux source package in Bionic: Confirmed Status in linux-aws source package in Bionic: New Status in linux source package in Cosmic: Confirmed Status in linux-aws source package in Cosmic: New Bug description: startup='Wed May 22 05:59:09 2019' memcg_usage_in_bytes_test 1 TINFO: Starting test 1 sh: echo: I/O error memcg_usage_in_bytes_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_usage_in_bytes_test 1 TINFO: Running memcg_process --mmap-anon -s 4194304 memcg_usage_in_bytes_test 1 TINFO: Warming up pid: 31689 memcg_usage_in_bytes_test 1 TINFO: Process is still here after warm up: 31689 memcg_usage_in_bytes_test 1 TFAIL: memory.usage_in_bytes is 4202496, 4194304 expected memcg_usage_in_bytes_test 2 TINFO: Starting test 2 sh: echo: I/O error memcg_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_usage_in_bytes_test 2 TCONF: mem+swap is not enabled tag=memcg_usage_in_bytes stime=1558504749 dur=1 exit=exited stat=33 core=no cu=5 cs=3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [14538.862950] cfg80211: Loading compiled-in X.509 certificates for regulatory database [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Date: Wed May 22 07:17:43 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829984/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837543] Re: crypto_user02 in crypto from ubuntu_ltp failed
** Tags added: sru-20200217 -- 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/1837543 Title: crypto_user02 in crypto from ubuntu_ltp failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-aws source package in Bionic: Confirmed Status in linux source package in Disco: Confirmed Status in linux-aws source package in Disco: New Status in linux source package in Eoan: Confirmed Status in linux-aws source package in Eoan: New Bug description: This is a new test, test will fail with: <<>> tag=crypto_user02 stime=1563881396 cmdline="crypto_user02" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s crypto_user02.c:59: INFO: Starting crypto_user larval deletion test. May crash buggy kernels. crypto_user02.c:91: BROK: unexpected error from tst_crypto_del_alg(): EBUSY Summary: passed 0 failed 0 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=2 corefile=no cutime=0 cstime=0 <<>> Nothing interesting in syslog: Jul 23 11:29:20 amaura systemd[1]: Started Session 1 of user ubuntu. Jul 23 11:29:56 amaura kernel: [ 619.646330] LTP: starting crypto_user02 Jul 23 11:30:23 amaura kernel: [ 646.554403] cfg80211: Loading compiled-in X.509 certificates for regulatory database Steps to run this test: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "crypto_user02 crypto_user02" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-21-generic 5.0.0-21.22 ProcVersionSignature: User Name 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 23 11:19 seq crw-rw 1 root audio 116, 33 Jul 23 11:19 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jul 23 11:30:15 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.178.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.sku: To be filled by O.E.M. dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1837543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829849] Re: proc01 in fs from ubuntu_ltp failed with D/B/E
** Changed in: linux-aws (Ubuntu) Status: New => Triaged ** Tags added: sru-20200217 ** Tags added: 5.0 -- 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/1829849 Title: proc01 in fs from ubuntu_ltp failed with D/B/E Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: Triaged Bug description: proc01 0 TINFO : /proc/sys/fs/binfmt_misc/register: is write-only. proc01 0 TINFO : /proc/sys/net/ipv6/conf/all/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/default/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/ens6/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/lo/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/kmsg: known issue: errno=EAGAIN/EWOULDBLOCK(11): Resource temporarily unavailable proc01 0 TINFO : /proc/sysrq-trigger: is write-only. proc01 0 TINFO : /proc/self/task/8782/mem: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/self/task/8782/clear_refs: is write-only. proc01 0 TINFO : /proc/self/task/8782/pagemap: reached maxmbytes (-m) proc01 0 TINFO : /proc/self/task/8782/attr/prev: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/exec: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/fscreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/keycreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/sockcreate: known issue: errno=EINVAL(22): Invalid argument proc01 1 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/current: errno=EINVAL(22): Invalid argument proc01 2 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/prev: errno=EINVAL(22): Invalid argument proc01 3 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/exec: errno=EINVAL(22): Invalid argument proc01 4 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument proc01 5 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument proc01 6 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument proc01 7 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/smack/current: errno=EINVAL(22): Invalid argument proc01 8 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/apparmor/prev: errno=EINVAL(22): Invalid argument proc01 9 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/apparmor/exec: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/mem: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/self/clear_refs: is write-only. proc01 0 TINFO : /proc/self/pagemap: reached maxmbytes (-m) proc01 0 TINFO : /proc/self/attr/prev: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/exec: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/fscreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/keycreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/sockcreate: known issue: errno=EINVAL(22): Invalid argument proc01 10 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/current: errno=EINVAL(22): Invalid argument proc01 11 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/prev: errno=EINVAL(22): Invalid argument proc01 12 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/exec: errno=EINVAL(22): Invalid argument proc01 13 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument proc01 14 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument proc01 15 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument proc01 16 TFAIL : proc01.c:397: read failed: /proc/self/attr/smack/current: errno=EINVAL(22): Invalid argument proc01 17 TFAIL : proc01.c:397: read failed: /proc/self/attr/apparmor/prev: errno=EINVAL(22): Invalid argument proc01 18 TFAIL
