from:"Curtis"

Linux kernel v4.4.0-117-generic (v4.4.114) works okay and 'kaslr' option
can be used again.

** 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/1748936

Title:
  kASLR: unable to boot Linux v4.4.0-113.136 - v4.4.0-115.139 kernels
  ("Spectre & Meltdown" patches.)

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Hello.

  It seems, that 'kaslr' option is responsible for issues with system
  booting. The latest working kernel is v4.4.0-112.135. Every next
  release: v4.4.0-113.136 and v4.4.0-115.139 are unable to boot if
  'kaslr' option is in use etc. Everything is described in my previous
  bug report (please see 1.), but I've decided to create a new one,
  because it seems, that some of the "Spectre & Meltdown" patches are
  not compatible with kASLR and are responsible for this regressions.

  Thanks, best regards.

  [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748710

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748936/+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 1748936] Re: kASLR: unable to boot Linux v4.4.0-113.136 - v4.4.0-115.139 kernels ("Spectre & Meltdown" patches.)

Hello. It seems, that everything is okay now and 'kaslr' option is
working again. After update Linux kernel to the v4.4.0-117-generic
(v4.4.114) version, system boots normally. So, some of the patches (see
1.) fixed this issue.

Thanks, best regards.
_
1.
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/commit/?id=fc74a5c4a98418105b4b246b935e3be90d6a635c

--
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/1748936

Title:
kASLR: unable to boot Linux v4.4.0-113.136 - v4.4.0-115.139 kernels
("Spectre & Meltdown" patches.)

Status in linux package in Ubuntu:
Fix Released

Bug description:
Hello.

It seems, that 'kaslr' option is responsible for issues with system
booting. The latest working kernel is v4.4.0-112.135. Every next
release: v4.4.0-113.136 and v4.4.0-115.139 are unable to boot if
'kaslr' option is in use etc. Everything is described in my previous
bug report (please see 1.), but I've decided to create a new one,
because it seems, that some of the "Spectre & Meltdown" patches are
not compatible with kASLR and are responsible for this regressions.

Thanks, best regards.

[1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748710

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748936/+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 1748710] Re: Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1 built-in shell (initramfs).

Hello.

I apologize for not testing the latest v4.16 kernel, but I've decided to
wait for an update to the v4.4 kernel used in "Xenial". And it seems,
that everything is okay now and 'kaslr' option is working again. After
update Linux kernel to the v4.4.0-117-generic (v4.4.114) version, system
boots normally. I've done some tests:

● boot system via GRUB (add 'kaslr' option and press 'CTRL + X')
● edit '/etc/default/grub' file and add 'kaslr' option to the
'GRUB_CMDLINE_LINUX_DEFAULT='

Everything is fine, system starts normally etc. There is no problem, as
I've described in my post #4. So, some of the patches (see 1.) fixed
this issue.

Thanks, best regards.
_
1.
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/commit/?id=fc74a5c4a98418105b4b246b935e3be90d6a635c

** Tags added: kernel-fixed-upstream

** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed

** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => Confirmed

--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1748710

Title:
Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1
built-in shell (initramfs).

Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Xenial:
Confirmed

Bug description:
Hello.

On Thu Feb 8, Linux kernel for Ubuntu 16.04.3 LTS has been updated to
the 4.4.0-113.136 version (xenial-proposed). However, after reboot,
plymouth freezes during start, and keys on an USB keyboard were in-
active. After several seconds, the BusyBox shell screen appeared. It
looks this way:

,--
| BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
| Enter 'help' for a list of built-in commands.
|
| (initramfs) _
`--

Unfortunately, the USB keyboard does not work and does not respond.
The only way to solve this issue is a "hard reset" and in GRUB menu
choosing an earlier kernel, which is linux 4.4.0-112.135. Now,
everything works okay.

Proposed update to the Linux 4.4.0-113.136 contains many new updates
(please see 1.) It's an i386/x86_32 architecture, which does not
contain PTI yet, right? I'm asking, because mentioned -proposed
updates contains a couple of PTI-related patches and bugs in PTI can
cause a few different signatures of crashes etc. For example:

→ Crashes in early boot, especially around CPU bringup. Bugs in the
trampoline code or mappings cause these.
→ Userspace segfaults early in boot, sometimes manifesting as mount(8)
failing to mount the rootfs. These have tended to be TLB invalidation issues.
Usually invalidating the wrong PCID, or otherwise missing an invalidation.

NOTE: if it's about PCID, which is mentioned in a second point, there
is one patch in -proposed update: "x86/mm/32: Move
setup_clear_cpu_cap(X86_FEATURE_PCID) earlier". Maybe that's is the
cause of a boot failure? There are no errors in log files, such as
'/var/log/syslog' or '/var/log/kern.log'. However, it's a Celeron, "E"
series. So, I don't know if mentioned patches are good for this type
of processor etc.? Especially on i386/x86_32 architecture.

● UPDATE/WARNING: It seems, that 'kaslr' option is responsible for
this issue. After booting the latest v4.4.0-115.139 kernel, I've had
the same problems as described above. However, after removing 'kaslr'
option from a command line via GRUB menu, system started normally etc.
The latest, working kernel with 'kaslr' option is v4.4.0-112.135.
According to all of this I think, that 'kaslr' is not compatible with
some "Spectre & Meltdown" mitigation patches and fixes etc.

✗ Release ('/proc/version_signature'): Ubuntu 4.4.0-112.135-generic 4.4.98
✗ Architecture: i386/x86_32
✗ PCI ('lspci -vnvn'): 00:0a.0 PCI bridge [0604]: NVIDIA Corporation MCP73
PCI Express bridge [10de:056d] (rev a1) (prog-if 01 [Subtractive decode])
Capabilities: [b8] Subsystem: Gigabyte Technology Co., Ltd MCP73 PCI Express
bridge [1458:026f]

Thanks, regards.

1. https://lists.ubuntu.com/archives/xenial-
changes/2018-February/020108.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748710/+subscriptions

[Kernel-packages] [Bug 1751021] Re: retpoline abi files are empty on i386

Hello.

Retpoline file, is not empty now. After update Linux kernel to the
v4.4.0.117.123 (v4.4.114) version in 16.04 LTS Release (i386/x86_32
architecture), '/boot/retpoline-4.4.0-117-generic' file contains some
data etc. (2,0K size). Previous files (see post #4) are empty, of
course.

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/1751021

Title:
  retpoline abi files are empty on i386

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  The .retpoline files in the current abi are actually blank.
  This is due to incorrect handling in retpoline-extract.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751021/+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 1748710] Re: Linux 4.4.0-113.136 (i386/x86_32): failed to boot when 'kaslr' option is in use.

** Summary changed:

- Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1 
built-in shell (initramfs).
+ Linux 4.4.0-113.136 (i386/x86_32): failed to boot when 'kaslr' option is in 
use.

-- 
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/1748710

Title:
  Linux 4.4.0-113.136 (i386/x86_32): failed to boot when 'kaslr' option
  is in use.

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  Hello.

  On Thu Feb 8, Linux kernel for Ubuntu 16.04.3 LTS has been updated to
  the 4.4.0-113.136 version (xenial-proposed). However, after reboot,
  plymouth freezes during start, and keys on an USB keyboard were in-
  active. After several seconds, the BusyBox shell screen appeared. It
  looks this way:

  ,--
  | BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
  | Enter 'help' for a list of built-in commands.
  |
  | (initramfs) _ 
  `--

  Unfortunately, the USB keyboard does not work and does not respond.
  The only way to solve this issue is a "hard reset" and in GRUB menu
  choosing an earlier kernel, which is linux 4.4.0-112.135. Now,
  everything works okay.

  Proposed update to the Linux 4.4.0-113.136 contains many new updates
  (please see 1.) It's an i386/x86_32 architecture, which does not
  contain PTI yet, right? I'm asking, because mentioned -proposed
  updates contains a couple of PTI-related patches and bugs in PTI can
  cause a few different signatures of crashes etc. For example:

  → Crashes in early boot, especially around CPU bringup.  Bugs in the 
trampoline code or mappings cause these. 
  → Userspace segfaults early in boot, sometimes manifesting as mount(8) 
failing to mount the rootfs.  These have tended to be TLB invalidation issues. 
Usually invalidating the wrong PCID, or otherwise missing an invalidation. 

  NOTE: if it's about PCID, which is mentioned in a second point, there
  is one patch in -proposed update: "x86/mm/32: Move
  setup_clear_cpu_cap(X86_FEATURE_PCID) earlier". Maybe that's is the
  cause of a boot failure? There are no errors in log files, such as
  '/var/log/syslog' or '/var/log/kern.log'. However, it's a Celeron, "E"
  series. So, I don't know if mentioned patches are good for this type
  of processor etc.? Especially on i386/x86_32 architecture.

  ● UPDATE/WARNING: It seems, that 'kaslr' option is responsible for
  this issue. After booting the latest v4.4.0-115.139 kernel, I've had
  the same problems as described above. However, after removing 'kaslr'
  option from a command line via GRUB menu, system started normally etc.
  The latest, working kernel with 'kaslr' option is v4.4.0-112.135.
  According to all of this I think, that 'kaslr' is not compatible with
  some "Spectre & Meltdown" mitigation patches and fixes etc.

  ✗ Release ('/proc/version_signature'): Ubuntu 4.4.0-112.135-generic 4.4.98
  ✗ Architecture: i386/x86_32
  ✗ PCI ('lspci -vnvn'): 00:0a.0 PCI bridge [0604]: NVIDIA Corporation MCP73 
PCI Express bridge [10de:056d] (rev a1) (prog-if 01 [Subtractive decode]) 
Capabilities: [b8] Subsystem: Gigabyte Technology Co., Ltd MCP73 PCI Express 
bridge [1458:026f] 

  Thanks, regards.
  

  1. https://lists.ubuntu.com/archives/xenial-
  changes/2018-February/020108.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748710/+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 1748936] Re: kASLR: unable to boot Linux v4.4.0-113.136 - v4.4.0-115.139 kernels ("Spectre & Meltdown" patches.)

** Tags added: kernel-fixed-upstream

** Changed in: linux (Ubuntu)
   Status: Fix Released => Confirmed

** Summary changed:

- kASLR: unable to boot Linux v4.4.0-113.136 - v4.4.0-115.139 kernels ("Spectre 
& Meltdown" patches.)
+ kASLR: unable to boot Linux v4.4.0-113.136 - v4.4.0-115.139 kernels; 
i386/x86_32 ("Spectre & Meltdown")

-- 
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/1748936

Title:
  kASLR: unable to boot Linux v4.4.0-113.136 - v4.4.0-115.139 kernels;
  i386/x86_32 ("Spectre & Meltdown")

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello.

  It seems, that 'kaslr' option is responsible for issues with system
  booting. The latest working kernel is v4.4.0-112.135. Every next
  release: v4.4.0-113.136 and v4.4.0-115.139 are unable to boot if
  'kaslr' option is in use etc. Everything is described in my previous
  bug report (please see 1.), but I've decided to create a new one,
  because it seems, that some of the "Spectre & Meltdown" patches are
  not compatible with kASLR and are responsible for this regressions.

  Thanks, best regards.

  [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748710

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748936/+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 1751021] Re: retpoline abi files are empty on i386

2018-03-21 Thread daniel CURTIS

** Tags removed: verification-needed-xenial
** Tags added: verification-done-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/1751021

Title:
  retpoline abi files are empty on i386

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  The .retpoline files in the current abi are actually blank.
  This is due to incorrect handling in retpoline-extract.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751021/+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 1748710] [NEW] Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1 built-in shell.

Public bug reported:

Hello.

On Thu Feb 8, Linux kernel for Ubuntu 16.04.3 LTS has been updated to
the 4.4.0-113.136 version (xenial-proposed). However, after reboot,
plymouth freezes during start, and keys on a keyboard were in-active.
After several seconds, the BusyBox screen appeared. It looks this way:

,--
| BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
| Enter 'help' for a list of built-in commands.
|
| (initramfs) _ 
`--

Unfortunately, the keyboard does not work and does not respond. The only
way to solve this issue is a "hard reset" and in GRUB menu choosing an
earlier kernel, which is linux 4.4.0-112.135. Now, everything works
okay.

Proposed update to the Linux 4.4.0-113.136 contains many new updates
(please see 1.) It's an i386/x86_32 architecture, which does not contain
PTI yet, right? I'm asking, because mentioned -proposed updates contains
a couple of PTI-related patches and bugs in PTI can cause a few
different signatures of crashes etc. For example:

✗ Crashes in early boot, especially around CPU bringup.  Bugs in the trampoline 
code or mappings cause these. 
✗ Userspace segfaults early in boot, sometimes manifesting as mount(8) failing 
to mount the rootfs.  These have tended to be TLB invalidation issues. Usually 
invalidating the wrong PCID, or otherwise missing an invalidation. 

NOTE: if it's about PCID, which is mentioned in a second point, there is
one patch in -proposed update: "x86/mm/32: Move
setup_clear_cpu_cap(X86_FEATURE_PCID) earlier". Maybe that's is the
cause of a boot failure? There are no errors in log files, such as
'/var/log/syslog' or '/var/log/kern.log'. Maybe only that one (but I
have no idea if it's important)?

✗ PCI: Using host bridge windows from ACPI; if necessary, use
"pci=nocrs" and report a bug

If I could provide some more informations, please let me know. Here are
some technical informations:

● Release ('/proc/version_signature'): Ubuntu 4.4.0-112.135-generic 4.4.98
● Architecture: i386/x86_32
● PCI ('lspci -vnvn'): 00:0a.0 PCI bridge [0604]: NVIDIA Corporation MCP73 PCI 
Express bridge [10de:056d] (rev a1) (prog-if 01 [Subtractive decode]) 
Capabilities: [b8] Subsystem: Gigabyte Technology Co., Ltd MCP73 PCI Express 
bridge [1458:026f] 

Thanks, regards.


1. https://lists.ubuntu.com/archives/xenial-
changes/2018-February/020108.html

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: i386 linux meltdown spectre xenial

** Description changed:

  Hello.
  
  On Thu Feb 8, Linux kernel for Ubuntu 16.04.3 LTS has been updated to
  the 4.4.0-113.136 version (xenial-proposed). However, after reboot,
  plymouth freezes during start, and keys on a keyboard were in-active.
  After several seconds, the BusyBox screen appeared. It looks this way:
  
- ✗
  ✗ BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
  ✗ Enter 'help' for a list of built-in commands.
  ✗
  ✗ (initramfs) _ 
- ✗
  
  Unfortunately, the keyboard does not work and does not respond. The only
  way to solve this issue is a "hard reset" and in GRUB menu choosing an
  earlier kernel, which is linux 4.4.0-112.135. Now, everything works
  okay.
  
  Proposed update to the Linux 4.4.0-113.136 contains many new updates
  (please see 1.) It's an i386/x86_32 architecture, which does not contain
  PTI yet, right? I'm asking, because mentioned -proposed updates contains
  a couple of PTI-related patches and bugs in PTI can cause a few
  different signatures of crashes etc. For example:
  
- ✓ Crashes in early boot, especially around CPU bringup.  Bugs in the 
trampoline code or mappings cause these. 
- ✓ Userspace segfaults early in boot, sometimes manifesting as mount(8) 
failing to mount the rootfs.  These have tended to be TLB invalidation issues. 
Usually invalidating the wrong PCID, or otherwise missing an invalidation. 
+ ● Crashes in early boot, especially around CPU bringup.  Bugs in the 
trampoline code or mappings cause these. 
+ ● Userspace segfaults early in boot, sometimes manifesting as mount(8) 
failing to mount the rootfs.  These have tended to be TLB invalidation issues. 
Usually invalidating the wrong PCID, or otherwise missing an invalidation. 
  
  NOTE: if it's about PCID, which is mentioned in a second point, there is
  one patch in -proposed update: "x86/mm/32: Move
  setup_clear_cpu_cap(X86_FEATURE_PCID) earlier". Maybe that's is the
  cause of a boot failure? There are no errors in log files, such as
  '/var/log/syslog' or '/var/log/kern.log'. Maybe only that one (but I
  have no idea if it's important)?
  
  ✗ PCI: Using host bridge windows from ACPI; if necessary, use
  "pci=nocrs" and report a bug
  
  If I could provide some more informations, please let me know. Here are
  some technical informations:
  
- ● Release ('/proc/version_signature'): Ubuntu 4.4.0-112.135-generic 4.4.98
- ● Architecture: i386/x86_32
- ● PCI ('lspci -vnvn'): 00:0a.0 PCI bridge [0604]: NVIDIA Corporation MCP73

[Kernel-packages] [Bug 1748710] Re: Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1 built-in shell.

Hi. I can not enter mentioned command, because during system boot
plymouth freezes and keyboard is unresponsive. After several seconds
plymouth disappears and BusyBox v1.22.1 "console" appears (here,
keyboard does not work and does not respond either). The only solution
is to use hard reboot and choose an earlier v4.4.0-112.135 Linux kernel
in GRUB menu etc.

Maybe I can execute 'apport-collect 1748710' command in v4.4.0-112.135
kernel? But this issue appeared after update to the "-proposed" kernel:
v4.4.0-112.135.

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/1748710

Title:
  Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1
  built-in shell.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello.

  On Thu Feb 8, Linux kernel for Ubuntu 16.04.3 LTS has been updated to
  the 4.4.0-113.136 version (xenial-proposed). However, after reboot,
  plymouth freezes during start, and keys on a keyboard were in-active.
  After several seconds, the BusyBox screen appeared. It looks this way:

  ,--
  | BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
  | Enter 'help' for a list of built-in commands.
  |
  | (initramfs) _ 
  `--

  Unfortunately, the keyboard does not work and does not respond. The
  only way to solve this issue is a "hard reset" and in GRUB menu
  choosing an earlier kernel, which is linux 4.4.0-112.135. Now,
  everything works okay.

  Proposed update to the Linux 4.4.0-113.136 contains many new updates
  (please see 1.) It's an i386/x86_32 architecture, which does not
  contain PTI yet, right? I'm asking, because mentioned -proposed
  updates contains a couple of PTI-related patches and bugs in PTI can
  cause a few different signatures of crashes etc. For example:

  ✗ Crashes in early boot, especially around CPU bringup.  Bugs in the 
trampoline code or mappings cause these. 
  ✗ Userspace segfaults early in boot, sometimes manifesting as mount(8) 
failing to mount the rootfs.  These have tended to be TLB invalidation issues. 
Usually invalidating the wrong PCID, or otherwise missing an invalidation. 

  NOTE: if it's about PCID, which is mentioned in a second point, there
  is one patch in -proposed update: "x86/mm/32: Move
  setup_clear_cpu_cap(X86_FEATURE_PCID) earlier". Maybe that's is the
  cause of a boot failure? There are no errors in log files, such as
  '/var/log/syslog' or '/var/log/kern.log'. Maybe only that one (but I
  have no idea if it's important)?

  ✗ PCI: Using host bridge windows from ACPI; if necessary, use
  "pci=nocrs" and report a bug

  If I could provide some more informations, please let me know. Here
  are some technical informations:

  ● Release ('/proc/version_signature'): Ubuntu 4.4.0-112.135-generic 4.4.98
  ● Architecture: i386/x86_32
  ● PCI ('lspci -vnvn'): 00:0a.0 PCI bridge [0604]: NVIDIA Corporation MCP73 
PCI Express bridge [10de:056d] (rev a1) (prog-if 01 [Subtractive decode]) 
Capabilities: [b8] Subsystem: Gigabyte Technology Co., Ltd MCP73 PCI Express 
bridge [1458:026f] 

  Thanks, regards.
  

  1. https://lists.ubuntu.com/archives/xenial-
  changes/2018-February/020108.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748710/+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 1748710] Re: Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1 built-in shell.

Please see "Ubuntu Kernel Bot (ubuntu-kernel-bot)" comment and answer.

** 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/1748710

Title:
  Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1
  built-in shell.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello.

  On Thu Feb 8, Linux kernel for Ubuntu 16.04.3 LTS has been updated to
  the 4.4.0-113.136 version (xenial-proposed). However, after reboot,
  plymouth freezes during start, and keys on a keyboard were in-active.
  After several seconds, the BusyBox screen appeared. It looks this way:

  ,--
  | BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
  | Enter 'help' for a list of built-in commands.
  |
  | (initramfs) _ 
  `--

  Unfortunately, the keyboard does not work and does not respond. The
  only way to solve this issue is a "hard reset" and in GRUB menu
  choosing an earlier kernel, which is linux 4.4.0-112.135. Now,
  everything works okay.

  Proposed update to the Linux 4.4.0-113.136 contains many new updates
  (please see 1.) It's an i386/x86_32 architecture, which does not
  contain PTI yet, right? I'm asking, because mentioned -proposed
  updates contains a couple of PTI-related patches and bugs in PTI can
  cause a few different signatures of crashes etc. For example:

  ✗ Crashes in early boot, especially around CPU bringup.  Bugs in the 
trampoline code or mappings cause these. 
  ✗ Userspace segfaults early in boot, sometimes manifesting as mount(8) 
failing to mount the rootfs.  These have tended to be TLB invalidation issues. 
Usually invalidating the wrong PCID, or otherwise missing an invalidation. 

  NOTE: if it's about PCID, which is mentioned in a second point, there
  is one patch in -proposed update: "x86/mm/32: Move
  setup_clear_cpu_cap(X86_FEATURE_PCID) earlier". Maybe that's is the
  cause of a boot failure? There are no errors in log files, such as
  '/var/log/syslog' or '/var/log/kern.log'. Maybe only that one (but I
  have no idea if it's important)?

  ✗ PCI: Using host bridge windows from ACPI; if necessary, use
  "pci=nocrs" and report a bug

  If I could provide some more informations, please let me know. Here
  are some technical informations:

  ● Release ('/proc/version_signature'): Ubuntu 4.4.0-112.135-generic 4.4.98
  ● Architecture: i386/x86_32
  ● PCI ('lspci -vnvn'): 00:0a.0 PCI bridge [0604]: NVIDIA Corporation MCP73 
PCI Express bridge [10de:056d] (rev a1) (prog-if 01 [Subtractive decode]) 
Capabilities: [b8] Subsystem: Gigabyte Technology Co., Ltd MCP73 PCI Express 
bridge [1458:026f] 

  Thanks, regards.
  

  1. https://lists.ubuntu.com/archives/xenial-
  changes/2018-February/020108.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748710/+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 1748710] Re: Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1 built-in shell (initramfs).

** Summary changed:

- Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1 
built-in shell.
+ Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1 
built-in shell (initramfs).

** Description changed:

  Hello.
  
  On Thu Feb 8, Linux kernel for Ubuntu 16.04.3 LTS has been updated to
  the 4.4.0-113.136 version (xenial-proposed). However, after reboot,
- plymouth freezes during start, and keys on a keyboard were in-active.
- After several seconds, the BusyBox screen appeared. It looks this way:
+ plymouth freezes during start, and keys on an USB keyboard were in-
+ active. After several seconds, the BusyBox shell screen appeared. It
+ looks this way:
  
  ,--
  | BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
  | Enter 'help' for a list of built-in commands.
  |
  | (initramfs) _ 
  `--
  
- Unfortunately, the keyboard does not work and does not respond. The only
- way to solve this issue is a "hard reset" and in GRUB menu choosing an
- earlier kernel, which is linux 4.4.0-112.135. Now, everything works
+ Unfortunately, the USB keyboard does not work and does not respond. The
+ only way to solve this issue is a "hard reset" and in GRUB menu choosing
+ an earlier kernel, which is linux 4.4.0-112.135. Now, everything works
  okay.
  
  Proposed update to the Linux 4.4.0-113.136 contains many new updates
  (please see 1.) It's an i386/x86_32 architecture, which does not contain
  PTI yet, right? I'm asking, because mentioned -proposed updates contains
  a couple of PTI-related patches and bugs in PTI can cause a few
  different signatures of crashes etc. For example:
  
  ✗ Crashes in early boot, especially around CPU bringup.  Bugs in the 
trampoline code or mappings cause these. 
  ✗ Userspace segfaults early in boot, sometimes manifesting as mount(8) 
failing to mount the rootfs.  These have tended to be TLB invalidation issues. 
Usually invalidating the wrong PCID, or otherwise missing an invalidation. 
  
  NOTE: if it's about PCID, which is mentioned in a second point, there is
  one patch in -proposed update: "x86/mm/32: Move
  setup_clear_cpu_cap(X86_FEATURE_PCID) earlier". Maybe that's is the
  cause of a boot failure? There are no errors in log files, such as
- '/var/log/syslog' or '/var/log/kern.log'. Maybe only that one (but I
- have no idea if it's important)?
+ '/var/log/syslog' or '/var/log/kern.log'. However, it's a Celeron, "E"
+ series. So, I don't know if mentioned patches are good for this type of
+ processor etc.? Especially on i386/x86_32 architecture.
  
- ✗ PCI: Using host bridge windows from ACPI; if necessary, use
- "pci=nocrs" and report a bug
- 
- If I could provide some more informations, please let me know. Here are
- some technical informations:
+ I hope, that all mitigations and fixes for "Metldown & Spectre_v1.2"
+ atacks will be available for 32-bit x86 architecture. (OpenSUSE
+ Developers are working on such a fixes/patches, right?) If I could
+ provide some more informations, please let me know. Here are some
+ technical informations:
  
  ● Release ('/proc/version_signature'): Ubuntu 4.4.0-112.135-generic 4.4.98
  ● Architecture: i386/x86_32
  ● PCI ('lspci -vnvn'): 00:0a.0 PCI bridge [0604]: NVIDIA Corporation MCP73 
PCI Express bridge [10de:056d] (rev a1) (prog-if 01 [Subtractive decode]) 
Capabilities: [b8] Subsystem: Gigabyte Technology Co., Ltd MCP73 PCI Express 
bridge [1458:026f] 
  
  Thanks, regards.
  
  
  1. https://lists.ubuntu.com/archives/xenial-
  changes/2018-February/020108.html

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1748710

Title:
  Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1
  built-in shell (initramfs).

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello.

  On Thu Feb 8, Linux kernel for Ubuntu 16.04.3 LTS has been updated to
  the 4.4.0-113.136 version (xenial-proposed). However, after reboot,
  plymouth freezes during start, and keys on an USB keyboard were in-
  active. After several seconds, the BusyBox shell screen appeared. It
  looks this way:

  ,--
  | BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
  | Enter 'help' for a list of built-in commands.
  |
  | (initramfs) _ 
  `--

  Unfortunately, the USB keyboard does not work and does not respond.
  The only way to solve this issue is a "hard reset" and in GRUB menu
  choosing an earlier kernel, which is linux 4.4.0-112.135. Now,
  everything works okay.

  Proposed update to the Linux 4.4.0-113.136 contains many new updates
  (please see 1.) It's an i386/x86_32 architecture, which does not
  contain PTI yet, right? I'm asking, because mentioned -proposed
  updates contains a couple of PTI-related patches and bugs in PTI can
  cause a few different signatures of crashes etc. For example:

  ✗ Crashes in early boot, especially ar

[Kernel-packages] [Bug 1748710] Re: Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1 built-in shell (initramfs).

2018-02-12 Thread daniel CURTIS

Hello. There is the same problem with a new, latest Linux
4.4.0-115-generic kernel (updated today). I've tried to boot system with
'nosplash' option (set via GRUB etc.) and it seems, that there is a
problem with:

Gave up waiting for root device. Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
   - Check root= (did the system wait for the right device?)
 - Missing modules (cat /proc/modules; ls /dev)

ALERT! UUID=* does not exist. Dropping to a shell!

BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
Enter 'help' for a lost of built-in commands.

(initramfs) _

However, I've decided try to boot v4.4.0-115-generic kernel once again,
because above 'ALERT!' message was very interesting for me, but this
time, without 'kaslr' option. So, in a GRUB menu I removed this option
and press CTRL + x. Everything was okay - system boot normally.

It seems, that there is a problem with a 'kaslr' in latest 16.04 LTS
Release kernels (I'm having this problem since update to the
v4.4.0-113.136 kernel version.

Should I create a new bug report about 'kaslr' and latest kernel
versions?

-- 
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/1748710

Title:
  Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1
  built-in shell (initramfs).

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello.

  On Thu Feb 8, Linux kernel for Ubuntu 16.04.3 LTS has been updated to
  the 4.4.0-113.136 version (xenial-proposed). However, after reboot,
  plymouth freezes during start, and keys on an USB keyboard were in-
  active. After several seconds, the BusyBox shell screen appeared. It
  looks this way:

  ,--
  | BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
  | Enter 'help' for a list of built-in commands.
  |
  | (initramfs) _ 
  `--

  Unfortunately, the USB keyboard does not work and does not respond.
  The only way to solve this issue is a "hard reset" and in GRUB menu
  choosing an earlier kernel, which is linux 4.4.0-112.135. Now,
  everything works okay.

  Proposed update to the Linux 4.4.0-113.136 contains many new updates
  (please see 1.) It's an i386/x86_32 architecture, which does not
  contain PTI yet, right? I'm asking, because mentioned -proposed
  updates contains a couple of PTI-related patches and bugs in PTI can
  cause a few different signatures of crashes etc. For example:

  ✗ Crashes in early boot, especially around CPU bringup.  Bugs in the 
trampoline code or mappings cause these. 
  ✗ Userspace segfaults early in boot, sometimes manifesting as mount(8) 
failing to mount the rootfs.  These have tended to be TLB invalidation issues. 
Usually invalidating the wrong PCID, or otherwise missing an invalidation. 

  NOTE: if it's about PCID, which is mentioned in a second point, there
  is one patch in -proposed update: "x86/mm/32: Move
  setup_clear_cpu_cap(X86_FEATURE_PCID) earlier". Maybe that's is the
  cause of a boot failure? There are no errors in log files, such as
  '/var/log/syslog' or '/var/log/kern.log'. However, it's a Celeron, "E"
  series. So, I don't know if mentioned patches are good for this type
  of processor etc.? Especially on i386/x86_32 architecture.

  I hope, that all mitigations and fixes for "Metldown & Spectre_v1.2"
  atacks will be available for 32-bit x86 architecture. (OpenSUSE
  Developers are working on such a fixes/patches, right?) If I could
  provide some more informations, please let me know. Here are some
  technical informations:

  ● Release ('/proc/version_signature'): Ubuntu 4.4.0-112.135-generic 4.4.98
  ● Architecture: i386/x86_32
  ● PCI ('lspci -vnvn'): 00:0a.0 PCI bridge [0604]: NVIDIA Corporation MCP73 
PCI Express bridge [10de:056d] (rev a1) (prog-if 01 [Subtractive decode]) 
Capabilities: [b8] Subsystem: Gigabyte Technology Co., Ltd MCP73 PCI Express 
bridge [1458:026f] 

  Thanks, regards.
  

  1. https://lists.ubuntu.com/archives/xenial-
  changes/2018-February/020108.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748710/+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 1748710] Re: Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1 built-in shell (initramfs).

2018-02-12 Thread daniel CURTIS

** Description changed:

  Hello.
  
  On Thu Feb 8, Linux kernel for Ubuntu 16.04.3 LTS has been updated to
  the 4.4.0-113.136 version (xenial-proposed). However, after reboot,
  plymouth freezes during start, and keys on an USB keyboard were in-
  active. After several seconds, the BusyBox shell screen appeared. It
  looks this way:
  
  ,--
  | BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
  | Enter 'help' for a list of built-in commands.
  |
  | (initramfs) _ 
  `--
  
  Unfortunately, the USB keyboard does not work and does not respond. The
  only way to solve this issue is a "hard reset" and in GRUB menu choosing
  an earlier kernel, which is linux 4.4.0-112.135. Now, everything works
  okay.
  
  Proposed update to the Linux 4.4.0-113.136 contains many new updates
  (please see 1.) It's an i386/x86_32 architecture, which does not contain
  PTI yet, right? I'm asking, because mentioned -proposed updates contains
  a couple of PTI-related patches and bugs in PTI can cause a few
  different signatures of crashes etc. For example:
  
- ✗ Crashes in early boot, especially around CPU bringup.  Bugs in the 
trampoline code or mappings cause these. 
- ✗ Userspace segfaults early in boot, sometimes manifesting as mount(8) 
failing to mount the rootfs.  These have tended to be TLB invalidation issues. 
Usually invalidating the wrong PCID, or otherwise missing an invalidation. 
+ → Crashes in early boot, especially around CPU bringup.  Bugs in the 
trampoline code or mappings cause these. 
+ → Userspace segfaults early in boot, sometimes manifesting as mount(8) 
failing to mount the rootfs.  These have tended to be TLB invalidation issues. 
Usually invalidating the wrong PCID, or otherwise missing an invalidation. 
  
  NOTE: if it's about PCID, which is mentioned in a second point, there is
  one patch in -proposed update: "x86/mm/32: Move
  setup_clear_cpu_cap(X86_FEATURE_PCID) earlier". Maybe that's is the
  cause of a boot failure? There are no errors in log files, such as
  '/var/log/syslog' or '/var/log/kern.log'. However, it's a Celeron, "E"
  series. So, I don't know if mentioned patches are good for this type of
  processor etc.? Especially on i386/x86_32 architecture.
  
- I hope, that all mitigations and fixes for "Metldown & Spectre_v1.2"
- atacks will be available for 32-bit x86 architecture. (OpenSUSE
- Developers are working on such a fixes/patches, right?) If I could
- provide some more informations, please let me know. Here are some
- technical informations:
+ ● UPDATE/WARNING: It seems, that 'kaslr' option is responsible for this
+ issue. After booting the latest v4.4.0-115.139 kernel, I've had the same
+ problems as described above. However, after removing 'kaslr' option from
+ a command line via GRUB menu, system started normally etc. The latest,
+ working kernel with 'kaslr' option is v4.4.0-112.135. According to all
+ of this I think, that 'kaslr' is not compatible with some "Spectre &
+ Meltdown" mitigation patches and fixes etc.
  
- ● Release ('/proc/version_signature'): Ubuntu 4.4.0-112.135-generic 4.4.98
- ● Architecture: i386/x86_32
- ● PCI ('lspci -vnvn'): 00:0a.0 PCI bridge [0604]: NVIDIA Corporation MCP73 
PCI Express bridge [10de:056d] (rev a1) (prog-if 01 [Subtractive decode]) 
Capabilities: [b8] Subsystem: Gigabyte Technology Co., Ltd MCP73 PCI Express 
bridge [1458:026f] 
+ ✗ Release ('/proc/version_signature'): Ubuntu 4.4.0-112.135-generic 4.4.98
+ ✗ Architecture: i386/x86_32
+ ✗ PCI ('lspci -vnvn'): 00:0a.0 PCI bridge [0604]: NVIDIA Corporation MCP73 
PCI Express bridge [10de:056d] (rev a1) (prog-if 01 [Subtractive decode]) 
Capabilities: [b8] Subsystem: Gigabyte Technology Co., Ltd MCP73 PCI Express 
bridge [1458:026f] 
  
  Thanks, regards.
  
  
  1. https://lists.ubuntu.com/archives/xenial-
  changes/2018-February/020108.html

** Tags added: kaslr

-- 
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/1748710

Title:
  Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1
  built-in shell (initramfs).

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello.

  On Thu Feb 8, Linux kernel for Ubuntu 16.04.3 LTS has been updated to
  the 4.4.0-113.136 version (xenial-proposed). However, after reboot,
  plymouth freezes during start, and keys on an USB keyboard were in-
  active. After several seconds, the BusyBox shell screen appeared. It
  looks this way:

  ,--
  | BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
  | Enter 'help' for a list of built-in commands.
  |
  | (initramfs) _ 
  `--

  Unfortunately, the USB keyboard does not work and does not respond.
  The only way to solve this issue is a "hard reset" and in GRUB menu
  choosing an earlier kernel, which is linux 4.4.0-112.135. Now,
  everything works okay.

  Proposed update to the Linux 4.4.0-113.136 contains

[Kernel-packages] [Bug 1748936] [NEW] kASLR: unable to boot Linux v4.4.0-113.136 - v4.4.0-115.139 kernels ("Spectre & Meltdown" patches.)

2018-02-12 Thread daniel CURTIS

Public bug reported:

Hello.

It seems, that 'kaslr' option is responsible for issues with system
booting. The latest working kernel is v4.4.0-112.135. Every next
release: v4.4.0-113.136 and v4.4.0-115.139 are unable to boot if 'kaslr'
option is in use etc. Everything is described in my previous bug report
(please see 1.), but I've decided to create a new one, because it seems,
that some of the "Spectre & Meltdown" patches are not compatible with
kASLR and are responsible for this regressions.

Thanks, best regards.

[1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748710

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: i386 kaslr linux meltdown spectre

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1748936

Title:
  kASLR: unable to boot Linux v4.4.0-113.136 - v4.4.0-115.139 kernels
  ("Spectre & Meltdown" patches.)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello.

  It seems, that 'kaslr' option is responsible for issues with system
  booting. The latest working kernel is v4.4.0-112.135. Every next
  release: v4.4.0-113.136 and v4.4.0-115.139 are unable to boot if
  'kaslr' option is in use etc. Everything is described in my previous
  bug report (please see 1.), but I've decided to create a new one,
  because it seems, that some of the "Spectre & Meltdown" patches are
  not compatible with kASLR and are responsible for this regressions.

  Thanks, best regards.

  [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748710

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748936/+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 1748710] Re: Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1 built-in shell (initramfs).

2018-02-14 Thread daniel CURTIS

Good day, Mr Salisbury.

Yes, I can test the latest kernel, but I have a few very naive questions
(I just want to be sure for one hundred percent etc.) So, because it's
an i386/x86_32 architecture I should:

✗ download 
'linux-headers-4.16.0-041600rc1-generic_4.16.0-041600rc1.201802120030_i386.deb' 
and 
'linux-image-4.16.0-041600rc1-generic_4.16.0-041600rc1.201802120030_i386.deb' 
packages;
✗ use, for example, dpkg(1) command to install these two packages ($ sudo dpkg 
-i ...);
✗ add "kaslr" option to the '/etc/default/grub' file (in 
'GRUB_CMDLINE_LINUX_DEFAULT' option);
✗ update GRUB with update-grub(8) command to generate a grub2 config file etc.; 
✗ reboot. 

Once again: I apologize for such a naive questions. Mr Salisbury, can
You confirm if what I've wrote is okay? Generally: is it a proper way to
test the latest kernel? And what about dpkg(1) command: I should use
'-i, --install' action only, right? I'm asking, because there is - for
example - a 'gdebi' package, which is a simple tool to install deb files
etc.

Geez, what a shame...

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/1748710

Title:
  Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1
  built-in shell (initramfs).

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete

Bug description:
  Hello.

  On Thu Feb 8, Linux kernel for Ubuntu 16.04.3 LTS has been updated to
  the 4.4.0-113.136 version (xenial-proposed). However, after reboot,
  plymouth freezes during start, and keys on an USB keyboard were in-
  active. After several seconds, the BusyBox shell screen appeared. It
  looks this way:

  ,--
  | BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
  | Enter 'help' for a list of built-in commands.
  |
  | (initramfs) _ 
  `--

  Unfortunately, the USB keyboard does not work and does not respond.
  The only way to solve this issue is a "hard reset" and in GRUB menu
  choosing an earlier kernel, which is linux 4.4.0-112.135. Now,
  everything works okay.

  Proposed update to the Linux 4.4.0-113.136 contains many new updates
  (please see 1.) It's an i386/x86_32 architecture, which does not
  contain PTI yet, right? I'm asking, because mentioned -proposed
  updates contains a couple of PTI-related patches and bugs in PTI can
  cause a few different signatures of crashes etc. For example:

  → Crashes in early boot, especially around CPU bringup.  Bugs in the 
trampoline code or mappings cause these. 
  → Userspace segfaults early in boot, sometimes manifesting as mount(8) 
failing to mount the rootfs.  These have tended to be TLB invalidation issues. 
Usually invalidating the wrong PCID, or otherwise missing an invalidation. 

  NOTE: if it's about PCID, which is mentioned in a second point, there
  is one patch in -proposed update: "x86/mm/32: Move
  setup_clear_cpu_cap(X86_FEATURE_PCID) earlier". Maybe that's is the
  cause of a boot failure? There are no errors in log files, such as
  '/var/log/syslog' or '/var/log/kern.log'. However, it's a Celeron, "E"
  series. So, I don't know if mentioned patches are good for this type
  of processor etc.? Especially on i386/x86_32 architecture.

  ● UPDATE/WARNING: It seems, that 'kaslr' option is responsible for
  this issue. After booting the latest v4.4.0-115.139 kernel, I've had
  the same problems as described above. However, after removing 'kaslr'
  option from a command line via GRUB menu, system started normally etc.
  The latest, working kernel with 'kaslr' option is v4.4.0-112.135.
  According to all of this I think, that 'kaslr' is not compatible with
  some "Spectre & Meltdown" mitigation patches and fixes etc.

  ✗ Release ('/proc/version_signature'): Ubuntu 4.4.0-112.135-generic 4.4.98
  ✗ Architecture: i386/x86_32
  ✗ PCI ('lspci -vnvn'): 00:0a.0 PCI bridge [0604]: NVIDIA Corporation MCP73 
PCI Express bridge [10de:056d] (rev a1) (prog-if 01 [Subtractive decode]) 
Capabilities: [b8] Subsystem: Gigabyte Technology Co., Ltd MCP73 PCI Express 
bridge [1458:026f] 

  Thanks, regards.
  

  1. https://lists.ubuntu.com/archives/xenial-
  changes/2018-February/020108.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748710/+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 1748710] Re: Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1 built-in shell (initramfs).

2018-02-14 Thread daniel CURTIS

Here is a new, separate bug report about 'kASLR' and system booting
issues (v4.4.0-113.136 - v4.4.0-115-generic kernel versions):

● https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748936

-- 
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/1748710

Title:
  Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1
  built-in shell (initramfs).

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete

Bug description:
  Hello.

  On Thu Feb 8, Linux kernel for Ubuntu 16.04.3 LTS has been updated to
  the 4.4.0-113.136 version (xenial-proposed). However, after reboot,
  plymouth freezes during start, and keys on an USB keyboard were in-
  active. After several seconds, the BusyBox shell screen appeared. It
  looks this way:

  ,--
  | BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
  | Enter 'help' for a list of built-in commands.
  |
  | (initramfs) _ 
  `--

  Unfortunately, the USB keyboard does not work and does not respond.
  The only way to solve this issue is a "hard reset" and in GRUB menu
  choosing an earlier kernel, which is linux 4.4.0-112.135. Now,
  everything works okay.

  Proposed update to the Linux 4.4.0-113.136 contains many new updates
  (please see 1.) It's an i386/x86_32 architecture, which does not
  contain PTI yet, right? I'm asking, because mentioned -proposed
  updates contains a couple of PTI-related patches and bugs in PTI can
  cause a few different signatures of crashes etc. For example:

  → Crashes in early boot, especially around CPU bringup.  Bugs in the 
trampoline code or mappings cause these. 
  → Userspace segfaults early in boot, sometimes manifesting as mount(8) 
failing to mount the rootfs.  These have tended to be TLB invalidation issues. 
Usually invalidating the wrong PCID, or otherwise missing an invalidation. 

  NOTE: if it's about PCID, which is mentioned in a second point, there
  is one patch in -proposed update: "x86/mm/32: Move
  setup_clear_cpu_cap(X86_FEATURE_PCID) earlier". Maybe that's is the
  cause of a boot failure? There are no errors in log files, such as
  '/var/log/syslog' or '/var/log/kern.log'. However, it's a Celeron, "E"
  series. So, I don't know if mentioned patches are good for this type
  of processor etc.? Especially on i386/x86_32 architecture.

  ● UPDATE/WARNING: It seems, that 'kaslr' option is responsible for
  this issue. After booting the latest v4.4.0-115.139 kernel, I've had
  the same problems as described above. However, after removing 'kaslr'
  option from a command line via GRUB menu, system started normally etc.
  The latest, working kernel with 'kaslr' option is v4.4.0-112.135.
  According to all of this I think, that 'kaslr' is not compatible with
  some "Spectre & Meltdown" mitigation patches and fixes etc.

  ✗ Release ('/proc/version_signature'): Ubuntu 4.4.0-112.135-generic 4.4.98
  ✗ Architecture: i386/x86_32
  ✗ PCI ('lspci -vnvn'): 00:0a.0 PCI bridge [0604]: NVIDIA Corporation MCP73 
PCI Express bridge [10de:056d] (rev a1) (prog-if 01 [Subtractive decode]) 
Capabilities: [b8] Subsystem: Gigabyte Technology Co., Ltd MCP73 PCI Express 
bridge [1458:026f] 

  Thanks, regards.
  

  1. https://lists.ubuntu.com/archives/xenial-
  changes/2018-February/020108.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748710/+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 1751021] Re: retpoline abi files are empty on i386

2018-03-11 Thread daniel CURTIS

Hello.

I've noticed this issue with blank '/boot/retpoline-*' files in 16.04
LTS Release (i386/x86_32) after Linux kernel update to the v4.4.0-115
version. (Generally, I've started to seeing these files when
"Spectre_V12" patches were available for i386 architecture. I wanted to
ask a question or report a bug about it etc.) So, these files are empty
and it looks this way on 16.04 LTS Release:

[~]$ ls -al /boot/retpoline-4.4.0-11*
-rw-r--r-- 1 root root 0 lut 11 19:00 /boot/retpoline-4.4.0-115-generic
-rw-r--r-- 1 root root 0 lut 13 00:14 /boot/retpoline-4.4.0-116-generic

[~]$ uname -m
i686

Thanks, best regards.

-- 
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/1751021

Title:
  retpoline abi files are empty on i386

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  The .retpoline files in the current abi are actually blank.
  This is due to incorrect handling in retpoline-extract.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751021/+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 1488426] Re: High CPU usage of kworker/ksoftirqd

2016-02-16 Thread Peter Curtis

I can also confirm that the 3.19.0.49-generic kernel solves the problem
for me.

-- 
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/1488426

Title:
  High CPU usage of kworker/ksoftirqd

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  kworker consuming 71.5% cpu resource
  ksoftirqd consuming 28.9% cpu resource

  It leads to power consumption issue and sometimes leads to BT does not
  work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1488426/+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 1323426] Re: HP Z8000 bluetooth mouse

2015-12-29 Thread Curtis Penner

Similar to Bela Berczi (bberczi).  This was on a new HP Envy 13t.  It
works fine with Windows 10, but will only connect as "All Types", and
will not work as a mouse, on the 14.04.3 release.

-- 
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/1323426

Title:
  HP Z8000 bluetooth mouse

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  This mouse is a HID over GAT recent HP low power mouse.

  It  is recognized as ALL types bluetooth peripherals not as a mouse!

  The mouse at the end of the installation process (automatic pin
  selection) results as PAIRED  but the connection option is not
  available in the bluetooth setting dialog.

  UBUNTU is last 14.04 full updated at filing bug time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1323426/+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 1540807] Re: ArpON ver. 2.7: the DARPI and -d (--darpi) flag bug.

2016-02-02 Thread daniel CURTIS

Change package to arpon.

** Package changed: linux (Ubuntu) => arpon (Ubuntu)

** Description changed:

  Hello. Because on Ubuntu 12.04 LTS an ArpON package is pretty outdated
  (ver. 2.0-2.1 0) I've decided to use a version from a Vivid release -
  2.7.
  
  It seems that ArpON ver. 2.7 has a bug related to a DARPI anti Arp
  Poisoning techniques. Because I am using a DHCP method to obtain an IP
  address I needed to use a DARPI method (Dynamin Arp Inspect.) instead of
  SARPI (Static Arp Inspect). After installation via 'apt-get' utility,
  configuring "arpon" file from '/etc/default/' directory and uncomment
  line responsible for a DARPI method, ArpON failed to start with a
  following error:
  
  $ sudo /etc/init.d/arpon start
  * Starting anti ARP poisoning daemon arpon
  20:38:55 PID = 
  
  /usr/bin/arpon: invalid  option -- 'd'  [fail]
  
- For a DARPI method line in the '/etc/default/arpon' file looks this way:
- DAEMON_OPTS="-q -f /var/log/arpon/arpon.log -g -d". According to the
- Ubuntu manpage[1] '-g' flag stands for "Works in logging mode", since
- '-d' flag means "Manages Arp Cache dynamically". Everything should work
- okay, but it does not. I've tried many possibilities, configurations
- etc.
+ For a DARPI method a line in the '/etc/default/arpon' file looks this
+ way: DAEMON_OPTS="-q -f /var/log/arpon/arpon.log -g -d". According to
+ the Ubuntu manpage[1] '-g' flag stands for "Works in logging mode",
+ since '-d' flag means "Manages Arp Cache dynamically". Everything should
+ work okay, but it does not. I've tried many possibilities,
+ configurations etc.
  
  And it seems, that a new ArpON 2.7 version requires a '-D' flag instead
  '-d'. So, now there must be the '-D' flag not '-d'. After this small
  change everything started to work okay:
  
  $ sudo /etc/init.d/arpon start
  * Starting anti ARP poisoning daemon arpon
  20:43:32 PID =[OK]
  
  One more test, to be one hundred percent sure: after running
  '/etc/init.d/arpon status' command, status of anti ARP poisoning daemon
  arpon is [OK]. Here are some technical details:
  
  * Ubuntu 3.2.0-98.138-generic-pae 3.2.75 ('cat /proc/version_signature' 
command result)
  * lsb_release -rd
-Description:   Ubuntu 12.04.5 LTS
-Release:   12.04
+    Description:   Ubuntu 12.04.5 LTS
+    Release:   12.04
  * arpon: 2.7.2-1
  
  By the way: ArpON sometimes crashed with "SIGSEGV in pthread_kill()"
  (after user login), but I will have to create a new bug report.
  
  Best regards.
  _
  
  [1] http://manpages.ubuntu.com/manpages/trusty/man8/arpon.8.html

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1540807

Title:
  ArpON ver. 2.7: the DARPI and  -d (--darpi) flag bug.

Status in arpon package in Ubuntu:
  New

Bug description:
  Hello. Because on Ubuntu 12.04 LTS an ArpON package is pretty outdated
  (ver. 2.0-2.1 0) I've decided to use a version from a Vivid release -
  2.7.

  It seems that ArpON ver. 2.7 has a bug related to a DARPI anti Arp
  Poisoning techniques. Because I am using a DHCP method to obtain an IP
  address I needed to use a DARPI method (Dynamin Arp Inspect.) instead
  of SARPI (Static Arp Inspect). After installation via 'apt-get'
  utility, configuring "arpon" file from '/etc/default/' directory and
  uncomment line responsible for a DARPI method, ArpON failed to start
  with a following error:

  $ sudo /etc/init.d/arpon start
  * Starting anti ARP poisoning daemon arpon
  20:38:55 PID = 

  /usr/bin/arpon: invalid  option -- 'd'  [fail]

  For a DARPI method a line in the '/etc/default/arpon' file looks this
  way: DAEMON_OPTS="-q -f /var/log/arpon/arpon.log -g -d". According to
  the Ubuntu manpage[1] '-g' flag stands for "Works in logging mode",
  since '-d' flag means "Manages Arp Cache dynamically". Everything
  should work okay, but it does not. I've tried many possibilities,
  configurations etc.

  And it seems, that a new ArpON 2.7 version requires a '-D' flag
  instead '-d'. So, now there must be the '-D' flag not '-d'. After this
  small change everything started to work okay:

  $ sudo /etc/init.d/arpon start
  * Starting anti ARP poisoning daemon arpon
  20:43:32 PID =[OK]

  One more test, to be one hundred percent sure: after running
  '/etc/init.d/arpon status' command, status of anti ARP poisoning
  daemon arpon is [OK]. Here are some technical details:

  * Ubuntu 3.2.0-98.138-generic-pae 3.2.75 ('cat /proc/version_signature' 
command result)
  * lsb_release -rd
     Description:   Ubuntu 12.04.5 LTS
     Release:   12.04
  * arpon: 2.7.2-1

  By the way: ArpON sometimes crashed with "SIGSEGV in pthread_kill()"
  (after user login), but I will have to create a new bug report.

  Best regards.
  _

  [1] http://manpages.ubuntu.com/manpages/trusty/man8/arpon.8.html

To manage notifications about this bug go to:
https

[Kernel-packages] [Bug 1540807] [NEW] ArpON ver. 2.7: the DARPI and -d (--darpi) flag bug.

2016-02-02 Thread daniel CURTIS

Public bug reported:

Hello. Because on Ubuntu 12.04 LTS an ArpON package is pretty outdated
(ver. 2.0-2.1 0) I've decided to use a version from a Vivid release -
2.7.

It seems that ArpON ver. 2.7 has a bug related to a DARPI anti Arp
Poisoning techniques. Because I am using a DHCP method to obtain an IP
address I needed to use a DARPI method (Dynamin Arp Inspect.) instead of
SARPI (Static Arp Inspect). After installation via 'apt-get' utility,
configuring "arpon" file from '/etc/default/' directory and uncomment
line responsible for a DARPI method, ArpON failed to start with a
following error:

$ sudo /etc/init.d/arpon start
* Starting anti ARP poisoning daemon arpon
20:38:55 PID = 

/usr/bin/arpon: invalid  option -- 'd'  [fail]

For a DARPI method a line in the '/etc/default/arpon' file looks this
way: DAEMON_OPTS="-q -f /var/log/arpon/arpon.log -g -d". According to
the Ubuntu manpage[1] '-g' flag stands for "Works in logging mode",
since '-d' flag means "Manages Arp Cache dynamically". Everything should
work okay, but it does not. I've tried many possibilities,
configurations etc.

And it seems, that a new ArpON 2.7 version requires a '-D' flag instead
'-d'. So, now there must be the '-D' flag not '-d'. After this small
change everything started to work okay:

$ sudo /etc/init.d/arpon start
* Starting anti ARP poisoning daemon arpon
20:43:32 PID =[OK]

One more test, to be one hundred percent sure: after running
'/etc/init.d/arpon status' command, status of anti ARP poisoning daemon
arpon is [OK]. Here are some technical details:

* Ubuntu 3.2.0-98.138-generic-pae 3.2.75 ('cat /proc/version_signature' command 
result)
* lsb_release -rd
   Description: Ubuntu 12.04.5 LTS
   Release: 12.04
* arpon: 2.7.2-1

By the way: ArpON sometimes crashed with "SIGSEGV in pthread_kill()"
(after user login), but I will have to create a new bug report.

Best regards.
_

[1] http://manpages.ubuntu.com/manpages/trusty/man8/arpon.8.html

** Affects: arpon (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: arpon darpi

-- 
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/1540807

Title:
  ArpON ver. 2.7: the DARPI and  -d (--darpi) flag bug.

Status in arpon package in Ubuntu:
  New

Bug description:
  Hello. Because on Ubuntu 12.04 LTS an ArpON package is pretty outdated
  (ver. 2.0-2.1 0) I've decided to use a version from a Vivid release -
  2.7.

  It seems that ArpON ver. 2.7 has a bug related to a DARPI anti Arp
  Poisoning techniques. Because I am using a DHCP method to obtain an IP
  address I needed to use a DARPI method (Dynamin Arp Inspect.) instead
  of SARPI (Static Arp Inspect). After installation via 'apt-get'
  utility, configuring "arpon" file from '/etc/default/' directory and
  uncomment line responsible for a DARPI method, ArpON failed to start
  with a following error:

  $ sudo /etc/init.d/arpon start
  * Starting anti ARP poisoning daemon arpon
  20:38:55 PID = 

  /usr/bin/arpon: invalid  option -- 'd'  [fail]

  For a DARPI method a line in the '/etc/default/arpon' file looks this
  way: DAEMON_OPTS="-q -f /var/log/arpon/arpon.log -g -d". According to
  the Ubuntu manpage[1] '-g' flag stands for "Works in logging mode",
  since '-d' flag means "Manages Arp Cache dynamically". Everything
  should work okay, but it does not. I've tried many possibilities,
  configurations etc.

  And it seems, that a new ArpON 2.7 version requires a '-D' flag
  instead '-d'. So, now there must be the '-D' flag not '-d'. After this
  small change everything started to work okay:

  $ sudo /etc/init.d/arpon start
  * Starting anti ARP poisoning daemon arpon
  20:43:32 PID =[OK]

  One more test, to be one hundred percent sure: after running
  '/etc/init.d/arpon status' command, status of anti ARP poisoning
  daemon arpon is [OK]. Here are some technical details:

  * Ubuntu 3.2.0-98.138-generic-pae 3.2.75 ('cat /proc/version_signature' 
command result)
  * lsb_release -rd
     Description:   Ubuntu 12.04.5 LTS
     Release:   12.04
  * arpon: 2.7.2-1

  By the way: ArpON sometimes crashed with "SIGSEGV in pthread_kill()"
  (after user login), but I will have to create a new bug report.

  Best regards.
  _

  [1] http://manpages.ubuntu.com/manpages/trusty/man8/arpon.8.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/arpon/+bug/1540807/+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 1245226] Re: HDMI: audio-video playback too fast

2014-05-28 Thread Peter Curtis

This should still be reopened as it occurs for me on a Chillblast
Defiant (Haswell/Optimus Architecture, Core i7 Processor and nVidia GTX
765M graphics) with Mint 17  running kernel 3.13.0-24 and I have also
tried the ubuntu mainline 3.14.4 kernel. In both cases HDMI sound is
about 20% fast whilst switching to normal audio output immediately slows
it down. Switching graphics processor makes no difference. Kernel
3.10.33 works fine as did 3.8.0 in Mint 15. We definitely have a
regression here somewhere between 3.10.33 and 3.13.0

-- 
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/1245226

Title:
  HDMI: audio-video playback too fast

Status in “linux” package in Ubuntu:
  Invalid

Bug description:
  After upgrading to Ubuntu 13.10, selecting HDMI as audio output device
  is broken. Audio is played back at high speed. When playing back video
  clips, the video frames are also too fast. Note that, when selecting
  headphone as audio output device, everything works.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu44
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sun Oct 27 18:00:53 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2010-11-07 (1085 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to saucy on 2013-10-22 (5 days ago)
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3+13.10.20131004-0ubuntu1
  --- 
  ApportVersion: 2.12.6-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 2831 F pulseaudio
   /dev/snd/controlC0:  ubuntu 2831 F pulseaudio
   /dev/snd/pcmC0D0c:   ubuntu 2831 F...m pulseaudio
  CasperVersion: 1.336ubuntu1
  CurrentDmesg:
   [   60.513505] systemd-hostnamed[5239]: Warning: nss-myhostname is not 
installed. Changing the local hostname might make it unresolveable. Please 
install nss-myhostname!
   [   63.157819] EXT4-fs (sda7): mounted filesystem with ordered data mode. 
Opts: (null)
  DistroRelease: Ubuntu 14.04
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131103)
  MachineType: MSI MS-7623
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
  ProcVersionSignature: Ubuntu 3.12.0-1.3-generic 3.12.0-rc7
  RelatedPackageVersions:
   linux-restricted-modules-3.12.0-1-generic N/A
   linux-backports-modules-3.12.0-1-generic  N/A
   linux-firmware1.117
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.12.0-1-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 08/10/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V11.5
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 880GM-E41 (MS-7623)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV11.5:bd08/10/2010:svnMSI:pnMS-7623:pvr2.0:rvnMSI:rn880GM-E41(MS-7623):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7623
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245226/+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 1245226] Re: HDMI: audio-video playback too fast

2014-05-30 Thread Peter Curtis

Christopher Penalver, life is too short to proliferate bug reports when
there is an existing one with all the background. In my opinion what is
needed is crosslinking and consolidation rather than proliferation so a
full picture emerges and the appropriate people address it.

It is, for example, also being looked at by the kernel team at
https://bugzilla.kernel.org/show_bug.cgi?id=60769 which has further
links to places the problem has been reported.

** Bug watch added: Linux Kernel Bug Tracker #60769
   http://bugzilla.kernel.org/show_bug.cgi?id=60769

-- 
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/1245226

Title:
  HDMI: audio-video playback too fast

Status in “linux” package in Ubuntu:
  Invalid

Bug description:
  After upgrading to Ubuntu 13.10, selecting HDMI as audio output device
  is broken. Audio is played back at high speed. When playing back video
  clips, the video frames are also too fast. Note that, when selecting
  headphone as audio output device, everything works.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu44
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sun Oct 27 18:00:53 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2010-11-07 (1085 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to saucy on 2013-10-22 (5 days ago)
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3+13.10.20131004-0ubuntu1
  --- 
  ApportVersion: 2.12.6-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 2831 F pulseaudio
   /dev/snd/controlC0:  ubuntu 2831 F pulseaudio
   /dev/snd/pcmC0D0c:   ubuntu 2831 F...m pulseaudio
  CasperVersion: 1.336ubuntu1
  CurrentDmesg:
   [   60.513505] systemd-hostnamed[5239]: Warning: nss-myhostname is not 
installed. Changing the local hostname might make it unresolveable. Please 
install nss-myhostname!
   [   63.157819] EXT4-fs (sda7): mounted filesystem with ordered data mode. 
Opts: (null)
  DistroRelease: Ubuntu 14.04
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131103)
  MachineType: MSI MS-7623
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
  ProcVersionSignature: Ubuntu 3.12.0-1.3-generic 3.12.0-rc7
  RelatedPackageVersions:
   linux-restricted-modules-3.12.0-1-generic N/A
   linux-backports-modules-3.12.0-1-generic  N/A
   linux-firmware1.117
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.12.0-1-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 08/10/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V11.5
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 880GM-E41 (MS-7623)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV11.5:bd08/10/2010:svnMSI:pnMS-7623:pvr2.0:rvnMSI:rn880GM-E41(MS-7623):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7623
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245226/+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 1311378] Re: [LENOVO INVALID] suspend/resume failure [non-free: wl]

2014-04-23 Thread Brandon Curtis

*** This bug is a duplicate of bug 1054732 ***
https://bugs.launchpad.net/bugs/1054732

** This bug has been marked a duplicate of bug 1054732
   [LENOVO 4298R86] suspend/resume failure

-- 
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/1311378

Title:
  [LENOVO INVALID] suspend/resume failure [non-free: wl]

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  ?

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.46
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: wl
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  max1724 F pulseaudio
   /dev/snd/controlC0:  max1724 F pulseaudio
  CurrentDmesg:
   [  122.022529] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
   [  122.023096] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
   [  122.024476] r8169 :01:00.0 eth0: link down
   [  123.779594] r8169 :01:00.0 eth0: link up
   [  123.779609] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
  Date: Tue Apr 22 15:42:45 2014
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=80a01e99-0c5b-4d19-bfd2-d9f201b66728
  InstallationDate: Installed on 2014-04-12 (10 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140316)
  InterpreterPath: /usr/bin/python3.4
  MachineType: LENOVO INVALID
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed 
root=UUID=2a5d2144-532f-4da7-8135-95c1d1d3d51e 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:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.126
  SourcePackage: linux
  StagingDrivers: rts5139
  Title: [LENOVO INVALID] suspend/resume failure [non-free: wl]
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8CCN29WW(V2.03)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3196WIN8 STD MBR IPG
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: INVALID
  dmi.modalias: 
dmi:bvnLENOVO:bvr8CCN29WW(V2.03):bd11/14/2013:svnLENOVO:pnINVALID:pvrINVALID:rvnLENOVO:rnINVALID:rvr3196WIN8STDMBRIPG:cvnLENOVO:ct10:cvrINVALID:
  dmi.product.name: INVALID
  dmi.product.version: INVALID
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1311378/+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 1293549] Re: Filesystem mount from lxc template causes filesystem permission breakages

2014-03-20 Thread Curtis Hovey

** Changed in: juju-core
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1293549

Title:
  Filesystem mount from lxc template causes filesystem permission
  breakages

Status in juju-core:
  Fix Released
Status in lxc containers:
  Confirmed
Status in “linux” package in Ubuntu:
  Confirmed
Status in “postgresql” package in Juju Charms Collection:
  New

Bug description:
  In juju-core 1.17.5, creating new lxc machines is now much faster as
  it appears to be using a template machine. In addition, the root
  filesystem is mounted from the template machine.

  Unfortunately, this causes filesystem permissions to screw up.

  juju deploy ubuntu
  juju ssh ubuntu/0
  sudo chown ubuntu:ubuntu /etc/ssl/private
  ls /etc/ssl/private

  That final 'ls' fails with a permission denied. This is possibly a
  security precaution in lxc or the filesystem.

  This issue breaks the postgresql charm. The PostgreSQL packages
  require and use the ssl-cert package, which changes /etc/ssl/private
  to be group readable by the ssl-cert group. The postgres user, a
  member of the ssl-cert group, is unable to read the private key stored
  in this directory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1293549/+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 1297514] [NEW] [Apple Inc. MacBookAir4, 2] suspend/resume failure

2014-03-25 Thread Brian Curtis

Public bug reported:

Ubuntu 14.04

Casual closing and opening of lid.

Couldn't resume screen after opening.

ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-19-generic 3.13.0-19.40
ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
Uname: Linux 3.13.0-19-generic x86_64
Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bcurtis1858 F pulseaudio
 /dev/snd/pcmC0D0p:   bcurtis1858 F...m pulseaudio
CurrentDmesg:
 [   43.036916] audit_printk_skb: 123 callbacks suppressed
 [   43.036920] type=1400 audit(1395782625.927:68): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="/usr/lib/cups/backend/cups-pdf" pid=2304 comm="apparmor_parser"
 [   43.036928] type=1400 audit(1395782625.927:69): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" 
pid=2304 comm="apparmor_parser"
 [   43.037356] type=1400 audit(1395782625.927:70): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" 
pid=2304 comm="apparmor_parser"
Date: Tue Mar 25 17:23:22 2014
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InstallationDate: Installed on 2014-03-23 (2 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64+mac (20140322)
InterpreterPath: /usr/bin/python3.4
MachineType: Apple Inc. MacBookAir4,2
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic 
root=UUID=b18f322c-211f-4f53-86dc-0905dacd5030 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:
 linux-restricted-modules-3.13.0-19-generic N/A
 linux-backports-modules-3.13.0-19-generic  N/A
 linux-firmware 1.126
SourcePackage: linux
Title: [Apple Inc. MacBookAir4,2] suspend/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 01/24/2012
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBA41.88Z.0077.B0F.1201241549
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-742912EFDBEE19B3
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookAir4,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-742912EFDBEE19B3
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B0F.1201241549:bd01/24/2012:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3:
dmi.product.name: MacBookAir4,2
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-kerneloops resume suspend trusty

-- 
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/1297514

Title:
  [Apple Inc. MacBookAir4,2] suspend/resume failure

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 14.04

  Casual closing and opening of lid.

  Couldn't resume screen after opening.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-19-generic 3.13.0-19.40
  ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bcurtis1858 F pulseaudio
   /dev/snd/pcmC0D0p:   bcurtis1858 F...m pulseaudio
  CurrentDmesg:
   [   43.036916] audit_printk_skb: 123 callbacks suppressed
   [   43.036920] type=1400 audit(1395782625.927:68): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="/usr/lib/cups/backend/cups-pdf" pid=2304 comm="apparmor_parser"
   [   43.036928] type=1400 audit(1395782625.927:69): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" 
pid=2304 comm="apparmor_parser"
   [   43.037356] type=1400 audit(1395782625.927:70): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" 
pid=2304 comm="apparmor_parser"
  Date: Tue Mar 25 17:23:22 2014
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  InstallationDate: Installed on 2014-03-23 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64+mac (20140322)
  InterpreterPath: /usr/bin/python3.4
  MachineType: Apple Inc. MacBookAir4,2
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnv

[Kernel-packages] [Bug 1402763] Re: Multicast traffic not propating correctly over linux bridge

2014-12-17 Thread Curtis Hovey

** Tags added: lxc network

** Changed in: juju-core
   Status: New => Triaged

** Changed in: juju-core
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1402763

Title:
  Multicast traffic not propating correctly over linux bridge

Status in juju-core:
  Triaged
Status in linux package in Ubuntu:
  Confirmed
Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  There's a lot of supposition in the title of this bug but its
  currently my best guess.

  In this deployment, I have a number of services running in LXC
  containers across multiple physical hosts; each service is clustered
  across three units, all on separate physical hosts, using corosync and
  pacemaker; when using multicast to support cluster communication, I
  occasionally see a container drop out of the cluster and use its
  isolation response (to shutdown all managed services); when using
  unicast I've not yet see this same problem.

  LXC containers are bridged to the main physical network using a linux
  bridge:

eth0 <-> juju-br0 <-> vethXXX <-> | vethXXX |

  All MTU's are standard (1500).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lxc 1.0.6-0ubuntu0.1
  ProcVersionSignature: User Name 3.13.0-40.69-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Mon Dec 15 17:20:08 2014
  ProcEnviron:
   TERM=screen-bce
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 17 10:16 seq
   crw-rw 1 root audio 116, 33 Dec 17 10:16 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 14.04
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: Dell Inc. PowerEdge R610
  Package: lxc 1.0.6-0ubuntu0.1
  PackageArchitecture: amd64
  PciMultimedia:
   
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic 
root=UUID=5a86874d-8bbd-4e7a-b73e-17c914de390b ro
  ProcEnviron:
   TERM=screen-bce
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic 
root=UUID=5a86874d-8bbd-4e7a-b73e-17c914de390b ro
  ProcVersionSignature: User Name 3.13.0-43.72-generic 3.13.11.11
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images trusty uec-images apparmor
  Uname: Linux 3.13.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy libvirtd netdev plugdev sudo 
video
  _MarkForUpload: True
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx
  dmi.bios.date: 08/18/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 6.0.7
  dmi.board.name: 0F0XJ6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr6.0.7:bd08/18/2011:svnDellInc.:pnPowerEdgeR610:pvr:rvnDellInc.:rn0F0XJ6:rvrA11:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R610
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1402763/+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 1616949] Re: guest on bridge becomes inaccessible

2016-10-27 Thread Curtis Hovey

** Tags added: jujuqa

-- 
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/1616949

Title:
  guest on bridge becomes inaccessible

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We have a "virtual maas" setup where we have a maas node on a linux
  bridge (created by libvirt) and some other number of nodes on that
  same bridge.

  the maas node then controls the other nodes turning them on and off
  and generally working maas-like magic.

  In this scenario on 16.04 with when deploying 3 or so nodes at a time,
  the maas node becomes inaccessible, and as it is the root device for
  iscsi storage of the installs, the nodes fail also.

  This occurred with xenial kernel (4.4).
  Reverting the kernel to 3.19 (linux-lts-vivid) kernel fixes the problem.
  https://launchpad.net/ubuntu/+source/linux-lts-vivid
  Specifically, the fixed kernel is
  $ dpkg-query --show | grep linux-.*3.19
  linux-image-3.19.0-66-generic   3.19.0-66.74~14.04.1
  linux-image-extra-3.19.0-66-generic 3.19.0-66.74~14.04.1

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 3.19.0-66.74~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-66-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 25 12:10 seq
   crw-rw 1 root audio 116, 33 Aug 25 12:10 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Aug 25 14:37:07 2016
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: root=/dev/mapper/mpath0-part2 ro console=hvc0
  ProcLoadAvg: 0.40 0.28 0.46 1/1337 140794
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 3.19.0-66-generic (buildd@bos01-ppc64el-021) (gcc 
version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #74~14.04.1-Ubuntu SMP Tue Jul 
19 19:54:47 UTC 2016
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-66-generic N/A
   linux-backports-modules-3.19.0-66-generic  N/A
   linux-firmware 1.157.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_dscr: DSCR is 0
  cpu_freq:
   min: 3.667 GHz (cpu 120)
   max: 3.691 GHz (cpu 0)
   avg: 3.689 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to firmware
  cpu_smt: SMT is off

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616949/+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 1239233] Re: Video playback is like fast forward in 13.10 when radeon HDMI audio output is enabled

2013-10-29 Thread Curtis Bissonnette

I take it this will be fixed with
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237530

-- 
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/1239233

Title:
  Video playback is like fast forward in 13.10 when radeon HDMI audio
  output is enabled

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  The PC is connected to TV with HDMI cable. With Xubuntu 13.04 no
  problem. With Xubuntu 13.10 video playback is like set to fast
  forward.

  Is is happening both in browser video playback (Youtube) and video
  playback in Parole.

  VLC doesn't suffer from the same problem.

  Checked with 3.12-RC4 kernel and nothing changed.
  Checked with or without radeon.dpm=1 and radeon.audio=1 settings.

  Video/Audio: ATi Radeon 2600 PRO

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-12-generic 3.11.0-12.19
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  verde  1324 F pulseaudio
  CurrentDmesg:

  Date: Sun Oct 13 02:10:43 2013
  HibernationDevice: RESUME=UUID=a8e666a9-5515-468a-a13a-deb0cda148ee
  InstallationDate: Installed on 2013-09-27 (15 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Beta i386 (20130925.1)
  MachineType: Gigabyte Technology Co., Ltd. GA-MA790X-DS4
  MarkForUpload: True
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=fb62d2dd-e7a5-46fc-aa9e-9e20b92ed63d ro quiet splash radeon.dpm=1 
radeon.audio=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-12-generic N/A
   linux-backports-modules-3.11.0-12-generic  N/A
   linux-firmware 1.116
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F9
  dmi.board.name: GA-MA790X-DS4
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd08/12/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790X-DS4:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790X-DS4:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA790X-DS4
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1239233/+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 1218547] Re: Clevo W350ST brightness keys don't work on Kubuntu

2013-11-24 Thread Peter Curtis

I have the same problem on a Clevo W230ST based machine running  Saucy
13 10. Exactly the same symtoms and print out of ls /sys/class/backlight
both using 3.11 and a 3.8  kernel on a LiveUSB. The keys will reduce the
backlight but not increase leaving one completely in the dark. I am
running Bumblebee and there is also a problem with bbswitch (an
important part of bumblebee) not getting the correct ACPI handles but it
seems unrelated to me.

-- 
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/1218547

Title:
  Clevo W350ST brightness keys don't work on Kubuntu

Status in The Linux Kernel:
  Unknown
Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  The Fn+F8 and Fn+F9 keys are not working on my Clevo W350ST with
  Kubuntu Raring to change screen brightness of the internal laptop
  screen. I installed linux-headers-3.11.0-4, linux-
  headers-3.11.0-4-generic,  linux-image-3.11.0-4-generic and linux-
  image-extra-3.11.0-4-generic  from Saucy packages repository but the
  problem persists.

  When trying:

  $ xev | sed -n 's/^.*state \([0-9].*\), keycode *\([0-9]\+\) *\(.*\), 
.*$/keycode \2 = \3, state = \1/p'  
  
  keycode 36 = (keysym 0xff0d, Return), state = 0x10
   
  keycode 232 = (keysym 0x1008ff03, XF86MonBrightnessDown), state = 0x10
   
  keycode 233 = (keysym 0x1008ff02, XF86MonBrightnessUp), state = 0x10

  Event codes appear correctly.

  And changing:

  /sys/class/backlight/intel_backlight/brightness

  changes the brightness of the screen, but pressing the key combination
  does not. I believe this happens because the key combination is, in
  fact, changing the value of

  /sys/class/backlight/acpi_video0/brightness

  I have

  http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu
  http://ppa.launchpad.net/bumblebee/stable/ubuntu

  in my package sources

  Thanks!
  --- 
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  silvio 2689 F pulseaudio
   /dev/snd/pcmC1D0p:   silvio 2689 F...m pulseaudio
   /dev/snd/controlC0:  silvio 2689 F pulseaudio
  DistroRelease: Ubuntu 13.04
  HibernationDevice: RESUME=UUID=58f7acf2-4914-4b11-a2ac-e641cb4b39fd
  InstallationDate: Installed on 2013-08-18 (57 days ago)
  InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Notebook W350STQ/W370ST
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-9-generic 
root=UUID=f0bca002-701a-49bb-befc-7343bac2e245 ro locale=pt_BR quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-9-generic N/A
   linux-backports-modules-3.11.0-9-generic  N/A
   linux-firmware1.106
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  raring
  Uname: Linux 3.11.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo vboxusers
  dmi.bios.date: 04/11/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W350STQ/W370ST
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/11/2013:svnNotebook:pnW350STQ/W370ST:pvrNotApplicable:rvnNotebook:rnW350STQ/W370ST:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W350STQ/W370ST
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1218547/+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 1239233] Re: Video playback is like fast forward in 13.10 when radeon HDMI audio output is enabled (but no sound at all)

2013-10-20 Thread Curtis Bissonnette

I am experiencing the same symptoms after upgrading from 13.04 to 13.10.
When I select HDMI as my output sound source video and audo appear to
play in fast forward.  When using analog sound everything appears to
work correctly.  This was working correctly in 13.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/1239233

Title:
  Video playback is like fast forward in 13.10 when radeon HDMI audio
  output is enabled (but no sound at all)

Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  The PC is connected to TV with HDMI cable. With Xubuntu 13.04 no
  problem. With Xubuntu 13.10 video playback is like set to fast
  forward.

  Is is happening both in browser video playback (Youtube) and video
  playback in Parole.

  VLC doesn't suffer from the same problem.

  Checked with 3.12-RC4 kernel and nothing changed.
  Checked with or without radeon.dpm=1 and radeon.audio=1 settings.

  Video/Audio: ATi Radeon 2600 PRO

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-12-generic 3.11.0-12.19
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  verde  1324 F pulseaudio
  CurrentDmesg:

  Date: Sun Oct 13 02:10:43 2013
  HibernationDevice: RESUME=UUID=a8e666a9-5515-468a-a13a-deb0cda148ee
  InstallationDate: Installed on 2013-09-27 (15 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Beta i386 (20130925.1)
  MachineType: Gigabyte Technology Co., Ltd. GA-MA790X-DS4
  MarkForUpload: True
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=fb62d2dd-e7a5-46fc-aa9e-9e20b92ed63d ro quiet splash radeon.dpm=1 
radeon.audio=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-12-generic N/A
   linux-backports-modules-3.11.0-12-generic  N/A
   linux-firmware 1.116
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F9
  dmi.board.name: GA-MA790X-DS4
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd08/12/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790X-DS4:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790X-DS4:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA790X-DS4
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1239233/+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 1488426] Re: High CPU usage of kworker/ksoftirqd

2015-12-02 Thread Peter Curtis

I also have a similar problem which does Not seem to be solved by the
patched kernel although the perf report looks very similar and plugging
in a USB device clears the problem. The starting and inhibiting of the
kworker spinning is very specific and rather bizare on my new Skylake
machine running Linux Mint 17.3 beta (Cinnamon 2.8 desktop) with kernels
between 3.19 and 4.2 during test.

It only starts when external power is off and the machine is suspended/resumed 
- I have not so far been able to provoke it any other way.
If power is restored excess usage stops but restarts if power unplugged.
If power is on and a suspend/resume cycle is carried out external power can be 
unplugged without the excess usage.
Any USB 2 device stops the excess usage when plugged into the USB2 port 
including USB3 devices.
USB 3 devices plugged into a USB3 port do not stop the power usage.
Turning on the webcam stops the usage as long as it is on - the webcam is on 
the usb2 hub
Turning Bluetooth off and on with the function key stops the high usage as long 
as it still remains on. Software disabling and enabling does not work. When 
bluetooth switched by function key it disappears/appears in lsusb under the USB 
2 hub

In other words everything seems to point to the USB 2 system. 
perf report
+   68.46% 0.00%  kworker/0:3  [kernel.kallsyms] [k] 
ret_from_fork ▒
+   68.46% 0.00%  kworker/0:3  [kernel.kallsyms] [k] 
kthread   ▒
+   68.46% 0.00%  kworker/0:3  [kernel.kallsyms] [k] 
worker_thread ▒
+   68.43% 0.02%  kworker/0:3  [kernel.kallsyms] [k] 
process_one_work  ▒
+   67.44% 0.07%  kworker/0:3  [kernel.kallsyms] [k] 
rpm_idle  ▒
+   66.89% 0.07%  kworker/0:3  [kernel.kallsyms] [k] 
rpm_suspend   ▒
+   66.84% 0.02%  kworker/0:3  [kernel.kallsyms] [k] 
pm_runtime_work   ▒
+   66.47% 0.00%  kworker/0:3  [kernel.kallsyms] [k] 
usb_runtime_idle  ▒
+   66.47% 0.00%  kworker/0:3  [kernel.kallsyms] [k] 
__rpm_callback▒
+   66.44% 0.00%  kworker/0:3  [kernel.kallsyms] [k] 
__pm_runtime_suspend  ▒
+   66.23% 0.02%  kworker/0:3  [kernel.kallsyms] [k] 
rpm_callback  ▒
+   66.21% 0.02%  kworker/0:3  [kernel.kallsyms] [k] 
usb_runtime_suspend   ▒
+   66.11% 0.02%  kworker/0:3  [kernel.kallsyms] [k] 
usb_suspend_both  ▒
+   64.11% 0.02%  kworker/0:3  [kernel.kallsyms] [k] 
hub_resume▒
+   64.11% 0.02%  kworker/0:3  [kernel.kallsyms] [k] 
usb_resume_interface.isra.6   ▒
+   64.04% 0.52%  kworker/0:3  [kernel.kallsyms] [k] 
hub_activate  ▒
+   62.49% 0.24%  kworker/0:3  [kernel.kallsyms] [k] 
hub_port_status   ▒
+   62.02% 0.21%  kworker/0:3  [kernel.kallsyms] [k] 
usb_control_msg   ▒
+   59.15% 0.26%  kworker/0:3  [kernel.kallsyms] [k] 
usb_start_wait_urb▒
+   53.26% 0.05%  kworker/0:3  [kernel.kallsyms] [k] 
usb_submit_urb▒
+   53.26% 0.64%  kworker/0:3  [kernel.kallsyms] [k] 
usb_submit_urb.part.6 ▒
+   50.96% 1.70%  kworker/0:3  [kernel.kallsyms] [k] 
usb_hcd_submit_urb▒
+   36.85%36.23%  kworker/0:3  [kernel.kallsyms] [k] 
xhci_hub_control  ▒
+   17.07% 0.00%  ksoftirqd/0  [kernel.kallsyms] [k] 
ret_from_fork ▒
+   17.07% 0.00%  ksoftirqd/0  [kernel.kallsyms] [k] 
kthread   ▒
+   16.65% 1.33%  ksoftirqd/0  [kernel.kallsyms] [k] 
smpboot_thread_fn ▒
+9.88% 0.69%  kworker/0:3  [kernel.kallsyms] [k] 
usb_hcd_giveback_urb  ▒
+8.22% 0.83%  kworker/0:3  [kernel.kallsyms] [k] 
__tasklet_schedule  


lspci and lsusb
@Helios:~$ lspci
00:00.0 Host bridge: Intel Corporation Sky Lake Host Bridge/DRAM Registers (rev 
08)
00:02.0 VGA compatible controller: Intel Corporation Sky Lake Integrated 
Graphics (rev 07)
00:14.0 USB controller: Intel Corporation Device 9d2f (rev 21)
00:14.2 Signal processing controller: Intel Corporation Device 9d31 (rev 21)
00:16.0 Communication controller: Intel Corporation Device 9d3a (rev 21)
00:17.0 SATA controller: Intel Corporation Device 9d03 (rev 21)
00:1c.0 PCI bridge: Intel Corporation Device 9d14 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Device 9d48 (rev 21)
00:1f.2 Memory controller: Intel Corporation Device 9d21 (rev 21)
00:1f.3 Audio device: Intel Corporati

[Kernel-packages] [Bug 1488426] Re: High CPU usage of kworker/ksoftirqd

2015-12-07 Thread Peter Curtis

I have carried out some more comprehensive tests using the kernel in #4 over 
the weekend and found it does improve my situation far more than my initial 
quick test showed. Most of the rather bizarre behaviour has gone include the 
changes with power from battery to external and the importance of suspending. 
Once kworker spinning has started it can now be _predictably_ stopped when 
using your kernel by:
Any USB 2 device being plugged into any USB port or a USB 3 device plugged 
into the USB 2 port
The internal Bluetooth being turned on so that it shows up as USB device
The internal Web cam being used (by cheese during my test). 
Note running the web cam does not change what is shown by lsusb -t, everything 
else which stops spinning shows as a new device being connected in dmesg and 
appears in lsusb.
Although the kernel in #4 does not completely solve the problem it is obviously 
addresses the correct area and in my case makes the machine usable without 
having anything plugged into a usb port, keeping bluetooth on is sufficient. 

@AceLan What is the status of the patch and other work on the issue? Is
there anything else I can do to progress the work?

-- 
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/1488426

Title:
  High CPU usage of kworker/ksoftirqd

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  kworker consuming 71.5% cpu resource
  ksoftirqd consuming 28.9% cpu resource

  It leads to power consumption issue and sometimes leads to BT does not
  work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1488426/+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 1488426] Re: High CPU usage of kworker/ksoftirqd

2015-12-09 Thread Peter Curtis

@Aditya Thanks for the clarification. I had been trying to find out if
the patch had been merged.

The issue is not however fixed for me with 4.2 nor was it for lpuser in
#8 who tried a number of kernels. However it an improvement as I said in
#17

The following shows the problem first without BT on then with showing
the problem disappearing:

:~$ uname -r
4.2.0-19-generic
pete@Helios-Ubuntu:~$ top

in,  2 users,  load average: 0.71, 0.28, 0.11
Tasks: 238 total,   2 running, 236 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.8 us, 25.0 sy,  0.0 ni, 73.8 id,  0.0 wa,  0.0 hi,  0.4 si,  0.0 st
KiB Mem:   8082944 total,  1196884 used,  6886060 free,61504 buffers
KiB Swap: 10239996 total,0 used, 10239996 free.   542960 cached Mem

  PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND 
   50 root  20   0   0  0  0 R  71.2  0.0   0:15.14 kworker/0:1 
3 root  20   0   0  0  0 S  28.9  0.0   0:11.58 ksoftirqd/0 
  729 root  20   0  294360  11812   7432 S   1.7  0.1   0:08.33 polkitd 
 1182 pete  20   0 1451368 183784  60088 S   1.7  2.3   0:25.51 cinnamon
  145 root  20   0   0  0  0 S   0.3  0.0   0:00.10 kworker/u8+ 
  638 root  20   0  462888  19056  13656 S   0.3  0.2   0:03.32 NetworkMan+ 
  644 message+  20   0   44192   5004   3480 S   0.3  0.1   0:03.83 dbus-daemon 
  796 root  20   0  405348  86652  76272 S   0.3  1.1   0:07.15 Xorg
1 root  20   0   37748   5784   3892 S   0.0  0.1   0:01.13 systemd 
2 root  20   0   0  0  0 S   0.0  0.0   0:00.00 kthreadd
4 root  20   0   0  0  0 S   0.0  0.0   0:13.54 kworker/0:0 
5 root   0 -20   0  0  0 S   0.0  0.0   0:00.00 kworker/0:+ 
6 root  20   0   0  0  0 S   0.0  0.0   0:00.03 kworker/u8+ 
7 root  20   0   0  0  0 S   0.0  0.0   0:00.39 rcu_sched   
8 root  20   0   0  0  0 S   0.0  0.0   0:00.00 rcu_bh  
9 root  20   0   0  0  0 S   0.0  0.0   0:00.35 rcuos/0 
   10 root  20   0   0  0  0 S   0.0  0.0   0:00.00 rcuob/0 
pete@Helios-Ubuntu:~$ lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 4: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M
|__ Port 4: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M

=== Now Switch on Bluetooth ==
~$ lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 3: Dev 4, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 3: Dev 4, If 1, Class=Wireless, Driver=btusb, 12M
|__ Port 4: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M
|__ Port 4: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M
$ top

top - 09:21:47 up 9 min,  2 users,  load average: 0.79, 0.69, 0.32
Tasks: 246 total,   1 running, 245 sleeping,   0 stopped,   0 zombie
%Cpu(s):  2.1 us,  0.3 sy,  0.0 ni, 97.6 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
KiB Mem:   8082944 total,  1289152 used,  6793792 free,74748 buffers
KiB Swap: 10239996 total,0 used, 10239996 free.   569360 cached Mem

  PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND 
 1182 pete  20   0 1453084 185460  60264 S   4.0  2.3   0:34.76 cinnamon
  729 root  20   0  294756  12112   7432 S   2.6  0.1   0:11.52 polkitd 
  638 root  20   0  462888  17052  13676 S   1.0  0.2   0:04.52 NetworkMan+ 
  644 message+  20   0   44192   5080   3480 S   1.0  0.1   0:05.15 dbus-daemon 
 2150 pete  20   0   29220   3172   2592 R   0.7  0.0   0:00.06 top 
  796 root  20   0  405400  87404  77020 S   0.3  1.1   0:09.59 Xorg
1 root  20   0  119676   5812   3892 S   0.0  0.1   0:01.15 systemd 
2 root  20   0   0  0  0 S   0.0  0.0   0:00.00 kthreadd
3 root  20   0   0  0  0 S   0.0  0.0   1:03.84 ksoftirqd/0 
4 root  20   0   0  0  0 S   0.0  0.0   1:16.92 kworker/0:0 
5 root   0 -20   0  0  0 S   0.0  0.0   0:00.00 kworker/0:+ 
6 root  20   0   0  0  0 S   0.0  0.0   0:00.03 kworker/u8+ 
7 root  20   0   0  0  0 S   0.0  0.0   0:00.50 rcu_sched   
8 root  20   0   0  0  0 S   0.0  0.0   0:00.00 rcu_bh  
9 root  20   0   0  0  0 S   0.0  0.0   0:00.39 rcuos/0 
   10 root  20   0   0  0  0 S   0.0  0.0   0:00.00 rcuob/0 

I hope a solution to my problem has been found at http://linux-
kernel.2935.n7.nabble.com/TESTPATCH-v2-xhci-fix-usb2-resume-timing-and-
races-tc1250796.html#a1256745

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ht

[Kernel-packages] [Bug 1488426] Re: High CPU usage of kworker/ksoftirqd

2015-12-10 Thread Peter Curtis

I have tried the test patch provided by Mathias Nyman in http://linux-
kernel.2935.n7.nabble.com/TESTPATCH-v2-xhci-fix-usb2-resume-timing-and-
races-tc1250796.html#a1256745 and rebuilt a Wily 4.2 kernel and that has
prevented High CPU usage of kworker/ksoftirqd under all the
circumstances I have tried. Note this is marked as a TESTPATCH and
Mathias Nyman mentions his intention is to  " do some minor cleanups and
add it to the queue ". At best it will be in the 4.4 kernel and then
available for backports  but it good to know that there is a solution in
hand.

@acelan Is there any way for you to also push the Mathias Nyman patch
into the ubuntu kernel, assuming it also solves your original problem.
Then normal users can just use an updated ubuntu kernel to get rid of
this issue. As it is a timing and race problem it may well turn out to
have  a much wider impact than current reports show, in particular as it
seems to affect Skylake machines.

-- 
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/1488426

Title:
  High CPU usage of kworker/ksoftirqd

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  kworker consuming 71.5% cpu resource
  ksoftirqd consuming 28.9% cpu resource

  It leads to power consumption issue and sometimes leads to BT does not
  work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1488426/+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 1991833] Re: VRF Kernel Module Does Not Exist

2023-01-06 Thread Clay Curtis

** Changed in: linux-aws (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1991833

Title:
  VRF Kernel Module Does Not Exist

Status in linux-aws package in Ubuntu:
  Invalid

Bug description:
  On a standard Ubuntu 22.04 LTS image, the vrf module exists and can be
  loaded. The AMI image ami-08c40ec9ead489470 in AWS us-east-1 (and all
  other regions that I have tested) does not have this kernel module
  built therefore I cannot create vrf network devices.

  Usually I could run `ip link add vrf-mgmt type vrf table 10` and
  create the VRF device, but instead get an error `Error: Unknown device
  type.`.

  
  Trying to load the module:

  # modprobe vrf
  modprobe: FATAL: Module vrf not found in directory 
/lib/modules/5.15.0-1020-aws

  
  # Boot config
  # grep VRF /boot/config-5.15.0-1020-aws 
  CONFIG_NET_VRF=m

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-aws-headers-5.15.0-1020 5.15.0-1020.24
  ProcVersionSignature: Ubuntu 5.15.0-1020.24-aws 5.15.53
  Uname: Linux 5.15.0-1020-aws x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Oct  5 18:41:11 2022
  Ec2AMI: ami-08c40ec9ead489470
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1a
  Ec2InstanceType: t3.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-aws
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1991833/+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 1943092] [NEW] package linux-headers-5.11.0-34-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-34-generic/scripts/mod/empty.dwo.

2021-09-08 Thread Curtis Schroeder

Public bug reported:

Description:Ubuntu 20.04.3 LTS
Release:20.04

\linux-headers-5.11.0-34-generic:
  Installed: (none)
  Candidate: 5.11.0-34.36~20.04.1
  Version table:
 5.11.0-34.36~20.04.1 500
500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages

Install failed during latest kernel update.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-headers-5.11.0-34-generic (not installed)
ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Sep  8 20:26:11 2021
DuplicateSignature:
 package:linux-headers-5.11.0-34-generic:(not installed)
 Unpacking linux-hwe-5.11-headers-5.11.0-34 (5.11.0-34.36~20.04.1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-26WFDo/10-linux-hwe-5.11-headers-5.11.0-34_5.11.0-34.36~20.04.1_all.deb
 (--unpack):
  unable to create new file 
'/var/lib/dpkg/info/linux-hwe-5.11-headers-5.11.0-34.list-new': Operation not 
permitted
ErrorMessage: unable to open 
'/usr/src/linux-headers-5.11.0-34-generic/scripts/mod/empty.dwo.dpkg-new': 
Operation not permitted
InstallationDate: Installed on 2021-02-21 (199 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: linux-hwe-5.11
Title: package linux-headers-5.11.0-34-generic (not installed) failed to 
install/upgrade: unable to open 
'/usr/src/linux-headers-5.11.0-34-generic/scripts/mod/empty.dwo.dpkg-new': 
Operation not permitted
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-hwe-5.11 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1943092

Title:
  package linux-headers-5.11.0-34-generic (not installed) failed to
  install/upgrade: unable to open '/usr/src/linux-
  headers-5.11.0-34-generic/scripts/mod/empty.dwo.dpkg-new': Operation
  not permitted

Status in linux-hwe-5.11 package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  \linux-headers-5.11.0-34-generic:
Installed: (none)
Candidate: 5.11.0-34.36~20.04.1
Version table:
   5.11.0-34.36~20.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages

  Install failed during latest kernel update.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-headers-5.11.0-34-generic (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Sep  8 20:26:11 2021
  DuplicateSignature:
   package:linux-headers-5.11.0-34-generic:(not installed)
   Unpacking linux-hwe-5.11-headers-5.11.0-34 (5.11.0-34.36~20.04.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-26WFDo/10-linux-hwe-5.11-headers-5.11.0-34_5.11.0-34.36~20.04.1_all.deb
 (--unpack):
unable to create new file 
'/var/lib/dpkg/info/linux-hwe-5.11-headers-5.11.0-34.list-new': Operation not 
permitted
  ErrorMessage: unable to open 
'/usr/src/linux-headers-5.11.0-34-generic/scripts/mod/empty.dwo.dpkg-new': 
Operation not permitted
  InstallationDate: Installed on 2021-02-21 (199 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: linux-hwe-5.11
  Title: package linux-headers-5.11.0-34-generic (not installed) failed to 
install/upgrade: unable to open 
'/usr/src/linux-headers-5.11.0-34-generic/scripts/mod/empty.dwo.dpkg-new': 
Operation not permitted
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1943092/+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 1943092] Re: package linux-headers-5.11.0-34-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-34-generic/scripts/mod/empty.dwo.dp

2021-09-19 Thread Curtis Schroeder

This is with the NVIDIA 460 driver. At present, I can't successfully
switch to the 470 driver, because it tries to use the 5.11.0-34.36
kernel files as part of the install.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1943092

Title:
  package linux-headers-5.11.0-34-generic (not installed) failed to
  install/upgrade: unable to open '/usr/src/linux-
  headers-5.11.0-34-generic/scripts/mod/empty.dwo.dpkg-new': Operation
  not permitted

Status in linux-hwe-5.11 package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  \linux-headers-5.11.0-34-generic:
Installed: (none)
Candidate: 5.11.0-34.36~20.04.1
Version table:
   5.11.0-34.36~20.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages

  Install failed during latest kernel update.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-headers-5.11.0-34-generic (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Sep  8 20:26:11 2021
  DuplicateSignature:
   package:linux-headers-5.11.0-34-generic:(not installed)
   Unpacking linux-hwe-5.11-headers-5.11.0-34 (5.11.0-34.36~20.04.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-26WFDo/10-linux-hwe-5.11-headers-5.11.0-34_5.11.0-34.36~20.04.1_all.deb
 (--unpack):
unable to create new file 
'/var/lib/dpkg/info/linux-hwe-5.11-headers-5.11.0-34.list-new': Operation not 
permitted
  ErrorMessage: unable to open 
'/usr/src/linux-headers-5.11.0-34-generic/scripts/mod/empty.dwo.dpkg-new': 
Operation not permitted
  InstallationDate: Installed on 2021-02-21 (199 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: linux-hwe-5.11
  Title: package linux-headers-5.11.0-34-generic (not installed) failed to 
install/upgrade: unable to open 
'/usr/src/linux-headers-5.11.0-34-generic/scripts/mod/empty.dwo.dpkg-new': 
Operation not permitted
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1943092/+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 1943092] Re: package linux-headers-5.11.0-34-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-34-generic/scripts/mod/empty.dwo.dp

2021-09-19 Thread Curtis Schroeder

$ sudo apt --fix-broken install
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
  linux-headers-5.11.0-34-generic linux-hwe-5.11-headers-5.11.0-34
The following NEW packages will be installed:
  linux-headers-5.11.0-34-generic
The following packages will be upgraded:
  linux-hwe-5.11-headers-5.11.0-34
1 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
57 not fully installed or removed.
Need to get 0 B/13.1 MB of archives.
After this operation, 90.4 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up libgcrypt20:amd64 (1.8.5-5ubuntu1.1) ...
Setting up libsystemd0:amd64 (245.4-4ubuntu3.13) ...
Setting up libgcrypt20:i386 (1.8.5-5ubuntu1.1) ...
Setting up systemd-timesyncd (245.4-4ubuntu3.13) ...
Setting up systemd (245.4-4ubuntu3.13) ...
Installing new version of config file /etc/dhcp/dhclient-enter-hooks.d/resolved 
...
(Reading database ... 263621 files and directories currently installed.)
Preparing to unpack .../linux-hwe-5.11-headers-5.11.0-34_5.11.0-34.36~20.04.1_al
l.deb ...
Unpacking linux-hwe-5.11-headers-5.11.0-34 (5.11.0-34.36~20.04.1) over (5.11.0-3
4.36~20.04.1) ...
Preparing to unpack .../linux-headers-5.11.0-34-generic_5.11.0-34.36~20.04.1_amd
64.deb ...
Unpacking linux-headers-5.11.0-34-generic (5.11.0-34.36~20.04.1) ...
dpkg: error processing archive /var/cache/apt/archives/linux-headers-5.11.0-34-g
eneric_5.11.0-34.36~20.04.1_amd64.deb (--unpack):
 unable to open '/usr/src/linux-headers-5.11.0-34-generic/scripts/mod/empty.dwo.
dpkg-new': Operation not permitted
Errors were encountered while processing:
 /var/cache/apt/archives/linux-headers-5.11.0-34-generic_5.11.0-34.36~20.04.1_am
d64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1943092

Title:
  package linux-headers-5.11.0-34-generic (not installed) failed to
  install/upgrade: unable to open '/usr/src/linux-
  headers-5.11.0-34-generic/scripts/mod/empty.dwo.dpkg-new': Operation
  not permitted

Status in linux-hwe-5.11 package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  \linux-headers-5.11.0-34-generic:
Installed: (none)
Candidate: 5.11.0-34.36~20.04.1
Version table:
   5.11.0-34.36~20.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages

  Install failed during latest kernel update.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-headers-5.11.0-34-generic (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Sep  8 20:26:11 2021
  DuplicateSignature:
   package:linux-headers-5.11.0-34-generic:(not installed)
   Unpacking linux-hwe-5.11-headers-5.11.0-34 (5.11.0-34.36~20.04.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-26WFDo/10-linux-hwe-5.11-headers-5.11.0-34_5.11.0-34.36~20.04.1_all.deb
 (--unpack):
unable to create new file 
'/var/lib/dpkg/info/linux-hwe-5.11-headers-5.11.0-34.list-new': Operation not 
permitted
  ErrorMessage: unable to open 
'/usr/src/linux-headers-5.11.0-34-generic/scripts/mod/empty.dwo.dpkg-new': 
Operation not permitted
  InstallationDate: Installed on 2021-02-21 (199 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: linux-hwe-5.11
  Title: package linux-headers-5.11.0-34-generic (not installed) failed to 
install/upgrade: unable to open 
'/usr/src/linux-headers-5.11.0-34-generic/scripts/mod/empty.dwo.dpkg-new': 
Operation not permitted
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1943092/+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 1945845] Re: package linux-firmware 1.187.16 failed to install/upgrade: unable to open '/lib/firmware/qcom/a530_zap.mdt.dpkg-new': Operation not permitted

2021-11-04 Thread Curtis Schroeder

Similar problem occurred during upgrade to linux-firmware (1.187.20);
initial install failed, but was able to successfully install after a
reboot.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1945845

Title:
  package linux-firmware 1.187.16 failed to install/upgrade: unable to
  open '/lib/firmware/qcom/a530_zap.mdt.dpkg-new': Operation not
  permitted

Status in linux-firmware package in Ubuntu:
  Invalid

Bug description:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  linux-firmware:
Installed: 1.187.16
Candidate: 1.187.17
Version table:
   1.187.17 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main i386 
Packages
   *** 1.187.16 100
  100 /var/lib/dpkg/status
   1.187 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu focal/main i386 Packages

  Installation failed during system update.

  Unpacking libgl1-mesa-dev:amd64 (21.0.3-0ubuntu0.3~20.04.2) over 
(21.0.3-0ubuntu
  0.3~20.04.1) ...
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-hJ8TxR/47-linux-firmware_1.187.17_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.16
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm2654 F pulseaudio
curts  3716 F pulseaudio
   /dev/snd/controlC0:  gdm2654 F pulseaudio
curts  3716 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Fri Oct  1 19:32:59 2021
  Dependencies:
   
  ErrorMessage: unable to open '/lib/firmware/qcom/a530_zap.mdt.dpkg-new': 
Operation not permitted
  InstallationDate: Installed on 2021-02-21 (222 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  IwConfig:
   lono wireless extensions.
   
   enp42s0   no wireless extensions.
   
   tun0  no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7C91
  PackageArchitecture: all
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz 
root=UUID=7A200ADA-3790-4EBA-8897-FF422F2FB377 quiet splash rootflags=subvol=@
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13
  RfKill:
   
  SourcePackage: linux-firmware
  Title: package linux-firmware 1.187.16 failed to install/upgrade: unable to 
open '/lib/firmware/qcom/a530_zap.mdt.dpkg-new': Operation not permitted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/14/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 1.50
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MPG B550 GAMING EDGE WIFI (MS-7C91)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.50:bd01/14/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C91:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGB550GAMINGEDGEWIFI(MS-7C91):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7C91
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1945845/+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 1960344] Re: Can't mount my encrypted drive with 5.4.0.99-generic

apport information

** Tags added: apport-collected una

** Description changed:

  When I boot with kernel 5.4.0-94 my Linux system properly asks me for
  the passphrase to my encrypted drive (full disk encryption) and then
  after that successfully gets me to the user login screen.  But when I
  updated my kernel to 5.4.0-99, the booting Linux system does not ask me
  for my drive encryption passphrase but instead indicates that it is
  waiting for a drive partition and eventually times out and drops me into
  a busybox session.
  
  The GRUB arguments are identical for both kernels 5.4.0-94 and 5.4.0-99,
  yet I can only successfully get into my Linux system using the 5.4.0-94
  kernel.
  
  I don't know whether the following info is useful or not, since it is
  gathered only from the kernel 5.4.0-94 where I can actually log in.
  
  cat /proc/version_signature :
   Ubuntu 5.4.0-94.106-generic 5.4.157
  
  lspci-vnvn.log is attached.
  
  Output of mount command :
  
  sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
  proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
  udev on /dev type devtmpfs 
(rw,nosuid,noexec,relatime,size=16365340k,nr_inodes=4091335,mode=755)
  devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
  tmpfs on /run type tmpfs 
(rw,nosuid,nodev,noexec,relatime,size=3282420k,mode=755)
  /dev/mapper/vgmint-root on / type ext4 
(rw,relatime,errors=remount-ro,stripe=16)
  securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
  tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
  tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
  tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
  cgroup2 on /sys/fs/cgroup/unified type cgroup2 
(rw,nosuid,nodev,noexec,relatime,nsdelegate)
  cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
  pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
  efivarfs on /sys/firmware/efi/efivars type efivarfs 
(rw,nosuid,nodev,noexec,relatime)
  none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
  cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
  cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
  cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
  cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
  cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
  cgroup on /sys/fs/cgroup/pids type cgroup 
(rw,nosuid,nodev,noexec,relatime,pids)
  cgroup on /sys/fs/cgroup/rdma type cgroup 
(rw,nosuid,nodev,noexec,relatime,rdma)
  cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
  cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
  cgroup on /sys/fs/cgroup/hugetlb type cgroup 
(rw,nosuid,nodev,noexec,relatime,hugetlb)
  cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
  systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=29737)
  hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
  mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
  debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
  tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
  fusectl on /sys/fs/fuse/connections type fusectl 
(rw,nosuid,nodev,noexec,relatime)
  configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
  /dev/mapper/isw_dbbdgggiei_Volume0p2 on /boot type ext4 
(rw,relatime,stripe=16)
  /dev/mapper/isw_dbbdgggiei_Volume0p1 on /boot/efi type vfat 
(rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
  tmpfs on /run/user/1000 type tmpfs 
(rw,nosuid,nodev,relatime,size=3282416k,mode=700,uid=1000,gid=1000)
  /home/.ecryptfs/cfast/.Private on /home/cfast type ecryptfs 
(rw,nosuid,nodev,relatime,ecryptfs_fnek_sig=2e786df13a224d25,ecryptfs_sig=bae1facf9d2afaeb,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_unlink_sigs)
  gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
  binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc 
(rw,nosuid,nodev,noexec,relatime)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.21
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  cfast  1658 F pulseaudio
+  /dev/snd/controlC0:  cfast  1658 F pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: X-Cinnamon
+ DistroRelease: Linux Mint 20.3
+ EcryptfsInUse: Yes
+ InstallationDate: Installed on 2021-12-11 (60 days ago)
+ Installat

[Kernel-packages] [Bug 1960344] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1960344/+attachment/5560010/+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/1960344

Title:
  Can't mount my encrypted drive with 5.4.0.99-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I boot with kernel 5.4.0-94 my Linux system properly asks me for
  the passphrase to my encrypted drive (full disk encryption) and then
  after that successfully gets me to the user login screen.  But when I
  updated my kernel to 5.4.0-99, the booting Linux system does not ask
  me for my drive encryption passphrase but instead indicates that it is
  waiting for a drive partition and eventually times out and drops me
  into a busybox session.

  The GRUB arguments are identical for both kernels 5.4.0-94 and
  5.4.0-99, yet I can only successfully get into my Linux system using
  the 5.4.0-94 kernel.

  I don't know whether the following info is useful or not, since it is
  gathered only from the kernel 5.4.0-94 where I can actually log in.

  cat /proc/version_signature :
   Ubuntu 5.4.0-94.106-generic 5.4.157

  lspci-vnvn.log is attached.

  Output of mount command :

  sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
  proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
  udev on /dev type devtmpfs 
(rw,nosuid,noexec,relatime,size=16365340k,nr_inodes=4091335,mode=755)
  devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
  tmpfs on /run type tmpfs 
(rw,nosuid,nodev,noexec,relatime,size=3282420k,mode=755)
  /dev/mapper/vgmint-root on / type ext4 
(rw,relatime,errors=remount-ro,stripe=16)
  securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
  tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
  tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
  tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
  cgroup2 on /sys/fs/cgroup/unified type cgroup2 
(rw,nosuid,nodev,noexec,relatime,nsdelegate)
  cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
  pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
  efivarfs on /sys/firmware/efi/efivars type efivarfs 
(rw,nosuid,nodev,noexec,relatime)
  none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
  cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
  cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
  cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
  cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
  cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
  cgroup on /sys/fs/cgroup/pids type cgroup 
(rw,nosuid,nodev,noexec,relatime,pids)
  cgroup on /sys/fs/cgroup/rdma type cgroup 
(rw,nosuid,nodev,noexec,relatime,rdma)
  cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
  cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
  cgroup on /sys/fs/cgroup/hugetlb type cgroup 
(rw,nosuid,nodev,noexec,relatime,hugetlb)
  cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
  systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=29737)
  hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
  mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
  debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
  tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
  fusectl on /sys/fs/fuse/connections type fusectl 
(rw,nosuid,nodev,noexec,relatime)
  configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
  /dev/mapper/isw_dbbdgggiei_Volume0p2 on /boot type ext4 
(rw,relatime,stripe=16)
  /dev/mapper/isw_dbbdgggiei_Volume0p1 on /boot/efi type vfat 
(rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
  tmpfs on /run/user/1000 type tmpfs 
(rw,nosuid,nodev,relatime,size=3282416k,mode=700,uid=1000,gid=1000)
  /home/.ecryptfs/cfast/.Private on /home/cfast type ecryptfs 
(rw,nosuid,nodev,relatime,ecryptfs_fnek_sig=2e786df13a224d25,ecryptfs_sig=bae1facf9d2afaeb,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_unlink_sigs)
  gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
  binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc 
(rw,nosuid,nodev,noexec,relatime)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64

[Kernel-packages] [Bug 1960344] Lsusb-t.txt

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1960344/+attachment/5560014/+files/Lsusb-t.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/1960344

Title:
  Can't mount my encrypted drive with 5.4.0.99-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I boot with kernel 5.4.0-94 my Linux system properly asks me for
  the passphrase to my encrypted drive (full disk encryption) and then
  after that successfully gets me to the user login screen.  But when I
  updated my kernel to 5.4.0-99, the booting Linux system does not ask
  me for my drive encryption passphrase but instead indicates that it is
  waiting for a drive partition and eventually times out and drops me
  into a busybox session.

  The GRUB arguments are identical for both kernels 5.4.0-94 and
  5.4.0-99, yet I can only successfully get into my Linux system using
  the 5.4.0-94 kernel.

  I don't know whether the following info is useful or not, since it is
  gathered only from the kernel 5.4.0-94 where I can actually log in.

  cat /proc/version_signature :
   Ubuntu 5.4.0-94.106-generic 5.4.157

  lspci-vnvn.log is attached.

  Output of mount command :

  sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
  proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
  udev on /dev type devtmpfs 
(rw,nosuid,noexec,relatime,size=16365340k,nr_inodes=4091335,mode=755)
  devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
  tmpfs on /run type tmpfs 
(rw,nosuid,nodev,noexec,relatime,size=3282420k,mode=755)
  /dev/mapper/vgmint-root on / type ext4 
(rw,relatime,errors=remount-ro,stripe=16)
  securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
  tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
  tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
  tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
  cgroup2 on /sys/fs/cgroup/unified type cgroup2 
(rw,nosuid,nodev,noexec,relatime,nsdelegate)
  cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
  pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
  efivarfs on /sys/firmware/efi/efivars type efivarfs 
(rw,nosuid,nodev,noexec,relatime)
  none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
  cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
  cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
  cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
  cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
  cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
  cgroup on /sys/fs/cgroup/pids type cgroup 
(rw,nosuid,nodev,noexec,relatime,pids)
  cgroup on /sys/fs/cgroup/rdma type cgroup 
(rw,nosuid,nodev,noexec,relatime,rdma)
  cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
  cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
  cgroup on /sys/fs/cgroup/hugetlb type cgroup 
(rw,nosuid,nodev,noexec,relatime,hugetlb)
  cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
  systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=29737)
  hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
  mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
  debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
  tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
  fusectl on /sys/fs/fuse/connections type fusectl 
(rw,nosuid,nodev,noexec,relatime)
  configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
  /dev/mapper/isw_dbbdgggiei_Volume0p2 on /boot type ext4 
(rw,relatime,stripe=16)
  /dev/mapper/isw_dbbdgggiei_Volume0p1 on /boot/efi type vfat 
(rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
  tmpfs on /run/user/1000 type tmpfs 
(rw,nosuid,nodev,relatime,size=3282416k,mode=700,uid=1000,gid=1000)
  /home/.ecryptfs/cfast/.Private on /home/cfast type ecryptfs 
(rw,nosuid,nodev,relatime,ecryptfs_fnek_sig=2e786df13a224d25,ecryptfs_sig=bae1facf9d2afaeb,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_unlink_sigs)
  gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
  binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc 
(rw,nosuid,nodev,noexec,relatime)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevic

[Kernel-packages] [Bug 1960344] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1960344/+attachment/5560019/+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/1960344

Title:
  Can't mount my encrypted drive with 5.4.0.99-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I boot with kernel 5.4.0-94 my Linux system properly asks me for
  the passphrase to my encrypted drive (full disk encryption) and then
  after that successfully gets me to the user login screen.  But when I
  updated my kernel to 5.4.0-99, the booting Linux system does not ask
  me for my drive encryption passphrase but instead indicates that it is
  waiting for a drive partition and eventually times out and drops me
  into a busybox session.

  The GRUB arguments are identical for both kernels 5.4.0-94 and
  5.4.0-99, yet I can only successfully get into my Linux system using
  the 5.4.0-94 kernel.

  I don't know whether the following info is useful or not, since it is
  gathered only from the kernel 5.4.0-94 where I can actually log in.

  cat /proc/version_signature :
   Ubuntu 5.4.0-94.106-generic 5.4.157

  lspci-vnvn.log is attached.

  Output of mount command :

  sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
  proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
  udev on /dev type devtmpfs 
(rw,nosuid,noexec,relatime,size=16365340k,nr_inodes=4091335,mode=755)
  devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
  tmpfs on /run type tmpfs 
(rw,nosuid,nodev,noexec,relatime,size=3282420k,mode=755)
  /dev/mapper/vgmint-root on / type ext4 
(rw,relatime,errors=remount-ro,stripe=16)
  securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
  tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
  tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
  tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
  cgroup2 on /sys/fs/cgroup/unified type cgroup2 
(rw,nosuid,nodev,noexec,relatime,nsdelegate)
  cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
  pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
  efivarfs on /sys/firmware/efi/efivars type efivarfs 
(rw,nosuid,nodev,noexec,relatime)
  none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
  cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
  cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
  cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
  cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
  cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
  cgroup on /sys/fs/cgroup/pids type cgroup 
(rw,nosuid,nodev,noexec,relatime,pids)
  cgroup on /sys/fs/cgroup/rdma type cgroup 
(rw,nosuid,nodev,noexec,relatime,rdma)
  cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
  cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
  cgroup on /sys/fs/cgroup/hugetlb type cgroup 
(rw,nosuid,nodev,noexec,relatime,hugetlb)
  cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
  systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=29737)
  hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
  mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
  debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
  tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
  fusectl on /sys/fs/fuse/connections type fusectl 
(rw,nosuid,nodev,noexec,relatime)
  configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
  /dev/mapper/isw_dbbdgggiei_Volume0p2 on /boot type ext4 
(rw,relatime,stripe=16)
  /dev/mapper/isw_dbbdgggiei_Volume0p1 on /boot/efi type vfat 
(rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
  tmpfs on /run/user/1000 type tmpfs 
(rw,nosuid,nodev,relatime,size=3282416k,mode=700,uid=1000,gid=1000)
  /home/.ecryptfs/cfast/.Private on /home/cfast type ecryptfs 
(rw,nosuid,nodev,relatime,ecryptfs_fnek_sig=2e786df13a224d25,ecryptfs_sig=bae1facf9d2afaeb,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_unlink_sigs)
  gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
  binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc 
(rw,nosuid,nodev,noexec,relatime)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd6

[Kernel-packages] [Bug 1960344] CRDA.txt

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1960344/+attachment/5560009/+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/1960344

Title:
  Can't mount my encrypted drive with 5.4.0.99-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I boot with kernel 5.4.0-94 my Linux system properly asks me for
  the passphrase to my encrypted drive (full disk encryption) and then
  after that successfully gets me to the user login screen.  But when I
  updated my kernel to 5.4.0-99, the booting Linux system does not ask
  me for my drive encryption passphrase but instead indicates that it is
  waiting for a drive partition and eventually times out and drops me
  into a busybox session.

  The GRUB arguments are identical for both kernels 5.4.0-94 and
  5.4.0-99, yet I can only successfully get into my Linux system using
  the 5.4.0-94 kernel.

  I don't know whether the following info is useful or not, since it is
  gathered only from the kernel 5.4.0-94 where I can actually log in.

  cat /proc/version_signature :
   Ubuntu 5.4.0-94.106-generic 5.4.157

  lspci-vnvn.log is attached.

  Output of mount command :

  sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
  proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
  udev on /dev type devtmpfs 
(rw,nosuid,noexec,relatime,size=16365340k,nr_inodes=4091335,mode=755)
  devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
  tmpfs on /run type tmpfs 
(rw,nosuid,nodev,noexec,relatime,size=3282420k,mode=755)
  /dev/mapper/vgmint-root on / type ext4 
(rw,relatime,errors=remount-ro,stripe=16)
  securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
  tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
  tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
  tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
  cgroup2 on /sys/fs/cgroup/unified type cgroup2 
(rw,nosuid,nodev,noexec,relatime,nsdelegate)
  cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
  pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
  efivarfs on /sys/firmware/efi/efivars type efivarfs 
(rw,nosuid,nodev,noexec,relatime)
  none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
  cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
  cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
  cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
  cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
  cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
  cgroup on /sys/fs/cgroup/pids type cgroup 
(rw,nosuid,nodev,noexec,relatime,pids)
  cgroup on /sys/fs/cgroup/rdma type cgroup 
(rw,nosuid,nodev,noexec,relatime,rdma)
  cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
  cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
  cgroup on /sys/fs/cgroup/hugetlb type cgroup 
(rw,nosuid,nodev,noexec,relatime,hugetlb)
  cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
  systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=29737)
  hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
  mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
  debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
  tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
  fusectl on /sys/fs/fuse/connections type fusectl 
(rw,nosuid,nodev,noexec,relatime)
  configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
  /dev/mapper/isw_dbbdgggiei_Volume0p2 on /boot type ext4 
(rw,relatime,stripe=16)
  /dev/mapper/isw_dbbdgggiei_Volume0p1 on /boot/efi type vfat 
(rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
  tmpfs on /run/user/1000 type tmpfs 
(rw,nosuid,nodev,relatime,size=3282416k,mode=700,uid=1000,gid=1000)
  /home/.ecryptfs/cfast/.Private on /home/cfast type ecryptfs 
(rw,nosuid,nodev,relatime,ecryptfs_fnek_sig=2e786df13a224d25,ecryptfs_sig=bae1facf9d2afaeb,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_unlink_sigs)
  gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
  binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc 
(rw,nosuid,nodev,noexec,relatime)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse

[Kernel-packages] [Bug 1960344] Lspci-vt.txt

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1960344/+attachment/5560012/+files/Lspci-vt.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/1960344

Title:
  Can't mount my encrypted drive with 5.4.0.99-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I boot with kernel 5.4.0-94 my Linux system properly asks me for
  the passphrase to my encrypted drive (full disk encryption) and then
  after that successfully gets me to the user login screen.  But when I
  updated my kernel to 5.4.0-99, the booting Linux system does not ask
  me for my drive encryption passphrase but instead indicates that it is
  waiting for a drive partition and eventually times out and drops me
  into a busybox session.

  The GRUB arguments are identical for both kernels 5.4.0-94 and
  5.4.0-99, yet I can only successfully get into my Linux system using
  the 5.4.0-94 kernel.

  I don't know whether the following info is useful or not, since it is
  gathered only from the kernel 5.4.0-94 where I can actually log in.

  cat /proc/version_signature :
   Ubuntu 5.4.0-94.106-generic 5.4.157

  lspci-vnvn.log is attached.

  Output of mount command :

  sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
  proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
  udev on /dev type devtmpfs 
(rw,nosuid,noexec,relatime,size=16365340k,nr_inodes=4091335,mode=755)
  devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
  tmpfs on /run type tmpfs 
(rw,nosuid,nodev,noexec,relatime,size=3282420k,mode=755)
  /dev/mapper/vgmint-root on / type ext4 
(rw,relatime,errors=remount-ro,stripe=16)
  securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
  tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
  tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
  tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
  cgroup2 on /sys/fs/cgroup/unified type cgroup2 
(rw,nosuid,nodev,noexec,relatime,nsdelegate)
  cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
  pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
  efivarfs on /sys/firmware/efi/efivars type efivarfs 
(rw,nosuid,nodev,noexec,relatime)
  none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
  cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
  cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
  cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
  cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
  cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
  cgroup on /sys/fs/cgroup/pids type cgroup 
(rw,nosuid,nodev,noexec,relatime,pids)
  cgroup on /sys/fs/cgroup/rdma type cgroup 
(rw,nosuid,nodev,noexec,relatime,rdma)
  cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
  cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
  cgroup on /sys/fs/cgroup/hugetlb type cgroup 
(rw,nosuid,nodev,noexec,relatime,hugetlb)
  cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
  systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=29737)
  hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
  mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
  debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
  tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
  fusectl on /sys/fs/fuse/connections type fusectl 
(rw,nosuid,nodev,noexec,relatime)
  configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
  /dev/mapper/isw_dbbdgggiei_Volume0p2 on /boot type ext4 
(rw,relatime,stripe=16)
  /dev/mapper/isw_dbbdgggiei_Volume0p1 on /boot/efi type vfat 
(rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
  tmpfs on /run/user/1000 type tmpfs 
(rw,nosuid,nodev,relatime,size=3282416k,mode=700,uid=1000,gid=1000)
  /home/.ecryptfs/cfast/.Private on /home/cfast type ecryptfs 
(rw,nosuid,nodev,relatime,ecryptfs_fnek_sig=2e786df13a224d25,ecryptfs_sig=bae1facf9d2afaeb,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_unlink_sigs)
  gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
  binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc 
(rw,nosuid,nodev,noexec,relatime)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDev

[Kernel-packages] [Bug 1960344] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1960344/+attachment/5560018/+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/1960344

Title:
  Can't mount my encrypted drive with 5.4.0.99-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I boot with kernel 5.4.0-94 my Linux system properly asks me for
  the passphrase to my encrypted drive (full disk encryption) and then
  after that successfully gets me to the user login screen.  But when I
  updated my kernel to 5.4.0-99, the booting Linux system does not ask
  me for my drive encryption passphrase but instead indicates that it is
  waiting for a drive partition and eventually times out and drops me
  into a busybox session.

  The GRUB arguments are identical for both kernels 5.4.0-94 and
  5.4.0-99, yet I can only successfully get into my Linux system using
  the 5.4.0-94 kernel.

  I don't know whether the following info is useful or not, since it is
  gathered only from the kernel 5.4.0-94 where I can actually log in.

  cat /proc/version_signature :
   Ubuntu 5.4.0-94.106-generic 5.4.157

  lspci-vnvn.log is attached.

  Output of mount command :

  sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
  proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
  udev on /dev type devtmpfs 
(rw,nosuid,noexec,relatime,size=16365340k,nr_inodes=4091335,mode=755)
  devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
  tmpfs on /run type tmpfs 
(rw,nosuid,nodev,noexec,relatime,size=3282420k,mode=755)
  /dev/mapper/vgmint-root on / type ext4 
(rw,relatime,errors=remount-ro,stripe=16)
  securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
  tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
  tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
  tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
  cgroup2 on /sys/fs/cgroup/unified type cgroup2 
(rw,nosuid,nodev,noexec,relatime,nsdelegate)
  cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
  pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
  efivarfs on /sys/firmware/efi/efivars type efivarfs 
(rw,nosuid,nodev,noexec,relatime)
  none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
  cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
  cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
  cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
  cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
  cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
  cgroup on /sys/fs/cgroup/pids type cgroup 
(rw,nosuid,nodev,noexec,relatime,pids)
  cgroup on /sys/fs/cgroup/rdma type cgroup 
(rw,nosuid,nodev,noexec,relatime,rdma)
  cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
  cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
  cgroup on /sys/fs/cgroup/hugetlb type cgroup 
(rw,nosuid,nodev,noexec,relatime,hugetlb)
  cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
  systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=29737)
  hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
  mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
  debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
  tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
  fusectl on /sys/fs/fuse/connections type fusectl 
(rw,nosuid,nodev,noexec,relatime)
  configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
  /dev/mapper/isw_dbbdgggiei_Volume0p2 on /boot type ext4 
(rw,relatime,stripe=16)
  /dev/mapper/isw_dbbdgggiei_Volume0p1 on /boot/efi type vfat 
(rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
  tmpfs on /run/user/1000 type tmpfs 
(rw,nosuid,nodev,relatime,size=3282416k,mode=700,uid=1000,gid=1000)
  /home/.ecryptfs/cfast/.Private on /home/cfast type ecryptfs 
(rw,nosuid,nodev,relatime,ecryptfs_fnek_sig=2e786df13a224d25,ecryptfs_sig=bae1facf9d2afaeb,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_unlink_sigs)
  gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
  binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc 
(rw,nosuid,nodev,noexec,relatime)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  Au

[Kernel-packages] [Bug 1960344] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1960344/+attachment/5560011/+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/1960344

Title:
  Can't mount my encrypted drive with 5.4.0.99-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I boot with kernel 5.4.0-94 my Linux system properly asks me for
  the passphrase to my encrypted drive (full disk encryption) and then
  after that successfully gets me to the user login screen.  But when I
  updated my kernel to 5.4.0-99, the booting Linux system does not ask
  me for my drive encryption passphrase but instead indicates that it is
  waiting for a drive partition and eventually times out and drops me
  into a busybox session.

  The GRUB arguments are identical for both kernels 5.4.0-94 and
  5.4.0-99, yet I can only successfully get into my Linux system using
  the 5.4.0-94 kernel.

  I don't know whether the following info is useful or not, since it is
  gathered only from the kernel 5.4.0-94 where I can actually log in.

  cat /proc/version_signature :
   Ubuntu 5.4.0-94.106-generic 5.4.157

  lspci-vnvn.log is attached.

  Output of mount command :

  sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
  proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
  udev on /dev type devtmpfs 
(rw,nosuid,noexec,relatime,size=16365340k,nr_inodes=4091335,mode=755)
  devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
  tmpfs on /run type tmpfs 
(rw,nosuid,nodev,noexec,relatime,size=3282420k,mode=755)
  /dev/mapper/vgmint-root on / type ext4 
(rw,relatime,errors=remount-ro,stripe=16)
  securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
  tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
  tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
  tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
  cgroup2 on /sys/fs/cgroup/unified type cgroup2 
(rw,nosuid,nodev,noexec,relatime,nsdelegate)
  cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
  pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
  efivarfs on /sys/firmware/efi/efivars type efivarfs 
(rw,nosuid,nodev,noexec,relatime)
  none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
  cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
  cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
  cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
  cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
  cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
  cgroup on /sys/fs/cgroup/pids type cgroup 
(rw,nosuid,nodev,noexec,relatime,pids)
  cgroup on /sys/fs/cgroup/rdma type cgroup 
(rw,nosuid,nodev,noexec,relatime,rdma)
  cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
  cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
  cgroup on /sys/fs/cgroup/hugetlb type cgroup 
(rw,nosuid,nodev,noexec,relatime,hugetlb)
  cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
  systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=29737)
  hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
  mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
  debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
  tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
  fusectl on /sys/fs/fuse/connections type fusectl 
(rw,nosuid,nodev,noexec,relatime)
  configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
  /dev/mapper/isw_dbbdgggiei_Volume0p2 on /boot type ext4 
(rw,relatime,stripe=16)
  /dev/mapper/isw_dbbdgggiei_Volume0p1 on /boot/efi type vfat 
(rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
  tmpfs on /run/user/1000 type tmpfs 
(rw,nosuid,nodev,relatime,size=3282416k,mode=700,uid=1000,gid=1000)
  /home/.ecryptfs/cfast/.Private on /home/cfast type ecryptfs 
(rw,nosuid,nodev,relatime,ecryptfs_fnek_sig=2e786df13a224d25,ecryptfs_sig=bae1facf9d2afaeb,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_unlink_sigs)
  gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
  binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc 
(rw,nosuid,nodev,noexec,relatime)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInU

[Kernel-packages] [Bug 1960344] Lsusb-v.txt

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1960344/+attachment/5560015/+files/Lsusb-v.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/1960344

Title:
  Can't mount my encrypted drive with 5.4.0.99-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I boot with kernel 5.4.0-94 my Linux system properly asks me for
  the passphrase to my encrypted drive (full disk encryption) and then
  after that successfully gets me to the user login screen.  But when I
  updated my kernel to 5.4.0-99, the booting Linux system does not ask
  me for my drive encryption passphrase but instead indicates that it is
  waiting for a drive partition and eventually times out and drops me
  into a busybox session.

  The GRUB arguments are identical for both kernels 5.4.0-94 and
  5.4.0-99, yet I can only successfully get into my Linux system using
  the 5.4.0-94 kernel.

  I don't know whether the following info is useful or not, since it is
  gathered only from the kernel 5.4.0-94 where I can actually log in.

  cat /proc/version_signature :
   Ubuntu 5.4.0-94.106-generic 5.4.157

  lspci-vnvn.log is attached.

  Output of mount command :

  sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
  proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
  udev on /dev type devtmpfs 
(rw,nosuid,noexec,relatime,size=16365340k,nr_inodes=4091335,mode=755)
  devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
  tmpfs on /run type tmpfs 
(rw,nosuid,nodev,noexec,relatime,size=3282420k,mode=755)
  /dev/mapper/vgmint-root on / type ext4 
(rw,relatime,errors=remount-ro,stripe=16)
  securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
  tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
  tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
  tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
  cgroup2 on /sys/fs/cgroup/unified type cgroup2 
(rw,nosuid,nodev,noexec,relatime,nsdelegate)
  cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
  pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
  efivarfs on /sys/firmware/efi/efivars type efivarfs 
(rw,nosuid,nodev,noexec,relatime)
  none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
  cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
  cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
  cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
  cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
  cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
  cgroup on /sys/fs/cgroup/pids type cgroup 
(rw,nosuid,nodev,noexec,relatime,pids)
  cgroup on /sys/fs/cgroup/rdma type cgroup 
(rw,nosuid,nodev,noexec,relatime,rdma)
  cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
  cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
  cgroup on /sys/fs/cgroup/hugetlb type cgroup 
(rw,nosuid,nodev,noexec,relatime,hugetlb)
  cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
  systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=29737)
  hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
  mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
  debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
  tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
  fusectl on /sys/fs/fuse/connections type fusectl 
(rw,nosuid,nodev,noexec,relatime)
  configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
  /dev/mapper/isw_dbbdgggiei_Volume0p2 on /boot type ext4 
(rw,relatime,stripe=16)
  /dev/mapper/isw_dbbdgggiei_Volume0p1 on /boot/efi type vfat 
(rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
  tmpfs on /run/user/1000 type tmpfs 
(rw,nosuid,nodev,relatime,size=3282416k,mode=700,uid=1000,gid=1000)
  /home/.ecryptfs/cfast/.Private on /home/cfast type ecryptfs 
(rw,nosuid,nodev,relatime,ecryptfs_fnek_sig=2e786df13a224d25,ecryptfs_sig=bae1facf9d2afaeb,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_unlink_sigs)
  gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
  binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc 
(rw,nosuid,nodev,noexec,relatime)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevic

[Kernel-packages] [Bug 1960344] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1960344/+attachment/5560020/+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/1960344

Title:
  Can't mount my encrypted drive with 5.4.0.99-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I boot with kernel 5.4.0-94 my Linux system properly asks me for
  the passphrase to my encrypted drive (full disk encryption) and then
  after that successfully gets me to the user login screen.  But when I
  updated my kernel to 5.4.0-99, the booting Linux system does not ask
  me for my drive encryption passphrase but instead indicates that it is
  waiting for a drive partition and eventually times out and drops me
  into a busybox session.

  The GRUB arguments are identical for both kernels 5.4.0-94 and
  5.4.0-99, yet I can only successfully get into my Linux system using
  the 5.4.0-94 kernel.

  I don't know whether the following info is useful or not, since it is
  gathered only from the kernel 5.4.0-94 where I can actually log in.

  cat /proc/version_signature :
   Ubuntu 5.4.0-94.106-generic 5.4.157

  lspci-vnvn.log is attached.

  Output of mount command :

  sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
  proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
  udev on /dev type devtmpfs 
(rw,nosuid,noexec,relatime,size=16365340k,nr_inodes=4091335,mode=755)
  devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
  tmpfs on /run type tmpfs 
(rw,nosuid,nodev,noexec,relatime,size=3282420k,mode=755)
  /dev/mapper/vgmint-root on / type ext4 
(rw,relatime,errors=remount-ro,stripe=16)
  securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
  tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
  tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
  tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
  cgroup2 on /sys/fs/cgroup/unified type cgroup2 
(rw,nosuid,nodev,noexec,relatime,nsdelegate)
  cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
  pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
  efivarfs on /sys/firmware/efi/efivars type efivarfs 
(rw,nosuid,nodev,noexec,relatime)
  none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
  cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
  cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
  cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
  cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
  cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
  cgroup on /sys/fs/cgroup/pids type cgroup 
(rw,nosuid,nodev,noexec,relatime,pids)
  cgroup on /sys/fs/cgroup/rdma type cgroup 
(rw,nosuid,nodev,noexec,relatime,rdma)
  cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
  cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
  cgroup on /sys/fs/cgroup/hugetlb type cgroup 
(rw,nosuid,nodev,noexec,relatime,hugetlb)
  cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
  systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=29737)
  hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
  mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
  debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
  tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
  fusectl on /sys/fs/fuse/connections type fusectl 
(rw,nosuid,nodev,noexec,relatime)
  configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
  /dev/mapper/isw_dbbdgggiei_Volume0p2 on /boot type ext4 
(rw,relatime,stripe=16)
  /dev/mapper/isw_dbbdgggiei_Volume0p1 on /boot/efi type vfat 
(rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
  tmpfs on /run/user/1000 type tmpfs 
(rw,nosuid,nodev,relatime,size=3282416k,mode=700,uid=1000,gid=1000)
  /home/.ecryptfs/cfast/.Private on /home/cfast type ecryptfs 
(rw,nosuid,nodev,relatime,ecryptfs_fnek_sig=2e786df13a224d25,ecryptfs_sig=bae1facf9d2afaeb,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_unlink_sigs)
  gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
  binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc 
(rw,nosuid,nodev,noexec,relatime)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  Au

[Kernel-packages] [Bug 1960344] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1960344/+attachment/5560017/+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/1960344

Title:
  Can't mount my encrypted drive with 5.4.0.99-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I boot with kernel 5.4.0-94 my Linux system properly asks me for
  the passphrase to my encrypted drive (full disk encryption) and then
  after that successfully gets me to the user login screen.  But when I
  updated my kernel to 5.4.0-99, the booting Linux system does not ask
  me for my drive encryption passphrase but instead indicates that it is
  waiting for a drive partition and eventually times out and drops me
  into a busybox session.

  The GRUB arguments are identical for both kernels 5.4.0-94 and
  5.4.0-99, yet I can only successfully get into my Linux system using
  the 5.4.0-94 kernel.

  I don't know whether the following info is useful or not, since it is
  gathered only from the kernel 5.4.0-94 where I can actually log in.

  cat /proc/version_signature :
   Ubuntu 5.4.0-94.106-generic 5.4.157

  lspci-vnvn.log is attached.

  Output of mount command :

  sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
  proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
  udev on /dev type devtmpfs 
(rw,nosuid,noexec,relatime,size=16365340k,nr_inodes=4091335,mode=755)
  devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
  tmpfs on /run type tmpfs 
(rw,nosuid,nodev,noexec,relatime,size=3282420k,mode=755)
  /dev/mapper/vgmint-root on / type ext4 
(rw,relatime,errors=remount-ro,stripe=16)
  securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
  tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
  tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
  tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
  cgroup2 on /sys/fs/cgroup/unified type cgroup2 
(rw,nosuid,nodev,noexec,relatime,nsdelegate)
  cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
  pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
  efivarfs on /sys/firmware/efi/efivars type efivarfs 
(rw,nosuid,nodev,noexec,relatime)
  none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
  cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
  cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
  cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
  cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
  cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
  cgroup on /sys/fs/cgroup/pids type cgroup 
(rw,nosuid,nodev,noexec,relatime,pids)
  cgroup on /sys/fs/cgroup/rdma type cgroup 
(rw,nosuid,nodev,noexec,relatime,rdma)
  cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
  cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
  cgroup on /sys/fs/cgroup/hugetlb type cgroup 
(rw,nosuid,nodev,noexec,relatime,hugetlb)
  cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
  systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=29737)
  hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
  mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
  debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
  tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
  fusectl on /sys/fs/fuse/connections type fusectl 
(rw,nosuid,nodev,noexec,relatime)
  configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
  /dev/mapper/isw_dbbdgggiei_Volume0p2 on /boot type ext4 
(rw,relatime,stripe=16)
  /dev/mapper/isw_dbbdgggiei_Volume0p1 on /boot/efi type vfat 
(rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
  tmpfs on /run/user/1000 type tmpfs 
(rw,nosuid,nodev,relatime,size=3282416k,mode=700,uid=1000,gid=1000)
  /home/.ecryptfs/cfast/.Private on /home/cfast type ecryptfs 
(rw,nosuid,nodev,relatime,ecryptfs_fnek_sig=2e786df13a224d25,ecryptfs_sig=bae1facf9d2afaeb,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_unlink_sigs)
  gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
  binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc 
(rw,nosuid,nodev,noexec,relatime)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architectu

[Kernel-packages] [Bug 1960344] Lsusb.txt

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1960344/+attachment/5560013/+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/1960344

Title:
  Can't mount my encrypted drive with 5.4.0.99-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I boot with kernel 5.4.0-94 my Linux system properly asks me for
  the passphrase to my encrypted drive (full disk encryption) and then
  after that successfully gets me to the user login screen.  But when I
  updated my kernel to 5.4.0-99, the booting Linux system does not ask
  me for my drive encryption passphrase but instead indicates that it is
  waiting for a drive partition and eventually times out and drops me
  into a busybox session.

  The GRUB arguments are identical for both kernels 5.4.0-94 and
  5.4.0-99, yet I can only successfully get into my Linux system using
  the 5.4.0-94 kernel.

  I don't know whether the following info is useful or not, since it is
  gathered only from the kernel 5.4.0-94 where I can actually log in.

  cat /proc/version_signature :
   Ubuntu 5.4.0-94.106-generic 5.4.157

  lspci-vnvn.log is attached.

  Output of mount command :

  sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
  proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
  udev on /dev type devtmpfs 
(rw,nosuid,noexec,relatime,size=16365340k,nr_inodes=4091335,mode=755)
  devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
  tmpfs on /run type tmpfs 
(rw,nosuid,nodev,noexec,relatime,size=3282420k,mode=755)
  /dev/mapper/vgmint-root on / type ext4 
(rw,relatime,errors=remount-ro,stripe=16)
  securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
  tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
  tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
  tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
  cgroup2 on /sys/fs/cgroup/unified type cgroup2 
(rw,nosuid,nodev,noexec,relatime,nsdelegate)
  cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
  pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
  efivarfs on /sys/firmware/efi/efivars type efivarfs 
(rw,nosuid,nodev,noexec,relatime)
  none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
  cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
  cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
  cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
  cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
  cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
  cgroup on /sys/fs/cgroup/pids type cgroup 
(rw,nosuid,nodev,noexec,relatime,pids)
  cgroup on /sys/fs/cgroup/rdma type cgroup 
(rw,nosuid,nodev,noexec,relatime,rdma)
  cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
  cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
  cgroup on /sys/fs/cgroup/hugetlb type cgroup 
(rw,nosuid,nodev,noexec,relatime,hugetlb)
  cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
  systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=29737)
  hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
  mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
  debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
  tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
  fusectl on /sys/fs/fuse/connections type fusectl 
(rw,nosuid,nodev,noexec,relatime)
  configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
  /dev/mapper/isw_dbbdgggiei_Volume0p2 on /boot type ext4 
(rw,relatime,stripe=16)
  /dev/mapper/isw_dbbdgggiei_Volume0p1 on /boot/efi type vfat 
(rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
  tmpfs on /run/user/1000 type tmpfs 
(rw,nosuid,nodev,relatime,size=3282416k,mode=700,uid=1000,gid=1000)
  /home/.ecryptfs/cfast/.Private on /home/cfast type ecryptfs 
(rw,nosuid,nodev,relatime,ecryptfs_fnek_sig=2e786df13a224d25,ecryptfs_sig=bae1facf9d2afaeb,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_unlink_sigs)
  gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
  binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc 
(rw,nosuid,nodev,noexec,relatime)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInU

[Kernel-packages] [Bug 1960344] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1960344/+attachment/5560016/+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/1960344

Title:
  Can't mount my encrypted drive with 5.4.0.99-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I boot with kernel 5.4.0-94 my Linux system properly asks me for
  the passphrase to my encrypted drive (full disk encryption) and then
  after that successfully gets me to the user login screen.  But when I
  updated my kernel to 5.4.0-99, the booting Linux system does not ask
  me for my drive encryption passphrase but instead indicates that it is
  waiting for a drive partition and eventually times out and drops me
  into a busybox session.

  The GRUB arguments are identical for both kernels 5.4.0-94 and
  5.4.0-99, yet I can only successfully get into my Linux system using
  the 5.4.0-94 kernel.

  I don't know whether the following info is useful or not, since it is
  gathered only from the kernel 5.4.0-94 where I can actually log in.

  cat /proc/version_signature :
   Ubuntu 5.4.0-94.106-generic 5.4.157

  lspci-vnvn.log is attached.

  Output of mount command :

  sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
  proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
  udev on /dev type devtmpfs 
(rw,nosuid,noexec,relatime,size=16365340k,nr_inodes=4091335,mode=755)
  devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
  tmpfs on /run type tmpfs 
(rw,nosuid,nodev,noexec,relatime,size=3282420k,mode=755)
  /dev/mapper/vgmint-root on / type ext4 
(rw,relatime,errors=remount-ro,stripe=16)
  securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
  tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
  tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
  tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
  cgroup2 on /sys/fs/cgroup/unified type cgroup2 
(rw,nosuid,nodev,noexec,relatime,nsdelegate)
  cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
  pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
  efivarfs on /sys/firmware/efi/efivars type efivarfs 
(rw,nosuid,nodev,noexec,relatime)
  none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
  cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
  cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
  cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
  cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
  cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
  cgroup on /sys/fs/cgroup/pids type cgroup 
(rw,nosuid,nodev,noexec,relatime,pids)
  cgroup on /sys/fs/cgroup/rdma type cgroup 
(rw,nosuid,nodev,noexec,relatime,rdma)
  cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
  cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
  cgroup on /sys/fs/cgroup/hugetlb type cgroup 
(rw,nosuid,nodev,noexec,relatime,hugetlb)
  cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
  systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=29737)
  hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
  mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
  debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
  tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
  fusectl on /sys/fs/fuse/connections type fusectl 
(rw,nosuid,nodev,noexec,relatime)
  configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
  /dev/mapper/isw_dbbdgggiei_Volume0p2 on /boot type ext4 
(rw,relatime,stripe=16)
  /dev/mapper/isw_dbbdgggiei_Volume0p1 on /boot/efi type vfat 
(rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
  tmpfs on /run/user/1000 type tmpfs 
(rw,nosuid,nodev,relatime,size=3282416k,mode=700,uid=1000,gid=1000)
  /home/.ecryptfs/cfast/.Private on /home/cfast type ecryptfs 
(rw,nosuid,nodev,relatime,ecryptfs_fnek_sig=2e786df13a224d25,ecryptfs_sig=bae1facf9d2afaeb,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_unlink_sigs)
  gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
  binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc 
(rw,nosuid,nodev,noexec,relatime)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  Au

[Kernel-packages] [Bug 1960344] acpidump.txt

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1960344/+attachment/5560024/+files/acpidump.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/1960344

Title:
  Can't mount my encrypted drive with 5.4.0.99-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I boot with kernel 5.4.0-94 my Linux system properly asks me for
  the passphrase to my encrypted drive (full disk encryption) and then
  after that successfully gets me to the user login screen.  But when I
  updated my kernel to 5.4.0-99, the booting Linux system does not ask
  me for my drive encryption passphrase but instead indicates that it is
  waiting for a drive partition and eventually times out and drops me
  into a busybox session.

  The GRUB arguments are identical for both kernels 5.4.0-94 and
  5.4.0-99, yet I can only successfully get into my Linux system using
  the 5.4.0-94 kernel.

  I don't know whether the following info is useful or not, since it is
  gathered only from the kernel 5.4.0-94 where I can actually log in.

  cat /proc/version_signature :
   Ubuntu 5.4.0-94.106-generic 5.4.157

  lspci-vnvn.log is attached.

  Output of mount command :

  sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
  proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
  udev on /dev type devtmpfs 
(rw,nosuid,noexec,relatime,size=16365340k,nr_inodes=4091335,mode=755)
  devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
  tmpfs on /run type tmpfs 
(rw,nosuid,nodev,noexec,relatime,size=3282420k,mode=755)
  /dev/mapper/vgmint-root on / type ext4 
(rw,relatime,errors=remount-ro,stripe=16)
  securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
  tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
  tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
  tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
  cgroup2 on /sys/fs/cgroup/unified type cgroup2 
(rw,nosuid,nodev,noexec,relatime,nsdelegate)
  cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
  pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
  efivarfs on /sys/firmware/efi/efivars type efivarfs 
(rw,nosuid,nodev,noexec,relatime)
  none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
  cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
  cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
  cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
  cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
  cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
  cgroup on /sys/fs/cgroup/pids type cgroup 
(rw,nosuid,nodev,noexec,relatime,pids)
  cgroup on /sys/fs/cgroup/rdma type cgroup 
(rw,nosuid,nodev,noexec,relatime,rdma)
  cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
  cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
  cgroup on /sys/fs/cgroup/hugetlb type cgroup 
(rw,nosuid,nodev,noexec,relatime,hugetlb)
  cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
  systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=29737)
  hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
  mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
  debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
  tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
  fusectl on /sys/fs/fuse/connections type fusectl 
(rw,nosuid,nodev,noexec,relatime)
  configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
  /dev/mapper/isw_dbbdgggiei_Volume0p2 on /boot type ext4 
(rw,relatime,stripe=16)
  /dev/mapper/isw_dbbdgggiei_Volume0p1 on /boot/efi type vfat 
(rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
  tmpfs on /run/user/1000 type tmpfs 
(rw,nosuid,nodev,relatime,size=3282416k,mode=700,uid=1000,gid=1000)
  /home/.ecryptfs/cfast/.Private on /home/cfast type ecryptfs 
(rw,nosuid,nodev,relatime,ecryptfs_fnek_sig=2e786df13a224d25,ecryptfs_sig=bae1facf9d2afaeb,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_unlink_sigs)
  gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
  binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc 
(rw,nosuid,nodev,noexec,relatime)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDev

[Kernel-packages] [Bug 1960344] Re: Can't mount my encrypted drive with 5.4.0.99-generic

Applied the "apport-collect 1960344" command as requested.  Note that
this is while using the 5.4.0-94 kernel, because I cannot successfully
log in with the 5.4.0-99 kernel.

** 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/1960344

Title:
  Can't mount my encrypted drive with 5.4.0.99-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I boot with kernel 5.4.0-94 my Linux system properly asks me for
  the passphrase to my encrypted drive (full disk encryption) and then
  after that successfully gets me to the user login screen.  But when I
  updated my kernel to 5.4.0-99, the booting Linux system does not ask
  me for my drive encryption passphrase but instead indicates that it is
  waiting for a drive partition and eventually times out and drops me
  into a busybox session.

  The GRUB arguments are identical for both kernels 5.4.0-94 and
  5.4.0-99, yet I can only successfully get into my Linux system using
  the 5.4.0-94 kernel.

  I don't know whether the following info is useful or not, since it is
  gathered only from the kernel 5.4.0-94 where I can actually log in.

  cat /proc/version_signature :
   Ubuntu 5.4.0-94.106-generic 5.4.157

  lspci-vnvn.log is attached.

  Output of mount command :

  sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
  proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
  udev on /dev type devtmpfs 
(rw,nosuid,noexec,relatime,size=16365340k,nr_inodes=4091335,mode=755)
  devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
  tmpfs on /run type tmpfs 
(rw,nosuid,nodev,noexec,relatime,size=3282420k,mode=755)
  /dev/mapper/vgmint-root on / type ext4 
(rw,relatime,errors=remount-ro,stripe=16)
  securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
  tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
  tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
  tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
  cgroup2 on /sys/fs/cgroup/unified type cgroup2 
(rw,nosuid,nodev,noexec,relatime,nsdelegate)
  cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
  pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
  efivarfs on /sys/firmware/efi/efivars type efivarfs 
(rw,nosuid,nodev,noexec,relatime)
  none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
  cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
  cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
  cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
  cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
  cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
  cgroup on /sys/fs/cgroup/pids type cgroup 
(rw,nosuid,nodev,noexec,relatime,pids)
  cgroup on /sys/fs/cgroup/rdma type cgroup 
(rw,nosuid,nodev,noexec,relatime,rdma)
  cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
  cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
  cgroup on /sys/fs/cgroup/hugetlb type cgroup 
(rw,nosuid,nodev,noexec,relatime,hugetlb)
  cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
  systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=29737)
  hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
  mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
  debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
  tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
  fusectl on /sys/fs/fuse/connections type fusectl 
(rw,nosuid,nodev,noexec,relatime)
  configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
  /dev/mapper/isw_dbbdgggiei_Volume0p2 on /boot type ext4 
(rw,relatime,stripe=16)
  /dev/mapper/isw_dbbdgggiei_Volume0p1 on /boot/efi type vfat 
(rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
  tmpfs on /run/user/1000 type tmpfs 
(rw,nosuid,nodev,relatime,size=3282416k,mode=700,uid=1000,gid=1000)
  /home/.ecryptfs/cfast/.Private on /home/cfast type ecryptfs 
(rw,nosuid,nodev,relatime,ecryptfs_fnek_sig=2e786df13a224d25,ecryptfs_sig=bae1facf9d2afaeb,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_unlink_sigs)
  gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
  binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc 
(rw,nosuid,nodev,noexec,re

[Kernel-packages] [Bug 1960344] PulseList.txt

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1960344/+attachment/5560021/+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/1960344

Title:
  Can't mount my encrypted drive with 5.4.0.99-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I boot with kernel 5.4.0-94 my Linux system properly asks me for
  the passphrase to my encrypted drive (full disk encryption) and then
  after that successfully gets me to the user login screen.  But when I
  updated my kernel to 5.4.0-99, the booting Linux system does not ask
  me for my drive encryption passphrase but instead indicates that it is
  waiting for a drive partition and eventually times out and drops me
  into a busybox session.

  The GRUB arguments are identical for both kernels 5.4.0-94 and
  5.4.0-99, yet I can only successfully get into my Linux system using
  the 5.4.0-94 kernel.

  I don't know whether the following info is useful or not, since it is
  gathered only from the kernel 5.4.0-94 where I can actually log in.

  cat /proc/version_signature :
   Ubuntu 5.4.0-94.106-generic 5.4.157

  lspci-vnvn.log is attached.

  Output of mount command :

  sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
  proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
  udev on /dev type devtmpfs 
(rw,nosuid,noexec,relatime,size=16365340k,nr_inodes=4091335,mode=755)
  devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
  tmpfs on /run type tmpfs 
(rw,nosuid,nodev,noexec,relatime,size=3282420k,mode=755)
  /dev/mapper/vgmint-root on / type ext4 
(rw,relatime,errors=remount-ro,stripe=16)
  securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
  tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
  tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
  tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
  cgroup2 on /sys/fs/cgroup/unified type cgroup2 
(rw,nosuid,nodev,noexec,relatime,nsdelegate)
  cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
  pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
  efivarfs on /sys/firmware/efi/efivars type efivarfs 
(rw,nosuid,nodev,noexec,relatime)
  none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
  cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
  cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
  cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
  cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
  cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
  cgroup on /sys/fs/cgroup/pids type cgroup 
(rw,nosuid,nodev,noexec,relatime,pids)
  cgroup on /sys/fs/cgroup/rdma type cgroup 
(rw,nosuid,nodev,noexec,relatime,rdma)
  cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
  cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
  cgroup on /sys/fs/cgroup/hugetlb type cgroup 
(rw,nosuid,nodev,noexec,relatime,hugetlb)
  cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
  systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=29737)
  hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
  mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
  debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
  tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
  fusectl on /sys/fs/fuse/connections type fusectl 
(rw,nosuid,nodev,noexec,relatime)
  configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
  /dev/mapper/isw_dbbdgggiei_Volume0p2 on /boot type ext4 
(rw,relatime,stripe=16)
  /dev/mapper/isw_dbbdgggiei_Volume0p1 on /boot/efi type vfat 
(rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
  tmpfs on /run/user/1000 type tmpfs 
(rw,nosuid,nodev,relatime,size=3282416k,mode=700,uid=1000,gid=1000)
  /home/.ecryptfs/cfast/.Private on /home/cfast type ecryptfs 
(rw,nosuid,nodev,relatime,ecryptfs_fnek_sig=2e786df13a224d25,ecryptfs_sig=bae1facf9d2afaeb,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_unlink_sigs)
  gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
  binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc 
(rw,nosuid,nodev,noexec,relatime)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioD

[Kernel-packages] [Bug 1960344] UdevDb.txt