[Kernel-packages] [Bug 1789772] Re: tlbie master timeout checkstop (using NVidia/GPU)

[Frank Heimes]

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-power-systems
   Status: New => Triaged

** Changed in: ubuntu-power-systems
   Importance: Undecided => Critical

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Tags added: triage-g

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

Title:
  tlbie master timeout checkstop (using NVidia/GPU)

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  A hung state machine in the chip's NMU logic can trigger a fatal
  condition that will be flagged by hardware through a checkstop. Hence,
  customers that have a Power 9 Whitherspoon (equipped with GPUs) will
  experience a crash on their server when using NVIDIA's toolkit.

  The server will crash with the following hardware failing message:
  Unrecoverable Hardware Failure, (Critical) A system checkstop occurred 
(AffectedSubsystem: Canister/Appliance, PID: 19703), Resolved: 0

  In this case, a `NCUFIR[10] tlbie master timeout` has been observed by
  only starting the NVIDIA ATS driver. This issue is being triggered
  because the NMU logic is getting stuck when a page is upgraded from RO
  -> RW without a following tlbie.

  This is addressed with the following patches:
  bd5050e38aec3055ff4257ade987d808ac93b582 powerpc/mm/radix: Change pte relax 
sequence to handle nest MMU hang
  e4c1112c3fc503fc78379fa61450bfda3f0717fe powerpc/mm: Change function prototype
  044003b52a78bcbda7103633c351da16505096cf powerpc/mm/radix: Move function from 
radix.h to pgtable-radix.c
  f069ff396d657ac7bdb5de866c3ec28b8d08d953 powerpc/mm/hugetlb: Update 
huge_ptep_set_access_flags to call __ptep_set_access_flags directly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1789772/+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 1786902] Re: [18.10 FEAT] SMC-Direct

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: Triaged => Fix Committed

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

Title:
  [18.10 FEAT] SMC-Direct

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Provide support for next generation HiperSockets.
  SMC-local (Shared Memory Communications -- local) provides a new architecture 
for high performance networking within a CEC. Buffers in the HSA can be shared 
between LPARs and will be used for communication.
  A new socket family will be used to eliminate TCP overhead. Integration with 
existing tooling through TCP handshaking.
  A preload library can be used to enable applications to use the new socket 
family transparently

  Backport from kernel 4.19 will be attached.

  For SMC enabling following kernel config has to be set
  CONFIG_HAVE_PNETID.

  With this setting an additoiponal modul need to be build : pnet.ko

  @canonical kernel team:
  please cherrypick:
  Here you go - sorry for the delay!
  In sequence, from oldest to latest:

  ddb457c6993babbcdd41fca638b870d2a2fc3941
  be6a3f38ff2a2bfd2e591fdc566940a0d4d9428c
  0afff91c6f5ecef27715ea71e34dc2baacba1060
  c6ba7c9ba43de1b57e9a53946e7ff988554c84ed
  1619f770589a183af56f248de261534b255122de
  c758dfddc1b5b1c9b8c64e5e4bb9bf24b74f4a59
  be244f28d22f77d939ba2b973c102ad2b49d3496
  413498440e30bfe381ac99dfc31628a3d8d4382a
  4b1b7d3b30a6d32ac1a1dcede284e76ef8a8542d
  c601171d7a60b5b09d7c2fe0579953323a80744e
  bac6de7b637018f4caacfdf2b4ad8c8749de7420
  00e5fb263f9f5f2af60754b79b7dcec0d5e88154
  144ce4b9b5a788953b5373162a1921267497fb38
  48bf5231771c7e3961c8326353b6027b1bed6eb5
  12c36dcfd6f48ece2fce4dc8e6ce68224d005d37
  2e3bbe46b4a18d16314dab0c0efdba0c079a5ed0
  947541f36c561b5e0ca639ffc450a8c5221de467
  7005ada68d1774d7c1109deaba0c2cd8e46f5091
  603cc1498455cf57f5ca4483b600efb37ea2c56c
  0d18a0cb4b1585d9e5a3b300d5df9ed866561ffb
  dd979b4df817e9976f18fb6f9d134d6bc4a3c317
  0d86caff06363151df21603eb1f4e3207ea91bd2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1786902/+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 1789634] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  computer does not reemerge from hibernate

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  I put the computer in hibernate
  I came back and pressed start button to reawake machine.
  No response.
  Black screen.

  Had to force hard reboot to get machine back to functional status.

  lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  
  posting this to systemd as that is power management package (as I understand)
  apt-cache policy systemd
  systemd:
Installed: 237-3ubuntu10.3
Candidate: 237-3ubuntu10.3
Version table:
   *** 237-3ubuntu10.3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   237-3ubuntu10 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Aug 29 14:31:57 2018
  InstallationDate: Installed on 2018-08-24 (4 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Dell Inc. Studio 1737
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=2b8227a7-271c-4d4c-8a2b-faa238133be0 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0P792H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A09
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd04/14/2011:svnDellInc.:pnStudio1737:pvrA09:rvnDellInc.:rn0P792H:rvrA09:cvnDellInc.:ct8:cvrA09:
  dmi.product.name: Studio 1737
  dmi.product.version: A09
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789634/+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 1788758] Re: linux-gcp: 4.15.0-1019.20~16.04.1 -proposed tracker

[Khaled El Mously]

** Summary changed:

- linux-gcp:  -proposed tracker
+ linux-gcp: 4.15.0-1019.20~16.04.1 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Kleber Sacilotto de Souza (kleber-souza) => Khaled El Mously 
(kmously)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Kleber Sacilotto de Souza (kleber-souza) => Khaled El Mously 
(kmously)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Kleber Sacilotto de Souza (kleber-souza) => Khaled El Mously 
(kmously)

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

Title:
  linux-gcp: 4.15.0-1019.20~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  New
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  New
Status in linux-gcp source package in Xenial:
  New

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1788744
  phase: Packaging
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788758/+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 1789634] Re: computer does not reemerge from hibernate

[Kai-Heng Feng]

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  computer does not reemerge from hibernate

Status in linux package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I put the computer in hibernate
  I came back and pressed start button to reawake machine.
  No response.
  Black screen.

  Had to force hard reboot to get machine back to functional status.

  lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  
  posting this to systemd as that is power management package (as I understand)
  apt-cache policy systemd
  systemd:
Installed: 237-3ubuntu10.3
Candidate: 237-3ubuntu10.3
Version table:
   *** 237-3ubuntu10.3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   237-3ubuntu10 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Aug 29 14:31:57 2018
  InstallationDate: Installed on 2018-08-24 (4 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Dell Inc. Studio 1737
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=2b8227a7-271c-4d4c-8a2b-faa238133be0 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0P792H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A09
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd04/14/2011:svnDellInc.:pnStudio1737:pvrA09:rvnDellInc.:rn0P792H:rvrA09:cvnDellInc.:ct8:cvrA09:
  dmi.product.name: Studio 1737
  dmi.product.version: A09
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789634/+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 1789790] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1789790

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Fix Intel Cannon Lake LPSS I2C input clock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ===SRU Justification===
  [Impact]
  i2c-hid touchpad stops working after a short usage, i2c controller timed
  out: 
  [   65.867065] i2c_hid i2c-DELL08CC:00: i2c_hid_get_input: incomplete
  report (14/17415)
  [   65.895356] i2c_hid i2c-DELL08CC:00: i2c_hid_get_input: incomplete
  report (14/15240)
  [   66.127727] i2c_hid i2c-DELL08CC:00: i2c_hid_get_input: incomplete
  report (14/65365) 
  [   71.720018] i2c_designware i2c_designware.0: i2c_dw_handle_tx_abort:
  lost arbitration
  [   72.736023] i2c_designware i2c_designware.0: controller timed out

  [Fix]
  Update Intel Cannon Lake LPSS with correct clock rate. This is a
  fallback value when platform ACPI doesn't define one.

  [Test]
  The touchpad works correctly after this patch gets applied.

  [Regression Potential]
  Low. This patch is already in linux-stable, also no functional change
  other than updated clock rate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1789790/+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 1789790] Re: Fix Intel Cannon Lake LPSS I2C input clock

[AceLan Kao]

** Tags added: originate-from-1789379 somerville

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

Title:
  Fix Intel Cannon Lake LPSS I2C input clock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ===SRU Justification===
  [Impact]
  i2c-hid touchpad stops working after a short usage, i2c controller timed
  out: 
  [   65.867065] i2c_hid i2c-DELL08CC:00: i2c_hid_get_input: incomplete
  report (14/17415)
  [   65.895356] i2c_hid i2c-DELL08CC:00: i2c_hid_get_input: incomplete
  report (14/15240)
  [   66.127727] i2c_hid i2c-DELL08CC:00: i2c_hid_get_input: incomplete
  report (14/65365) 
  [   71.720018] i2c_designware i2c_designware.0: i2c_dw_handle_tx_abort:
  lost arbitration
  [   72.736023] i2c_designware i2c_designware.0: controller timed out

  [Fix]
  Update Intel Cannon Lake LPSS with correct clock rate. This is a
  fallback value when platform ACPI doesn't define one.

  [Test]
  The touchpad works correctly after this patch gets applied.

  [Regression Potential]
  Low. This patch is already in linux-stable, also no functional change
  other than updated clock rate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1789790/+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 1789790] [NEW] Fix Intel Cannon Lake LPSS I2C input clock

[Kai-Heng Feng]

Public bug reported:

===SRU Justification===
[Impact]
i2c-hid touchpad stops working after a short usage, i2c controller timed
out: 
[   65.867065] i2c_hid i2c-DELL08CC:00: i2c_hid_get_input: incomplete
report (14/17415)
[   65.895356] i2c_hid i2c-DELL08CC:00: i2c_hid_get_input: incomplete
report (14/15240)
[   66.127727] i2c_hid i2c-DELL08CC:00: i2c_hid_get_input: incomplete
report (14/65365) 
[   71.720018] i2c_designware i2c_designware.0: i2c_dw_handle_tx_abort:
lost arbitration
[   72.736023] i2c_designware i2c_designware.0: controller timed out

[Fix]
Update Intel Cannon Lake LPSS with correct clock rate. This is a
fallback value when platform ACPI doesn't define one.

[Test]
The touchpad works correctly after this patch gets applied.

[Regression Potential]
Low. This patch is already in linux-stable, also no functional change
other than updated clock rate.

** Affects: hwe-next
 Importance: Undecided
 Status: New

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


** Tags: originate-from-1789379 somerville

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

Title:
  Fix Intel Cannon Lake LPSS I2C input clock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ===SRU Justification===
  [Impact]
  i2c-hid touchpad stops working after a short usage, i2c controller timed
  out: 
  [   65.867065] i2c_hid i2c-DELL08CC:00: i2c_hid_get_input: incomplete
  report (14/17415)
  [   65.895356] i2c_hid i2c-DELL08CC:00: i2c_hid_get_input: incomplete
  report (14/15240)
  [   66.127727] i2c_hid i2c-DELL08CC:00: i2c_hid_get_input: incomplete
  report (14/65365) 
  [   71.720018] i2c_designware i2c_designware.0: i2c_dw_handle_tx_abort:
  lost arbitration
  [   72.736023] i2c_designware i2c_designware.0: controller timed out

  [Fix]
  Update Intel Cannon Lake LPSS with correct clock rate. This is a
  fallback value when platform ACPI doesn't define one.

  [Test]
  The touchpad works correctly after this patch gets applied.

  [Regression Potential]
  Low. This patch is already in linux-stable, also no functional change
  other than updated clock rate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1789790/+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 1789774] Re: linux s390x cosmic autopkgtests fail to clone from git.launchpad.net?!

[Dimitri John Ledkov]

what confuses me is why "https://; protocol is used here, instead of
git:// protocol.

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

Title:
  linux s390x cosmic autopkgtests fail to clone from git.launchpad.net?!

Status in Launchpad itself:
  Incomplete
Status in autopkgtest package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  22:17:19 DEBUG| Running 'git clone --depth 1 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/cosmic linux'
  22:17:19 ERROR| [stderr] Cloning into 'linux'...
  22:18:06 ERROR| [stderr] warning: You appear to have cloned an empty 
repository.

  
  And later:

  22:18:06 INFO |   GOODubuntu_kernel_selftests.setup   
ubuntu_kernel_selftests.setup   timestamp=1535581086localtime=Aug 29 
22:18:06   completed successfully
  22:18:06 INFO |   END GOODubuntu_kernel_selftests.setup   
ubuntu_kernel_selftests.setup   timestamp=1535581086localtime=Aug 29 
22:18:06   
  22:18:06 DEBUG| Persistent state client._record_indent now set to 1
  22:18:06 DEBUG| Persistent state client.unexpected_reboot deleted
  22:18:06 INFO |   START   ubuntu_kernel_selftests.breakpoints 
ubuntu_kernel_selftests.breakpoints timestamp=1535581086localtime=Aug 
29 22:18:06   
  22:18:06 DEBUG| Persistent state client._record_indent now set to 2
  22:18:06 DEBUG| Persistent state client.unexpected_reboot now set to 
('ubuntu_kernel_selftests.breakpoints', 'ubuntu_kernel_selftests.breakpoints')
  22:18:06 DEBUG| Running 'sudo make -C 
linux/tools/testing/selftests/breakpoints all run_tests'
  22:18:06 ERROR| [stderr] make: *** linux/tools/testing/selftests/breakpoints: 
No such file or directory.  Stop.
  22:18:06 ERROR| Exception escaping from test:

  And many many tracebacks about empty directories.

  Hence it ends up with:

  $ head -n 3 autotest-results.ubuntu_kernel_selftests.xml
  
  

  Proxy settings are:
  "http_proxy": "http://squid.internal:3128;, 
  "https_proxy": "http://squid.internal:3128;, 
  "no_proxy": 
"127.0.0.1,127.0.1.1,localhost,localdomain,novalocal,internal,archive.ubuntu.com,security.ubuntu.com,changelogs.ubuntu.com,ddebs.ubuntu.com,ppa.launchpad.net"

  Is there something odd about s390x cloning from launchpad? cause that
  repository is not empty on launchpad.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1789774/+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 1789774] Re: linux s390x cosmic autopkgtests fail to clone from git.launchpad.net?!

[Dimitri John Ledkov]

https://bileto.ubuntu.com/#/ticket/3394 should end up with autopkgtests
detailing what's happening.

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

Title:
  linux s390x cosmic autopkgtests fail to clone from git.launchpad.net?!

Status in Launchpad itself:
  Incomplete
Status in autopkgtest package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  22:17:19 DEBUG| Running 'git clone --depth 1 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/cosmic linux'
  22:17:19 ERROR| [stderr] Cloning into 'linux'...
  22:18:06 ERROR| [stderr] warning: You appear to have cloned an empty 
repository.

  
  And later:

  22:18:06 INFO |   GOODubuntu_kernel_selftests.setup   
ubuntu_kernel_selftests.setup   timestamp=1535581086localtime=Aug 29 
22:18:06   completed successfully
  22:18:06 INFO |   END GOODubuntu_kernel_selftests.setup   
ubuntu_kernel_selftests.setup   timestamp=1535581086localtime=Aug 29 
22:18:06   
  22:18:06 DEBUG| Persistent state client._record_indent now set to 1
  22:18:06 DEBUG| Persistent state client.unexpected_reboot deleted
  22:18:06 INFO |   START   ubuntu_kernel_selftests.breakpoints 
ubuntu_kernel_selftests.breakpoints timestamp=1535581086localtime=Aug 
29 22:18:06   
  22:18:06 DEBUG| Persistent state client._record_indent now set to 2
  22:18:06 DEBUG| Persistent state client.unexpected_reboot now set to 
('ubuntu_kernel_selftests.breakpoints', 'ubuntu_kernel_selftests.breakpoints')
  22:18:06 DEBUG| Running 'sudo make -C 
linux/tools/testing/selftests/breakpoints all run_tests'
  22:18:06 ERROR| [stderr] make: *** linux/tools/testing/selftests/breakpoints: 
No such file or directory.  Stop.
  22:18:06 ERROR| Exception escaping from test:

  And many many tracebacks about empty directories.

  Hence it ends up with:

  $ head -n 3 autotest-results.ubuntu_kernel_selftests.xml
  
  

  Proxy settings are:
  "http_proxy": "http://squid.internal:3128;, 
  "https_proxy": "http://squid.internal:3128;, 
  "no_proxy": 
"127.0.0.1,127.0.1.1,localhost,localdomain,novalocal,internal,archive.ubuntu.com,security.ubuntu.com,changelogs.ubuntu.com,ddebs.ubuntu.com,ppa.launchpad.net"

  Is there something odd about s390x cloning from launchpad? cause that
  repository is not empty on launchpad.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1789774/+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 1789774] Re: linux s390x cosmic autopkgtests fail to clone from git.launchpad.net?!

[William Grant]

It doesn't seem likely that this has anything to do with Launchpad.
You'll need to try to reproduce it outside an autopkgtest and ideally
get logs with GIT_CURL_VERBOSE=1 GIT_TRACE=1.

** Changed in: launchpad
   Status: New => Incomplete

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

Title:
  linux s390x cosmic autopkgtests fail to clone from git.launchpad.net?!

Status in Launchpad itself:
  Incomplete
Status in autopkgtest package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  22:17:19 DEBUG| Running 'git clone --depth 1 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/cosmic linux'
  22:17:19 ERROR| [stderr] Cloning into 'linux'...
  22:18:06 ERROR| [stderr] warning: You appear to have cloned an empty 
repository.

  
  And later:

  22:18:06 INFO |   GOODubuntu_kernel_selftests.setup   
ubuntu_kernel_selftests.setup   timestamp=1535581086localtime=Aug 29 
22:18:06   completed successfully
  22:18:06 INFO |   END GOODubuntu_kernel_selftests.setup   
ubuntu_kernel_selftests.setup   timestamp=1535581086localtime=Aug 29 
22:18:06   
  22:18:06 DEBUG| Persistent state client._record_indent now set to 1
  22:18:06 DEBUG| Persistent state client.unexpected_reboot deleted
  22:18:06 INFO |   START   ubuntu_kernel_selftests.breakpoints 
ubuntu_kernel_selftests.breakpoints timestamp=1535581086localtime=Aug 
29 22:18:06   
  22:18:06 DEBUG| Persistent state client._record_indent now set to 2
  22:18:06 DEBUG| Persistent state client.unexpected_reboot now set to 
('ubuntu_kernel_selftests.breakpoints', 'ubuntu_kernel_selftests.breakpoints')
  22:18:06 DEBUG| Running 'sudo make -C 
linux/tools/testing/selftests/breakpoints all run_tests'
  22:18:06 ERROR| [stderr] make: *** linux/tools/testing/selftests/breakpoints: 
No such file or directory.  Stop.
  22:18:06 ERROR| Exception escaping from test:

  And many many tracebacks about empty directories.

  Hence it ends up with:

  $ head -n 3 autotest-results.ubuntu_kernel_selftests.xml
  
  

  Proxy settings are:
  "http_proxy": "http://squid.internal:3128;, 
  "https_proxy": "http://squid.internal:3128;, 
  "no_proxy": 
"127.0.0.1,127.0.1.1,localhost,localdomain,novalocal,internal,archive.ubuntu.com,security.ubuntu.com,changelogs.ubuntu.com,ddebs.ubuntu.com,ppa.launchpad.net"

  Is there something odd about s390x cloning from launchpad? cause that
  repository is not empty on launchpad.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1789774/+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 1789758] Re: bluetooth headphones a2dp profile does not function after suspend

[Daniel van Vugt]

Reassigned to pulseaudio. Bluetooth audio is a software feature
implemented in pulseaudio, not in bluez.

** Tags added: a2dp

** Also affects: pulseaudio (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: resume suspend-resume

** Summary changed:

- bluetooth headphones a2dp profile does not function after suspend
+ bluetooth headphones a2dp profile does not function after suspend, only HSP

** No longer affects: bluez (Ubuntu)

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

Title:
  bluetooth headphones a2dp profile does not function after suspend,
  only HSP

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  2) $ apt-cache policy bluez
  bluez:
Installed: 5.48-0ubuntu3.1
Candidate: 5.48-0ubuntu3.1
Version table:
   *** 5.48-0ubuntu3.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.48-0ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  3) bluetooth headphones stay working in a2dp mode even after suspend

  4) bluetooth headphones connect but no sound will come out of a2dp
  mode, only in HSP profile

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 29 18:07:26 2018
  InstallationDate: Installed on 2018-05-26 (95 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180525)
  InterestingModules: rfcomm bnep btusb bluetooth
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=9e84ffd4-d629-4dcd-a6c4-6648d1a34665 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/16/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: RKPPT10H.86A.0041.2015.0316.1442
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: D53427RKE
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G87971-406
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrRKPPT10H.86A.0041.2015.0316.1442:bd03/16/2015:svn:pn:pvr:rvnIntelCorporation:rnD53427RKE:rvrG87971-406:cvn:ct3:cvr:
  dmi.product.family: To be filled by O.E.M.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 48:51:B7:07:93:F5  ACL MTU: 1021:5  SCO MTU: 96:5
DOWN 
RX bytes:5617087 acl:790 sco:22622 events:634625 errors:0
TX bytes:540631745 acl:632348 sco:22584 commands:537 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1789758/+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 1789774] Re: ubuntu_kernel_selftests fails on s390x cosmic - bad git?

[Dimitri John Ledkov]

Similarly:

08/29 22:16:44 DEBUG| utils:0116| Running 'git clone --depth 1 
https://git.launchpad.net/qa-regression-testing'
08/29 22:16:44 ERROR| utils:0153| [stderr] Cloning into 
'qa-regression-testing'...
08/29 22:17:06 ERROR| utils:0153| [stderr] warning: You appear to have 
cloned an empty repository.
08/29 22:17:06 ERROR|  test:0414| Exception escaping from test:

Results in:

autotest-results.ubuntu_qrt_apparmor.xml:
--
autotest-results.ubuntu_qrt_kernel_aslr_collisions.xml:


** Summary changed:

- ubuntu_kernel_selftests fails on s390x cosmic - bad git?
+ linux s390x cosmic autopkgtests fail to clone from git.launchpad.net?!

** Also affects: launchpad
   Importance: Undecided
   Status: New

** Also affects: autopkgtest (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  linux s390x cosmic autopkgtests fail to clone from git.launchpad.net?!

Status in Launchpad itself:
  Incomplete
Status in autopkgtest package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  22:17:19 DEBUG| Running 'git clone --depth 1 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/cosmic linux'
  22:17:19 ERROR| [stderr] Cloning into 'linux'...
  22:18:06 ERROR| [stderr] warning: You appear to have cloned an empty 
repository.

  
  And later:

  22:18:06 INFO |   GOODubuntu_kernel_selftests.setup   
ubuntu_kernel_selftests.setup   timestamp=1535581086localtime=Aug 29 
22:18:06   completed successfully
  22:18:06 INFO |   END GOODubuntu_kernel_selftests.setup   
ubuntu_kernel_selftests.setup   timestamp=1535581086localtime=Aug 29 
22:18:06   
  22:18:06 DEBUG| Persistent state client._record_indent now set to 1
  22:18:06 DEBUG| Persistent state client.unexpected_reboot deleted
  22:18:06 INFO |   START   ubuntu_kernel_selftests.breakpoints 
ubuntu_kernel_selftests.breakpoints timestamp=1535581086localtime=Aug 
29 22:18:06   
  22:18:06 DEBUG| Persistent state client._record_indent now set to 2
  22:18:06 DEBUG| Persistent state client.unexpected_reboot now set to 
('ubuntu_kernel_selftests.breakpoints', 'ubuntu_kernel_selftests.breakpoints')
  22:18:06 DEBUG| Running 'sudo make -C 
linux/tools/testing/selftests/breakpoints all run_tests'
  22:18:06 ERROR| [stderr] make: *** linux/tools/testing/selftests/breakpoints: 
No such file or directory.  Stop.
  22:18:06 ERROR| Exception escaping from test:

  And many many tracebacks about empty directories.

  Hence it ends up with:

  $ head -n 3 autotest-results.ubuntu_kernel_selftests.xml
  
  

  Proxy settings are:
  "http_proxy": "http://squid.internal:3128;, 
  "https_proxy": "http://squid.internal:3128;, 
  "no_proxy": 
"127.0.0.1,127.0.1.1,localhost,localdomain,novalocal,internal,archive.ubuntu.com,security.ubuntu.com,changelogs.ubuntu.com,ddebs.ubuntu.com,ppa.launchpad.net"

  Is there something odd about s390x cloning from launchpad? cause that
  repository is not empty on launchpad.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1789774/+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 1788730] Re: TP-LINK TG-3468 network card not recognized correctly

[Anthony Wong]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Anthony Wong (anthonywong)

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

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

Title:
  TP-LINK TG-3468 network card not recognized correctly

Status in linux package in Ubuntu:
  In Progress

Bug description:
  A few days ago purchased a couple of TP-LINK TG-3468 network cards
  (reviewed by Phoronix here:
  https://www.phoronix.com/scan.php?page=news_item=MTY2ODQ), both
  brand new, not reused. After installed them to a pc, to my surprise,
  one of them was correctly identified and the other was incorrectly
  identified as "NCube Device 8168 (rev 06)".

  After DuckDuckGoing for a while I found this kernel bud report for
  FreeBSD: https://forums.freebsd.org/threads/not-recognized-pci-e
  -network-card.57734/

  IMHO is the same issue but I'm using Ubuntu 16.04.5 server i686. I
  wanted to report this so it can be fixed, please let me know wich
  logs/data should I provide.

  When ran lspci -nv this is shown for the correct nic:
  03:00.0 0200: 10ec:8168 (rev 06)
Subsystem: 7470:3468
Flags: bus master, fast devsel, latency 0, IRQ 27
I/O ports at e800 [size=256]
Memory at febff000 (64-bit, non-prefetchable) [size=4K]
Memory at fdffc000 (64-bit, prefetchable) [size=16K]
Capabilities: 
Kernel driver in use: r8169
Kernel modules: r8169

  And this for the incorrect one:
  01:00.0 0200: 10ff:8168 (rev 06)
Subsystem: 7470:3468
Flags: bus master, fast devsel, latency 0, IRQ 11
I/O ports at c800 [size=256]
Memory at fe9ff000 (64-bit, non-prefetchable) [size=4K]
Memory at fdefc000 (64-bit, prefetchable) [size=16K]
Capabilities: 

  1) lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  2) In regard to the package I think this is related to the kernel itself?
  3) Both cards should be identified as "Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)" and the 
r8169 driver should be used.
  4) The network card was erroneously detected as a different one and the 
driver was not loaded by the kernel.

  Best regards.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-133-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=652853e2-bd7e-44bb-9b13-f2c9c3823791
  InstallationDate: Installed on 2017-12-06 (260 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.3)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-133-generic 
root=UUID=89ec3fdb-2ccd-497a-8657-bbe2b53393ed ro
  ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-133-generic N/A
   linux-backports-modules-4.4.0-133-generic  N/A
   linux-firmware 1.157.20
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-133-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/27/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0702
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5KPL-CM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0702:bd08/27/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-CM:rvrx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : 

[Kernel-packages] [Bug 1789774] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1789774

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

** Tags added: cosmic

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

Title:
  linux s390x cosmic autopkgtests fail to clone from git.launchpad.net?!

Status in Launchpad itself:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  22:17:19 DEBUG| Running 'git clone --depth 1 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/cosmic linux'
  22:17:19 ERROR| [stderr] Cloning into 'linux'...
  22:18:06 ERROR| [stderr] warning: You appear to have cloned an empty 
repository.

  
  And later:

  22:18:06 INFO |   GOODubuntu_kernel_selftests.setup   
ubuntu_kernel_selftests.setup   timestamp=1535581086localtime=Aug 29 
22:18:06   completed successfully
  22:18:06 INFO |   END GOODubuntu_kernel_selftests.setup   
ubuntu_kernel_selftests.setup   timestamp=1535581086localtime=Aug 29 
22:18:06   
  22:18:06 DEBUG| Persistent state client._record_indent now set to 1
  22:18:06 DEBUG| Persistent state client.unexpected_reboot deleted
  22:18:06 INFO |   START   ubuntu_kernel_selftests.breakpoints 
ubuntu_kernel_selftests.breakpoints timestamp=1535581086localtime=Aug 
29 22:18:06   
  22:18:06 DEBUG| Persistent state client._record_indent now set to 2
  22:18:06 DEBUG| Persistent state client.unexpected_reboot now set to 
('ubuntu_kernel_selftests.breakpoints', 'ubuntu_kernel_selftests.breakpoints')
  22:18:06 DEBUG| Running 'sudo make -C 
linux/tools/testing/selftests/breakpoints all run_tests'
  22:18:06 ERROR| [stderr] make: *** linux/tools/testing/selftests/breakpoints: 
No such file or directory.  Stop.
  22:18:06 ERROR| Exception escaping from test:

  And many many tracebacks about empty directories.

  Hence it ends up with:

  $ head -n 3 autotest-results.ubuntu_kernel_selftests.xml
  
  

  Proxy settings are:
  "http_proxy": "http://squid.internal:3128;, 
  "https_proxy": "http://squid.internal:3128;, 
  "no_proxy": 
"127.0.0.1,127.0.1.1,localhost,localdomain,novalocal,internal,archive.ubuntu.com,security.ubuntu.com,changelogs.ubuntu.com,ddebs.ubuntu.com,ppa.launchpad.net"

  Is there something odd about s390x cloning from launchpad? cause that
  repository is not empty on launchpad.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1789774/+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 1789774] [NEW] linux s390x cosmic autopkgtests fail to clone from git.launchpad.net?!

[Dimitri John Ledkov]

Public bug reported:

22:17:19 DEBUG| Running 'git clone --depth 1 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/cosmic linux'
22:17:19 ERROR| [stderr] Cloning into 'linux'...
22:18:06 ERROR| [stderr] warning: You appear to have cloned an empty repository.


And later:

22:18:06 INFO | GOODubuntu_kernel_selftests.setup   
ubuntu_kernel_selftests.setup   timestamp=1535581086localtime=Aug 29 
22:18:06   completed successfully
22:18:06 INFO | END GOODubuntu_kernel_selftests.setup   
ubuntu_kernel_selftests.setup   timestamp=1535581086localtime=Aug 29 
22:18:06   
22:18:06 DEBUG| Persistent state client._record_indent now set to 1
22:18:06 DEBUG| Persistent state client.unexpected_reboot deleted
22:18:06 INFO | START   ubuntu_kernel_selftests.breakpoints 
ubuntu_kernel_selftests.breakpoints timestamp=1535581086localtime=Aug 
29 22:18:06   
22:18:06 DEBUG| Persistent state client._record_indent now set to 2
22:18:06 DEBUG| Persistent state client.unexpected_reboot now set to 
('ubuntu_kernel_selftests.breakpoints', 'ubuntu_kernel_selftests.breakpoints')
22:18:06 DEBUG| Running 'sudo make -C linux/tools/testing/selftests/breakpoints 
all run_tests'
22:18:06 ERROR| [stderr] make: *** linux/tools/testing/selftests/breakpoints: 
No such file or directory.  Stop.
22:18:06 ERROR| Exception escaping from test:

And many many tracebacks about empty directories.

Hence it ends up with:

$ head -n 3 autotest-results.ubuntu_kernel_selftests.xml



Proxy settings are:
"http_proxy": "http://squid.internal:3128;, 
"https_proxy": "http://squid.internal:3128;, 
"no_proxy": 
"127.0.0.1,127.0.1.1,localhost,localdomain,novalocal,internal,archive.ubuntu.com,security.ubuntu.com,changelogs.ubuntu.com,ddebs.ubuntu.com,ppa.launchpad.net"

Is there something odd about s390x cloning from launchpad? cause that
repository is not empty on launchpad.

** Affects: launchpad
 Importance: Undecided
 Status: New

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


** Tags: cosmic

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

Title:
  linux s390x cosmic autopkgtests fail to clone from git.launchpad.net?!

Status in Launchpad itself:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  22:17:19 DEBUG| Running 'git clone --depth 1 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/cosmic linux'
  22:17:19 ERROR| [stderr] Cloning into 'linux'...
  22:18:06 ERROR| [stderr] warning: You appear to have cloned an empty 
repository.

  
  And later:

  22:18:06 INFO |   GOODubuntu_kernel_selftests.setup   
ubuntu_kernel_selftests.setup   timestamp=1535581086localtime=Aug 29 
22:18:06   completed successfully
  22:18:06 INFO |   END GOODubuntu_kernel_selftests.setup   
ubuntu_kernel_selftests.setup   timestamp=1535581086localtime=Aug 29 
22:18:06   
  22:18:06 DEBUG| Persistent state client._record_indent now set to 1
  22:18:06 DEBUG| Persistent state client.unexpected_reboot deleted
  22:18:06 INFO |   START   ubuntu_kernel_selftests.breakpoints 
ubuntu_kernel_selftests.breakpoints timestamp=1535581086localtime=Aug 
29 22:18:06   
  22:18:06 DEBUG| Persistent state client._record_indent now set to 2
  22:18:06 DEBUG| Persistent state client.unexpected_reboot now set to 
('ubuntu_kernel_selftests.breakpoints', 'ubuntu_kernel_selftests.breakpoints')
  22:18:06 DEBUG| Running 'sudo make -C 
linux/tools/testing/selftests/breakpoints all run_tests'
  22:18:06 ERROR| [stderr] make: *** linux/tools/testing/selftests/breakpoints: 
No such file or directory.  Stop.
  22:18:06 ERROR| Exception escaping from test:

  And many many tracebacks about empty directories.

  Hence it ends up with:

  $ head -n 3 autotest-results.ubuntu_kernel_selftests.xml
  
  

  Proxy settings are:
  "http_proxy": "http://squid.internal:3128;, 
  "https_proxy": "http://squid.internal:3128;, 
  "no_proxy": 
"127.0.0.1,127.0.1.1,localhost,localdomain,novalocal,internal,archive.ubuntu.com,security.ubuntu.com,changelogs.ubuntu.com,ddebs.ubuntu.com,ppa.launchpad.net"

  Is there something odd about s390x cloning from launchpad? cause that
  repository is not empty on launchpad.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1789774/+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 1788730] Re: TP-LINK TG-3468 network card not recognized correctly

[Anthony Wong]

You testing is good, the first kernel should work fine. I will build one
more kernel soon and need your help to verify that. If the test result
is again positive, I will send the fix to upstream.

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

Title:
  TP-LINK TG-3468 network card not recognized correctly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A few days ago purchased a couple of TP-LINK TG-3468 network cards
  (reviewed by Phoronix here:
  https://www.phoronix.com/scan.php?page=news_item=MTY2ODQ), both
  brand new, not reused. After installed them to a pc, to my surprise,
  one of them was correctly identified and the other was incorrectly
  identified as "NCube Device 8168 (rev 06)".

  After DuckDuckGoing for a while I found this kernel bud report for
  FreeBSD: https://forums.freebsd.org/threads/not-recognized-pci-e
  -network-card.57734/

  IMHO is the same issue but I'm using Ubuntu 16.04.5 server i686. I
  wanted to report this so it can be fixed, please let me know wich
  logs/data should I provide.

  When ran lspci -nv this is shown for the correct nic:
  03:00.0 0200: 10ec:8168 (rev 06)
Subsystem: 7470:3468
Flags: bus master, fast devsel, latency 0, IRQ 27
I/O ports at e800 [size=256]
Memory at febff000 (64-bit, non-prefetchable) [size=4K]
Memory at fdffc000 (64-bit, prefetchable) [size=16K]
Capabilities: 
Kernel driver in use: r8169
Kernel modules: r8169

  And this for the incorrect one:
  01:00.0 0200: 10ff:8168 (rev 06)
Subsystem: 7470:3468
Flags: bus master, fast devsel, latency 0, IRQ 11
I/O ports at c800 [size=256]
Memory at fe9ff000 (64-bit, non-prefetchable) [size=4K]
Memory at fdefc000 (64-bit, prefetchable) [size=16K]
Capabilities: 

  1) lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  2) In regard to the package I think this is related to the kernel itself?
  3) Both cards should be identified as "Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)" and the 
r8169 driver should be used.
  4) The network card was erroneously detected as a different one and the 
driver was not loaded by the kernel.

  Best regards.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-133-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=652853e2-bd7e-44bb-9b13-f2c9c3823791
  InstallationDate: Installed on 2017-12-06 (260 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.3)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-133-generic 
root=UUID=89ec3fdb-2ccd-497a-8657-bbe2b53393ed ro
  ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-133-generic N/A
   linux-backports-modules-4.4.0-133-generic  N/A
   linux-firmware 1.157.20
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-133-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/27/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0702
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5KPL-CM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0702:bd08/27/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-CM:rvrx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : 

[Kernel-packages] [Bug 1788387] Re: After upgrading from 4.4.0 to 4.15.0 system doesn't boot - ACPI issue

[Kai-Heng Feng]

Would it be possible for you to do a kernel bisection?

First, find the last good -rc kernel and the first bad -rc kernel from
http://kernel.ubuntu.com/~kernel-ppa/mainline/

Then,
$ sudo apt build-dep linux
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$ git bisect start
$ git bisect good $(the good version you found)
$ git bisect bad $(the bad version found)
$ make localmodconfig
$ make -j`nproc` deb-pkg
Install the newly built kernel, then reboot with it.
If the issue still happens,
$ git bisect bad
Otherwise,
$ git bisect good
Repeat to "make -j`nproc` deb-pkg" until you find the commit that causes the 
regression.

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

Title:
  After upgrading from 4.4.0 to 4.15.0 system doesn't boot - ACPI issue

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Xubuntu in an old system, I'm concerned because other users
  looking for a light OS for their old PC wouldn't be able to install or
  boot the 18.04 version and above.

  With kernel 4.4.0 the system boots without problem (xubuntu 16.04),
  after upgrading to kernel 4.15 the system doesn't boot anymore
  (18.04). This issue was present when testing kernel 4.13 too.

  The install crashes with an error: BIOS bug:8254 timer not connected
  to io-apic error on.

  Adding any of these commands to the boot allows the system to load
  properly:

  -acpi=off
  -pci=noacpi
  -acpi=noirq

  I attach the info related.

  Ubuntu 4.15.0-32.35-generic 4.15.18
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0: 1509 F pulseaudio
   /dev/snd/controlC1: 1509 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=ed42d246-f10a-403e-a009-8c6428ce1a88
  InstallationDate: Installed on 2018-06-12 (70 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 152d:2338 JMicron Technology Corp. / JMicron USA 
Technology Corp. JM20337 Hi-Speed USB to SATA & PATA Combo Bridge
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 248a:00da
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Dell Inc Dimension C521
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=467ee8bd-241d-4d11-95d9-6d9268a1dca6 ro quiet splash pci=noacpi 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  RfKill:

  Tags:  bionic
  Uname: Linux 4.15.0-32-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-17 (5 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788387/+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 1789772] [NEW] tlbie master timeout checkstop (using NVidia/GPU)

[bugproxy]

Public bug reported:

A hung state machine in the chip's NMU logic can trigger a fatal
condition that will be flagged by hardware through a checkstop. Hence,
customers that have a Power 9 Whitherspoon (equipped with GPUs) will
experience a crash on their server when using NVIDIA's toolkit.

The server will crash with the following hardware failing message:
Unrecoverable Hardware Failure, (Critical) A system checkstop occurred 
(AffectedSubsystem: Canister/Appliance, PID: 19703), Resolved: 0

In this case, a `NCUFIR[10] tlbie master timeout` has been observed by
only starting the NVIDIA ATS driver. This issue is being triggered
because the NMU logic is getting stuck when a page is upgraded from RO
-> RW without a following tlbie.

This is addressed with the following patches:
bd5050e38aec3055ff4257ade987d808ac93b582 powerpc/mm/radix: Change pte relax 
sequence to handle nest MMU hang
e4c1112c3fc503fc78379fa61450bfda3f0717fe powerpc/mm: Change function prototype
044003b52a78bcbda7103633c351da16505096cf powerpc/mm/radix: Move function from 
radix.h to pgtable-radix.c
f069ff396d657ac7bdb5de866c3ec28b8d08d953 powerpc/mm/hugetlb: Update 
huge_ptep_set_access_flags to call __ptep_set_access_flags directly

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-170972 severity-critical 
targetmilestone-inin1804

** Tags added: architecture-ppc64le bugnameltc-170972 severity-critical
targetmilestone-inin1804

** Changed in: ubuntu
 Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage 
(ubuntu-power-triage)

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

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

Title:
  tlbie master timeout checkstop (using NVidia/GPU)

Status in linux package in Ubuntu:
  New

Bug description:
  A hung state machine in the chip's NMU logic can trigger a fatal
  condition that will be flagged by hardware through a checkstop. Hence,
  customers that have a Power 9 Whitherspoon (equipped with GPUs) will
  experience a crash on their server when using NVIDIA's toolkit.

  The server will crash with the following hardware failing message:
  Unrecoverable Hardware Failure, (Critical) A system checkstop occurred 
(AffectedSubsystem: Canister/Appliance, PID: 19703), Resolved: 0

  In this case, a `NCUFIR[10] tlbie master timeout` has been observed by
  only starting the NVIDIA ATS driver. This issue is being triggered
  because the NMU logic is getting stuck when a page is upgraded from RO
  -> RW without a following tlbie.

  This is addressed with the following patches:
  bd5050e38aec3055ff4257ade987d808ac93b582 powerpc/mm/radix: Change pte relax 
sequence to handle nest MMU hang
  e4c1112c3fc503fc78379fa61450bfda3f0717fe powerpc/mm: Change function prototype
  044003b52a78bcbda7103633c351da16505096cf powerpc/mm/radix: Move function from 
radix.h to pgtable-radix.c
  f069ff396d657ac7bdb5de866c3ec28b8d08d953 powerpc/mm/hugetlb: Update 
huge_ptep_set_access_flags to call __ptep_set_access_flags directly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789772/+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 1789772] [NEW] tlbie master timeout checkstop (using NVidia/GPU)

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

A hung state machine in the chip's NMU logic can trigger a fatal
condition that will be flagged by hardware through a checkstop. Hence,
customers that have a Power 9 Whitherspoon (equipped with GPUs) will
experience a crash on their server when using NVIDIA's toolkit.

The server will crash with the following hardware failing message:
Unrecoverable Hardware Failure, (Critical) A system checkstop occurred 
(AffectedSubsystem: Canister/Appliance, PID: 19703), Resolved: 0

In this case, a `NCUFIR[10] tlbie master timeout` has been observed by
only starting the NVIDIA ATS driver. This issue is being triggered
because the NMU logic is getting stuck when a page is upgraded from RO
-> RW without a following tlbie.

This is addressed with the following patches:
bd5050e38aec3055ff4257ade987d808ac93b582 powerpc/mm/radix: Change pte relax 
sequence to handle nest MMU hang
e4c1112c3fc503fc78379fa61450bfda3f0717fe powerpc/mm: Change function prototype
044003b52a78bcbda7103633c351da16505096cf powerpc/mm/radix: Move function from 
radix.h to pgtable-radix.c
f069ff396d657ac7bdb5de866c3ec28b8d08d953 powerpc/mm/hugetlb: Update 
huge_ptep_set_access_flags to call __ptep_set_access_flags directly

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-170972 severity-critical 
targetmilestone-inin1804
-- 
tlbie master timeout checkstop (using NVidia/GPU)
https://bugs.launchpad.net/bugs/1789772
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1777238] Re: video lag

[Boris]

After a couple of weeks without issues, thanks to changing the v-sync in 
compris, it is back and getting progressively worse.
Will try running system monitor and see if this helps.

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

Title:
  video lag

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The problem exists for months and I didn't find a good answer on it.
  It affects many softwares: Cheese, Super Tux Cart, VLC (when I rewind
  the video the sounds continues, but the video stops), youtube,
  Hangouts and every software where video is played.

  I experienced that there are 2 things that can break it:
   - if I move the mouse out and in on the affected window (it doesn't work in 
full screen)
   - if I open the system monitor, the problem also disappears

  other people also face with this problem:
  
https://unix.stackexchange.com/questions/447696/ubuntu-16-04-18-04-video-playback-lags-stutters
  
https://askubuntu.com/questions/1032035/ubuntu-18-04-budgie-desktop-video-lag-youtube-twitch-in-chrome
  
https://askubuntu.com/questions/1030074/my-video-player-in-ubuntu-18-04-lts-lags/1030194
  https://askubuntu.com/questions/1030155/youtube-video-lag-on-18-04

  Ubuntu 4.15.0-23.25-generic 4.15.18
  it was upgraded from 16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cheese 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 16 14:34:26 2018
  ExecutablePath: /usr/bin/cheese
  InstallationDate: Installed on 2016-08-04 (680 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Latitude E5440
  RelatedPackageVersions:
   cheese3.28.0-1ubuntu1
   cheese-common 3.28.0-1ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-04-02 (74 days ago)
  dmi.bios.date: 05/01/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 009TY8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  vandor 3436 F pulseaudio
   /dev/snd/controlC1:  vandor 3436 F pulseaudio
   /dev/snd/controlC0:  vandor 3436 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=b5a3c617-9443-458f-92a3-63eea1f57d5c
  InstallationDate: Installed on 2016-08-04 (681 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Latitude E5440
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=38affd30-88f0-4a36-b9ae-6b5c210844b4 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-02 (74 days ago)
  UserGroups: adm bumblebee cdrom dip docker libvirt libvirtd lpadmin mail 
plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/01/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 009TY8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777238/+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 1788730] Re: TP-LINK TG-3468 network card not recognized correctly

[dienteperro]

Installed files from folder 1. Card is recognized, module r8169 loaded,
and is operational! I made some speed tests and all appears to be okay.

Also to note. I didn't have installed the linux-tools and linux-cloud-
tools packages (from repositories, not yours). So I needed to install
linux-tools-generic and linux-cloud-tools-generic from repos and then
install yours. I made and image of the disk prior to deploy your files,
If you want I can try the files without "tools" packages (repos and
yours).

After that I installed files from folder 2. Not all went fine, after
issuing command "sudo dpkg -i linux-image-
unsigned-4.15.0-33-generic_4.15.0-33.36ubuntu2_amd64.deb" an error
appeared:

Selecting previously unselected package linux-image-unsigned-4.15.0-33-generic.
dpkg: regarding 
linux-image-unsigned-4.15.0-33-generic_4.15.0-33.36ubuntu2_amd64.deb containing 
linux-image-unsigned-4.15.0-33-generic:
 linux-image-unsigned-4.15.0-33-generic conflicts with 
linux-image-4.15.0-33-generic
  linux-image-4.15.0-33-generic (version 4.15.0-33.36) is present and installed.

dpkg: error processing archive 
linux-image-unsigned-4.15.0-33-generic_4.15.0-33.36ubuntu2_amd64.deb 
(--install):
 conflicting packages - not installing linux-image-unsigned-4.15.0-33-generic
Errors were encountered while processing:
 linux-image-unsigned-4.15.0-33-generic_4.15.0-33.36ubuntu2_amd64.deb

I rebooted with a different kernel 4.15.0-29 and removed all files
related to 4.15.0-33, after that rebooted and reinstalled all "folder 2"
files, after reboot (again) the nic is sort-of detected but no
operational, issuing command lspci -vv outputs the card with "Kernel
modules: r8169" but no sign of "Kernel driver in use", this line of
disappeared.

I'll try again tomorrow installing folder 2 files over folder 1.
Fortunately I made an image prior to deployment of files.

Thanks a lot!

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

Title:
  TP-LINK TG-3468 network card not recognized correctly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A few days ago purchased a couple of TP-LINK TG-3468 network cards
  (reviewed by Phoronix here:
  https://www.phoronix.com/scan.php?page=news_item=MTY2ODQ), both
  brand new, not reused. After installed them to a pc, to my surprise,
  one of them was correctly identified and the other was incorrectly
  identified as "NCube Device 8168 (rev 06)".

  After DuckDuckGoing for a while I found this kernel bud report for
  FreeBSD: https://forums.freebsd.org/threads/not-recognized-pci-e
  -network-card.57734/

  IMHO is the same issue but I'm using Ubuntu 16.04.5 server i686. I
  wanted to report this so it can be fixed, please let me know wich
  logs/data should I provide.

  When ran lspci -nv this is shown for the correct nic:
  03:00.0 0200: 10ec:8168 (rev 06)
Subsystem: 7470:3468
Flags: bus master, fast devsel, latency 0, IRQ 27
I/O ports at e800 [size=256]
Memory at febff000 (64-bit, non-prefetchable) [size=4K]
Memory at fdffc000 (64-bit, prefetchable) [size=16K]
Capabilities: 
Kernel driver in use: r8169
Kernel modules: r8169

  And this for the incorrect one:
  01:00.0 0200: 10ff:8168 (rev 06)
Subsystem: 7470:3468
Flags: bus master, fast devsel, latency 0, IRQ 11
I/O ports at c800 [size=256]
Memory at fe9ff000 (64-bit, non-prefetchable) [size=4K]
Memory at fdefc000 (64-bit, prefetchable) [size=16K]
Capabilities: 

  1) lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  2) In regard to the package I think this is related to the kernel itself?
  3) Both cards should be identified as "Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)" and the 
r8169 driver should be used.
  4) The network card was erroneously detected as a different one and the 
driver was not loaded by the kernel.

  Best regards.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-133-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=652853e2-bd7e-44bb-9b13-f2c9c3823791
  InstallationDate: Installed on 2017-12-06 (260 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.3)
  IwConfig: Error: 

[Kernel-packages] [Bug 1774817] Re: Temperature sensors on x470 not reporting correctly

[Steven Clarkson]

This also applies to the new Threadrippers (2990WX, etc.)

Recent commits

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/drivers/hwmon/k10temp.c?id=484a84f25ca7817c3662001316ba7d1e06b74ae2

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/hwmon/k10temp.c?id=cd6a2064dbf9e485b80c54687f0ce91cca91a6df

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

Title:
  Temperature sensors on x470 not reporting correctly

Status in linux package in Ubuntu:
  Triaged

Bug description:
  x470-I ROG strix motherboard and Ryzen 2700

  After
  sudo sensors-detect
  and answering yes to all the probes the net result is:
  "Sorry, no sensors were detected.
  Either your system has no sensors, or they are not supported, or
  they are connected to an I2C or SMBus adapter that is not
  supported."

  sensors output lists:
  asus-isa-
  Adapter: ISA adapter
  cpu_fan:0 RPM

  nouveau-pci-0900
  Adapter: PCI adapter
  fan1:   0 RPM
  temp1:+65.0°C  (high = +95.0°C, hyst =  +3.0°C)
     (crit = +105.0°C, hyst =  +5.0°C)
     (emerg = +135.0°C, hyst =  +5.0°C)

  k10temp-pci-00c3
  Adapter: PCI adapter
  temp1:+94.2°C  (high = +70.0°C)

  Where the cpu fan is patently wrong and the k10temp likewise. The
  nouveau-pci-0900 appears to be the actual CPU temperature.

  May be related to:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740736

  Other info:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  version log:
  Ubuntu 4.15.0-22.24-generic 4.15.17

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774817/+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 1781049] Re: WiFI hard blocked after resuming laptop (RTL 8723BE)

[Dexter]

Hello,
Blacklisting the below modules one after the another individually or all of 
them did no good. The hard-block bug is still there. [2]

blacklist hp_wmi
blacklist hp_wireless

Also, while going through the output of dmesg, I found a few lines that
might be of interest (not that I have any experience, as my handle
suggests, I'm a noob at Linux) or help you guys.

# ** *
dmesg snippets (when no modules are blacklisted) [2]

HP Wireless hotkeys as /devices/virtual/input/input8
hp_wmi: query 0xd returned error 0x5
HP WMI hotkeys as /devices/virtual/input/input10

[   96.374587] iwlwifi :08:00.0: reporting RF_KILL (radio disabled)
[   96.374700] iwlwifi :08:00.0: RF_KILL bit toggled to disable radio.

# ** *
Files that sparked my interest:

The file at '/sys/devices/virtual/input/input8/uevent' has the following 
contents:
PRODUCT=19/0/0/0
NAME="HP Wireless hotkeys"
PHYS="hpq6001/input0"
PROP=0
EV=3
KEY=80 0 0 0
MODALIAS=input:b0019vpe-e0,1,kF7,ramlsfw

The file at '/sys/devices/virtual/input/input10/uevent' has the following 
contents:
PRODUCT=19/0/0/0
NAME="HP WMI hotkeys"
PHYS="wmi/input0"
PROP=0
EV=33
KEY=40 0 10007 2102400 0 0
MSC=10
SW=0
MODALIAS=input:b0019vpe-e0,1,4,5,k8A,8D,94,99,E0,E1,E2,F0,166,ram4,lsfw

Trying to emulate some keys by trying to write to the file results in
I/O errors. (suggested on the internet)

# ** *

Files from attached after copying as root, but with some errors: [1]
cp: error reading 'input10/power/autosuspend_delay_ms': Input/output error
cp: error reading 'input10/event9/power/autosuspend_delay_ms': Input/output 
error
cp: error reading 'input8/power/autosuspend_delay_ms': Input/output error
cp: error reading 'input8/event7/power/autosuspend_delay_ms': Input/output error
cp: error reading 'mice/power/autosuspend_delay_ms': Input/output error

# ** *

[1] Files from /sys/devices/virtual/input
[2] Attached 3 dmesg logs with the filenames explaining the test case. 

# ** *

Thank you for your time!

** Attachment added: "Contains dmesg output and files from path [1]"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781049/+attachment/5182401/+files/attachments.tar

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

Title:
  WiFI hard blocked after resuming laptop (RTL 8723BE)

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  I installed a fresh copy of Ubuntu 18.04 and everything seems to work
  fine, till I suspended and resumed the laptop. After resume, the wifi
  is hard blocked is rfkill. Reinstalling drivers, different drivers,
  nothing helped. All this was done under Secure Boot disabled under
  Ubuntu and BIOS (UEFI).

  The WiFI card is Realtek 8723BE. laptop is HP AB035TX Pavilion 15. If
  any further info is required, I'll add it on notification. I am
  familiar with Linux, any help will be really appreciated.

  
  P.S: If this wifi card is the issue, please suggest some PCI-mini card that 
will work with my Ubuntu, even after suspend and resume (Ideally a 2.4/5G + BT 
5.0)

  Thank you all!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mythreya   1281 F pulseaudio
   /dev/snd/controlC1:  mythreya   1281 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-06-26 (16 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.6 metric 600
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 05c8:0379 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion Notebook
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=300b2c4a-387a-49b5-9cb6-93de471ebbdb ro quiet splash nouveau.runpm=0 
vt.handoff=1
  

[Kernel-packages] [Bug 1789135] Re: package linux-image-3.13.0-45-generic 3.13.0-45.74 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[Kevin Greene]

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

Title:
  package linux-image-3.13.0-45-generic 3.13.0-45.74 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Now unable to restart current applications on the host.
  Serious problem.

  root@xray:/boot# su zimbra
  zimbra@xray:/boot$ zmcontrol start
  Perl API version v5.14.0 of Socket does not match v5.18.0 at 
/usr/share/perl/5.18/XSLoader.pm line 117.
  Compilation failed in require at /usr/lib/perl/5.18/Sys/Syslog.pm line 10.
  BEGIN failed--compilation aborted at /usr/lib/perl/5.18/Sys/Syslog.pm line 10.
  Compilation failed in require at 
/opt/zimbra/zimbramon/lib/Zimbra/Mon/Logger.pm line 23.
  BEGIN failed--compilation aborted at 
/opt/zimbra/zimbramon/lib/Zimbra/Mon/Logger.pm line 23.
  Compilation failed in require at /opt/zimbra/bin/zmcontrol line 27.
  BEGIN failed--compilation aborted at /opt/zimbra/bin/zmcontrol line 27.
  zimbra@xray:/boot$

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-45-generic 3.13.0-45.74
  ProcVersionSignature: Ubuntu 3.13.0-117.164~precise1-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-117-generic x86_64
  NonfreeKernelModules: gpio_ich lpc_ich hpilo mac_hid e752x_edac edac_core 
shpchp tg3 cciss pata_acpi
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 26 19:29 seq
   crw-rw 1 root audio 116, 33 Aug 26 19:29 timer
  AplayDevices: aplay: device_list:268: no soundcards found...
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  ArecordDevices: arecord: device_list:268: no soundcards found...
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp3', '/dev/dsp2', 
'/dev/dsp1', '/dev/dsp', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer'] 
failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Sun Aug 26 20:36:34 2018
  DuplicateSignature: 
package:linux-image-3.13.0-45-generic:3.13.0-45.74:subprocess installed 
post-installation script returned error exit status 2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  HibernationDevice: RESUME=UUID=01d95e3f-884b-481d-b871-b941923121e2
  InstallationDate: Installed on 2011-04-13 (2692 days ago)
  InstallationMedia: Ubuntu-Server 10.04.2 LTS "Lucid Lynx" - Release amd64 
(20110211.1)
  IwConfig:
   eth2  no wireless extensions.
   
   eth3  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: HP ProLiant DL380 G4
  PciMultimedia:
   
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-117-generic 
root=/dev/mapper/hostname-root ro text
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.14
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  Title: package linux-image-3.13.0-45-generic 3.13.0-45.74 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
  UpgradeStatus: Upgraded to trusty on 2018-08-26 (0 days ago)
  dmi.bios.date: 07/19/2007
  dmi.bios.vendor: HP
  dmi.bios.version: P51
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP51:bd07/19/2007:svnHP:pnProLiantDL380G4:pvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant DL380 G4
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789135/+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 1699772]

[Xiscofauli]

*** Bug 119078 has been marked as a duplicate of this bug. ***

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

Title:
  linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux-
  image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-
  image-3.13.0-121-generic | Regression: many user-space apps crashing

Status in LibreOffice:
  Won't Fix
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  Incomplete
Status in linux package in Debian:
  Fix Released

Bug description:
  Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10)

  linux-image-4.4.0-81-generic appears to contain a regression, probably
  related to the CVE-2017-1000364 fix backport / patch.

  Using this kernel, the Oracle Java browser plugin always crashes
  during stack-related actions on initialization. This means, the plugin
  completely stopped working.

  
  It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to 
CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also 
contains a fix for CVE-2017-1000364.


  uname -a:

  > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06
  UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


  I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as
  well as Iceweasel / Firefox/3.5.16 in a chroot.

  Using linux-image-4.4.0-81-generic it crashes in all combinations
  while with both other kernels it works.

  
  I was not able to obtain any detailed crash information from Firefox 51.0.1, 
but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace 
which shows the relation to stack operations performed by the plugin, even 
without proper debug symbols:

  
  > (gdb) bt full
  > #0  0x7fa06d805307 in _expand_stack_to(unsigned char*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #1  0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, 
unsigned char*) ()
  >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #2  0x7fa06d80cf0b in JVM_handle_linux_signal () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #3  0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #4  

  
  I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6.

  
  The crash will be triggered by any applet, for example the test applet at:

  * https://java.com/en/download/installed8.jsp

  
  I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow 
apparently does not allow me to use apport to report this bug:

  > $ LANG= apport-cli linux-image-4.4.0-81-generic
  > 
  > *** Collecting problem information
  > 
  > The collected information can be sent to the developers to improve the
  > application. This might take a few minutes.
  > .
  > 
  > *** Problem in linux-image-4.4.0-81-generic
  > 
  > The problem cannot be reported:
  > 
  > This is not an official KDE package. Please remove any third party package 
and try again.

  If someone can tell me how to get apport working for this package, I
  can use it to collect additional information, but (unfortunately?) the
  problem should be fairly easy to reproduce...

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1699772/+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 1699772]

[Xiscofauli]

*** Bug 119487 has been marked as a duplicate of this bug. ***

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

Title:
  linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux-
  image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-
  image-3.13.0-121-generic | Regression: many user-space apps crashing

Status in LibreOffice:
  Won't Fix
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  Incomplete
Status in linux package in Debian:
  Fix Released

Bug description:
  Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10)

  linux-image-4.4.0-81-generic appears to contain a regression, probably
  related to the CVE-2017-1000364 fix backport / patch.

  Using this kernel, the Oracle Java browser plugin always crashes
  during stack-related actions on initialization. This means, the plugin
  completely stopped working.

  
  It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to 
CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also 
contains a fix for CVE-2017-1000364.


  uname -a:

  > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06
  UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


  I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as
  well as Iceweasel / Firefox/3.5.16 in a chroot.

  Using linux-image-4.4.0-81-generic it crashes in all combinations
  while with both other kernels it works.

  
  I was not able to obtain any detailed crash information from Firefox 51.0.1, 
but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace 
which shows the relation to stack operations performed by the plugin, even 
without proper debug symbols:

  
  > (gdb) bt full
  > #0  0x7fa06d805307 in _expand_stack_to(unsigned char*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #1  0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, 
unsigned char*) ()
  >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #2  0x7fa06d80cf0b in JVM_handle_linux_signal () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #3  0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #4  

  
  I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6.

  
  The crash will be triggered by any applet, for example the test applet at:

  * https://java.com/en/download/installed8.jsp

  
  I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow 
apparently does not allow me to use apport to report this bug:

  > $ LANG= apport-cli linux-image-4.4.0-81-generic
  > 
  > *** Collecting problem information
  > 
  > The collected information can be sent to the developers to improve the
  > application. This might take a few minutes.
  > .
  > 
  > *** Problem in linux-image-4.4.0-81-generic
  > 
  > The problem cannot be reported:
  > 
  > This is not an official KDE package. Please remove any third party package 
and try again.

  If someone can tell me how to get apport working for this package, I
  can use it to collect additional information, but (unfortunately?) the
  problem should be fairly easy to reproduce...

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1699772/+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 1789758] [NEW] bluetooth headphones a2dp profile does not function after suspend

[Ryan Harper]

Public bug reported:

1) lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04

2) $ apt-cache policy bluez
bluez:
  Installed: 5.48-0ubuntu3.1
  Candidate: 5.48-0ubuntu3.1
  Version table:
 *** 5.48-0ubuntu3.1 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 5.48-0ubuntu3 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

3) bluetooth headphones stay working in a2dp mode even after suspend

4) bluetooth headphones connect but no sound will come out of a2dp mode,
only in HSP profile

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bluez 5.48-0ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
Uname: Linux 4.15.0-30-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 29 18:07:26 2018
InstallationDate: Installed on 2018-05-26 (95 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180525)
InterestingModules: rfcomm bnep btusb bluetooth
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=9e84ffd4-d629-4dcd-a6c4-6648d1a34665 ro quiet splash vt.handoff=1
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/16/2015
dmi.bios.vendor: Intel Corp.
dmi.bios.version: RKPPT10H.86A.0041.2015.0316.1442
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: D53427RKE
dmi.board.vendor: Intel Corporation
dmi.board.version: G87971-406
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrRKPPT10H.86A.0041.2015.0316.1442:bd03/16/2015:svn:pn:pvr:rvnIntelCorporation:rnD53427RKE:rvrG87971-406:cvn:ct3:cvr:
dmi.product.family: To be filled by O.E.M.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 48:51:B7:07:93:F5  ACL MTU: 1021:5  SCO MTU: 96:5
DOWN 
RX bytes:5617087 acl:790 sco:22622 events:634625 errors:0
TX bytes:540631745 acl:632348 sco:22584 commands:537 errors:0

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


** Tags: amd64 apport-bug bionic

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

Title:
  bluetooth headphones a2dp profile does not function after suspend

Status in bluez package in Ubuntu:
  New

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  2) $ apt-cache policy bluez
  bluez:
Installed: 5.48-0ubuntu3.1
Candidate: 5.48-0ubuntu3.1
Version table:
   *** 5.48-0ubuntu3.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.48-0ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  3) bluetooth headphones stay working in a2dp mode even after suspend

  4) bluetooth headphones connect but no sound will come out of a2dp
  mode, only in HSP profile

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 29 18:07:26 2018
  InstallationDate: Installed on 2018-05-26 (95 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180525)
  InterestingModules: rfcomm bnep btusb bluetooth
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=9e84ffd4-d629-4dcd-a6c4-6648d1a34665 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/16/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: RKPPT10H.86A.0041.2015.0316.1442
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: D53427RKE
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G87971-406
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrRKPPT10H.86A.0041.2015.0316.1442:bd03/16/2015:svn:pn:pvr:rvnIntelCorporation:rnD53427RKE:rvrG87971-406:cvn:ct3:cvr:
  dmi.product.family: To be filled by O.E.M.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 48:51:B7:07:93:F5  ACL MTU: 1021:5  SCO MTU: 96:5
DOWN 
RX bytes:5617087 acl:790 sco:22622 events:634625 errors:0
TX bytes:540631745 acl:632348 sco:22584 commands:537 errors:0

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net

[Kernel-packages] [Bug 1789756] Re: Swap not being used, RAM not being released, CPU use at 100%

[Cortimi]

** Description changed:

+ Memory usage continues to climb to 100%, even as applications are shut
+ down. Swap file is not being used. CPU usage climbs to %100 even as
+ applications are shut down.
  
- Memory usage continues to climb to 100%, even as applications are shut down. 
Swap file is not being used. CPU usage climbs to %100 even as applications are 
shut down.
- 
+ After reboot, system will operate normally for a number of hours, until
+ a virtual machine (Virtual Box) is run. At this point memory and CPU
+ usage will climb until %100. Exiting programs and closing the VM does
+ not resolve the issue.
  
  More information in this thread, started by me:
  
  https://discourse.ubuntubudgie.org/t/high-ram-use-no-swap-use/940/9
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  cortimi1688 F pulseaudio
   /dev/snd/controlC1:  cortimi1688 F pulseaudio
   /dev/snd/controlC0:  cortimi1688 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Wed Aug 29 17:39:45 2018
  InstallationDate: Installed on 2018-08-23 (6 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725.1)
  MachineType: MSI MS-7817
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=10f46365-0845-48bb-a427-fe155f6085c0 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/30/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-P33 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd03/30/2015:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnH81M-P33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

Title:
  Swap not being used, RAM not being released, CPU use at 100%

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Memory usage continues to climb to 100%, even as applications are shut
  down. Swap file is not being used. CPU usage climbs to %100 even as
  applications are shut down.

  After reboot, system will operate normally for a number of hours,
  until a virtual machine (Virtual Box) is run. At this point memory and
  CPU usage will climb until %100. Exiting programs and closing the VM
  does not resolve the issue.

  More information in this thread, started by me:

  https://discourse.ubuntubudgie.org/t/high-ram-use-no-swap-use/940/9

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  cortimi1688 F pulseaudio
   /dev/snd/controlC1:  cortimi1688 F pulseaudio
   /dev/snd/controlC0:  cortimi1688 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Wed Aug 29 17:39:45 2018
  InstallationDate: Installed on 2018-08-23 (6 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725.1)
  MachineType: MSI MS-7817
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=10f46365-0845-48bb-a427-fe155f6085c0 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/30/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-P33 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  

[Kernel-packages] [Bug 1789756] Re: Swap not being used, RAM not being released, CPU use at 100%

[Cortimi]

** Attachment added: "HTOP after reboot, same apps running"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789756/+attachment/5182385/+files/After%20reboot.png

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

Title:
  Swap not being used, RAM not being released, CPU use at 100%

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Memory usage continues to climb to 100%, even as applications are shut
  down. Swap file is not being used. CPU usage climbs to %100 even as
  applications are shut down.

  After reboot, system will operate normally for a number of hours,
  until a virtual machine (Virtual Box) is run. At this point memory and
  CPU usage will climb until %100. Exiting programs and closing the VM
  does not resolve the issue.

  More information in this thread, started by me:

  https://discourse.ubuntubudgie.org/t/high-ram-use-no-swap-use/940/9

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  cortimi1688 F pulseaudio
   /dev/snd/controlC1:  cortimi1688 F pulseaudio
   /dev/snd/controlC0:  cortimi1688 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Wed Aug 29 17:39:45 2018
  InstallationDate: Installed on 2018-08-23 (6 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725.1)
  MachineType: MSI MS-7817
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=10f46365-0845-48bb-a427-fe155f6085c0 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/30/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-P33 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd03/30/2015:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnH81M-P33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789756/+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 1789756] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Swap not being used, RAM not being released, CPU use at 100%

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Memory usage continues to climb to 100%, even as applications are shut
  down. Swap file is not being used. CPU usage climbs to %100 even as
  applications are shut down.

  After reboot, system will operate normally for a number of hours,
  until a virtual machine (Virtual Box) is run. At this point memory and
  CPU usage will climb until %100. Exiting programs and closing the VM
  does not resolve the issue.

  More information in this thread, started by me:

  https://discourse.ubuntubudgie.org/t/high-ram-use-no-swap-use/940/9

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  cortimi1688 F pulseaudio
   /dev/snd/controlC1:  cortimi1688 F pulseaudio
   /dev/snd/controlC0:  cortimi1688 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Wed Aug 29 17:39:45 2018
  InstallationDate: Installed on 2018-08-23 (6 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725.1)
  MachineType: MSI MS-7817
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=10f46365-0845-48bb-a427-fe155f6085c0 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/30/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-P33 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd03/30/2015:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnH81M-P33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789756/+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 1789756] Re: Swap not being used, RAM not being released, CPU use at 100%

[Cortimi]

** Description changed:

+ 
+ Memory usage continues to climb to 100%, even as applications are shut down. 
Swap file is not being used. CPU usage climbs to %100 even as applications are 
shut down.
+ 
+ 
  More information in this thread, started by me:
  
  https://discourse.ubuntubudgie.org/t/high-ram-use-no-swap-use/940/9
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC2:  cortimi1688 F pulseaudio
-  /dev/snd/controlC1:  cortimi1688 F pulseaudio
-  /dev/snd/controlC0:  cortimi1688 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC2:  cortimi1688 F pulseaudio
+  /dev/snd/controlC1:  cortimi1688 F pulseaudio
+  /dev/snd/controlC0:  cortimi1688 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Wed Aug 29 17:39:45 2018
  InstallationDate: Installed on 2018-08-23 (6 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725.1)
  MachineType: MSI MS-7817
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=10f46365-0845-48bb-a427-fe155f6085c0 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
-  linux-restricted-modules-4.15.0-33-generic N/A
-  linux-backports-modules-4.15.0-33-generic  N/A
-  linux-firmware 1.173.1
+  linux-restricted-modules-4.15.0-33-generic N/A
+  linux-backports-modules-4.15.0-33-generic  N/A
+  linux-firmware 1.173.1
  RfKill:
-  0: phy0: Wireless LAN
-   Soft blocked: no
-   Hard blocked: no
+  0: phy0: Wireless LAN
+   Soft blocked: no
+   Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/30/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-P33 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd03/30/2015:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnH81M-P33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

** Attachment added: "HTOP showing issue"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789756/+attachment/5182384/+files/before%20reboot.png

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

Title:
  Swap not being used, RAM not being released, CPU use at 100%

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Memory usage continues to climb to 100%, even as applications are shut
  down. Swap file is not being used. CPU usage climbs to %100 even as
  applications are shut down.

  After reboot, system will operate normally for a number of hours,
  until a virtual machine (Virtual Box) is run. At this point memory and
  CPU usage will climb until %100. Exiting programs and closing the VM
  does not resolve the issue.

  More information in this thread, started by me:

  https://discourse.ubuntubudgie.org/t/high-ram-use-no-swap-use/940/9

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  cortimi1688 F pulseaudio
   /dev/snd/controlC1:  cortimi1688 F pulseaudio
   /dev/snd/controlC0:  cortimi1688 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Wed Aug 29 17:39:45 2018
  InstallationDate: Installed on 2018-08-23 (6 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725.1)
  MachineType: MSI MS-7817
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=10f46365-0845-48bb-a427-fe155f6085c0 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/30/2015
  dmi.bios.vendor: American 

[Kernel-packages] [Bug 1789756] [NEW] Swap not being used, RAM not being released, CPU use at 100%

[Cortimi]

Public bug reported:


Memory usage continues to climb to 100%, even as applications are shut down. 
Swap file is not being used. CPU usage climbs to %100 even as applications are 
shut down.


More information in this thread, started by me:

https://discourse.ubuntubudgie.org/t/high-ram-use-no-swap-use/940/9

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-33-generic 4.15.0-33.36
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  cortimi1688 F pulseaudio
 /dev/snd/controlC1:  cortimi1688 F pulseaudio
 /dev/snd/controlC0:  cortimi1688 F pulseaudio
CurrentDesktop: Budgie:GNOME
Date: Wed Aug 29 17:39:45 2018
InstallationDate: Installed on 2018-08-23 (6 days ago)
InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725.1)
MachineType: MSI MS-7817
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=10f46365-0845-48bb-a427-fe155f6085c0 ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-33-generic N/A
 linux-backports-modules-4.15.0-33-generic  N/A
 linux-firmware 1.173.1
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/30/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.9
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H81M-P33 (MS-7817)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd03/30/2015:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnH81M-P33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7817
dmi.product.version: 1.0
dmi.sys.vendor: MSI

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


** Tags: amd64 apport-bug bionic

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

Title:
  Swap not being used, RAM not being released, CPU use at 100%

Status in linux package in Ubuntu:
  New

Bug description:
  
  Memory usage continues to climb to 100%, even as applications are shut down. 
Swap file is not being used. CPU usage climbs to %100 even as applications are 
shut down.

  
  More information in this thread, started by me:

  https://discourse.ubuntubudgie.org/t/high-ram-use-no-swap-use/940/9

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  cortimi1688 F pulseaudio
   /dev/snd/controlC1:  cortimi1688 F pulseaudio
   /dev/snd/controlC0:  cortimi1688 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Wed Aug 29 17:39:45 2018
  InstallationDate: Installed on 2018-08-23 (6 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725.1)
  MachineType: MSI MS-7817
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=10f46365-0845-48bb-a427-fe155f6085c0 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/30/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-P33 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd03/30/2015:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnH81M-P33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : 

[Kernel-packages] [Bug 1783906] Re: Linux 4.15 and onwards fails to initialize some hard drives

[danieru]

Here's dmesg with #33~lp1783906DEBUGv2: https://paste.ubuntu.com/p/jK6zjKjtqc/
I expected this to have the bug and only print additional debug info, but it 
seems this fix the bug. The second drive (WDC) came up and I could mount it's 
partitions and read info from them.

Just to make sure, I did a second run and everything seemed to still
work fine, here's the dmesg of the second run:
https://paste.ubuntu.com/p/Tj5gnTWbs3/

(didn't test write now that i think about it)

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

Title:
  Linux 4.15 and onwards fails to initialize some hard drives

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  I have two hard drives, the main hard drive is a TOSHIBA DT01ACA200
  the second backup hard drive is a Western Digital WD5003AZEX. I
  installed lubuntu 18.04.1 on the Toshiba HDD and it boots just fine,
  the issue is with the second hard drive, when installing the WD HDD
  wouldn't even come as an option to install, and after boot the WD HDD
  still wouldn't come up, this is the dmesg with the stock kernel (4.15)
  https://paste.ubuntu.com/p/kpxh94v2SK/

  ata6 is the WD HDD that refuses to work. The messages:
  [  302.107650] ata6: SError: { CommWake 10B8B Dispar DevExch }
  [  302.107658] ata6: hard resetting link
  [  307.860291] ata6: link is slow to respond, please be patient (ready=0)
  [  312.120898] ata6: COMRESET failed (errno=-16)
  [  363.445120] INFO: task kworker/u8:5:201 blocked for more than 120 seconds.
  [  363.445131]   Not tainted 4.15.0-29-generic #31-Ubuntu
  [  363.445135] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.445140] kworker/u8:5D0   201  2 0x8000
  [  363.445155] Workqueue: events_unbound async_run_entry_fn
  [  363.445157] Call Trace:
  [  363.445171]  __schedule+0x291/0x8a0
  [  363.445177]  schedule+0x2c/0x80
  [  363.445182]  ata_port_wait_eh+0x7c/0xf0
  [  363.445186]  ? wait_woken+0x80/0x80
  [  363.445189]  ata_port_probe+0x28/0x40
  [  363.445192]  async_port_probe+0x2e/0x52
  [  363.445196]  async_run_entry_fn+0x3c/0x150
  [  363.445199]  process_one_work+0x1de/0x410
  [  363.445203]  worker_thread+0x32/0x410
  [  363.445207]  kthread+0x121/0x140
  [  363.445210]  ? process_one_work+0x410/0x410
  [  363.445214]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  363.445218]  ret_from_fork+0x22/0x40

  Repeat constantly. Also when I try to turn off the computer, the
  computer seem to freeze, the lights of the keyboard and mouse turn off
  and the computer just stay on.

  I tried Tiny Core 9.0 which has linux 4.14.10, and i didn't had this
  issue, i also installed linux 4.14 on this lubuntu 18.04 using Ukuu
  Kernel Update Utility. And with this kernel version, or any previous
  version the WD HDD does work again. Here's a dmesg of lubuntu 18.04
  with linux 4.14 and the WD HDD finally coming up at the end:
  https://paste.ubuntu.com/p/Gd3cGFbjTJ/

  Also tried with with linux 4.17 but the WD HDD would also refuse to
  work on this version. Here's another dmesg with this version:
  https://paste.ubuntu.com/p/PmNn96vZZv/

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-29-generic 4.15.0-29.31
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-29-generic.
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  testtest756 F pulseaudio
   /dev/snd/controlC1:  testtest756 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'NVidia_1'/'HDA NVidia at 0xfe02 irq 22'
 Mixer name : 'Realtek ALC1200'
 Components : 'HDA:10ec0888,10ec,00100101 
HDA:10de0002,10de0101,0010'
 Controls  : 56
 Simple ctrls  : 21
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xfcffc000 irq 16'
 Mixer name : 'Nvidia GPU 42 HDMI/DP'
 Components : 'HDA:10de0042,38422651,00100100'
 Controls  : 21
 Simple ctrls  : 3
  CurrentDesktop: LXDE
  Date: Thu Jul 26 17:10:58 2018
  HibernationDevice: RESUME=UUID=17e70869-516d-4b63-b900-e92e3c4b73b6
  InstallationDate: Installed on 2018-07-26 (0 days ago)
  InstallationMedia: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: 113 1
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=71cf0a32-7827-49be-a2c0-cd50a72c26a1 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   0: phy0: Wireless LAN
  

[Kernel-packages] [Bug 1789746] Re: getxattr: always handle namespaced attributes

[Stéphane Graber]

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

** Also affects: linux (Ubuntu Cosmic)
   Importance: High
   Status: Triaged

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

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

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Bionic)
   Importance: Undecided => High

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

Title:
  getxattr: always handle namespaced attributes

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Cosmic:
  Triaged

Bug description:
  Hey everyone,

  When running in a container with a user namespace, if you call getxattr
  with name = "system.posix_acl_access" and size % 8 != 4, then getxattr
  silently skips the user namespace fixup that it normally does resulting in
  un-fixed-up data being returned.
  This is caused by posix_acl_fix_xattr_to_user() being passed the total
  buffer size and not the actual size of the xattr as returned by
  vfs_getxattr().

  I have pushed a commit upstream that fixes this bug:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=82c9a927bc5df6e06b72d206d24a9d10cced4eb5

  
  This commit passes the actual length of the xattr as returned by
  vfs_getxattr() down.

  A reproducer for the issue is:

touch acl_posix

setfacl -m user:0:rwx acl_posix

  and the compile:

#define _GNU_SOURCE
#include 
#include 
#include 
#include 
#include 
#include 
#include 

/* Run in user namespace with nsuid 0 mapped to uid != 0 on the host. */
int main(int argc, void **argv)
{
ssize_t ret1, ret2;
char buf1[128], buf2[132];
int fret = EXIT_SUCCESS;
char *file;

if (argc < 2) {
fprintf(stderr,
"Please specify a file with "
"\"system.posix_acl_access\" permissions set\n");
_exit(EXIT_FAILURE);
}
file = argv[1];

ret1 = getxattr(file, "system.posix_acl_access",
buf1, sizeof(buf1));
if (ret1 < 0) {
fprintf(stderr, "%s - Failed to retrieve "
"\"system.posix_acl_access\" "
"from \"%s\"\n", strerror(errno), file);
_exit(EXIT_FAILURE);
}

ret2 = getxattr(file, "system.posix_acl_access",
buf2, sizeof(buf2));
if (ret2 < 0) {
fprintf(stderr, "%s - Failed to retrieve "
"\"system.posix_acl_access\" "
"from \"%s\"\n", strerror(errno), file);
_exit(EXIT_FAILURE);
}

if (ret1 != ret2) {
fprintf(stderr, "The value of \"system.posix_acl_"
"access\" for file \"%s\" changed "
"between two successive calls\n", file);
_exit(EXIT_FAILURE);
}

for (ssize_t i = 0; i < ret2; i++) {
if (buf1[i] == buf2[i])
continue;

fprintf(stderr,
"Unexpected different in byte %zd: "
"%02x != %02x\n", i, buf1[i], buf2[i]);
fret = EXIT_FAILURE;
}

if (fret == EXIT_SUCCESS)
fprintf(stderr, "Test passed\n");
else
fprintf(stderr, "Test failed\n");

_exit(fret);
}
  and run:

./tester acl_posix

  On a non-fixed up kernel this should return something like:

root@c1:/# ./t
Unexpected different in byte 16: ffa0 != 00
Unexpected different in byte 17: ff86 != 00
Unexpected different in byte 18: 01 != 00

  and on a fixed kernel:

root@c1:~# ./t
Test passed

  
  Please backport this to the 4.15 (bionic) and 4.4 (xenial) kernels. :)

  Thanks!
  Christian

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789746/+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 1789746] [NEW] getxattr: always handle namespaced attributes

[Christian Brauner]

Public bug reported:

Hey everyone,

When running in a container with a user namespace, if you call getxattr
with name = "system.posix_acl_access" and size % 8 != 4, then getxattr
silently skips the user namespace fixup that it normally does resulting in
un-fixed-up data being returned.
This is caused by posix_acl_fix_xattr_to_user() being passed the total
buffer size and not the actual size of the xattr as returned by
vfs_getxattr().

I have pushed a commit upstream that fixes this bug:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=82c9a927bc5df6e06b72d206d24a9d10cced4eb5


This commit passes the actual length of the xattr as returned by
vfs_getxattr() down.

A reproducer for the issue is:

  touch acl_posix

  setfacl -m user:0:rwx acl_posix

and the compile:

  #define _GNU_SOURCE
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  /* Run in user namespace with nsuid 0 mapped to uid != 0 on the host. */
  int main(int argc, void **argv)
  {
  ssize_t ret1, ret2;
  char buf1[128], buf2[132];
  int fret = EXIT_SUCCESS;
  char *file;

  if (argc < 2) {
  fprintf(stderr,
  "Please specify a file with "
  "\"system.posix_acl_access\" permissions set\n");
  _exit(EXIT_FAILURE);
  }
  file = argv[1];

  ret1 = getxattr(file, "system.posix_acl_access",
  buf1, sizeof(buf1));
  if (ret1 < 0) {
  fprintf(stderr, "%s - Failed to retrieve "
  "\"system.posix_acl_access\" "
  "from \"%s\"\n", strerror(errno), file);
  _exit(EXIT_FAILURE);
  }

  ret2 = getxattr(file, "system.posix_acl_access",
  buf2, sizeof(buf2));
  if (ret2 < 0) {
  fprintf(stderr, "%s - Failed to retrieve "
  "\"system.posix_acl_access\" "
  "from \"%s\"\n", strerror(errno), file);
  _exit(EXIT_FAILURE);
  }

  if (ret1 != ret2) {
  fprintf(stderr, "The value of \"system.posix_acl_"
  "access\" for file \"%s\" changed "
  "between two successive calls\n", file);
  _exit(EXIT_FAILURE);
  }

  for (ssize_t i = 0; i < ret2; i++) {
  if (buf1[i] == buf2[i])
  continue;

  fprintf(stderr,
  "Unexpected different in byte %zd: "
  "%02x != %02x\n", i, buf1[i], buf2[i]);
  fret = EXIT_FAILURE;
  }

  if (fret == EXIT_SUCCESS)
  fprintf(stderr, "Test passed\n");
  else
  fprintf(stderr, "Test failed\n");

  _exit(fret);
  }
and run:

  ./tester acl_posix

On a non-fixed up kernel this should return something like:

  root@c1:/# ./t
  Unexpected different in byte 16: ffa0 != 00
  Unexpected different in byte 17: ff86 != 00
  Unexpected different in byte 18: 01 != 00

and on a fixed kernel:

  root@c1:~# ./t
  Test passed


Please backport this to the 4.15 (bionic) and 4.4 (xenial) kernels. :)

Thanks!
Christian

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

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

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

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

Title:
  getxattr: always handle namespaced attributes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hey everyone,

  When running in a container with a user namespace, if you call getxattr
  with name = "system.posix_acl_access" and size % 8 != 4, then getxattr
  silently skips the user namespace fixup that it normally does resulting in
  un-fixed-up data being returned.
  This is caused by posix_acl_fix_xattr_to_user() being passed the total
  buffer size and not the actual size of the xattr as returned by
  vfs_getxattr().

  I have pushed a commit upstream that fixes this bug:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=82c9a927bc5df6e06b72d206d24a9d10cced4eb5

  
  This commit passes the actual length of the xattr as returned by
  vfs_getxattr() down.

  A reproducer for the issue is:

touch acl_posix

setfacl -m user:0:rwx acl_posix

  and the compile:

#define _GNU_SOURCE
#include 
#include 
#include 
#include 
#include 
#include 
#include 

/* Run in user namespace with nsuid 0 mapped to uid != 0 on the host. */
int main(int argc, void **argv)
{
ssize_t ret1, ret2;
  

[Kernel-packages] [Bug 1781049] Re: WiFI hard blocked after resuming laptop (RTL 8723BE)

[Dexter]

Hello!
I've tested the rc1 release kernel (4.19.0-041900rc1-generic), and sure enough, 
the bug persists. WiFi hard-blocked after suspend-resume. 

Driver issues can be ruled out as I've installed a new wifi card form intel 
(Wireless 3165, iwlwifi driver: 4.19.0-041900rc1-generic, firmware: 
29.1044073957.0)
and the problem exists with both the cards, on both the kernel versions. 

As far as I know, from dmesg, reports that some hardware switch is being 
flipped, while there is none on my model (HP AB035TX - Manual here [0]).
The 'Airplane Mode' key only works on soft blocks. 

Any solutions are really helpful!
Thank you very much for your time!
Regards, 
Dexter

[0] My Laptop manual - http://h10032.www1.hp.com/ctg/Manual/c04642845

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

Title:
  WiFI hard blocked after resuming laptop (RTL 8723BE)

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  I installed a fresh copy of Ubuntu 18.04 and everything seems to work
  fine, till I suspended and resumed the laptop. After resume, the wifi
  is hard blocked is rfkill. Reinstalling drivers, different drivers,
  nothing helped. All this was done under Secure Boot disabled under
  Ubuntu and BIOS (UEFI).

  The WiFI card is Realtek 8723BE. laptop is HP AB035TX Pavilion 15. If
  any further info is required, I'll add it on notification. I am
  familiar with Linux, any help will be really appreciated.

  
  P.S: If this wifi card is the issue, please suggest some PCI-mini card that 
will work with my Ubuntu, even after suspend and resume (Ideally a 2.4/5G + BT 
5.0)

  Thank you all!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mythreya   1281 F pulseaudio
   /dev/snd/controlC1:  mythreya   1281 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-06-26 (16 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.6 metric 600
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 05c8:0379 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion Notebook
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=300b2c4a-387a-49b5-9cb6-93de471ebbdb ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.87
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8096
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 89.33
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.87:bd02/26/2018:svnHewlett-Packard:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8096:rvr89.33:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
   [connection]
   wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-30T14:39:45.608645
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2018-06-28T16:23:51.596655
  nmcli-con:
   NAME   UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE 
   NETGEAR71  

[Kernel-packages] [Bug 1781049] Re: WiFI hard blocked after resuming laptop (RTL 8723BE)

[Dexter]

** Tags removed: rtl8723be
** Tags added: kernel-bug-exists-upstream resume suspend

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

Title:
  WiFI hard blocked after resuming laptop (RTL 8723BE)

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  I installed a fresh copy of Ubuntu 18.04 and everything seems to work
  fine, till I suspended and resumed the laptop. After resume, the wifi
  is hard blocked is rfkill. Reinstalling drivers, different drivers,
  nothing helped. All this was done under Secure Boot disabled under
  Ubuntu and BIOS (UEFI).

  The WiFI card is Realtek 8723BE. laptop is HP AB035TX Pavilion 15. If
  any further info is required, I'll add it on notification. I am
  familiar with Linux, any help will be really appreciated.

  
  P.S: If this wifi card is the issue, please suggest some PCI-mini card that 
will work with my Ubuntu, even after suspend and resume (Ideally a 2.4/5G + BT 
5.0)

  Thank you all!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mythreya   1281 F pulseaudio
   /dev/snd/controlC1:  mythreya   1281 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-06-26 (16 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.6 metric 600
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 05c8:0379 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion Notebook
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=300b2c4a-387a-49b5-9cb6-93de471ebbdb ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.87
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8096
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 89.33
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.87:bd02/26/2018:svnHewlett-Packard:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8096:rvr89.33:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
   [connection]
   wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-30T14:39:45.608645
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2018-06-28T16:23:51.596655
  nmcli-con:
   NAME   UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE 
   NETGEAR71  1a9d81bf-e7f5-4f8a-956f-96180dc493e1  wifi  1531450229  Thu 
12 Jul 2018 09:50:29 PM CDT  yes  0 no
/org/freedesktop/NetworkManager/Settings/2  yes wlo1activated  
/org/freedesktop/NetworkManager/ActiveConnection/2  --
   Ethernet   81087af0-5c8d-451f-84c0-1a95c6034098  ethernet  1530214661  Thu 
28 Jun 2018 02:37:41 PM CDT  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  no  --  -- --   
   --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID   

[Kernel-packages] [Bug 1788623] Re: regression: IPv6 PMTU discovery fails with source-specific routing

[Mikael Magnusson]

Yes, kernel 4.14.0-041400rc3-generic resolves the bug. The test case in
#1 succeeds with that kernel.

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

Title:
  regression: IPv6 PMTU discovery fails with source-specific routing

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  IPv6 PMTU discovery fails when using source-specific routing on Ubuntu
  18.04.

  I have attached a test case called pmtu-sads.sh which is based on
  tools/testing/selftests/net/pmtu.sh in the linux source.

  I have verified that the test fails on:
  Ubuntu 18.04 with 4.15.0-30.32
  Ubuntu 18.04 with 4.17.0-041700.201806041953
  Ubuntu 18.04 with 4.18.3-041803.201808180530

  The test succeeds on Ubuntu 16.04 with 4.4.0.131.137 which makes it a
  regression.

  System information:
  Ubuntu 4.15.0-30.32-generic 4.15.18

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  See below for a patch which is working for me. I'm currently using linux 
kernel 4.15.0-32.35 built from git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git 
with this patch.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-30-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=041f6e1e-4904-4760-8518-3a88dc288556 ro splash quiet vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-30-generic N/A
   linux-backports-modules-4.15.0-30-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-30-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-bionic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-bionic
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788623/+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 1783267] Re: linux-modules-extra breaks virtualbox guest modules

[Gianfranco Costamagna]

can you please try a systemctl cat virtualbox-guest-utils-hwe when the
system is not starting?

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

Title:
  linux-modules-extra breaks virtualbox guest modules

Status in linux package in Ubuntu:
  Confirmed
Status in virtualbox-hwe package in Ubuntu:
  New

Bug description:
  linux-modules-extra-4.15.0-29-generic installs virtualbox guest
  modules that are newer than what virtualbox-guest-dkms-hwe provides
  (5.2.8 vs 5.1.34):

  $ modinfo 
/lib/modules/4.15.0-29-generic/kernel/drivers/staging/vboxvideo/vboxvideo.ko
  filename:   
/lib/modules/4.15.0-29-generic/kernel/drivers/staging/vboxvideo/vboxvideo.ko
  license:GPL and additional rights
  description:Oracle VM VirtualBox Graphics Card
  author: Oracle Corporation
  srcversion: 689EDF1E50DE15779B4F930
  alias:  pci:v80EEdBEEFsv*sd*bc*sc*i*
  depends:drm,drm_kms_helper,ttm
  staging:Y
  retpoline:  Y
  intree: Y
  name:   vboxvideo
  vermagic:   4.15.0-29-generic SMP mod_unload 
  parm:   modeset:Disable/Enable modesetting (int)

  $ modinfo /lib/modules/4.15.0-29-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko 
  filename:   
/lib/modules/4.15.0-29-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko
  version:5.2.8_KernelUbuntu r120774
  alias:  fs-vboxsf
  license:GPL
  author: Oracle Corporation
  description:Oracle VM VirtualBox VFS Module for Host File System Access
  srcversion: AF89497125574B5225F9B6A
  depends:vboxguest
  retpoline:  Y
  intree: Y
  name:   vboxsf
  vermagic:   4.15.0-29-generic SMP mod_unload 
  parm:   follow_symlinks:Let host resolve symlinks rather than showing 
them (int)

  $ modinfo 
/lib/modules/4.15.0-29-generic/kernel/ubuntu/vbox/vboxguest/vboxguest.ko 
  filename:   
/lib/modules/4.15.0-29-generic/kernel/ubuntu/vbox/vboxguest/vboxguest.ko
  version:5.2.8_KernelUbuntu r120774
  license:GPL
  description:Oracle VM VirtualBox Guest Additions for Linux Module
  author: Oracle Corporation
  srcversion: F2E5886E3B0544500D404A1
  alias:  pci:v80EEdCAFEsvsdbc*sc*i*
  depends:
  retpoline:  Y
  intree: Y
  name:   vboxguest
  vermagic:   4.15.0-29-generic SMP mod_unload

  Thus installation with dkms fails (while attempting `apt-get install
  --reinstall virtualbox-guest-dkms-hwe`):

  Building initial module for 4.15.0-29-generic
  Done.

  vboxguest:
  Running module version sanity check.
  Error! Module version 5.1.34_Ubuntu for vboxguest.ko
  is not newer than what is already found in kernel 4.15.0-29-generic 
(5.2.8_KernelUbuntu).
  You may override by specifying --force.

  vboxsf.ko:
  Running module version sanity check.
  Error! Module version 5.1.34_Ubuntu for vboxsf.ko
  is not newer than what is already found in kernel 4.15.0-29-generic 
(5.2.8_KernelUbuntu).
  You may override by specifying --force.

  vboxvideo.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.15.0-29-generic/updates/dkms/

  depmod

  DKMS: install completed.

  
  My system does not start correctly with kernel 4.15 and I had to fall back to 
4.13 which has working virtualbox guest modules.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-modules-extra-4.15.0-29-generic 4.15.0-29.31~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Jul 24 08:33:57 2018
  InstallationDate: Installed on 2015-02-04 (1265 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: linux-hwe
  UpgradeStatus: Upgraded to xenial on 2016-08-02 (720 days ago)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dyslimet   3006 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=c045d946-13ab-48d3-afa0-2496f98eb0a4
  InstallationDate: Installed on 2015-02-04 (1266 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
   
   docker0   no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 80ee:0022 VirtualBox 
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: innotek GmbH VirtualBox
  Package: virtualbox-hwe
  ProcFB: 0 vboxdrmfb
  

[Kernel-packages] [Bug 1684240] Re: Lagging square around mouse pointer

[Witold Burkiewicz]

Crippling your system (switching to xrender and much slower nouveau driver) is 
not a solution.
What works for me flawlessly for more than a week on KDE Neon:
In file:
   /lib/systemd/system/sddm.service
Add:
   ExecStartPre=/bin/sleep 10
After [Service]
The problem apparently is that something SDDM needs is not initialized before 
is starts, so delaying SDDM by 10 sec is adequate workaround. Perhaps it could 
be less, but it doesn't bother me as long as I don't have to log out/log in 
manually.

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

Title:
  Lagging square around mouse pointer

Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in plasma-workspace package in Ubuntu:
  Confirmed

Bug description:
  (This can also be an nvidia related problem)

  Mouse pointer behaves as if it has an invisible square attached to it.
  This square covers some area next to the pointer, but it is not always
  clear exactly where (a link to a screenshot is shown below, please
  note the white square with some text from the previous webpage
  displayed in that window).

  This makes selecting text difficult, as one never knows where exactly
  the selection ends. Also, scrolling in some windows becomes
  problematic, as the pointer shadows a part of the scrollbar. When a
  text is being typed, one needs to make sure that the pointer is parked
  sufficiently far from the text (so, to make a long story short, this
  is very annoying).

  This behavior does not depend on the choice of the cursor theme.

  (A link to the screenshot: https://goo.gl/photos/92KKGyFs3AkdxYb79)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: plasma-workspace 4:5.9.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Apr 19 10:41:58 2017
  InstallationDate: Installed on 2015-06-05 (684 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: plasma-workspace
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1684240/+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 1779817] Re: r8169 no internet after suspending

[Seth Forshee]

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

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

Title:
  r8169 no internet after suspending

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  New

Bug description:
  ===SRU Justification===
  [Impact]
  r8169 failed to establish connection after the fix for LP: #1752772
  landed.

  [Fix]
  Accepts BIOS WoL settings again, and disables MSI-X for certain chip
  revisions.

  [Test]
  Users confirmed the fix worked for them.

  [Regression Potential]
  Low. This brings back the old behavior for both WoL and MSI.

  ===Original Bug Report===
  When my computer wakes up from suspending, there's no internet. Unplugging 
and replugging cable doesn't work, restarting network service doesn't work 
also. Only after restarting the computer, internet comes back.
  It only started happening after I freshly installed Ubuntu Budgie (18.04) and 
did all the system updates. Before I was using Ubuntu with Unity (16.04) and 
there was no problems with my internet.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-24-generic 4.15.0-24.26
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  minihydra   2085 F pulseaudio
   /dev/snd/controlC0:  minihydra   2085 F pulseaudio
   /dev/snd/controlC1:  minihydra   2085 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Tue Jul  3 10:13:19 2018
  HibernationDevice: RESUME=UUID=3747bab8-c258-4600-bc24-5d1f56a642dd
  InstallationDate: Installed on 2018-07-02 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IwConfig:
   enp2s0no wireless extensions.

   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=a5ceb36e-76f7-4bd4-a37b-0b91b995c635 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/28/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A77T
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2103:bd06/28/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A77T:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817/+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 1783651] Re: Please enable CONFIG_PAGE_POISONING

[Seth Forshee]

** Changed in: linux (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

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

Title:
  Please enable CONFIG_PAGE_POISONING

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  I'd like to be able to use page poisoning, but CONFIG_PAGE_POISONING
  is not enabled on Ubuntu. (This option itself has a near-zero
  performance impact since it must be combined with the boot option
  "page_poison=1" to actually enable the poisoning.)

  To make the poisoning (when enabled) less of an impact, I'd also like
  to see CONFIG_PAGE_POISONING_ZERO=y too, which means GFP_ZEROing can
  be skipped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783651/+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 1787945] Re: Tango platform uses __initcall without further checks

[Seth Forshee]

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

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

Title:
  Tango platform uses __initcall without further checks

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  New

Bug description:
  Impact:

  The TANGO platform (an embedded soc used in home entertainment,
  connectivity and control devices) is enabled by default in the generic
  arm kernel. During kernel bootup, the tango platform blindly registers
  its pm ops in arch/arm/mach-tango/pm.c via initcalls() (without
  checking whether it's actually running on the correspondent hardware)
  and this causes OOPS during suspend on tegra platforms since the tango
  pm .enter function directly pokes the underlying hardware.

  Given the narrow scope of this SOC, i propose to disable support for
  the TANGO arch.

  Fix:

  Apply the attached patch and recompile.

  How to test:

  Suspend the tegra board and chek that it worked - either close the laptop
  lid, 'systemctl suspend' or:

  # echo -n mem > /sys/power/state

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787945/+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 1789145] Re: Microphone cannot be detected with front panel audio combo jack on HP Z8-G4 machine

[Seth Forshee]

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

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

Title:
  Microphone cannot be detected with front panel audio combo jack on HP
  Z8-G4 machine

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  New

Bug description:
  
  [Impact]
  This bug comes from OEM cert project of HP, the front mic jack can't detect
  any plug/unplug, and we can't record any sound from plugged mic. This is a
  block for OEM project.

  [Fix]
  The fix comes from Realtek, it is said that this is a power issue, after 
changing
  the capability of the pin of linein, the power will keep being on for both 
linein
  and front mic, then this issue is fixed.

  [Test Case]
  We tested plug/unplug detection and record through iphone/nokia type 
headset-mic,
  all worked well.

  [Regression Potential]
  none, this is new added quirk, and only apply to the specific machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1789145/+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 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04

[Simon Ádám]

UPDATE:
I wanted to try out installing 18.04.1
After having the live mode started and opening the menu my laptop shutted down 
suddenly and it is hot now.
Also it somehow messing up the fan. I have to restart from Windows to have it 
sound and work fine.
Windows is running like charm, no overheats.

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

Title:
  Ubuntu 18.04 is overheating after upgrade from 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu is overheating at my laptop. Opening youtube on firefox is
  enough for critical temperature shutdown.

  Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C 
with only firefox or chrome open and doing nothing. 
  On my old 16.04 with same using, the temp varies between 55 and 70°C.

  First thought was the driver nouveau is the problem, and finally I was
  able to install by add "nouveau.modeset=0" at livecd boot options,
  without temp shutdown.

  After install I disable the nouveau at modprobe blacklist, but the
  system continues overheating and shutdown with basic usage.

  
  I have no idea what's happening with the bionic at my laptop.

  My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 16:22:40 2018
  InstallationDate: Installed on 2018-04-27 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptHistorylog:
   Start-Date: 2018-04-27  15:46:02
   End-Date: 2018-04-27  15:46:02
  VarLogDistupgradeAptlog:
   Log time: 2018-04-27 15:45:39.753331
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
   Log time: 2018-04-27 15:46:04.859979
  VarLogDistupgradeApttermlog:
   Log started: 2018-04-27  15:46:02
   Log ended: 2018-04-27  15:46:02
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edir   2354 F pulseaudio
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family 
Integrated Graphics Controller [144d:c0a5]
 Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5]
  HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d
  InstallationDate: Installed on 2018-04-27 (36 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-nouveau 1:1.0.15-2
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 10HX.M034.20110426.SSH
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: RF511/RF411/RF711
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: 10HX
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 

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

[gagzou]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1789653/+attachment/5182329/+files/UdevDb.txt

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

** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => 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/1789653

Title:
  regression with EXT4 file systems and meta_bg flag

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Hello,

  In 16.04 lts (Ubuntu 4.4.0-134.160-generic 4.4.140) with all
  partitions in ext4 with flag meta_bg :

  kernel: [ 1905.799557] EXT4-fs (dm-7): ext4_check_descriptors: Block bitmap 
for group 0 overlaps block group descriptors
  kernel: [ 1905.799858] EXT4-fs (dm-7): group descriptors corrupted!

  Go back with the kernel 4.4.0-133-generic and all partitions mount
  correctly.

  It looks like this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/commit/?id=44de022c4382541cebdd6de4465d1f4f465ff1dd

  The patch is available in 4.4.147 (https://lwn.net/Articles/762083/)
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   août 29 21:01:28 Template1604LTS kernel: [UFW BLOCK] IN=admin OUT= 

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

[gagzou]

apport information

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

Title:
  regression with EXT4 file systems and meta_bg flag

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Hello,

  In 16.04 lts (Ubuntu 4.4.0-134.160-generic 4.4.140) with all
  partitions in ext4 with flag meta_bg :

  kernel: [ 1905.799557] EXT4-fs (dm-7): ext4_check_descriptors: Block bitmap 
for group 0 overlaps block group descriptors
  kernel: [ 1905.799858] EXT4-fs (dm-7): group descriptors corrupted!

  Go back with the kernel 4.4.0-133-generic and all partitions mount
  correctly.

  It looks like this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/commit/?id=44de022c4382541cebdd6de4465d1f4f465ff1dd

  The patch is available in 4.4.147 (https://lwn.net/Articles/762083/)
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   août 29 21:01:28 Template1604LTS kernel: [UFW BLOCK] IN=admin OUT= 
MAC=01:00:5e:00:00:01:a0:1b:29:89:4f:1a:08:00 SRC=192.168.1.1 DST=224.0.0.1 
LEN=32 TOS=0x00 PREC=0x80 TTL=1 ID=0 DF PROTO=2 
   août 29 21:02:08 

[Kernel-packages] [Bug 575542] Re: resize2fs does not respect flex_bg

[Theodore Ts'o]

Yes, this has been fixed quite a while ago.  :-)

Online resize with flex_bg was fixed in 2012 --- call with the v3.10
kernel or so.

Offline resize was fixed around that time (e2fsprogs 1.43), but there
have been some bugs with flex_bg and off-line resizing, so I'd recommend
using at least e2fsprogs 1.44.x if you want to off-line resize file
systems with flex_bg.  And on-line resizing is actually going to be
safer in general --- mainly because it's less capable --- the scary bits
with off-line resizing are things that on-line resize can't do, like
shrink the file system or move the inode table around to make room for
more block group descriptors than were originally reserved at mkfs time.

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

Title:
  resize2fs does not respect flex_bg

Status in e2fsprogs package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: e2fsprogs

  When running resize2fs to perform an online extend of an ext4
  filesystem, it does not respect the flex_bg feature.  Instead, it lays
  out the added block groups with their normal non flex_bg positions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/575542/+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 1786902] Re: [18.10 FEAT] SMC-Direct

[Seth Forshee]

Applied the list provided, excluding
ddb457c6993babbcdd41fca638b870d2a2fc3941, to our unstable (4.18) branch
for cosmic. I'm not applying this to 4.17 as I expect the next kernel we
upload for cosmic to be based on 4.18.

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

** Changed in: linux (Ubuntu)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee 
(sforshee)

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

Title:
  [18.10 FEAT] SMC-Direct

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Provide support for next generation HiperSockets.
  SMC-local (Shared Memory Communications -- local) provides a new architecture 
for high performance networking within a CEC. Buffers in the HSA can be shared 
between LPARs and will be used for communication.
  A new socket family will be used to eliminate TCP overhead. Integration with 
existing tooling through TCP handshaking.
  A preload library can be used to enable applications to use the new socket 
family transparently

  Backport from kernel 4.19 will be attached.

  For SMC enabling following kernel config has to be set
  CONFIG_HAVE_PNETID.

  With this setting an additoiponal modul need to be build : pnet.ko

  @canonical kernel team:
  please cherrypick:
  Here you go - sorry for the delay!
  In sequence, from oldest to latest:

  ddb457c6993babbcdd41fca638b870d2a2fc3941
  be6a3f38ff2a2bfd2e591fdc566940a0d4d9428c
  0afff91c6f5ecef27715ea71e34dc2baacba1060
  c6ba7c9ba43de1b57e9a53946e7ff988554c84ed
  1619f770589a183af56f248de261534b255122de
  c758dfddc1b5b1c9b8c64e5e4bb9bf24b74f4a59
  be244f28d22f77d939ba2b973c102ad2b49d3496
  413498440e30bfe381ac99dfc31628a3d8d4382a
  4b1b7d3b30a6d32ac1a1dcede284e76ef8a8542d
  c601171d7a60b5b09d7c2fe0579953323a80744e
  bac6de7b637018f4caacfdf2b4ad8c8749de7420
  00e5fb263f9f5f2af60754b79b7dcec0d5e88154
  144ce4b9b5a788953b5373162a1921267497fb38
  48bf5231771c7e3961c8326353b6027b1bed6eb5
  12c36dcfd6f48ece2fce4dc8e6ce68224d005d37
  2e3bbe46b4a18d16314dab0c0efdba0c079a5ed0
  947541f36c561b5e0ca639ffc450a8c5221de467
  7005ada68d1774d7c1109deaba0c2cd8e46f5091
  603cc1498455cf57f5ca4483b600efb37ea2c56c
  0d18a0cb4b1585d9e5a3b300d5df9ed866561ffb
  dd979b4df817e9976f18fb6f9d134d6bc4a3c317
  0d86caff06363151df21603eb1f4e3207ea91bd2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1786902/+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 1789653] Re: regression with EXT4 file systems and meta_bg flag

[gagzou]

The kernel test resolves the bug.
The partition mount correctly at startup, I do not remain block at boot 
(emergency mode).
Only difference, I'm with a minimal kernel 
(linux-image-virtual/linux-headers-virtual).

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

Title:
  regression with EXT4 file systems and meta_bg flag

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Hello,

  In 16.04 lts (Ubuntu 4.4.0-134.160-generic 4.4.140) with all
  partitions in ext4 with flag meta_bg :

  kernel: [ 1905.799557] EXT4-fs (dm-7): ext4_check_descriptors: Block bitmap 
for group 0 overlaps block group descriptors
  kernel: [ 1905.799858] EXT4-fs (dm-7): group descriptors corrupted!

  Go back with the kernel 4.4.0-133-generic and all partitions mount
  correctly.

  It looks like this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/commit/?id=44de022c4382541cebdd6de4465d1f4f465ff1dd

  The patch is available in 4.4.147 (https://lwn.net/Articles/762083/)
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   août 29 21:01:28 Template1604LTS kernel: [UFW BLOCK] IN=admin OUT= 
MAC=01:00:5e:00:00:01:a0:1b:29:89:4f:1a:08:00 SRC=192.168.1.1 DST=224.0.0.1 
LEN=32 

[Kernel-packages] [Bug 1788766] Re: linux: 4.4.0-135.161 -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux: 4.4.0-135.161 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1788767 (linux-aws), bug 1788768 (linux-lts-xenial)
  derivatives: bug 1788769 (linux-aws), bug 1788770 (linux-euclid), bug 1788771 
(linux-kvm), bug 1788772 (linux-raspi2), bug 1788773 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788766/+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 1788769] Re: linux-aws: 4.4.0-1067.77 -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux-aws: 4.4.0-1067.77 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  New

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1788766
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788769/+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 1788767] Re: linux-aws: 4.4.0-1029.32 -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux-aws: 4.4.0-1029.32 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  New

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1788766
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788767/+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 1788771] Re: linux-kvm: 4.4.0-1033.39 -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux-kvm: 4.4.0-1033.39 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Xenial:
  New

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1788766
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788771/+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 1789519] Re: Low Memory corruption logged in syslog

[Tim Newby]

Tested the 4.19-rc1 upstream kernel (4.19.0-041900rc1)
and the issue still exists!

dmesg output showing "Memory corruption detected in low memory"
attached.


** Attachment added: "Low Memory Corruption - dmesg for kernel 4.19-rc1.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789519/+attachment/5182330/+files/Low%20Memory%20Corruption%20-%20dmesg%20for%20kernel%204.19-rc1.txt

** Tags added: kernel-bug-exists-upstream

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

Title:
  Low Memory corruption logged in syslog

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dell Inspiron 3847 Desktop running Ubuntu 18.04.1 LTS
  kernel: 4.15.0-33-generic

  Corrupted low memory messages logged in syslog

  Can be reproduced with script:

  #!/bin/bash

  # log to syslog...
  logger -st low_mem_corruption.sh "Checking for low memory corruption with 
kernel $(uname -rv)..."

  # this will cause syslog messages on affected kernels...
  cat /proc/i8k

  logger -st low_mem_corruption.sh "Please wait for 90 secs to ensure low 
memory test has completed..."
  # sleep for 1.5 mins - enough time for mem check every 60 secs...
  sleep 90
  logger -st low_mem_corruption.sh "Check for low memory corruption done! Was 
anything logged in syslog?"

  
  Kernels tested:
  Kernel 4.15.0-29-generic - fine
  Kernel 4.15.0-30-generic - fine
  Kernel 4.15.0-30-generic - Never installed, do not know - did it exist?
  Kernel 4.15.0-32-generic - Low Memory corruption!
  Kernel 4.15.0-33-generic - Low Memory corruption!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bossman1316 F pulseaudio
   /dev/snd/pcmC1D0p:   bossman1316 F...m pulseaudio
   /dev/snd/controlC1:  bossman1316 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 28 16:56:01 2018
  HibernationDevice: RESUME=UUID=1c065a24-2acf-43dc-bf3d-1382f3bbf0ac
  InstallationDate: Installed on 2018-05-12 (108 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Inspiron 3847
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=a5dec663-366e-4ecc-a17a-ce4219c54897 ro quiet loglevel=3 splash
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/10/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 088DT1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd05/10/2018:svnDellInc.:pnInspiron3847:pvr:rvnDellInc.:rn088DT1:rvrA01:cvnDellInc.:ct3:cvr:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Inspiron 3847
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789519/+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 1684240] Re: Lagging square around mouse pointer

[djem]

Okey guys i solved this i am on kubuntu i was having the exact same
problem, now to the solution

Go in System Settings > Display and Monitor > Compositor and change Rendering 
backend to xRender
if you still have the same problem get back into x.org/nouveau driver and thats 
it.

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

Title:
  Lagging square around mouse pointer

Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in plasma-workspace package in Ubuntu:
  Confirmed

Bug description:
  (This can also be an nvidia related problem)

  Mouse pointer behaves as if it has an invisible square attached to it.
  This square covers some area next to the pointer, but it is not always
  clear exactly where (a link to a screenshot is shown below, please
  note the white square with some text from the previous webpage
  displayed in that window).

  This makes selecting text difficult, as one never knows where exactly
  the selection ends. Also, scrolling in some windows becomes
  problematic, as the pointer shadows a part of the scrollbar. When a
  text is being typed, one needs to make sure that the pointer is parked
  sufficiently far from the text (so, to make a long story short, this
  is very annoying).

  This behavior does not depend on the choice of the cursor theme.

  (A link to the screenshot: https://goo.gl/photos/92KKGyFs3AkdxYb79)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: plasma-workspace 4:5.9.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Apr 19 10:41:58 2017
  InstallationDate: Installed on 2015-06-05 (684 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: plasma-workspace
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1684240/+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 1789653] Re: regression with EXT4 file systems and meta_bg flag

[Joseph Salisbury]

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

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

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

Title:
  regression with EXT4 file systems and meta_bg flag

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Hello,

  In 16.04 lts (Ubuntu 4.4.0-134.160-generic 4.4.140) with all
  partitions in ext4 with flag meta_bg :

  kernel: [ 1905.799557] EXT4-fs (dm-7): ext4_check_descriptors: Block bitmap 
for group 0 overlaps block group descriptors
  kernel: [ 1905.799858] EXT4-fs (dm-7): group descriptors corrupted!

  Go back with the kernel 4.4.0-133-generic and all partitions mount
  correctly.

  It looks like this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/commit/?id=44de022c4382541cebdd6de4465d1f4f465ff1dd

  The patch is available in 4.4.147 (https://lwn.net/Articles/762083/)
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   août 29 21:01:28 Template1604LTS kernel: [UFW BLOCK] IN=admin OUT= 
MAC=01:00:5e:00:00:01:a0:1b:29:89:4f:1a:08:00 SRC=192.168.1.1 DST=224.0.0.1 
LEN=32 TOS=0x00 PREC=0x80 TTL=1 ID=0 DF PROTO=2 
   août 29 21:02:08 

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

[gagzou]

apport information

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

Title:
  regression with EXT4 file systems and meta_bg flag

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Hello,

  In 16.04 lts (Ubuntu 4.4.0-134.160-generic 4.4.140) with all
  partitions in ext4 with flag meta_bg :

  kernel: [ 1905.799557] EXT4-fs (dm-7): ext4_check_descriptors: Block bitmap 
for group 0 overlaps block group descriptors
  kernel: [ 1905.799858] EXT4-fs (dm-7): group descriptors corrupted!

  Go back with the kernel 4.4.0-133-generic and all partitions mount
  correctly.

  It looks like this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/commit/?id=44de022c4382541cebdd6de4465d1f4f465ff1dd

  The patch is available in 4.4.147 (https://lwn.net/Articles/762083/)
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   août 29 21:01:28 Template1604LTS kernel: [UFW BLOCK] IN=admin OUT= 
MAC=01:00:5e:00:00:01:a0:1b:29:89:4f:1a:08:00 SRC=192.168.1.1 DST=224.0.0.1 
LEN=32 TOS=0x00 PREC=0x80 TTL=1 ID=0 DF PROTO=2 
   août 29 

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

[gagzou]

apport information

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

Title:
  regression with EXT4 file systems and meta_bg flag

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Hello,

  In 16.04 lts (Ubuntu 4.4.0-134.160-generic 4.4.140) with all
  partitions in ext4 with flag meta_bg :

  kernel: [ 1905.799557] EXT4-fs (dm-7): ext4_check_descriptors: Block bitmap 
for group 0 overlaps block group descriptors
  kernel: [ 1905.799858] EXT4-fs (dm-7): group descriptors corrupted!

  Go back with the kernel 4.4.0-133-generic and all partitions mount
  correctly.

  It looks like this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/commit/?id=44de022c4382541cebdd6de4465d1f4f465ff1dd

  The patch is available in 4.4.147 (https://lwn.net/Articles/762083/)
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   août 29 21:01:28 Template1604LTS kernel: [UFW BLOCK] IN=admin OUT= 
MAC=01:00:5e:00:00:01:a0:1b:29:89:4f:1a:08:00 SRC=192.168.1.1 DST=224.0.0.1 
LEN=32 TOS=0x00 PREC=0x80 TTL=1 ID=0 DF PROTO=2 
   août 29 21:02:08 

[Kernel-packages] [Bug 1789653] HookError_generic.txt

[gagzou]

apport information

** Attachment added: "HookError_generic.txt"
   
https://bugs.launchpad.net/bugs/1789653/+attachment/5182324/+files/HookError_generic.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/1789653

Title:
  regression with EXT4 file systems and meta_bg flag

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Hello,

  In 16.04 lts (Ubuntu 4.4.0-134.160-generic 4.4.140) with all
  partitions in ext4 with flag meta_bg :

  kernel: [ 1905.799557] EXT4-fs (dm-7): ext4_check_descriptors: Block bitmap 
for group 0 overlaps block group descriptors
  kernel: [ 1905.799858] EXT4-fs (dm-7): group descriptors corrupted!

  Go back with the kernel 4.4.0-133-generic and all partitions mount
  correctly.

  It looks like this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/commit/?id=44de022c4382541cebdd6de4465d1f4f465ff1dd

  The patch is available in 4.4.147 (https://lwn.net/Articles/762083/)
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   août 29 21:01:28 Template1604LTS kernel: [UFW BLOCK] IN=admin OUT= 
MAC=01:00:5e:00:00:01:a0:1b:29:89:4f:1a:08:00 SRC=192.168.1.1 DST=224.0.0.1 
LEN=32 TOS=0x00 PREC=0x80 TTL=1 ID=0 DF PROTO=2 
   août 29 

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

[gagzou]

apport information

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

Title:
  regression with EXT4 file systems and meta_bg flag

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Hello,

  In 16.04 lts (Ubuntu 4.4.0-134.160-generic 4.4.140) with all
  partitions in ext4 with flag meta_bg :

  kernel: [ 1905.799557] EXT4-fs (dm-7): ext4_check_descriptors: Block bitmap 
for group 0 overlaps block group descriptors
  kernel: [ 1905.799858] EXT4-fs (dm-7): group descriptors corrupted!

  Go back with the kernel 4.4.0-133-generic and all partitions mount
  correctly.

  It looks like this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/commit/?id=44de022c4382541cebdd6de4465d1f4f465ff1dd

  The patch is available in 4.4.147 (https://lwn.net/Articles/762083/)
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   août 29 21:01:28 Template1604LTS kernel: [UFW BLOCK] IN=admin OUT= 
MAC=01:00:5e:00:00:01:a0:1b:29:89:4f:1a:08:00 SRC=192.168.1.1 DST=224.0.0.1 
LEN=32 TOS=0x00 PREC=0x80 TTL=1 ID=0 DF PROTO=2 
   août 29 21:02:08 

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

[gagzou]

apport information

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

Title:
  regression with EXT4 file systems and meta_bg flag

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Hello,

  In 16.04 lts (Ubuntu 4.4.0-134.160-generic 4.4.140) with all
  partitions in ext4 with flag meta_bg :

  kernel: [ 1905.799557] EXT4-fs (dm-7): ext4_check_descriptors: Block bitmap 
for group 0 overlaps block group descriptors
  kernel: [ 1905.799858] EXT4-fs (dm-7): group descriptors corrupted!

  Go back with the kernel 4.4.0-133-generic and all partitions mount
  correctly.

  It looks like this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/commit/?id=44de022c4382541cebdd6de4465d1f4f465ff1dd

  The patch is available in 4.4.147 (https://lwn.net/Articles/762083/)
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   août 29 21:01:28 Template1604LTS kernel: [UFW BLOCK] IN=admin OUT= 
MAC=01:00:5e:00:00:01:a0:1b:29:89:4f:1a:08:00 SRC=192.168.1.1 DST=224.0.0.1 
LEN=32 TOS=0x00 PREC=0x80 TTL=1 ID=0 DF PROTO=2 
   août 29 21:02:08 Template1604LTS 

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

[gagzou]

apport information

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

Title:
  regression with EXT4 file systems and meta_bg flag

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Hello,

  In 16.04 lts (Ubuntu 4.4.0-134.160-generic 4.4.140) with all
  partitions in ext4 with flag meta_bg :

  kernel: [ 1905.799557] EXT4-fs (dm-7): ext4_check_descriptors: Block bitmap 
for group 0 overlaps block group descriptors
  kernel: [ 1905.799858] EXT4-fs (dm-7): group descriptors corrupted!

  Go back with the kernel 4.4.0-133-generic and all partitions mount
  correctly.

  It looks like this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/commit/?id=44de022c4382541cebdd6de4465d1f4f465ff1dd

  The patch is available in 4.4.147 (https://lwn.net/Articles/762083/)
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   août 29 21:01:28 Template1604LTS kernel: [UFW BLOCK] IN=admin OUT= 
MAC=01:00:5e:00:00:01:a0:1b:29:89:4f:1a:08:00 SRC=192.168.1.1 DST=224.0.0.1 
LEN=32 TOS=0x00 PREC=0x80 TTL=1 ID=0 DF PROTO=2 
   août 29 

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

[gagzou]

apport information

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

Title:
  regression with EXT4 file systems and meta_bg flag

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Hello,

  In 16.04 lts (Ubuntu 4.4.0-134.160-generic 4.4.140) with all
  partitions in ext4 with flag meta_bg :

  kernel: [ 1905.799557] EXT4-fs (dm-7): ext4_check_descriptors: Block bitmap 
for group 0 overlaps block group descriptors
  kernel: [ 1905.799858] EXT4-fs (dm-7): group descriptors corrupted!

  Go back with the kernel 4.4.0-133-generic and all partitions mount
  correctly.

  It looks like this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/commit/?id=44de022c4382541cebdd6de4465d1f4f465ff1dd

  The patch is available in 4.4.147 (https://lwn.net/Articles/762083/)
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   août 29 21:01:28 Template1604LTS kernel: [UFW BLOCK] IN=admin OUT= 
MAC=01:00:5e:00:00:01:a0:1b:29:89:4f:1a:08:00 SRC=192.168.1.1 DST=224.0.0.1 
LEN=32 TOS=0x00 PREC=0x80 TTL=1 ID=0 DF PROTO=2 
   août 29 21:02:08 

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

[gagzou]

apport information

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

Title:
  regression with EXT4 file systems and meta_bg flag

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Hello,

  In 16.04 lts (Ubuntu 4.4.0-134.160-generic 4.4.140) with all
  partitions in ext4 with flag meta_bg :

  kernel: [ 1905.799557] EXT4-fs (dm-7): ext4_check_descriptors: Block bitmap 
for group 0 overlaps block group descriptors
  kernel: [ 1905.799858] EXT4-fs (dm-7): group descriptors corrupted!

  Go back with the kernel 4.4.0-133-generic and all partitions mount
  correctly.

  It looks like this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/commit/?id=44de022c4382541cebdd6de4465d1f4f465ff1dd

  The patch is available in 4.4.147 (https://lwn.net/Articles/762083/)
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   août 29 21:01:28 Template1604LTS kernel: [UFW BLOCK] IN=admin OUT= 
MAC=01:00:5e:00:00:01:a0:1b:29:89:4f:1a:08:00 SRC=192.168.1.1 DST=224.0.0.1 
LEN=32 TOS=0x00 PREC=0x80 TTL=1 ID=0 DF PROTO=2 
   août 29 21:02:08 

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

[gagzou]

apport information

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

Title:
  regression with EXT4 file systems and meta_bg flag

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Hello,

  In 16.04 lts (Ubuntu 4.4.0-134.160-generic 4.4.140) with all
  partitions in ext4 with flag meta_bg :

  kernel: [ 1905.799557] EXT4-fs (dm-7): ext4_check_descriptors: Block bitmap 
for group 0 overlaps block group descriptors
  kernel: [ 1905.799858] EXT4-fs (dm-7): group descriptors corrupted!

  Go back with the kernel 4.4.0-133-generic and all partitions mount
  correctly.

  It looks like this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/commit/?id=44de022c4382541cebdd6de4465d1f4f465ff1dd

  The patch is available in 4.4.147 (https://lwn.net/Articles/762083/)
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   août 29 21:01:28 Template1604LTS kernel: [UFW BLOCK] IN=admin OUT= 
MAC=01:00:5e:00:00:01:a0:1b:29:89:4f:1a:08:00 SRC=192.168.1.1 DST=224.0.0.1 
LEN=32 TOS=0x00 PREC=0x80 TTL=1 ID=0 DF PROTO=2 
   août 29 21:02:08 

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

[gagzou]

apport information

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

Title:
  regression with EXT4 file systems and meta_bg flag

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Hello,

  In 16.04 lts (Ubuntu 4.4.0-134.160-generic 4.4.140) with all
  partitions in ext4 with flag meta_bg :

  kernel: [ 1905.799557] EXT4-fs (dm-7): ext4_check_descriptors: Block bitmap 
for group 0 overlaps block group descriptors
  kernel: [ 1905.799858] EXT4-fs (dm-7): group descriptors corrupted!

  Go back with the kernel 4.4.0-133-generic and all partitions mount
  correctly.

  It looks like this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/commit/?id=44de022c4382541cebdd6de4465d1f4f465ff1dd

  The patch is available in 4.4.147 (https://lwn.net/Articles/762083/)
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   août 29 21:01:28 Template1604LTS kernel: [UFW BLOCK] IN=admin OUT= 
MAC=01:00:5e:00:00:01:a0:1b:29:89:4f:1a:08:00 SRC=192.168.1.1 DST=224.0.0.1 
LEN=32 TOS=0x00 PREC=0x80 TTL=1 ID=0 DF PROTO=2 
   août 29 21:02:08 

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

[gagzou]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1789653/+attachment/5182314/+files/UdevDb.txt

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

Title:
  regression with EXT4 file systems and meta_bg flag

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Hello,

  In 16.04 lts (Ubuntu 4.4.0-134.160-generic 4.4.140) with all
  partitions in ext4 with flag meta_bg :

  kernel: [ 1905.799557] EXT4-fs (dm-7): ext4_check_descriptors: Block bitmap 
for group 0 overlaps block group descriptors
  kernel: [ 1905.799858] EXT4-fs (dm-7): group descriptors corrupted!

  Go back with the kernel 4.4.0-133-generic and all partitions mount
  correctly.

  It looks like this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/commit/?id=44de022c4382541cebdd6de4465d1f4f465ff1dd

  The patch is available in 4.4.147 (https://lwn.net/Articles/762083/)
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   août 29 21:01:28 Template1604LTS kernel: [UFW BLOCK] IN=admin OUT= 
MAC=01:00:5e:00:00:01:a0:1b:29:89:4f:1a:08:00 SRC=192.168.1.1 DST=224.0.0.1 
LEN=32 TOS=0x00 PREC=0x80 TTL=1 ID=0 DF PROTO=2 
   août 29 21:02:08 Template1604LTS 

[Kernel-packages] [Bug 1789653] AudioDevicesInUse.txt

[gagzou]

apport information

** Attachment added: "AudioDevicesInUse.txt"
   
https://bugs.launchpad.net/bugs/1789653/+attachment/5182322/+files/AudioDevicesInUse.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/1789653

Title:
  regression with EXT4 file systems and meta_bg flag

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Hello,

  In 16.04 lts (Ubuntu 4.4.0-134.160-generic 4.4.140) with all
  partitions in ext4 with flag meta_bg :

  kernel: [ 1905.799557] EXT4-fs (dm-7): ext4_check_descriptors: Block bitmap 
for group 0 overlaps block group descriptors
  kernel: [ 1905.799858] EXT4-fs (dm-7): group descriptors corrupted!

  Go back with the kernel 4.4.0-133-generic and all partitions mount
  correctly.

  It looks like this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/commit/?id=44de022c4382541cebdd6de4465d1f4f465ff1dd

  The patch is available in 4.4.147 (https://lwn.net/Articles/762083/)
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   août 29 21:01:28 Template1604LTS kernel: [UFW BLOCK] IN=admin OUT= 
MAC=01:00:5e:00:00:01:a0:1b:29:89:4f:1a:08:00 SRC=192.168.1.1 DST=224.0.0.1 
LEN=32 TOS=0x00 PREC=0x80 TTL=1 ID=0 DF PROTO=2 
   août 29 

[Kernel-packages] [Bug 1789653] WifiSyslog.txt

[gagzou]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1789653/+attachment/5182315/+files/WifiSyslog.txt

** Description changed:

  Hello,
  
  In 16.04 lts (Ubuntu 4.4.0-134.160-generic 4.4.140) with all partitions
  in ext4 with flag meta_bg :
  
  kernel: [ 1905.799557] EXT4-fs (dm-7): ext4_check_descriptors: Block bitmap 
for group 0 overlaps block group descriptors
  kernel: [ 1905.799858] EXT4-fs (dm-7): group descriptors corrupted!
  
  Go back with the kernel 4.4.0-133-generic and all partitions mount
  correctly.
  
  It looks like this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/commit/?id=44de022c4382541cebdd6de4465d1f4f465ff1dd
  
  The patch is available in 4.4.147 (https://lwn.net/Articles/762083/)
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
+ --- 
+ AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
+ AplayDevices: Error: [Errno 2] No such file or directory
+ ApportVersion: 2.20.1-0ubuntu2.18
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory
+ CRDA: N/A
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
+ InstallationDate: Installed on 2017-04-28 (488 days ago)
+ InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
+ IwConfig: Error: [Errno 2] No such file or directory
+ Lsusb: Error: [Errno 2] No such file or directory
+ MachineType: VMware, Inc. VMware Virtual Platform
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcEnviron:
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=fr_FR.UTF-8
+  SHELL=/bin/bash
+ ProcFB:
+  
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
+ ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
+ RelatedPackageVersions:
+  linux-restricted-modules-4.4.0-134-generic N/A
+  linux-backports-modules-4.4.0-134-generic  N/A
+  linux-firmware N/A
+ RfKill: Error: [Errno 2] No such file or directory
+ Tags:  xenial xenial xenial
+ Uname: Linux 4.4.0-134-generic x86_64
+ UnreportableReason: The report belongs to a package that is not installed.
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ WifiSyslog:
+  août 29 21:01:28 Template1604LTS kernel: [UFW BLOCK] IN=admin OUT= 
MAC=01:00:5e:00:00:01:a0:1b:29:89:4f:1a:08:00 SRC=192.168.1.1 DST=224.0.0.1 
LEN=32 TOS=0x00 PREC=0x80 TTL=1 ID=0 DF PROTO=2 
+  août 29 21:02:08 Template1604LTS kernel: [UFW BLOCK] IN=admin OUT= 
MAC=01:00:5e:00:00:01:a0:1b:29:89:4f:1a:08:00 SRC=192.168.1.1 DST=224.0.0.1 
LEN=32 TOS=0x00 PREC=0x80 TTL=1 ID=0 DF PROTO=2
+ _MarkForUpload: False
+ dmi.bios.date: 07/31/2013
+ dmi.bios.vendor: Phoenix Technologies LTD
+ dmi.bios.version: 6.00
+ dmi.board.name: 440BX 

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

[gagzou]

apport information

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

Title:
  regression with EXT4 file systems and meta_bg flag

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Hello,

  In 16.04 lts (Ubuntu 4.4.0-134.160-generic 4.4.140) with all
  partitions in ext4 with flag meta_bg :

  kernel: [ 1905.799557] EXT4-fs (dm-7): ext4_check_descriptors: Block bitmap 
for group 0 overlaps block group descriptors
  kernel: [ 1905.799858] EXT4-fs (dm-7): group descriptors corrupted!

  Go back with the kernel 4.4.0-133-generic and all partitions mount
  correctly.

  It looks like this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/commit/?id=44de022c4382541cebdd6de4465d1f4f465ff1dd

  The patch is available in 4.4.147 (https://lwn.net/Articles/762083/)
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   août 29 21:01:28 Template1604LTS kernel: [UFW BLOCK] IN=admin OUT= 
MAC=01:00:5e:00:00:01:a0:1b:29:89:4f:1a:08:00 SRC=192.168.1.1 DST=224.0.0.1 
LEN=32 TOS=0x00 PREC=0x80 TTL=1 ID=0 DF PROTO=2 
   août 29 21:02:08 Template1604LTS 

[Kernel-packages] [Bug 1789653] Re: regression with EXT4 file systems and meta_bg flag

[gagzou]

apport information

** Tags added: apport-collected

** Description changed:

  Hello,
  
  In 16.04 lts (Ubuntu 4.4.0-134.160-generic 4.4.140) with all partitions
  in ext4 with flag meta_bg :
  
  kernel: [ 1905.799557] EXT4-fs (dm-7): ext4_check_descriptors: Block bitmap 
for group 0 overlaps block group descriptors
  kernel: [ 1905.799858] EXT4-fs (dm-7): group descriptors corrupted!
  
  Go back with the kernel 4.4.0-133-generic and all partitions mount
  correctly.
  
  It looks like this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/commit/?id=44de022c4382541cebdd6de4465d1f4f465ff1dd
  
  The patch is available in 4.4.147 (https://lwn.net/Articles/762083/)
+ --- 
+ AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
+ AplayDevices: Error: [Errno 2] No such file or directory
+ ApportVersion: 2.20.1-0ubuntu2.18
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory
+ CRDA: N/A
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
+ InstallationDate: Installed on 2017-04-28 (488 days ago)
+ InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
+ IwConfig: Error: [Errno 2] No such file or directory
+ Lsusb: Error: [Errno 2] No such file or directory
+ MachineType: VMware, Inc. VMware Virtual Platform
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcEnviron:
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=fr_FR.UTF-8
+  SHELL=/bin/bash
+ ProcFB:
+  
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
+ ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
+ RelatedPackageVersions:
+  linux-restricted-modules-4.4.0-134-generic N/A
+  linux-backports-modules-4.4.0-134-generic  N/A
+  linux-firmware N/A
+ RfKill: Error: [Errno 2] No such file or directory
+ Tags:  xenial xenial
+ Uname: Linux 4.4.0-134-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 07/31/2013
+ dmi.bios.vendor: Phoenix Technologies LTD
+ dmi.bios.version: 6.00
+ dmi.board.name: 440BX Desktop Reference Platform
+ dmi.board.vendor: Intel Corporation
+ dmi.board.version: None
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 1
+ dmi.chassis.vendor: No Enclosure
+ dmi.chassis.version: N/A
+ dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
+ dmi.product.name: VMware Virtual Platform
+ dmi.product.version: None
+ dmi.sys.vendor: VMware, Inc.

** Attachment added: "AudioDevicesInUse.txt"
   
https://bugs.launchpad.net/bugs/1789653/+attachment/5182307/+files/AudioDevicesInUse.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/1789653

Title:
  regression with EXT4 file systems and meta_bg flag

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Hello,

  In 16.04 lts (Ubuntu 4.4.0-134.160-generic 4.4.140) with all
  partitions in ext4 with flag meta_bg :

  kernel: [ 1905.799557] EXT4-fs (dm-7): ext4_check_descriptors: Block bitmap 
for group 0 overlaps block group descriptors
  kernel: [ 1905.799858] EXT4-fs (dm-7): group descriptors corrupted!

  Go back with the kernel 4.4.0-133-generic and all partitions mount
  correctly.

  It looks like this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/commit/?id=44de022c4382541cebdd6de4465d1f4f465ff1dd

  The patch is available in 4.4.147 (https://lwn.net/Articles/762083/)
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  

[Kernel-packages] [Bug 1789118] Re: Fails to boot under Xen PV: BUG: unable to handle kernel paging request at edc21fd9

[Joseph Salisbury]

Thanks for the update, Andy.  If you need any specific upstream kernel
versions, they are all prebuilt here:

http://kernel.ubuntu.com/~kernel-ppa/mainline/

Just let me know if you need assistance with a kernel bisect or building
any specific kernels.

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

Title:
  Fails to boot under Xen PV: BUG: unable to handle kernel paging
  request at edc21fd9

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  After the most recent 18.04 32-bit upgrade of linux-image-generic, it
  now refuses to boot under Xen PV mode:

  .
  .
  .
  [0.114370] clocksource: jiffies: mask: 0x max_cycles: 0x, 
max_idle_ns: 764504178510 ns
  [0.114382] futex hash table entries: 256 (order: 2, 16384 bytes)
  [0.114423] pinctrl core: initialized pinctrl subsystem
  [0.134326] RTC time: 165:165:165, date: 165/165/65
  [0.134442] NET: Registered protocol family 16
  [0.134457] xen:grant_table: Grant tables using version 1 layout
  [0.134502] Grant table initialized
  [0.134544] audit: initializing netlink subsys (disabled)
  [0.134611] audit: type=2000 audit(1535307799.132:1): state=initialized 
audit_enabled=0 res=1
  [0.134678] EISA bus registered
  [0.136019] PCI: setting up Xen PCI frontend stub
  [0.136073] BUG: unable to handle kernel paging request at edc21fd9
  [0.136084] IP: eisa_bus_probe+0x19/0x36
  [0.136089] *pdpt = 01ee6027 *pde = 29cc6067 *pte = 
 
  [0.136100] Oops:  [#1] SMP
  [0.136105] Modules linked in:
  [0.136111] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.15.0-33-generic 
#36-Ubuntu
  [0.136120] EIP: eisa_bus_probe+0x19/0x36
  [0.136125] EFLAGS: 00010246 CPU: 0
  [0.136130] EAX: edc21fd9 EBX:  ECX: 01e0d000 EDX: 0200
  [0.136138] ESI: c1d0d452 EDI: c1dd34a4 EBP: e9c89f24 ESP: e9c89f24
  [0.136145]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: e021
  [0.136154] CR0: 80050033 CR2: edc21fd9 CR3: 01e1 CR4: 00042660
  [0.136166] Call Trace:
  [0.136173]  do_one_initcall+0x49/0x174
  [0.136179]  ? parse_args+0x143/0x390
  [0.136187]  ? set_debug_rodata+0x14/0x14
  [0.136193]  kernel_init_freeable+0x149/0x1c5
  [0.136201]  ? rest_init+0xa0/0xa0
  [0.136207]  kernel_init+0xd/0xf0
  [0.136213]  ret_from_fork+0x2e/0x38
  [0.14] Code: ff b8 df 43 ae c1 e8 35 1b 88 ff e8 20 12 88 ff c9 c3 3e 
8d 74 26 00 55 b9 04 00 00 00 31 d2 b8 d9 ff 0f 00 89 e5 e8 35 8d 35 ff <8b> 10 
81 fa 45 49 53 41 75 0a c7 05 a0 76 ed c1 01 00 00 00 e8
  [0.14] EIP: eisa_bus_probe+0x19/0x36 SS:ESP: e021:e9c89f24
  [0.14] CR2: edc21fd9
  [0.14] ---[ end trace 8c00b3cb7d4f06ba ]---
  [0.140013] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009

  This is: [0.00] Linux version 4.15.0-33-generic
  (buildd@lgw01-amd64-038) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3))
  #36-Ubuntu SMP Wed Aug 15 13:44:35 UTC 2018 (Ubuntu
  4.15.0-33.36-generic 4.15.18)

  Switching to a 64-bit kernel allows boot to proceed.

  I cannot include output of the commands you request (uname,
  version_signature, dmesg, lspci) because the guest doesn't boot. The
  above kernel output is from a just-installed clean guest however.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789118/+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 1783906] Re: Linux 4.15 and onwards fails to initialize some hard drives

[Joseph Salisbury]

I built a second test kernel with additional debug output as requested
by David. This kernel also has the two lines removed request by David.

Can you test this kernel and post your syslog or dmesg output?

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1783906

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

Title:
  Linux 4.15 and onwards fails to initialize some hard drives

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  I have two hard drives, the main hard drive is a TOSHIBA DT01ACA200
  the second backup hard drive is a Western Digital WD5003AZEX. I
  installed lubuntu 18.04.1 on the Toshiba HDD and it boots just fine,
  the issue is with the second hard drive, when installing the WD HDD
  wouldn't even come as an option to install, and after boot the WD HDD
  still wouldn't come up, this is the dmesg with the stock kernel (4.15)
  https://paste.ubuntu.com/p/kpxh94v2SK/

  ata6 is the WD HDD that refuses to work. The messages:
  [  302.107650] ata6: SError: { CommWake 10B8B Dispar DevExch }
  [  302.107658] ata6: hard resetting link
  [  307.860291] ata6: link is slow to respond, please be patient (ready=0)
  [  312.120898] ata6: COMRESET failed (errno=-16)
  [  363.445120] INFO: task kworker/u8:5:201 blocked for more than 120 seconds.
  [  363.445131]   Not tainted 4.15.0-29-generic #31-Ubuntu
  [  363.445135] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.445140] kworker/u8:5D0   201  2 0x8000
  [  363.445155] Workqueue: events_unbound async_run_entry_fn
  [  363.445157] Call Trace:
  [  363.445171]  __schedule+0x291/0x8a0
  [  363.445177]  schedule+0x2c/0x80
  [  363.445182]  ata_port_wait_eh+0x7c/0xf0
  [  363.445186]  ? wait_woken+0x80/0x80
  [  363.445189]  ata_port_probe+0x28/0x40
  [  363.445192]  async_port_probe+0x2e/0x52
  [  363.445196]  async_run_entry_fn+0x3c/0x150
  [  363.445199]  process_one_work+0x1de/0x410
  [  363.445203]  worker_thread+0x32/0x410
  [  363.445207]  kthread+0x121/0x140
  [  363.445210]  ? process_one_work+0x410/0x410
  [  363.445214]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  363.445218]  ret_from_fork+0x22/0x40

  Repeat constantly. Also when I try to turn off the computer, the
  computer seem to freeze, the lights of the keyboard and mouse turn off
  and the computer just stay on.

  I tried Tiny Core 9.0 which has linux 4.14.10, and i didn't had this
  issue, i also installed linux 4.14 on this lubuntu 18.04 using Ukuu
  Kernel Update Utility. And with this kernel version, or any previous
  version the WD HDD does work again. Here's a dmesg of lubuntu 18.04
  with linux 4.14 and the WD HDD finally coming up at the end:
  https://paste.ubuntu.com/p/Gd3cGFbjTJ/

  Also tried with with linux 4.17 but the WD HDD would also refuse to
  work on this version. Here's another dmesg with this version:
  https://paste.ubuntu.com/p/PmNn96vZZv/

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-29-generic 4.15.0-29.31
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-29-generic.
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  testtest756 F pulseaudio
   /dev/snd/controlC1:  testtest756 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'NVidia_1'/'HDA NVidia at 0xfe02 irq 22'
 Mixer name : 'Realtek ALC1200'
 Components : 'HDA:10ec0888,10ec,00100101 
HDA:10de0002,10de0101,0010'
 Controls  : 56
 Simple ctrls  : 21
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xfcffc000 irq 16'
 Mixer name : 'Nvidia GPU 42 HDMI/DP'
 Components : 'HDA:10de0042,38422651,00100100'
 Controls  : 21
 Simple ctrls  : 3
  CurrentDesktop: LXDE
  Date: Thu Jul 26 17:10:58 2018
  HibernationDevice: RESUME=UUID=17e70869-516d-4b63-b900-e92e3c4b73b6
  InstallationDate: Installed on 2018-07-26 (0 days ago)
  InstallationMedia: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: 113 1
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=71cf0a32-7827-49be-a2c0-cd50a72c26a1 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2008
  

[Kernel-packages] [Bug 1785739] Re: [Regression] APM Merlin boards fail to recover link after interface down/up

[dann frazier]

** Description changed:

  [Impact]
  On an APM Merlin (X-Gene2) board, the onboard 1G interface fails to 
re-establish link when the interface is brought down and back up. Juju + MAAS 
provider does this after every install (so to configure a bridge), making this 
config unusable.
  
  This was actually a regression introduced by the fix for LP: #1632739 in
  4.4.0-48.69.
  
  [Test Case]
  1) From a remote system, start a ping to the IP address of the Merlin board's 
eth0 interface.
- 2) On the merlin board: sudo ifconfig eth0 down; sudo ifconfig eth0 up
+ 2) On the merlin board: sudo ifdown eth0; sudo ifup eth0
  3) Ping should recover, but doesn't
  
  [Fix]
  commit 84a527a41f38a80353f185d05e41b021e1ff672b
  Author: Shaohui Xie 
  Date:   Tue May 10 17:42:26 2016 +0800
  
  net: phylib: fix interrupts re-enablement in phy_start
  
  [Regression Risk]
  The fix appears to be straightforward - don't enable interrupts on a phy that 
does not have a valid interrupt. Fixes are upstream, so any regressions should 
get upstream support for fixing.

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

Title:
  [Regression] APM Merlin boards fail to recover link after interface
  down/up

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  On an APM Merlin (X-Gene2) board, the onboard 1G interface fails to 
re-establish link when the interface is brought down and back up. Juju + MAAS 
provider does this after every install (so to configure a bridge), making this 
config unusable.

  This was actually a regression introduced by the fix for LP: #1632739
  in 4.4.0-48.69.

  [Test Case]
  1) From a remote system, start a ping to the IP address of the Merlin board's 
eth0 interface.
  2) On the merlin board: sudo ifdown eth0; sudo ifup eth0
  3) Ping should recover, but doesn't

  [Fix]
  commit 84a527a41f38a80353f185d05e41b021e1ff672b
  Author: Shaohui Xie 
  Date:   Tue May 10 17:42:26 2016 +0800

  net: phylib: fix interrupts re-enablement in phy_start

  [Regression Risk]
  The fix appears to be straightforward - don't enable interrupts on a phy that 
does not have a valid interrupt. Fixes are upstream, so any regressions should 
get upstream support for fixing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785739/+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 1789653] Re: regression with EXT4 file systems and meta_bg flag

[Joseph Salisbury]

I built a test kernel with commit 44de022c4382541cebdd6de4465d1f4f465ff1dd.  
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1789653

Can you test this kernel and see if it resolves this bug?

Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the 
linux-image and linux-image-extra .deb packages.
• If the test kernel is 4.15(Bionic) or newer, you need to install the 
linux-modules, linux-modules-extra and linux-image-unsigned .deb packages.

Thanks in advance!

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

Title:
  regression with EXT4 file systems and meta_bg flag

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Hello,

  In 16.04 lts (Ubuntu 4.4.0-134.160-generic 4.4.140) with all
  partitions in ext4 with flag meta_bg :

  kernel: [ 1905.799557] EXT4-fs (dm-7): ext4_check_descriptors: Block bitmap 
for group 0 overlaps block group descriptors
  kernel: [ 1905.799858] EXT4-fs (dm-7): group descriptors corrupted!

  Go back with the kernel 4.4.0-133-generic and all partitions mount
  correctly.

  It looks like this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/commit/?id=44de022c4382541cebdd6de4465d1f4f465ff1dd

  The patch is available in 4.4.147 (https://lwn.net/Articles/762083/)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789653/+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 1784665] Re: mkfs.ext4 over /dev/bcache0 hangs

[Joseph Salisbury]

Thanks for testing.  I was hoping a fix would be in 4.19, but I'll dig
some more.

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

Title:
  mkfs.ext4 over /dev/bcache0 hangs

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  $ cat /proc/version_signature 
  Ubuntu 4.15.0-29.31-generic 4.15.18

  $ lsb_release -rd
  Description:  Ubuntu Cosmic Cuttlefish (development branch)
  Release:  18.10

  $ apt-cache policy linux-image-`uname -r`
  linux-image-4.15.0-29-generic:
Installed: 4.15.0-29.31
Candidate: 4.15.0-29.31
Version table:
   *** 4.15.0-29.31 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  
  3) mkfs.ext4 /dev/bcache0 returns successful creating an ext4 filesystem on 
top of a bcache device

  4) mkfs.ext4 doesn't return and kernel prints hung process info

  [   58.018099] cloud-init[920]: Running command ['mkfs.ext4', '-F', '-L', 
'root-fs', '-U', 'f01aec97-9457-11e8-b8d6-525400123401', '/dev/bcache0'] with 
allowed return codes [0] (capture=True)
  [  242.652018] INFO: task kworker/u4:0:5 blocked for more than 120 seconds.
  [  242.653767]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  242.655391] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  242.657397] INFO: task kworker/0:2:410 blocked for more than 120 seconds.
  [  242.659126]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  242.660980] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  242.663000] INFO: task bcache_allocato:2326 blocked for more than 120 
seconds.
  [  242.664807]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  242.666516] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  242.668503] INFO: task bcache_writebac:2345 blocked for more than 120 
seconds.
  [  242.670301]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  242.671936] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  242.673909] INFO: task mkfs.ext4:2803 blocked for more than 120 seconds.
  [  242.675414]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  242.677038] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.483998] INFO: task kworker/u4:0:5 blocked for more than 120 seconds.
  [  363.488441]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  363.489598] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.491043] INFO: task kworker/0:2:410 blocked for more than 120 seconds.
  [  363.492252]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  363.494085] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.495659] INFO: task bcache_allocato:2326 blocked for more than 120 
seconds.
  [  363.496957]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  363.498454] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.499866] INFO: task bcache_writebac:2345 blocked for more than 120 
seconds.
  [  363.501156]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  363.502597] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.504048] INFO: task mkfs.ext4:2803 blocked for more than 120 seconds.
  [  363.505505]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  363.506677] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.

  
  System has two virtio block devices.  bcache was created like so:

  make-bcache -C /dev/vdb
  make-bcache -B /dev/vda2

  resulting in /dev/bcache0

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.15.0-29-generic 4.15.0-29.31
  ProcVersionSignature: User Name 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 31 15:52 seq
   crw-rw 1 root audio 116, 33 Jul 31 15:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Tue Jul 31 15:53:56 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   

Re: [Kernel-packages] [Bug 1784665] Re: mkfs.ext4 over /dev/bcache0 hangs

[Ryan Harper]

On Wed, Aug 29, 2018 at 12:01 PM Joseph Salisbury
 wrote:
>
> Thanks for digging up this additional information.  I'll investigate
> further.  While I do that, the v4.19-rc1 kernel is now out.  It might be
> worthwhile to give that one a go, and see if the fix was already
> committed to mainline:
>
> http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc1/

v4.19 also hangs like 4.16+ does, but does not oops like 4.15.

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

Title:
  mkfs.ext4 over /dev/bcache0 hangs

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  $ cat /proc/version_signature 
  Ubuntu 4.15.0-29.31-generic 4.15.18

  $ lsb_release -rd
  Description:  Ubuntu Cosmic Cuttlefish (development branch)
  Release:  18.10

  $ apt-cache policy linux-image-`uname -r`
  linux-image-4.15.0-29-generic:
Installed: 4.15.0-29.31
Candidate: 4.15.0-29.31
Version table:
   *** 4.15.0-29.31 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  
  3) mkfs.ext4 /dev/bcache0 returns successful creating an ext4 filesystem on 
top of a bcache device

  4) mkfs.ext4 doesn't return and kernel prints hung process info

  [   58.018099] cloud-init[920]: Running command ['mkfs.ext4', '-F', '-L', 
'root-fs', '-U', 'f01aec97-9457-11e8-b8d6-525400123401', '/dev/bcache0'] with 
allowed return codes [0] (capture=True)
  [  242.652018] INFO: task kworker/u4:0:5 blocked for more than 120 seconds.
  [  242.653767]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  242.655391] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  242.657397] INFO: task kworker/0:2:410 blocked for more than 120 seconds.
  [  242.659126]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  242.660980] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  242.663000] INFO: task bcache_allocato:2326 blocked for more than 120 
seconds.
  [  242.664807]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  242.666516] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  242.668503] INFO: task bcache_writebac:2345 blocked for more than 120 
seconds.
  [  242.670301]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  242.671936] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  242.673909] INFO: task mkfs.ext4:2803 blocked for more than 120 seconds.
  [  242.675414]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  242.677038] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.483998] INFO: task kworker/u4:0:5 blocked for more than 120 seconds.
  [  363.488441]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  363.489598] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.491043] INFO: task kworker/0:2:410 blocked for more than 120 seconds.
  [  363.492252]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  363.494085] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.495659] INFO: task bcache_allocato:2326 blocked for more than 120 
seconds.
  [  363.496957]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  363.498454] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.499866] INFO: task bcache_writebac:2345 blocked for more than 120 
seconds.
  [  363.501156]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  363.502597] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.504048] INFO: task mkfs.ext4:2803 blocked for more than 120 seconds.
  [  363.505505]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  363.506677] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.

  
  System has two virtio block devices.  bcache was created like so:

  make-bcache -C /dev/vdb
  make-bcache -B /dev/vda2

  resulting in /dev/bcache0

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.15.0-29-generic 4.15.0-29.31
  ProcVersionSignature: User Name 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 31 15:52 seq
   crw-rw 1 root audio 116, 33 Jul 31 15:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A

[Kernel-packages] [Bug 1789653] Re: regression with EXT4 file systems and meta_bg flag

[Joseph Salisbury]

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Xenial)
   Status: Triaged => In Progress

** Changed in: linux (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  regression with EXT4 file systems and meta_bg flag

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Hello,

  In 16.04 lts (Ubuntu 4.4.0-134.160-generic 4.4.140) with all
  partitions in ext4 with flag meta_bg :

  kernel: [ 1905.799557] EXT4-fs (dm-7): ext4_check_descriptors: Block bitmap 
for group 0 overlaps block group descriptors
  kernel: [ 1905.799858] EXT4-fs (dm-7): group descriptors corrupted!

  Go back with the kernel 4.4.0-133-generic and all partitions mount
  correctly.

  It looks like this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/commit/?id=44de022c4382541cebdd6de4465d1f4f465ff1dd

  The patch is available in 4.4.147 (https://lwn.net/Articles/762083/)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789653/+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 1789518] Re: automounting MTP or USB storage devices no longer works.

[b]

Update: I can now see that USB storage devices are automounted. This was
resolved by installing gvfs:

sudo apt-get install gvfs
[sudo] password for bbogart: 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  gvfs-daemons gvfs-libs
Suggested packages:
  gvfs-backends
The following NEW packages will be installed:
  gvfs gvfs-daemons gvfs-libs
0 upgraded, 3 newly installed, 0 to remove and 41 not upgraded.
Need to get 323 kB of archives.
After this operation, 1,305 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://mirrors.accretive-networks.net/ubuntu bionic-updates/main amd64 
gvfs-libs amd64 1.36.1-0ubuntu1.1 [95.1 kB]
Get:2 http://mirrors.accretive-networks.net/ubuntu bionic-updates/main amd64 
gvfs-daemons amd64 1.36.1-0ubuntu1.1 [116 kB]
Get:3 http://mirrors.accretive-networks.net/ubuntu bionic-updates/main amd64 
gvfs amd64 1.36.1-0ubuntu1.1 [111 kB]
Fetched 323 kB in 1s (393 kB/s)
Selecting previously unselected package gvfs-libs:amd64.
(Reading database ... 333054 files and directories currently installed.)
Preparing to unpack .../gvfs-libs_1.36.1-0ubuntu1.1_amd64.deb ...
Unpacking gvfs-libs:amd64 (1.36.1-0ubuntu1.1) ...
Selecting previously unselected package gvfs-daemons.
Preparing to unpack .../gvfs-daemons_1.36.1-0ubuntu1.1_amd64.deb ...
Unpacking gvfs-daemons (1.36.1-0ubuntu1.1) ...
Selecting previously unselected package gvfs:amd64.
Preparing to unpack .../gvfs_1.36.1-0ubuntu1.1_amd64.deb ...
Unpacking gvfs:amd64 (1.36.1-0ubuntu1.1) ...
Processing triggers for libglib2.0-0:amd64 (2.56.1-2ubuntu1) ...
Setting up gvfs-libs:amd64 (1.36.1-0ubuntu1.1) ...
Setting up gvfs-daemons (1.36.1-0ubuntu1.1) ...
Setting up gvfs:amd64 (1.36.1-0ubuntu1.1) ...

It is unclear to me why gvfs was not installed during the do-release-
upgrade. Is there a way I can file a bug against do-release-upgrade?

MTP USB mounting still does not work:

Aug 29 10:37:26 insitu kernel: [ 3013.040023] usb 1-8: new high-speed USB 
device number 10 using ehci-pci
Aug 29 10:37:26 insitu kernel: [ 3013.198520] usb 1-8: New USB device found, 
idVendor=04e8, idProduct=6860
Aug 29 10:37:26 insitu kernel: [ 3013.198524] usb 1-8: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
Aug 29 10:37:26 insitu kernel: [ 3013.198526] usb 1-8: Product: SAMSUNG_Android
Aug 29 10:37:26 insitu kernel: [ 3013.198527] usb 1-8: Manufacturer: SAMSUNG
Aug 29 10:37:26 insitu kernel: [ 3013.198529] usb 1-8: SerialNumber: 
dd8450b3050d150f
Aug 29 10:37:26 insitu upowerd[1596]: unhandled action 'bind' on 
/sys/devices/pci:00/:00:10.4/usb1/1-8
Aug 29 10:37:26 insitu dbus-daemon[1442]: [session uid=1000 pid=1442] 
Activating via systemd: service name='org.gtk.vfs.GPhoto2VolumeMonitor' 
unit='gvfs-gphoto2-volume-monitor.service' requested by ':1.166' (uid=1000 
pid=5547 comm="thunar-volman --device-added /sys/devices/pci:" 
label="unconfined")
Aug 29 10:37:26 insitu systemd[1412]: Starting Virtual filesystem service - 
digital camera monitor...
Aug 29 10:37:27 insitu upowerd[1596]: unhandled action 'bind' on 
/sys/devices/pci:00/:00:10.4/usb1/1-8/1-8:1.0
Aug 29 10:37:27 insitu upowerd[1596]: unhandled action 'unbind' on 
/sys/devices/pci:00/:00:10.4/usb1/1-8/1-8:1.0
Aug 29 10:37:27 insitu dbus-daemon[1442]: [session uid=1000 pid=1442] 
Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor'
Aug 29 10:37:27 insitu systemd[1412]: Started Virtual filesystem service - 
digital camera monitor.
Aug 29 10:37:27 insitu dbus-daemon[1442]: [session uid=1000 pid=1442] 
Activating via systemd: service name='org.gtk.vfs.MTPVolumeMonitor' 
unit='gvfs-mtp-volume-monitor.service' requested by ':1.166' (uid=1000 pid=5547 
comm="thunar-volman --device-added /sys/devices/pci:" label="unconfined")
Aug 29 10:37:27 insitu systemd[1412]: Starting Virtual filesystem service - 
Media Transfer Protocol monitor...
Aug 29 10:37:27 insitu dbus-daemon[1442]: [session uid=1000 pid=1442] 
Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'
Aug 29 10:37:27 insitu systemd[1412]: Started Virtual filesystem service - 
Media Transfer Protocol monitor.
Aug 29 10:37:27 insitu dbus-daemon[1442]: [session uid=1000 pid=1442] 
Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' 
unit='gvfs-afc-volume-monitor.service' requested by ':1.166' (uid=1000 pid=5547 
comm="thunar-volman --device-added /sys/devices/pci:" label="unconfined")
Aug 29 10:37:27 insitu systemd[1412]: Starting Virtual filesystem service - 
Apple File Conduit monitor...
Aug 29 10:37:27 insitu gvfs-afc-volume-monitor[5563]: Volume monitor alive
Aug 29 10:37:27 insitu dbus-daemon[1442]: [session uid=1000 pid=1442] 
Successfully activated service 'org.gtk.vfs.AfcVolumeMonitor'
Aug 29 10:37:27 insitu systemd[1412]: Started Virtual filesystem service - 
Apple File Conduit monitor.
Aug 29 10:37:27 insitu dbus-daemon[1442]: [session 

[Kernel-packages] [Bug 1722719] Re: HID: multitouch: Correct ALPS PTP Stick and Touchpad devices ID

[Anthony Wong]

** Changed in: hwe-next
   Status: New => 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/1722719

Title:
  HID: multitouch: Correct ALPS PTP Stick and Touchpad devices ID

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Alps touchpad with ID 0x120A + trackpoint will not be used for mass 
production machines.
  Touchpad 0x120A w/o trackpoint still reports it has a trackpoint, this will 
confuse userspace apps.

  [Fix]
  Reverts commit fcaa4a07d2a4b541e91da7a55d8b3331f96d1865, so 0x120A device is 
no longer a MT_CLS_WIN_8_DUAL device.

  [Test Case]
  Verified on the systems affected with this issue and confirmed that this 
solution works.

  [Regression Potential]
  Minimal.
  This patch is for a single device in a specific driver.

  This bug is used for tracking purposes, please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1722719/+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 1783906] Re: Linux 4.15 and onwards fails to initialize some hard drives

[Joseph Salisbury]

Thanks for the response, David!  Correct the print for the mask came
after those 2 lines of code.  Here is the snippet:

 /* unconditionally mask off the highest bit */
bit = fls(mask) - 1;
mask &= ~(1 << bit);

/* Debug added for lp1783906: */
dump_stack();
pr_info("***-> Function calling sata_down_spd_limit: %pf",  
__builtin_return_address(0));
printk(KERN_DEBUG "***-> Value of spd_limit: %u\n", spd_limit);
printk(KERN_DEBUG "***-> Value of sstatus: %u\n", sstatus);
printk(KERN_DEBUG "***-> Value of spd: %u\n", spd);
printk(KERN_DEBUG "***-> Value of mask: %u\n", mask);

/*
 * Mask off all speeds higher than or equal to the current one.  At
 * this point, if current SPD is not available and we previously
 * recorded the link speed from SStatus, the driver has already
 * masked off the highest bit so mask should already be 1 or 0.
 * Otherwise, we should not force 1.5Gbps on a link where we have
 * not previously recorded speed from SStatus.  Just return in this
 * case.
 */
if (spd > 1)
mask &= (1 << (spd - 1)) - 1;

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

Title:
  Linux 4.15 and onwards fails to initialize some hard drives

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  I have two hard drives, the main hard drive is a TOSHIBA DT01ACA200
  the second backup hard drive is a Western Digital WD5003AZEX. I
  installed lubuntu 18.04.1 on the Toshiba HDD and it boots just fine,
  the issue is with the second hard drive, when installing the WD HDD
  wouldn't even come as an option to install, and after boot the WD HDD
  still wouldn't come up, this is the dmesg with the stock kernel (4.15)
  https://paste.ubuntu.com/p/kpxh94v2SK/

  ata6 is the WD HDD that refuses to work. The messages:
  [  302.107650] ata6: SError: { CommWake 10B8B Dispar DevExch }
  [  302.107658] ata6: hard resetting link
  [  307.860291] ata6: link is slow to respond, please be patient (ready=0)
  [  312.120898] ata6: COMRESET failed (errno=-16)
  [  363.445120] INFO: task kworker/u8:5:201 blocked for more than 120 seconds.
  [  363.445131]   Not tainted 4.15.0-29-generic #31-Ubuntu
  [  363.445135] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.445140] kworker/u8:5D0   201  2 0x8000
  [  363.445155] Workqueue: events_unbound async_run_entry_fn
  [  363.445157] Call Trace:
  [  363.445171]  __schedule+0x291/0x8a0
  [  363.445177]  schedule+0x2c/0x80
  [  363.445182]  ata_port_wait_eh+0x7c/0xf0
  [  363.445186]  ? wait_woken+0x80/0x80
  [  363.445189]  ata_port_probe+0x28/0x40
  [  363.445192]  async_port_probe+0x2e/0x52
  [  363.445196]  async_run_entry_fn+0x3c/0x150
  [  363.445199]  process_one_work+0x1de/0x410
  [  363.445203]  worker_thread+0x32/0x410
  [  363.445207]  kthread+0x121/0x140
  [  363.445210]  ? process_one_work+0x410/0x410
  [  363.445214]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  363.445218]  ret_from_fork+0x22/0x40

  Repeat constantly. Also when I try to turn off the computer, the
  computer seem to freeze, the lights of the keyboard and mouse turn off
  and the computer just stay on.

  I tried Tiny Core 9.0 which has linux 4.14.10, and i didn't had this
  issue, i also installed linux 4.14 on this lubuntu 18.04 using Ukuu
  Kernel Update Utility. And with this kernel version, or any previous
  version the WD HDD does work again. Here's a dmesg of lubuntu 18.04
  with linux 4.14 and the WD HDD finally coming up at the end:
  https://paste.ubuntu.com/p/Gd3cGFbjTJ/

  Also tried with with linux 4.17 but the WD HDD would also refuse to
  work on this version. Here's another dmesg with this version:
  https://paste.ubuntu.com/p/PmNn96vZZv/

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-29-generic 4.15.0-29.31
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-29-generic.
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  testtest756 F pulseaudio
   /dev/snd/controlC1:  testtest756 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'NVidia_1'/'HDA NVidia at 0xfe02 irq 22'
 Mixer name : 'Realtek ALC1200'
 Components : 'HDA:10ec0888,10ec,00100101 
HDA:10de0002,10de0101,0010'
 Controls  : 56
 Simple ctrls  : 21
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xfcffc000 irq 16'
 Mixer name : 'Nvidia GPU 42 HDMI/DP'
 Components : 

[Kernel-packages] [Bug 1759088] Re: can't record sound via front headset port on the Dell Precision 3630

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  can't record sound via front headset port on the Dell Precision 3630

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  [Impact]
  The Dell Precision 3630 is a desktop computer, it has only one front headset
  jack on it, after we plug a headset in it, we can't record sound via the
  headset-mic.

  And Realtek told us that "This platform was the fixed type headset only for
  iphone type. Fixed type headset was not run for default headset mode rule.
  It's hardware fixed type solution. Don't need to run software headset mode.
  Hardware layout not support UAJ functions."

  And Realtek submitted this patch to fix this problem.

  [Fix]
  With this patch, the driver only set pin 0x19 as the headset-mic and will not
  call alcxxx_headset_mode init function anymore since the circuit is hardware
  fixed to be iphone-type headset-mic.

  [Test Case]
  Boot up the system, and plug a iphone-type headset, record the sound via
  headset-mic, it can record the sound and sound quality is pretty good.

  [Regression Potential]
  Very low, this patch is only specific to precision 3930 (subsystem id:
  0x10280871 and 0x10280872).

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1759088/+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 1788752] Re: linux-gcp: 4.15.0-1019.20 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => In Progress

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Incomplete

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1788744
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Wednesday, 29. August 2018 17:31 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1788744
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Wednesday, 29. August 2018 17:31 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux-gcp: 4.15.0-1019.20 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  New

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1788744
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788752/+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 1783906] Re: Linux 4.15 and onwards fails to initialize some hard drives

[Joseph Salisbury]

I'll build another test kernel with you're suggestions and ask @danieru
to test.

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

Title:
  Linux 4.15 and onwards fails to initialize some hard drives

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  I have two hard drives, the main hard drive is a TOSHIBA DT01ACA200
  the second backup hard drive is a Western Digital WD5003AZEX. I
  installed lubuntu 18.04.1 on the Toshiba HDD and it boots just fine,
  the issue is with the second hard drive, when installing the WD HDD
  wouldn't even come as an option to install, and after boot the WD HDD
  still wouldn't come up, this is the dmesg with the stock kernel (4.15)
  https://paste.ubuntu.com/p/kpxh94v2SK/

  ata6 is the WD HDD that refuses to work. The messages:
  [  302.107650] ata6: SError: { CommWake 10B8B Dispar DevExch }
  [  302.107658] ata6: hard resetting link
  [  307.860291] ata6: link is slow to respond, please be patient (ready=0)
  [  312.120898] ata6: COMRESET failed (errno=-16)
  [  363.445120] INFO: task kworker/u8:5:201 blocked for more than 120 seconds.
  [  363.445131]   Not tainted 4.15.0-29-generic #31-Ubuntu
  [  363.445135] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.445140] kworker/u8:5D0   201  2 0x8000
  [  363.445155] Workqueue: events_unbound async_run_entry_fn
  [  363.445157] Call Trace:
  [  363.445171]  __schedule+0x291/0x8a0
  [  363.445177]  schedule+0x2c/0x80
  [  363.445182]  ata_port_wait_eh+0x7c/0xf0
  [  363.445186]  ? wait_woken+0x80/0x80
  [  363.445189]  ata_port_probe+0x28/0x40
  [  363.445192]  async_port_probe+0x2e/0x52
  [  363.445196]  async_run_entry_fn+0x3c/0x150
  [  363.445199]  process_one_work+0x1de/0x410
  [  363.445203]  worker_thread+0x32/0x410
  [  363.445207]  kthread+0x121/0x140
  [  363.445210]  ? process_one_work+0x410/0x410
  [  363.445214]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  363.445218]  ret_from_fork+0x22/0x40

  Repeat constantly. Also when I try to turn off the computer, the
  computer seem to freeze, the lights of the keyboard and mouse turn off
  and the computer just stay on.

  I tried Tiny Core 9.0 which has linux 4.14.10, and i didn't had this
  issue, i also installed linux 4.14 on this lubuntu 18.04 using Ukuu
  Kernel Update Utility. And with this kernel version, or any previous
  version the WD HDD does work again. Here's a dmesg of lubuntu 18.04
  with linux 4.14 and the WD HDD finally coming up at the end:
  https://paste.ubuntu.com/p/Gd3cGFbjTJ/

  Also tried with with linux 4.17 but the WD HDD would also refuse to
  work on this version. Here's another dmesg with this version:
  https://paste.ubuntu.com/p/PmNn96vZZv/

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-29-generic 4.15.0-29.31
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-29-generic.
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  testtest756 F pulseaudio
   /dev/snd/controlC1:  testtest756 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'NVidia_1'/'HDA NVidia at 0xfe02 irq 22'
 Mixer name : 'Realtek ALC1200'
 Components : 'HDA:10ec0888,10ec,00100101 
HDA:10de0002,10de0101,0010'
 Controls  : 56
 Simple ctrls  : 21
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xfcffc000 irq 16'
 Mixer name : 'Nvidia GPU 42 HDMI/DP'
 Components : 'HDA:10de0042,38422651,00100100'
 Controls  : 21
 Simple ctrls  : 3
  CurrentDesktop: LXDE
  Date: Thu Jul 26 17:10:58 2018
  HibernationDevice: RESUME=UUID=17e70869-516d-4b63-b900-e92e3c4b73b6
  InstallationDate: Installed on 2018-07-26 (0 days ago)
  InstallationMedia: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: 113 1
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=71cf0a32-7827-49be-a2c0-cd50a72c26a1 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: 113-M2-E113
  dmi.board.vendor: EVGA
  dmi.board.version: 1
  dmi.chassis.asset.tag: Unknow
  dmi.chassis.type: 3
  dmi.chassis.vendor: 

[Kernel-packages] [Bug 1520343] Re: Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported

[Anthony Wong]

** Changed in: linux-firmware (Ubuntu)
 Assignee: Alex (leksander3) => (unassigned)

** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  ---

  STATUS 2016-03-17:

  ==
  WARNING: You need at least kernel 4.5.0 for the following new fix to work, 
else refer to the old method described in post #22
  ==

  The support for this card has now been merged to
  https://github.com/kvalo/ath10k-firmware. The repository now contains
  the required board.bin, board-2.bin and firmware-4.bin files for the
  card to initialize and connect to a bgn-access point (5GHz (ac-
  protocol) is still untested, feel free to modify this if you can
  confirm it works). Here are the new commands to get you online:

  sudo mkdir -p /lib/firmware/ath10k/QCA6174/hw3.0/

  sudo rm /lib/firmware/ath10k/QCA6174/hw3.0/* 2> /dev/null

  sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/board.bin
  https://github.com/kvalo/ath10k-
  firmware/blob/master/QCA6174/hw3.0/board.bin?raw=true

  sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/board-2.bin
  https://github.com/kvalo/ath10k-
  firmware/blob/master/QCA6174/hw3.0/board-2.bin?raw=true

  sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/firmware-4.bin
  https://github.com/kvalo/ath10k-
  
firmware/blob/master/QCA6174/hw3.0/firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1?raw=true

  Reboot or reload the ath10k_pci module and you should be able to
  connect!

  ---

  STATUS 2015-12-22:

  Currently there is a fix for this problem in post #22 (originally post
  #19, but reposted due to command typos!) which seems to have fixed the
  issue for many. This bug is unique to revision 32 of the card
  [168c:003e], fixes for older revisions don't seem to work.

  There are a couple of issues regarding the fix for some people (not
  all):

  1. Wireless works, but network throughput stops some time after
  connecting to access point

  2. Bluetooth communications take a noticeable performance hit when
  transferring something over WiFi

  ---

  Original description:

  I have recently installed Ubuntu 15.10 (64-bit) alongside Windows 10 on an 
Acer Aspire VN7-792G-76ZH and discovered, that the Qualcomm wireless card 
doesn't work in it or 16.04.
  The card has the device id 168c:003e as many other cards, for example the 
Qualcomm Atheros Killer 
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184), but it has a 
newer revision number (32) and the suggested fixes work only partially and the 
wireless is unusable.

  The computer has just been released this summer and is Intel Skylake
  -based.

  I've tried the patch from bug 1383184, which has a fix for the card revision 
20:
  Make the directory /lib/firmware/ath10k/QCA6174/hw3.0/ and put in the patch 
files:
  board.bin
  firmware-4.bin
  notice_ath10k_firmware-4.txt

  ath10k_pci succeeds in loading the firmware, but it seems that the
  firmware is not working correctly:

  dmesg | grep ath
  [5.452683] ath10k_pci :07:00.0: pci irq msi-x interrupts 8 irq_mode 0 
reset_mode 0
  [5.678420] ath10k_pci :07:00.0: Direct firmware load for 
ath10k/cal-pci-:07:00.0.bin failed with error -2
  [5.678773] ath10k_pci :07:00.0: Direct firmware load for 
ath10k/QCA6174/hw3.0/board-pci-168c:003e:11ad:0807.bin failed with error -2
  [5.678781] ath10k_pci :07:00.0: failed to load spec board file, 
falling back to generic: -2
  [5.679445] ath10k_pci :07:00.0: Direct firmware load for 
ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
  [5.679453] ath10k_pci :07:00.0: could not fetch firmware file 
'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
  [7.802316] ath10k_pci :07:00.0: qca6174 hw3.2 (0x0503, 
0x00340aff, 168c:003e:11ad:0807 fallback) fw WLAN.RM.2.0-00180-QCARMSWPZ-1 api 
4 htt 3.26 wmi 4 cal otp max_sta 32
  [7.802329] ath10k_pci :07:00.0: debug 0 debugfs 1 tracing 1 dfs 0 
testmode 0
  [8.200607] ath: EEPROM regdomain: 0x6c
  [8.200614] ath: EEPROM indicates we should expect a direct regpair map
  [8.200619] ath: Country alpha2 being used: 00
  [8.200621] ath: Regpair used: 0x6c
  [8.216605] ath10k_pci :07:00.0 wlp7s0: renamed from wlan0
  [   13.462029] ath10k_pci :07:00.0: failed to enable dynamic BW: -11
  [   16.461416] ath10k_pci :07:00.0: could not suspend target (-11)
  [   24.760062] ath10k_pci :07:00.0: failed to enable dynamic 

[Kernel-packages] [Bug 1731822] Re: system can't detect external microphone with the codec alc274

[Anthony Wong]

** Changed in: hwe-next
   Status: Fix Committed => Fix Released

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

Title:
  system can't detect external microphone with the codec alc274

Status in HWE Next:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  After installing the latest artful kernel (Ubuntu-4.13.0-16.19), and
  boot up the system with this kernel, we plug a headset to the headset
  jack, then open the gnome-sound-setting, but we can not see the
  headset microphone in it, there is only one internal microphone in it,
  as a result we can't record the sound with the headset microphone.

  This Dell machine has audio codec alc274, it needs to apply a fixup
  like ALC269_FIXUP_DELL1_MIC_NO_PRESENCE.

  After applying this fixup in the kernel driver, the headset mic can be
  detected and works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1731822/+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 1732206] Re: nvidia-graphics-drivers deferred DKMS feature does not work in xenial

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  nvidia-graphics-drivers deferred DKMS feature does not work in xenial

Status in HWE Next:
  Fix Released
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-384 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-384 source package in Zesty:
  Fix Released
Status in nvidia-graphics-drivers-384 source package in Artful:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Deferred module build was a feature that worked with Upstart and that was 
never updated to work with systemd.

  [Test Case]

  1) Enter the following command to create the temporary file:
  sudo touch /tmp/do_not_build_dkms_module

  2) Enable the -proposed repository, and install the new "nvidia-384"

  3) Check that DKMS didn't build the module (the "dkms status" will
  give you a clue).

  3) Restart your computer and see if the module is built correctly (you
  should be able to access the desktop session). Check that the module
  is there with the "dkms status" command.

  [Regression Potential]
  Low, as, currently, the feature doesn't work at all with systemd.

  _
  The nvidia-graphics-drivers 
(https://github.com/tseliot/nvidia-graphics-drivers/tree/375-xenial) deferred 
DKMS feature does not work in xenial.

  With upstart, doing a touch of the /tmp/do_not_build_dkms_module file
  indicates to defer building the kernel modules, then install the
  nvidia driver packages, which creates an upstart script to build the
  modules later. Upon reboot the upstart script would then do the DKMS
  build.

  This no longer works in xenial. The code was never updated for the
  transition from upstart to systemd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1732206/+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 1728523] Re: QCA6174A XR cannot find any WiFi AP

[Anthony Wong]

** Changed in: hwe-next
   Status: Fix Committed => Fix Released

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

Title:
  QCA6174A XR cannot find any WiFi AP

Status in HWE Next:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Released

Bug description:
  SRU Justification
  [Impact]
  Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e]
  Atheros QCA6174 can't find any WiFi APs and got below message in dmesg

  [   16.158772] ath10k_pci :02:00.0: failed to enable dynamic BW: -11
  [   22.162575] ath10k_pci :02:00.0: could not suspend target (-11)
  [   27.533002] ath10k_pci :02:00.0: failed to enable dynamic BW: -11
  [   33.535958] ath10k_pci :02:00.0: could not suspend target (-11)
  [   38.890790] ath10k_pci :02:00.0: failed to enable dynamic BW: -11
  [   44.893968] ath10k_pci :02:00.0: could not suspend target (-11)
  [   46.358194] i2c_designware i2c_designware.0: controller timed out
  [   47.358231] i2c_designware i2c_designware.0: controller timed out
  [   48.358506] i2c_designware i2c_designware.0: controller timed out
  [   49.566240] i2c_designware i2c_designware.2: controller timed out
  [   50.566862] i2c_designware i2c_designware.2: controller timed out
  [   51.566307] i2c_designware i2c_designware.2: controller timed out
  [   52.670330] i2c_designware i2c_designware.3: controller timed out
  [   53.670775] i2c_designware i2c_designware.3: controller timed out
  [   54.670427] i2c_designware i2c_designware.3: controller timed out
  [   60.326619] ath10k_pci :02:00.0: failed to enable dynamic BW: -11
  [   66.327117] ath10k_pci :02:00.0: could not suspend target (-11)
  [   71.678943] ath10k_pci :02:00.0: failed to enable dynamic BW: -11
  [   77.679084] ath10k_pci :02:00.0: could not suspend target (-11)

  It requires updated firmwares to enable it.

  [Test Case]
  After applying the required firmwares, it can search APs and connect to the 
network.

  [Regression Potential]
  Although the new firmware overwrite the old one, considering it exists in 
linux-firmware git tree and didn't get any update for 3 month, it should be 
good with no regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1728523/+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 1766398] Re: set PINCFG_HEADSET_MIC to parse_flags for Dell precision 3630

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  set PINCFG_HEADSET_MIC to parse_flags for Dell precision 3630

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-oem source package in Artful:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  On this Dell machine (codename: turtle bay), the microphone always shows up
  in the sound-setting even there is no microphone plugged in.

  [Fix]

  Without this fix, the pin will be regarded as microphone, and the jack name
  is "Mic Phantom", it is always on in the pulseaudio even nothing is plugged
  into the jack. So the UI is confusing to users since the microphone always
  shows up in the UI even there is no microphone plugged.

  After adding this flag, the jack name is "Headset Mic Phantom", then
  the pulseaudio can handle its detection correctly.

  
  [Test Case]
  After booting up the system, and without plugging anything in the audio combo
  jack, there is nothing in the input tab of sound-setting, then plug a headset
  in the jack, the what-did-you-plug-in dialogue pops up, users can select 
headset
  mic from UI, and headset-mic shows up in the sound-setting, we can record 
sound
  via headset-mic

  
  [Regression Potential]
  Very low, since this patch is specific for ALC255_FIXUP_DELL_HEADSET_MIC 
which is
  only used by Dell precision 3630 by now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1766398/+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 1744058] Re: [Artful] Realtek ALC225: 2 secs noise when a headset plugged in

[Anthony Wong]

** Changed in: hwe-next
   Status: New => 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/1744058

Title:
  [Artful] Realtek ALC225: 2 secs noise when a headset plugged in

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  There is a noise last for about 2 secs when a headset is plugged in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1744058/+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 1764684] Re: Fix an issue that some PCI devices get incorrectly suspended

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  Fix an issue that some PCI devices get incorrectly suspended

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-oem source package in Artful:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  Some PCI device are not power managed by system firmware get runtime 
suspended incorrectly. In this case it's an xHC device, which can't be woken up 
by plugging USB device.

  [Test]
  With the patch, the xHC no longer get put to suspend incorrectly. USB devices 
can work on the xHC now.

  [Fix]
  We need to check if the device is power managed by system firmware, also if 
it supports PME from D3hot.

  [Regression Potential]
  Low.
  It fixes a regression caused by the PM core refactor.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1764684/+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 1766197] Re: Update btusb reset-resume quirk to decrease power usage

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  Update btusb reset-resume quirk to decrease power usage

Status in HWE Next:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  USB reset-resume quirk prevents the device from runtime suspending,
  which increases power usage.

  [Test]
  With the patch, the power consumption decreases 0.5W.
  The tested machine doesn't need the quirk to make btusb work.

  [Fix]
  Update the btusb reset-resume quirk with a DMI based version, which can
  be more specific.

  [Regression Potential]
  Low.
  Everthing is in mainline, and I haven't seen any new report about this
  issue for some time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1766197/+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 1757584] Re: Let headset-mode initialization be called on Dell Precision 3930

[Anthony Wong]

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

** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  Let headset-mode initialization be called on Dell Precision 3930

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  == SRU Justification ==
  [Impact]
  There is only one audio jack on this machine (codename: zuma-p), so
  there is only one output device (headphone), then the driver will not generate
  auto-mute control on this machine, without auto-mute, the headset-mode
  initialization routine will not be called, as a result, all audio devices
  can't work (output and input). To fix it, add a dummy lineout on this
  machine, then there are two output devices (headphone + lineout), the
  driver will create auto-mute control on this machine finally.

  Due to the patch conflicts, I prepared two patches, one is for artful+oem,
  the other is for bionic.

  [Test Case]
  plug the headset and play or record the sound on this machine, both playing
  and recording work well.

  [Fix]
  one commit from mainline kernel.

  [Regression Potential]
  very low, since this patch only applies to the specific Dell machine 
Precision 3930.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1757584/+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 1759511] Re: Fix an issue that when system in S3, USB keyboard can't wake up the system.

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

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

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

Title:
  Fix an issue that when system in S3, USB keyboard can't wake up the
  system.

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  ===SRU Justification===
  [Impact]
  xHC stays at D0 when system is in S3. Unfortunately D0 can't generate PME# 
wakeup event, so USB device can't wake the system.

  [Test]
  Intel NUC can't be waken up by USB keyboard when the system is in S3.
  With the patch, USB keyboard can wake up the system.

  [Regression Potential]
  Low.
  The issue starts appearing from Gemini Lake, older generation hardware 
shouldn't get affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1759511/+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 1756700] Re: Ryzen/Raven Ridge USB ports do not work

[Anthony Wong]

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

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

Title:
  Ryzen/Raven Ridge USB ports do not work

Status in HWE Next:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Triaged
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  USB controller stops working once a USB device gets plugged.

  [Fix]
  Add a delay for xHC can workaround the issue.

  [Test]
  Plug a USB device to affected system. USB controller stop working
  afterward.
  With the patch, the issue is solved.

  [Regression Potential] 
  Low. Trivial patch which adds a delay. No functional change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1756700/+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 1763271] Re: [8086:3e92] display becomes blank after S3

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  [8086:3e92] display becomes blank after S3

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-oem source package in Artful:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  The display becomes black after S3 with the following error messages.

  dmesg:
  [ 60.546305] [drm:intel_dp_start_link_train [i915]] Link Training failed at 
link rate = 54, lane count = 4

  Xorg.0.log:
  [ 60.748] (EE) modeset(0): failed to set mode: Invalid argument
  [ 60.748] (WW) modeset(0): hotplug event: connector 48's link-state is BAD, 
tried resetting the current mode. You may be left with a black screen if this 
fails...

  [Fix]
  Looks like link training fallback fails sometimes with eDP, we need this 
commit to fix the issue.

  commit a306343bcd7df89d9d45a601929e26866e7b7a81 (refs/bisect/bad)
  Author: Manasi Navare 
  Date: Thu Oct 12 12:13:38 2017 -0700

  drm/i915/edp: Do not do link training fallback or prune modes on
  EDP

  [Regression Potential]
  Should be low.
  To avoid conflicts, we introduce 4 commits, I'll try explaining them below

  a306343 drm/i915/edp: Do not do link training fallback or prune modes on EDP
     This is the fix commit and the behavior only changes when DP is eDP, it 
does nothing if DP is eDP. Should be fine to not do link training fallback and 
not emit Hotplug Uevent to userspace to start modeset, since its eDP, the 
display is fixed.

  1853a9d drm/i915/dp: make is_edp non-static and rename to intel_dp_is_edp
  7b91bf7 drm/i915/dp: rename intel_dp_is_edp to intel_dp_is_port_edp
     Above 2 commits do function name renaming only.

  dc911f5 drm/i915/edp: Allow alternate fixed mode for eDP if available.
     Change the prototype of function "intel_panel_init()" and adding one extra 
argument, should have small impact on the display.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1763271/+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 1758829] Re: speaker can't output sound anymore after system resumes from S3 on a lenovo machine with alc257

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  speaker can't output sound anymore after system resumes from S3 on a
  lenovo machine with alc257

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  [Impact]
  After booting up, the speaker works well. If we suspend the machine then 
resume
  it back, the speaker can't output sound, even rebooting can't make the speaker
  work, we need to power off the machine then power up the machine, the speaker
  can work again.

  [Fix]
  We need to add the basic support for the codec alc257 first (0001-xxx.patch),
  then add hooking function for this codec and clear the bit of 15 for register
  0x57 (0002-xxx.patch). Both of these two patches come from mainline kernel.

  [Test Case]
  After booting up the system, suspend the machine, then resume the machine,
  test the speaker, the speaker can output sound. Repeat the testing steps many
  times, the speaker still can work.

  [Regression Potential]
  Very low, since the 1st patch just add the support for a new codec alc257, it
  will not affect other codecs. The 2nd patch just apply a fix for alc257, it
  doesn't affect other codecs too. And both of them come from mainline and
  realtek.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1758829/+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 1738523] Re: [SRU] External HDMI monitor failed to show screen on Lenovo X1 series

[Anthony Wong]

** Changed in: hwe-next
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] External HDMI monitor failed to show screen on Lenovo X1 series

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  Thinkpad X1 yoga:
  CPU: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (family: 0x6, model: 0x8e, 
stepping: 0xa)
  GPU: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])

  Steps:
  1, Connect an external monitor
  2, Try to switch display modes in mirrored, extended, displayed on external 
or internal.

  [Impact]
  External HDMI monitor failed to show screen on Lenovo X1 yoga/carbon

  [Fix]
  Add a workaround to bypass this TMDS_OE writing on identified laptop models.

  [Test Case]
  Tested on ThinkPad X1 yoga 2nd/3rd and Carbon 6th, external HDMI output
  OK.

  [Regression Potential]
  Low, it limits to ThinkPad specific laptops.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1738523/+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