[Kernel-packages] [Bug 2077376] [NEW] package nvidia-dkms-535 535.183.01-0ubuntu0.24.04.1 failed to install/upgrade: installed nvidia-dkms-535 package post-installation script subprocess returned erro
Public bug reported: whiles installing nvidia dkms 535 ProblemType: Package DistroRelease: Ubuntu 24.04 Package: nvidia-dkms-535 535.183.01-0ubuntu0.24.04.1 ProcVersionSignature: Ubuntu 6.8.0-40.40-generic 6.8.12 Uname: Linux 6.8.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./casper/minimal.de.squashfs ./casper/minimal.standard.squashfs CasperMD5CheckResult: fail Date: Tue Aug 20 02:32:56 2024 ErrorMessage: installed nvidia-dkms-535 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2024-08-20 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.6ubuntu6.1 apt 2.7.14build2 SourcePackage: nvidia-graphics-drivers-535 Title: package nvidia-dkms-535 535.183.01-0ubuntu0.24.04.1 failed to install/upgrade: installed nvidia-dkms-535 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package noble -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2077376 Title: package nvidia-dkms-535 535.183.01-0ubuntu0.24.04.1 failed to install/upgrade: installed nvidia-dkms-535 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-535 package in Ubuntu: New Bug description: whiles installing nvidia dkms 535 ProblemType: Package DistroRelease: Ubuntu 24.04 Package: nvidia-dkms-535 535.183.01-0ubuntu0.24.04.1 ProcVersionSignature: Ubuntu 6.8.0-40.40-generic 6.8.12 Uname: Linux 6.8.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./casper/minimal.de.squashfs ./casper/minimal.standard.squashfs CasperMD5CheckResult: fail Date: Tue Aug 20 02:32:56 2024 ErrorMessage: installed nvidia-dkms-535 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2024-08-20 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.6ubuntu6.1 apt 2.7.14build2 SourcePackage: nvidia-graphics-drivers-535 Title: package nvidia-dkms-535 535.183.01-0ubuntu0.24.04.1 failed to install/upgrade: installed nvidia-dkms-535 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2077376/+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 2077187] [NEW] Windows repositioned on monitor wake after latest update
Public bug reported: 1) Ubuntu 22.04.4 LTS 2) 470.256.02-0ubuntu0.22.04.1 3) After monitor sleeps and wakes, windows have same positions and sizes as when monitor went to sleep 4) After monitor sleeps and wakes, windows have different positions and sizes Since installing version 470.256.02-0ubuntu0.22.04.1, the positioning of all open windows is scrambled after the monitor sleeps then wakes. I only have a single primary monitor and this has not been a problem in the past. ** Affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/2077187 Title: Windows repositioned on monitor wake after latest update Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: 1) Ubuntu 22.04.4 LTS 2) 470.256.02-0ubuntu0.22.04.1 3) After monitor sleeps and wakes, windows have same positions and sizes as when monitor went to sleep 4) After monitor sleeps and wakes, windows have different positions and sizes Since installing version 470.256.02-0ubuntu0.22.04.1, the positioning of all open windows is scrambled after the monitor sleeps then wakes. I only have a single primary monitor and this has not been a problem in the past. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2077187/+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 2044657] Re: Multiple data corruption issues in zfs
Actually, it may not be an issue even for Jammy HWE. My copy shows block
cloning as an option that's off.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2044657
Title:
Multiple data corruption issues in zfs
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Xenial:
Confirmed
Status in zfs-linux source package in Bionic:
Confirmed
Status in zfs-linux source package in Focal:
Fix Released
Status in zfs-linux source package in Jammy:
Fix Released
Status in zfs-linux source package in Lunar:
Won't Fix
Status in zfs-linux source package in Mantic:
Fix Released
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
[ Impact ]
* Multiple data corruption issues have been identified and fixed in
ZFS. Some of them, at varying real-life reproducibility frequency have
been deterimed to affect very old zfs releases. Recommendation is to
upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
ensure users get other potentially related fixes and runtime tunables
to possibly mitigate other bugs that are related and are being fixed
upstream for future releases.
* For jammy the 2.1.14 upgrade will bring HWE kernel support and also
compatiblity/support for hardened kernel builds that mitigate SLS
(straight-line-speculation).
* In the absence of the upgrade a cherry-pick will address this
particular popular issue alone - without addressing other issues
w.r.t. Redbleed / SLS, bugfixes around trim support, and other related
improvements that were discovered and fixed around the same time as
this popular issue.
[ Test Plan ]
* !!! Danger !!! use reproducer from
https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
and confirm if that issue is resolved or not. Do not run on production
ZFS pools / systems.
* autopkgtest pass (from https://ubuntu-archive-
team.ubuntu.com/proposed-migration/ )
* adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )
* kernel regression zfs testsuite pass (from Kernel team RT test
results summary, private)
* zsys integration test pass (upgrade of zsys installed systems for
all releases)
* zsys install test pass (for daily images of LTS releases only that
have such installer support, as per iso tracker test case)
* LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
2.1.14, and test LXD on these updated kernels)
[ Where problems could occur ]
* Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will
introduce slight slow down on amd64 (for hw accelerated assembly code-
paths only in the encryption primitives)
* Uncertain of the perfomance impact of the extra checks in dnat
patch fix itself. Possibly affecting speed of operation, at the
benefit of correctness.
* The cherry-picked patch ("dnat"? dnode) changes the dirty data check, but
only makes it stronger and not weaker, thus if it were incorrect, likely
only performance would be impacted (and it is unlikely to be incorrect
given upstream reviews and attention to data corruption issues; also,
there are no additional changes to that function upstream)
[ Other Info ]
* https://github.com/openzfs/zfs/pull/15571 is most current
consideration of affairs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+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 2044657] Re: Multiple data corruption issues in zfs
This issue is different. It's another problem with block copy. But
that's known to still be an issue. It's why block copy is disabled in
2.2.1. This is only an issue for the Jammy HWE, which has 2.2.0. No one
should be shipping 2.2.0 with anything. It should be replaced with 2.2.1
at least.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2044657
Title:
Multiple data corruption issues in zfs
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Xenial:
Confirmed
Status in zfs-linux source package in Bionic:
Confirmed
Status in zfs-linux source package in Focal:
Fix Released
Status in zfs-linux source package in Jammy:
Fix Released
Status in zfs-linux source package in Lunar:
Won't Fix
Status in zfs-linux source package in Mantic:
Fix Released
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
[ Impact ]
* Multiple data corruption issues have been identified and fixed in
ZFS. Some of them, at varying real-life reproducibility frequency have
been deterimed to affect very old zfs releases. Recommendation is to
upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
ensure users get other potentially related fixes and runtime tunables
to possibly mitigate other bugs that are related and are being fixed
upstream for future releases.
* For jammy the 2.1.14 upgrade will bring HWE kernel support and also
compatiblity/support for hardened kernel builds that mitigate SLS
(straight-line-speculation).
* In the absence of the upgrade a cherry-pick will address this
particular popular issue alone - without addressing other issues
w.r.t. Redbleed / SLS, bugfixes around trim support, and other related
improvements that were discovered and fixed around the same time as
this popular issue.
[ Test Plan ]
* !!! Danger !!! use reproducer from
https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
and confirm if that issue is resolved or not. Do not run on production
ZFS pools / systems.
* autopkgtest pass (from https://ubuntu-archive-
team.ubuntu.com/proposed-migration/ )
* adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )
* kernel regression zfs testsuite pass (from Kernel team RT test
results summary, private)
* zsys integration test pass (upgrade of zsys installed systems for
all releases)
* zsys install test pass (for daily images of LTS releases only that
have such installer support, as per iso tracker test case)
* LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
2.1.14, and test LXD on these updated kernels)
[ Where problems could occur ]
* Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will
introduce slight slow down on amd64 (for hw accelerated assembly code-
paths only in the encryption primitives)
* Uncertain of the perfomance impact of the extra checks in dnat
patch fix itself. Possibly affecting speed of operation, at the
benefit of correctness.
* The cherry-picked patch ("dnat"? dnode) changes the dirty data check, but
only makes it stronger and not weaker, thus if it were incorrect, likely
only performance would be impacted (and it is unlikely to be incorrect
given upstream reviews and attention to data corruption issues; also,
there are no additional changes to that function upstream)
[ Other Info ]
* https://github.com/openzfs/zfs/pull/15571 is most current
consideration of affairs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+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 2044657] Re: Multiple data corruption issues in zfs
Since I was just referenced, note that I wouldn't favor putting 2.2 into
Jammy. I would, however, prefer to see the latest 2.1.x.
2.2 is still seeing a substantial number of bug fixes. It will probably
be ok by the release date of 24.04, but I still wouldn't change major
versions for Jammy.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2044657
Title:
Multiple data corruption issues in zfs
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Xenial:
Confirmed
Status in zfs-linux source package in Bionic:
Confirmed
Status in zfs-linux source package in Focal:
Fix Committed
Status in zfs-linux source package in Jammy:
Fix Committed
Status in zfs-linux source package in Lunar:
Won't Fix
Status in zfs-linux source package in Mantic:
Fix Released
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
[ Impact ]
* Multiple data corruption issues have been identified and fixed in
ZFS. Some of them, at varying real-life reproducibility frequency have
been deterimed to affect very old zfs releases. Recommendation is to
upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
ensure users get other potentially related fixes and runtime tunables
to possibly mitigate other bugs that are related and are being fixed
upstream for future releases.
* For jammy the 2.1.14 upgrade will bring HWE kernel support and also
compatiblity/support for hardened kernel builds that mitigate SLS
(straight-line-speculation).
* In the absence of the upgrade a cherry-pick will address this
particular popular issue alone - without addressing other issues
w.r.t. Redbleed / SLS, bugfixes around trim support, and other related
improvements that were discovered and fixed around the same time as
this popular issue.
[ Test Plan ]
* !!! Danger !!! use reproducer from
https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
and confirm if that issue is resolved or not. Do not run on production
ZFS pools / systems.
* autopkgtest pass (from https://ubuntu-archive-
team.ubuntu.com/proposed-migration/ )
* adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )
* kernel regression zfs testsuite pass (from Kernel team RT test
results summary, private)
* zsys integration test pass (upgrade of zsys installed systems for
all releases)
* zsys install test pass (for daily images of LTS releases only that
have such installer support, as per iso tracker test case)
* LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
2.1.14, and test LXD on these updated kernels)
[ Where problems could occur ]
* Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will
introduce slight slow down on amd64 (for hw accelerated assembly code-
paths only in the encryption primitives)
* Uncertain of the perfomance impact of the extra checks in dnat
patch fix itself. Possibly affecting speed of operation, at the
benefit of correctness.
* The cherry-picked patch ("dnat"? dnode) changes the dirty data check, but
only makes it stronger and not weaker, thus if it were incorrect, likely
only performance would be impacted (and it is unlikely to be incorrect
given upstream reviews and attention to data corruption issues; also,
there are no additional changes to that function upstream)
[ Other Info ]
* https://github.com/openzfs/zfs/pull/15571 is most current
consideration of affairs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+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 2044657] Re: Multiple data corruption issues in zfs
it's likely to take a while. It's been committed but not released. They
chose to cherry pick the patch, so the version will still show as 2.1.5.
A lot of us would prefer going to 2.1.14, but there are enough other
changes that Ubuntu staff didn't want to do it. I'm considering building
my own zfs module.
We chose Ubuntu for our file servers primarily because their support for
ZFS. As I look more closely at the quality of that support I'm
questioning the decision.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2044657
Title:
Multiple data corruption issues in zfs
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Xenial:
Confirmed
Status in zfs-linux source package in Bionic:
Confirmed
Status in zfs-linux source package in Focal:
Fix Committed
Status in zfs-linux source package in Jammy:
Fix Committed
Status in zfs-linux source package in Lunar:
Won't Fix
Status in zfs-linux source package in Mantic:
Fix Released
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
[ Impact ]
* Multiple data corruption issues have been identified and fixed in
ZFS. Some of them, at varying real-life reproducibility frequency have
been deterimed to affect very old zfs releases. Recommendation is to
upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
ensure users get other potentially related fixes and runtime tunables
to possibly mitigate other bugs that are related and are being fixed
upstream for future releases.
* For jammy the 2.1.14 upgrade will bring HWE kernel support and also
compatiblity/support for hardened kernel builds that mitigate SLS
(straight-line-speculation).
* In the absence of the upgrade a cherry-pick will address this
particular popular issue alone - without addressing other issues
w.r.t. Redbleed / SLS, bugfixes around trim support, and other related
improvements that were discovered and fixed around the same time as
this popular issue.
[ Test Plan ]
* !!! Danger !!! use reproducer from
https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
and confirm if that issue is resolved or not. Do not run on production
ZFS pools / systems.
* autopkgtest pass (from https://ubuntu-archive-
team.ubuntu.com/proposed-migration/ )
* adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )
* kernel regression zfs testsuite pass (from Kernel team RT test
results summary, private)
* zsys integration test pass (upgrade of zsys installed systems for
all releases)
* zsys install test pass (for daily images of LTS releases only that
have such installer support, as per iso tracker test case)
* LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
2.1.14, and test LXD on these updated kernels)
[ Where problems could occur ]
* Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will
introduce slight slow down on amd64 (for hw accelerated assembly code-
paths only in the encryption primitives)
* Uncertain of the perfomance impact of the extra checks in dnat
patch fix itself. Possibly affecting speed of operation, at the
benefit of correctness.
* The cherry-picked patch ("dnat"? dnode) changes the dirty data check, but
only makes it stronger and not weaker, thus if it were incorrect, likely
only performance would be impacted (and it is unlikely to be incorrect
given upstream reviews and attention to data corruption issues; also,
there are no additional changes to that function upstream)
[ Other Info ]
* https://github.com/openzfs/zfs/pull/15571 is most current
consideration of affairs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+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 2044657] Re: Multiple data corruption issues in zfs
For what it's worth, we've been running a file server for several weeks
with the 2.1.14 .ko files in 22.04 with no problem. I didn't try to
cherry pick the one fix as I'd prefer to have the whole 2.1.14.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2044657
Title:
Multiple data corruption issues in zfs
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Xenial:
Confirmed
Status in zfs-linux source package in Bionic:
Confirmed
Status in zfs-linux source package in Focal:
In Progress
Status in zfs-linux source package in Jammy:
In Progress
Status in zfs-linux source package in Lunar:
Won't Fix
Status in zfs-linux source package in Mantic:
In Progress
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
[ Impact ]
* Multiple data corruption issues have been identified and fixed in
ZFS. Some of them, at varying real-life reproducibility frequency have
been deterimed to affect very old zfs releases. Recommendation is to
upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
ensure users get other potentially related fixes and runtime tunables
to possibly mitigate other bugs that are related and are being fixed
upstream for future releases.
* For jammy the 2.1.14 upgrade will bring HWE kernel support and also
compatiblity/support for hardened kernel builds that mitigate SLS
(straight-line-speculation).
* In the absence of the upgrade a cherry-pick will address this
particular popular issue alone - without addressing other issues
w.r.t. Redbleed / SLS, bugfixes around trim support, and other related
improvements that were discovered and fixed around the same time as
this popular issue.
[ Test Plan ]
* !!! Danger !!! use reproducer from
https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
and confirm if that issue is resolved or not. Do not run on production
ZFS pools / systems.
* autopkgtest pass (from https://ubuntu-archive-
team.ubuntu.com/proposed-migration/ )
* adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )
* kernel regression zfs testsuite pass (from Kernel team RT test
results summary, private)
* zsys integration test pass (upgrade of zsys installed systems for
all releases)
* zsys install test pass (for daily images of LTS releases only that
have such installer support, as per iso tracker test case)
* LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
2.1.14, and test LXD on these updated kernels)
[ Where problems could occur ]
* Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will
introduce slight slow down on amd64 (for hw accelerated assembly code-
paths only in the encryption primitives)
* Uncertain of the perfomance impact of the extra checks in dnat
patch fix itself. Possibly affecting speed of operation, at the
benefit of correctness.
* The cherry-picked patch ("dnat"? dnode) changes the dirty data check, but
only makes it stronger and not weaker, thus if it were incorrect, likely
only performance would be impacted (and it is unlikely to be incorrect
given upstream reviews and attention to data corruption issues; also,
there are no additional changes to that function upstream)
[ Other Info ]
* https://github.com/openzfs/zfs/pull/15571 is most current
consideration of affairs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+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 2050098] Re: cgroup2 broken since 5.15.0-90-generic?
Furthermore, slurm doesn't actually use the log data that the kernel would pass back. So my code is better even with kernels that work. Why pass a log buffer that you aren't going to use? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2050098 Title: cgroup2 broken since 5.15.0-90-generic? Status in linux-signed package in Ubuntu: Confirmed Bug description: We're using Slurm workload manager in a cluster with Ubuntu 22.04 and the linux-generic kernel (amd64). We use cgroups (cgroup2) for resource allocation with Slurm. With kernel version linux-image-5.15.0-91-generic 5.15.0-91.101 amd64 I'm seeing a new issue. This must have been introduced recently, I can confirm that with kernel 5.15.0-88-generic the issue does not exist. When I request a single GPU on a node with kernel 5.15.0-88-generic all is well: $ srun -G 1 -w gpu59 nvidia-smi -L GPU 0: NVIDIA [...] Instead with kernel 5.15.0-91-generic: $ srun -G 1 -w gpu59 nvidia-smi -L slurmstepd: error: load_ebpf_prog: BPF load error (No space left on device). Please check your system limits (MEMLOCK). GPU 0: NVIDIA [...] GPU 1: NVIDIA [...] GPU 2: NVIDIA [...] GPU 3: NVIDIA [...] GPU 4: NVIDIA [...] GPU 5: NVIDIA [...] GPU 6: NVIDIA [...] GPU 7: NVIDIA [...] So I get this error regarding MEMLOCK limit and see all GPUs in the system instead of only the one requested. Hence I assume the problem is related to cgroups. $ cat /proc/version_signature Ubuntu 5.15.0-91.101-generic 5.15.131 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2050098/+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 2050098] Re: cgroup2 broken since 5.15.0-90-generic?
However the same patch is in 6.5. I give up. At least I have a workaround. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2050098 Title: cgroup2 broken since 5.15.0-90-generic? Status in linux-signed package in Ubuntu: Confirmed Bug description: We're using Slurm workload manager in a cluster with Ubuntu 22.04 and the linux-generic kernel (amd64). We use cgroups (cgroup2) for resource allocation with Slurm. With kernel version linux-image-5.15.0-91-generic 5.15.0-91.101 amd64 I'm seeing a new issue. This must have been introduced recently, I can confirm that with kernel 5.15.0-88-generic the issue does not exist. When I request a single GPU on a node with kernel 5.15.0-88-generic all is well: $ srun -G 1 -w gpu59 nvidia-smi -L GPU 0: NVIDIA [...] Instead with kernel 5.15.0-91-generic: $ srun -G 1 -w gpu59 nvidia-smi -L slurmstepd: error: load_ebpf_prog: BPF load error (No space left on device). Please check your system limits (MEMLOCK). GPU 0: NVIDIA [...] GPU 1: NVIDIA [...] GPU 2: NVIDIA [...] GPU 3: NVIDIA [...] GPU 4: NVIDIA [...] GPU 5: NVIDIA [...] GPU 6: NVIDIA [...] GPU 7: NVIDIA [...] So I get this error regarding MEMLOCK limit and see all GPUs in the system instead of only the one requested. Hence I assume the problem is related to cgroups. $ cat /proc/version_signature Ubuntu 5.15.0-91.101-generic 5.15.131 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2050098/+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 2050098] Re: cgroup2 broken since 5.15.0-90-generic?
>From timing I suspect kernel.org 2dcb31e65d26a29a6842500e904907180e80a091, but I don't understand the code so I can't tell whether there's actually a problem there. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2050098 Title: cgroup2 broken since 5.15.0-90-generic? Status in linux-signed package in Ubuntu: Confirmed Bug description: We're using Slurm workload manager in a cluster with Ubuntu 22.04 and the linux-generic kernel (amd64). We use cgroups (cgroup2) for resource allocation with Slurm. With kernel version linux-image-5.15.0-91-generic 5.15.0-91.101 amd64 I'm seeing a new issue. This must have been introduced recently, I can confirm that with kernel 5.15.0-88-generic the issue does not exist. When I request a single GPU on a node with kernel 5.15.0-88-generic all is well: $ srun -G 1 -w gpu59 nvidia-smi -L GPU 0: NVIDIA [...] Instead with kernel 5.15.0-91-generic: $ srun -G 1 -w gpu59 nvidia-smi -L slurmstepd: error: load_ebpf_prog: BPF load error (No space left on device). Please check your system limits (MEMLOCK). GPU 0: NVIDIA [...] GPU 1: NVIDIA [...] GPU 2: NVIDIA [...] GPU 3: NVIDIA [...] GPU 4: NVIDIA [...] GPU 5: NVIDIA [...] GPU 6: NVIDIA [...] GPU 7: NVIDIA [...] So I get this error regarding MEMLOCK limit and see all GPUs in the system instead of only the one requested. Hence I assume the problem is related to cgroups. $ cat /proc/version_signature Ubuntu 5.15.0-91.101-generic 5.15.131 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2050098/+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 2050098] Re: cgroup2 broken since 5.15.0-90-generic?
In src/plugins/cgroup/v2/ebpf.c, comment out logging. I.e. change attr.log_level = 1; attr.log_buf = (size_t) log; attr.log_size = sizeof(log); to attr.log_level = 0; attr.log_buf = NULL; attr.log_size = 0; I think you'll find that this fixes it. I have no idea why this is a problem in this specific kernel release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2050098 Title: cgroup2 broken since 5.15.0-90-generic? Status in linux-signed package in Ubuntu: Confirmed Bug description: We're using Slurm workload manager in a cluster with Ubuntu 22.04 and the linux-generic kernel (amd64). We use cgroups (cgroup2) for resource allocation with Slurm. With kernel version linux-image-5.15.0-91-generic 5.15.0-91.101 amd64 I'm seeing a new issue. This must have been introduced recently, I can confirm that with kernel 5.15.0-88-generic the issue does not exist. When I request a single GPU on a node with kernel 5.15.0-88-generic all is well: $ srun -G 1 -w gpu59 nvidia-smi -L GPU 0: NVIDIA [...] Instead with kernel 5.15.0-91-generic: $ srun -G 1 -w gpu59 nvidia-smi -L slurmstepd: error: load_ebpf_prog: BPF load error (No space left on device). Please check your system limits (MEMLOCK). GPU 0: NVIDIA [...] GPU 1: NVIDIA [...] GPU 2: NVIDIA [...] GPU 3: NVIDIA [...] GPU 4: NVIDIA [...] GPU 5: NVIDIA [...] GPU 6: NVIDIA [...] GPU 7: NVIDIA [...] So I get this error regarding MEMLOCK limit and see all GPUs in the system instead of only the one requested. Hence I assume the problem is related to cgroups. $ cat /proc/version_signature Ubuntu 5.15.0-91.101-generic 5.15.131 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2050098/+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 2050098] Re: cgroup2 broken since 5.15.0-90-generic?
I'm concerned with the security implications of being frozen on a kernel we can't update. I suspect we should start testing an HWE kernel. That raises other issues, since there are lots of other features we also need to work, so it's going to require a fair amount of testing. I'd accelerate our move to 24.04, except there is too much question about update of user packages, which often lag new system versions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2050098 Title: cgroup2 broken since 5.15.0-90-generic? Status in linux-signed package in Ubuntu: Confirmed Bug description: We're using Slurm workload manager in a cluster with Ubuntu 22.04 and the linux-generic kernel (amd64). We use cgroups (cgroup2) for resource allocation with Slurm. With kernel version linux-image-5.15.0-91-generic 5.15.0-91.101 amd64 I'm seeing a new issue. This must have been introduced recently, I can confirm that with kernel 5.15.0-88-generic the issue does not exist. When I request a single GPU on a node with kernel 5.15.0-88-generic all is well: $ srun -G 1 -w gpu59 nvidia-smi -L GPU 0: NVIDIA [...] Instead with kernel 5.15.0-91-generic: $ srun -G 1 -w gpu59 nvidia-smi -L slurmstepd: error: load_ebpf_prog: BPF load error (No space left on device). Please check your system limits (MEMLOCK). GPU 0: NVIDIA [...] GPU 1: NVIDIA [...] GPU 2: NVIDIA [...] GPU 3: NVIDIA [...] GPU 4: NVIDIA [...] GPU 5: NVIDIA [...] GPU 6: NVIDIA [...] GPU 7: NVIDIA [...] So I get this error regarding MEMLOCK limit and see all GPUs in the system instead of only the one requested. Hence I assume the problem is related to cgroups. $ cat /proc/version_signature Ubuntu 5.15.0-91.101-generic 5.15.131 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2050098/+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 2050098] Re: cgroup2 broken since 5.15.0-90-generic?
We are also seeing this. We're now stuck on old kernels until this is fixed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2050098 Title: cgroup2 broken since 5.15.0-90-generic? Status in linux-signed package in Ubuntu: Confirmed Bug description: We're using Slurm workload manager in a cluster with Ubuntu 22.04 and the linux-generic kernel (amd64). We use cgroups (cgroup2) for resource allocation with Slurm. With kernel version linux-image-5.15.0-91-generic 5.15.0-91.101 amd64 I'm seeing a new issue. This must have been introduced recently, I can confirm that with kernel 5.15.0-88-generic the issue does not exist. When I request a single GPU on a node with kernel 5.15.0-88-generic all is well: $ srun -G 1 -w gpu59 nvidia-smi -L GPU 0: NVIDIA [...] Instead with kernel 5.15.0-91-generic: $ srun -G 1 -w gpu59 nvidia-smi -L slurmstepd: error: load_ebpf_prog: BPF load error (No space left on device). Please check your system limits (MEMLOCK). GPU 0: NVIDIA [...] GPU 1: NVIDIA [...] GPU 2: NVIDIA [...] GPU 3: NVIDIA [...] GPU 4: NVIDIA [...] GPU 5: NVIDIA [...] GPU 6: NVIDIA [...] GPU 7: NVIDIA [...] So I get this error regarding MEMLOCK limit and see all GPUs in the system instead of only the one requested. Hence I assume the problem is related to cgroups. $ cat /proc/version_signature Ubuntu 5.15.0-91.101-generic 5.15.131 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2050098/+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 2049285] Re: thermald cannot start
Maybe not accurate ** Attachment added: "Capture d’écran du 2024-01-14 01-13-39.png" https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2049285/+attachment/5739103/+files/Capture%20d%E2%80%99%C3%A9cran%20du%202024-01-14%2001-13-39.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2049285 Title: thermald cannot start Status in thermald package in Ubuntu: New Bug description: After a moment my system slow down, don't want to burn cpu or gpu :-( Thanks jc@jc-Portable:~$ sudo thermald --no-daemon --loglevel=debug [1705190368][DEBUG]RAPL sysfs present [1705190368][DEBUG]RAPL base path /sys/class/powercap/intel-rapl/ [1705190368][DEBUG]RAPL domain dir uevent [1705190368][DEBUG] /sys/class/powercap/intel-rapl/uevent/name doesn't exist [1705190368][DEBUG]RAPL domain dir enabled [1705190368][DEBUG] /sys/class/powercap/intel-rapl/enabled/name doesn't exist [1705190368][DEBUG]RAPL domain dir power [1705190368][DEBUG] /sys/class/powercap/intel-rapl/power/name doesn't exist [1705190368][DEBUG]RAPL domain dir intel-rapl:0 [1705190368][DEBUG]name package-0 [1705190368][DEBUG]RAPL base path /sys/class/powercap/intel-rapl/intel-rapl:0/ [1705190368][DEBUG]RAPL domain dir uevent [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/uevent/name doesn't exist [1705190368][DEBUG]RAPL domain dir energy_uj [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/energy_uj/name doesn't exist [1705190368][DEBUG]RAPL domain dir intel-rapl:0:2 [1705190368][DEBUG]name dram [1705190368][DEBUG]RAPL domain dir intel-rapl:0:0 [1705190368][DEBUG]name core [1705190368][DEBUG]RAPL domain dir enabled [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/enabled/name doesn't exist [1705190368][DEBUG]RAPL domain dir constraint_1_max_power_uw [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/constraint_1_max_power_uw/name doesn't exist [1705190368][DEBUG]RAPL domain dir power [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/power/name doesn't exist [1705190368][DEBUG]RAPL domain dir device [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/device/name doesn't exist [1705190368][DEBUG]RAPL domain dir constraint_1_time_window_us [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/constraint_1_time_window_us/name doesn't exist [1705190368][DEBUG]RAPL domain dir constraint_1_power_limit_uw [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/constraint_1_power_limit_uw/name doesn't exist [1705190368][DEBUG]RAPL domain dir intel-rapl:0:1 [1705190368][DEBUG]name uncore [1705190368][DEBUG]RAPL domain dir constraint_0_time_window_us [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/constraint_0_time_window_us/name doesn't exist [1705190368][DEBUG]RAPL domain dir subsystem [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/subsystem/name doesn't exist [1705190368][DEBUG]RAPL domain dir constraint_1_name [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/constraint_1_name/name doesn't exist [1705190368][DEBUG]RAPL domain dir constraint_0_power_limit_uw [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/constraint_0_power_limit_uw/name doesn't exist [1705190368][DEBUG]RAPL domain dir constraint_0_name [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/constraint_0_name/name doesn't exist [1705190368][DEBUG]RAPL domain dir name [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/name/name doesn't exist [1705190368][DEBUG]RAPL domain dir constraint_0_max_power_uw [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/constraint_0_max_power_uw/name doesn't exist [1705190368][DEBUG]RAPL domain dir max_energy_range_uj [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/max_energy_range_uj/name doesn't exist [1705190368][INFO]RAPL domain count 1 [1705190368][DEBUG]RAPL domain dir subsystem [1705190368][DEBUG] /sys/class/powercap/intel-rapl/subsystem/name doesn't exist [1705190368][INFO]RAPL domain count 1 [1705190368][MSG]22 CPUID levels; family:model:stepping 0x6:9e:9 (6:158:9) [1705190368][DEBUG]thd_read_default_thermal_sensors [1705190368][INFO]sensor_update: type pch_skylake [1705190368][INFO]sensor_update: type acpitz [1705190368][INFO]sensor_update: type iwlwifi_1 [1705190368][INFO]sensor_update: type B0D4 [1705190368][INFO]sensor_update: type INT3400 [1705190368][INFO]sensor_update: type x86_pkg_temp [1705190368][INFO]thd_read_default_thermal_sensors loaded 6 sensors [1705190368][INFO]dts /sys/devices/platform/coretemp.0/name doesn't exist [1705190368][MSG]sensor id 11 : No temp sysfs for reading raw temp [1705190368][MSG]sensor id 11 : No temp sysfs for reading raw temp [
[Kernel-packages] [Bug 2049285] Re: thermald cannot start
Maybe this could be useful too, thanks a lot, by the way I did try to reintall and purge the service, same problem: jan 14 00:35:27 jc-Portable systemd[1]: Starting thermald.service - Thermal Daemon Service... jan 14 00:35:27 jc-Portable systemd[1]: Started thermald.service - Thermal Daemon Service. jan 14 00:35:27 jc-Portable thermald[1089]: 22 CPUID levels; family:model:stepping 0x6:9e:9 (6:158:9) jan 14 00:35:27 jc-Portable thermald[1089]: 22 CPUID levels; family:model:stepping 0x6:9e:9 (6:158:9) jan 14 00:35:27 jc-Portable thermald[1089]: sensor id 11 : No temp sysfs for reading raw temp jan 14 00:35:27 jc-Portable thermald[1089]: sensor id 11 : No temp sysfs for reading raw temp jan 14 00:35:27 jc-Portable thermald[1089]: sensor id 11 : No temp sysfs for reading raw temp jan 14 00:35:27 jc-Portable thermald[1089]: *** stack smashing detected ***: terminated jan 14 00:35:27 jc-Portable systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT jan 14 00:35:27 jc-Portable systemd[1]: thermald.service: Failed with result 'signal'. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2049285 Title: thermald cannot start Status in thermald package in Ubuntu: New Bug description: After a moment my system slow down, don't want to burn cpu or gpu :-( Thanks jc@jc-Portable:~$ sudo thermald --no-daemon --loglevel=debug [1705190368][DEBUG]RAPL sysfs present [1705190368][DEBUG]RAPL base path /sys/class/powercap/intel-rapl/ [1705190368][DEBUG]RAPL domain dir uevent [1705190368][DEBUG] /sys/class/powercap/intel-rapl/uevent/name doesn't exist [1705190368][DEBUG]RAPL domain dir enabled [1705190368][DEBUG] /sys/class/powercap/intel-rapl/enabled/name doesn't exist [1705190368][DEBUG]RAPL domain dir power [1705190368][DEBUG] /sys/class/powercap/intel-rapl/power/name doesn't exist [1705190368][DEBUG]RAPL domain dir intel-rapl:0 [1705190368][DEBUG]name package-0 [1705190368][DEBUG]RAPL base path /sys/class/powercap/intel-rapl/intel-rapl:0/ [1705190368][DEBUG]RAPL domain dir uevent [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/uevent/name doesn't exist [1705190368][DEBUG]RAPL domain dir energy_uj [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/energy_uj/name doesn't exist [1705190368][DEBUG]RAPL domain dir intel-rapl:0:2 [1705190368][DEBUG]name dram [1705190368][DEBUG]RAPL domain dir intel-rapl:0:0 [1705190368][DEBUG]name core [1705190368][DEBUG]RAPL domain dir enabled [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/enabled/name doesn't exist [1705190368][DEBUG]RAPL domain dir constraint_1_max_power_uw [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/constraint_1_max_power_uw/name doesn't exist [1705190368][DEBUG]RAPL domain dir power [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/power/name doesn't exist [1705190368][DEBUG]RAPL domain dir device [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/device/name doesn't exist [1705190368][DEBUG]RAPL domain dir constraint_1_time_window_us [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/constraint_1_time_window_us/name doesn't exist [1705190368][DEBUG]RAPL domain dir constraint_1_power_limit_uw [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/constraint_1_power_limit_uw/name doesn't exist [1705190368][DEBUG]RAPL domain dir intel-rapl:0:1 [1705190368][DEBUG]name uncore [1705190368][DEBUG]RAPL domain dir constraint_0_time_window_us [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/constraint_0_time_window_us/name doesn't exist [1705190368][DEBUG]RAPL domain dir subsystem [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/subsystem/name doesn't exist [1705190368][DEBUG]RAPL domain dir constraint_1_name [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/constraint_1_name/name doesn't exist [1705190368][DEBUG]RAPL domain dir constraint_0_power_limit_uw [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/constraint_0_power_limit_uw/name doesn't exist [1705190368][DEBUG]RAPL domain dir constraint_0_name [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/constraint_0_name/name doesn't exist [1705190368][DEBUG]RAPL domain dir name [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/name/name doesn't exist [1705190368][DEBUG]RAPL domain dir constraint_0_max_power_uw [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/constraint_0_max_power_uw/name doesn't exist [1705190368][DEBUG]RAPL domain dir max_energy_range_uj [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/max_energy_range_uj/name doesn't exist [1705190368][INFO]RAPL domain count 1 [1705190368][DEBUG]RAPL domain dir subsystem [1
[Kernel-packages] [Bug 2049285] [NEW] thermald cannot start
Public bug reported: After a moment my system slow down, don't want to burn cpu or gpu :-( Thanks jc@jc-Portable:~$ sudo thermald --no-daemon --loglevel=debug [1705190368][DEBUG]RAPL sysfs present [1705190368][DEBUG]RAPL base path /sys/class/powercap/intel-rapl/ [1705190368][DEBUG]RAPL domain dir uevent [1705190368][DEBUG] /sys/class/powercap/intel-rapl/uevent/name doesn't exist [1705190368][DEBUG]RAPL domain dir enabled [1705190368][DEBUG] /sys/class/powercap/intel-rapl/enabled/name doesn't exist [1705190368][DEBUG]RAPL domain dir power [1705190368][DEBUG] /sys/class/powercap/intel-rapl/power/name doesn't exist [1705190368][DEBUG]RAPL domain dir intel-rapl:0 [1705190368][DEBUG]name package-0 [1705190368][DEBUG]RAPL base path /sys/class/powercap/intel-rapl/intel-rapl:0/ [1705190368][DEBUG]RAPL domain dir uevent [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/uevent/name doesn't exist [1705190368][DEBUG]RAPL domain dir energy_uj [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/energy_uj/name doesn't exist [1705190368][DEBUG]RAPL domain dir intel-rapl:0:2 [1705190368][DEBUG]name dram [1705190368][DEBUG]RAPL domain dir intel-rapl:0:0 [1705190368][DEBUG]name core [1705190368][DEBUG]RAPL domain dir enabled [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/enabled/name doesn't exist [1705190368][DEBUG]RAPL domain dir constraint_1_max_power_uw [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/constraint_1_max_power_uw/name doesn't exist [1705190368][DEBUG]RAPL domain dir power [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/power/name doesn't exist [1705190368][DEBUG]RAPL domain dir device [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/device/name doesn't exist [1705190368][DEBUG]RAPL domain dir constraint_1_time_window_us [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/constraint_1_time_window_us/name doesn't exist [1705190368][DEBUG]RAPL domain dir constraint_1_power_limit_uw [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/constraint_1_power_limit_uw/name doesn't exist [1705190368][DEBUG]RAPL domain dir intel-rapl:0:1 [1705190368][DEBUG]name uncore [1705190368][DEBUG]RAPL domain dir constraint_0_time_window_us [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/constraint_0_time_window_us/name doesn't exist [1705190368][DEBUG]RAPL domain dir subsystem [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/subsystem/name doesn't exist [1705190368][DEBUG]RAPL domain dir constraint_1_name [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/constraint_1_name/name doesn't exist [1705190368][DEBUG]RAPL domain dir constraint_0_power_limit_uw [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/constraint_0_power_limit_uw/name doesn't exist [1705190368][DEBUG]RAPL domain dir constraint_0_name [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/constraint_0_name/name doesn't exist [1705190368][DEBUG]RAPL domain dir name [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/name/name doesn't exist [1705190368][DEBUG]RAPL domain dir constraint_0_max_power_uw [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/constraint_0_max_power_uw/name doesn't exist [1705190368][DEBUG]RAPL domain dir max_energy_range_uj [1705190368][DEBUG] /sys/class/powercap/intel-rapl/intel-rapl:0/max_energy_range_uj/name doesn't exist [1705190368][INFO]RAPL domain count 1 [1705190368][DEBUG]RAPL domain dir subsystem [1705190368][DEBUG] /sys/class/powercap/intel-rapl/subsystem/name doesn't exist [1705190368][INFO]RAPL domain count 1 [1705190368][MSG]22 CPUID levels; family:model:stepping 0x6:9e:9 (6:158:9) [1705190368][DEBUG]thd_read_default_thermal_sensors [1705190368][INFO]sensor_update: type pch_skylake [1705190368][INFO]sensor_update: type acpitz [1705190368][INFO]sensor_update: type iwlwifi_1 [1705190368][INFO]sensor_update: type B0D4 [1705190368][INFO]sensor_update: type INT3400 [1705190368][INFO]sensor_update: type x86_pkg_temp [1705190368][INFO]thd_read_default_thermal_sensors loaded 6 sensors [1705190368][INFO]dts /sys/devices/platform/coretemp.0/name doesn't exist [1705190368][MSG]sensor id 11 : No temp sysfs for reading raw temp [1705190368][MSG]sensor id 11 : No temp sysfs for reading raw temp [1705190368][MSG]sensor id 11 : No temp sysfs for reading raw temp [1705190368][INFO]INT3400 Base path is /sys/bus/acpi/devices/INT3400:00/physical_node/uuids/ [1705190368][INFO] failed to GET COUNT on /dev/acpi_thermal_rel [1705190368][DEBUG]TRT count 1 ... [1705190368][DEBUG]TRT 0: SRC B0D4: [1705190368][DEBUG]TRT 0: TGT B0D4: [1705190368][DEBUG]TRT 0: INF 10: [1705190368][DEBUG]TRT 0: SMPL 50: [1705190368][DEBUG]uuid: 97C68AE7-15FA-499c-B8C9-5DA81D606E0A [1705190368][DEBUG]uuid: 9E04115A-AE87-4D1C-9500-0F3E340BFE75 [1705190368][INFO]Passive 1 UUID is not present, hence ignore _TRT, as it may have junk
[Kernel-packages] [Bug 2003053] Re: NFS: client permission error after adding user to permissible group
** Bug watch added: Linux Kernel Bug Tracker #217165 https://bugzilla.kernel.org/show_bug.cgi?id=217165 -- 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/2003053 Title: NFS: client permission error after adding user to permissible group Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Committed Bug description: [Impact] The NFS client's access cache becomes stale due to the user's group membership changing on the server after the user has already logged in on the client. The access cache only expires if either NFS_INO_INVALID_ACCESS flag is on or timeout (without delegation). Adding a user to a group in the NFS server will not cause any file attributes to change. The client will encounter permission errors until other file attributes are changed or the memory cache is dropped. [Fix] The access cache shall be cleared once the user logs out and logs back in again. 0eb43812c0270ee3d005ff32f91f7d0a6c4943af NFS: Clear the file access cache upon login 029085b8949f5d269ae2bbd14915407dd0c7f902 NFS: Judge the file access cache's timestamp in rcu path 5e9a7b9c2ea18551759833146a181b14835bfe39 NFS: Fix up a sparse warning [Test Plan] 1.[client side] testuser is not part of testgroup testuser@kinetic:~$ ls -ld /mnt/private/ drwxrwx--- 2 root testgroup 4096 Nov 24 08:23 /mnt/private/ testuser@kinetic:~$ mktemp -p /mnt/private/ mktemp: failed to create file via template ‘/mnt/private/tmp.XX’: Permission denied 2.[server side] add testuser into testgroup, which has access to folder root@kinetic:~$ usermod -aG testgroup testuser && echo `date +'%s'` > /proc/net/rpc/auth.unix.gid/flush 3.[client side] create a file again but still fail testuser@kinetic:~$ mktemp -p /mnt/private/ mktemp: failed to create file via template ‘/mnt/private/tmp.XX’: Permission denied [Where problems could occur] The fix will apply upstream commits, so the regression can be considered as low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003053/+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 2003588] Re: CVE 2022-4378 fix is in Kinetic, needed on Lunar
Because it is not production ready, We use the livecd uninstalled. Please make an exception for the kernel packages, Please just put the kinetic kernels on the lunar livecds, (And for all new) So we dont have to roll our own livecd just to smoke test a new version, So we dont get the avalanche of failures like our recent move to jammy. Without the kernel package I have not found it practical to try lunar (and all new) online at all. -- 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/2003588 Title: CVE 2022-4378 fix is in Kinetic, needed on Lunar Status in linux package in Ubuntu: Won't Fix Bug description: This and many other CVE's are still unfixed on Lunar. No sign of a tracking bug on Lunar Is there a reason the Kinetic kernel can't be pushed to lunar? Priority is high: https://ubuntu.com/security/CVE-2022-4378 Can the lunar livecd automatically get all linux package updates when they hit kinetic? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003588/+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 187761] Re: Need a way to disable selected modules with a kernel flag
uas.ko hangs, fails, spams dmesg on all 5 HP AMD A10 systems tested, on all AMD USB3 ports if writing to any device that has UAS. If booting a livecd on a UAS capable device, UAS cannot be unloaded. UAS will stall any writes to the temp log partition ubuntu creates on the boot device. -- 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/187761 Title: Need a way to disable selected modules with a kernel flag Status in linux package in Ubuntu: In Progress Bug description: Binary package hint: linux-image Bug #90271 and bug #187671 describe situations where Live CDs and install CDs fail to work because a broken kernel module causes a hang before user has a say. The error may be in an optional kernel module (such as sound card driver or memory card reader) but the end user has no way to prevent kernel from loading a possibly known broken module. Vanilla kernels from kernel.org support flag disablemodules (e.g. disablemodules=8139too,sdhci prevents linux kernel from loading 8139too.ko or sdhci.ko) but such flag does not seem to work with Ubuntu. This is a feature request to enable such a flag. It is not needed for normal use but in case of rare hardware exposing a bug in a kernel module not having such a flag prevents one from booting Ubuntu. (I'd prefer booting without network adapter or memory card reader to not booting at all). This issue also causes slowdowns such as bug #187671 which cannot proceed until bug #90271 is fixed because testing possible fixes for the bug is really hard until the other kernel module has been fixed. (This is because both bugs affect the same laptop hardware and both kernel modules cause a kernel hang.) I'd consider disablemodules flag similar to acpi flag - it should not be needed but still we need it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/187761/+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 1993318] Re: ZFS + Encryption installations of Ubuntu Desktop suffer various severe problems related to the package manager
Note that there are serious bugs with ZFS encryption. Most involve send | receive, but not all. I strongly recommend against using it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1993318 Title: ZFS + Encryption installations of Ubuntu Desktop suffer various severe problems related to the package manager Status in ubiquity package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in zsys package in Ubuntu: Incomplete Bug description: This is *probably* the wrong package, but it's the best I can figure for this, so here goes. Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core i5, UEFI, no secure boot. Testing done in GNOME Boxes, BIOS, 4 GB RAM, 50 GB disk space . OS is Ubuntu Desktop, Kinetic Final ISO. Steps to reproduce: 1. Boot the Ubuntu desktop ISO. 2. Select "Install Ubuntu" and proceed with the installation process. 3. When you get to the "Installation type" screen, select "Advanced Options", and enable ZFS + Encryption. 4. Proceed with the rest of the installation as normal. 5. Reboot into the newly installed system. 6. Log in. 7. Run "sudo apt update" in a terminal. Expected result: The package database should be updated normally. Actual result: You are presented with the following errors at the end of the apt output: Reading package lists... Error! E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or directory) E: Could not open file - open (2: No such file or directory) E: Problem opening E: The package lists or status file could not be parsed or opened. Notes: Switching to a TTY will print a crash error message related to the same missing /var/lib/dpkg/status file. Running "sudo touch /var/lib/dpkg/status" will allow "sudo apt update" to function and fix the crashed process in the TTY. Once you log in, you'll notice that Firefox is missing (bug #1993279), and you will likely be presented with a ton of error messages and other scary junk. At least one of those error messages was related to update-manager in my experience, and another one was from "check-new- release-gtk". ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: zsys (not installed) ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 18 09:55:27 2022 InstallationDate: Installed on 2022-10-18 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1993318/+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 1986436] [NEW] restarting nfs-server seems to create memory corruption
Public bug reported: I just upgraded an NFS server from 20.04 to 22.04. Because of problems in my setup, it didn't come up cleanly. As part of recovery I did "systemctl restart nfs-server." I did this after two reboots. In both cases shortly thereafter I got one or more backtraces in syslog Aug 11 09:49:25 eternal.lcsr.rutgers.edu kernel: [ 286.197557] refcount_t: addition on 0; use-after-free. ... Aug 11 09:49:25 eternal.lcsr.rutgers.edu kernel: [ 286.197695] get_nfsdfs_client+0x65/0x80 [nfsd] I'm not giving the whole thing because it should show in the data sent by apport. Also, starting after the first one, I started seeing things like Aug 11 09:49:26 eternal.lcsr.rutgers.edu rpc.mountd[19922]: v4.0 client detached: (null) from (null) Aug 11 09:49:26 eternal.lcsr.rutgers.edu rpc.mountd[19922]: message repeated 1831 times: [ v4.0 client detached: (null) f\ rom (null)] About 30 min after the first attempted restart, the kernel crashed. I have no further information, because it hung in the startup process when trying to get a dump. That means I don't absolutely know that the crash was due to the restart nfs-server. However our NFS servers have been quite stable otherwise, under both 20.04 and 22.04, so it seems a good bet the crash is connected. At least the use-after-free seems reproducible, since I saw it both times I tried the same thing after rebooting. Ubuntu 5.15.0-46.49-generic 5.15.39 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 11 10:46 seq crw-rw 1 root audio 116, 33 Aug 11 10:46 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 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: CasperMD5CheckResult: pass Date: Sat Aug 13 15:04:23 2022 InstallationDate: Installed on 2020-11-12 (639 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=0075734a-4440-4327-82e0-b0c303f1a1d7 ro crashkernel=512M-:192M RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-08-11 (2 days ago) dmi.bios.date: 11/02/2019 dmi.bios.release: 2.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.11.0 dmi.board.name: 0599V5 dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.11.0:bd11/02/2019:br2.11:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn0599V5:rvrA06:cvnDellInc.:ct23:cvr:skuSKU=NotProvided;ModelName=PowerEdgeR730: dmi.product.name: PowerEdge R730 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R730 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-11-12T12:56:54.987058 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy uec-images -- 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/1986436 Title: restarting nfs-server seems to create memory corruption Status in linux package in Ubuntu: New Bug description: I just upgraded an NFS server from 20.04 to 22.04. Because of problems in my setup, it didn't come up cleanly. As part of recovery I did "systemctl restart nfs-server." I did this after two reboots. In both cases shortly thereafter I got one or more backtraces in syslog Aug 11 09:49:25 eternal.lcsr.rutgers.edu kernel: [ 286.197557] refcount_t: addition on 0; use-after-free. ... Aug 11 09:49:25 eternal.lcsr.rutgers.edu kernel: [ 286.197695] get_nfsdfs_client+0x65/0x80 [nfsd] I'm not giving the whole thing because it should show in the data sent by apport. Also, starting after the first one, I started seeing things like Aug 11 09:49:26 eternal.lcsr.rutgers.edu rpc.mountd[19922]: v4.0 client detached: (null) from (null) Aug 11 09:49:26 eternal.lcsr.rutgers.edu rpc.mountd[19922]: message repeated 1831 times: [ v4.0 client detached: (null) f\ rom (null)] About 30 min after the first attempted restart, the kernel crashed
[Kernel-packages] [Bug 1948626] Re: Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010
Jeff, The patches are queued up to be submitted to 5.18 https://git.infradead.org/git/nvme.git/log/refs/tags/nvme-5.18-2022-03-03 -- 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/1948626 Title: Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010 Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: NVMe-oF suffers from a well-known discovery problem that fundamentally limits the size of realistic deployments. To address this discovery problem, the FMDS working group (within nvme.org) is working on two proposals that will allow NVMe-oF to be managed via a “network centric” provisioning process instead of an “end-node centric” one. TP-8009 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625): will enable the Automated Discovery of NVMe-oF Discovery Controllers in an IP Network and will prevent an end-user from needing to manually configure the IP Address of Discovery Controllers. TP-8010 (this launchpad): will define the concept of a Centralized Discovery Controller (CDC) and will allow end-users to manage connectivity from a single point of management on an IP Fabric by IP Fabric basis. Here is code that implements TP8009 and TP8010: https://github.com/martin-belanger/nvme-stas/ which now got pulled into upstream - https://github.com/linux-nvme/nvme-stas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948626/+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
Re: [Kernel-packages] [Bug 1609750]
solved the bug already i cleared some things and made an update On Sun, Sep 26, 2021, 05:40 ian <1609...@bugs.launchpad.net> wrote: > Any update on this? Having issues with sound working for some time, > than suddenly stopping with a buzzing sound. Will attempt to modify > patch for most recent kernel, but my understanding is the kernel should > already be patched. Works fine on galliumos, but not with any other > distro or most recent kernel > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1803810). > https://bugs.launchpad.net/bugs/1609750 > > Title: > Audio not working on Acer Chromebook R11 > > Status in linux: > Confirmed > Status in linux package in Ubuntu: > In Progress > Status in pulseaudio package in Ubuntu: > Invalid > > Bug description: > Audio is not working at all on Acer Chromebook R11 (codename CYAN). > It's a Intel Braswell platform. snd_hda_intel messages seem normal, > but Pulseaudio does not detect sound hardware. > > ProblemType: Bug > DistroRelease: Ubuntu 16.10 > Package: pulseaudio 1:9.0-1.1ubuntu1 > ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 > Uname: Linux 4.4.0-33-generic x86_64 > ApportVersion: 2.20.3-0ubuntu2 > Architecture: amd64 > AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', > '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', > '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', > '/dev/snd/timer'] failed with exit code 1: > CurrentDesktop: Unity > Date: Thu Aug 4 14:12:03 2016 > InstallationDate: Installed on 2016-07-22 (13 days ago) > InstallationMedia: > > PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No > PulseAudio daemon running, or not running as session daemon. > SourcePackage: pulseaudio > Symptom: audio > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 05/20/2016 > dmi.bios.vendor: coreboot > dmi.chassis.type: 3 > dmi.chassis.vendor: GOOGLE > dmi.modalias: > dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: > dmi.product.name: Cyan > dmi.product.version: 1.0 > dmi.sys.vendor: GOOGLE > --- > ApportVersion: 2.20.3-0ubuntu2 > Architecture: amd64 > AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', > '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', > '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', > '/dev/snd/timer'] failed with exit code 1: > CurrentDesktop: Unity > DistroRelease: Ubuntu 16.10 > HibernationDevice: RESUME=UUID=53fe7902-c347-4ff8-945d-a3e3de773a08 > InstallationDate: Installed on 2016-07-22 (13 days ago) > InstallationMedia: > > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 003: ID 8087:0a2a Intel Corp. >Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: GOOGLE Cyan > Package: linux-image-4.4.0-33-generic 4.4.0-33.52 > PackageArchitecture: amd64 > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic > root=UUID=742e4082-264a-4459-93df-9ec07b41d5e8 ro quiet splash vt.handoff=7 > ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 > PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No > PulseAudio daemon running, or not running as session daemon. > RelatedPackageVersions: >linux-restricted-modules-4.4.0-33-generic N/A >linux-backports-modules-4.4.0-33-generic N/A >linux-firmware1.159 > Tags: yakkety > Uname: Linux 4.4.0-33-generic x86_64 > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > _MarkForUpload: True > dmi.bios.date: 05/20/2016 > dmi.bios.vendor: coreboot > dmi.chassis.type: 3 > dmi.chassis.vendor: GOOGLE > dmi.modalias: > dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: > dmi.product.name: Cyan > dmi.product.version: 1.0 > dmi.sys.vendor: GOOGLE > > To manage notifications about this bug go to: > https://bugs.launchpad.net/kernel/+bug/1609750/+subscriptions > > -- 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/1609750 Title: Audio not working on Acer Chromebook R11 Status in linux: Confirmed Status in linux package in Ubuntu: In Progress Status in pulseaudio package in Ubuntu: Invalid Bug description: Audio is not working at all on Acer Chromebook R11 (codename CYAN). It's a Intel Braswell platform. snd_hda_intel messages seem normal, but Pulseaudio does not detect sound hardware. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: pulseaudio 1:9.0-1.1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 Uname: Li
[Kernel-packages] [Bug 1939177] Re: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken
I've also seen this. I wondered if the problem is that the libraries and utilities haven't been updated. I doubt that it's intended for a version 0.8.3 ZFS send and receive to run on a ZFS 2.0.2. kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1939177 Title: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken Status in zfs-linux package in Ubuntu: Confirmed Bug description: https://github.com/openzfs/zfs/issues/12462 Ubuntu 20.04.2 LTS Kernel: 5.11.0-25-generic #27~20.04.1-Ubuntu zfs-0.8.3-1ubuntu12.12 zfs-kmod-2.0.2-1ubuntu5 Trying to run zfs send | receive and getting an error: # zfs send 'rpool/home'@'autosnap_2020-08-01_00:59:01_monthly' | zfs receive -s -F 'nas/rpool_backup/home' cannot receive: failed to read from stream cannot receive new filesystem stream: dataset does not exist This used to work before the recent Ubuntu kernel update from 5.8 to 5.11 Kernel 5.8 came with zfs-kmod-0.8.4-1ubuntu11.2 Ubuntu updates that broke it: Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux- image-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux-generic-hwe-20.04 :amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10) Sending the zfs send part to a file works, but then sending the file to zfs receive also fails. The dump file size seems reasonable but the contents may not be correct. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939177/+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
Re: [Kernel-packages] [Bug 1911352] Re: Black screen on boot after 20.04 upgraded to kernel 5.8
I have also had the boot problem disappear, return, and disappear again. On 1/22/21 11:12 AM, Wolf Pichler wrote: > I have these installed: > > dpkg -l | grep "linux\-[a-z]*\-" > > rc linux-modules-extra-5.4.0-42-generic 5.4.0-42.46 > ii linux-modules-extra-5.4.0-58-generic 5.4.0-58.64 > ii linux-modules-extra-5.8.0-36-generic 5.8.0-36.40~20.04.1 > ii linux-modules-extra-5.8.0-38-generic 5.8.0-38.43~20.04.1 > > I tried as Charles Green said: Switching to tty2 and then back to tty1 causes > the boot to complete. > (Ctrl+Alt+F2, Ctrl+Alt+F1) > -- 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/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 Status in linux package in Ubuntu: Confirmed Bug description: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben4518 F pulseaudio /dev/snd/pcmC0D0p: ben4518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-27 (138 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+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
Re: [Kernel-packages] [Bug 1911352] Re: Black screen on boot after 20.04 upgraded to kernel 5.8
The ctrl+alt+f2 - this was a fresh install on a system76 machine, running the integrated graphics. I have since loaded the NVidia drivers and my some miracle, I no longer need this work around. The ttys run from 1 to 7, I think, but the keyboard shortcuts to activate them are always ctrl+alt+f(num) On 1/20/21 12:18 PM, Ben Hoyt wrote: > Charles, very interesting. Though I wonder if yours is a different > problem, partly because it's not in tty mode at all (for me it's in a > graphical mode, sometimes with the Dell logo up). I can't seem to switch > to tty2 using Alt-F2 or Ctrl-Alt-F2 -- what are the exact keys you're > using? > -- 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/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 Status in linux package in Ubuntu: Confirmed Bug description: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben4518 F pulseaudio /dev/snd/pcmC0D0p: ben4518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-27 (138 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+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 1911352] Re: Black screen on boot after 20.04 upgraded to kernel 5.8
I've got the same issue on a system76 gazelle - I just reinstalled 20.04 hoping that this would fix the issue, but the 5.8.0-38 kernel does not complete the boot cycle by itself. I have found that switching to tty2 and then back to tty1 causes the boot to complete -- 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/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 Status in linux package in Ubuntu: Confirmed Bug description: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben4518 F pulseaudio /dev/snd/pcmC0D0p: ben4518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-27 (138 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+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 1910875] Re: Broadcom wireless driver failed to install with code 10 on focal 20.04
@jsarka, Thanks for those clear instructions! As it turns out I already
figured out (I hope) how to revert to kernel 5.4. That has brought back
my wifi. If other things go bonkers, I'll get 5.8 back and follow your
steps.
The bump to 5.8 broke several things on my system, which is why I first
tried downgrading kernels. I deliberately picked an LTS, so I'm very
surprised that I got a kernel bump that skips three point releases
without any warning.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1910875
Title:
Broadcom wireless driver failed to install with code 10 on focal
20.04
Status in bcmwl package in Ubuntu:
Confirmed
Bug description:
First, I suspect this may be the same bug as Bug #1905211 "package
bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed focal fossa in
kernel v5.9" because I got the same error "installed bcmwl-kernel-
source package post-installation script subprocess returned error exit
status 10". However, I wanted to make a separate report because I am
still on kernel v5.8. Please merge these threads if it seems like
they're the same bug.
Anyway, my problem is this:
The last time I installed a tranche of system updates, I got a "System
software problem detected" dialog and submitted the crash report. The
next time I booted up my computer, the Broadcom wifi device was not
recognized. The wifi had worked fine up until that point.
I tried to manually uninstall and reinstall the driver using dpkg with
the bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu5) package
downloaded from packages.ubuntu.com (the machine in question does not
have a wired ethernet connection). dpkg produced the following
output:
Preparing to unpack bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu5_amd64.deb
...
Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu5) over
(6.30.223.271+bdcom-0ubuntu5) ...
Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu5) ...
Loading new bcmwl-6.30.223.271+bdcom DKMS files...
Building for 5.8.0-36-generic
Building for architecture x86_64
Building initial module for 5.8.0-36-generic
ERROR: Cannot create report: [Errno 17] File exists:
'/var/crash/bcmwl-kernel-source.0.crash'
Error! Bad return status for module build on kernel: 5.8.0-36-generic (x86_64)
Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more
information.
dpkg: error processing package bcmwl-kernel-source (--install):
installed bcmwl-kernel-source package post-installation script subprocess
returned error exit status 10
Errors were encountered while processing:
bcmwl-kernel-source
The make log from my manually installation attempt read:
DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.8.0-36-generic
(x86_64)
Sat 09 Jan 2021 01:14:26 PM PST
make: Entering directory '/usr/src/linux-headers-5.8.0-36-generic'
CFG80211 API is prefered for this kernel version
Using CFG80211 API
AR /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o
CC [M]
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In
function ‘osl_reg_map’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
error: implicit declaration of function ‘ioremap_nocache’; did you mean
‘ioremap_cache’? [-Werror=implicit-function-declaration]
949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ^~~
| ioremap_cache
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
warning: returning ‘int’ from a function with return type ‘void *’ makes
pointer from integer without a cast [-Wint-conversion]
949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ~^~~~
In file included from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:
In function ‘wl_set_auth_type’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5:
warning: this statement may fall through [-Wimplicit-fallthrough=]
52 | if (wl_dbg_level & WL_DBG_DBG) { \
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:816:3:
note: in expansion of macro ‘WL_DBG’
816 | WL_DBG(("network eap\n"));
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:817:2:
note: here
817 | de
[Kernel-packages] [Bug 1910875] Re: Broadcom wireless driver failed to install with code 10 on focal 20.04
I'm new to Linux, so bear with me, but...Within the last hour or so I installed a bunch of system updates in KDE Discover, and suddenly wifi stopped working after the enforced restart. By "stopped working", I mean I have no internet connection via wifi and `nmcli dev` no longer lists my wireless device "wlp2so" *at all*. I'm on an Apple MacBookPro9,2 running 20.04 with KDE. "Driver Manger" tells me I'm using "Broadcom 802.11 Linux STA wireless driver source from bcmwl-kernel-source (proprietary)", for the BCM4331 device. I tried clicking "Do not use the device" and then re-enabling it but I got some cryptic error. Upon re-opening Driver Manager it again says I'm using the proprietary driver. I hope this can be quickly fixed, since this machine is now internet- free except for the occasional times I can plug into ethernet. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1910875 Title: Broadcom wireless driver failed to install with code 10 on focal 20.04 Status in bcmwl package in Ubuntu: Confirmed Bug description: First, I suspect this may be the same bug as Bug #1905211 "package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed focal fossa in kernel v5.9" because I got the same error "installed bcmwl-kernel- source package post-installation script subprocess returned error exit status 10". However, I wanted to make a separate report because I am still on kernel v5.8. Please merge these threads if it seems like they're the same bug. Anyway, my problem is this: The last time I installed a tranche of system updates, I got a "System software problem detected" dialog and submitted the crash report. The next time I booted up my computer, the Broadcom wifi device was not recognized. The wifi had worked fine up until that point. I tried to manually uninstall and reinstall the driver using dpkg with the bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu5) package downloaded from packages.ubuntu.com (the machine in question does not have a wired ethernet connection). dpkg produced the following output: Preparing to unpack bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu5_amd64.deb ... Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu5) over (6.30.223.271+bdcom-0ubuntu5) ... Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu5) ... Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.8.0-36-generic Building for architecture x86_64 Building initial module for 5.8.0-36-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/bcmwl-kernel-source.0.crash' Error! Bad return status for module build on kernel: 5.8.0-36-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information. dpkg: error processing package bcmwl-kernel-source (--install): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 Errors were encountered while processing: bcmwl-kernel-source The make log from my manually installation attempt read: DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.8.0-36-generic (x86_64) Sat 09 Jan 2021 01:14:26 PM PST make: Entering directory '/usr/src/linux-headers-5.8.0-36-generic' CFG80211 API is prefered for this kernel version Using CFG80211 API AR /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In function ‘osl_reg_map’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] 949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size)); | ^~~ | ioremap_cache /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: warning: returning ‘int’ from a function with return type ‘void *’ makes pointer from integer without a cast [-Wint-conversion] 949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size)); | ~^~~~ In file included from /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c: In function ‘wl_set_auth_type’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5: warning: this statement may fall through
[Kernel-packages] [Bug 1860416] [NEW] Mint 5.3.0-26 does not boot
Public bug reported: Hello, I updated the kernel from 5.0 to 5.3 and I cannot boot anymore. Booting with 5.0 works perfectly Thank you ** 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/1860416 Title: Mint 5.3.0-26 does not boot Status in linux package in Ubuntu: New Bug description: Hello, I updated the kernel from 5.0 to 5.3 and I cannot boot anymore. Booting with 5.0 works perfectly Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860416/+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 1851340] Re: [mgag200] Ubuntu 19.10 upgrade results in invisible mouse cursor on Matrox G200eR2
Good day just did an update and the issue is still their
--
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/1851340
Title:
[mgag200] Ubuntu 19.10 upgrade results in invisible mouse cursor on
Matrox G200eR2
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Eoan:
Fix Committed
Bug description:
== SRU Justification ==
The cursor on Matrox G200eR2 will disappear after upgrading kernel from
Disco to Eoan, this is caused by this commit that got applied in Eoan:
4dc57b10 (drm/mgag200: Rewrite cursor handling)
== Fix ==
* a9c342ab (drm/mgag200: Don't unpin the current cursor image's buffer.)
* cf578c8c (drm/mgag200: Set cursor scanout address to correct BO)
* e61576c4 (drm/mgag200: add in missing { } around if block)
* a0fd72d2 (drm/mgag200: Pin displayed cursor BO to video memory)
Focal got these patches already and it does not have this issue.
== Test ==
Test kernel could be found here:
https://people.canonical.com/~phlin/kernel/lp-1851340-mgag200-cursor/
Verified by the bug reporter, John Hartley, the patched kernel can fix
this issue.
== Regression Potential ==
Low, change limited to mgag200 cursor itself, and it's already been
applied on newer releases.
== Original Bug Report ==
Following in place upgrade of Ubuntu 19.04 -> 19.10 I no longer have visible
cursor with my Gnone desktop.
I have found the same problem when upgrading 2 machines from Ubuntu
19.04 -> 19.10.
Reproducing problem is easy:
1. Open Ubuntu Update Window
2. Select "Upgrade"
3. On completion of update (after reboot) cursor is no longer visible.
4. This applies to display connected to VGA port on host with USB Keyboard +
Mouse
While the connected display has no visible cursor and so is usable, I
have always used X11VNC Server to provide network GUI access. On the
remote X11VNC display I see and can use the cursor.
This bug report is being sent via Remote X11VNC window, as I cannot
use the main VGA display window (due to lack of visible cursor)
I have done search online and thought that maybe issue was with my USB
Mighty Mouse, so I also tried with Logitech M100R USB Mouse. Same
result, no visible mouse cursor.
I have done: "grep usb /var/log/syslog" and can see many USB events,
including both Apple and Logitech mouse detection events.
NOTE:
Due to compatibility issue with X11VNC, I have disable Wayland on both
machines by adding the following option to: /etc/gdm3/custom.conf
WaylandEnable=false
Regards,
John Hartley.
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.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 5 18:25:23 2019
DistUpgraded: 2019-11-05 15:20:04,402 ERROR got error from PostInstallScript
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: eoan
DistroVariant: ubuntu
GraphicsCard:
Matrox Electronics Systems Ltd. G200eR2 [102b:0534] (rev 01) (prog-if 00
[VGA controller])
Subsystem: Lenovo G200eR2 [1d49:0a01]
InstallationDate: Installed on 2018-12-17 (322 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
MachineType: LENOVO System x3650 M5: -[8871AC1]-
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic
root=UUID=3b8f415b-7e78-461c-83df-64f1f1a7826a ro ipv6.disable=1 quiet splash
iommu=1 intel_iommu=on ipv6.disable=1 vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to eoan on 2019-11-05 (0 days ago)
dmi.bios.date: 06/03/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: -[TCE140H-2.91]-
dmi.board.asset.tag: (none)
dmi.board.name: 01KN179
dmi.board.vendor: LENOVO
dmi.board.version: NULL
dmi.chassis.asset.tag: none
dmi.chassis.type: 23
dmi.chassis.vendor: LENOVO
dmi.chassis.version: none
dmi.modalias:
dmi:bvnLENOVO:bvr-[TCE140H-2.91]-:bd06/03/2019:svnLENOVO:pnSystemx3650M5-[8871AC1]-:pvr13:rvnLENOVO:rn01KN179:rvrNULL:cvnLENOVO:ct23:cvrnone:
dmi.product.family: System X
dmi.product.name: System x3650 M5: -[8871AC1]-
dmi.product.sku: (none)
dmi.product.version: 13
dmi.sys.vendor: LENOVO
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:1
[Kernel-packages] [Bug 869017] Re: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used)
Some additional information and observations. What I am currently seeing with this issue on 3 systems running Ubuntu 18.04 that did not occur on the same systems that previously ran 16.04 is that the actual screen blanking in 18.04, aside from default settings or overrides, fails to turn off the monitor using DPMS as it did in 16.04, but only with nvidia binary drivers installed and only in 18.04, and only with the console blanking code in its current state. In 18.04 without the nvidia binary driver, console blanking seems to work, as expected, with the consoleblank=n. This includes a correct power down. In 18.04 with the nvidia binary driver 340.107, console blanking only blanks the screen, but fails to power down the monitor- yet a call to vbetool dpms off does work, as do any similar calls in X for those systems that have X installed. So if vbetool dpms works with the nvidia binary driver and the console blanking code no longer does, I am half way to an assumption that the dpms code in the console blanking has changed, with some reservation that possibly the latest nvidia binary driver doesn't like the way the call is coming from the newly changed console blanking code. This problem did not exist in 16.04, on any of our systems to my knowledge, with or without a graphical desktop installed and with or without a binary driver installed. >From my perspective, this isn't an issue of default blanking behaviour, but rather an issue with a broken dpms call in 18.04 to a system with the nvidia binary driver. Other calls, such as vbetool dpms off work as do those within graphical desktop systems such as those like the one that xscreensaver uses. -- 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/869017 Title: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used) Status in kbd package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in kbd source package in Zesty: Invalid Status in linux source package in Zesty: Fix Released Status in kbd package in Debian: Fix Released Bug description: James Rice of Jump Networks noticed that there is a screen-blanker enabled on Ubuntu Server. James notes that this blanking is not enabling DPMS power saving (thereby negating any power-saving benefit), and is simply turning the screen content blank. This means that the crash output is invisible which is unhelpful on a server (virtual or otherwise). Ideally the screen should (at a minimum) be turned on and unblanked at the point of an OOPs/crash being printed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/869017/+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 869017] Re: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used)
To Robie Basak, specifically #22, You said, "I don't see how we created another problem. We changed the default, that's all." You seem to have concluded that merely a change of default functionally was made at some point. Perhaps that is the case. If so, what specifically was the default setting that was changed? For example, was it a kernel compilation time option? If so, can you please specify what setting can be changed back in order to re-enable Console blanking using DPMS (console display in power saving mode) for Ubuntu server 18.04? -- 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/869017 Title: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used) Status in kbd package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in kbd source package in Zesty: Invalid Status in linux source package in Zesty: Fix Released Status in kbd package in Debian: Fix Released Bug description: James Rice of Jump Networks noticed that there is a screen-blanker enabled on Ubuntu Server. James notes that this blanking is not enabling DPMS power saving (thereby negating any power-saving benefit), and is simply turning the screen content blank. This means that the crash output is invisible which is unhelpful on a server (virtual or otherwise). Ideally the screen should (at a minimum) be turned on and unblanked at the point of an OOPs/crash being printed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/869017/+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 1767568] Re: Console DPMS is not enabled by default in Ubuntu Server 18.04
To Robie Basak, specifically with regards to #37. The title of this bug already specified particularly that Console DPMS is not working. This bug report already was not about simply console blanking. I understand that the original reporter said that he got it working with setterm, but as by convention these bug reports often require verification from others in order to get any attention, it seems only reasonable that after many have said that the DPMS power saving is what is not working, while simple blanking and leaving the monitor on is what is currently happening, that this bug should not have been marked invalid. As many others have pointed out, Console DPMS power saving is not working in 18.04. It is clear after reading this thread as well as a few basic tests with setterm that nobody has working Console DPMS power saving at all in Ubuntu 18.04. If this is only a matter of default settings as you seem to have concluded that it is, then please specify which optional setting re- enables Console DPMS power saving, because the following does NOT work on any of my Ubuntu 18.04 installations (as well as several others in this bug report) beyond mere blanking and leaving the monitor on: in grub.cfg consoleblank=600 setterm --powersave powerdown setterm --powerdown 10 If this is just a kernel option that is no longer the default setting, then it should be specified here, in this bug report, what the appropriate change is to revert back to a very mature working functionality. -- 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/1767568 Title: Console DPMS is not enabled by default in Ubuntu Server 18.04 Status in linux package in Ubuntu: Invalid Bug description: My console display is DPMS capable, i.e., power management functions worked before upgrading from Ubuntu Server 16.0.4.4. Currently the display stays on 24x7 with idle keyboard input. 1) My release information is as follows: Description:Ubuntu 18.04 LTS Release:18.04 2) I am not sure what package this issue is tied to. The current kernel appears to have DPMS support enabled, per the configuration file in /boot. If the kernel is responsible, below is the version I am running. linux-generic: Installed: 4.15.0.20.23 3) I expected to have DPMS support for my console as in the previous release of Ubuntu Server. 4) What happened instead is my monitor stays on all the time, without DPMS controlling it. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-20-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ab9de6b4-cca0-4e5c-89d7-e706214c8f11 InstallationDate: Installed on 2014-07-23 (1378 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Gigabyte Technology Co., Ltd. X58A-UD5 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 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=5631d3aa-8dce-4306-a08d-4ab3753256ab ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic apport-hook-error Uname: Linux 4.15.0-20-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-04-26 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 03/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name
Re: [Kernel-packages] [Bug 1609750] Re: Audio not working on Acer Chromebook R11
thanks for the feedback On Thu, Sep 26, 2019, 09:55 daniel primo stuart <1609...@bugs.launchpad.net> wrote: > Kernel needs this patch for maxim98090 to work on cyan and some baytrail > chromebooks: > > https://github.com/torvalds/linux/commit/d5e120422db8808e1c8b1507900ca393a877c58f > > As it didn't make to 5.3 on time, would be nice if it were backported by > ubuntu devs > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1803810). > https://bugs.launchpad.net/bugs/1609750 > > Title: > Audio not working on Acer Chromebook R11 > > Status in linux: > Confirmed > Status in linux package in Ubuntu: > In Progress > Status in pulseaudio package in Ubuntu: > Invalid > > Bug description: > Audio is not working at all on Acer Chromebook R11 (codename CYAN). > It's a Intel Braswell platform. snd_hda_intel messages seem normal, > but Pulseaudio does not detect sound hardware. > > ProblemType: Bug > DistroRelease: Ubuntu 16.10 > Package: pulseaudio 1:9.0-1.1ubuntu1 > ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 > Uname: Linux 4.4.0-33-generic x86_64 > ApportVersion: 2.20.3-0ubuntu2 > Architecture: amd64 > AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', > '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', > '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', > '/dev/snd/timer'] failed with exit code 1: > CurrentDesktop: Unity > Date: Thu Aug 4 14:12:03 2016 > InstallationDate: Installed on 2016-07-22 (13 days ago) > InstallationMedia: > > PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No > PulseAudio daemon running, or not running as session daemon. > SourcePackage: pulseaudio > Symptom: audio > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 05/20/2016 > dmi.bios.vendor: coreboot > dmi.chassis.type: 3 > dmi.chassis.vendor: GOOGLE > dmi.modalias: > dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: > dmi.product.name: Cyan > dmi.product.version: 1.0 > dmi.sys.vendor: GOOGLE > --- > ApportVersion: 2.20.3-0ubuntu2 > Architecture: amd64 > AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', > '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', > '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', > '/dev/snd/timer'] failed with exit code 1: > CurrentDesktop: Unity > DistroRelease: Ubuntu 16.10 > HibernationDevice: RESUME=UUID=53fe7902-c347-4ff8-945d-a3e3de773a08 > InstallationDate: Installed on 2016-07-22 (13 days ago) > InstallationMedia: > > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 003: ID 8087:0a2a Intel Corp. >Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: GOOGLE Cyan > Package: linux-image-4.4.0-33-generic 4.4.0-33.52 > PackageArchitecture: amd64 > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic > root=UUID=742e4082-264a-4459-93df-9ec07b41d5e8 ro quiet splash vt.handoff=7 > ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 > PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No > PulseAudio daemon running, or not running as session daemon. > RelatedPackageVersions: >linux-restricted-modules-4.4.0-33-generic N/A >linux-backports-modules-4.4.0-33-generic N/A >linux-firmware1.159 > Tags: yakkety > Uname: Linux 4.4.0-33-generic x86_64 > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > _MarkForUpload: True > dmi.bios.date: 05/20/2016 > dmi.bios.vendor: coreboot > dmi.chassis.type: 3 > dmi.chassis.vendor: GOOGLE > dmi.modalias: > dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: > dmi.product.name: Cyan > dmi.product.version: 1.0 > dmi.sys.vendor: GOOGLE > > To manage notifications about this bug go to: > https://bugs.launchpad.net/kernel/+bug/1609750/+subscriptions > -- 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/1609750 Title: Audio not working on Acer Chromebook R11 Status in linux: Confirmed Status in linux package in Ubuntu: In Progress Status in pulseaudio package in Ubuntu: Invalid Bug description: Audio is not working at all on Acer Chromebook R11 (codename CYAN). It's a Intel Braswell platform. snd_hda_intel messages seem normal, but Pulseaudio does not detect sound hardware. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: pulseaudio 1:9.0-1.1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 Uname: Linux 4.4.0-33-generic x86_64 ApportVersion: 2.20.3-0ubuntu2 Architecture:
[Kernel-packages] [Bug 1823074] Re: Adjust xenial d-i builds to only used signed kernel image
I see that this is a result of LP #1764794, I've adjusted my copy debian-installer source package to compensate (using bionic version as a template). This however, should be fixed for xenial if there is going to be another point release. ** Summary changed: - xenial 4.4.0-145 image udeb overwrites unsigned image + Adjust xenial d-i builds to only used signed kernel image ** Package changed: linux-signed (Ubuntu) => debian-installer (Ubuntu) ** Summary changed: - Adjust xenial d-i builds to only used signed kernel image + Adjust xenial d-i builds to only use signed kernel image -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1823074 Title: Adjust xenial d-i builds to only use signed kernel image Status in debian-installer package in Ubuntu: New Bug description: The payload in the xenial package kernel-signed-image-4.4.0-145 -generic-di_4.4.0-145.171_amd64.udeb doesn't have the proper suffix and overwrites the unsigned version of the same kernel image: (from data.tar.xz from the package): ./ ./boot/ ./boot/vmlinuz-4.4.0-145-generic It should be ./ ./boot/ ./boot/vmlinuz-4.4.0-145-generic.efi.signed This was found while trying to build out a set of installer images via building the debian-installer source package from xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1823074/+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 1823074] [NEW] xenial 4.4.0-145 image udeb overwrites unsigned image
Public bug reported: The payload in the xenial package kernel-signed-image-4.4.0-145-generic- di_4.4.0-145.171_amd64.udeb doesn't have the proper suffix and overwrites the unsigned version of the same kernel image: (from data.tar.xz from the package): ./ ./boot/ ./boot/vmlinuz-4.4.0-145-generic It should be ./ ./boot/ ./boot/vmlinuz-4.4.0-145-generic.efi.signed This was found while trying to build out a set of installer images via building the debian-installer source package from xenial ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1823074 Title: xenial 4.4.0-145 image udeb overwrites unsigned image Status in linux-signed package in Ubuntu: New Bug description: The payload in the xenial package kernel-signed-image-4.4.0-145 -generic-di_4.4.0-145.171_amd64.udeb doesn't have the proper suffix and overwrites the unsigned version of the same kernel image: (from data.tar.xz from the package): ./ ./boot/ ./boot/vmlinuz-4.4.0-145-generic It should be ./ ./boot/ ./boot/vmlinuz-4.4.0-145-generic.efi.signed This was found while trying to build out a set of installer images via building the debian-installer source package from xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1823074/+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 1806755] Re: 4.19 kernels before 8.9 have filesystem corruption under memory pressure
New fixed kernel is out, 60 days later ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806755 Title: 4.19 kernels before 8.9 have filesystem corruption under memory pressure Status in linux package in Ubuntu: Fix Released Bug description: Bug 201685 - ext4 file system corruption https://bugzilla.kernel.org/show_bug.cgi?id=201685 Quote: Before running the bisect, I tested these kernels (all Ubuntu mainline from http://kernel.ubuntu.com/~kernel-ppa/mainline/): Had FS corruption: 4.19-rc1 4.19 4.19.1 4.19.2 4.19.3 4.19.4 4.19.5 4.19.6 No corruption (yet): 4.18 4.18.20 /quote Please release the latest security update for linux 4.18 to disco ASAP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806755/+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 1807264] Re: Ubuntu 18.04 Video Crash on Suspend/Hibernate
Very similar to kubuntu 16.04.1 with kernel 4.4.0-41 -- 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/1807264 Title: Ubuntu 18.04 Video Crash on Suspend/Hibernate Status in linux package in Ubuntu: Confirmed Bug description: After updating to 18.04 when the system automatically suspends/hibernates after non-use, the screen goes black, but will not wake up by taping the space bar, nor does it display the hibernation screen. Additionally, I'm using two screens the laptop and an external monitor connected with the Mini Display port. When required to come out of suspend, each screen behaves differently. The laptop screen flashes while the external monitor may show any of these: 1) background screen image with no tool bars or menu; 2) remains black; or 3) shows a gray image. The only way to recover is to reboot, either by holding the power button or Ctrl-F1 to log back into the system and use the reboot command; only the external monitor will recover to a terminal screen. Upgrading the kernel from 4.15 thru 4.19 does not change the suspend/hibernation issue. It seems to be video related issue, since HDMI port reacts differently than the Mini Display port, in that device settings do not operate the same and changing the settings can cause the same type of screen crash. Additionally, trying NVIDIA drivers will help with the suspend/hibernation problem and allows the hibernation screen to show, but is not a cure. Sometimes the NVIDIA drivers will allow it to come back from hibernation and sometimes not. My suspicion is that the drivers are not correct for the Intel video card. I am also flummoxed by the fact that I cannot control suspend/hibernation. There is no obvious way to keep the system from suspending. Screen lock is OFF. Automatic suspend is OFF. Power button suspend is OFF. There needs to be more control; the ability to eliminate any and all suspend operations is a must! With this type of control, I could have kept if from suspending until a fix is generated. Reports are as follows: - lspci: 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09) 00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 09) 00:04.0 Signal processing controller: Intel Corporation Haswell-ULT Thermal Subsystem (rev 09) 00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04) 00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04) 00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev e4) 00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev e4) 00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04) 00:1f.6 Signal processing controller: Intel Corporation 8 Series Thermal (rev 04) 02:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) - ubuntu-bug linux: Problem in linux-image-4.19.17-041907-generic cannot be reported, this report is about a package that is not installed - cat /proc/version_signature > version.log: cat: /proc/version_signature: No such file or directory - sudo lspci -vnvn > lspci-vnvn.log: (no response) - lsb_release -rd: Ubuntu 18.04 LTS - apt-cache policy pkgname: N: Unable to locate package pkgname - sudo lshw -C display; uname -a; lsb_release -a; sudo dmidecode -t 1: *-display description: VGA compatible controller product: Haswell-ULT Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:42 memory:f780-f7bf memory:e000-efff ioport:f000(size=64) memory:c-d Linux tablet3 4.19.7-041907-generic #201812052010 SMP Wed Dec 5 20:11:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux LSB Version: core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch Distributor ID: Ubuntu Description: Ubuntu 18.04 LTS Release: 18.04 Codename: bionic --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2014-10-31 (1497 days ago) InstallationMedia
[Kernel-packages] [Bug 1806755] Re: All 4.19 kernels have filesystem corruption under memory pressure, upstream is doing triage
4.19.0-8.9 reports in the changelog that this is fixed. When this version is released, this bug can be closed. ** Summary changed: - All 4.19 kernels have filesystem corruption under memory pressure, upstream is doing triage + 4.19 kernels before 8.9 have filesystem corruption under memory pressure -- 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/1806755 Title: 4.19 kernels before 8.9 have filesystem corruption under memory pressure Status in linux package in Ubuntu: Confirmed Bug description: Bug 201685 - ext4 file system corruption https://bugzilla.kernel.org/show_bug.cgi?id=201685 Quote: Before running the bisect, I tested these kernels (all Ubuntu mainline from http://kernel.ubuntu.com/~kernel-ppa/mainline/): Had FS corruption: 4.19-rc1 4.19 4.19.1 4.19.2 4.19.3 4.19.4 4.19.5 4.19.6 No corruption (yet): 4.18 4.18.20 /quote Please release the latest security update for linux 4.18 to disco ASAP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806755/+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 1806755] Re: All 4.19 kernels have filesystem corruption under memory pressure, upstream is doing triage
I am still running cosmic, since no secure and functional Kernel is out for disco at the moment. -- 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/1806755 Title: All 4.19 kernels have filesystem corruption under memory pressure, upstream is doing triage Status in linux package in Ubuntu: Confirmed Bug description: Bug 201685 - ext4 file system corruption https://bugzilla.kernel.org/show_bug.cgi?id=201685 Quote: Before running the bisect, I tested these kernels (all Ubuntu mainline from http://kernel.ubuntu.com/~kernel-ppa/mainline/): Had FS corruption: 4.19-rc1 4.19 4.19.1 4.19.2 4.19.3 4.19.4 4.19.5 4.19.6 No corruption (yet): 4.18 4.18.20 /quote Please release the latest security update for linux 4.18 to disco ASAP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806755/+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 187761] Re: Need a way to disable selected modules with a kernel flag
I have a usecase for disabling kernel modules: I need to disable uas when booting (or at least after booting) a livecd: All my usb3 to SATA adapters load uas.ko when plugged, then promptly malfunction. They work when plugged into a usb2 port. Deleting uas.ko breaks usb hotplug. I am assuming that usb storage will actually work without uas. -- 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/187761 Title: Need a way to disable selected modules with a kernel flag Status in linux package in Ubuntu: In Progress Bug description: Binary package hint: linux-image Bug #90271 and bug #187671 describe situations where Live CDs and install CDs fail to work because a broken kernel module causes a hang before user has a say. The error may be in an optional kernel module (such as sound card driver or memory card reader) but the end user has no way to prevent kernel from loading a possibly known broken module. Vanilla kernels from kernel.org support flag disablemodules (e.g. disablemodules=8139too,sdhci prevents linux kernel from loading 8139too.ko or sdhci.ko) but such flag does not seem to work with Ubuntu. This is a feature request to enable such a flag. It is not needed for normal use but in case of rare hardware exposing a bug in a kernel module not having such a flag prevents one from booting Ubuntu. (I'd prefer booting without network adapter or memory card reader to not booting at all). This issue also causes slowdowns such as bug #187671 which cannot proceed until bug #90271 is fixed because testing possible fixes for the bug is really hard until the other kernel module has been fixed. (This is because both bugs affect the same laptop hardware and both kernel modules cause a kernel hang.) I'd consider disablemodules flag similar to acpi flag - it should not be needed but still we need it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/187761/+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 1806755] Re: All 4.19 kernels have filesystem corruption under memory pressure, upstream is doing triage
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806755 Title: All 4.19 kernels have filesystem corruption under memory pressure, upstream is doing triage Status in linux package in Ubuntu: Confirmed Bug description: Bug 201685 - ext4 file system corruption https://bugzilla.kernel.org/show_bug.cgi?id=201685 Quote: Before running the bisect, I tested these kernels (all Ubuntu mainline from http://kernel.ubuntu.com/~kernel-ppa/mainline/): Had FS corruption: 4.19-rc1 4.19 4.19.1 4.19.2 4.19.3 4.19.4 4.19.5 4.19.6 No corruption (yet): 4.18 4.18.20 /quote Please release the latest security update for linux 4.18 to disco ASAP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806755/+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 1806755] [NEW] All 4.19 kernels have filesystem corruption under memory pressure, upstream is doing triage
Public bug reported: Bug 201685 - ext4 file system corruption https://bugzilla.kernel.org/show_bug.cgi?id=201685 Quote: Before running the bisect, I tested these kernels (all Ubuntu mainline from http://kernel.ubuntu.com/~kernel-ppa/mainline/): Had FS corruption: 4.19-rc1 4.19 4.19.1 4.19.2 4.19.3 4.19.4 4.19.5 4.19.6 No corruption (yet): 4.18 4.18.20 /quote Please release the latest security update for linux 4.18 to disco ASAP ** 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/1806755 Title: All 4.19 kernels have filesystem corruption under memory pressure, upstream is doing triage Status in linux package in Ubuntu: New Bug description: Bug 201685 - ext4 file system corruption https://bugzilla.kernel.org/show_bug.cgi?id=201685 Quote: Before running the bisect, I tested these kernels (all Ubuntu mainline from http://kernel.ubuntu.com/~kernel-ppa/mainline/): Had FS corruption: 4.19-rc1 4.19 4.19.1 4.19.2 4.19.3 4.19.4 4.19.5 4.19.6 No corruption (yet): 4.18 4.18.20 /quote Please release the latest security update for linux 4.18 to disco ASAP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806755/+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 1791323] Re: XFS fallocate implementation incorrectly reports ENOSPC
Confirmed in the latest RC kernel: charles@ubuntuvm:~/temp$ fallocate -l 1GB image.img charles@ubuntuvm:~/temp$ sudo modprobe loop [sudo] password for charles: charles@ubuntuvm:~/temp$ mkfs.xfs image.img meta-data=image.img isize=512agcount=4, agsize=61035 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0, rmapbt=0, reflink=0 data = bsize=4096 blocks=244140, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=855, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 charles@ubuntuvm:~/temp$ mkdir mnt charles@ubuntuvm:~/temp$ mount -o loop ./image.img mnt mount: only root can use "--options" option charles@ubuntuvm:~/temp$ sudo mount -o loop ./image.img mnt charles@ubuntuvm:~/temp$ cd mnt/ charles@ubuntuvm:~/temp/mnt$ sudo fallocate -o 0 -l 700mb image.img charles@ubuntuvm:~/temp/mnt$ sudo fallocate -o 0 -l 700mb image.img fallocate: fallocate failed: No space left on device charles@ubuntuvm:~/temp/mnt$ uname -a Linux ubuntuvm 4.19.0-041900rc3-generic #201809120832 SMP Wed Sep 12 12:35:08 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux charles@ubuntuvm:~/temp/mnt$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.1 LTS Release:18.04 Codename: bionic ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791323 Title: XFS fallocate implementation incorrectly reports ENOSPC Status in linux package in Ubuntu: Confirmed Bug description: When given an offset of 0 and a length, fallocate (man 2 fallocate) reports ENOSPC if the size of the file + the length to be allocated is greater than the available space. Example below using the fallocate command (man 1 fallocate) for simplicity; the issue is with the logic backing the system call. chathaway@bender:~/temp$ fallocate -l 1GB example.img chathaway@bender:~/temp$ mkfs.xfs example.img meta-data=example.imgisize=512agcount=4, agsize=61035 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0, rmapbt=0, reflink=0 data = bsize=4096 blocks=244140, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=855, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 chathaway@bender:~/temp$ sudo modprobe loop chathaway@bender:~/temp$ mkdir mnt chathaway@bender:~/temp$ sudo mount -o loop ./example.img ./mnt/ chathaway@bender:~/temp$ cd mnt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt fallocate: fallocate failed: No space left on device chathaway@bender:~/temp/mnt$ df -h . Filesystem Size Used Avail Use% Mounted on /dev/loop0 951M 766M 185M 81% /home/chathaway/temp/mnt Expected behaviour: because we allocate 768MB starting at offset 0, and have 951MB on the disk, we would expect that the allocation should be fine. Other filesystem behave this way (for example, ext4). Thanks! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chathaway 2608 F pulseaudio /dev/snd/controlC1: chathaway 2608 F pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.04 MachineType: ASUSTeK COMPUTER INC. UX303LN Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: initrd=\EFI\Pop_OS-c80adbe3-92ed-45ea-a314-7e7c694d0161\initrd.img root=UUID=c80adbe3-92ed-45ea-a314-7e7c694d0161 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm docker sudo wireshark _MarkForUpload: True dmi.bios.date: 09/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LN.204 dmi.bo
[Kernel-packages] [Bug 1791323] Re: XFS fallocate implementation incorrectly reports ENOSPC
Hi Joseph, Give me a moment to try testing the upstream kernel; I haven't done that before. This issue was first reported by a customer sometime back, we worked around it by changing the way we called fallocate. I believe I confirmed it back in 16.04, but I haven't tested beyond that. Charles -- 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/1791323 Title: XFS fallocate implementation incorrectly reports ENOSPC Status in linux package in Ubuntu: Incomplete Bug description: When given an offset of 0 and a length, fallocate (man 2 fallocate) reports ENOSPC if the size of the file + the length to be allocated is greater than the available space. Example below using the fallocate command (man 1 fallocate) for simplicity; the issue is with the logic backing the system call. chathaway@bender:~/temp$ fallocate -l 1GB example.img chathaway@bender:~/temp$ mkfs.xfs example.img meta-data=example.imgisize=512agcount=4, agsize=61035 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0, rmapbt=0, reflink=0 data = bsize=4096 blocks=244140, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=855, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 chathaway@bender:~/temp$ sudo modprobe loop chathaway@bender:~/temp$ mkdir mnt chathaway@bender:~/temp$ sudo mount -o loop ./example.img ./mnt/ chathaway@bender:~/temp$ cd mnt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt fallocate: fallocate failed: No space left on device chathaway@bender:~/temp/mnt$ df -h . Filesystem Size Used Avail Use% Mounted on /dev/loop0 951M 766M 185M 81% /home/chathaway/temp/mnt Expected behaviour: because we allocate 768MB starting at offset 0, and have 951MB on the disk, we would expect that the allocation should be fine. Other filesystem behave this way (for example, ext4). Thanks! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chathaway 2608 F pulseaudio /dev/snd/controlC1: chathaway 2608 F pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.04 MachineType: ASUSTeK COMPUTER INC. UX303LN Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: initrd=\EFI\Pop_OS-c80adbe3-92ed-45ea-a314-7e7c694d0161\initrd.img root=UUID=c80adbe3-92ed-45ea-a314-7e7c694d0161 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm docker sudo wireshark _MarkForUpload: True dmi.bios.date: 09/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LN.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LN.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX303LN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791323/+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 1791323] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1791323/+attachment/5186082/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791323 Title: XFS fallocate implementation incorrectly reports ENOSPC Status in linux package in Ubuntu: Confirmed Bug description: When given an offset of 0 and a length, fallocate (man 2 fallocate) reports ENOSPC if the size of the file + the length to be allocated is greater than the available space. Example below using the fallocate command (man 1 fallocate) for simplicity; the issue is with the logic backing the system call. chathaway@bender:~/temp$ fallocate -l 1GB example.img chathaway@bender:~/temp$ mkfs.xfs example.img meta-data=example.imgisize=512agcount=4, agsize=61035 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0, rmapbt=0, reflink=0 data = bsize=4096 blocks=244140, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=855, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 chathaway@bender:~/temp$ sudo modprobe loop chathaway@bender:~/temp$ mkdir mnt chathaway@bender:~/temp$ sudo mount -o loop ./example.img ./mnt/ chathaway@bender:~/temp$ cd mnt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt fallocate: fallocate failed: No space left on device chathaway@bender:~/temp/mnt$ df -h . Filesystem Size Used Avail Use% Mounted on /dev/loop0 951M 766M 185M 81% /home/chathaway/temp/mnt Expected behaviour: because we allocate 768MB starting at offset 0, and have 951MB on the disk, we would expect that the allocation should be fine. Other filesystem behave this way (for example, ext4). Thanks! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chathaway 2608 F pulseaudio /dev/snd/controlC1: chathaway 2608 F pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.04 MachineType: ASUSTeK COMPUTER INC. UX303LN Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: initrd=\EFI\Pop_OS-c80adbe3-92ed-45ea-a314-7e7c694d0161\initrd.img root=UUID=c80adbe3-92ed-45ea-a314-7e7c694d0161 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm docker sudo wireshark _MarkForUpload: True dmi.bios.date: 09/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LN.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LN.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX303LN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791323/+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 1791323] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1791323/+attachment/5186084/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791323 Title: XFS fallocate implementation incorrectly reports ENOSPC Status in linux package in Ubuntu: Confirmed Bug description: When given an offset of 0 and a length, fallocate (man 2 fallocate) reports ENOSPC if the size of the file + the length to be allocated is greater than the available space. Example below using the fallocate command (man 1 fallocate) for simplicity; the issue is with the logic backing the system call. chathaway@bender:~/temp$ fallocate -l 1GB example.img chathaway@bender:~/temp$ mkfs.xfs example.img meta-data=example.imgisize=512agcount=4, agsize=61035 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0, rmapbt=0, reflink=0 data = bsize=4096 blocks=244140, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=855, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 chathaway@bender:~/temp$ sudo modprobe loop chathaway@bender:~/temp$ mkdir mnt chathaway@bender:~/temp$ sudo mount -o loop ./example.img ./mnt/ chathaway@bender:~/temp$ cd mnt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt fallocate: fallocate failed: No space left on device chathaway@bender:~/temp/mnt$ df -h . Filesystem Size Used Avail Use% Mounted on /dev/loop0 951M 766M 185M 81% /home/chathaway/temp/mnt Expected behaviour: because we allocate 768MB starting at offset 0, and have 951MB on the disk, we would expect that the allocation should be fine. Other filesystem behave this way (for example, ext4). Thanks! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chathaway 2608 F pulseaudio /dev/snd/controlC1: chathaway 2608 F pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.04 MachineType: ASUSTeK COMPUTER INC. UX303LN Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: initrd=\EFI\Pop_OS-c80adbe3-92ed-45ea-a314-7e7c694d0161\initrd.img root=UUID=c80adbe3-92ed-45ea-a314-7e7c694d0161 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm docker sudo wireshark _MarkForUpload: True dmi.bios.date: 09/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LN.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LN.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX303LN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791323/+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 1791323] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1791323/+attachment/5186083/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791323 Title: XFS fallocate implementation incorrectly reports ENOSPC Status in linux package in Ubuntu: Confirmed Bug description: When given an offset of 0 and a length, fallocate (man 2 fallocate) reports ENOSPC if the size of the file + the length to be allocated is greater than the available space. Example below using the fallocate command (man 1 fallocate) for simplicity; the issue is with the logic backing the system call. chathaway@bender:~/temp$ fallocate -l 1GB example.img chathaway@bender:~/temp$ mkfs.xfs example.img meta-data=example.imgisize=512agcount=4, agsize=61035 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0, rmapbt=0, reflink=0 data = bsize=4096 blocks=244140, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=855, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 chathaway@bender:~/temp$ sudo modprobe loop chathaway@bender:~/temp$ mkdir mnt chathaway@bender:~/temp$ sudo mount -o loop ./example.img ./mnt/ chathaway@bender:~/temp$ cd mnt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt fallocate: fallocate failed: No space left on device chathaway@bender:~/temp/mnt$ df -h . Filesystem Size Used Avail Use% Mounted on /dev/loop0 951M 766M 185M 81% /home/chathaway/temp/mnt Expected behaviour: because we allocate 768MB starting at offset 0, and have 951MB on the disk, we would expect that the allocation should be fine. Other filesystem behave this way (for example, ext4). Thanks! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chathaway 2608 F pulseaudio /dev/snd/controlC1: chathaway 2608 F pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.04 MachineType: ASUSTeK COMPUTER INC. UX303LN Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: initrd=\EFI\Pop_OS-c80adbe3-92ed-45ea-a314-7e7c694d0161\initrd.img root=UUID=c80adbe3-92ed-45ea-a314-7e7c694d0161 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm docker sudo wireshark _MarkForUpload: True dmi.bios.date: 09/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LN.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LN.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX303LN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791323/+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 1791323] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1791323/+attachment/5186081/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791323 Title: XFS fallocate implementation incorrectly reports ENOSPC Status in linux package in Ubuntu: Confirmed Bug description: When given an offset of 0 and a length, fallocate (man 2 fallocate) reports ENOSPC if the size of the file + the length to be allocated is greater than the available space. Example below using the fallocate command (man 1 fallocate) for simplicity; the issue is with the logic backing the system call. chathaway@bender:~/temp$ fallocate -l 1GB example.img chathaway@bender:~/temp$ mkfs.xfs example.img meta-data=example.imgisize=512agcount=4, agsize=61035 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0, rmapbt=0, reflink=0 data = bsize=4096 blocks=244140, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=855, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 chathaway@bender:~/temp$ sudo modprobe loop chathaway@bender:~/temp$ mkdir mnt chathaway@bender:~/temp$ sudo mount -o loop ./example.img ./mnt/ chathaway@bender:~/temp$ cd mnt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt fallocate: fallocate failed: No space left on device chathaway@bender:~/temp/mnt$ df -h . Filesystem Size Used Avail Use% Mounted on /dev/loop0 951M 766M 185M 81% /home/chathaway/temp/mnt Expected behaviour: because we allocate 768MB starting at offset 0, and have 951MB on the disk, we would expect that the allocation should be fine. Other filesystem behave this way (for example, ext4). Thanks! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chathaway 2608 F pulseaudio /dev/snd/controlC1: chathaway 2608 F pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.04 MachineType: ASUSTeK COMPUTER INC. UX303LN Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: initrd=\EFI\Pop_OS-c80adbe3-92ed-45ea-a314-7e7c694d0161\initrd.img root=UUID=c80adbe3-92ed-45ea-a314-7e7c694d0161 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm docker sudo wireshark _MarkForUpload: True dmi.bios.date: 09/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LN.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LN.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX303LN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791323/+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 1791323] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1791323/+attachment/5186080/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791323 Title: XFS fallocate implementation incorrectly reports ENOSPC Status in linux package in Ubuntu: Confirmed Bug description: When given an offset of 0 and a length, fallocate (man 2 fallocate) reports ENOSPC if the size of the file + the length to be allocated is greater than the available space. Example below using the fallocate command (man 1 fallocate) for simplicity; the issue is with the logic backing the system call. chathaway@bender:~/temp$ fallocate -l 1GB example.img chathaway@bender:~/temp$ mkfs.xfs example.img meta-data=example.imgisize=512agcount=4, agsize=61035 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0, rmapbt=0, reflink=0 data = bsize=4096 blocks=244140, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=855, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 chathaway@bender:~/temp$ sudo modprobe loop chathaway@bender:~/temp$ mkdir mnt chathaway@bender:~/temp$ sudo mount -o loop ./example.img ./mnt/ chathaway@bender:~/temp$ cd mnt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt fallocate: fallocate failed: No space left on device chathaway@bender:~/temp/mnt$ df -h . Filesystem Size Used Avail Use% Mounted on /dev/loop0 951M 766M 185M 81% /home/chathaway/temp/mnt Expected behaviour: because we allocate 768MB starting at offset 0, and have 951MB on the disk, we would expect that the allocation should be fine. Other filesystem behave this way (for example, ext4). Thanks! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chathaway 2608 F pulseaudio /dev/snd/controlC1: chathaway 2608 F pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.04 MachineType: ASUSTeK COMPUTER INC. UX303LN Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: initrd=\EFI\Pop_OS-c80adbe3-92ed-45ea-a314-7e7c694d0161\initrd.img root=UUID=c80adbe3-92ed-45ea-a314-7e7c694d0161 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm docker sudo wireshark _MarkForUpload: True dmi.bios.date: 09/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LN.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LN.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX303LN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791323/+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 1791323] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1791323/+attachment/5186079/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791323 Title: XFS fallocate implementation incorrectly reports ENOSPC Status in linux package in Ubuntu: Confirmed Bug description: When given an offset of 0 and a length, fallocate (man 2 fallocate) reports ENOSPC if the size of the file + the length to be allocated is greater than the available space. Example below using the fallocate command (man 1 fallocate) for simplicity; the issue is with the logic backing the system call. chathaway@bender:~/temp$ fallocate -l 1GB example.img chathaway@bender:~/temp$ mkfs.xfs example.img meta-data=example.imgisize=512agcount=4, agsize=61035 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0, rmapbt=0, reflink=0 data = bsize=4096 blocks=244140, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=855, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 chathaway@bender:~/temp$ sudo modprobe loop chathaway@bender:~/temp$ mkdir mnt chathaway@bender:~/temp$ sudo mount -o loop ./example.img ./mnt/ chathaway@bender:~/temp$ cd mnt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt fallocate: fallocate failed: No space left on device chathaway@bender:~/temp/mnt$ df -h . Filesystem Size Used Avail Use% Mounted on /dev/loop0 951M 766M 185M 81% /home/chathaway/temp/mnt Expected behaviour: because we allocate 768MB starting at offset 0, and have 951MB on the disk, we would expect that the allocation should be fine. Other filesystem behave this way (for example, ext4). Thanks! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chathaway 2608 F pulseaudio /dev/snd/controlC1: chathaway 2608 F pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.04 MachineType: ASUSTeK COMPUTER INC. UX303LN Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: initrd=\EFI\Pop_OS-c80adbe3-92ed-45ea-a314-7e7c694d0161\initrd.img root=UUID=c80adbe3-92ed-45ea-a314-7e7c694d0161 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm docker sudo wireshark _MarkForUpload: True dmi.bios.date: 09/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LN.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LN.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX303LN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791323/+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 1791323] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1791323/+attachment/5186075/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791323 Title: XFS fallocate implementation incorrectly reports ENOSPC Status in linux package in Ubuntu: Confirmed Bug description: When given an offset of 0 and a length, fallocate (man 2 fallocate) reports ENOSPC if the size of the file + the length to be allocated is greater than the available space. Example below using the fallocate command (man 1 fallocate) for simplicity; the issue is with the logic backing the system call. chathaway@bender:~/temp$ fallocate -l 1GB example.img chathaway@bender:~/temp$ mkfs.xfs example.img meta-data=example.imgisize=512agcount=4, agsize=61035 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0, rmapbt=0, reflink=0 data = bsize=4096 blocks=244140, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=855, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 chathaway@bender:~/temp$ sudo modprobe loop chathaway@bender:~/temp$ mkdir mnt chathaway@bender:~/temp$ sudo mount -o loop ./example.img ./mnt/ chathaway@bender:~/temp$ cd mnt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt fallocate: fallocate failed: No space left on device chathaway@bender:~/temp/mnt$ df -h . Filesystem Size Used Avail Use% Mounted on /dev/loop0 951M 766M 185M 81% /home/chathaway/temp/mnt Expected behaviour: because we allocate 768MB starting at offset 0, and have 951MB on the disk, we would expect that the allocation should be fine. Other filesystem behave this way (for example, ext4). Thanks! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chathaway 2608 F pulseaudio /dev/snd/controlC1: chathaway 2608 F pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.04 MachineType: ASUSTeK COMPUTER INC. UX303LN Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: initrd=\EFI\Pop_OS-c80adbe3-92ed-45ea-a314-7e7c694d0161\initrd.img root=UUID=c80adbe3-92ed-45ea-a314-7e7c694d0161 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm docker sudo wireshark _MarkForUpload: True dmi.bios.date: 09/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LN.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LN.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX303LN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791323/+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 1791323] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1791323/+attachment/5186077/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791323 Title: XFS fallocate implementation incorrectly reports ENOSPC Status in linux package in Ubuntu: Confirmed Bug description: When given an offset of 0 and a length, fallocate (man 2 fallocate) reports ENOSPC if the size of the file + the length to be allocated is greater than the available space. Example below using the fallocate command (man 1 fallocate) for simplicity; the issue is with the logic backing the system call. chathaway@bender:~/temp$ fallocate -l 1GB example.img chathaway@bender:~/temp$ mkfs.xfs example.img meta-data=example.imgisize=512agcount=4, agsize=61035 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0, rmapbt=0, reflink=0 data = bsize=4096 blocks=244140, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=855, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 chathaway@bender:~/temp$ sudo modprobe loop chathaway@bender:~/temp$ mkdir mnt chathaway@bender:~/temp$ sudo mount -o loop ./example.img ./mnt/ chathaway@bender:~/temp$ cd mnt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt fallocate: fallocate failed: No space left on device chathaway@bender:~/temp/mnt$ df -h . Filesystem Size Used Avail Use% Mounted on /dev/loop0 951M 766M 185M 81% /home/chathaway/temp/mnt Expected behaviour: because we allocate 768MB starting at offset 0, and have 951MB on the disk, we would expect that the allocation should be fine. Other filesystem behave this way (for example, ext4). Thanks! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chathaway 2608 F pulseaudio /dev/snd/controlC1: chathaway 2608 F pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.04 MachineType: ASUSTeK COMPUTER INC. UX303LN Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: initrd=\EFI\Pop_OS-c80adbe3-92ed-45ea-a314-7e7c694d0161\initrd.img root=UUID=c80adbe3-92ed-45ea-a314-7e7c694d0161 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm docker sudo wireshark _MarkForUpload: True dmi.bios.date: 09/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LN.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LN.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX303LN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791323/+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 1791323] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1791323/+attachment/5186085/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791323 Title: XFS fallocate implementation incorrectly reports ENOSPC Status in linux package in Ubuntu: Confirmed Bug description: When given an offset of 0 and a length, fallocate (man 2 fallocate) reports ENOSPC if the size of the file + the length to be allocated is greater than the available space. Example below using the fallocate command (man 1 fallocate) for simplicity; the issue is with the logic backing the system call. chathaway@bender:~/temp$ fallocate -l 1GB example.img chathaway@bender:~/temp$ mkfs.xfs example.img meta-data=example.imgisize=512agcount=4, agsize=61035 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0, rmapbt=0, reflink=0 data = bsize=4096 blocks=244140, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=855, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 chathaway@bender:~/temp$ sudo modprobe loop chathaway@bender:~/temp$ mkdir mnt chathaway@bender:~/temp$ sudo mount -o loop ./example.img ./mnt/ chathaway@bender:~/temp$ cd mnt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt fallocate: fallocate failed: No space left on device chathaway@bender:~/temp/mnt$ df -h . Filesystem Size Used Avail Use% Mounted on /dev/loop0 951M 766M 185M 81% /home/chathaway/temp/mnt Expected behaviour: because we allocate 768MB starting at offset 0, and have 951MB on the disk, we would expect that the allocation should be fine. Other filesystem behave this way (for example, ext4). Thanks! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chathaway 2608 F pulseaudio /dev/snd/controlC1: chathaway 2608 F pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.04 MachineType: ASUSTeK COMPUTER INC. UX303LN Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: initrd=\EFI\Pop_OS-c80adbe3-92ed-45ea-a314-7e7c694d0161\initrd.img root=UUID=c80adbe3-92ed-45ea-a314-7e7c694d0161 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm docker sudo wireshark _MarkForUpload: True dmi.bios.date: 09/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LN.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LN.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX303LN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791323/+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 1791323] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1791323/+attachment/5186074/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791323 Title: XFS fallocate implementation incorrectly reports ENOSPC Status in linux package in Ubuntu: Confirmed Bug description: When given an offset of 0 and a length, fallocate (man 2 fallocate) reports ENOSPC if the size of the file + the length to be allocated is greater than the available space. Example below using the fallocate command (man 1 fallocate) for simplicity; the issue is with the logic backing the system call. chathaway@bender:~/temp$ fallocate -l 1GB example.img chathaway@bender:~/temp$ mkfs.xfs example.img meta-data=example.imgisize=512agcount=4, agsize=61035 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0, rmapbt=0, reflink=0 data = bsize=4096 blocks=244140, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=855, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 chathaway@bender:~/temp$ sudo modprobe loop chathaway@bender:~/temp$ mkdir mnt chathaway@bender:~/temp$ sudo mount -o loop ./example.img ./mnt/ chathaway@bender:~/temp$ cd mnt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt fallocate: fallocate failed: No space left on device chathaway@bender:~/temp/mnt$ df -h . Filesystem Size Used Avail Use% Mounted on /dev/loop0 951M 766M 185M 81% /home/chathaway/temp/mnt Expected behaviour: because we allocate 768MB starting at offset 0, and have 951MB on the disk, we would expect that the allocation should be fine. Other filesystem behave this way (for example, ext4). Thanks! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chathaway 2608 F pulseaudio /dev/snd/controlC1: chathaway 2608 F pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.04 MachineType: ASUSTeK COMPUTER INC. UX303LN Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: initrd=\EFI\Pop_OS-c80adbe3-92ed-45ea-a314-7e7c694d0161\initrd.img root=UUID=c80adbe3-92ed-45ea-a314-7e7c694d0161 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm docker sudo wireshark _MarkForUpload: True dmi.bios.date: 09/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LN.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LN.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX303LN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791323/+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 1791323] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1791323/+attachment/5186078/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791323 Title: XFS fallocate implementation incorrectly reports ENOSPC Status in linux package in Ubuntu: Confirmed Bug description: When given an offset of 0 and a length, fallocate (man 2 fallocate) reports ENOSPC if the size of the file + the length to be allocated is greater than the available space. Example below using the fallocate command (man 1 fallocate) for simplicity; the issue is with the logic backing the system call. chathaway@bender:~/temp$ fallocate -l 1GB example.img chathaway@bender:~/temp$ mkfs.xfs example.img meta-data=example.imgisize=512agcount=4, agsize=61035 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0, rmapbt=0, reflink=0 data = bsize=4096 blocks=244140, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=855, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 chathaway@bender:~/temp$ sudo modprobe loop chathaway@bender:~/temp$ mkdir mnt chathaway@bender:~/temp$ sudo mount -o loop ./example.img ./mnt/ chathaway@bender:~/temp$ cd mnt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt fallocate: fallocate failed: No space left on device chathaway@bender:~/temp/mnt$ df -h . Filesystem Size Used Avail Use% Mounted on /dev/loop0 951M 766M 185M 81% /home/chathaway/temp/mnt Expected behaviour: because we allocate 768MB starting at offset 0, and have 951MB on the disk, we would expect that the allocation should be fine. Other filesystem behave this way (for example, ext4). Thanks! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chathaway 2608 F pulseaudio /dev/snd/controlC1: chathaway 2608 F pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.04 MachineType: ASUSTeK COMPUTER INC. UX303LN Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: initrd=\EFI\Pop_OS-c80adbe3-92ed-45ea-a314-7e7c694d0161\initrd.img root=UUID=c80adbe3-92ed-45ea-a314-7e7c694d0161 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm docker sudo wireshark _MarkForUpload: True dmi.bios.date: 09/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LN.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LN.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX303LN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791323/+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 1791323] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1791323/+attachment/5186076/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791323 Title: XFS fallocate implementation incorrectly reports ENOSPC Status in linux package in Ubuntu: Confirmed Bug description: When given an offset of 0 and a length, fallocate (man 2 fallocate) reports ENOSPC if the size of the file + the length to be allocated is greater than the available space. Example below using the fallocate command (man 1 fallocate) for simplicity; the issue is with the logic backing the system call. chathaway@bender:~/temp$ fallocate -l 1GB example.img chathaway@bender:~/temp$ mkfs.xfs example.img meta-data=example.imgisize=512agcount=4, agsize=61035 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0, rmapbt=0, reflink=0 data = bsize=4096 blocks=244140, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=855, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 chathaway@bender:~/temp$ sudo modprobe loop chathaway@bender:~/temp$ mkdir mnt chathaway@bender:~/temp$ sudo mount -o loop ./example.img ./mnt/ chathaway@bender:~/temp$ cd mnt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt fallocate: fallocate failed: No space left on device chathaway@bender:~/temp/mnt$ df -h . Filesystem Size Used Avail Use% Mounted on /dev/loop0 951M 766M 185M 81% /home/chathaway/temp/mnt Expected behaviour: because we allocate 768MB starting at offset 0, and have 951MB on the disk, we would expect that the allocation should be fine. Other filesystem behave this way (for example, ext4). Thanks! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chathaway 2608 F pulseaudio /dev/snd/controlC1: chathaway 2608 F pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.04 MachineType: ASUSTeK COMPUTER INC. UX303LN Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: initrd=\EFI\Pop_OS-c80adbe3-92ed-45ea-a314-7e7c694d0161\initrd.img root=UUID=c80adbe3-92ed-45ea-a314-7e7c694d0161 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm docker sudo wireshark _MarkForUpload: True dmi.bios.date: 09/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LN.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LN.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX303LN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791323/+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 1791323] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1791323/+attachment/5186073/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791323 Title: XFS fallocate implementation incorrectly reports ENOSPC Status in linux package in Ubuntu: Confirmed Bug description: When given an offset of 0 and a length, fallocate (man 2 fallocate) reports ENOSPC if the size of the file + the length to be allocated is greater than the available space. Example below using the fallocate command (man 1 fallocate) for simplicity; the issue is with the logic backing the system call. chathaway@bender:~/temp$ fallocate -l 1GB example.img chathaway@bender:~/temp$ mkfs.xfs example.img meta-data=example.imgisize=512agcount=4, agsize=61035 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0, rmapbt=0, reflink=0 data = bsize=4096 blocks=244140, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=855, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 chathaway@bender:~/temp$ sudo modprobe loop chathaway@bender:~/temp$ mkdir mnt chathaway@bender:~/temp$ sudo mount -o loop ./example.img ./mnt/ chathaway@bender:~/temp$ cd mnt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt fallocate: fallocate failed: No space left on device chathaway@bender:~/temp/mnt$ df -h . Filesystem Size Used Avail Use% Mounted on /dev/loop0 951M 766M 185M 81% /home/chathaway/temp/mnt Expected behaviour: because we allocate 768MB starting at offset 0, and have 951MB on the disk, we would expect that the allocation should be fine. Other filesystem behave this way (for example, ext4). Thanks! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chathaway 2608 F pulseaudio /dev/snd/controlC1: chathaway 2608 F pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.04 MachineType: ASUSTeK COMPUTER INC. UX303LN Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: initrd=\EFI\Pop_OS-c80adbe3-92ed-45ea-a314-7e7c694d0161\initrd.img root=UUID=c80adbe3-92ed-45ea-a314-7e7c694d0161 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm docker sudo wireshark _MarkForUpload: True dmi.bios.date: 09/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LN.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LN.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX303LN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791323/+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 1791323] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1791323/+attachment/5186072/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791323 Title: XFS fallocate implementation incorrectly reports ENOSPC Status in linux package in Ubuntu: Confirmed Bug description: When given an offset of 0 and a length, fallocate (man 2 fallocate) reports ENOSPC if the size of the file + the length to be allocated is greater than the available space. Example below using the fallocate command (man 1 fallocate) for simplicity; the issue is with the logic backing the system call. chathaway@bender:~/temp$ fallocate -l 1GB example.img chathaway@bender:~/temp$ mkfs.xfs example.img meta-data=example.imgisize=512agcount=4, agsize=61035 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0, rmapbt=0, reflink=0 data = bsize=4096 blocks=244140, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=855, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 chathaway@bender:~/temp$ sudo modprobe loop chathaway@bender:~/temp$ mkdir mnt chathaway@bender:~/temp$ sudo mount -o loop ./example.img ./mnt/ chathaway@bender:~/temp$ cd mnt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt fallocate: fallocate failed: No space left on device chathaway@bender:~/temp/mnt$ df -h . Filesystem Size Used Avail Use% Mounted on /dev/loop0 951M 766M 185M 81% /home/chathaway/temp/mnt Expected behaviour: because we allocate 768MB starting at offset 0, and have 951MB on the disk, we would expect that the allocation should be fine. Other filesystem behave this way (for example, ext4). Thanks! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chathaway 2608 F pulseaudio /dev/snd/controlC1: chathaway 2608 F pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.04 MachineType: ASUSTeK COMPUTER INC. UX303LN Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: initrd=\EFI\Pop_OS-c80adbe3-92ed-45ea-a314-7e7c694d0161\initrd.img root=UUID=c80adbe3-92ed-45ea-a314-7e7c694d0161 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm docker sudo wireshark _MarkForUpload: True dmi.bios.date: 09/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LN.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LN.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX303LN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791323/+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 1791323] Re: XFS fallocate implementation incorrectly reports ENOSPC
apport information ** Tags added: apport-collected bionic ** Description changed: When given an offset of 0 and a length, fallocate (man 2 fallocate) reports ENOSPC if the size of the file + the length to be allocated is greater than the available space. Example below using the fallocate command (man 1 fallocate) for simplicity; the issue is with the logic backing the system call. chathaway@bender:~/temp$ fallocate -l 1GB example.img chathaway@bender:~/temp$ mkfs.xfs example.img meta-data=example.imgisize=512agcount=4, agsize=61035 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0, rmapbt=0, reflink=0 data = bsize=4096 blocks=244140, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=855, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 chathaway@bender:~/temp$ sudo modprobe loop chathaway@bender:~/temp$ mkdir mnt chathaway@bender:~/temp$ sudo mount -o loop ./example.img ./mnt/ chathaway@bender:~/temp$ cd mnt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt fallocate: fallocate failed: No space left on device chathaway@bender:~/temp/mnt$ df -h . Filesystem Size Used Avail Use% Mounted on /dev/loop0 951M 766M 185M 81% /home/chathaway/temp/mnt Expected behaviour: because we allocate 768MB starting at offset 0, and have 951MB on the disk, we would expect that the allocation should be fine. Other filesystem behave this way (for example, ext4). Thanks! + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.2 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: chathaway 2608 F pulseaudio + /dev/snd/controlC1: chathaway 2608 F pulseaudio + CurrentDesktop: pop:GNOME + DistroRelease: Pop!_OS 18.04 + MachineType: ASUSTeK COMPUTER INC. UX303LN + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: initrd=\EFI\Pop_OS-c80adbe3-92ed-45ea-a314-7e7c694d0161\initrd.img root=UUID=c80adbe3-92ed-45ea-a314-7e7c694d0161 ro quiet loglevel=0 systemd.show_status=false splash + ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-33-generic N/A + linux-backports-modules-4.15.0-33-generic N/A + linux-firmware 1.173.1 + Tags: bionic + Uname: Linux 4.15.0-33-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm docker sudo wireshark + _MarkForUpload: True + dmi.bios.date: 09/01/2014 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: UX303LN.204 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: UX303LN + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: 1.0 + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: ASUSTeK COMPUTER INC. + dmi.chassis.version: 1.0 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LN.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: + dmi.product.family: UX + dmi.product.name: UX303LN + dmi.product.version: 1.0 + dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1791323/+attachment/5186071/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791323 Title: XFS fallocate implementation incorrectly reports ENOSPC Status in linux package in Ubuntu: Confirmed Bug description: When given an offset of 0 and a length, fallocate (man 2 fallocate) reports ENOSPC if the size of the file + the length to be allocated is greater than the available space. Example below using the fallocate command (man 1 fallocate) for simplicity; the issue is with the logic backing the system call. chathaway@bender:~/temp$ fallocate -l 1GB example.img chathaway@bender:~/temp$ mkfs.xfs example.img meta-data=example.imgisize=512agcount=4, agsize=61035 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0, rmapbt=0, reflink=0 data = bsize=4096 blocks=244140, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=855, version=2 =
[Kernel-packages] [Bug 1791323] [NEW] XFS fallocate implementation incorrectly reports ENOSPC
Public bug reported: When given an offset of 0 and a length, fallocate (man 2 fallocate) reports ENOSPC if the size of the file + the length to be allocated is greater than the available space. Example below using the fallocate command (man 1 fallocate) for simplicity; the issue is with the logic backing the system call. chathaway@bender:~/temp$ fallocate -l 1GB example.img chathaway@bender:~/temp$ mkfs.xfs example.img meta-data=example.imgisize=512agcount=4, agsize=61035 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0, rmapbt=0, reflink=0 data = bsize=4096 blocks=244140, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=855, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 chathaway@bender:~/temp$ sudo modprobe loop chathaway@bender:~/temp$ mkdir mnt chathaway@bender:~/temp$ sudo mount -o loop ./example.img ./mnt/ chathaway@bender:~/temp$ cd mnt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt fallocate: fallocate failed: No space left on device chathaway@bender:~/temp/mnt$ df -h . Filesystem Size Used Avail Use% Mounted on /dev/loop0 951M 766M 185M 81% /home/chathaway/temp/mnt Expected behaviour: because we allocate 768MB starting at offset 0, and have 951MB on the disk, we would expect that the allocation should be fine. Other filesystem behave this way (for example, ext4). Thanks! ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: xfs ** Attachment added: "attachments.tar.gz" https://bugs.launchpad.net/bugs/1791323/+attachment/5186057/+files/attachments.tar.gz -- 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/1791323 Title: XFS fallocate implementation incorrectly reports ENOSPC Status in linux package in Ubuntu: New Bug description: When given an offset of 0 and a length, fallocate (man 2 fallocate) reports ENOSPC if the size of the file + the length to be allocated is greater than the available space. Example below using the fallocate command (man 1 fallocate) for simplicity; the issue is with the logic backing the system call. chathaway@bender:~/temp$ fallocate -l 1GB example.img chathaway@bender:~/temp$ mkfs.xfs example.img meta-data=example.imgisize=512agcount=4, agsize=61035 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0, rmapbt=0, reflink=0 data = bsize=4096 blocks=244140, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=855, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 chathaway@bender:~/temp$ sudo modprobe loop chathaway@bender:~/temp$ mkdir mnt chathaway@bender:~/temp$ sudo mount -o loop ./example.img ./mnt/ chathaway@bender:~/temp$ cd mnt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt fallocate: fallocate failed: No space left on device chathaway@bender:~/temp/mnt$ df -h . Filesystem Size Used Avail Use% Mounted on /dev/loop0 951M 766M 185M 81% /home/chathaway/temp/mnt Expected behaviour: because we allocate 768MB starting at offset 0, and have 951MB on the disk, we would expect that the allocation should be fine. Other filesystem behave this way (for example, ext4). Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791323/+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 1779827] Re: failure to boot with linux-image-4.15.0-24-generic
Participating in bug https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1779476 for the last couple of days. Clevo barebook W540 pentium 3805U 1.90G onboard graphics BroadwellGT1 single ssd, intel Wless 3160, only hardware hanging off it is a usb wireless mouse. Had indefinite hang begin with update to Ubuntu-offered *-24 kernel. A fair amount of keyboarding and mouse wiggling (average 90s) is needed to wake the process up again. Holding the SHIFT key speeds up the boot to an acceptable delay. Once into Gnome, networking is also fairly retarded (average 45s) and sometimes needs UI operation for the Net Manager to do its usual auto connect to its secure network. Installing haveged stopped the hang. Network also appears to be more responsive, but this can be masked by the flaky operation of our el-cheapo wireless router. Using a usb dongle which emulates etho appears to deliver much more reliable network start. Booting into *-23 stopped all symptoms - haveged not needed. Booting into the dev channel *-26 returned the hang and added a few display artefacts to the plymouth/Gnome handover process. Zero networking delivered in Gnome, not even a UI for Net Manager. Hanging a portable WD 1TB spinner off the laptop USB3 port returned a good boot time into Gnome with the *-24 kernel without haveged installed. Networking was however delayed variously between 60s and at one boot appeared to need UI input to wake the hardware up to the secure connection already in the Net Manager's list, even though Net Manager could immediately see other networks around the place. Reverting now to *-23 kernel for the week's work. Hope these naive reports were in any way useful. -- 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/1779827 Title: failure to boot with linux-image-4.15.0-24-generic Status in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in The Bionic Beaver: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: This was the last OK then my 18.04 hangs after an update this morning. 07:00 AM CEST Last Ok in boot was Started gnome display manager. dispatcher service .. tem changes.pp link was shut down Tried install lightdm from command line and the response was lastest already installed. Probably it is what is coming after the lastest OK which is to be the error. And here I have lots of guesses.. Any Ideas ? I need to do some work and I may not be waiting long. Search and browsed and now close to give up. Yeah it is a Lenovo. Guys: turn of auto update it is a machine killer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1779827/+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 1779827] Re: failure to boot with linux-image-4.15.0-24-generic
Booting into the *-26 kernel gave a very quick handover to Gnome, but with some kind of badly painted cursor and progress images apparently bleeding through from the plymouth screens. However the deal breaker is that networking isn't enabled at all. Report then is that *-26 kernel is not a workaround or a fix for this machine: Clevo bareboook W540 onboard graphics. haveged is a workaround for getting into Gnome with *-24 kernel but networking is fairly retarded in its delivery to the desktop after Gnome starts - averaging 30s. Booting into *-23 is the optimum boot speed and delivers networking in good time. -- 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/1779827 Title: failure to boot with linux-image-4.15.0-24-generic Status in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in The Bionic Beaver: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: This was the last OK then my 18.04 hangs after an update this morning. 07:00 AM CEST Last Ok in boot was Started gnome display manager. dispatcher service .. tem changes.pp link was shut down Tried install lightdm from command line and the response was lastest already installed. Probably it is what is coming after the lastest OK which is to be the error. And here I have lots of guesses.. Any Ideas ? I need to do some work and I may not be waiting long. Search and browsed and now close to give up. Yeah it is a Lenovo. Guys: turn of auto update it is a machine killer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1779827/+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 1779476] Re: Boot process hangs indefinitely. Never finishes.
Further to the above on wireless start, booting into *.23 kernel, Bionic loses all the retarding symptoms for Gnome start and for wireless network start. -- 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/1779476 Title: Boot process hangs indefinitely. Never finishes. Status in gdm3 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in plymouth package in Ubuntu: Incomplete Status in plymouth package in Debian: Fix Released Bug description: After update of gdm and kernel gdm3 no longer enables graphics. What happens: = With and without: WaylandEnable=false in /etc/gdm3/custom.conf gdm3 does not switch to graphics. In both cases I case the X process running (Xwayland or Xorg) but no vt has it. lightdm does work, but barely. It takes up to a minute to get to the login screen. What I expected to happen: == gdm3 switching to graphics in ~20 after boot like pre-update. Release: $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 $ apt-cache policy kernel-common gdm3 lightdm xorg xwayland kernel-common: Installed: (none) Candidate: 13.018+nmu1 Version table: 13.018+nmu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic/universe i386 Packages gdm3: Installed: 3.28.2-0ubuntu1.3 Candidate: 3.28.2-0ubuntu1.3 Version table: *** 3.28.2-0ubuntu1.3 500 500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.28.2-0ubuntu1.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 3.28.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status xorg: Installed: 1:7.7+19ubuntu7 Candidate: 1:7.7+19ubuntu7 Version table: *** 1:7.7+19ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status xwayland: Installed: 2:1.19.6-1ubuntu4 Candidate: 2:1.19.6-1ubuntu4 Version table: *** 2:1.19.6-1ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Attaching journalctl -b. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-27 (673 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) NonfreeKernelModules: wl Package: gdm3 3.28.2-0ubuntu1.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Tags: bionic package-from-proposed Uname: Linux 4.15.0-24-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-27 (674 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) NonfreeKernelModules: wl Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Tags: bionic package-from-proposed Uname: Linux 4.15.0-24-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.gdm3.custom.conf: [modified] mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1779476/+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 1779476] Re: Boot process hangs indefinitely. Never finishes.
Installing plymouth 0.9.3-3 over the distro 0.9.3-1 had no effect on this system - amd64 - either. Steps taken with dpkg for a hash-checked .deb were: Preparing to unpack .../plymouth_0.9.3-3_amd64.deb ... Unpacking plymouth (0.9.3-3) over (0.9.3-1ubuntu7) ... Setting up plymouth (0.9.3-3) ... update-initramfs: deferring update (trigger activated) update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Processing triggers for systemd (237-3ubuntu10) ... Processing triggers for ureadahead (0.100.0-20) ... ureadahead will be reprofiled on next reboot Processing triggers for man-db (2.8.3-2) ... Processing triggers for initramfs-tools (0.130ubuntu3.1) ... update-initramfs: Generating /boot/initrd.img-4.15.0-24-generic Apt complained about some redundancies, which I deleted. After uninstalling haveged, the system hung indefinitely once more at various advices of processes waiting, depending on the 3 restarts I tried. GDM featured variously, as did utmp. Not knowing much at that level, I can only report that plymouth 0.9.3-3 doesn't fix the hang I reported upthread. Nor does it change the lack of either keyboard or usb mouse/touchpad access for at least 90s of that hang. Another symptom, just noticed because of all the restarts, is that wireless networking gets a significant delay before kicking in after the handover to Gnome - about 30s. With the 16.04 I dual boot this machine to, wireless networking is ready to go almost as soon as the UI is up. Reinstalling haveged returns the good handover to Gnome - about 20s, but wireless networking stays slow to begin its work. Note that uninstalling plymouth 0.9.3-3 returns the listing of 0.9.3-1 to the system, but a couple of the Ubuntu display dependencies needed also to be reinstalled to get back a coherent recognisable splash screen progress. Probably time for me to get familiar with using the shell at startup. That UI looks like a real curate's egg and this is a significant bug (or set of bugs maybe). -- 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/1779476 Title: Boot process hangs indefinitely. Never finishes. Status in gdm3 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in plymouth package in Ubuntu: Incomplete Status in plymouth package in Debian: Fix Released Bug description: After update of gdm and kernel gdm3 no longer enables graphics. What happens: = With and without: WaylandEnable=false in /etc/gdm3/custom.conf gdm3 does not switch to graphics. In both cases I case the X process running (Xwayland or Xorg) but no vt has it. lightdm does work, but barely. It takes up to a minute to get to the login screen. What I expected to happen: == gdm3 switching to graphics in ~20 after boot like pre-update. Release: $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 $ apt-cache policy kernel-common gdm3 lightdm xorg xwayland kernel-common: Installed: (none) Candidate: 13.018+nmu1 Version table: 13.018+nmu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic/universe i386 Packages gdm3: Installed: 3.28.2-0ubuntu1.3 Candidate: 3.28.2-0ubuntu1.3 Version table: *** 3.28.2-0ubuntu1.3 500 500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.28.2-0ubuntu1.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 3.28.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status xorg: Installed: 1:7.7+19ubuntu7 Candidate: 1:7.7+19ubuntu7 Version table: *** 1:7.7+19ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status xwayland: Installed: 2:1.19.6-1ubuntu4 Candidate: 2:1.19.6-1ubuntu4 Version table: *** 2:1.19.6-1ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Attaching journalctl -b. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-27 (673 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (
[Kernel-packages] [Bug 1779476] Re: Ubuntu 18.04: gdm3 does not switch to graphics after update
I can report a very similar experience after the update to kernel *-24. The difference with my machine - a barebook Clevo packaged by Pioneer Computers Australia - is that no keyboarding, usb mouse, or touchpad use reproducably reduces the hang time by plymouth to less than an average 90seconds. The appearance of the cursor is fairly unpredictable within those times and at a rare few boots, CTRL+ALT F2 sent the system into a wobbly dance between the shell and plymouth. Holding SHIFT during boot however does produce an acceptable and reproducable boot into Xorg time of about 15s. Installing and enabling haveged in sysctrl has the same effect as holding the SHIFT key. Booting into the *-23 kernel removes the hang and any of the wobbly moves between shell and plymouth. As requested, after uninstalling haveged and booting to *-24 kernel, both using the SHIFT workaround and the longer playing with keyboard and pointers, issuing the command: lsof | grep /dev/random listed nothing. Interesting that with sudo prefixed, the command complains: 'lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete.' While it doesn't complain when the user themself issues the command. Is this a bug too, or is it logical that the virtual gnome file system is indeed run per user and not by root? Neither forms of the command list anything. -- 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/1779476 Title: Ubuntu 18.04: gdm3 does not switch to graphics after update Status in gdm3 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: After update of gdm and kernel gdm3 no longer enables graphics. What happens: = With and without: WaylandEnable=false in /etc/gdm3/custom.conf gdm3 does not switch to graphics. In both cases I case the X process running (Xwayland or Xorg) but no vt has it. lightdm does work, but barely. It takes up to a minute to get to the login screen. What I expected to happen: == gdm3 switching to graphics in ~20 after boot like pre-update. Release: $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 $ apt-cache policy kernel-common gdm3 lightdm xorg xwayland kernel-common: Installed: (none) Candidate: 13.018+nmu1 Version table: 13.018+nmu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic/universe i386 Packages gdm3: Installed: 3.28.2-0ubuntu1.3 Candidate: 3.28.2-0ubuntu1.3 Version table: *** 3.28.2-0ubuntu1.3 500 500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.28.2-0ubuntu1.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 3.28.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status xorg: Installed: 1:7.7+19ubuntu7 Candidate: 1:7.7+19ubuntu7 Version table: *** 1:7.7+19ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status xwayland: Installed: 2:1.19.6-1ubuntu4 Candidate: 2:1.19.6-1ubuntu4 Version table: *** 2:1.19.6-1ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Attaching journalctl -b. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-27 (673 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) NonfreeKernelModules: wl Package: gdm3 3.28.2-0ubuntu1.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Tags: bionic package-from-proposed Uname: Linux 4.15.0-24-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-27 (674 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) NonfreeKernelModules: wl Package: linux Pack
[Kernel-packages] [Bug 1730958] Re: nuvoton-cir not working after boot
I've just tried with more recent kernel, but issue still exists. Kernel: linux-image-4.16.0-041600rc7-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/1730958 Title: nuvoton-cir not working after boot Status in linux package in Ubuntu: Confirmed Bug description: Current setup/failing setup: Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 4.13.0-17.20-generic 4.13.8 Ubuntu 17.10, 4.13.0-17-generic Nuvoton w836x7hg Infrared Remote Transceiver Zotac ID42 Working setup: Ubuntu 17.10, 4.4.8-040408-generic I'm not able to get the remote working after a normal reboot (using 4.13 kernel) It does actually after a suspend and wake-up, and do a echo 'auto' to resources. Please find snapshot of dmesg below: [ 14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input7 [ 14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 14.468526] nuvoton-cir 00:0a: driver has been successfully loaded modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input13 [ 66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 66.232240] nuvoton-cir 00:0a: driver has been successfully loaded suspend/resume [ 105.890769] nuvoton-cir 00:0a: disabled [ 106.651982] nuvoton-cir 00:0a: activated modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input17 [ 138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 138.552256] nuvoton-cir 00:0a: driver has been successfully loaded In order to get the device working I need the following in this order: * suspend/resume * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6 InstallationDate: Installed on 2014-04-01 (1317 days ago) InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 (20130820) MachineType: ZOTAC ZBOX-ID42-BE NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago) UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B201P010 dmi.board.asset.tag: NA dmi.board.name: ZBOX-ID42-BE dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: NA dmi.chassis.type: 3 dmi.chassis.vendor: NA dmi.chassis.version: NA dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA: dmi.product.family: NA dmi.product.name: ZBOX-ID42-BE dmi.product.version: XX dmi.sys.vendor: ZOTAC To manage notifications about this bug go
[Kernel-packages] [Bug 1754979] [NEW] zfs-dkms 0.6.5.6-0ubuntu19: zfs kernel module failed to build
Public bug reported: Happened on a simple software update. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: zfs-dkms 0.6.5.6-0ubuntu19 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 DKMSBuildLog: DKMS make.log for zfs-0.6.5.6 for kernel 4.13.0-36-generic (x86_64) Sun Mar 11 09:58:57 MDT 2018 make: *** No targets specified and no makefile found. Stop. DKMSKernelVersion: 4.13.0-36-generic Date: Sun Mar 11 09:59:00 2018 InstallationDate: Installed on 2017-12-16 (84 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) PackageVersion: 0.6.5.6-0ubuntu19 RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: zfs-linux Title: zfs-dkms 0.6.5.6-0ubuntu19: zfs kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1754979 Title: zfs-dkms 0.6.5.6-0ubuntu19: zfs kernel module failed to build Status in zfs-linux package in Ubuntu: New Bug description: Happened on a simple software update. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: zfs-dkms 0.6.5.6-0ubuntu19 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 DKMSBuildLog: DKMS make.log for zfs-0.6.5.6 for kernel 4.13.0-36-generic (x86_64) Sun Mar 11 09:58:57 MDT 2018 make: *** No targets specified and no makefile found. Stop. DKMSKernelVersion: 4.13.0-36-generic Date: Sun Mar 11 09:59:00 2018 InstallationDate: Installed on 2017-12-16 (84 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) PackageVersion: 0.6.5.6-0ubuntu19 RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: zfs-linux Title: zfs-dkms 0.6.5.6-0ubuntu19: zfs kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1754979/+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 1730958] Re: nuvoton-cir not working after boot
Should I file an upstream kernel bug or is that automatically done? Any parts missing or anything I can try? I’ve noticed it on two different systems and really strange that there are no #metoos -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730958 Title: nuvoton-cir not working after boot Status in linux package in Ubuntu: Confirmed Bug description: Current setup/failing setup: Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 4.13.0-17.20-generic 4.13.8 Ubuntu 17.10, 4.13.0-17-generic Nuvoton w836x7hg Infrared Remote Transceiver Zotac ID42 Working setup: Ubuntu 17.10, 4.4.8-040408-generic I'm not able to get the remote working after a normal reboot (using 4.13 kernel) It does actually after a suspend and wake-up, and do a echo 'auto' to resources. Please find snapshot of dmesg below: [ 14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input7 [ 14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 14.468526] nuvoton-cir 00:0a: driver has been successfully loaded modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input13 [ 66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 66.232240] nuvoton-cir 00:0a: driver has been successfully loaded suspend/resume [ 105.890769] nuvoton-cir 00:0a: disabled [ 106.651982] nuvoton-cir 00:0a: activated modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input17 [ 138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 138.552256] nuvoton-cir 00:0a: driver has been successfully loaded In order to get the device working I need the following in this order: * suspend/resume * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6 InstallationDate: Installed on 2014-04-01 (1317 days ago) InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 (20130820) MachineType: ZOTAC ZBOX-ID42-BE NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago) UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B201P010 dmi.board.asset.tag: NA dmi.board.name: ZBOX-ID42-BE dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: NA dmi.chassis.type: 3 dmi.chassis.vendor: NA dmi.chassis.version: NA dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA: dmi.product.family: NA dmi.product.name: ZBOX-ID42-BE
[Kernel-packages] [Bug 1742698] [NEW] zfs-dkms 0.6.5.6-0ubuntu18: zfs kernel module failed to build
Public bug reported: Ubuntu MATE 16.04 standard distro. It looks like there is a common defect across many versions that has not been addressed. If they are trying to fix this, whatever they've been doing is not effective. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: zfs-dkms 0.6.5.6-0ubuntu18 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 DKMSBuildLog: DKMS make.log for zfs-0.6.5.6 for kernel 4.13.0-26-generic (x86_64) Thu Jan 11 06:40:09 MST 2018 make: *** No targets specified and no makefile found. Stop. DKMSKernelVersion: 4.13.0-26-generic Date: Thu Jan 11 06:40:12 2018 InstallationDate: Installed on 2017-12-16 (25 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) PackageVersion: 0.6.5.6-0ubuntu18 RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: zfs-linux Title: zfs-dkms 0.6.5.6-0ubuntu18: zfs kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1742698 Title: zfs-dkms 0.6.5.6-0ubuntu18: zfs kernel module failed to build Status in zfs-linux package in Ubuntu: New Bug description: Ubuntu MATE 16.04 standard distro. It looks like there is a common defect across many versions that has not been addressed. If they are trying to fix this, whatever they've been doing is not effective. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: zfs-dkms 0.6.5.6-0ubuntu18 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 DKMSBuildLog: DKMS make.log for zfs-0.6.5.6 for kernel 4.13.0-26-generic (x86_64) Thu Jan 11 06:40:09 MST 2018 make: *** No targets specified and no makefile found. Stop. DKMSKernelVersion: 4.13.0-26-generic Date: Thu Jan 11 06:40:12 2018 InstallationDate: Installed on 2017-12-16 (25 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) PackageVersion: 0.6.5.6-0ubuntu18 RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: zfs-linux Title: zfs-dkms 0.6.5.6-0ubuntu18: zfs kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1742698/+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 1742323] Re: Meltdown Update Kernel doesnt boot
*** This bug is a duplicate of bug 1741934 *** https://bugs.launchpad.net/bugs/1741934 How can I find 4.4.0-109? I have tried to update with Ubuntu Software and 'about this computer' from the settings icon in the taskbar. Both methods tell me that my system is up to date and I can't find 109 on any of the Xenial repos. Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742323 Title: Meltdown Update Kernel doesnt boot Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: Using a Dell Poweredge T20 and Ubuntu 16.04 with the 4.4 Kernel. Just got the Meltdown update to kernel linux-image-4.4.0-108-generic but this doesnt boot at all. It just hangs after grub. There is no logs from syslog or such. SysReq Keys dont work neither. The last kernel linux-image-4.4.0-104-generic still boots fine. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-104-generic 4.4.0-104.127 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-104-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Date: Wed Jan 10 01:36:01 2018 HibernationDevice: RESUME=UUID=9b654b0f-96ef-49f0-bfd8-ad7907cb7b99 InstallationDate: Installed on 2017-05-17 (237 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge T20 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic.efi.signed root=UUID=9edb2ffb-791e-4988-b3a9-7ce73227802c ro RelatedPackageVersions: linux-restricted-modules-4.4.0-104-generic N/A linux-backports-modules-4.4.0-104-generic N/A linux-firmware 1.157.14 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0VD5HY dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/11/2017:svnDellInc.:pnPowerEdgeT20:pvr00:rvnDellInc.:rn0VD5HY:rvrA07:cvnDellInc.:ct6:cvr: dmi.product.name: PowerEdge T20 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742323/+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 1730958] Re: nuvoton-cir not working after boot
not sure if it helps, but please /proc/ioports below. There is a difference between kernel 4.13 (not working) and kernel 4.5.7 (working): kernel 4.5.7 (working): 0220-022e : nuvoton-cir 02e0-02ee : nuvoton-cir kernel 4.13 before suspend and before module reload (not working): 03e0-03ee : nuvoton-cir 0a20-0a2e : nuvoton-cir-wake kernel 4.13 after suspend and module reload (working): 0220-022e : nuvoton-cir-wake 02e0-02ee : nuvoton-cir Maybe resource allocation is causing issues 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/1730958 Title: nuvoton-cir not working after boot Status in linux package in Ubuntu: Confirmed Bug description: Current setup/failing setup: Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 4.13.0-17.20-generic 4.13.8 Ubuntu 17.10, 4.13.0-17-generic Nuvoton w836x7hg Infrared Remote Transceiver Zotac ID42 Working setup: Ubuntu 17.10, 4.4.8-040408-generic I'm not able to get the remote working after a normal reboot (using 4.13 kernel) It does actually after a suspend and wake-up, and do a echo 'auto' to resources. Please find snapshot of dmesg below: [ 14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input7 [ 14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 14.468526] nuvoton-cir 00:0a: driver has been successfully loaded modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input13 [ 66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 66.232240] nuvoton-cir 00:0a: driver has been successfully loaded suspend/resume [ 105.890769] nuvoton-cir 00:0a: disabled [ 106.651982] nuvoton-cir 00:0a: activated modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input17 [ 138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 138.552256] nuvoton-cir 00:0a: driver has been successfully loaded In order to get the device working I need the following in this order: * suspend/resume * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6 InstallationDate: Installed on 2014-04-01 (1317 days ago) InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 (20130820) MachineType: ZOTAC ZBOX-ID42-BE NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago) UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B201P010 dmi.board.asset.tag: NA dmi.board.name: ZBOX-ID42-BE dmi.board.vendor: ZOTAC dmi.board.version: XX dm
[Kernel-packages] [Bug 1730958] Re: nuvoton-cir not working after boot
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730958 Title: nuvoton-cir not working after boot Status in linux package in Ubuntu: Confirmed Bug description: Current setup/failing setup: Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 4.13.0-17.20-generic 4.13.8 Ubuntu 17.10, 4.13.0-17-generic Nuvoton w836x7hg Infrared Remote Transceiver Zotac ID42 Working setup: Ubuntu 17.10, 4.4.8-040408-generic I'm not able to get the remote working after a normal reboot (using 4.13 kernel) It does actually after a suspend and wake-up, and do a echo 'auto' to resources. Please find snapshot of dmesg below: [ 14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input7 [ 14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 14.468526] nuvoton-cir 00:0a: driver has been successfully loaded modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input13 [ 66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 66.232240] nuvoton-cir 00:0a: driver has been successfully loaded suspend/resume [ 105.890769] nuvoton-cir 00:0a: disabled [ 106.651982] nuvoton-cir 00:0a: activated modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input17 [ 138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 138.552256] nuvoton-cir 00:0a: driver has been successfully loaded In order to get the device working I need the following in this order: * suspend/resume * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6 InstallationDate: Installed on 2014-04-01 (1317 days ago) InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 (20130820) MachineType: ZOTAC ZBOX-ID42-BE NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago) UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B201P010 dmi.board.asset.tag: NA dmi.board.name: ZBOX-ID42-BE dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: NA dmi.chassis.type: 3 dmi.chassis.vendor: NA dmi.chassis.version: NA dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA: dmi.product.family: NA dmi.product.name: ZBOX-ID42-BE dmi.product.version: XX dmi.sys.vendor: ZOTAC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+so
[Kernel-packages] [Bug 1730958] Re: nuvoton-cir not working after boot
277edbabf6fece057b14fb6db5e3a34e00f42f42 is the first bad commit Hope this helps. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730958 Title: nuvoton-cir not working after boot Status in linux package in Ubuntu: Incomplete Bug description: Current setup/failing setup: Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 4.13.0-17.20-generic 4.13.8 Ubuntu 17.10, 4.13.0-17-generic Nuvoton w836x7hg Infrared Remote Transceiver Zotac ID42 Working setup: Ubuntu 17.10, 4.4.8-040408-generic I'm not able to get the remote working after a normal reboot (using 4.13 kernel) It does actually after a suspend and wake-up, and do a echo 'auto' to resources. Please find snapshot of dmesg below: [ 14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input7 [ 14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 14.468526] nuvoton-cir 00:0a: driver has been successfully loaded modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input13 [ 66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 66.232240] nuvoton-cir 00:0a: driver has been successfully loaded suspend/resume [ 105.890769] nuvoton-cir 00:0a: disabled [ 106.651982] nuvoton-cir 00:0a: activated modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input17 [ 138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 138.552256] nuvoton-cir 00:0a: driver has been successfully loaded In order to get the device working I need the following in this order: * suspend/resume * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6 InstallationDate: Installed on 2014-04-01 (1317 days ago) InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 (20130820) MachineType: ZOTAC ZBOX-ID42-BE NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago) UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B201P010 dmi.board.asset.tag: NA dmi.board.name: ZBOX-ID42-BE dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: NA dmi.chassis.type: 3 dmi.chassis.vendor: NA dmi.chassis.version: NA dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA: dmi.product.family: NA dmi.product.name: ZBOX-ID42-BE dmi.product.version: XX dmi.sys.vendor: ZOTAC To manage notifications about this bug go to: https://bugs.launchpad
[Kernel-packages] [Bug 1730958] Re: nuvoton-cir not working after boot
Thanks Joseph! Progress is made with bisect. Only 9 steps left, but takes time with compile and testing. Hope to get there soon. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730958 Title: nuvoton-cir not working after boot Status in linux package in Ubuntu: Incomplete Bug description: Current setup/failing setup: Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 4.13.0-17.20-generic 4.13.8 Ubuntu 17.10, 4.13.0-17-generic Nuvoton w836x7hg Infrared Remote Transceiver Zotac ID42 Working setup: Ubuntu 17.10, 4.4.8-040408-generic I'm not able to get the remote working after a normal reboot (using 4.13 kernel) It does actually after a suspend and wake-up, and do a echo 'auto' to resources. Please find snapshot of dmesg below: [ 14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input7 [ 14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 14.468526] nuvoton-cir 00:0a: driver has been successfully loaded modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input13 [ 66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 66.232240] nuvoton-cir 00:0a: driver has been successfully loaded suspend/resume [ 105.890769] nuvoton-cir 00:0a: disabled [ 106.651982] nuvoton-cir 00:0a: activated modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input17 [ 138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 138.552256] nuvoton-cir 00:0a: driver has been successfully loaded In order to get the device working I need the following in this order: * suspend/resume * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6 InstallationDate: Installed on 2014-04-01 (1317 days ago) InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 (20130820) MachineType: ZOTAC ZBOX-ID42-BE NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago) UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B201P010 dmi.board.asset.tag: NA dmi.board.name: ZBOX-ID42-BE dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: NA dmi.chassis.type: 3 dmi.chassis.vendor: NA dmi.chassis.version: NA dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA: dmi.product.family: NA dmi.product.name: ZBOX-ID42-BE dmi.product.version: XX dmi.sys.vendor: ZOTAC To manage notificatio
[Kernel-packages] [Bug 1730958] Re: nuvoton-cir not working after boot
Kernel 4.14 (latest) does NOT work correctly Kernel 4.5.7 does work correctly Kernel 4.6.0 does NOT work correctly I need to do bisecting between 4.5.7 and 4.6.0 somehow. Let me figure out how to do it (or give some recommendation please). ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730958 Title: nuvoton-cir not working after boot Status in linux package in Ubuntu: Incomplete Bug description: Current setup/failing setup: Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 4.13.0-17.20-generic 4.13.8 Ubuntu 17.10, 4.13.0-17-generic Nuvoton w836x7hg Infrared Remote Transceiver Zotac ID42 Working setup: Ubuntu 17.10, 4.4.8-040408-generic I'm not able to get the remote working after a normal reboot (using 4.13 kernel) It does actually after a suspend and wake-up, and do a echo 'auto' to resources. Please find snapshot of dmesg below: [ 14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input7 [ 14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 14.468526] nuvoton-cir 00:0a: driver has been successfully loaded modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input13 [ 66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 66.232240] nuvoton-cir 00:0a: driver has been successfully loaded suspend/resume [ 105.890769] nuvoton-cir 00:0a: disabled [ 106.651982] nuvoton-cir 00:0a: activated modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input17 [ 138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 138.552256] nuvoton-cir 00:0a: driver has been successfully loaded In order to get the device working I need the following in this order: * suspend/resume * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6 InstallationDate: Installed on 2014-04-01 (1317 days ago) InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 (20130820) MachineType: ZOTAC ZBOX-ID42-BE NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago) UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B201P010 dmi.board.asset.tag: NA dmi.board.name: ZBOX-ID42-BE dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: NA dmi.chassis.type: 3 dmi.chassis.vendor: NA dmi.chassis.version: NA dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE
[Kernel-packages] [Bug 1730958] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1730958/+attachment/5005915/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730958 Title: nuvoton-cir not working after boot Status in linux package in Ubuntu: Confirmed Bug description: Current setup/failing setup: Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 4.13.0-17.20-generic 4.13.8 Ubuntu 17.10, 4.13.0-17-generic Nuvoton w836x7hg Infrared Remote Transceiver Zotac ID42 Working setup: Ubuntu 17.10, 4.4.8-040408-generic I'm not able to get the remote working after a normal reboot (using 4.13 kernel) It does actually after a suspend and wake-up, and do a echo 'auto' to resources. Please find snapshot of dmesg below: [ 14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input7 [ 14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 14.468526] nuvoton-cir 00:0a: driver has been successfully loaded modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input13 [ 66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 66.232240] nuvoton-cir 00:0a: driver has been successfully loaded suspend/resume [ 105.890769] nuvoton-cir 00:0a: disabled [ 106.651982] nuvoton-cir 00:0a: activated modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input17 [ 138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 138.552256] nuvoton-cir 00:0a: driver has been successfully loaded In order to get the device working I need the following in this order: * suspend/resume * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6 InstallationDate: Installed on 2014-04-01 (1317 days ago) InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 (20130820) MachineType: ZOTAC ZBOX-ID42-BE NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago) UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B201P010 dmi.board.asset.tag: NA dmi.board.name: ZBOX-ID42-BE dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: NA dmi.chassis.type: 3 dmi.chassis.vendor: NA dmi.chassis.version: NA dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA: dmi.product.family: NA dmi.product.name: ZB
[Kernel-packages] [Bug 1730958] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1730958/+attachment/5005911/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730958 Title: nuvoton-cir not working after boot Status in linux package in Ubuntu: Confirmed Bug description: Current setup/failing setup: Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 4.13.0-17.20-generic 4.13.8 Ubuntu 17.10, 4.13.0-17-generic Nuvoton w836x7hg Infrared Remote Transceiver Zotac ID42 Working setup: Ubuntu 17.10, 4.4.8-040408-generic I'm not able to get the remote working after a normal reboot (using 4.13 kernel) It does actually after a suspend and wake-up, and do a echo 'auto' to resources. Please find snapshot of dmesg below: [ 14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input7 [ 14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 14.468526] nuvoton-cir 00:0a: driver has been successfully loaded modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input13 [ 66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 66.232240] nuvoton-cir 00:0a: driver has been successfully loaded suspend/resume [ 105.890769] nuvoton-cir 00:0a: disabled [ 106.651982] nuvoton-cir 00:0a: activated modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input17 [ 138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 138.552256] nuvoton-cir 00:0a: driver has been successfully loaded In order to get the device working I need the following in this order: * suspend/resume * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6 InstallationDate: Installed on 2014-04-01 (1317 days ago) InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 (20130820) MachineType: ZOTAC ZBOX-ID42-BE NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago) UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B201P010 dmi.board.asset.tag: NA dmi.board.name: ZBOX-ID42-BE dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: NA dmi.chassis.type: 3 dmi.chassis.vendor: NA dmi.chassis.version: NA dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA: dmi.product.family: NA dmi.product.name: ZBOX-ID42-BE dmi.product.version: XX dmi.sys.vendor: ZOTAC
[Kernel-packages] [Bug 1730958] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1730958/+attachment/5005914/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730958 Title: nuvoton-cir not working after boot Status in linux package in Ubuntu: Confirmed Bug description: Current setup/failing setup: Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 4.13.0-17.20-generic 4.13.8 Ubuntu 17.10, 4.13.0-17-generic Nuvoton w836x7hg Infrared Remote Transceiver Zotac ID42 Working setup: Ubuntu 17.10, 4.4.8-040408-generic I'm not able to get the remote working after a normal reboot (using 4.13 kernel) It does actually after a suspend and wake-up, and do a echo 'auto' to resources. Please find snapshot of dmesg below: [ 14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input7 [ 14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 14.468526] nuvoton-cir 00:0a: driver has been successfully loaded modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input13 [ 66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 66.232240] nuvoton-cir 00:0a: driver has been successfully loaded suspend/resume [ 105.890769] nuvoton-cir 00:0a: disabled [ 106.651982] nuvoton-cir 00:0a: activated modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input17 [ 138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 138.552256] nuvoton-cir 00:0a: driver has been successfully loaded In order to get the device working I need the following in this order: * suspend/resume * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6 InstallationDate: Installed on 2014-04-01 (1317 days ago) InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 (20130820) MachineType: ZOTAC ZBOX-ID42-BE NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago) UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B201P010 dmi.board.asset.tag: NA dmi.board.name: ZBOX-ID42-BE dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: NA dmi.chassis.type: 3 dmi.chassis.vendor: NA dmi.chassis.version: NA dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA: dmi.product.family: NA dmi.product.name: ZBOX-ID42-BE dmi.product.version: XX dmi.sys.vendor: ZOTAC To manage notific
[Kernel-packages] [Bug 1730958] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1730958/+attachment/5005913/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730958 Title: nuvoton-cir not working after boot Status in linux package in Ubuntu: Confirmed Bug description: Current setup/failing setup: Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 4.13.0-17.20-generic 4.13.8 Ubuntu 17.10, 4.13.0-17-generic Nuvoton w836x7hg Infrared Remote Transceiver Zotac ID42 Working setup: Ubuntu 17.10, 4.4.8-040408-generic I'm not able to get the remote working after a normal reboot (using 4.13 kernel) It does actually after a suspend and wake-up, and do a echo 'auto' to resources. Please find snapshot of dmesg below: [ 14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input7 [ 14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 14.468526] nuvoton-cir 00:0a: driver has been successfully loaded modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input13 [ 66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 66.232240] nuvoton-cir 00:0a: driver has been successfully loaded suspend/resume [ 105.890769] nuvoton-cir 00:0a: disabled [ 106.651982] nuvoton-cir 00:0a: activated modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input17 [ 138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 138.552256] nuvoton-cir 00:0a: driver has been successfully loaded In order to get the device working I need the following in this order: * suspend/resume * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6 InstallationDate: Installed on 2014-04-01 (1317 days ago) InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 (20130820) MachineType: ZOTAC ZBOX-ID42-BE NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago) UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B201P010 dmi.board.asset.tag: NA dmi.board.name: ZBOX-ID42-BE dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: NA dmi.chassis.type: 3 dmi.chassis.vendor: NA dmi.chassis.version: NA dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA: dmi.product.family: NA dmi.product.name: ZBOX-ID42-BE dmi.product.version: XX dmi.sys.vendor: ZOTAC To manage notific
[Kernel-packages] [Bug 1730958] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1730958/+attachment/5005912/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730958 Title: nuvoton-cir not working after boot Status in linux package in Ubuntu: Confirmed Bug description: Current setup/failing setup: Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 4.13.0-17.20-generic 4.13.8 Ubuntu 17.10, 4.13.0-17-generic Nuvoton w836x7hg Infrared Remote Transceiver Zotac ID42 Working setup: Ubuntu 17.10, 4.4.8-040408-generic I'm not able to get the remote working after a normal reboot (using 4.13 kernel) It does actually after a suspend and wake-up, and do a echo 'auto' to resources. Please find snapshot of dmesg below: [ 14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input7 [ 14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 14.468526] nuvoton-cir 00:0a: driver has been successfully loaded modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input13 [ 66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 66.232240] nuvoton-cir 00:0a: driver has been successfully loaded suspend/resume [ 105.890769] nuvoton-cir 00:0a: disabled [ 106.651982] nuvoton-cir 00:0a: activated modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input17 [ 138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 138.552256] nuvoton-cir 00:0a: driver has been successfully loaded In order to get the device working I need the following in this order: * suspend/resume * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6 InstallationDate: Installed on 2014-04-01 (1317 days ago) InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 (20130820) MachineType: ZOTAC ZBOX-ID42-BE NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago) UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B201P010 dmi.board.asset.tag: NA dmi.board.name: ZBOX-ID42-BE dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: NA dmi.chassis.type: 3 dmi.chassis.vendor: NA dmi.chassis.version: NA dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA: dmi.product.family: NA dmi.product.name: ZBOX-ID42-BE dmi.product.version: XX dmi.sys.vendor: ZOTAC To man
[Kernel-packages] [Bug 1730958] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1730958/+attachment/5005910/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730958 Title: nuvoton-cir not working after boot Status in linux package in Ubuntu: Confirmed Bug description: Current setup/failing setup: Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 4.13.0-17.20-generic 4.13.8 Ubuntu 17.10, 4.13.0-17-generic Nuvoton w836x7hg Infrared Remote Transceiver Zotac ID42 Working setup: Ubuntu 17.10, 4.4.8-040408-generic I'm not able to get the remote working after a normal reboot (using 4.13 kernel) It does actually after a suspend and wake-up, and do a echo 'auto' to resources. Please find snapshot of dmesg below: [ 14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input7 [ 14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 14.468526] nuvoton-cir 00:0a: driver has been successfully loaded modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input13 [ 66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 66.232240] nuvoton-cir 00:0a: driver has been successfully loaded suspend/resume [ 105.890769] nuvoton-cir 00:0a: disabled [ 106.651982] nuvoton-cir 00:0a: activated modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input17 [ 138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 138.552256] nuvoton-cir 00:0a: driver has been successfully loaded In order to get the device working I need the following in this order: * suspend/resume * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6 InstallationDate: Installed on 2014-04-01 (1317 days ago) InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 (20130820) MachineType: ZOTAC ZBOX-ID42-BE NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago) UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B201P010 dmi.board.asset.tag: NA dmi.board.name: ZBOX-ID42-BE dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: NA dmi.chassis.type: 3 dmi.chassis.vendor: NA dmi.chassis.version: NA dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA: dmi.product.family: NA dmi.product.name: ZBOX-ID42-BE dmi.product.version: XX dmi.sys.vendor: ZOTAC To man
[Kernel-packages] [Bug 1730958] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1730958/+attachment/5005908/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730958 Title: nuvoton-cir not working after boot Status in linux package in Ubuntu: Confirmed Bug description: Current setup/failing setup: Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 4.13.0-17.20-generic 4.13.8 Ubuntu 17.10, 4.13.0-17-generic Nuvoton w836x7hg Infrared Remote Transceiver Zotac ID42 Working setup: Ubuntu 17.10, 4.4.8-040408-generic I'm not able to get the remote working after a normal reboot (using 4.13 kernel) It does actually after a suspend and wake-up, and do a echo 'auto' to resources. Please find snapshot of dmesg below: [ 14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input7 [ 14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 14.468526] nuvoton-cir 00:0a: driver has been successfully loaded modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input13 [ 66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 66.232240] nuvoton-cir 00:0a: driver has been successfully loaded suspend/resume [ 105.890769] nuvoton-cir 00:0a: disabled [ 106.651982] nuvoton-cir 00:0a: activated modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input17 [ 138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 138.552256] nuvoton-cir 00:0a: driver has been successfully loaded In order to get the device working I need the following in this order: * suspend/resume * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6 InstallationDate: Installed on 2014-04-01 (1317 days ago) InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 (20130820) MachineType: ZOTAC ZBOX-ID42-BE NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago) UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B201P010 dmi.board.asset.tag: NA dmi.board.name: ZBOX-ID42-BE dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: NA dmi.chassis.type: 3 dmi.chassis.vendor: NA dmi.chassis.version: NA dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA: dmi.product.family: NA dmi.product.name: ZBOX-ID42-BE dmi.product.version: XX dmi.sys.vendor: ZOTAC To man
[Kernel-packages] [Bug 1730958] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1730958/+attachment/5005909/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730958 Title: nuvoton-cir not working after boot Status in linux package in Ubuntu: Confirmed Bug description: Current setup/failing setup: Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 4.13.0-17.20-generic 4.13.8 Ubuntu 17.10, 4.13.0-17-generic Nuvoton w836x7hg Infrared Remote Transceiver Zotac ID42 Working setup: Ubuntu 17.10, 4.4.8-040408-generic I'm not able to get the remote working after a normal reboot (using 4.13 kernel) It does actually after a suspend and wake-up, and do a echo 'auto' to resources. Please find snapshot of dmesg below: [ 14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input7 [ 14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 14.468526] nuvoton-cir 00:0a: driver has been successfully loaded modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input13 [ 66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 66.232240] nuvoton-cir 00:0a: driver has been successfully loaded suspend/resume [ 105.890769] nuvoton-cir 00:0a: disabled [ 106.651982] nuvoton-cir 00:0a: activated modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input17 [ 138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 138.552256] nuvoton-cir 00:0a: driver has been successfully loaded In order to get the device working I need the following in this order: * suspend/resume * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6 InstallationDate: Installed on 2014-04-01 (1317 days ago) InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 (20130820) MachineType: ZOTAC ZBOX-ID42-BE NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago) UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B201P010 dmi.board.asset.tag: NA dmi.board.name: ZBOX-ID42-BE dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: NA dmi.chassis.type: 3 dmi.chassis.vendor: NA dmi.chassis.version: NA dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA: dmi.product.family: NA dmi.product.name: ZBOX-ID42-BE dmi.product.version: XX dmi.sys.vendor:
[Kernel-packages] [Bug 1730958] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1730958/+attachment/5005906/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730958 Title: nuvoton-cir not working after boot Status in linux package in Ubuntu: Confirmed Bug description: Current setup/failing setup: Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 4.13.0-17.20-generic 4.13.8 Ubuntu 17.10, 4.13.0-17-generic Nuvoton w836x7hg Infrared Remote Transceiver Zotac ID42 Working setup: Ubuntu 17.10, 4.4.8-040408-generic I'm not able to get the remote working after a normal reboot (using 4.13 kernel) It does actually after a suspend and wake-up, and do a echo 'auto' to resources. Please find snapshot of dmesg below: [ 14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input7 [ 14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 14.468526] nuvoton-cir 00:0a: driver has been successfully loaded modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input13 [ 66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 66.232240] nuvoton-cir 00:0a: driver has been successfully loaded suspend/resume [ 105.890769] nuvoton-cir 00:0a: disabled [ 106.651982] nuvoton-cir 00:0a: activated modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input17 [ 138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 138.552256] nuvoton-cir 00:0a: driver has been successfully loaded In order to get the device working I need the following in this order: * suspend/resume * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6 InstallationDate: Installed on 2014-04-01 (1317 days ago) InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 (20130820) MachineType: ZOTAC ZBOX-ID42-BE NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago) UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B201P010 dmi.board.asset.tag: NA dmi.board.name: ZBOX-ID42-BE dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: NA dmi.chassis.type: 3 dmi.chassis.vendor: NA dmi.chassis.version: NA dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA: dmi.product.family: NA dmi.product.name: ZBOX-ID42-BE dmi.product.version: XX dmi.sys.vendor: ZOTAC To manage notificat
[Kernel-packages] [Bug 1730958] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1730958/+attachment/5005905/+files/JournalErrors.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730958 Title: nuvoton-cir not working after boot Status in linux package in Ubuntu: Confirmed Bug description: Current setup/failing setup: Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 4.13.0-17.20-generic 4.13.8 Ubuntu 17.10, 4.13.0-17-generic Nuvoton w836x7hg Infrared Remote Transceiver Zotac ID42 Working setup: Ubuntu 17.10, 4.4.8-040408-generic I'm not able to get the remote working after a normal reboot (using 4.13 kernel) It does actually after a suspend and wake-up, and do a echo 'auto' to resources. Please find snapshot of dmesg below: [ 14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input7 [ 14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 14.468526] nuvoton-cir 00:0a: driver has been successfully loaded modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input13 [ 66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 66.232240] nuvoton-cir 00:0a: driver has been successfully loaded suspend/resume [ 105.890769] nuvoton-cir 00:0a: disabled [ 106.651982] nuvoton-cir 00:0a: activated modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input17 [ 138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 138.552256] nuvoton-cir 00:0a: driver has been successfully loaded In order to get the device working I need the following in this order: * suspend/resume * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6 InstallationDate: Installed on 2014-04-01 (1317 days ago) InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 (20130820) MachineType: ZOTAC ZBOX-ID42-BE NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago) UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B201P010 dmi.board.asset.tag: NA dmi.board.name: ZBOX-ID42-BE dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: NA dmi.chassis.type: 3 dmi.chassis.vendor: NA dmi.chassis.version: NA dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA: dmi.product.family: NA dmi.product.name: ZBOX-ID42-BE dmi.product.version: XX dmi.sys.vendor: ZOTAC To
[Kernel-packages] [Bug 1730958] Re: nuvoton-cir not working after boot
apport information ** Tags added: apport-collected ** Description changed: Current setup/failing setup: Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 4.13.0-17.20-generic 4.13.8 Ubuntu 17.10, 4.13.0-17-generic Nuvoton w836x7hg Infrared Remote Transceiver Zotac ID42 Working setup: Ubuntu 17.10, 4.4.8-040408-generic I'm not able to get the remote working after a normal reboot (using 4.13 kernel) It does actually after a suspend and wake-up, and do a echo 'auto' to resources. Please find snapshot of dmesg below: [ 14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input7 [ 14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 14.468526] nuvoton-cir 00:0a: driver has been successfully loaded modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input13 [ 66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 66.232240] nuvoton-cir 00:0a: driver has been successfully loaded suspend/resume [ 105.890769] nuvoton-cir 00:0a: disabled [ 106.651982] nuvoton-cir 00:0a: activated modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input17 [ 138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 138.552256] nuvoton-cir 00:0a: driver has been successfully loaded In order to get the device working I need the following in this order: * suspend/resume * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources + --- + ApportVersion: 2.20.7-0ubuntu3.1 + Architecture: amd64 + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 17.10 + HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6 + InstallationDate: Installed on 2014-04-01 (1317 days ago) + InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 (20130820) + MachineType: ZOTAC ZBOX-ID42-BE + NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 VESA VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7 + ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-4.13.0-17-generic N/A + linux-backports-modules-4.13.0-17-generic N/A + linux-firmware 1.169 + Tags: artful + Uname: Linux 4.13.0-17-generic x86_64 + UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago) + UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev sambashare sudo video + _MarkForUpload: True + dmi.bios.date: 05/03/2013 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: B201P010 + dmi.board.asset.tag: NA + dmi.board.name: ZBOX-ID42-BE + dmi.board.vendor: ZOTAC + dmi.board.version: XX + dmi.chassis.asset.tag: NA + dmi.chassis.type: 3 + dmi.chassis.vendor: NA + dmi.chassis.version: NA + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA: + dmi.product.family: NA + dmi.product.name: ZBOX-ID42-BE + dmi.product.version: XX + dmi.sys.vendor: ZOTAC ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1730958/+attachment/5005901/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730958 Title: nuvoton-cir not working after boo
[Kernel-packages] [Bug 1730958] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1730958/+attachment/5005902/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730958 Title: nuvoton-cir not working after boot Status in linux package in Ubuntu: Confirmed Bug description: Current setup/failing setup: Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 4.13.0-17.20-generic 4.13.8 Ubuntu 17.10, 4.13.0-17-generic Nuvoton w836x7hg Infrared Remote Transceiver Zotac ID42 Working setup: Ubuntu 17.10, 4.4.8-040408-generic I'm not able to get the remote working after a normal reboot (using 4.13 kernel) It does actually after a suspend and wake-up, and do a echo 'auto' to resources. Please find snapshot of dmesg below: [ 14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input7 [ 14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 14.468526] nuvoton-cir 00:0a: driver has been successfully loaded modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input13 [ 66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 66.232240] nuvoton-cir 00:0a: driver has been successfully loaded suspend/resume [ 105.890769] nuvoton-cir 00:0a: disabled [ 106.651982] nuvoton-cir 00:0a: activated modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input17 [ 138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 138.552256] nuvoton-cir 00:0a: driver has been successfully loaded In order to get the device working I need the following in this order: * suspend/resume * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6 InstallationDate: Installed on 2014-04-01 (1317 days ago) InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 (20130820) MachineType: ZOTAC ZBOX-ID42-BE NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago) UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B201P010 dmi.board.asset.tag: NA dmi.board.name: ZBOX-ID42-BE dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: NA dmi.chassis.type: 3 dmi.chassis.vendor: NA dmi.chassis.version: NA dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA: dmi.product.family: NA dmi.product.name: ZBOX-ID42-BE dmi.product.version: XX dmi.sys.vendor: ZOTAC To manage notificatio
[Kernel-packages] [Bug 1730958] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1730958/+attachment/5005907/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730958 Title: nuvoton-cir not working after boot Status in linux package in Ubuntu: Confirmed Bug description: Current setup/failing setup: Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 4.13.0-17.20-generic 4.13.8 Ubuntu 17.10, 4.13.0-17-generic Nuvoton w836x7hg Infrared Remote Transceiver Zotac ID42 Working setup: Ubuntu 17.10, 4.4.8-040408-generic I'm not able to get the remote working after a normal reboot (using 4.13 kernel) It does actually after a suspend and wake-up, and do a echo 'auto' to resources. Please find snapshot of dmesg below: [ 14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input7 [ 14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 14.468526] nuvoton-cir 00:0a: driver has been successfully loaded modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input13 [ 66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 66.232240] nuvoton-cir 00:0a: driver has been successfully loaded suspend/resume [ 105.890769] nuvoton-cir 00:0a: disabled [ 106.651982] nuvoton-cir 00:0a: activated modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input17 [ 138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 138.552256] nuvoton-cir 00:0a: driver has been successfully loaded In order to get the device working I need the following in this order: * suspend/resume * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6 InstallationDate: Installed on 2014-04-01 (1317 days ago) InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 (20130820) MachineType: ZOTAC ZBOX-ID42-BE NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago) UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B201P010 dmi.board.asset.tag: NA dmi.board.name: ZBOX-ID42-BE dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: NA dmi.chassis.type: 3 dmi.chassis.vendor: NA dmi.chassis.version: NA dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA: dmi.product.family: NA dmi.product.name: ZBOX-ID42-BE dmi.product.version: XX dmi.sys.vendor: ZOTAC To manage notificat
[Kernel-packages] [Bug 1730958] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1730958/+attachment/5005904/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730958 Title: nuvoton-cir not working after boot Status in linux package in Ubuntu: Confirmed Bug description: Current setup/failing setup: Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 4.13.0-17.20-generic 4.13.8 Ubuntu 17.10, 4.13.0-17-generic Nuvoton w836x7hg Infrared Remote Transceiver Zotac ID42 Working setup: Ubuntu 17.10, 4.4.8-040408-generic I'm not able to get the remote working after a normal reboot (using 4.13 kernel) It does actually after a suspend and wake-up, and do a echo 'auto' to resources. Please find snapshot of dmesg below: [ 14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input7 [ 14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 14.468526] nuvoton-cir 00:0a: driver has been successfully loaded modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input13 [ 66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 66.232240] nuvoton-cir 00:0a: driver has been successfully loaded suspend/resume [ 105.890769] nuvoton-cir 00:0a: disabled [ 106.651982] nuvoton-cir 00:0a: activated modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input17 [ 138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 138.552256] nuvoton-cir 00:0a: driver has been successfully loaded In order to get the device working I need the following in this order: * suspend/resume * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6 InstallationDate: Installed on 2014-04-01 (1317 days ago) InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 (20130820) MachineType: ZOTAC ZBOX-ID42-BE NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago) UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B201P010 dmi.board.asset.tag: NA dmi.board.name: ZBOX-ID42-BE dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: NA dmi.chassis.type: 3 dmi.chassis.vendor: NA dmi.chassis.version: NA dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA: dmi.product.family: NA dmi.product.name: ZBOX-ID42-BE dmi.product.version: XX dmi.sys.vendor: ZOTAC To manage no
[Kernel-packages] [Bug 1730958] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1730958/+attachment/5005903/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730958 Title: nuvoton-cir not working after boot Status in linux package in Ubuntu: Confirmed Bug description: Current setup/failing setup: Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 4.13.0-17.20-generic 4.13.8 Ubuntu 17.10, 4.13.0-17-generic Nuvoton w836x7hg Infrared Remote Transceiver Zotac ID42 Working setup: Ubuntu 17.10, 4.4.8-040408-generic I'm not able to get the remote working after a normal reboot (using 4.13 kernel) It does actually after a suspend and wake-up, and do a echo 'auto' to resources. Please find snapshot of dmesg below: [ 14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input7 [ 14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 14.468526] nuvoton-cir 00:0a: driver has been successfully loaded modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input13 [ 66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 66.232240] nuvoton-cir 00:0a: driver has been successfully loaded suspend/resume [ 105.890769] nuvoton-cir 00:0a: disabled [ 106.651982] nuvoton-cir 00:0a: activated modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input17 [ 138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 138.552256] nuvoton-cir 00:0a: driver has been successfully loaded In order to get the device working I need the following in this order: * suspend/resume * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6 InstallationDate: Installed on 2014-04-01 (1317 days ago) InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 (20130820) MachineType: ZOTAC ZBOX-ID42-BE NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago) UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B201P010 dmi.board.asset.tag: NA dmi.board.name: ZBOX-ID42-BE dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: NA dmi.chassis.type: 3 dmi.chassis.vendor: NA dmi.chassis.version: NA dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA: dmi.product.family: NA dmi.product.name: ZBOX-ID42-BE dmi.product.version: XX dmi.sys.vendor: ZOTAC To m
[Kernel-packages] [Bug 1730958] Re: nuvoton-cir not working after boot
** Attachment added: "lspci log" https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1730958/+attachment/5005891/+files/lspci -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1730958 Title: nuvoton-cir not working after boot Status in linux package in Ubuntu: New Bug description: Current setup/failing setup: Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 4.13.0-17.20-generic 4.13.8 Ubuntu 17.10, 4.13.0-17-generic Nuvoton w836x7hg Infrared Remote Transceiver Zotac ID42 Working setup: Ubuntu 17.10, 4.4.8-040408-generic I'm not able to get the remote working after a normal reboot (using 4.13 kernel) It does actually after a suspend and wake-up, and do a echo 'auto' to resources. Please find snapshot of dmesg below: [ 14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input7 [ 14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 14.468526] nuvoton-cir 00:0a: driver has been successfully loaded modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input13 [ 66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 66.232240] nuvoton-cir 00:0a: driver has been successfully loaded suspend/resume [ 105.890769] nuvoton-cir 00:0a: disabled [ 106.651982] nuvoton-cir 00:0a: activated modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input17 [ 138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 138.552256] nuvoton-cir 00:0a: driver has been successfully loaded In order to get the device working I need the following in this order: * suspend/resume * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730958/+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 1730958] [NEW] nuvoton-cir not working after boot
Public bug reported: Current setup/failing setup: Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 4.13.0-17.20-generic 4.13.8 Ubuntu 17.10, 4.13.0-17-generic Nuvoton w836x7hg Infrared Remote Transceiver Zotac ID42 Working setup: Ubuntu 17.10, 4.4.8-040408-generic I'm not able to get the remote working after a normal reboot (using 4.13 kernel) It does actually after a suspend and wake-up, and do a echo 'auto' to resources. Please find snapshot of dmesg below: [ 14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input7 [ 14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 14.468526] nuvoton-cir 00:0a: driver has been successfully loaded modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input13 [ 66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 66.232240] nuvoton-cir 00:0a: driver has been successfully loaded suspend/resume [ 105.890769] nuvoton-cir 00:0a: disabled [ 106.651982] nuvoton-cir 00:0a: activated modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input17 [ 138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 138.552256] nuvoton-cir 00:0a: driver has been successfully loaded In order to get the device working I need the following in this order: * suspend/resume * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources ** 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-meta in Ubuntu. https://bugs.launchpad.net/bugs/1730958 Title: nuvoton-cir not working after boot Status in linux package in Ubuntu: New Bug description: Current setup/failing setup: Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 4.13.0-17.20-generic 4.13.8 Ubuntu 17.10, 4.13.0-17-generic Nuvoton w836x7hg Infrared Remote Transceiver Zotac ID42 Working setup: Ubuntu 17.10, 4.4.8-040408-generic I'm not able to get the remote working after a normal reboot (using 4.13 kernel) It does actually after a suspend and wake-up, and do a echo 'auto' to resources. Please find snapshot of dmesg below: [ 14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input7 [ 14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 14.468526] nuvoton-cir 00:0a: driver has been successfully loaded modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input13 [ 66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 66.232240] nuvoton-cir 00:0a: driver has been successfully loaded suspend/resume [ 105.890769] nuvoton-cir 00:0a: disabled [ 106.651982] nuvoton-cir 00:0a: activated modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input17 [ 138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 138.552256] nuvo
[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free
Is there any way for a non-kernel-dev type to see exactly which resource unregister_netdevice is waiting for? (Or does it only keep track of usage count?) -- 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/1711407 Title: unregister_netdevice: waiting for lo to become free Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: New Status in linux source package in Xenial: New Status in linux source package in Zesty: New Status in linux source package in Artful: Confirmed Status in linux source package in bb-series: New Bug description: This is a "continuation" of bug 1403152, as that bug has been marked "fix released" and recent reports of failure may (or may not) be a new bug. Any further reports of the problem should please be reported here instead of that bug. -- [Impact] When shutting down and starting containers the container network namespace may experience a dst reference counting leak which results in this message repeated in the logs: unregister_netdevice: waiting for lo to become free. Usage count = 1 This can cause issues when trying to create net network namespace and thus block a user from creating new containers. [Test Case] See comment 16, reproducer provided at https://github.com/fho/docker- samba-loop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407/+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 1711407] Re: unregister_netdevice: waiting for lo to become free
We're seeing this on our build servers. These are VMWare virtual machines which run docker containers in privileged mode. Inside the containers are Jenkins agents and a build environment. Part of the build process uses unshare to create these namespaces: ipc uts mount pid net. If you have any questions about this arrangement, I can try to provide more detail and maybe example code. The kernel is 4.4.0-79-generic x86_64. We are using docker 17.05.0-ce. In one case, the whole VM hung when this was encountered. Are there any workarounds for 16.04 users beyond rebooting the host? -- 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/1711407 Title: unregister_netdevice: waiting for lo to become free Status in linux package in Ubuntu: Confirmed Bug description: This is a "continuation" of bug 1403152, as that bug has been marked "fix released" and recent reports of failure may (or may not) be a new bug. Any further reports of the problem should please be reported here instead of that bug. -- [Impact] When shutting down and starting containers the container network namespace may experience a dst reference counting leak which results in this message repeated in the logs: unregister_netdevice: waiting for lo to become free. Usage count = 1 This can cause issues when trying to create net network namespace and thus block a user from creating new containers. [Test Case] See comment 16, reproducer provided at https://github.com/fho/docker- samba-loop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407/+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 1691556] Re: Can't send audio to Amazon Echo via Bluetooth
** Also affects: bluez Importance: Undecided Status: New ** No longer affects: bluez -- 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/1691556 Title: Can't send audio to Amazon Echo via Bluetooth Status in bluez package in Ubuntu: Confirmed Bug description: Pairing and coupling to Amazon Echo works, but no sound is heard. I believe the issue is related to the fact that Amazon Echo is paired as a handset (i.e., speaker + microphone) rather than just as a speaker. I believe the critical error is found in a dmesg line such as: Feb 28 10:59:05 n1 bluetoothd[1025]: a2dp-source profile connect failed for 50:F5:DA:A6:3F:EA: Device or resource busy as I describe in the askubuntu.com discussion at: https://askubuntu.com/questions/871630/cant-send-audio-to-amazon-echo- via-bluetooth I have clarified there my thinking and the steps I've taken thus far on this issue, which includes trying debug bluetooth per the Ubuntu wiki page which describes how to do so. This is probably an upstream issue, as Mike H-R has commented there that the problem also occurs on ArchLinux. I and a few others would like to get this resolved, and I am happy to help (I'm a software developer). However, at this point, I'm not sure how to proceed without some assistance. I suppose I could report it to Debain, but I've only ever used Debain vis a vis Ubuntu, so I thought it best to start here. Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 17 22:27:59 2017 InstallationDate: Installed on 2015-12-26 (507 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) InterestingModules: rfcomm bnep btusb bluetooth ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic root=UUID=5950fbba-cde1-49ac-a918-04e517894c57 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to xenial on 2017-02-28 (78 days ago) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Intel Corporation dmi.bios.version: RYBDWi35.86A.0362.2017.0118.0940 dmi.board.name: NUC5i5RYB dmi.board.vendor: Intel Corporation dmi.board.version: H40999-504 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0362.2017.0118.0940:bd01/18/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr: hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: DC:53:60:97:55:17 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:13547334 acl:58 sco:0 events:1935087 errors:0 TX bytes:1652407651 acl:1934967 sco:0 commands:76 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2015-12-29T07:24:08.439240 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1691556/+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 1699386] [NEW] package linux-image-4.4.0-81-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
*** This bug is a duplicate of bug 1699108 *** https://bugs.launchpad.net/bugs/1699108 Public bug reported: System just hung for hours (10) trying to install the package as specified in the summary box. I tried to do this install via the Ubuntu Software app (not via apt-get). The graph showing how far the install went stopped moving when it got to the first 'l' in "Installing." This has happened previously. Canceling and rebooting and then recoing the package install doesn't seem to help. Ubuntu 16.04 LTS o(64-bit) n a Dell E4310 laptop with 7.Gb memory available. Thanks :) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-81-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: charles1756 F pulseaudio Date: Tue Jun 20 20:23:22 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=bf53ffee-03b9-4c92-a18d-94db88c0e284 InstallationDate: Installed on 2017-02-04 (136 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Latitude E4310 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-79-generic root=UUID=800019f4-1881-4f83-a2aa-98d2de9bcc3a ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.11 SourcePackage: linux Title: package linux-image-4.4.0-81-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 04HKYP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/05/2013:svnDellInc.:pnLatitudeE4310:pvr0001:rvnDellInc.:rn04HKYP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E4310 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- 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/1699386 Title: package linux-image-4.4.0-81-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: New Bug description: System just hung for hours (10) trying to install the package as specified in the summary box. I tried to do this install via the Ubuntu Software app (not via apt-get). The graph showing how far the install went stopped moving when it got to the first 'l' in "Installing." This has happened previously. Canceling and rebooting and then recoing the package install doesn't seem to help. Ubuntu 16.04 LTS o(64-bit) n a Dell E4310 laptop with 7.Gb memory available. Thanks :) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-81-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: charles1756 F pulseaudio Date: Tue Jun 20 20:23:22 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=bf53ffee-03b9-4c92-a18d-94db88c0e284 InstallationDate: Installed on 2017-02-04 (136 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Latitude E4310 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-79-generic root=UUID=800019f4-1881-4f83-a2aa-98d2de9bcc3a ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.11 SourcePackage: linux Title: package linux-image-4.4.0-81-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 04HKYP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor:
Re: [Kernel-packages] [Bug 1698966] Status changed to Confirmed
What should I do? - Original Message - From: "Joseph Salisbury" To: coyl...@comcast.net Sent: Monday, June 19, 2017 6:30:12 PM Subject: [Bug 1698966] Status changed to Confirmed This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1698966 Title: package linux-image-4.4.0-80-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Confirmed Bug description: Not sure what happened ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-80-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: wayne 1627 F pulseaudio Date: Tue Jun 13 16:35:27 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=cd31b069-7591-4edf-a470-23cf396be76b InstallationDate: Installed on 2017-02-12 (127 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: lo no wireless extensions. enp0s7 no wireless extensions. Lsusb: Bus 001 Device 004: ID 0bda:0158 Realtek Semiconductor Corp. USB 2.0 multicard reader Bus 001 Device 003: ID 0930:6545 Toshiba Corp. Kingston DataTraveler 102/2.0 / HEMA Flash Drive 2 GB / PNY Attache 4GB Stick Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: HP-Pavilion NY469AA-ABA s5123w ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-79-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.11 RfKill: SourcePackage: linux Title: package linux-image-4.4.0-80-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2009 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.38 dmi.board.name: NARRA5 dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 5.00 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.38:bd03/20/2009:svnHP-Pavilion:pnNY469AA-ABAs5123w:pvr:rvnPEGATRONCORPORATION:rnNARRA5:rvr5.00:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: NY469AA-ABA s5123w dmi.sys.vendor: HP-Pavilion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1698966/+subscriptions -- 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/1698966 Title: package linux-image-4.4.0-80-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Confirmed Bug description: Not sure what happened ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-80-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wayne 1627 F pulseaudio Date: Tue Jun 13 16:35:27 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=cd31b069-7591-4edf-a470-23cf396be76b InstallationDate: Installed on 2017-02-12 (127 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: lono wireless extensions. enp0s7no wireless extensions. Lsusb: Bus 001 Device 004: ID 0bda:0158 Realtek Semiconductor Corp. USB 2.0 multicard reader Bus 001 Device 003: ID 0930:6545 Toshiba Corp. Kingston DataTraveler 102/2.0 / HEMA Flash Drive 2 GB / PNY Attache 4GB Stick Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: HP-Pavilion NY469AA-ABA s5123w ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-79-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash PulseList: E
[Kernel-packages] [Bug 1698966] [NEW] package linux-image-4.4.0-80-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
Public bug reported: Not sure what happened ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-80-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wayne 1627 F pulseaudio Date: Tue Jun 13 16:35:27 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=cd31b069-7591-4edf-a470-23cf396be76b InstallationDate: Installed on 2017-02-12 (127 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: lono wireless extensions. enp0s7no wireless extensions. Lsusb: Bus 001 Device 004: ID 0bda:0158 Realtek Semiconductor Corp. USB 2.0 multicard reader Bus 001 Device 003: ID 0930:6545 Toshiba Corp. Kingston DataTraveler 102/2.0 / HEMA Flash Drive 2 GB / PNY Attache 4GB Stick Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: HP-Pavilion NY469AA-ABA s5123w ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-79-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.11 RfKill: SourcePackage: linux Title: package linux-image-4.4.0-80-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2009 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.38 dmi.board.name: NARRA5 dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 5.00 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.38:bd03/20/2009:svnHP-Pavilion:pnNY469AA-ABAs5123w:pvr:rvnPEGATRONCORPORATION:rnNARRA5:rvr5.00:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: NY469AA-ABA s5123w dmi.sys.vendor: HP-Pavilion ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- 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/1698966 Title: package linux-image-4.4.0-80-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: New Bug description: Not sure what happened ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-80-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wayne 1627 F pulseaudio Date: Tue Jun 13 16:35:27 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=cd31b069-7591-4edf-a470-23cf396be76b InstallationDate: Installed on 2017-02-12 (127 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: lono wireless extensions. enp0s7no wireless extensions. Lsusb: Bus 001 Device 004: ID 0bda:0158 Realtek Semiconductor Corp. USB 2.0 multicard reader Bus 001 Device 003: ID 0930:6545 Toshiba Corp. Kingston DataTraveler 102/2.0 / HEMA Flash Drive 2 GB / PNY Attache 4GB Stick Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: HP-Pavilion NY469AA-ABA s5123w ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-79-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.11 RfKill: SourcePackage: linux Title: package linux-image-4.4.0-80-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2009 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.38 dmi.board.name: NARRA5 dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 5.00 dmi.chassis.
