[Kernel-packages] [Bug 1809219] Re: Killer 802.11ac 2x2 (1550 or 1550i) [8086:2526][1a56:1550] is not supported

2019-01-02 Thread AceLan Kao
** Tags added: originate-from-1809194 somerville

** Description changed:

  [Impact]
  Killer Wireless-1550 is not supported by Bionic kernel.
  
  [Fix]
  This card can be supported by adding its structs and IDs into table by below 
commit.
  0a5257bc6d89 iwlwifi: add more card IDs for 9000 series
  
  [Test]
+ Verified wifi works after applied the commit.
  
  [Regression Potential]
  Low. It adds its own structs and IDs to support killer cards.

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

Title:
  Killer 802.11ac 2x2 (1550 or 1550i) [8086:2526][1a56:1550] is not
  supported

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

Bug description:
  [Impact]
  Killer Wireless-1550 is not supported by Bionic kernel.

  [Fix]
  This card can be supported by adding its structs and IDs into table by below 
commit.
  0a5257bc6d89 iwlwifi: add more card IDs for 9000 series

  [Test]
  Verified wifi works after applied the commit.

  [Regression Potential]
  Low. It adds its own structs and IDs to support killer cards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1809219/+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 1810370] Re: linux-oem: 4.15.0-1031.36 -proposed tracker

2019-01-02 Thread Brad Figg
** 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 --
  kernel-stable-master-bug: 1810369
+ phase: Packaging
+ phase-changed: Thursday, 03. January 2019 07:30 UTC
  reason:
-   prepare-package: Stalled -- waiting for master bug
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
+   prepare-package-signed: Pending -- package not yet uploaded

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

Title:
  linux-oem: 4.15.0-1031.36 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  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 upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oem package in Ubuntu:
  Invalid

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: 1810369
  phase: Packaging
  phase-changed: Thursday, 03. January 2019 07:30 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1810370/+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 1810130] Re: ic2-HTIX5288

2019-01-02 Thread Kai-Heng Feng
Please attach dmesg under v4.20.

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

Title:
  ic2-HTIX5288

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  touchpad not working

  Ubuntu Disco Dingo (development branch)

  WINBOOK 13

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  docmint2172 F pulseaudio
   /dev/snd/controlC1:  docmint2172 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 31 00:55:26 2018
  InstallationDate: Installed on 2018-12-30 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181230)
  MachineType: AXDIA International GmbH WINBOOK 13
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=ea66942b-3d65-4c18-a99e-d02e31358a42 ro recovery nomodeset 
i8042.nomux=1 i8042.reset
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2017
  dmi.bios.vendor: WINBOOK 13
  dmi.bios.version: 1.6
  dmi.board.asset.tag: Default string
  dmi.board.name: K132
  dmi.board.vendor: AXDIA International GmbH
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnWINBOOK13:bvr1.6:bd11/27/2017:svnAXDIAInternationalGmbH:pnWINBOOK13:pvrDefaultstring:rvnAXDIAInternationalGmbH:rnK132:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Notebook
  dmi.product.name: WINBOOK 13
  dmi.product.sku: WINBOOK13-K132-02
  dmi.product.version: Default string
  dmi.sys.vendor: AXDIA International GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810130/+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 1809868] Re: 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5 in btrfs_kernel_fixes failed on T

2019-01-02 Thread Po-Hsu Lin
** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: ubuntu-kernel-tests
   Status: New => 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/1809868

Title:
  29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5 in btrfs_kernel_fixes failed
  on T

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  Test failed with "ERROR: rmdir o259-6-0 failed. No such file or
  directory" on Trusty.

  
  Invoking test 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5

  fix 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5

  Btrfs: send, don't send rmdir for same target multiple times

  When doing an incremental send, if we delete a directory that has N > 1
  hardlinks for the same file and that file has the highest inode number
  inside the directory contents, an incremental send would send N times an
  rmdir operation against the directory. This made the btrfs receive command
  fail on the second rmdir instruction, as the target directory didn't exist
  anymore.

  Performing full device TRIM (1.00GiB) ...
  Turning ON incompat feature 'extref': increased hardlink limit per file to 
65536

  WARNING! - Btrfs v3.12 IS EXPERIMENTAL
  WARNING! - see http://btrfs.wiki.kernel.org before using

  fs created label (null) on /dev/loop0
nodesize 16384 leafsize 16384 sectorsize 4096 size 1.00GiB
  Btrfs v3.12
  Create a readonly snapshot of 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5' in 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap1'
  At subvol /tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap1
  Create a readonly snapshot of 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5' in 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap2'
  At subvol /tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap2
  Performing full device TRIM (1.00GiB) ...
  Turning ON incompat feature 'extref': increased hardlink limit per file to 
65536

  WARNING! - Btrfs v3.12 IS EXPERIMENTAL
  WARNING! - see http://btrfs.wiki.kernel.org before using

  fs created label (null) on /dev/loop0
nodesize 16384 leafsize 16384 sectorsize 4096 size 1.00GiB
  Btrfs v3.12
  At subvol snap1
  At snapshot snap2
  ERROR: rmdir o259-6-0 failed. No such file or directory
  incremental receive failed

  It seems that commit 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5 does not
  exist in Trusty tree.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-164-generic 3.13.0-164.214
  ProcVersionSignature: User Name 3.13.0-164.214-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-164-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 27 03:14 seq
   crw-rw 1 root audio 116, 33 Dec 27 03:14 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   [13958.095408] btrfs: device fsid da34075a-4eaa-4e50-aeea-02206e8c8e44 devid 
1 transid 4 /dev/loop0
   [13958.102670] btrfs: device fsid da34075a-4eaa-4e50-aeea-02206e8c8e44 devid 
1 transid 4 /dev/loop0
   [13958.105901] btrfs: device fsid da34075a-4eaa-4e50-aeea-02206e8c8e44 devid 
1 transid 4 /dev/loop0
   [13958.106099] btrfs: disk space caching is enabled
   [13958.107771] btrfs: creating UUID tree
  Date: Thu Dec 27 07:11:58 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-164-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-164-generic N/A
   linux-backports-modules-3.13.0-164-generic  N/A
   linux-firmware  1.127.24
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i44

[Kernel-packages] [Bug 1685937] Re: HID 1018:1006 Touchpad does not work

2019-01-02 Thread Kai-Heng Feng
Sorry for the belated response.

Please send the patch upstream and we can include the patch to Ubuntu's
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/1685937

Title:
  HID 1018:1006 Touchpad does not work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touchpad does not work. hid_multitouch interprets gestures as weird stuff 
-> opens search, types letters. If I didnt overlook anything the touchpad 
position does not show in any of the /dev/input files.. Any help would be 
appreciated.
  edit:  its on a trekstor surfbook w2.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21 [modified: 
boot/vmlinuz-4.10.0-19-generic]
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity:Unity7
  Date: Mon Apr 24 23:05:18 2017
  MachineType: TrekStor SurfBook W2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=78342794-9ef5-4a63-9b1e-040a63fd644b ro i8042.nopnp quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/22/2016
  dmi.bios.version: SB14464-2_BIOS_V2.1.1
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: CherryTrail CR
  dmi.board.vendor: TS_I-Net
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvn:bvrSB14464-2_BIOS_V2.1.1:bd11/22/2016:svnTrekStor:pnSurfBookW2:pvrType1-TBDbyOEM:rvnTS_I-Net:rnCherryTrailCR:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: SurfBook W2
  dmi.product.version: Type1 - TBD by OEM
  dmi.sys.vendor: TrekStor

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

2019-01-02 Thread Kai-Heng Feng
L1TF was introduced between these two versions.

Do you still see the issue with up-to-date Ubuntu kernel and up-to-date
BIOS?

-- 
You 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 1781016] Re: Slow flood of do_IRQ: No irq for vector

2019-01-02 Thread Kai-Heng Feng
A,

The default kernel doesn't enable IRQ debugfs so there's no
"/sys/kernel/debug/irq".

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

Title:
  Slow flood of do_IRQ: No irq for vector

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Every few seconds I get something like this in my dmesg:

  [44984.933221] do_IRQ: 1.34 No irq handler for vector
  [44986.933976] do_IRQ: 1.34 No irq handler for vector
  [44991.935614] do_IRQ: 1.34 No irq handler for vector
  [45004.938590] do_IRQ: 1.34 No irq handler for vector
  [45005.939002] do_IRQ: 4.34 No irq handler for vector
  [45034.949161] do_IRQ: 4.34 No irq handler for vector
  [45051.954569] do_IRQ: 4.34 No irq handler for vector
  [45058.956019] do_IRQ: 4.34 No irq handler for vector
  [45062.957727] do_IRQ: 4.34 No irq handler for vector
  [45063.958204] do_IRQ: 4.34 No irq handler for vector
  [45073.961103] do_IRQ: 4.34 No irq handler for vector

  The numbers vary. Some examples are 4.34, 4.36, 1.34, 0.33, 6.34,
  7.33, 5.37. Eventually dmesg's ring buffer is full and my entire log
  is just messages like above with varying #.## numbers.

  I researched it and tried disabling irqbalance. It had no effect, the
  messages continued.

  The system is a Ryzen 2700X with B350 chipset on Asus Prime B350-PLUS.
  I have 64GB of Kingston DDR4-2400 ECC memory and Samsung 960 PRO M.2
  NVMe SSD, and an Intel I350-T4 quad port gigabit NIC. This issue never
  occurred before installing 18.03 on the same hardware. No overclocking
  whatsoever has ever been done to this machine.

  Also, I had to disable selective suspend on USB in this version to
  prevent major USB issues, which was not required in 17.10, that might
  be related.

  My system seems stable, but spurious IRQs can't be good. I'd like to
  resolve this if possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-26-generic 4.15.0-26.28
  ProcVersionSignature: Ubuntu 4.15.0-26.28-generic 4.15.18
  Uname: Linux 4.15.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2145 F pulseaudio
doug   3736 F pulseaudio
   /dev/snd/controlC1:  gdm2145 F pulseaudio
doug   3736 F pulseaudio
  Date: Tue Jul 10 12:49:00 2018
  HibernationDevice:
   
  InstallationDate: Installed on 2017-06-26 (379 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-26-generic 
root=UUID=53446747-0814-48f7-b7c4-7fd7d7234d83 ro video=vesa:off vga=normal 
video=efifb:off usbcore.autosuspend=-1 usbhid.quirks=0x1e71:0x170e:0x4
  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-26-generic N/A
   linux-backports-modules-4.15.0-26-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4011
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B350-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4011:bd04/19/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  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/1781016/+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 1789589] Re: USB-SATA resets when UAS is used

2019-01-02 Thread Kai-Heng Feng
Have you tried other quirks?

FWIW it's "usb-storage.quirks=" instead of "usbstoragequirks=".

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

Title:
  USB-SATA resets when UAS is used

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dear developers,
  I have a Icybox 4 HDD enclosure with a JMicrom JMS567 SATA to USB converter. 
When the device is under load and more than 1 hardrive is acessed, the USB 
enclosure frequently restarts. This leaves often a corrup filesystem. I tried 
to switch off UAS by creating a file in /etc/modprobe.d/blacklist_uas.conf with 
the following content:
  options usb-storage quirks=152d:0567:u
  This disables UAS, and I did not exerinecs restarts of the box. But of course 
thios laves only USB speeds on the USB3 connector, which is quite slow.
  I think this suggest this is a kernel bug and not a hardware issues.
  I aasume the problem is in the linux-image-4.15.0-33-generic package.
  Similar has been reported:
  https://www.spinics.net/lists/linux-usb/msg157550.html  
  Any help would be greatly appreciated.
  Best regards
  Michael

  lsusb -vvv -s 003:004

  Bus 003 Device 004: ID 152d:0567 JMicron Technology Corp. / JMicron USA 
Technology Corp. JMS567 SATA 6Gb/s bridge
  Couldn't open device, some information will be missing
  Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB   3.00
bDeviceClass0 (Defined at Interface level)
bDeviceSubClass 0 
bDeviceProtocol 0 
bMaxPacketSize0 9
idVendor   0x152d JMicron Technology Corp. / JMicron USA Technology 
Corp.
idProduct  0x0567 JMS567 SATA 6Gb/s bridge
bcdDevice2.05
iManufacturer  10 
iProduct   11 
iSerial 5 
bNumConfigurations  1
Configuration Descriptor:
  bLength 9
  bDescriptorType 2
  wTotalLength   44
  bNumInterfaces  1
  bConfigurationValue 1
  iConfiguration  0 
  bmAttributes 0xc0
Self Powered
  MaxPower2mA
  Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber0
bAlternateSetting   0
bNumEndpoints   2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass  6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface  0 
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x81  EP 1 IN
  bmAttributes2
Transfer TypeBulk
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0400  1x 1024 bytes
  bInterval   0
  bMaxBurst  15
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x02  EP 2 OUT
  bmAttributes2
Transfer TypeBulk
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0400  1x 1024 bytes
  bInterval   0
  bMaxBurst  15
  res3stockm@brix:~$ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  res3stockm  11358 F pulseaudio
   /dev/snd/controlC0:  res3stockm  11358 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=3e40bf65-88c1-45fc-a2f5-7bc5e4bd2fff
  MachineType: GIGABYTE MMLP3AP-00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=daee2663-9ad7-4cac-b5b5-5176a8d4e589 ro quiet usbcore.autosuspend=-1 
usbstoragequirks=0x152d:0x0567:f
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (139 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MMLP3AP-00
  dmi.board.vendor: GIGABYTE
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10

[Kernel-packages] [Bug 1810370] Re: linux-oem: 4.15.0-1031.36 -proposed tracker

2019-01-02 Thread AceLan Kao
** Summary changed:

- linux-oem:  -proposed tracker
+ linux-oem: 4.15.0-1031.36 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => AceLan Kao 
(acelankao)

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => AceLan Kao 
(acelankao)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => AceLan Kao 
(acelankao)

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

Title:
  linux-oem: 4.15.0-1031.36 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  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 upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oem package in Ubuntu:
  Invalid

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: 1810369
  reason:
prepare-package: Stalled -- waiting for master bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1810370/+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 1087010] Re: kworker uses 70-90% of a CPU core (hyperthreaded)

2019-01-02 Thread Kai-Heng Feng
Sorry for the belated response.

In this case, I think kernel parameter "acpi_mask_gpe=0x13" to disable
it is the only workaround.

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

Title:
  kworker uses 70-90% of a CPU core (hyperthreaded)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I see high (70-90%) cpu usage from a kworker thread. Usually
  kworker/0:1 or kworker/0:2. This does not always happen. On some boots
  all is fine but once it shows, rebooting does not make it go away.

  WORKAROUND: Execute:
  echo "disable" > /sys/firmware/acpi/interrupts/gpe13 

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: linux-image-3.5.0-19-generic 3.5.0-19.30
  ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
  Uname: Linux 3.5.0-19-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mio1965 F pulseaudio
   /dev/snd/pcmC0D0p:   mio1965 F...m pulseaudio
  Date: Wed Dec  5 22:37:00 2012
  HibernationDevice: RESUME=UUID=a371882c-0fe7-45e5-9adb-83da8374bc11
  InstallationDate: Installed on 2012-10-10 (55 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 700Z7C
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-19-generic 
root=UUID=79674508-93de-43e0-b313-f6a9b480c606 ro 
crashkernel=384M-2G:64M,2G-:128M acpi_osi=Linux pcie_aspm=force i915.modeset=1 
i915.i915_enable_rc6=1 i915.lvds_downclock=1 i915.semaphores=1 i915.powersave=1 
snd_hda_intel.power_save_controller=1 snd_hda_intel.power_save=1 quiet splash 
vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory 
/home/mio not ours.
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-19-generic N/A
   linux-backports-modules-3.5.0-19-generic  N/A
   linux-firmware1.95
  SourcePackage: linux
  UpgradeStatus: Upgraded to quantal on 2012-10-11 (55 days ago)
  dmi.bios.date: 08/02/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P04AAE
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP04AAE:bd08/02/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn700Z7C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 700Z7C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  ---
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mio1568 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=3f9af81f-77f0-4438-9a4b-6722de269cbb
  InstallationDate: Installed on 2018-05-09 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 700Z7C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=7c436149-ab84-40d0-919f-032364393f9b ro quiet splash video=VGA1:d 
nouveau.runpm=0 vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/02/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P04AAE
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP04AAE:bd08/02/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn700Z7C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 700Z7C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG

[Kernel-packages] [Bug 1801102] Re: Please include this patch in bionic kernel https://www.spinics.net/lists/linux-wireless/msg169994.html

2019-01-02 Thread Kai-Heng Feng
** Description changed:

+ ===SRU Justification===
+ [Impact]
+ iwlwifi spews "Too many chunks: 20" in dmesg.
+ 
+ [Fix] 
+ From the patch description:
+ "
+ When we free the TFD, we check its number of valid pointers
+ and make sure it doesn't exceed the number of pointers the
+ hardware support.
+ This check had an off by one bug: it is perfectly valid to
+ free the 20 pointers if the TFD has 20 pointers.
+ "
+ 
+ [Test]
+ User confirms the patch solves the problem.
+ 
+ [Regression Potential]
+ Low. The fix is limited to iwlwifi, and the patch is in mainline for a
+ while.
+ 
+ ===Original Bug Report===
  Hi:
  
  I am having the same issue i.e. when downloading torrent with KTorrent.
  Please include this fix https://www.spinics.net/lists/linux-
  wireless/msg169994.html in the release kernel.
  
  Thanks

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

Title:
  Please include this patch in bionic kernel
  https://www.spinics.net/lists/linux-wireless/msg169994.html

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

Bug description:
  ===SRU Justification===
  [Impact]
  iwlwifi spews "Too many chunks: 20" in dmesg.

  [Fix] 
  From the patch description:
  "
  When we free the TFD, we check its number of valid pointers
  and make sure it doesn't exceed the number of pointers the
  hardware support.
  This check had an off by one bug: it is perfectly valid to
  free the 20 pointers if the TFD has 20 pointers.
  "

  [Test]
  User confirms the patch solves the problem.

  [Regression Potential]
  Low. The fix is limited to iwlwifi, and the patch is in mainline for a
  while.

  ===Original Bug Report===
  Hi:

  I am having the same issue i.e. when downloading torrent with
  KTorrent. Please include this fix https://www.spinics.net/lists/linux-
  wireless/msg169994.html in the release kernel.

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801102/+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 1805079] Re: click/pop noise in the headphone on several lenovo laptops

2019-01-02 Thread Hui Wang
@Vadim,

Since James pointed out a solution, let us test if this workaround can
fix the noise of headphone on your machine?

After you heard the noise from headphone, run "sudo hda-verb
/dev/snd/hwC0D0 0x1d SET_PIN_WIDGET_CONTROL 0x0" in the terminal. Then
can you still hear the noise?

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

Title:
  click/pop noise in the headphone on several lenovo laptops

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  [Impact]
  Lenovo told us that some linux uers reported headphone noise on Lenovo's
  website. After investigating, we found those Lenovo laptop mdoels all
  have the codec of alc285, and we can reproduce the noise problem too.

  [Fix]
  Don't use the DAC of headphone, let headphone share the DAC with speaker,
  the noise disappears.

  [Test Case]
  After applying this patch, we tested on Lenovo P52, P72, X1 carbon and X1
  Yoda2, no noise anymore

  [Regression Potential]
  Low. This patch only apply to several lenovo machines, and after applying
  this patch, both speaker and headphone still work very well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805079/+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 1805079] Re: click/pop noise in the headphone on several lenovo laptops

2019-01-02 Thread Hui Wang
@James, thanks for your comment, the kernel of 18.04.1 doesn't include
my patches yet, you can have a try https://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.20/, to see if you still can experience popping from
L-Channel and if you can hear noise from headphone (#12).

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

Title:
  click/pop noise in the headphone on several lenovo laptops

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  [Impact]
  Lenovo told us that some linux uers reported headphone noise on Lenovo's
  website. After investigating, we found those Lenovo laptop mdoels all
  have the codec of alc285, and we can reproduce the noise problem too.

  [Fix]
  Don't use the DAC of headphone, let headphone share the DAC with speaker,
  the noise disappears.

  [Test Case]
  After applying this patch, we tested on Lenovo P52, P72, X1 carbon and X1
  Yoda2, no noise anymore

  [Regression Potential]
  Low. This patch only apply to several lenovo machines, and after applying
  this patch, both speaker and headphone still work very well.

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

2019-01-02 Thread Brad Figg
** 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
  
  backports: 
  derivatives: bug 1810370 (linux-oem)
+ -- swm properties --
+ phase: Packaging
+ phase-changed: Thursday, 03. January 2019 06:30 UTC
+ reason:
+   prepare-package: Pending -- version not specified

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid

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: 
  derivatives: bug 1810370 (linux-oem)
  -- swm properties --
  phase: Packaging
  phase-changed: Thursday, 03. January 2019 06:30 UTC
  reason:
prepare-package: Pending -- version not specified

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

2019-01-02 Thread Brad Figg
** 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 --
  kernel-stable-master-bug: 1810369
+ reason:
+   prepare-package: Stalled -- waiting for master bug

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

Title:
  linux-oem:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-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 upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oem package in Ubuntu:
  Invalid

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: 1810369
  reason:
prepare-package: Stalled -- waiting for master bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1810370/+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 1810370] [NEW] linux-oem: -proposed tracker

2019-01-02 Thread Khaled El Mously
Public bug reported:

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: 1810369

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-oem (Ubuntu)
 Importance: Undecided
 Status: Invalid


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2018.12.03 kernel-sru-derivative-of-1810369

** Tags added: kernel-release-tracking-bug

** Tags added: kernel-release-tracking-bug-live

** Tags added: bionic

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Ch

[Kernel-packages] [Bug 1810369] [NEW] linux: -proposed tracker

2019-01-02 Thread Khaled El Mously
Public bug reported:

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: 
derivatives: bug 1810370 (linux-oem)

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-beta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-candidate
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-edge
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-stable
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2018.12.03 kernel-sru-master-kernel

** Tags added: kernel-release-tracking-bug

** Tags added: kernel-release-tracking-bug-live

** Tags added: bionic

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-beta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-candidate
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-edge
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-stable
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-te

[Kernel-packages] [Bug 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370

2019-01-02 Thread Kai-Heng Feng
Please enable btusb autosuspend during test.

This is what happened:
[25781.865975] PM: suspend entry (deep)
System is about to suspend to deep (S3),

[25782.016682] pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16
[25782.016691] dpm_run_callback(): pci_pm_suspend+0x0/0x130 returns -16
[25782.016694] PM: Device :00:14.0 failed to suspend async: error -16
[25782.920799] PM: Some devices failed to suspend, or early wake event detected
But the xHC (USB controller) wakes up early, so the system aborted S3,

[25782.922906] usb usb1-port7: status 0103 change 0004
The one wakes xHC up is btusb, which is woken up by BLE events,

[25783.167977] PM: suspend exit
[25783.168050] PM: suspend entry (s2idle)
System tries to suspend again, via s2idle. This happens more than once.

[25842.804908] PM: suspend entry (deep)
[25842.804912] PM: Syncing filesystems ... done.
[25842.834864] Freezing user space processes ... (elapsed 0.002 seconds) done.
[25842.837207] OOM killer disabled.
[25842.837208] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
[25842.838619] Suspending console(s) (use no_console_suspend to debug)

Finally it suspends successfully, but both btusb and ath10k_pci devices fail to 
work:
[25843.579504] ath10k_pci :02:00.0: Refused to change power state, 
currently in D3
[25844.303534] usb 1-7: device descriptor read/64, error -71

Most devices' .resume() and .suspend() callbacks rely on full system
suspend/resume works successfully. This assumption breaks when the first
system suspend fails, which is cause by the BLE event.

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

Title:
  Missing wifi and bluetooth after sleep on XPS 9370

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  I have XPS9370 with self-installed Ubuntu 18.10 (not project sputnik) with 
Killer 1435 wireless module.
  And sometimes I find wifi and bluetooth missing after sleep. I cannot exactly 
define preconditions, but it seems there are following steps to reproduce the 
issue
  1. Connect something via bluetooth  (I use bluetooth headset)
  2. Send laptop to sleep
  3. Wake it and find wifi and bluetooth missing.

  I have to mention that I have also been experienced bluetooth only
  missing, but it somehow transformed to the issue with both wireless
  devices.

  Dmesg after waking up with the issue attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kao2362 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-09-22 (33 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 012: ID 0489:e0a2 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=34230cbd-d3d2-4cb8-855a-307883bc35ea ro quiet splash 
mem_sleep_default=deep video=1920x1080 usbcore.dyndbg=+p vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0VM1FG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0VM1FG:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1799988/+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 1799082] Re: Returning from suspend exits x session

2019-01-02 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Returning from suspend exits x session

Status in linux package in Ubuntu:
  Expired

Bug description:
  Using kernel 4.15.0-36 on my XPS15, suspending (e.g. closing the
  laptop lid) and reopening will take me to the 'swipe up' screen; upon
  swiping up, the session ends and I end back at the login screen. Does
  not reproduce on 4.15.0-34

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tim4385 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 21 20:07:05 2018
  InstallationDate: Installed on 2017-09-16 (399 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 003: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=13c87a4d-94b5-421e-8e39-d6bf0a2b05a5 ro quiet splash 
acpi_rev_override=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-06-03 (140 days ago)
  dmi.bios.date: 08/30/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799082/+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 1809868] Re: 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5 in btrfs_kernel_fixes failed on T

2019-01-02 Thread Po-Hsu Lin
It appears to be an error in command "btrfs receive -f
$TMP/incremental.send $MNT" [1]

This command will return 1 and complains about:
"ERROR: rmdir o259-6-0 failed. No such file or directory"

[1] https://kernel.ubuntu.com/git/ubuntu/autotest-client-
tests.git/tree/ubuntu_btrfs_kernel_fixes/fixes/29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5.sh#n39

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

Title:
  29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5 in btrfs_kernel_fixes failed
  on T

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Test failed with "ERROR: rmdir o259-6-0 failed. No such file or
  directory" on Trusty.

  
  Invoking test 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5

  fix 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5

  Btrfs: send, don't send rmdir for same target multiple times

  When doing an incremental send, if we delete a directory that has N > 1
  hardlinks for the same file and that file has the highest inode number
  inside the directory contents, an incremental send would send N times an
  rmdir operation against the directory. This made the btrfs receive command
  fail on the second rmdir instruction, as the target directory didn't exist
  anymore.

  Performing full device TRIM (1.00GiB) ...
  Turning ON incompat feature 'extref': increased hardlink limit per file to 
65536

  WARNING! - Btrfs v3.12 IS EXPERIMENTAL
  WARNING! - see http://btrfs.wiki.kernel.org before using

  fs created label (null) on /dev/loop0
nodesize 16384 leafsize 16384 sectorsize 4096 size 1.00GiB
  Btrfs v3.12
  Create a readonly snapshot of 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5' in 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap1'
  At subvol /tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap1
  Create a readonly snapshot of 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5' in 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap2'
  At subvol /tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap2
  Performing full device TRIM (1.00GiB) ...
  Turning ON incompat feature 'extref': increased hardlink limit per file to 
65536

  WARNING! - Btrfs v3.12 IS EXPERIMENTAL
  WARNING! - see http://btrfs.wiki.kernel.org before using

  fs created label (null) on /dev/loop0
nodesize 16384 leafsize 16384 sectorsize 4096 size 1.00GiB
  Btrfs v3.12
  At subvol snap1
  At snapshot snap2
  ERROR: rmdir o259-6-0 failed. No such file or directory
  incremental receive failed

  It seems that commit 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5 does not
  exist in Trusty tree.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-164-generic 3.13.0-164.214
  ProcVersionSignature: User Name 3.13.0-164.214-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-164-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 27 03:14 seq
   crw-rw 1 root audio 116, 33 Dec 27 03:14 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   [13958.095408] btrfs: device fsid da34075a-4eaa-4e50-aeea-02206e8c8e44 devid 
1 transid 4 /dev/loop0
   [13958.102670] btrfs: device fsid da34075a-4eaa-4e50-aeea-02206e8c8e44 devid 
1 transid 4 /dev/loop0
   [13958.105901] btrfs: device fsid da34075a-4eaa-4e50-aeea-02206e8c8e44 devid 
1 transid 4 /dev/loop0
   [13958.106099] btrfs: disk space caching is enabled
   [13958.107771] btrfs: creating UUID tree
  Date: Thu Dec 27 07:11:58 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-164-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-164-generic N/A
   linux-backports-modules-3.13.0-164-generic  N/A
   linux-firmware  1.127.24
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.pr

[Kernel-packages] [Bug 1810092] Re: nvidia-384 384.130-0ubuntu0.16.04.1: nvidia-384 kernel module failed to build

2019-01-02 Thread Seth Arnold
** Information type changed from Private Security to Public

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

Title:
  nvidia-384 384.130-0ubuntu0.16.04.1: nvidia-384 kernel module failed
  to build

Status in nvidia-graphics-drivers-384 package in Ubuntu:
  New

Bug description:
  Ubuntu starts in recovery mode only

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-384 384.130-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  DKMSKernelVersion: 4.4.0-141-generic
  Date: Sun Dec 30 20:39:36 2018
  InstallationDate: Installed on 2018-10-20 (70 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  PackageVersion: 384.130-0ubuntu0.16.04.1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.29
  SourcePackage: nvidia-graphics-drivers-384
  Title: nvidia-384 384.130-0ubuntu0.16.04.1: nvidia-384 kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia-384_hybrid.conf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1810092/+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 1774711] Re: excessive seccomp audit logs

2019-01-02 Thread A. Denton
After some research I can now safely confirm this bug. However, the log
lines do not seem to be related to any rules in "/etc/audit/rules.d" or
AppArmor profiles loaded. %‑)

The only difference between the log lines in *this* bug report, my lines
and the ones mentioned on
https://bugzilla.redhat.com/show_bug.cgi?id=1507282 seems to be system-
specific configuration, e.g. SELinux.

Over the past 24 hours, I also had sometimes 100 lines at once in my log
when opening or reloading a web page, in a new tab in Firefox. Therefore
Firefox seems to be the only "offending" application at present.

I also cleared the /etc/audit/rules.d and uninstalled the AppArmor
extras packages (apparmor-profiles, apparmor-profiles-extra) with the
Firefox profiles in it. Unfortunately the logs lines still poured in.
Therefore I also changed the abstractions for Firefox
(/etc/apparmor.d/abstractions/ubuntu-browsers) and commented out
everything Firefox related, with no avail.

The problem is somewhere deeper and not Firefox-specific. I hope Tyler
Hicks (tyhicks) is correct and the fixes mentioned will soon be
available. Due to the problem I generated several GiB of logs a day
which is not so good for my SSD (even with wear-leveling).

My temporary workaround is to stop auditd, since unlike
/etc/systemd/journald.conf there is no Storage=volatile option for
auditd. :-0  ',:-l  >:/

** Bug watch added: Red Hat Bugzilla #1507282
   https://bugzilla.redhat.com/show_bug.cgi?id=1507282

** Bug watch added: Red Hat Bugzilla #1117953
   https://bugzilla.redhat.com/show_bug.cgi?id=1117953

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

Title:
  excessive seccomp audit logs

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello, my audit logs are currently filled with messages from Firefox's
  seccomp filters which looks like this:

  type=SECCOMP msg=audit(1527882167.659:223316): auid=1000 uid=1000 gid=1000 
ses=1 pid=28901 comm=57656220436F6E74656E74 
exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 
arch=c03e syscall=257 compat=0 ip=0x7f4329623d19 code=0x3
  type=SECCOMP msg=audit(1527882167.659:223317): auid=1000 uid=1000 gid=1000 
ses=1 pid=28901 comm=57656220436F6E74656E74 
exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 
arch=c03e syscall=4 compat=0 ip=0x7f4329623775 code=0x3
  type=SECCOMP msg=audit(1527882167.659:223318): auid=1000 uid=1000 gid=1000 
ses=1 pid=28901 comm=57656220436F6E74656E74 
exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 
arch=c03e syscall=87 compat=0 ip=0x7f4329625d47 code=0x3
  type=SECCOMP msg=audit(1527882167.687:223319): auid=1000 uid=1000 gid=1000 
ses=1 pid=28901 comm=57656220436F6E74656E74 
exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 
arch=c03e syscall=257 compat=0 ip=0x7f4329623d19 code=0x3
  type=SECCOMP msg=audit(1527882167.687:223320): auid=1000 uid=1000 gid=1000 
ses=1 pid=28901 comm=57656220436F6E74656E74 
exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 
arch=c03e syscall=4 compat=0 ip=0x7f4329623775 code=0x3
  type=SECCOMP msg=audit(1527882167.687:223321): auid=1000 uid=1000 gid=1000 
ses=1 pid=28901 comm=57656220436F6E74656E74 
exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 
arch=c03e syscall=87 compat=0 ip=0x7f4329625d47 code=0x3
  type=SECCOMP msg=audit(1527882167.691:223322): auid=1000 uid=1000 gid=1000 
ses=1 pid=28901 comm=57656220436F6E74656E74 
exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 
arch=c03e syscall=257 compat=0 ip=0x7f4329623d19 code=0x3
  type=SECCOMP msg=audit(1527882167.691:223323): auid=1000 uid=1000 gid=1000 
ses=1 pid=28901 comm=57656220436F6E74656E74 
exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 
arch=c03e syscall=4 compat=0 ip=0x7f4329623775 code=0x3
  type=SECCOMP msg=audit(1527882167.691:223324): auid=1000 uid=1000 gid=1000 
ses=1 pid=28901 comm=57656220436F6E74656E74 
exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 
arch=c03e syscall=87 compat=0 ip=0x7f4329625d47 code=0x3

  $ aa-decode 57656220436F6E74656E74
  Decoded: Web Content
  $ aa-decode 
2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429
  Decoded: /usr/lib/firefox/firefox (deleted)

  Over a recent 48 hour stretch it averaged out to nearly one message
  per second.

  My current audit rules are:
  ## This file is automatically generated from /etc/audit/rules.d
  -D
  -b 8192

  --loginuid-immutable
  -a always,exit -F arch=b32 -S adjtimex,settimeofday,stime -F key=time-change
  -a always,exit -F arch=b64 -S adjtimex,settimeofday -F key=time-change
  -a always,exit -F arch=b32 -S clock_settime -F a0=0x0 -F 

[Kernel-packages] [Bug 1774711] Re: excessive seccomp audit logs

2019-01-02 Thread A. Denton
Oh in short my /etc/audit/rules.d/audit.rules looks like this:

-D
-b 8192
-f 1
-i
--backlog_wait_time 0
-w /etc/anacrontab -p w -k AU-FS01-0001
[some more -w `foo` -p w -k `bar` here ...]

Has someone here tried
https://bugzilla.redhat.com/show_bug.cgi?id=1117953 / adding a "-a
task,never" to /etc/audit/rules.d/audit.rules? Is that a bit extendive?


However, 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/kernel/seccomp.c?id=326bee0286d7f6b0d780f5b75a35ea9fe489a802
 looks very promising!
-   /*
-* Let the audit subsystem decide if the action should be audited based
-* on whether the current task itself is being audited.
-*/
-   return audit_seccomp(syscall, signr, action);
+   audit_seccomp(syscall, signr, action);

Thanks Tyler! :×

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

Title:
  excessive seccomp audit logs

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello, my audit logs are currently filled with messages from Firefox's
  seccomp filters which looks like this:

  type=SECCOMP msg=audit(1527882167.659:223316): auid=1000 uid=1000 gid=1000 
ses=1 pid=28901 comm=57656220436F6E74656E74 
exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 
arch=c03e syscall=257 compat=0 ip=0x7f4329623d19 code=0x3
  type=SECCOMP msg=audit(1527882167.659:223317): auid=1000 uid=1000 gid=1000 
ses=1 pid=28901 comm=57656220436F6E74656E74 
exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 
arch=c03e syscall=4 compat=0 ip=0x7f4329623775 code=0x3
  type=SECCOMP msg=audit(1527882167.659:223318): auid=1000 uid=1000 gid=1000 
ses=1 pid=28901 comm=57656220436F6E74656E74 
exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 
arch=c03e syscall=87 compat=0 ip=0x7f4329625d47 code=0x3
  type=SECCOMP msg=audit(1527882167.687:223319): auid=1000 uid=1000 gid=1000 
ses=1 pid=28901 comm=57656220436F6E74656E74 
exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 
arch=c03e syscall=257 compat=0 ip=0x7f4329623d19 code=0x3
  type=SECCOMP msg=audit(1527882167.687:223320): auid=1000 uid=1000 gid=1000 
ses=1 pid=28901 comm=57656220436F6E74656E74 
exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 
arch=c03e syscall=4 compat=0 ip=0x7f4329623775 code=0x3
  type=SECCOMP msg=audit(1527882167.687:223321): auid=1000 uid=1000 gid=1000 
ses=1 pid=28901 comm=57656220436F6E74656E74 
exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 
arch=c03e syscall=87 compat=0 ip=0x7f4329625d47 code=0x3
  type=SECCOMP msg=audit(1527882167.691:223322): auid=1000 uid=1000 gid=1000 
ses=1 pid=28901 comm=57656220436F6E74656E74 
exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 
arch=c03e syscall=257 compat=0 ip=0x7f4329623d19 code=0x3
  type=SECCOMP msg=audit(1527882167.691:223323): auid=1000 uid=1000 gid=1000 
ses=1 pid=28901 comm=57656220436F6E74656E74 
exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 
arch=c03e syscall=4 compat=0 ip=0x7f4329623775 code=0x3
  type=SECCOMP msg=audit(1527882167.691:223324): auid=1000 uid=1000 gid=1000 
ses=1 pid=28901 comm=57656220436F6E74656E74 
exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 
arch=c03e syscall=87 compat=0 ip=0x7f4329625d47 code=0x3

  $ aa-decode 57656220436F6E74656E74
  Decoded: Web Content
  $ aa-decode 
2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429
  Decoded: /usr/lib/firefox/firefox (deleted)

  Over a recent 48 hour stretch it averaged out to nearly one message
  per second.

  My current audit rules are:
  ## This file is automatically generated from /etc/audit/rules.d
  -D
  -b 8192

  --loginuid-immutable
  -a always,exit -F arch=b32 -S adjtimex,settimeofday,stime -F key=time-change
  -a always,exit -F arch=b64 -S adjtimex,settimeofday -F key=time-change
  -a always,exit -F arch=b32 -S clock_settime -F a0=0x0 -F key=time-change
  -a always,exit -F arch=b64 -S clock_settime -F a0=0x0 -F key=time-change
  -w /etc/localtime -p wa -k time-change
  -w /usr/share/zoneinfo/ -p wa -k time-change
  -w /etc/group -p wa -k identity
  -w /etc/passwd -p wa -k identity
  -w /etc/gshadow -p wa -k identity
  -w /etc/shadow -p wa -k identity
  -w /etc/security/opasswd -p wa -k identity
  -a always,exit -F arch=b32 -S sethostname,setdomainname -F key=system-locale
  -a always,exit -F arch=b64 -S sethostname,setdomainname -F key=system-locale
  -w /etc/issue -p wa -k system-locale
  -w /etc/issue.net -p wa -k system-locale
  -w /etc/hosts -p wa -k system-locale
  -w /etc/network -p wa -k system-locale
  -a always,exit -F dir=/etc/NetworkManager/ -F perm=wa -F key=system-locale
  -w /etc/a

[Kernel-packages] [Bug 1809603] Re: package libnvidia-compute-390 (not installed) failed to install/upgrade: попытка перезаписать «/usr/lib/x86_64-linux-gnu/libnvidia-ml.so», который уже имеется в пак

2019-01-02 Thread Seth Arnold
** Information type changed from Private Security to Public

** Also affects: nvidia-graphics-drivers-340 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  package libnvidia-compute-390 (not installed) failed to
  install/upgrade: попытка перезаписать «/usr/lib/x86_64-linux-gnu
  /libnvidia-ml.so», который уже имеется в пакете nvidia-340
  340.107-0ubuntu0.18.04.1

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  after install package 'hashcat'

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libnvidia-compute-390 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Sun Dec 23 21:16:02 2018
  ErrorMessage: попытка перезаписать 
«/usr/lib/x86_64-linux-gnu/libnvidia-ml.so», который уже имеется в пакете 
nvidia-340 340.107-0ubuntu0.18.04.1
  InstallationDate: Installed on 2018-12-23 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: nvidia-graphics-drivers-390
  Title: package libnvidia-compute-390 (not installed) failed to 
install/upgrade: попытка перезаписать 
«/usr/lib/x86_64-linux-gnu/libnvidia-ml.so», который уже имеется в пакете 
nvidia-340 340.107-0ubuntu0.18.04.1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1809603/+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 1787742] Re: TP-Link Archer T1U 5GHz WiFi adapter not compatible

2019-01-02 Thread Robert weaver
I can confirm that after upgrading to Kernel 4.18.0-13 , and moving up to 
ubuntu 18.10 
BCM4360 802.11ac Wireless Network Adaptor (rev 03)
Still not able to view 5Ghz networks .
Wifi Radar only see's G Networks.

iwlist freq shows available frequencies
wlp2s032 channels in total; available frequencies :
  Channel 01 : 2.412 GHz
  Channel 02 : 2.417 GHz
  Channel 03 : 2.422 GHz
  Channel 04 : 2.427 GHz
  Channel 05 : 2.432 GHz
  Channel 06 : 2.437 GHz
  Channel 07 : 2.442 GHz
  Channel 08 : 2.447 GHz
  Channel 09 : 2.452 GHz
  Channel 10 : 2.457 GHz
  Channel 11 : 2.462 GHz
  Channel 12 : 2.467 GHz
  Channel 13 : 2.472 GHz
  Channel 36 : 5.18 GHz
  Channel 38 : 5.19 GHz
  Channel 40 : 5.2 GHz
  Channel 42 : 5.21 GHz
  Channel 44 : 5.22 GHz
  Channel 46 : 5.23 GHz
  Channel 48 : 5.24 GHz
  Channel 52 : 5.26 GHz
  Channel 54 : 5.27 GHz
  Channel 56 : 5.28 GHz
  Channel 58 : 5.29 GHz
  Channel 60 : 5.3 GHz
  Channel 62 : 5.31 GHz
  Channel 64 : 5.32 GHz
  Channel 100 : 5.5 GHz
  Channel 102 : 5.51 GHz
  Channel 104 : 5.52 GHz
  Channel 106 : 5.53 GHz
  Channel 108 : 5.54 GHz
  Current Frequency:2.462 GHz (Channel 11)

I can confirm that when I run iwlist scan i can see skqbox on 5GHz 
8166-  Cell 05 - Address: 0C:F9:C0:24:19:3B
8213-Channel:36
8244:Frequency:5.18 GHz (Channel 36)
8296-Quality=28/70  Signal level=-82 dBm  
8354-Encryption key:on
8392-ESSID:"SKY2D188"

So Changing my wifi AP , to use 5Ghz on Channel 36 , im now able to see
the AP

10209-  Cell 06 - Address: 7C:FF:4D:EE:D3:A8
10256-Channel:36
10287:Frequency:5.18 GHz (Channel 36)
10339-Quality=34/70  Signal level=-76 dBm  
10397-Encryption key:on
10435-ESSID:"FRITZ!Box 3490"
10478-Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
10550-  36 Mb/s; 48 Mb/s; 54 Mb/s
10606-Mode:Master
10638-Extra:tsf=
10685-Extra: Last beacon: 80ms ago
10734-IE: Unknown: 000E465249545A21426F782033343930

But connection Manager still wont use the the above network

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

Title:
  TP-Link Archer T1U 5GHz WiFi adapter not compatible

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My TP-Link Archer T1U 5GHz USB WiFi adapter/dongle is not being recognized by 
the system settings and WiFi setup wizards, likely due to a compatibility issue 
with the Linux kernel.
  The device is functional in Windows and recognized by my motherboard, but 
unfortunately it is a mere waste of a USB port with Ubuntu and other Linux 
distributions.

  -
  Terminal output when running 'lsusb' cmd:
  jeb@A880G:~$ lsusb
  Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 006 Device 002: ID 03f0:d407 Hewlett-Packard 
  Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 005 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
  Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 001 Device 005: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
  Bus 001 Device 008: ID 0461:4d75 Primax Electronics, Ltd Rocketfish RF-FLBTAD 
Bluetooth Adapter
  Bus 001 Device 007: ID 0a5c:4503 Broadcom Corp. Mouse (Boot Interface 
Subclass)
  Bus 001 Device 006: ID 0a5c:4502 Broadcom Corp. Keyboard (Boot Interface 
Subclass)
  Bus 001 Device 004: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part 
of BCM2046 Bluetooth)
  Bus 001 Device 009: ID 2357:0105  
  Bus 001 Device 003: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless 
Adapter
  Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
  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
  -

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-32-generic 4.15.0-32.35
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jeb1608 F pulseaudio
   /dev/snd/controlC1:  jeb1608 F pulseaudio
   /dev/snd/controlC0:  jeb1608 F pulseaudio
  Curr

[Kernel-packages] [Bug 1805079] Re: click/pop noise in the headphone on several lenovo laptops

2019-01-02 Thread James Thorne
I am using an X1 Carbon Gen 6 (BIOS 1.31) with Ubuntu 18.04.1 LTS, and I
too experience the popping sounds in the left-channel of my headphones
(this does not occur when connecting the same headphones with a 3.5mm-
to-USB-C adapter to the second USB-C port).

Other than that issue, audio through the headphones sounds great and can
get very loud (I typically cannot go above 58%), but audio through the
speakers can get tinny/distorted and is quiet at 100%. I believe this is
a known issue with the X1 Carbon's speakers and is probably unrelated to
the issue at hand, but I thought it is worth mentioning since there is
discussion in this thread about using the speaker's DAC for the
headphones instead of the headphone's DAC.

I applied the changes mentioned here [1], and the popping sounds in the
left-channel of my headphones appear to have stopped. I have been using
this video [2] to test before and after the changes due to its wide
range of audio and vocals (quiet, normal, and loud moments).


alsa-info: 
http://www.alsa-project.org/db/?f=d961cfbf429bc18b38ce8d1cf8e931482ba4a627

[1] https://forums.lenovo.com/t5/Linux-Discussion/X1-Carbon-Gen-6-weird-
audio-behaviour/m-p/4172468/highlight/true#M11520

[2] https://youtu.be/f2kesmAO8VU

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

Title:
  click/pop noise in the headphone on several lenovo laptops

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  [Impact]
  Lenovo told us that some linux uers reported headphone noise on Lenovo's
  website. After investigating, we found those Lenovo laptop mdoels all
  have the codec of alc285, and we can reproduce the noise problem too.

  [Fix]
  Don't use the DAC of headphone, let headphone share the DAC with speaker,
  the noise disappears.

  [Test Case]
  After applying this patch, we tested on Lenovo P52, P72, X1 carbon and X1
  Yoda2, no noise anymore

  [Regression Potential]
  Low. This patch only apply to several lenovo machines, and after applying
  this patch, both speaker and headphone still work very well.

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

2019-01-02 Thread 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/1810345

Title:
  kernel: general protection fault:  [#1] SMP PTI

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  using 18.10, all updates included. Desktop (gnome on wayland) is
  crashing from time to time at idle, or on reactivating from
  screensaver or while working(mostly while playing videos in browsers)
  where only sysreq gets to reboot. Running kernel 4.18.0-13-generic
  #14-Ubuntu

  Looking at the logs i found:

  Jan  2 23:29:07 ThinkPad kernel: [44709.167257] general protection fault: 
 [#1] SMP PTI
  Jan  2 23:29:07 ThinkPad kernel: [44709.167284] CPU: 0 PID: 22311 Comm: 
kworker/u17:0 Not tainted 4.18.0-13-generic #14-Ubuntu
  Jan  2 23:29:07 ThinkPad kernel: [44709.167286] Hardware name: LENOVO 
2325TZX/2325TZX, BIOS G2ETB3WW (2.73 ) 06/19/2018
  Jan  2 23:29:07 ThinkPad kernel: [44709.167315] Workqueue: hci0 hci_rx_work 
[bluetooth]
  Jan  2 23:29:07 ThinkPad kernel: [44709.167325] RIP: 
0010:__wake_up_common+0xb4/0x140
  Jan  2 23:29:07 ThinkPad kernel: [44709.167327] Code: 4d 85 ed 74 25 41 83 c4 
01 41 83 fc 40 7e 1b 49 8d 46 18 48 39 c3 75 70 8b 45 c4 48 83 c4 18 5b 41 5c 
41 5d 41 5e 41 5f 5d c3 <49> 8b 56 18 49 8d 46 18 4c 89 f7 4c 8d 72 e8 48 39 c3 
75 94 eb d8 
  Jan  2 23:29:07 ThinkPad kernel: [44709.167376] RSP: 0018:a941c3c0fbd8 
EFLAGS: 00010083
  Jan  2 23:29:07 ThinkPad kernel: [44709.167379] RAX:  RBX: 
9c5d5ef42008 RCX: 
  Jan  2 23:29:07 ThinkPad kernel: [44709.167381] RDX: 0001 RSI: 
0082 RDI: 0082
  Jan  2 23:29:07 ThinkPad kernel: [44709.167384] RBP: a941c3c0fc18 R08: 
 R09: a941c3c0fb50
  Jan  2 23:29:07 ThinkPad kernel: [44709.167386] R10: 9c5e03920400 R11: 
0a00 R12: 0002
  Jan  2 23:29:07 ThinkPad kernel: [44709.167389] R13: a941c3c0fc30 R14: 
dead00e8 R15: 
  Jan  2 23:29:07 ThinkPad kernel: [44709.167392] FS:  () 
GS:9c5f1e20() knlGS:
  Jan  2 23:29:07 ThinkPad kernel: [44709.167395] CS:  0010 DS:  ES:  
CR0: 80050033
  Jan  2 23:29:07 ThinkPad kernel: [44709.167397] CR2: 7f741dc0 CR3: 
0001cd20a005 CR4: 001606f0
  Jan  2 23:29:07 ThinkPad kernel: [44709.167399] Call Trace:
  Jan  2 23:29:07 ThinkPad kernel: [44709.167407]  
__wake_up_common_lock+0x80/0xc0
  Jan  2 23:29:07 ThinkPad kernel: [44709.167412]  __wake_up+0x13/0x20
  Jan  2 23:29:07 ThinkPad kernel: [44709.167418]  sock_def_wakeup+0x36/0x40
  Jan  2 23:29:07 ThinkPad kernel: [44709.167440]  
l2cap_sock_teardown_cb+0x192/0x1f0 [bluetooth]
  Jan  2 23:29:07 ThinkPad kernel: [44709.167460]  l2cap_chan_del+0x4a/0x2f0 
[bluetooth]
  Jan  2 23:29:07 ThinkPad kernel: [44709.167481]  
l2cap_sig_channel+0xb55/0x1270 [bluetooth]
  Jan  2 23:29:07 ThinkPad kernel: [44709.167486]  ? __switch_to_asm+0x34/0x70
  Jan  2 23:29:07 ThinkPad kernel: [44709.167490]  ? __switch_to_asm+0x40/0x70
  Jan  2 23:29:07 ThinkPad kernel: [44709.167493]  ? __switch_to_asm+0x34/0x70
  Jan  2 23:29:07 ThinkPad kernel: [44709.167513]  l2cap_recv_frame+0x280/0xc80 
[bluetooth]
  Jan  2 23:29:07 ThinkPad kernel: [44709.167517]  ? __switch_to_asm+0x40/0x70
  Jan  2 23:29:07 ThinkPad kernel: [44709.167519]  ? __switch_to_asm+0x34/0x70
  Jan  2 23:29:07 ThinkPad kernel: [44709.167542]  
l2cap_recv_acldata+0x2f6/0x300 [bluetooth]
  Jan  2 23:29:07 ThinkPad kernel: [44709.167558]  hci_rx_work+0x28f/0x380 
[bluetooth]
  Jan  2 23:29:07 ThinkPad kernel: [44709.167565]  process_one_work+0x20f/0x3c0
  Jan  2 23:29:07 ThinkPad kernel: [44709.167570]  worker_thread+0x34/0x400
  Jan  2 23:29:07 ThinkPad kernel: [44709.167575]  kthread+0x120/0x140
  Jan  2 23:29:07 ThinkPad kernel: [44709.167579]  ? 
pwq_unbound_release_workfn+0xd0/0xd0
  Jan  2 23:29:07 ThinkPad kernel: [44709.167583]  ? kthread_bind+0x40/0x40
  Jan  2 23:29:07 ThinkPad kernel: [44709.167586]  ret_from_fork+0x35/0x40
  Jan  2 23:29:07 ThinkPad kernel: [44709.167589] Modules linked in: rfcomm 
hidp rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache ccm cmac bnep 
nls_iso8859_1 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic 
wmi_bmof intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
snd_hda_intel kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul 
snd_hda_codec ghash_clmulni_intel snd_hda_core pcbc snd_hwdep snd_pcm 
aesni_intel aes_x86_64 crypto_simd arc4 cryptd glue_helper intel_cstate 
intel_rapl_perf iwldvm snd_seq_midi snd_seq_midi_event uvcvideo mac80211 btusb 
input_leds snd_rawmidi joydev btrtl serio_raw btbcm videobuf2_vmalloc btintel 
snd_seq videobuf2_memops thinkpad_acpi videobuf2_v4l2 iwlwifi bluetooth 
videobuf2_common i915 nv

[Kernel-packages] [Bug 1809586] Re: [ 14.259626] i2c_hid i2c-HTIX5288:00: i2c-HTIX5288:00 supply vddl not found, using dummy regulator

2019-01-02 Thread Daniel
I didn't log this bug but i have the same issue on my geo book 3 same
HTIX touchpad. Tested it today on mainline 4.20 and it did not fix the
issue. I also have kworker consuming 100% CPU and when i echo "disable"
> /sys/firmware/acpi/interrupts/gpe03 the CPU drops and the touchpad
response gets noticeibly worse. This is connsistent every time i disable
that interrupt.

Pretty sure its the same issue so just wnated to add this information.

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

Title:
  [   14.259626] i2c_hid i2c-HTIX5288:00: i2c-HTIX5288:00 supply vddl
  not found, using dummy regulator

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Missing i2c-HTIX5288 driver. Touch does work OK but sometimes it
  freezes at random times. When using a mouse the mouse works fine.

  Ubuntu 18.04
  Kernel 4.18.0-13
  Dual-Core Intel® Celeron® N4000 CPU @ 1.10GHz

  ~$ dmesg

  [   14.259578] i2c_hid i2c-HTIX5288:00: i2c-HTIX5288:00 supply vdd not found, 
using dummy regulator
  [   14.259622] i2c_hid i2c-HTIX5288:00: Linked as a consumer to regulator.0
  [   14.259626] i2c_hid i2c-HTIX5288:00: i2c-HTIX5288:00 supply vddl not 
found, using dummy regulator
  [   14.296078] ahci :00:12.0: port does not support device sleep
  [   14.421143] input: HTIX5288:00 0911:5288 Mouse as 
/devices/pci:00/:00:17.3/i2c_designware.7/i2c-12/i2c-HTIX5288:00/0018:0911:5288.0002/input/input17
  [   14.421507] input: HTIX5288:00 0911:5288 Touchpad as 
/devices/pci:00/:00:17.3/i2c_designware.7/i2c-12/i2c-HTIX5288:00/0018:0911:5288.0002/input/input18
  [   14.421715] hid-generic 0018:0911:5288.0002: input,hidraw1: I2C HID v1.00 
Mouse [HTIX5288:00 0911:5288] on i2c-HTIX5288:00
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  juno   1113 F pulseaudio
   /dev/snd/controlC0:  juno   1113 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-12-23 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Default string Default string
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=161d8da2-6b65-4a94-b327-82974d663e77 ro quiet splash acpi_osi=Linux 
i8042.nopnp vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/28/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL5-BIOS-4G-V3-002-A
  dmi.board.asset.tag: Default string
  dmi.board.name: Gemini II
  dmi.board.vendor: PC Specialist LTD
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL5-BIOS-4G-V3-002-A:bd11/28/2018:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnPCSpecialistLTD:rnGeminiII:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Default string

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809586/+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 1810345] [NEW] kernel: general protection fault: 0000 [#1] SMP PTI

2019-01-02 Thread Achim Behrens
Public bug reported:

using 18.10, all updates included. Desktop (gnome on wayland) is
crashing from time to time at idle, or on reactivating from screensaver
or while working(mostly while playing videos in browsers) where only
sysreq gets to reboot. Running kernel 4.18.0-13-generic #14-Ubuntu

Looking at the logs i found:

Jan  2 23:29:07 ThinkPad kernel: [44709.167257] general protection fault:  
[#1] SMP PTI
Jan  2 23:29:07 ThinkPad kernel: [44709.167284] CPU: 0 PID: 22311 Comm: 
kworker/u17:0 Not tainted 4.18.0-13-generic #14-Ubuntu
Jan  2 23:29:07 ThinkPad kernel: [44709.167286] Hardware name: LENOVO 
2325TZX/2325TZX, BIOS G2ETB3WW (2.73 ) 06/19/2018
Jan  2 23:29:07 ThinkPad kernel: [44709.167315] Workqueue: hci0 hci_rx_work 
[bluetooth]
Jan  2 23:29:07 ThinkPad kernel: [44709.167325] RIP: 
0010:__wake_up_common+0xb4/0x140
Jan  2 23:29:07 ThinkPad kernel: [44709.167327] Code: 4d 85 ed 74 25 41 83 c4 
01 41 83 fc 40 7e 1b 49 8d 46 18 48 39 c3 75 70 8b 45 c4 48 83 c4 18 5b 41 5c 
41 5d 41 5e 41 5f 5d c3 <49> 8b 56 18 49 8d 46 18 4c 89 f7 4c 8d 72 e8 48 39 c3 
75 94 eb d8 
Jan  2 23:29:07 ThinkPad kernel: [44709.167376] RSP: 0018:a941c3c0fbd8 
EFLAGS: 00010083
Jan  2 23:29:07 ThinkPad kernel: [44709.167379] RAX:  RBX: 
9c5d5ef42008 RCX: 
Jan  2 23:29:07 ThinkPad kernel: [44709.167381] RDX: 0001 RSI: 
0082 RDI: 0082
Jan  2 23:29:07 ThinkPad kernel: [44709.167384] RBP: a941c3c0fc18 R08: 
 R09: a941c3c0fb50
Jan  2 23:29:07 ThinkPad kernel: [44709.167386] R10: 9c5e03920400 R11: 
0a00 R12: 0002
Jan  2 23:29:07 ThinkPad kernel: [44709.167389] R13: a941c3c0fc30 R14: 
dead00e8 R15: 
Jan  2 23:29:07 ThinkPad kernel: [44709.167392] FS:  () 
GS:9c5f1e20() knlGS:
Jan  2 23:29:07 ThinkPad kernel: [44709.167395] CS:  0010 DS:  ES:  
CR0: 80050033
Jan  2 23:29:07 ThinkPad kernel: [44709.167397] CR2: 7f741dc0 CR3: 
0001cd20a005 CR4: 001606f0
Jan  2 23:29:07 ThinkPad kernel: [44709.167399] Call Trace:
Jan  2 23:29:07 ThinkPad kernel: [44709.167407]  __wake_up_common_lock+0x80/0xc0
Jan  2 23:29:07 ThinkPad kernel: [44709.167412]  __wake_up+0x13/0x20
Jan  2 23:29:07 ThinkPad kernel: [44709.167418]  sock_def_wakeup+0x36/0x40
Jan  2 23:29:07 ThinkPad kernel: [44709.167440]  
l2cap_sock_teardown_cb+0x192/0x1f0 [bluetooth]
Jan  2 23:29:07 ThinkPad kernel: [44709.167460]  l2cap_chan_del+0x4a/0x2f0 
[bluetooth]
Jan  2 23:29:07 ThinkPad kernel: [44709.167481]  l2cap_sig_channel+0xb55/0x1270 
[bluetooth]
Jan  2 23:29:07 ThinkPad kernel: [44709.167486]  ? __switch_to_asm+0x34/0x70
Jan  2 23:29:07 ThinkPad kernel: [44709.167490]  ? __switch_to_asm+0x40/0x70
Jan  2 23:29:07 ThinkPad kernel: [44709.167493]  ? __switch_to_asm+0x34/0x70
Jan  2 23:29:07 ThinkPad kernel: [44709.167513]  l2cap_recv_frame+0x280/0xc80 
[bluetooth]
Jan  2 23:29:07 ThinkPad kernel: [44709.167517]  ? __switch_to_asm+0x40/0x70
Jan  2 23:29:07 ThinkPad kernel: [44709.167519]  ? __switch_to_asm+0x34/0x70
Jan  2 23:29:07 ThinkPad kernel: [44709.167542]  l2cap_recv_acldata+0x2f6/0x300 
[bluetooth]
Jan  2 23:29:07 ThinkPad kernel: [44709.167558]  hci_rx_work+0x28f/0x380 
[bluetooth]
Jan  2 23:29:07 ThinkPad kernel: [44709.167565]  process_one_work+0x20f/0x3c0
Jan  2 23:29:07 ThinkPad kernel: [44709.167570]  worker_thread+0x34/0x400
Jan  2 23:29:07 ThinkPad kernel: [44709.167575]  kthread+0x120/0x140
Jan  2 23:29:07 ThinkPad kernel: [44709.167579]  ? 
pwq_unbound_release_workfn+0xd0/0xd0
Jan  2 23:29:07 ThinkPad kernel: [44709.167583]  ? kthread_bind+0x40/0x40
Jan  2 23:29:07 ThinkPad kernel: [44709.167586]  ret_from_fork+0x35/0x40
Jan  2 23:29:07 ThinkPad kernel: [44709.167589] Modules linked in: rfcomm hidp 
rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache ccm cmac bnep 
nls_iso8859_1 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic 
wmi_bmof intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
snd_hda_intel kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul 
snd_hda_codec ghash_clmulni_intel snd_hda_core pcbc snd_hwdep snd_pcm 
aesni_intel aes_x86_64 crypto_simd arc4 cryptd glue_helper intel_cstate 
intel_rapl_perf iwldvm snd_seq_midi snd_seq_midi_event uvcvideo mac80211 btusb 
input_leds snd_rawmidi joydev btrtl serio_raw btbcm videobuf2_vmalloc btintel 
snd_seq videobuf2_memops thinkpad_acpi videobuf2_v4l2 iwlwifi bluetooth 
videobuf2_common i915 nvram videodev snd_seq_device ecdh_generic snd_timer 
media cfg80211 drm_kms_helper mei_me
Jan  2 23:29:07 ThinkPad kernel: [44709.167653]  mei snd wmi drm mac_hid 
soundcore i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt video 
sch_fq_codel parport_pc sunrpc ppdev lp parport ip_tables x_tables autofs4 
hid_generic usbhid hid gpio_ich psmouse e1000e ahci i2c_i801 sdhci_pci libahci 
cqhci lpc_ich sdhci
Jan  2 23:29:07 ThinkPad kernel: [447

[Kernel-packages] [Bug 1783523] Re: Beep doesn't beep

2019-01-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Beep doesn't beep

Status in beep package in Ubuntu:
  Confirmed

Bug description:
  The 'beep' command does not beep: I get no errors, not even in log files or 
dmesg, but no sound can be heard.
  The beep volume is ok (checked and unmuted with 'alsamixer').

  This used to work in 16.04, so it is a regression.

  'lsmod' shows that the 'pcspkr' module is loaded. It was also un-
  blacklisted from /etc/modprobe.d/blacklist.

  Thanks,
  MZ

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: beep 1.3-4+deb9u1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 25 11:39:47 2018
  InstallationDate: Installed on 2018-07-12 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: beep
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/beep/+bug/1783523/+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 1810328] Re: iommu - need to effectively disable iommu if "intel_iommu=off" is passed as a kernel parameter

2019-01-02 Thread Guilherme G. Piccoli
Patch submitted to kernel-team mailing list:
https://lists.ubuntu.com/archives/kernel-team/2019-January/097452.html

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

Title:
  iommu - need to effectively disable iommu if "intel_iommu=off" is
  passed as a kernel parameter

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  * If the parameter "intel_iommu=off" is passed for the kernel in a
  boot instance coming from a previously iommu-enabled kernel (like a
  kexec/kdump scenario), currently Xenial kernel (4.4 version) is
  missing a patch to effectively disable the iommu. As a result, the
  previous DMA mappings remain and the new kernel will try to use them,
  which is wrong since we don't have iommu initialized to translate the
  addresses.

  * The upstream patch proposed to SRU here, 161b28aae165 ("iommu/vt-d:
  Make sure IOMMUs are off when intel_iommu=off") fixes the issue by
  effectively disabling the iommu in case it was requested.

  * One important use case is in a scenario of iommu bug that is leading to a 
kernel crash; kdump naturally will have the iommu tables copied from previous 
kernel in kdump boot time, so if iommu
  tables are bogus, we could inherit the bug in the kdump kernel preventing a 
successful dump.
  Have the ability to disable iommu (given that the functionality is there) is 
essential.

  
  [Test Case]

  * Boot a kernel with "intel_iommu=on", and then kexec a new kernel with 
"intel_iommu=off"
  parameter. A kdump test is also possible, by changing the kdump command-line 
to disable
  iommu (after booting a kernel with iommu enabled) - then, induce a crash and 
the issue
  will show.

  * Attached to this Launchpad are 2 files with the kdump test case: 
"iommu-missing" shows
  the issue in a Trusty HWE kernel - without the fix patch, we can see messages 
like

  [36.489918] DMAR: DRHD: handling fault status reg 202
  [36.734830] DMAR: DMAR:[DMA Read] Request device [03:00.0] fault addr 3179a000
  [36.734830] DMAR:[fault reason 06] PTE Read access is not set

  In our case, the rootfs couldn't be initialized since the SCSI adapter
  wasn't initialized due to the DMAR failures (hpsa driver). Also,
  Solarflare NIC (sfc driver) couldn't get initialized too.

  The patch fixed those error messages and the rootfs was mounted (see file 
"iommu-patched").
  Notice the succeeding case couldn't kdump for other reasons, not strictly 
related to the proposed patch here.

  
  [Regression Potential]

  * iommu operations are complex and subject to HW issues eventually. Having 
iommu enabled
  and then boot a kernel with this component disabled is inherently a "danger" 
operation from
  drivers (or any users of such mappings) point-of-view. That said, I don't see 
a potential regression for this patch, in a way currently an user can't disable 
iommu properly if it was
  once enabled, and this simple patch fixes it

  * Care should be taken of course to not confuse regressions with problems 
induced by disabling the
  iommu after it was enabled before (which would show that the patch works fine 
indeed, by allowing iommu to get disabled) - some drivers/devices may require 
iommu to be enabled in order to work, in such case disabling it would prevent 
the device to work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810328/+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 1810328] Re: iommu - need to effectively disable iommu if "intel_iommu=off" is passed as a kernel parameter

2019-01-02 Thread Guilherme G. Piccoli
** Attachment added: "Issue scenario (iommu couldn't get disabled without the 
patch)"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810328/+attachment/5226416/+files/iommu-missing

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

Title:
  iommu - need to effectively disable iommu if "intel_iommu=off" is
  passed as a kernel parameter

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  * If the parameter "intel_iommu=off" is passed for the kernel in a
  boot instance coming from a previously iommu-enabled kernel (like a
  kexec/kdump scenario), currently Xenial kernel (4.4 version) is
  missing a patch to effectively disable the iommu. As a result, the
  previous DMA mappings remain and the new kernel will try to use them,
  which is wrong since we don't have iommu initialized to translate the
  addresses.

  * The upstream patch proposed to SRU here, 161b28aae165 ("iommu/vt-d:
  Make sure IOMMUs are off when intel_iommu=off") fixes the issue by
  effectively disabling the iommu in case it was requested.

  * One important use case is in a scenario of iommu bug that is leading to a 
kernel crash; kdump naturally will have the iommu tables copied from previous 
kernel in kdump boot time, so if iommu
  tables are bogus, we could inherit the bug in the kdump kernel preventing a 
successful dump.
  Have the ability to disable iommu (given that the functionality is there) is 
essential.

  
  [Test Case]

  * Boot a kernel with "intel_iommu=on", and then kexec a new kernel with 
"intel_iommu=off"
  parameter. A kdump test is also possible, by changing the kdump command-line 
to disable
  iommu (after booting a kernel with iommu enabled) - then, induce a crash and 
the issue
  will show.

  * Attached to this Launchpad are 2 files with the kdump test case: 
"iommu-missing" shows
  the issue in a Trusty HWE kernel - without the fix patch, we can see messages 
like

  [36.489918] DMAR: DRHD: handling fault status reg 202
  [36.734830] DMAR: DMAR:[DMA Read] Request device [03:00.0] fault addr 3179a000
  [36.734830] DMAR:[fault reason 06] PTE Read access is not set

  In our case, the rootfs couldn't be initialized since the SCSI adapter
  wasn't initialized due to the DMAR failures (hpsa driver). Also,
  Solarflare NIC (sfc driver) couldn't get initialized too.

  The patch fixed those error messages and the rootfs was mounted (see file 
"iommu-patched").
  Notice the succeeding case couldn't kdump for other reasons, not strictly 
related to the proposed patch here.

  
  [Regression Potential]

  * iommu operations are complex and subject to HW issues eventually. Having 
iommu enabled
  and then boot a kernel with this component disabled is inherently a "danger" 
operation from
  drivers (or any users of such mappings) point-of-view. That said, I don't see 
a potential regression for this patch, in a way currently an user can't disable 
iommu properly if it was
  once enabled, and this simple patch fixes it

  * Care should be taken of course to not confuse regressions with problems 
induced by disabling the
  iommu after it was enabled before (which would show that the patch works fine 
indeed, by allowing iommu to get disabled) - some drivers/devices may require 
iommu to be enabled in order to work, in such case disabling it would prevent 
the device to work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810328/+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 1810328] Re: iommu - need to effectively disable iommu if "intel_iommu=off" is passed as a kernel parameter

2019-01-02 Thread Guilherme G. Piccoli
** Attachment added: "Fix scenario (iommu correctly disabled with the proposed 
patch)"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810328/+attachment/5226417/+files/iommu-patched

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

Title:
  iommu - need to effectively disable iommu if "intel_iommu=off" is
  passed as a kernel parameter

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  * If the parameter "intel_iommu=off" is passed for the kernel in a
  boot instance coming from a previously iommu-enabled kernel (like a
  kexec/kdump scenario), currently Xenial kernel (4.4 version) is
  missing a patch to effectively disable the iommu. As a result, the
  previous DMA mappings remain and the new kernel will try to use them,
  which is wrong since we don't have iommu initialized to translate the
  addresses.

  * The upstream patch proposed to SRU here, 161b28aae165 ("iommu/vt-d:
  Make sure IOMMUs are off when intel_iommu=off") fixes the issue by
  effectively disabling the iommu in case it was requested.

  * One important use case is in a scenario of iommu bug that is leading to a 
kernel crash; kdump naturally will have the iommu tables copied from previous 
kernel in kdump boot time, so if iommu
  tables are bogus, we could inherit the bug in the kdump kernel preventing a 
successful dump.
  Have the ability to disable iommu (given that the functionality is there) is 
essential.

  
  [Test Case]

  * Boot a kernel with "intel_iommu=on", and then kexec a new kernel with 
"intel_iommu=off"
  parameter. A kdump test is also possible, by changing the kdump command-line 
to disable
  iommu (after booting a kernel with iommu enabled) - then, induce a crash and 
the issue
  will show.

  * Attached to this Launchpad are 2 files with the kdump test case: 
"iommu-missing" shows
  the issue in a Trusty HWE kernel - without the fix patch, we can see messages 
like

  [36.489918] DMAR: DRHD: handling fault status reg 202
  [36.734830] DMAR: DMAR:[DMA Read] Request device [03:00.0] fault addr 3179a000
  [36.734830] DMAR:[fault reason 06] PTE Read access is not set

  In our case, the rootfs couldn't be initialized since the SCSI adapter
  wasn't initialized due to the DMAR failures (hpsa driver). Also,
  Solarflare NIC (sfc driver) couldn't get initialized too.

  The patch fixed those error messages and the rootfs was mounted (see file 
"iommu-patched").
  Notice the succeeding case couldn't kdump for other reasons, not strictly 
related to the proposed patch here.

  
  [Regression Potential]

  * iommu operations are complex and subject to HW issues eventually. Having 
iommu enabled
  and then boot a kernel with this component disabled is inherently a "danger" 
operation from
  drivers (or any users of such mappings) point-of-view. That said, I don't see 
a potential regression for this patch, in a way currently an user can't disable 
iommu properly if it was
  once enabled, and this simple patch fixes it

  * Care should be taken of course to not confuse regressions with problems 
induced by disabling the
  iommu after it was enabled before (which would show that the patch works fine 
indeed, by allowing iommu to get disabled) - some drivers/devices may require 
iommu to be enabled in order to work, in such case disabling it would prevent 
the device to work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810328/+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 1810328] [NEW] iommu - need to effectively disable iommu if "intel_iommu=off" is passed as a kernel parameter

2019-01-02 Thread Guilherme G. Piccoli
Public bug reported:

[Impact]

* If the parameter "intel_iommu=off" is passed for the kernel in a boot
instance coming from a previously iommu-enabled kernel (like a
kexec/kdump scenario), currently Xenial kernel (4.4 version) is missing
a patch to effectively disable the iommu. As a result, the previous DMA
mappings remain and the new kernel will try to use them, which is wrong
since we don't have iommu initialized to translate the addresses.

* The upstream patch proposed to SRU here, 161b28aae165 ("iommu/vt-d:
Make sure IOMMUs are off when intel_iommu=off") fixes the issue by
effectively disabling the iommu in case it was requested.

* One important use case is in a scenario of iommu bug that is leading to a 
kernel crash; kdump naturally will have the iommu tables copied from previous 
kernel in kdump boot time, so if iommu
tables are bogus, we could inherit the bug in the kdump kernel preventing a 
successful dump.
Have the ability to disable iommu (given that the functionality is there) is 
essential.


[Test Case]

* Boot a kernel with "intel_iommu=on", and then kexec a new kernel with 
"intel_iommu=off"
parameter. A kdump test is also possible, by changing the kdump command-line to 
disable
iommu (after booting a kernel with iommu enabled) - then, induce a crash and 
the issue
will show.

* Attached to this Launchpad are 2 files with the kdump test case: 
"iommu-missing" shows
the issue in a Trusty HWE kernel - without the fix patch, we can see messages 
like

[36.489918] DMAR: DRHD: handling fault status reg 202
[36.734830] DMAR: DMAR:[DMA Read] Request device [03:00.0] fault addr 3179a000
[36.734830] DMAR:[fault reason 06] PTE Read access is not set

In our case, the rootfs couldn't be initialized since the SCSI adapter
wasn't initialized due to the DMAR failures (hpsa driver). Also,
Solarflare NIC (sfc driver) couldn't get initialized too.

The patch fixed those error messages and the rootfs was mounted (see file 
"iommu-patched").
Notice the succeeding case couldn't kdump for other reasons, not strictly 
related to the proposed patch here.


[Regression Potential]

* iommu operations are complex and subject to HW issues eventually. Having 
iommu enabled
and then boot a kernel with this component disabled is inherently a "danger" 
operation from
drivers (or any users of such mappings) point-of-view. That said, I don't see a 
potential regression for this patch, in a way currently an user can't disable 
iommu properly if it was
once enabled, and this simple patch fixes it

* Care should be taken of course to not confuse regressions with problems 
induced by disabling the
iommu after it was enabled before (which would show that the patch works fine 
indeed, by allowing iommu to get disabled) - some drivers/devices may require 
iommu to be enabled in order to work, in such case disabling it would prevent 
the device to work.

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Guilherme G. Piccoli (gpiccoli)
 Status: Confirmed


** Tags: sts

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

Title:
  iommu - need to effectively disable iommu if "intel_iommu=off" is
  passed as a kernel parameter

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  * If the parameter "intel_iommu=off" is passed for the kernel in a
  boot instance coming from a previously iommu-enabled kernel (like a
  kexec/kdump scenario), currently Xenial kernel (4.4 version) is
  missing a patch to effectively disable the iommu. As a result, the
  previous DMA mappings remain and the new kernel will try to use them,
  which is wrong since we don't have iommu initialized to translate the
  addresses.

  * The upstream patch proposed to SRU here, 161b28aae165 ("iommu/vt-d:
  Make sure IOMMUs are off when intel_iommu=off") fixes the issue by
  effectively disabling the iommu in case it was requested.

  * One important use case is in a scenario of iommu bug that is leading to a 
kernel crash; kdump naturally will have the iommu tables copied from previous 
kernel in kdump boot time, so if iommu
  tables are bogus, we could inherit the bug in the kdump kernel preventing a 
successful dump.
  Have the ability to disable iommu (given that the functionality is there) is 
essential.

  
  [Test Case]

  * Boot a kernel with "intel_iommu=on", and then kexec a new kernel with 
"intel_iommu=off"
  parameter. A kdump test is also possible, by changing the kdump command-line 
to disable
  iommu (after booting a kernel with iommu enabled) - then, induce a crash and 
the issue
  will show.

  * Attached to this Launchpad are 2 files with the kdump test case: 
"iommu-missing" shows
  the issue in a Trusty HWE kernel - without the fix patch, we can see messages 
like

  [36.489918] DMAR: DRHD: handling fault status reg 202
  [36.734830] DMAR: DMAR:[DMA Read] Request device [03:00.0] fau

[Kernel-packages] [Bug 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

2019-01-02 Thread Eugene Kosogin
I've written to support center. They said that there is no guarantee
that device can work with OS which differs from windows 10. They are the
best.

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

Title:
  CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

Status in linux package in Ubuntu:
  Incomplete
Status in thermald package in Ubuntu:
  New

Bug description:
  After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
  GPU fans suddenly go full throttle. It doesn't seem to depend on
  temperature, could happen when 32 °C reported, sometimes the laptop
  can work for day or two without this issue, but eventually it happens.
  The only way to stop fans is to power off the laptop, power on (fans
  go 100% at this point again), power off during BIOS splash screen and
  power on again. Seems to happen more often after waking up from a
  sleep.

  Things tried:

  Upgrading BIOS to latest available on ASUS site to the date of
  writing. No change.

  asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
  both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
  does not seem to control it and does not prevent going full throttle.

  4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
  issue.

  Userspace fan control software (https://github.com/hirschmann/nbfc).
  Can control speed of both fans to the point where they go full
  throttle, after that has no effect on them.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  whale  3068 F pulseaudio
   /dev/snd/controlC0:  whale  3068 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=ada9b595-bbf2-40a3-8575-5908492bb969
  InstallationDate: Installed on 2014-10-20 (1333 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac 
(20140722.2)
  MachineType: ASUSTeK COMPUTER INC. G752VT
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash 
acpi_backlight=vendor 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 audio cdrom dip docker lpadmin plugdev sambashare sudo tty 
video
  _MarkForUpload: True
  dmi.bios.date: 06/29/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VT.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VT
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


Re: [Kernel-packages] [Bug 1810130] ic2-HTIX5288

2019-01-02 Thread Thomas Müllrt
-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1810130

Title:
  ic2-HTIX5288

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  touchpad not working

  Ubuntu Disco Dingo (development branch)

  WINBOOK 13

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  docmint2172 F pulseaudio
   /dev/snd/controlC1:  docmint2172 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 31 00:55:26 2018
  InstallationDate: Installed on 2018-12-30 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181230)
  MachineType: AXDIA International GmbH WINBOOK 13
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=ea66942b-3d65-4c18-a99e-d02e31358a42 ro recovery nomodeset 
i8042.nomux=1 i8042.reset
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2017
  dmi.bios.vendor: WINBOOK 13
  dmi.bios.version: 1.6
  dmi.board.asset.tag: Default string
  dmi.board.name: K132
  dmi.board.vendor: AXDIA International GmbH
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnWINBOOK13:bvr1.6:bd11/27/2017:svnAXDIAInternationalGmbH:pnWINBOOK13:pvrDefaultstring:rvnAXDIAInternationalGmbH:rnK132:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Notebook
  dmi.product.name: WINBOOK 13
  dmi.product.sku: WINBOOK13-K132-02
  dmi.product.version: Default string
  dmi.sys.vendor: AXDIA International GmbH

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

2019-01-02 Thread Thomas Müllrt
kernel-bug-exists-upstream

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

Title:
  ic2-HTIX5288

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  touchpad not working

  Ubuntu Disco Dingo (development branch)

  WINBOOK 13

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  docmint2172 F pulseaudio
   /dev/snd/controlC1:  docmint2172 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 31 00:55:26 2018
  InstallationDate: Installed on 2018-12-30 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181230)
  MachineType: AXDIA International GmbH WINBOOK 13
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=ea66942b-3d65-4c18-a99e-d02e31358a42 ro recovery nomodeset 
i8042.nomux=1 i8042.reset
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2017
  dmi.bios.vendor: WINBOOK 13
  dmi.bios.version: 1.6
  dmi.board.asset.tag: Default string
  dmi.board.name: K132
  dmi.board.vendor: AXDIA International GmbH
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnWINBOOK13:bvr1.6:bd11/27/2017:svnAXDIAInternationalGmbH:pnWINBOOK13:pvrDefaultstring:rvnAXDIAInternationalGmbH:rnK132:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Notebook
  dmi.product.name: WINBOOK 13
  dmi.product.sku: WINBOOK13-K132-02
  dmi.product.version: Default string
  dmi.sys.vendor: AXDIA International GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810130/+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 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370

2019-01-02 Thread kao
Kai Heng,

Should I keep btusb autosuspend disabled (I have been using it as workaround) 
while testing?
And could you write few words how missing bluetooth is related to advertising 
event?

Thank you

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

Title:
  Missing wifi and bluetooth after sleep on XPS 9370

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  I have XPS9370 with self-installed Ubuntu 18.10 (not project sputnik) with 
Killer 1435 wireless module.
  And sometimes I find wifi and bluetooth missing after sleep. I cannot exactly 
define preconditions, but it seems there are following steps to reproduce the 
issue
  1. Connect something via bluetooth  (I use bluetooth headset)
  2. Send laptop to sleep
  3. Wake it and find wifi and bluetooth missing.

  I have to mention that I have also been experienced bluetooth only
  missing, but it somehow transformed to the issue with both wireless
  devices.

  Dmesg after waking up with the issue attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kao2362 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-09-22 (33 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 012: ID 0489:e0a2 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=34230cbd-d3d2-4cb8-855a-307883bc35ea ro quiet splash 
mem_sleep_default=deep video=1920x1080 usbcore.dyndbg=+p vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0VM1FG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0VM1FG:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1799988/+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 1777863] Re: [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit

2019-01-02 Thread Lubomir Stanko
I've updated the kernel to v4.20:
Linux citadel 4.20.0-042000-generic #201812232030 SMP Mon Dec 24 01:32:58 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

So far I've got no problem with docking and undocking. OS recognizes
both monitors with no problem.

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

Title:
  [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI
  BUF C idle bit

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System reboot. This could be related to putting the NB back into the docking 
station.
  Search for [ cut here ] to find the final error 
message before reboot.

  Linux mymachine4 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16
  UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Using vrefresh ranges from config file
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Printing DDC gathered Modelines:
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "1920x1080"x0.0  148.50  1920 2008 2052 2200  1080 1084 1089 1125 
+hsync +vsync (67.5 kHz eP)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync 
(37.9 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync 
(37.5 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync 
(31.5 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync 
(31.5 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 
+hsync +vsync (80.0 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync 
+vsync (60.0 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync 
-vsync (48.4 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync 
(46.9 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync 
+vsync (67.5 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 
+hsync +vsync (64.0 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "1600x900"x60.0  119.00  1600 1696 1864 2128  900 901 904 932 -hsync 
+vsync (55.9 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "1920x1080"x60.0  172.80  1920 2040 2248 2576  1080 1081 1084 1118 
-hsync +vsync (67.1 kHz e)
  Jun 20 12:05:18 mymachine kernel: [drm:intel_wait_ddi_buf_idle [i915]] 
*ERROR* Timeout waiting for DDI BUF C idle bit
  Jun 20 12:05:18 mymachine kernel: [ cut here ]
  Jun 20 12:05:18 mymachine kernel: vblank wait timed out on crtc 2
  Jun 20 12:05:18 mymachine kernel: WARNING: CPU: 2 PID: 4445 at 
/build/linux-uT8zSN/linux-4.15.0/drivers/gpu/drm/drm_vblank.c:1073 
drm_wait_one_vblank+0x181/0x190 [drm]
  Jun 20 12:05:18 mymachine kernel: Modules linked in: msr rfcomm ccm veth 
nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo br_netfilter bridge stp llc 
overlay thunderbolt cmac bnep btusb btrtl btbcm uvcvideo 
  Jun 20 12:05:18 mymachine kernel:  intel_cstate mac80211 intel_rapl_perf 
snd_compress ac97_bus snd_pcm_dmaengine snd_seq_midi snd_seq_midi_event 
snd_hda_intel snd_rawmidi snd_hda_codec snd_hda_core snd_hwdep i
  Jun 20 12:05:18 mymachine kernel:  pps_core drm nvme_core wmi video
  Jun 20 12:05:18 mymachine kernel: CPU: 2 PID: 4445 Comm: Xorg Tainted: G  
  W4.15.0-23-generic #25-Ubuntu
  Jun 20 12:05:18 mymachine kernel: Hardware name: LENOVO 
20HGS30X00/20HGS30X00, BIOS N1WET34W (1.13 ) 06/26/2017
  Jun 20 12:05:18 mymachine kernel: RIP: 0010:drm_wait_one_vblank+0x181/0x190 
[drm]
  Jun 20 12:05:18 mymachine kernel: RSP: 0018:a32ac3b83a68 EFLAGS: 00010282
  Jun 20 12:05:18 mymachine kernel: RAX:  RBX: 8c5175a38000 
RCX: 0006
  Jun 20 12:05:18 mymachine kernel: RDX: 0007 RSI: 0096 
RDI: 8c519e516490
  Jun 20 12:05:1

[Kernel-packages] [Bug 1783267] Re: linux-modules-extra breaks virtualbox guest modules

2019-01-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: virtualbox-hwe (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/1783267

Title:
  linux-modules-extra breaks virtualbox guest modules

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

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
 

[Kernel-packages] [Bug 132002] Re: libportaudio packaging very confusing

2019-01-02 Thread Robin
As suggested in #3 above, this solution may work:

The clean solution to this issue is to install libjack-jackd2-dev
*before* installing portaudio19-dev.


I have a note on this, available on request.

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

Title:
  libportaudio packaging very confusing

Status in portaudio19 package in Ubuntu:
  Opinion

Bug description:
  Installing portaudio 19 is very confusing.  I am trying to compile an
  application which uses it, as well as the CPP bindings which are
  contained in libportaudiocpp0.

  1) Previously, PortAudio 18 dev files were installed using the package 
libportaudio-dev.  So far so good.
  2) So libportaudio0 goes with libportaudio-dev and libportaudio-doc, for V18.
  3) To install V19 and the cpp bindings, first I tried installing 
libportaudiocpp0.
  4) Apparently libportaudiocpp0 is not intended for libportaudio0, but for 
portaudio19-dev.
  5) portaudio19-dev is the development files for libportaudio2.  2?  Why 
couldn't this be 19?
  6) The dev files for libportaudiocpp0 are contained in portaudio19-dev.  I 
spent some time looking for a package called libportaudiocpp0-dev, but was very 
confused for a while.

  So anyways, it finally become apparent that all I had to do was install 
portaudio19-dev and libportaudiocpp0.
  I just wanted to state my general confusion here at the package naming 
scheme...
  At the very least, why not put the cpp binding dev files in 
libportaudiocpp0-dev?  And if I install libportaudiocpp0, it should detect the 
dependancy on libportaudio2, instead of allowing me to compile programs with an 
incompatible version of the library.
  It is very non-obvious which package to install for V18 or V19.  I had to 
issue several "apt-cache show" commands before figuring it out.
  Lastly, V18 for some reason is mutually exclusive with V19.  This is a bad 
thing, because some older applications may require V18.  There is a perfectly 
good way to deal with this problem, by using version numbers in the file names. 
 (For example, I currently have both libglib-1.2 and libglib-2.0 installed at 
the same time.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/portaudio19/+bug/132002/+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 1810238] Lsusb.txt

2019-01-02 Thread rpetrusevski
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1810238/+attachment/5226370/+files/Lsusb.txt

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

Title:
  4.15.0-43 back screen of death :)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  crashes the whole system when playing a game (I have nvidia). Rolled back to 
4.15.0-42 everything works fine.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rp 4614 F pulseaudio
   /dev/snd/controlC1:  rp 4614 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=3ee4cc45-4d22-42ae-abe7-692ff96391c3
  InstallationDate: Installed on 2018-07-03 (183 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  MachineType: LENOVO ThinkServer TS440
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=8dee5144-332c-4f2b-9dee-4cdd173451f9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  tessa
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev roccat sambashare sudo 
ubridge
  _MarkForUpload: True
  dmi.bios.date: 04/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FBKTCEAUS
  dmi.board.name: ThinkServer TS440
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrFBKTCEAUS:bd04/10/2017:svnLENOVO:pnThinkServerTS440:pvr70AQ0009UX:rvnLENOVO:rnThinkServerTS440:rvrNotDefined:cvnLENOVO:ct7:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: ThinkServer TS440
  dmi.product.version: 70AQ0009UX
  dmi.sys.vendor: LENOVO

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

2019-01-02 Thread rpetrusevski
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1810238/+attachment/5226376/+files/PulseList.txt

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

Title:
  4.15.0-43 back screen of death :)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  crashes the whole system when playing a game (I have nvidia). Rolled back to 
4.15.0-42 everything works fine.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rp 4614 F pulseaudio
   /dev/snd/controlC1:  rp 4614 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=3ee4cc45-4d22-42ae-abe7-692ff96391c3
  InstallationDate: Installed on 2018-07-03 (183 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  MachineType: LENOVO ThinkServer TS440
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=8dee5144-332c-4f2b-9dee-4cdd173451f9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  tessa
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev roccat sambashare sudo 
ubridge
  _MarkForUpload: True
  dmi.bios.date: 04/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FBKTCEAUS
  dmi.board.name: ThinkServer TS440
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrFBKTCEAUS:bd04/10/2017:svnLENOVO:pnThinkServerTS440:pvr70AQ0009UX:rvnLENOVO:rnThinkServerTS440:rvrNotDefined:cvnLENOVO:ct7:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: ThinkServer TS440
  dmi.product.version: 70AQ0009UX
  dmi.sys.vendor: LENOVO

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

2019-01-02 Thread rpetrusevski
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1810238/+attachment/5226368/+files/IwConfig.txt

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

Title:
  4.15.0-43 back screen of death :)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  crashes the whole system when playing a game (I have nvidia). Rolled back to 
4.15.0-42 everything works fine.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rp 4614 F pulseaudio
   /dev/snd/controlC1:  rp 4614 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=3ee4cc45-4d22-42ae-abe7-692ff96391c3
  InstallationDate: Installed on 2018-07-03 (183 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  MachineType: LENOVO ThinkServer TS440
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=8dee5144-332c-4f2b-9dee-4cdd173451f9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  tessa
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev roccat sambashare sudo 
ubridge
  _MarkForUpload: True
  dmi.bios.date: 04/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FBKTCEAUS
  dmi.board.name: ThinkServer TS440
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrFBKTCEAUS:bd04/10/2017:svnLENOVO:pnThinkServerTS440:pvr70AQ0009UX:rvnLENOVO:rnThinkServerTS440:rvrNotDefined:cvnLENOVO:ct7:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: ThinkServer TS440
  dmi.product.version: 70AQ0009UX
  dmi.sys.vendor: LENOVO

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

2019-01-02 Thread rpetrusevski
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1810238/+attachment/5226373/+files/ProcEnviron.txt

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

Title:
  4.15.0-43 back screen of death :)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  crashes the whole system when playing a game (I have nvidia). Rolled back to 
4.15.0-42 everything works fine.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rp 4614 F pulseaudio
   /dev/snd/controlC1:  rp 4614 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=3ee4cc45-4d22-42ae-abe7-692ff96391c3
  InstallationDate: Installed on 2018-07-03 (183 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  MachineType: LENOVO ThinkServer TS440
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=8dee5144-332c-4f2b-9dee-4cdd173451f9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  tessa
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev roccat sambashare sudo 
ubridge
  _MarkForUpload: True
  dmi.bios.date: 04/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FBKTCEAUS
  dmi.board.name: ThinkServer TS440
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrFBKTCEAUS:bd04/10/2017:svnLENOVO:pnThinkServerTS440:pvr70AQ0009UX:rvnLENOVO:rnThinkServerTS440:rvrNotDefined:cvnLENOVO:ct7:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: ThinkServer TS440
  dmi.product.version: 70AQ0009UX
  dmi.sys.vendor: LENOVO

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

2019-01-02 Thread rpetrusevski
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1810238/+attachment/5226378/+files/WifiSyslog.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/1810238

Title:
  4.15.0-43 back screen of death :)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  crashes the whole system when playing a game (I have nvidia). Rolled back to 
4.15.0-42 everything works fine.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rp 4614 F pulseaudio
   /dev/snd/controlC1:  rp 4614 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=3ee4cc45-4d22-42ae-abe7-692ff96391c3
  InstallationDate: Installed on 2018-07-03 (183 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  MachineType: LENOVO ThinkServer TS440
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=8dee5144-332c-4f2b-9dee-4cdd173451f9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  tessa
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev roccat sambashare sudo 
ubridge
  _MarkForUpload: True
  dmi.bios.date: 04/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FBKTCEAUS
  dmi.board.name: ThinkServer TS440
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrFBKTCEAUS:bd04/10/2017:svnLENOVO:pnThinkServerTS440:pvr70AQ0009UX:rvnLENOVO:rnThinkServerTS440:rvrNotDefined:cvnLENOVO:ct7:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: ThinkServer TS440
  dmi.product.version: 70AQ0009UX
  dmi.sys.vendor: LENOVO

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

2019-01-02 Thread rpetrusevski
apport information

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

Title:
  4.15.0-43 back screen of death :)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  crashes the whole system when playing a game (I have nvidia). Rolled back to 
4.15.0-42 everything works fine.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rp 4614 F pulseaudio
   /dev/snd/controlC1:  rp 4614 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=3ee4cc45-4d22-42ae-abe7-692ff96391c3
  InstallationDate: Installed on 2018-07-03 (183 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  MachineType: LENOVO ThinkServer TS440
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=8dee5144-332c-4f2b-9dee-4cdd173451f9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  tessa
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev roccat sambashare sudo 
ubridge
  _MarkForUpload: True
  dmi.bios.date: 04/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FBKTCEAUS
  dmi.board.name: ThinkServer TS440
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrFBKTCEAUS:bd04/10/2017:svnLENOVO:pnThinkServerTS440:pvr70AQ0009UX:rvnLENOVO:rnThinkServerTS440:rvrNotDefined:cvnLENOVO:ct7:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: ThinkServer TS440
  dmi.product.version: 70AQ0009UX
  dmi.sys.vendor: LENOVO

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

2019-01-02 Thread rpetrusevski
apport information

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

Title:
  4.15.0-43 back screen of death :)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  crashes the whole system when playing a game (I have nvidia). Rolled back to 
4.15.0-42 everything works fine.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rp 4614 F pulseaudio
   /dev/snd/controlC1:  rp 4614 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=3ee4cc45-4d22-42ae-abe7-692ff96391c3
  InstallationDate: Installed on 2018-07-03 (183 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  MachineType: LENOVO ThinkServer TS440
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=8dee5144-332c-4f2b-9dee-4cdd173451f9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  tessa
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev roccat sambashare sudo 
ubridge
  _MarkForUpload: True
  dmi.bios.date: 04/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FBKTCEAUS
  dmi.board.name: ThinkServer TS440
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrFBKTCEAUS:bd04/10/2017:svnLENOVO:pnThinkServerTS440:pvr70AQ0009UX:rvnLENOVO:rnThinkServerTS440:rvrNotDefined:cvnLENOVO:ct7:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: ThinkServer TS440
  dmi.product.version: 70AQ0009UX
  dmi.sys.vendor: LENOVO

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

2019-01-02 Thread rpetrusevski
apport information

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

Title:
  4.15.0-43 back screen of death :)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  crashes the whole system when playing a game (I have nvidia). Rolled back to 
4.15.0-42 everything works fine.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rp 4614 F pulseaudio
   /dev/snd/controlC1:  rp 4614 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=3ee4cc45-4d22-42ae-abe7-692ff96391c3
  InstallationDate: Installed on 2018-07-03 (183 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  MachineType: LENOVO ThinkServer TS440
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=8dee5144-332c-4f2b-9dee-4cdd173451f9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  tessa
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev roccat sambashare sudo 
ubridge
  _MarkForUpload: True
  dmi.bios.date: 04/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FBKTCEAUS
  dmi.board.name: ThinkServer TS440
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrFBKTCEAUS:bd04/10/2017:svnLENOVO:pnThinkServerTS440:pvr70AQ0009UX:rvnLENOVO:rnThinkServerTS440:rvrNotDefined:cvnLENOVO:ct7:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: ThinkServer TS440
  dmi.product.version: 70AQ0009UX
  dmi.sys.vendor: LENOVO

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

2019-01-02 Thread rpetrusevski
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1810238/+attachment/5226377/+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/1810238

Title:
  4.15.0-43 back screen of death :)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  crashes the whole system when playing a game (I have nvidia). Rolled back to 
4.15.0-42 everything works fine.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rp 4614 F pulseaudio
   /dev/snd/controlC1:  rp 4614 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=3ee4cc45-4d22-42ae-abe7-692ff96391c3
  InstallationDate: Installed on 2018-07-03 (183 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  MachineType: LENOVO ThinkServer TS440
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=8dee5144-332c-4f2b-9dee-4cdd173451f9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  tessa
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev roccat sambashare sudo 
ubridge
  _MarkForUpload: True
  dmi.bios.date: 04/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FBKTCEAUS
  dmi.board.name: ThinkServer TS440
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrFBKTCEAUS:bd04/10/2017:svnLENOVO:pnThinkServerTS440:pvr70AQ0009UX:rvnLENOVO:rnThinkServerTS440:rvrNotDefined:cvnLENOVO:ct7:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: ThinkServer TS440
  dmi.product.version: 70AQ0009UX
  dmi.sys.vendor: LENOVO

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

2019-01-02 Thread rpetrusevski
apport information

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

Title:
  4.15.0-43 back screen of death :)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  crashes the whole system when playing a game (I have nvidia). Rolled back to 
4.15.0-42 everything works fine.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rp 4614 F pulseaudio
   /dev/snd/controlC1:  rp 4614 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=3ee4cc45-4d22-42ae-abe7-692ff96391c3
  InstallationDate: Installed on 2018-07-03 (183 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  MachineType: LENOVO ThinkServer TS440
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=8dee5144-332c-4f2b-9dee-4cdd173451f9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  tessa
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev roccat sambashare sudo 
ubridge
  _MarkForUpload: True
  dmi.bios.date: 04/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FBKTCEAUS
  dmi.board.name: ThinkServer TS440
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrFBKTCEAUS:bd04/10/2017:svnLENOVO:pnThinkServerTS440:pvr70AQ0009UX:rvnLENOVO:rnThinkServerTS440:rvrNotDefined:cvnLENOVO:ct7:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: ThinkServer TS440
  dmi.product.version: 70AQ0009UX
  dmi.sys.vendor: LENOVO

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

2019-01-02 Thread rpetrusevski
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1810238/+attachment/5226366/+files/CRDA.txt

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

Title:
  4.15.0-43 back screen of death :)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  crashes the whole system when playing a game (I have nvidia). Rolled back to 
4.15.0-42 everything works fine.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rp 4614 F pulseaudio
   /dev/snd/controlC1:  rp 4614 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=3ee4cc45-4d22-42ae-abe7-692ff96391c3
  InstallationDate: Installed on 2018-07-03 (183 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  MachineType: LENOVO ThinkServer TS440
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=8dee5144-332c-4f2b-9dee-4cdd173451f9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  tessa
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev roccat sambashare sudo 
ubridge
  _MarkForUpload: True
  dmi.bios.date: 04/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FBKTCEAUS
  dmi.board.name: ThinkServer TS440
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrFBKTCEAUS:bd04/10/2017:svnLENOVO:pnThinkServerTS440:pvr70AQ0009UX:rvnLENOVO:rnThinkServerTS440:rvrNotDefined:cvnLENOVO:ct7:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: ThinkServer TS440
  dmi.product.version: 70AQ0009UX
  dmi.sys.vendor: LENOVO

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

2019-01-02 Thread rpetrusevski
apport information

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

Title:
  4.15.0-43 back screen of death :)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  crashes the whole system when playing a game (I have nvidia). Rolled back to 
4.15.0-42 everything works fine.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rp 4614 F pulseaudio
   /dev/snd/controlC1:  rp 4614 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=3ee4cc45-4d22-42ae-abe7-692ff96391c3
  InstallationDate: Installed on 2018-07-03 (183 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  MachineType: LENOVO ThinkServer TS440
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=8dee5144-332c-4f2b-9dee-4cdd173451f9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  tessa
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev roccat sambashare sudo 
ubridge
  _MarkForUpload: True
  dmi.bios.date: 04/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FBKTCEAUS
  dmi.board.name: ThinkServer TS440
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrFBKTCEAUS:bd04/10/2017:svnLENOVO:pnThinkServerTS440:pvr70AQ0009UX:rvnLENOVO:rnThinkServerTS440:rvrNotDefined:cvnLENOVO:ct7:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: ThinkServer TS440
  dmi.product.version: 70AQ0009UX
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810238/+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 1810238] Re: 4.15.0-43 back screen of death :)

2019-01-02 Thread rpetrusevski
I did run the command, but at the moment I am on 4.15.0-42, not sure
that this is what you need.

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

Title:
  4.15.0-43 back screen of death :)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  crashes the whole system when playing a game (I have nvidia). Rolled back to 
4.15.0-42 everything works fine.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rp 4614 F pulseaudio
   /dev/snd/controlC1:  rp 4614 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=3ee4cc45-4d22-42ae-abe7-692ff96391c3
  InstallationDate: Installed on 2018-07-03 (183 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  MachineType: LENOVO ThinkServer TS440
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=8dee5144-332c-4f2b-9dee-4cdd173451f9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  tessa
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev roccat sambashare sudo 
ubridge
  _MarkForUpload: True
  dmi.bios.date: 04/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FBKTCEAUS
  dmi.board.name: ThinkServer TS440
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrFBKTCEAUS:bd04/10/2017:svnLENOVO:pnThinkServerTS440:pvr70AQ0009UX:rvnLENOVO:rnThinkServerTS440:rvrNotDefined:cvnLENOVO:ct7:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: ThinkServer TS440
  dmi.product.version: 70AQ0009UX
  dmi.sys.vendor: LENOVO

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

2019-01-02 Thread rpetrusevski
apport information

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

Title:
  4.15.0-43 back screen of death :)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  crashes the whole system when playing a game (I have nvidia). Rolled back to 
4.15.0-42 everything works fine.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rp 4614 F pulseaudio
   /dev/snd/controlC1:  rp 4614 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=3ee4cc45-4d22-42ae-abe7-692ff96391c3
  InstallationDate: Installed on 2018-07-03 (183 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  MachineType: LENOVO ThinkServer TS440
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=8dee5144-332c-4f2b-9dee-4cdd173451f9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  tessa
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev roccat sambashare sudo 
ubridge
  _MarkForUpload: True
  dmi.bios.date: 04/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FBKTCEAUS
  dmi.board.name: ThinkServer TS440
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrFBKTCEAUS:bd04/10/2017:svnLENOVO:pnThinkServerTS440:pvr70AQ0009UX:rvnLENOVO:rnThinkServerTS440:rvrNotDefined:cvnLENOVO:ct7:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: ThinkServer TS440
  dmi.product.version: 70AQ0009UX
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810238/+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 1810238] Re: 4.15.0-43 back screen of death :)

2019-01-02 Thread rpetrusevski
apport information

** Tags added: apport-collected tessa

** Description changed:

- crashes the whole system when playing a game (I have nvidia). Rolled
- back to 4.15.0-42 everything works fine.
+ crashes the whole system when playing a game (I have nvidia). Rolled back to 
4.15.0-42 everything works fine.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.5
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  rp 4614 F pulseaudio
+  /dev/snd/controlC1:  rp 4614 F pulseaudio
+ CurrentDesktop: X-Cinnamon
+ DistroRelease: Linux Mint 19.1
+ EcryptfsInUse: Yes
+ HibernationDevice: RESUME=UUID=3ee4cc45-4d22-42ae-abe7-692ff96391c3
+ InstallationDate: Installed on 2018-07-03 (183 days ago)
+ InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
+ MachineType: LENOVO ThinkServer TS440
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcFB: 0 EFI VGA
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=8dee5144-332c-4f2b-9dee-4cdd173451f9 ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-42-generic N/A
+  linux-backports-modules-4.15.0-42-generic  N/A
+  linux-firmware 1.173.2
+ RfKill:
+  0: hci0: Bluetooth
+   Soft blocked: no
+   Hard blocked: no
+ Tags:  tessa
+ Uname: Linux 4.15.0-42-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip libvirt lpadmin plugdev roccat sambashare sudo 
ubridge
+ _MarkForUpload: True
+ dmi.bios.date: 04/10/2017
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: FBKTCEAUS
+ dmi.board.name: ThinkServer TS440
+ dmi.board.vendor: LENOVO
+ dmi.board.version: Not Defined
+ dmi.chassis.type: 7
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: To Be Filled By O.E.M.
+ dmi.modalias: 
dmi:bvnLENOVO:bvrFBKTCEAUS:bd04/10/2017:svnLENOVO:pnThinkServerTS440:pvr70AQ0009UX:rvnLENOVO:rnThinkServerTS440:rvrNotDefined:cvnLENOVO:ct7:cvrToBeFilledByO.E.M.:
+ dmi.product.family: To be filled by O.E.M.
+ dmi.product.name: ThinkServer TS440
+ dmi.product.version: 70AQ0009UX
+ dmi.sys.vendor: LENOVO

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1810238/+attachment/5226365/+files/AlsaInfo.txt

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

Title:
  4.15.0-43 back screen of death :)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  crashes the whole system when playing a game (I have nvidia). Rolled back to 
4.15.0-42 everything works fine.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rp 4614 F pulseaudio
   /dev/snd/controlC1:  rp 4614 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=3ee4cc45-4d22-42ae-abe7-692ff96391c3
  InstallationDate: Installed on 2018-07-03 (183 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  MachineType: LENOVO ThinkServer TS440
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=8dee5144-332c-4f2b-9dee-4cdd173451f9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  tessa
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev roccat sambashare sudo 
ubridge
  _MarkForUpload: True
  dmi.bios.date: 04/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FBKTCEAUS
  dmi.board.name: ThinkServer TS440
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrFBKTCEAUS:bd04/10/2017:svnLENOVO:pnThinkServerTS440:pvr70AQ0009UX:rvnLENOVO:rnThinkServerTS440:rvrNotDefined:cvnLENOVO:ct7:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: ThinkServer TS440
  dmi.product.version: 70AQ0009UX
  dmi.sys.vendor: LENOVO

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

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

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

2019-01-02 Thread Aaron
apport information

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

Title:
  Kernel 4.15.0-43 crashes laptop on boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading kernel from 4.15.0-33 to 4.15.0-43 my laptop no longer
  boots, it crashes when reaching the stage where it says Reached Target
  Encrypted Volumes. Have reverted to 4.15.0-33 in the meantime. Is this
  something that can be rectified?

  Using an ASUS XM553MA laptop.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaron  1222 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  InstallationDate: Installed on 2018-12-06 (27 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X553MA
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=7fdad478-0ec8-4191-9c7e-22f837dc7af3 ro
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  tessa
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X553MA.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X553MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX553MA.211:bd04/10/2015:svnASUSTeKCOMPUTERINC.:pnX553MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX553MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X553MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

2019-01-02 Thread Aaron
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1810210/+attachment/5226328/+files/IwConfig.txt

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

Title:
  Kernel 4.15.0-43 crashes laptop on boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading kernel from 4.15.0-33 to 4.15.0-43 my laptop no longer
  boots, it crashes when reaching the stage where it says Reached Target
  Encrypted Volumes. Have reverted to 4.15.0-33 in the meantime. Is this
  something that can be rectified?

  Using an ASUS XM553MA laptop.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaron  1222 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  InstallationDate: Installed on 2018-12-06 (27 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X553MA
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=7fdad478-0ec8-4191-9c7e-22f837dc7af3 ro
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  tessa
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X553MA.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X553MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX553MA.211:bd04/10/2015:svnASUSTeKCOMPUTERINC.:pnX553MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX553MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X553MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

2019-01-02 Thread Aaron
apport information

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

Title:
  Kernel 4.15.0-43 crashes laptop on boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading kernel from 4.15.0-33 to 4.15.0-43 my laptop no longer
  boots, it crashes when reaching the stage where it says Reached Target
  Encrypted Volumes. Have reverted to 4.15.0-33 in the meantime. Is this
  something that can be rectified?

  Using an ASUS XM553MA laptop.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaron  1222 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  InstallationDate: Installed on 2018-12-06 (27 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X553MA
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=7fdad478-0ec8-4191-9c7e-22f837dc7af3 ro
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  tessa
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X553MA.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X553MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX553MA.211:bd04/10/2015:svnASUSTeKCOMPUTERINC.:pnX553MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX553MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X553MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

2019-01-02 Thread Aaron
apport information

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

Title:
  Kernel 4.15.0-43 crashes laptop on boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading kernel from 4.15.0-33 to 4.15.0-43 my laptop no longer
  boots, it crashes when reaching the stage where it says Reached Target
  Encrypted Volumes. Have reverted to 4.15.0-33 in the meantime. Is this
  something that can be rectified?

  Using an ASUS XM553MA laptop.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaron  1222 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  InstallationDate: Installed on 2018-12-06 (27 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X553MA
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=7fdad478-0ec8-4191-9c7e-22f837dc7af3 ro
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  tessa
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X553MA.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X553MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX553MA.211:bd04/10/2015:svnASUSTeKCOMPUTERINC.:pnX553MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX553MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X553MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

2019-01-02 Thread Aaron
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1810210/+attachment/5226326/+files/CRDA.txt

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

Title:
  Kernel 4.15.0-43 crashes laptop on boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading kernel from 4.15.0-33 to 4.15.0-43 my laptop no longer
  boots, it crashes when reaching the stage where it says Reached Target
  Encrypted Volumes. Have reverted to 4.15.0-33 in the meantime. Is this
  something that can be rectified?

  Using an ASUS XM553MA laptop.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaron  1222 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  InstallationDate: Installed on 2018-12-06 (27 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X553MA
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=7fdad478-0ec8-4191-9c7e-22f837dc7af3 ro
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  tessa
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X553MA.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X553MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX553MA.211:bd04/10/2015:svnASUSTeKCOMPUTERINC.:pnX553MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX553MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X553MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

2019-01-02 Thread Aaron
apport information

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

Title:
  Kernel 4.15.0-43 crashes laptop on boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading kernel from 4.15.0-33 to 4.15.0-43 my laptop no longer
  boots, it crashes when reaching the stage where it says Reached Target
  Encrypted Volumes. Have reverted to 4.15.0-33 in the meantime. Is this
  something that can be rectified?

  Using an ASUS XM553MA laptop.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaron  1222 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  InstallationDate: Installed on 2018-12-06 (27 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X553MA
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=7fdad478-0ec8-4191-9c7e-22f837dc7af3 ro
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  tessa
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X553MA.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X553MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX553MA.211:bd04/10/2015:svnASUSTeKCOMPUTERINC.:pnX553MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX553MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X553MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

2019-01-02 Thread Aaron
apport information

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

Title:
  Kernel 4.15.0-43 crashes laptop on boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading kernel from 4.15.0-33 to 4.15.0-43 my laptop no longer
  boots, it crashes when reaching the stage where it says Reached Target
  Encrypted Volumes. Have reverted to 4.15.0-33 in the meantime. Is this
  something that can be rectified?

  Using an ASUS XM553MA laptop.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaron  1222 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  InstallationDate: Installed on 2018-12-06 (27 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X553MA
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=7fdad478-0ec8-4191-9c7e-22f837dc7af3 ro
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  tessa
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X553MA.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X553MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX553MA.211:bd04/10/2015:svnASUSTeKCOMPUTERINC.:pnX553MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX553MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X553MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

2019-01-02 Thread Aaron
apport information

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

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

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

Title:
  Kernel 4.15.0-43 crashes laptop on boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading kernel from 4.15.0-33 to 4.15.0-43 my laptop no longer
  boots, it crashes when reaching the stage where it says Reached Target
  Encrypted Volumes. Have reverted to 4.15.0-33 in the meantime. Is this
  something that can be rectified?

  Using an ASUS XM553MA laptop.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaron  1222 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  InstallationDate: Installed on 2018-12-06 (27 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X553MA
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=7fdad478-0ec8-4191-9c7e-22f837dc7af3 ro
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  tessa
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X553MA.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X553MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX553MA.211:bd04/10/2015:svnASUSTeKCOMPUTERINC.:pnX553MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX553MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X553MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

2019-01-02 Thread Aaron
apport information

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

Title:
  Kernel 4.15.0-43 crashes laptop on boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading kernel from 4.15.0-33 to 4.15.0-43 my laptop no longer
  boots, it crashes when reaching the stage where it says Reached Target
  Encrypted Volumes. Have reverted to 4.15.0-33 in the meantime. Is this
  something that can be rectified?

  Using an ASUS XM553MA laptop.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaron  1222 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  InstallationDate: Installed on 2018-12-06 (27 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X553MA
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=7fdad478-0ec8-4191-9c7e-22f837dc7af3 ro
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  tessa
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X553MA.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X553MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX553MA.211:bd04/10/2015:svnASUSTeKCOMPUTERINC.:pnX553MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX553MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X553MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810210/+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 1810210] Re: Kernel 4.15.0-43 crashes laptop on boot

2019-01-02 Thread Aaron
If this is of any help, the laptop will not boot with any kernel from
4.15.0-34 upwards. 4.15.0-33 seems to be the most recent useable kernel
that my laptop will work with.

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

Title:
  Kernel 4.15.0-43 crashes laptop on boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading kernel from 4.15.0-33 to 4.15.0-43 my laptop no longer
  boots, it crashes when reaching the stage where it says Reached Target
  Encrypted Volumes. Have reverted to 4.15.0-33 in the meantime. Is this
  something that can be rectified?

  Using an ASUS XM553MA laptop.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaron  1222 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  InstallationDate: Installed on 2018-12-06 (27 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X553MA
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=7fdad478-0ec8-4191-9c7e-22f837dc7af3 ro
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  tessa
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X553MA.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X553MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX553MA.211:bd04/10/2015:svnASUSTeKCOMPUTERINC.:pnX553MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX553MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X553MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

2019-01-02 Thread Aaron
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1810210/+attachment/5226335/+files/PulseList.txt

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

Title:
  Kernel 4.15.0-43 crashes laptop on boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading kernel from 4.15.0-33 to 4.15.0-43 my laptop no longer
  boots, it crashes when reaching the stage where it says Reached Target
  Encrypted Volumes. Have reverted to 4.15.0-33 in the meantime. Is this
  something that can be rectified?

  Using an ASUS XM553MA laptop.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaron  1222 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  InstallationDate: Installed on 2018-12-06 (27 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X553MA
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=7fdad478-0ec8-4191-9c7e-22f837dc7af3 ro
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  tessa
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X553MA.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X553MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX553MA.211:bd04/10/2015:svnASUSTeKCOMPUTERINC.:pnX553MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX553MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X553MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

2019-01-02 Thread Aaron
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1810210/+attachment/5226336/+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/1810210

Title:
  Kernel 4.15.0-43 crashes laptop on boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading kernel from 4.15.0-33 to 4.15.0-43 my laptop no longer
  boots, it crashes when reaching the stage where it says Reached Target
  Encrypted Volumes. Have reverted to 4.15.0-33 in the meantime. Is this
  something that can be rectified?

  Using an ASUS XM553MA laptop.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaron  1222 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  InstallationDate: Installed on 2018-12-06 (27 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X553MA
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=7fdad478-0ec8-4191-9c7e-22f837dc7af3 ro
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  tessa
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X553MA.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X553MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX553MA.211:bd04/10/2015:svnASUSTeKCOMPUTERINC.:pnX553MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX553MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X553MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

2019-01-02 Thread Aaron
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1810210/+attachment/5226332/+files/ProcEnviron.txt

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

Title:
  Kernel 4.15.0-43 crashes laptop on boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading kernel from 4.15.0-33 to 4.15.0-43 my laptop no longer
  boots, it crashes when reaching the stage where it says Reached Target
  Encrypted Volumes. Have reverted to 4.15.0-33 in the meantime. Is this
  something that can be rectified?

  Using an ASUS XM553MA laptop.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaron  1222 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  InstallationDate: Installed on 2018-12-06 (27 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X553MA
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=7fdad478-0ec8-4191-9c7e-22f837dc7af3 ro
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  tessa
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X553MA.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X553MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX553MA.211:bd04/10/2015:svnASUSTeKCOMPUTERINC.:pnX553MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX553MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X553MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810210/+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 1810210] Re: Kernel 4.15.0-43 crashes laptop on boot

2019-01-02 Thread Aaron
apport information

** Tags added: apport-collected tessa

** Description changed:

  Since upgrading kernel from 4.15.0-33 to 4.15.0-43 my laptop no longer
  boots, it crashes when reaching the stage where it says Reached Target
  Encrypted Volumes. Have reverted to 4.15.0-33 in the meantime. Is this
  something that can be rectified?
  
  Using an ASUS XM553MA laptop.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.5
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  aaron  1222 F pulseaudio
+ CurrentDesktop: X-Cinnamon
+ DistroRelease: Linux Mint 19.1
+ InstallationDate: Installed on 2018-12-06 (27 days ago)
+ InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp. 
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: ASUSTeK COMPUTER INC. X553MA
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=7fdad478-0ec8-4191-9c7e-22f837dc7af3 ro
+ ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-33-generic N/A
+  linux-backports-modules-4.15.0-33-generic  N/A
+  linux-firmware 1.173.2
+ RfKill:
+  0: phy0: Wireless LAN
+   Soft blocked: no
+   Hard blocked: no
+ Tags:  tessa
+ Uname: Linux 4.15.0-33-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 04/10/2015
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: X553MA.211
+ dmi.board.asset.tag: ATN12345678901234567
+ dmi.board.name: X553MA
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: 1.0
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: ASUSTeK COMPUTER INC.
+ dmi.chassis.version: 1.0
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX553MA.211:bd04/10/2015:svnASUSTeKCOMPUTERINC.:pnX553MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX553MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
+ dmi.product.family: X
+ dmi.product.name: X553MA
+ dmi.product.version: 1.0
+ dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1810210/+attachment/5226325/+files/AlsaInfo.txt

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

Title:
  Kernel 4.15.0-43 crashes laptop on boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading kernel from 4.15.0-33 to 4.15.0-43 my laptop no longer
  boots, it crashes when reaching the stage where it says Reached Target
  Encrypted Volumes. Have reverted to 4.15.0-33 in the meantime. Is this
  something that can be rectified?

  Using an ASUS XM553MA laptop.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaron  1222 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  InstallationDate: Installed on 2018-12-06 (27 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X553MA
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=7fdad478-0ec8-4191-9c7e-22f837dc7af3 ro
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  tessa
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X553MA.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X553MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX553MA.211:bd04/10/2015:svnASUSTeKCOMPUTERINC.:pnX553MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX553MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.n

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

2019-01-02 Thread 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 1810064

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

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

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

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

** Tags added: bionic

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

Title:
  UI hangs When booting Live version of Ubuntu 18.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My system:
  Graphics:  Card: Advanced Micro Devices [AMD/ATI] Device 98e4
 bus-ID: 00:01.0 chip-ID: 1002:98e4
 Display Server: X.Org 1.18.4 drivers: ati,amdgpu (unloaded: 
fbdev,vesa,radeon)
 Resolution: 1366x768@60.03hz
 GLX Renderer: Gallium 0.4 on AMD STONEY (DRM 3.1.0, LLVM 3.8.0)
 GLX Version: 3.0 Mesa 11.2.0 Direct Rendering: Yes

  description: Notebook
  product: Inspiron 15-3565 (078E)
  vendor: Dell Inc.
  version: 1.7.0
  serial: 9LWJ6L2
  width: 64 bits
  capabilities: smbios-3.0 dmi-3.0 smp vsyscall32
  configuration: boot=normal chassis=notebook family=Inspiron sku=078E 
uuid=44454C4C-4C00-1057-804A-B9C04F364C32
*-core
 description: Motherboard
 product: Inspiron 15-3565
 vendor: Dell Inc.
 physical id: 0
 version: A00
 serial: .9LWJ6L2.CNWSC0083900Q7.
 slot: Default string
   *-firmware
description: BIOS
vendor: Dell Inc.
physical id: 0
version: 1.7.0
date: 10/23/2017
size: 64KiB
capacity: 8128KiB
capabilities: pci pnp upgrade shadowing cdboot bootselect edd 
int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int14serial 
int17printer acpi usb biosbootspecification netboot uefi
   *-cache:0
description: L1 cache
physical id: 17
slot: L1 CACHE
size: 160KiB
capacity: 160KiB
clock: 1GHz (1.0ns)
capabilities: pipeline-burst internal write-back unified
configuration: level=1
   *-cache:1
description: L2 cache
physical id: 18
slot: L2 CACHE
size: 1MiB
capacity: 1MiB
clock: 1GHz (1.0ns)
capabilities: pipeline-burst internal write-back unified
configuration: level=2
   *-memory
description: System Memory
physical id: 25
slot: System board or motherboard
size: 4GiB
  *-bank:0
   description: SODIMM DDR4 [empty]
   product: A1_PartNum0
   vendor: 
   physical id: 0
   serial: A1_SerialNum0
   slot: DIMM 0
   width: 64 bits
  *-bank:1
   description: SODIMM DDR4 Synchronous Unbuffered (Unregistered) 
2400 MHz (0.4 ns)
   product: 4ATF51264HZ-2G3E1
   vendor: 009C360B
   physical id: 1
   serial: 1B0B3BB5
   slot: DIMM 1
   size: 4GiB
   width: 64 bits
   clock: 2400MHz (0.4ns)
   *-cpu
description: CPU
product: AMD A6-9200 RADEON R4, 5 COMPUTE CORES 2C+3G
vendor: Advanced Micro Devices [AMD]
physical id: 2c
bus info: cpu@0
version: AMD A6-9200 RADEON R4, 5 COMPUTE CORES 2C+3G
slot: P0
size: 1620MHz
capacity: 2GHz
width: 64 bits
clock: 100MHz
capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae 
mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht 
syscall nx mmxext fxsr_opt pdpe1gb rdtscp constant_tsc rep_good acc_power nopl 
nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 
sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm 
extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt 
lwp fma4 tce nodeid_msr tbm perfctr_core perfctr_nb bpext ptsc mwaitx cpb 
hw_pstate vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock 
nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter 
pfthreshold avic v_vmsave_vmload vgif overflow_recov cpufreq
configuration: cores=2 enabledcores=2 threads=2
   *-pci:0
description: Host bridge
product: Advanced Micro Devices, I

[Kernel-packages] [Bug 1810064] Re: UI hangs When booting Live version of Ubuntu 18.04

2019-01-02 Thread Richard
Thanks! Finally got it to work.

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

** No longer affects: linux (Ubuntu)

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

Title:
  UI hangs When booting Live version of Ubuntu 18.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My system:
  Graphics:  Card: Advanced Micro Devices [AMD/ATI] Device 98e4
 bus-ID: 00:01.0 chip-ID: 1002:98e4
 Display Server: X.Org 1.18.4 drivers: ati,amdgpu (unloaded: 
fbdev,vesa,radeon)
 Resolution: 1366x768@60.03hz
 GLX Renderer: Gallium 0.4 on AMD STONEY (DRM 3.1.0, LLVM 3.8.0)
 GLX Version: 3.0 Mesa 11.2.0 Direct Rendering: Yes

  description: Notebook
  product: Inspiron 15-3565 (078E)
  vendor: Dell Inc.
  version: 1.7.0
  serial: 9LWJ6L2
  width: 64 bits
  capabilities: smbios-3.0 dmi-3.0 smp vsyscall32
  configuration: boot=normal chassis=notebook family=Inspiron sku=078E 
uuid=44454C4C-4C00-1057-804A-B9C04F364C32
*-core
 description: Motherboard
 product: Inspiron 15-3565
 vendor: Dell Inc.
 physical id: 0
 version: A00
 serial: .9LWJ6L2.CNWSC0083900Q7.
 slot: Default string
   *-firmware
description: BIOS
vendor: Dell Inc.
physical id: 0
version: 1.7.0
date: 10/23/2017
size: 64KiB
capacity: 8128KiB
capabilities: pci pnp upgrade shadowing cdboot bootselect edd 
int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int14serial 
int17printer acpi usb biosbootspecification netboot uefi
   *-cache:0
description: L1 cache
physical id: 17
slot: L1 CACHE
size: 160KiB
capacity: 160KiB
clock: 1GHz (1.0ns)
capabilities: pipeline-burst internal write-back unified
configuration: level=1
   *-cache:1
description: L2 cache
physical id: 18
slot: L2 CACHE
size: 1MiB
capacity: 1MiB
clock: 1GHz (1.0ns)
capabilities: pipeline-burst internal write-back unified
configuration: level=2
   *-memory
description: System Memory
physical id: 25
slot: System board or motherboard
size: 4GiB
  *-bank:0
   description: SODIMM DDR4 [empty]
   product: A1_PartNum0
   vendor: 
   physical id: 0
   serial: A1_SerialNum0
   slot: DIMM 0
   width: 64 bits
  *-bank:1
   description: SODIMM DDR4 Synchronous Unbuffered (Unregistered) 
2400 MHz (0.4 ns)
   product: 4ATF51264HZ-2G3E1
   vendor: 009C360B
   physical id: 1
   serial: 1B0B3BB5
   slot: DIMM 1
   size: 4GiB
   width: 64 bits
   clock: 2400MHz (0.4ns)
   *-cpu
description: CPU
product: AMD A6-9200 RADEON R4, 5 COMPUTE CORES 2C+3G
vendor: Advanced Micro Devices [AMD]
physical id: 2c
bus info: cpu@0
version: AMD A6-9200 RADEON R4, 5 COMPUTE CORES 2C+3G
slot: P0
size: 1620MHz
capacity: 2GHz
width: 64 bits
clock: 100MHz
capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae 
mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht 
syscall nx mmxext fxsr_opt pdpe1gb rdtscp constant_tsc rep_good acc_power nopl 
nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 
sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm 
extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt 
lwp fma4 tce nodeid_msr tbm perfctr_core perfctr_nb bpext ptsc mwaitx cpb 
hw_pstate vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock 
nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter 
pfthreshold avic v_vmsave_vmload vgif overflow_recov cpufreq
configuration: cores=2 enabledcores=2 threads=2
   *-pci:0
description: Host bridge
product: Advanced Micro Devices, Inc. [AMD]
vendor: Advanced Micro Devices, Inc. [AMD]
physical id: 100
bus info: pci@:00:00.0
version: 00
width: 32 bits
clock: 33MHz
  *-generic:0 UNCLAIMED
   description: IOMMU
   product: Advanced Micro Devices, Inc. [AMD]
   vendor: Advanced Micro Devices, Inc. [AMD]
   physical id: 0.2
   

[Kernel-packages] [Bug 1810064] [NEW] UI hangs When booting Live version of Ubuntu 18.04

2019-01-02 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

My system:
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Device 98e4
   bus-ID: 00:01.0 chip-ID: 1002:98e4
   Display Server: X.Org 1.18.4 drivers: ati,amdgpu (unloaded: 
fbdev,vesa,radeon)
   Resolution: 1366x768@60.03hz
   GLX Renderer: Gallium 0.4 on AMD STONEY (DRM 3.1.0, LLVM 3.8.0)
   GLX Version: 3.0 Mesa 11.2.0 Direct Rendering: Yes

description: Notebook
product: Inspiron 15-3565 (078E)
vendor: Dell Inc.
version: 1.7.0
serial: 9LWJ6L2
width: 64 bits
capabilities: smbios-3.0 dmi-3.0 smp vsyscall32
configuration: boot=normal chassis=notebook family=Inspiron sku=078E 
uuid=44454C4C-4C00-1057-804A-B9C04F364C32
  *-core
   description: Motherboard
   product: Inspiron 15-3565
   vendor: Dell Inc.
   physical id: 0
   version: A00
   serial: .9LWJ6L2.CNWSC0083900Q7.
   slot: Default string
 *-firmware
  description: BIOS
  vendor: Dell Inc.
  physical id: 0
  version: 1.7.0
  date: 10/23/2017
  size: 64KiB
  capacity: 8128KiB
  capabilities: pci pnp upgrade shadowing cdboot bootselect edd 
int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int14serial 
int17printer acpi usb biosbootspecification netboot uefi
 *-cache:0
  description: L1 cache
  physical id: 17
  slot: L1 CACHE
  size: 160KiB
  capacity: 160KiB
  clock: 1GHz (1.0ns)
  capabilities: pipeline-burst internal write-back unified
  configuration: level=1
 *-cache:1
  description: L2 cache
  physical id: 18
  slot: L2 CACHE
  size: 1MiB
  capacity: 1MiB
  clock: 1GHz (1.0ns)
  capabilities: pipeline-burst internal write-back unified
  configuration: level=2
 *-memory
  description: System Memory
  physical id: 25
  slot: System board or motherboard
  size: 4GiB
*-bank:0
 description: SODIMM DDR4 [empty]
 product: A1_PartNum0
 vendor: 
 physical id: 0
 serial: A1_SerialNum0
 slot: DIMM 0
 width: 64 bits
*-bank:1
 description: SODIMM DDR4 Synchronous Unbuffered (Unregistered) 
2400 MHz (0.4 ns)
 product: 4ATF51264HZ-2G3E1
 vendor: 009C360B
 physical id: 1
 serial: 1B0B3BB5
 slot: DIMM 1
 size: 4GiB
 width: 64 bits
 clock: 2400MHz (0.4ns)
 *-cpu
  description: CPU
  product: AMD A6-9200 RADEON R4, 5 COMPUTE CORES 2C+3G
  vendor: Advanced Micro Devices [AMD]
  physical id: 2c
  bus info: cpu@0
  version: AMD A6-9200 RADEON R4, 5 COMPUTE CORES 2C+3G
  slot: P0
  size: 1620MHz
  capacity: 2GHz
  width: 64 bits
  clock: 100MHz
  capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae mce 
cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall 
nx mmxext fxsr_opt pdpe1gb rdtscp constant_tsc rep_good acc_power nopl 
nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 
sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm 
extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt 
lwp fma4 tce nodeid_msr tbm perfctr_core perfctr_nb bpext ptsc mwaitx cpb 
hw_pstate vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock 
nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter 
pfthreshold avic v_vmsave_vmload vgif overflow_recov cpufreq
  configuration: cores=2 enabledcores=2 threads=2
 *-pci:0
  description: Host bridge
  product: Advanced Micro Devices, Inc. [AMD]
  vendor: Advanced Micro Devices, Inc. [AMD]
  physical id: 100
  bus info: pci@:00:00.0
  version: 00
  width: 32 bits
  clock: 33MHz
*-generic:0 UNCLAIMED
 description: IOMMU
 product: Advanced Micro Devices, Inc. [AMD]
 vendor: Advanced Micro Devices, Inc. [AMD]
 physical id: 0.2
 bus info: pci@:00:00.2
 version: 00
 width: 32 bits
 clock: 33MHz
 capabilities: msi ht bus_master cap_list
 configuration: latency=0
*-display UNCLAIMED
 description: VGA compatible controller
 product: Advanced Micro Devices, Inc. [AMD/ATI]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 1
 bus info: pci@:00:01.0
 version: c0
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list
 conf

[Kernel-packages] [Bug 1777586] Re: Ubuntu Server 18.04 LTS aacraid error

2019-01-02 Thread telsch
I run in similar issue after upgrading from 14.04 to 16.04 as well to
18.04 again.

Previously solution was to upgrade the firmware: 

https://storage.microsemi.com/en-us/downloads/bios_fw/bios_fw_ver/productid=sas-6405&dn=adaptec+raid+6405.php


Changelog describe added support:
 http://download.adaptec.com/pdfs/readme/microsemi_relnotes_arc_8_2017.pdf
- Added support for Ubuntu 16.04.
- Added support for Ubuntu 14.04.4.

Support Call gives no hope, cause this raid-controller is eol.

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

Title:
  Ubuntu Server 18.04 LTS aacraid error

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

Bug description:
  I upgraded from a previous version of Ubuntu 14.04LTS to 18.04LTS and
  am now running into these raid adapter driver errors.   The server ran
  fine in older version.  My apologies as I lost the exact version, but
  it never had any errors like this version.

  Now when ever I try to copy files to the RAID 5 drive, or untar a
  file, I get these errors now after a few MB's of written data.

  Linux batboat 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC
  2018 x86_64 x86_64 x86_64 GNU/Linux

  batboat:/var/log$ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  I have tried the IRQ debugging tips to no avail.   I loaded in
  Debian9.4.0 and it only briefly showed this error once.   But appears
  to be much more resilient and appears to work fine.


  Jun 19 00:02:21 batboat kernel: [  498.770839] aacraid: Host adapter reset 
request. SCSI hang ?
  Jun 19 00:02:37 batboat kernel: [  514.139167] aacraid: Host adapter reset 
request. SCSI hang ?
  Jun 19 00:02:37 batboat kernel: [  514.795083] aacraid :03:09.0: Adapter 
health - 199
  Jun 19 00:02:37 batboat kernel: [  514.800376] aacraid :03:09.0: 
outstanding cmd: midlevel-0
  Jun 19 00:02:37 batboat kernel: [  514.800378] aacraid :03:09.0: 
outstanding cmd: lowlevel-0
  Jun 19 00:02:37 batboat kernel: [  514.800381] aacraid :03:09.0: 
outstanding cmd: error handler-0
  Jun 19 00:02:37 batboat kernel: [  514.800383] aacraid :03:09.0: 
outstanding cmd: firmware-5
  Jun 19 00:02:37 batboat kernel: [  514.800385] aacraid :03:09.0: 
outstanding cmd: kernel-0
  Jun 19 00:02:37 batboat kernel: [  514.800391] sd 4:0:0:0: Device offlined - 
not ready after error recovery
  Jun 19 00:02:37 batboat kernel: [  514.800394] sd 4:0:0:0: Device offlined - 
not ready after error recovery
  Jun 19 00:02:37 batboat kernel: [  514.800396] sd 4:0:0:0: Device offlined - 
not ready after error recovery
  Jun 19 00:02:37 batboat kernel: [  514.800399] sd 4:0:0:0: Device offlined - 
not ready after error recovery
  Jun 19 00:02:37 batboat kernel: [  514.800401] sd 4:0:0:0: Device offlined - 
not ready after error recovery

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777586/+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 1778087] Re: ELAN1200 touchpad jumps around and disconnects

2019-01-02 Thread Tetrix
I am experiencing the same behavior with the 4.19 kernel.
The touchpad does not work smoothly and freezes occasionally and I have to wait 
for couple of minutes, after which it starts working again.

dmesg command gives the same output like what other people have
reported: i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report
(16/65535)

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

Title:
  ELAN1200 touchpad jumps around and disconnects

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is on an ASUS GL503VD laptop and would probably affect other ASUS
  laptops equipped with the ELAN1200 touchpad.

  I am on Kernel 4.17.2 because older kernels did not enable the
  touchpad at all(It was just unrecognized or i2c-hid stopped the
  computer from booting)

  The touchpad works but it has erratic behaviour and disconnects
  randomly. After it disconnects the only way to bring it back is to
  `modprobe -r hid-multitouch && modprobe hid-multitouch`

  Libinput and synaptics can handle the touchpad though I found
  synaptics to be more stable.

  dmesg gets spammed with this whenever I move the touchpad:
  [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report 
(16/65535)

  I tried to compile: https://github.com/mishurov/linux_elan1200_touchpad
  Because from what I understand the "jumpy/disconnect" problem is associated 
to the incomplete reports and Mishurov managed to mitigate those. Unfortunately 
some symbols were deprecated in kernel 4.17.2 and it did not compile for my 
system.

  While I can use my touchpad as is right now, and "restart" it with
  modprobe when needed, it would be nice to have it function bug-free.
  (Right after I typed this my touchpad disconnected and I needed to
  modprobe again, I am considering making a cronjob for that)

  Let me know if anything else is needed. Will wait for an apport collection to 
add log files.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-10 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 4.17.2 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778087/+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 1810297] [NEW] package nvidia-utils-390 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-340 340.1

2019-01-02 Thread Aman Deep
Public bug reported:

Problem occured while going through these steps
https://medium.com/@taylordenouden/installing-tensorflow-gpu-on-
ubuntu-18-04-89a142325138

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: nvidia-utils-390 (not installed)
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
AptOrdering:
 libcuda1-340:amd64: Remove
 nvidia-opencl-icd-340:amd64: Remove
 libnvidia-compute-390:amd64: Install
 nvidia-utils-390:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Wed Jan  2 18:27:00 2019
ErrorMessage: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is 
also in package nvidia-340 340.107-0ubuntu0.18.04.1
InstallationDate: Installed on 2018-12-31 (1 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: nvidia-graphics-drivers-390
Title: package nvidia-utils-390 (not installed) failed to install/upgrade: 
trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package 
nvidia-340 340.107-0ubuntu0.18.04.1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-390 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package nvidia-utils-390 (not installed) failed to install/upgrade:
  trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in
  package nvidia-340 340.107-0ubuntu0.18.04.1

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  Problem occured while going through these steps
  https://medium.com/@taylordenouden/installing-tensorflow-gpu-on-
  ubuntu-18-04-89a142325138

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-utils-390 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  AptOrdering:
   libcuda1-340:amd64: Remove
   nvidia-opencl-icd-340:amd64: Remove
   libnvidia-compute-390:amd64: Install
   nvidia-utils-390:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Jan  2 18:27:00 2019
  ErrorMessage: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is 
also in package nvidia-340 340.107-0ubuntu0.18.04.1
  InstallationDate: Installed on 2018-12-31 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: nvidia-graphics-drivers-390
  Title: package nvidia-utils-390 (not installed) failed to install/upgrade: 
trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package 
nvidia-340 340.107-0ubuntu0.18.04.1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1810297/+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 1810293] Status changed to Confirmed

2019-01-02 Thread 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/1810293

Title:
  Kernel metadata scrubbing facility is not available.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running xfs_scrub leads to an error:

  sudo xfs_scrub /
  EXPERIMENTAL xfs_scrub program in use! Use at your own risk!
  Info: /: Kernel metadata scrubbing facility is not available.
  Info: /: Scrub aborted after phase 1.
  /: errors found: 1

  
  Expected behaviour:
  xfs_scrub can srub the XFS filesystems.

  xfs_info /
  meta-data=/dev/mapper/sda5_crypt isize=512agcount=4, agsize=7767424 blks
   =   sectsz=512   attr=2, projid32bit=1
   =   crc=1finobt=1 spinodes=0 rmapbt=0
   =   reflink=0
  data =   bsize=4096   blocks=31069696, imaxpct=25
   =   sunit=0  swidth=0 blks
  naming   =version 2  bsize=4096   ascii-ci=0 ftype=1
  log  =internal   bsize=4096   blocks=15170, version=2
   =   sectsz=512   sunit=0 blks, lazy-count=1
  realtime =none   extsz=4096   blocks=0, rtextents=0


  Ubuntu Version:
  Description:  Ubuntu 18.10
  Release:  18.10

  related packages:
  linux-generic:
Installed: 4.18.0.13.14
Candidate: 4.18.0.13.14
Version table:
   *** 4.18.0.13.14 500
  500 http://ftp.halifax.rwth-aachen.de/ubuntu cosmic-updates/main 
amd64 Packages
  500 http://ftp.halifax.rwth-aachen.de/ubuntu cosmic-security/main 
amd64 Packages
  500 http://ftp.halifax.rwth-aachen.de/ubuntu cosmic-proposed/main 
amd64 Packages
  100 /var/lib/dpkg/status
   4.18.0.10.11 500
  500 http://ftp.halifax.rwth-aachen.de/ubuntu cosmic/main amd64 
Packages
  xfsprogs:
Installed: 4.15.1-1ubuntu1
Candidate: 4.15.1-1ubuntu1
Version table:
   *** 4.15.1-1ubuntu1 500
  500 http://ftp.halifax.rwth-aachen.de/ubuntu cosmic/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bfr2664 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Jan  2 12:50:13 2019
  MachineType: LENOVO 2325G70
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=UUID=0bc0ece5-9967-416c-9c82-1dae5051f2c8 ro splash quiet vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-10-21 (72 days ago)
  dmi.bios.date: 06/19/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETB3WW (2.73 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325G70
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: PK1R41C
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETB3WW(2.73):bd06/19/2018:svnLENOVO:pn2325G70:pvrThinkPadX230:rvnLENOVO:rn2325G70:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2325G70
  dmi.product.sku: LENOVO_MT_2325
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810293/+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 1810293] [NEW] Kernel metadata scrubbing facility is not available.

2019-01-02 Thread bjo
Public bug reported:

Running xfs_scrub leads to an error:

sudo xfs_scrub /
EXPERIMENTAL xfs_scrub program in use! Use at your own risk!
Info: /: Kernel metadata scrubbing facility is not available.
Info: /: Scrub aborted after phase 1.
/: errors found: 1


Expected behaviour:
xfs_scrub can srub the XFS filesystems.

xfs_info /
meta-data=/dev/mapper/sda5_crypt isize=512agcount=4, agsize=7767424 blks
 =   sectsz=512   attr=2, projid32bit=1
 =   crc=1finobt=1 spinodes=0 rmapbt=0
 =   reflink=0
data =   bsize=4096   blocks=31069696, imaxpct=25
 =   sunit=0  swidth=0 blks
naming   =version 2  bsize=4096   ascii-ci=0 ftype=1
log  =internal   bsize=4096   blocks=15170, version=2
 =   sectsz=512   sunit=0 blks, lazy-count=1
realtime =none   extsz=4096   blocks=0, rtextents=0


Ubuntu Version:
Description:Ubuntu 18.10
Release:18.10

related packages:
linux-generic:
  Installed: 4.18.0.13.14
  Candidate: 4.18.0.13.14
  Version table:
 *** 4.18.0.13.14 500
500 http://ftp.halifax.rwth-aachen.de/ubuntu cosmic-updates/main amd64 
Packages
500 http://ftp.halifax.rwth-aachen.de/ubuntu cosmic-security/main amd64 
Packages
500 http://ftp.halifax.rwth-aachen.de/ubuntu cosmic-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 4.18.0.10.11 500
500 http://ftp.halifax.rwth-aachen.de/ubuntu cosmic/main amd64 Packages
xfsprogs:
  Installed: 4.15.1-1ubuntu1
  Candidate: 4.15.1-1ubuntu1
  Version table:
 *** 4.15.1-1ubuntu1 500
500 http://ftp.halifax.rwth-aachen.de/ubuntu cosmic/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-10-generic 4.18.0-10.11
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bfr2664 F pulseaudio
CurrentDesktop: XFCE
Date: Wed Jan  2 12:50:13 2019
MachineType: LENOVO 2325G70
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=UUID=0bc0ece5-9967-416c-9c82-1dae5051f2c8 ro splash quiet vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-10-generic N/A
 linux-backports-modules-4.18.0-10-generic  N/A
 linux-firmware 1.175.1
SourcePackage: linux
UpgradeStatus: Upgraded to cosmic on 2018-10-21 (72 days ago)
dmi.bios.date: 06/19/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: G2ETB3WW (2.73 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2325G70
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: PK1R41C
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETB3WW(2.73):bd06/19/2018:svnLENOVO:pn2325G70:pvrThinkPadX230:rvnLENOVO:rn2325G70:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad X230
dmi.product.name: 2325G70
dmi.product.sku: LENOVO_MT_2325
dmi.product.version: ThinkPad X230
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug cosmic kernel xfs

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

Title:
  Kernel metadata scrubbing facility is not available.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running xfs_scrub leads to an error:

  sudo xfs_scrub /
  EXPERIMENTAL xfs_scrub program in use! Use at your own risk!
  Info: /: Kernel metadata scrubbing facility is not available.
  Info: /: Scrub aborted after phase 1.
  /: errors found: 1

  
  Expected behaviour:
  xfs_scrub can srub the XFS filesystems.

  xfs_info /
  meta-data=/dev/mapper/sda5_crypt isize=512agcount=4, agsize=7767424 blks
   =   sectsz=512   attr=2, projid32bit=1
   =   crc=1finobt=1 spinodes=0 rmapbt=0
   =   reflink=0
  data =   bsize=4096   blocks=31069696, imaxpct=25
   =   sunit=0  swidth=0 blks
  naming   =version 2  bsize=4096   ascii-ci=0 ftype=1
  log  =internal   bsize=4096   blocks=15170, version=2
   =   sectsz=512   sunit=0 blks, lazy-count=1
  realtime =none   extsz=4096   blocks=0, rtextents=0


  Ubuntu Version:
  Description:  Ubuntu 18.10
  Release:  18.10

  related packages:
  linux-generic:
Installed: 4.18.0.13.14
Candidate: 4.18.0.13.14
Version table:
   *** 4.18.0.13.14 500
  500 http://ftp.halifax.rwth-aachen.de/ubu

[Kernel-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

2019-01-02 Thread Siavash
This happens to me on a clean install with OS updates installed
19/01/01.

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

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

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.
  I've talked to another user on IRC who seems to be having the same freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  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/1798961/+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 1781016] Re: Slow flood of do_IRQ: No irq for vector

2019-01-02 Thread A
Running an Intel S2600ST motherboard with dual Gold 6148 I get this
error regularly after the last kernel update I did.

The number before the dot seems to be a CPU number since I see many varied 
numbers and there's 40 cores/80 threads on my motherboard
e.g.
[Wed Dec 26 14:20:25 2018] do_IRQ: 14.216 No irq handler for vector
[Wed Dec 26 18:35:32 2018] do_IRQ: 46.40 No irq handler for vector
[Thu Dec 27 00:56:21 2018] do_IRQ: 15.55 No irq handler for vector
(there are 37 of these over the last 2 weeks)

There's no /sys/kernel/debug/irq/ folder

The current kernel on "Ubuntu 16.04.5 LTS" I am using is
"vmlinuz-4.4.0-140-generic"

I updated from "vmlinuz-4.4.0-119-generic" (which was also 16.04 LTS)

I've had this server for over a year and with the 4.4.0-140 update is
the first time I've seen this.

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

Title:
  Slow flood of do_IRQ: No irq for vector

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Every few seconds I get something like this in my dmesg:

  [44984.933221] do_IRQ: 1.34 No irq handler for vector
  [44986.933976] do_IRQ: 1.34 No irq handler for vector
  [44991.935614] do_IRQ: 1.34 No irq handler for vector
  [45004.938590] do_IRQ: 1.34 No irq handler for vector
  [45005.939002] do_IRQ: 4.34 No irq handler for vector
  [45034.949161] do_IRQ: 4.34 No irq handler for vector
  [45051.954569] do_IRQ: 4.34 No irq handler for vector
  [45058.956019] do_IRQ: 4.34 No irq handler for vector
  [45062.957727] do_IRQ: 4.34 No irq handler for vector
  [45063.958204] do_IRQ: 4.34 No irq handler for vector
  [45073.961103] do_IRQ: 4.34 No irq handler for vector

  The numbers vary. Some examples are 4.34, 4.36, 1.34, 0.33, 6.34,
  7.33, 5.37. Eventually dmesg's ring buffer is full and my entire log
  is just messages like above with varying #.## numbers.

  I researched it and tried disabling irqbalance. It had no effect, the
  messages continued.

  The system is a Ryzen 2700X with B350 chipset on Asus Prime B350-PLUS.
  I have 64GB of Kingston DDR4-2400 ECC memory and Samsung 960 PRO M.2
  NVMe SSD, and an Intel I350-T4 quad port gigabit NIC. This issue never
  occurred before installing 18.03 on the same hardware. No overclocking
  whatsoever has ever been done to this machine.

  Also, I had to disable selective suspend on USB in this version to
  prevent major USB issues, which was not required in 17.10, that might
  be related.

  My system seems stable, but spurious IRQs can't be good. I'd like to
  resolve this if possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-26-generic 4.15.0-26.28
  ProcVersionSignature: Ubuntu 4.15.0-26.28-generic 4.15.18
  Uname: Linux 4.15.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2145 F pulseaudio
doug   3736 F pulseaudio
   /dev/snd/controlC1:  gdm2145 F pulseaudio
doug   3736 F pulseaudio
  Date: Tue Jul 10 12:49:00 2018
  HibernationDevice:
   
  InstallationDate: Installed on 2017-06-26 (379 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-26-generic 
root=UUID=53446747-0814-48f7-b7c4-7fd7d7234d83 ro video=vesa:off vga=normal 
video=efifb:off usbcore.autosuspend=-1 usbhid.quirks=0x1e71:0x170e:0x4
  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-26-generic N/A
   linux-backports-modules-4.15.0-26-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4011
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B350-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4011:bd04/19/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product 

[Kernel-packages] [Bug 1809868] Re: 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5 in btrfs_kernel_fixes failed on T

2019-01-02 Thread Po-Hsu Lin
** Also affects: ubuntu-kernel-tests
   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/1809868

Title:
  29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5 in btrfs_kernel_fixes failed
  on T

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Test failed with "ERROR: rmdir o259-6-0 failed. No such file or
  directory" on Trusty.

  
  Invoking test 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5

  fix 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5

  Btrfs: send, don't send rmdir for same target multiple times

  When doing an incremental send, if we delete a directory that has N > 1
  hardlinks for the same file and that file has the highest inode number
  inside the directory contents, an incremental send would send N times an
  rmdir operation against the directory. This made the btrfs receive command
  fail on the second rmdir instruction, as the target directory didn't exist
  anymore.

  Performing full device TRIM (1.00GiB) ...
  Turning ON incompat feature 'extref': increased hardlink limit per file to 
65536

  WARNING! - Btrfs v3.12 IS EXPERIMENTAL
  WARNING! - see http://btrfs.wiki.kernel.org before using

  fs created label (null) on /dev/loop0
nodesize 16384 leafsize 16384 sectorsize 4096 size 1.00GiB
  Btrfs v3.12
  Create a readonly snapshot of 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5' in 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap1'
  At subvol /tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap1
  Create a readonly snapshot of 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5' in 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap2'
  At subvol /tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap2
  Performing full device TRIM (1.00GiB) ...
  Turning ON incompat feature 'extref': increased hardlink limit per file to 
65536

  WARNING! - Btrfs v3.12 IS EXPERIMENTAL
  WARNING! - see http://btrfs.wiki.kernel.org before using

  fs created label (null) on /dev/loop0
nodesize 16384 leafsize 16384 sectorsize 4096 size 1.00GiB
  Btrfs v3.12
  At subvol snap1
  At snapshot snap2
  ERROR: rmdir o259-6-0 failed. No such file or directory
  incremental receive failed

  It seems that commit 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5 does not
  exist in Trusty tree.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-164-generic 3.13.0-164.214
  ProcVersionSignature: User Name 3.13.0-164.214-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-164-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 27 03:14 seq
   crw-rw 1 root audio 116, 33 Dec 27 03:14 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   [13958.095408] btrfs: device fsid da34075a-4eaa-4e50-aeea-02206e8c8e44 devid 
1 transid 4 /dev/loop0
   [13958.102670] btrfs: device fsid da34075a-4eaa-4e50-aeea-02206e8c8e44 devid 
1 transid 4 /dev/loop0
   [13958.105901] btrfs: device fsid da34075a-4eaa-4e50-aeea-02206e8c8e44 devid 
1 transid 4 /dev/loop0
   [13958.106099] btrfs: disk space caching is enabled
   [13958.107771] btrfs: creating UUID tree
  Date: Thu Dec 27 07:11:58 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-164-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-164-generic N/A
   linux-backports-modules-3.13.0-164-generic  N/A
   linux-firmware  1.127.24
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1809868/+subscriptions

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

[Kernel-packages] [Bug 1809869] Re: 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5 in btrfs_kernel_fixes failed on T

2019-01-02 Thread Po-Hsu Lin
*** This bug is a duplicate of bug 1809868 ***
https://bugs.launchpad.net/bugs/1809868

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

** This bug has been marked a duplicate of bug 1809868
   29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5 in btrfs_kernel_fixes failed on T

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

Title:
  29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5 in btrfs_kernel_fixes failed
  on T

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Test failed with "ERROR: rmdir o259-6-0 failed. No such file or
  directory" on Trusty.

  
  Invoking test 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5

  fix 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5

  Btrfs: send, don't send rmdir for same target multiple times

  When doing an incremental send, if we delete a directory that has N > 1
  hardlinks for the same file and that file has the highest inode number
  inside the directory contents, an incremental send would send N times an
  rmdir operation against the directory. This made the btrfs receive command
  fail on the second rmdir instruction, as the target directory didn't exist
  anymore.

  Performing full device TRIM (1.00GiB) ...
  Turning ON incompat feature 'extref': increased hardlink limit per file to 
65536

  WARNING! - Btrfs v3.12 IS EXPERIMENTAL
  WARNING! - see http://btrfs.wiki.kernel.org before using

  fs created label (null) on /dev/loop0
nodesize 16384 leafsize 16384 sectorsize 4096 size 1.00GiB
  Btrfs v3.12
  Create a readonly snapshot of 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5' in 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap1'
  At subvol /tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap1
  Create a readonly snapshot of 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5' in 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap2'
  At subvol /tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap2
  Performing full device TRIM (1.00GiB) ...
  Turning ON incompat feature 'extref': increased hardlink limit per file to 
65536

  WARNING! - Btrfs v3.12 IS EXPERIMENTAL
  WARNING! - see http://btrfs.wiki.kernel.org before using

  fs created label (null) on /dev/loop0
nodesize 16384 leafsize 16384 sectorsize 4096 size 1.00GiB
  Btrfs v3.12
  At subvol snap1
  At snapshot snap2
  ERROR: rmdir o259-6-0 failed. No such file or directory
  incremental receive failed

  It seems that commit 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5 does not
  exist in Trusty tree.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-164-generic 3.13.0-164.214
  ProcVersionSignature: User Name 3.13.0-164.214-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-164-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 27 03:14 seq
   crw-rw 1 root audio 116, 33 Dec 27 03:14 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   [13958.095408] btrfs: device fsid da34075a-4eaa-4e50-aeea-02206e8c8e44 devid 
1 transid 4 /dev/loop0
   [13958.102670] btrfs: device fsid da34075a-4eaa-4e50-aeea-02206e8c8e44 devid 
1 transid 4 /dev/loop0
   [13958.105901] btrfs: device fsid da34075a-4eaa-4e50-aeea-02206e8c8e44 devid 
1 transid 4 /dev/loop0
   [13958.106099] btrfs: disk space caching is enabled
   [13958.107771] btrfs: creating UUID tree
  Date: Thu Dec 27 07:11:58 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-164-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-164-generic N/A
   linux-backports-modules-3.13.0-164-generic  N/A
   linux-firmware  1.127.24
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys

[Kernel-packages] [Bug 1810239] Re: amd_iommu conflict with Marvell Sata controller

2019-01-02 Thread Bug Watch Updater
** Changed in: linux (Debian)
   Status: Unknown => 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/1810239

Title:
  amd_iommu conflict with  Marvell Sata controller

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  Unknown

Bug description:
  This bug is to confirm that the Marvell 88SE9230 chipset bug presents
  under AMD's IOMMU implementation with Ubuntu 18.04 and the latest HWE
  Kernel

  This has similar characteristics to 
   - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1089768

  System
   - AMD Athlon 200GE
   - Gigabyte GA-B450M-S2H board
   - Marvell 88SE9230 SATA Controller with latest Firmware

  Kernel
   - Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17

  
  If I boot the HWE 4.18.0-13-generic Kernel I get the errors reported above

  If I boot with "amd_iommu=off" the drives appear to work correctly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mythfe 1170 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=/dev/mythnew/swap
  InstallationDate: Installed on 2016-07-02 (913 days ago)
  InstallationMedia: Mythbuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp9s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. B450M S2H
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/mythnew-root ro verbose 
drm_kms_helper.edid_firmware=HDMI-A-3:edid/panasonic.edid
  ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-07-27 (158 days ago)
  UserGroups: adm cdrom dip lpadmin mythtv nopasswdlogin plugdev sambashare 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 12/04/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2c
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M S2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2c:bd12/04/2018:svnGigabyteTechnologyCo.,Ltd.:pnB450MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1810239/+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 1810239] Re: amd_iommu conflict with Marvell Sata controller

2019-01-02 Thread Steven Ellis
I attempted a boot with the following upstream kernel packages

  
linux-image-unsigned-4.20.0-042000-generic_4.20.0-042000.201812232030_amd64.deb
  linux-modules-4.20.0-042000-generic_4.20.0-042000.201812232030_amd64.deb


On boot I see the following errors


Jan 02 22:09:23 mythfe-amd kernel: ata4.00: qc timeout (cmd 0xec)
Jan 02 22:09:23 mythfe-amd kernel: ata2.00: qc timeout (cmd 0xec)
Jan 02 22:09:23 mythfe-amd kernel: ata2.00: failed to IDENTIFY (I/O error, 
err_mask=0x4)
Jan 02 22:09:23 mythfe-amd kernel: ata4.00: failed to IDENTIFY (I/O error, 
err_mask=0x4)
Jan 02 22:09:23 mythfe-amd kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 
SControl 300)
Jan 02 22:09:23 mythfe-amd kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 
SControl 300)
Jan 02 22:09:23 mythfe-amd kernel: ata8.00: qc timeout (cmd 0xef)
Jan 02 22:09:23 mythfe-amd kernel: ata8.00: failed to set xfermode 
(err_mask=0x4)
Jan 02 22:09:23 mythfe-amd kernel: ata2.00: qc timeout (cmd 0xec)
Jan 02 22:09:23 mythfe-amd kernel: ata2.00: failed to IDENTIFY (I/O error, 
err_mask=0x4)
Jan 02 22:09:23 mythfe-amd kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 
SControl 300)
Jan 02 22:09:23 mythfe-amd kernel: ata4.00: qc timeout (cmd 0xec)
Jan 02 22:09:23 mythfe-amd kernel: ata8: SATA link up 1.5 Gbps (SStatus 113 
SControl 300)
Jan 02 22:09:23 mythfe-amd kernel: ata4.00: failed to IDENTIFY (I/O error, 
err_mask=0x4)
Jan 02 22:09:23 mythfe-amd kernel: ata4: limiting SATA link speed to 1.5 Gbps
Jan 02 22:09:23 mythfe-amd kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 
SControl 310)
Jan 02 22:09:23 mythfe-amd kernel: ata8.00: qc timeout (cmd 0xa1)
Jan 02 22:09:23 mythfe-amd kernel: ata8.00: failed to IDENTIFY (I/O error, 
err_mask=0x4)
Jan 02 22:09:23 mythfe-amd kernel: ata8.00: revalidation failed (errno=-5)
Jan 02 22:09:23 mythfe-amd kernel: ata8: SATA link up 1.5 Gbps (SStatus 113 
SControl 300)
Jan 02 22:09:23 mythfe-amd kernel: ata8.00: qc timeout (cmd 0xa1)
Jan 02 22:09:23 mythfe-amd kernel: ata8.00: failed to IDENTIFY (I/O error, 
err_mask=0x4)
Jan 02 22:09:23 mythfe-amd kernel: ata8.00: revalidation failed (errno=-5)
Jan 02 22:09:23 mythfe-amd kernel: ata8.00: disabled
Jan 02 22:09:23 mythfe-amd kernel: ata8: SATA link up 1.5 Gbps (SStatus 113 
SControl 300)
Jan 02 22:09:23 mythfe-amd kernel: ata2.00: qc timeout (cmd 0xec)
Jan 02 22:09:23 mythfe-amd kernel: ata2.00: failed to IDENTIFY (I/O error, 
err_mask=0x4)
Jan 02 22:09:23 mythfe-amd kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 
SControl 300)
Jan 02 22:09:23 mythfe-amd kernel: ata4.00: qc timeout (cmd 0xec)
Jan 02 22:09:23 mythfe-amd kernel: ata4.00: failed to IDENTIFY (I/O error, 
err_mask=0x4)
Jan 02 22:09:23 mythfe-amd kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 
SControl 310)
Jan 02 22:09:23 mythfe-amd kernel: ata10: SATA link down (SStatus 0 SControl 
330)
Jan 02 22:09:23 mythfe-amd kernel: ata13: SATA link down (SStatus 0 SControl 
330)
Jan 02 22:09:23 mythfe-amd kernel: ata14: SATA link down (SStatus 0 SControl 
330)

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

Title:
  amd_iommu conflict with  Marvell Sata controller

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in linux package in Debian:
  Unknown
Status in linux package in Fedora:
  Unknown

Bug description:
  This bug is to confirm that the Marvell 88SE9230 chipset bug presents
  under AMD's IOMMU implementation with Ubuntu 18.04 and the latest HWE
  Kernel

  This has similar characteristics to 
   - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1089768

  System
   - AMD Athlon 200GE
   - Gigabyte GA-B450M-S2H board
   - Marvell 88SE9230 SATA Controller with latest Firmware

  Kernel
   - Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17

  
  If I boot the HWE 4.18.0-13-generic Kernel I get the errors reported above

  If I boot with "amd_iommu=off" the drives appear to work correctly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mythfe 1170 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=/dev/mythnew/swap
  InstallationDate: Installed on 2016-07-02 (913 days ago)
  InstallationMedia: Mythbuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp9s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. B450M S2H
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/mythnew-root ro verbose 
drm_kms_helper.edid_firmware=HDMI-A-3:edid/panasonic.edid
  ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-gen

[Kernel-packages] [Bug 1810239] Re: amd_iommu conflict with Marvell Sata controller

2019-01-02 Thread Steven Ellis
Rebooted with the 4.20.0-042000-generic and the option "amd_iommu=off"
and the card works


Jan 02 22:10:52 mythfe-amd kernel: ata8.00: ATAPI: MARVELL VIRTUAL, 1.09, max 
UDMA/66
Jan 02 22:10:52 mythfe-amd kernel: ata8.00: configured for UDMA/66
Jan 02 22:10:52 mythfe-amd kernel: ata4.00: ATA-8: ST3500418AS, CC46, max 
UDMA/133
Jan 02 22:10:52 mythfe-amd kernel: ata4.00: 976773168 sectors, multi 0: LBA48 
NCQ (depth 32)
Jan 02 22:10:52 mythfe-amd kernel: ata4.00: configured for UDMA/133
Jan 02 22:10:52 mythfe-amd kernel: ata2.00: ATA-7: ST3250820AS, 3.AAE, max 
UDMA/133
Jan 02 22:10:52 mythfe-amd kernel: ata2.00: 488397168 sectors, multi 0: LBA48 
NCQ (depth 32)
Jan 02 22:10:52 mythfe-amd kernel: ata2.00: configured for UDMA/133
Jan 02 22:10:52 mythfe-amd kernel: scsi 1:0:0:0: Direct-Access ATA  
ST3250820AS  EPQ: 0 ANSI: 5
Jan 02 22:10:52 mythfe-amd kernel: sd 1:0:0:0: Attached scsi generic sg0 type 0
Jan 02 22:10:52 mythfe-amd kernel: sd 1:0:0:0: [sda] 488397168 512-byte logical 
blocks: (250 GB/233 GiB)
Jan 02 22:10:52 mythfe-amd kernel: scsi 3:0:0:0: Direct-Access ATA  
ST3500418AS  CC46 PQ: 0 ANSI: 5
Jan 02 22:10:52 mythfe-amd kernel: sd 1:0:0:0: [sda] Write Protect is off

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

Title:
  amd_iommu conflict with  Marvell Sata controller

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in linux package in Debian:
  Unknown
Status in linux package in Fedora:
  Unknown

Bug description:
  This bug is to confirm that the Marvell 88SE9230 chipset bug presents
  under AMD's IOMMU implementation with Ubuntu 18.04 and the latest HWE
  Kernel

  This has similar characteristics to 
   - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1089768

  System
   - AMD Athlon 200GE
   - Gigabyte GA-B450M-S2H board
   - Marvell 88SE9230 SATA Controller with latest Firmware

  Kernel
   - Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17

  
  If I boot the HWE 4.18.0-13-generic Kernel I get the errors reported above

  If I boot with "amd_iommu=off" the drives appear to work correctly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mythfe 1170 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=/dev/mythnew/swap
  InstallationDate: Installed on 2016-07-02 (913 days ago)
  InstallationMedia: Mythbuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp9s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. B450M S2H
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/mythnew-root ro verbose 
drm_kms_helper.edid_firmware=HDMI-A-3:edid/panasonic.edid
  ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-07-27 (158 days ago)
  UserGroups: adm cdrom dip lpadmin mythtv nopasswdlogin plugdev sambashare 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 12/04/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2c
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M S2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2c:bd12/04/2018:svnGigabyteTechnologyCo.,Ltd.:pnB450MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

2019-01-02 Thread 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 1810202

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

Title:
  allow a patch that makes elder radeon cards UltraHD ready

Status in linux package in Ubuntu:
  Incomplete

Bug description:
In March 2016 I had developed a kernel patch that allows to set the TMDS 
frequency for Radeon cards by a new kernel parameter called radeon.hdmimhz if 
the automatically set frequency stays either behind of what has been advertised 
for the card or by what is achievable through overclocking. A similar parameter 
for Nvidia/Nouveau cards is already available somewhat longer. There exists a 
patched ATI driver even for Windows. However up to now the patch has not been 
accepted into the mainline kernel simply because Radeon developers are not 
encouraged to enable this feature for elder cards by the policy of their 
sponsors. Here are some of my considerations which you may take into account 
when deciding about the acceptance of the patch for Ubuntu:
 * the patch is very simple, just a few lines of code
 * behaviour of the kernel is not influenced by the patch except when the 
user gives a non-zero value for radeon.hdmimhz
 * the patch has already wheathered time; the surrounding code has more or 
less remained unchanged since March
 * long time usage experience is available at least with the Radeon R5 230 
and the Radeon HD 6770 cards (no heast issues) as well as different monitors; 
my personal experience with the patch is very good
 * the patch provides a huge advantage at least for all people who still 
use Core 2 based systems:
   - elder Radeon cards can be made UHD ready
   - the R5 230 card supported by the patch may be the only one of its type 
that has a single slot height - and it has been sold to me as DVI-UltraHD 
ready; however this feature can not be exploited without the kernel patch
   - newer Radeon cards are often incompatible with elder Core 2 systems
 * at least Nouveau developers say that by overclocking your TMDS it would 
hardly be possible to damage a card even if it shows heat issues; a way of 
proceeding considered safe can be read in the linked article 
https://www.elstel.org/software/hunt-for-4K-UHD-2160p.html.en. The patch can 
also be found on this website; see also: 
https://bugs.freedesktop.org/show_bug.cgi?id=93885#c24. Mageia was the first 
distribution to accept this patch. The patch is safe and has been proven useful 
(since then many people with positive experience have linked to my site) - so 
why do we not include it for Ubuntu?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810202/+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 1810239] Re: amd_iommu conflict with Marvell Sata controller

2019-01-02 Thread Steven Ellis
Looks like there is a new upstream issue with
 - https://bugzilla.kernel.org/show_bug.cgi?id=199733

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

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

Title:
  amd_iommu conflict with  Marvell Sata controller

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in linux package in Debian:
  Unknown
Status in linux package in Fedora:
  Unknown

Bug description:
  This bug is to confirm that the Marvell 88SE9230 chipset bug presents
  under AMD's IOMMU implementation with Ubuntu 18.04 and the latest HWE
  Kernel

  This has similar characteristics to 
   - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1089768

  System
   - AMD Athlon 200GE
   - Gigabyte GA-B450M-S2H board
   - Marvell 88SE9230 SATA Controller with latest Firmware

  Kernel
   - Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17

  
  If I boot the HWE 4.18.0-13-generic Kernel I get the errors reported above

  If I boot with "amd_iommu=off" the drives appear to work correctly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mythfe 1170 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=/dev/mythnew/swap
  InstallationDate: Installed on 2016-07-02 (913 days ago)
  InstallationMedia: Mythbuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp9s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. B450M S2H
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/mythnew-root ro verbose 
drm_kms_helper.edid_firmware=HDMI-A-3:edid/panasonic.edid
  ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-07-27 (158 days ago)
  UserGroups: adm cdrom dip lpadmin mythtv nopasswdlogin plugdev sambashare 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 12/04/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2c
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M S2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2c:bd12/04/2018:svnGigabyteTechnologyCo.,Ltd.:pnB450MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1810239/+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 1777863] Re: [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit

2019-01-02 Thread Haug Bürger
I'm currently running latest Ubuntu version and it didn't happen to me for 
quite some time now:
Linux ZALANDO-27144 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

I can't recall with which update it went away, sorry.

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

Title:
  [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI
  BUF C idle bit

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System reboot. This could be related to putting the NB back into the docking 
station.
  Search for [ cut here ] to find the final error 
message before reboot.

  Linux mymachine4 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16
  UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Using vrefresh ranges from config file
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Printing DDC gathered Modelines:
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "1920x1080"x0.0  148.50  1920 2008 2052 2200  1080 1084 1089 1125 
+hsync +vsync (67.5 kHz eP)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync 
(37.9 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync 
(37.5 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync 
(31.5 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync 
(31.5 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 
+hsync +vsync (80.0 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync 
+vsync (60.0 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync 
-vsync (48.4 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync 
(46.9 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync 
+vsync (67.5 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 
+hsync +vsync (64.0 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "1600x900"x60.0  119.00  1600 1696 1864 2128  900 901 904 932 -hsync 
+vsync (55.9 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "1920x1080"x60.0  172.80  1920 2040 2248 2576  1080 1081 1084 1118 
-hsync +vsync (67.1 kHz e)
  Jun 20 12:05:18 mymachine kernel: [drm:intel_wait_ddi_buf_idle [i915]] 
*ERROR* Timeout waiting for DDI BUF C idle bit
  Jun 20 12:05:18 mymachine kernel: [ cut here ]
  Jun 20 12:05:18 mymachine kernel: vblank wait timed out on crtc 2
  Jun 20 12:05:18 mymachine kernel: WARNING: CPU: 2 PID: 4445 at 
/build/linux-uT8zSN/linux-4.15.0/drivers/gpu/drm/drm_vblank.c:1073 
drm_wait_one_vblank+0x181/0x190 [drm]
  Jun 20 12:05:18 mymachine kernel: Modules linked in: msr rfcomm ccm veth 
nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo br_netfilter bridge stp llc 
overlay thunderbolt cmac bnep btusb btrtl btbcm uvcvideo 
  Jun 20 12:05:18 mymachine kernel:  intel_cstate mac80211 intel_rapl_perf 
snd_compress ac97_bus snd_pcm_dmaengine snd_seq_midi snd_seq_midi_event 
snd_hda_intel snd_rawmidi snd_hda_codec snd_hda_core snd_hwdep i
  Jun 20 12:05:18 mymachine kernel:  pps_core drm nvme_core wmi video
  Jun 20 12:05:18 mymachine kernel: CPU: 2 PID: 4445 Comm: Xorg Tainted: G  
  W4.15.0-23-generic #25-Ubuntu
  Jun 20 12:05:18 mymachine kernel: Hardware name: LENOVO 
20HGS30X00/20HGS30X00, BIOS N1WET34W (1.13 ) 06/26/2017
  Jun 20 12:05:18 mymachine kernel: RIP: 0010:drm_wait_one_vblank+0x181/0x190 
[drm]
  Jun 20 12:05:18 mymachine kernel: RSP: 0018:a32ac3b83a68 EFLAGS: 00010282
  Jun 20 12:05:18 mymachine kernel: RAX:  RBX: 8c5175a38000 
RCX: 0006
  Jun 20 12:05:18 mymachine kernel: RDX: 0007 RSI: 0096 
RDI: 8c519e516490
 

[Kernel-packages] [Bug 1810202] Re: allow a patch that makes elder radeon cards UltraHD ready

2019-01-02 Thread Estellnb
No, that seems to be an error. I have again once more changed it to be
filed against the linux kernel.

** Package changed: libreoffice (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/1810202

Title:
  allow a patch that makes elder radeon cards UltraHD ready

Status in linux package in Ubuntu:
  New

Bug description:
In March 2016 I had developed a kernel patch that allows to set the TMDS 
frequency for Radeon cards by a new kernel parameter called radeon.hdmimhz if 
the automatically set frequency stays either behind of what has been advertised 
for the card or by what is achievable through overclocking. A similar parameter 
for Nvidia/Nouveau cards is already available somewhat longer. There exists a 
patched ATI driver even for Windows. However up to now the patch has not been 
accepted into the mainline kernel simply because Radeon developers are not 
encouraged to enable this feature for elder cards by the policy of their 
sponsors. Here are some of my considerations which you may take into account 
when deciding about the acceptance of the patch for Ubuntu:
 * the patch is very simple, just a few lines of code
 * behaviour of the kernel is not influenced by the patch except when the 
user gives a non-zero value for radeon.hdmimhz
 * the patch has already wheathered time; the surrounding code has more or 
less remained unchanged since March
 * long time usage experience is available at least with the Radeon R5 230 
and the Radeon HD 6770 cards (no heast issues) as well as different monitors; 
my personal experience with the patch is very good
 * the patch provides a huge advantage at least for all people who still 
use Core 2 based systems:
   - elder Radeon cards can be made UHD ready
   - the R5 230 card supported by the patch may be the only one of its type 
that has a single slot height - and it has been sold to me as DVI-UltraHD 
ready; however this feature can not be exploited without the kernel patch
   - newer Radeon cards are often incompatible with elder Core 2 systems
 * at least Nouveau developers say that by overclocking your TMDS it would 
hardly be possible to damage a card even if it shows heat issues; a way of 
proceeding considered safe can be read in the linked article 
https://www.elstel.org/software/hunt-for-4K-UHD-2160p.html.en. The patch can 
also be found on this website; see also: 
https://bugs.freedesktop.org/show_bug.cgi?id=93885#c24. Mageia was the first 
distribution to accept this patch. The patch is safe and has been proven useful 
(since then many people with positive experience have linked to my site) - so 
why do we not include it for Ubuntu?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810202/+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 1809872] Re: btrfs send / receive command with -f argument position in btrfs_kernel_fixes is causing failures on B

2019-01-02 Thread Po-Hsu Lin
https://kernel.ubuntu.com/git/ubuntu/autotest-client-
tests.git/commit/?id=058bd865bd27b2b2fc097c6e490b38b0891141f6

** Changed in: ubuntu-kernel-tests
   Status: In Progress => 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/1809872

Title:
  btrfs send / receive command with -f argument position in
  btrfs_kernel_fixes is causing failures on B

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Invalid

Bug description:
  This issue is different from bug 1809869.

  Test failed with:
  ERROR: unable to resolve -f
  And:
  btrfs receive: too many arguments

  This patch does exist in Bionic kernel tree.

  
  Invoking test 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5

  fix 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5

  Btrfs: send, don't send rmdir for same target multiple times

  When doing an incremental send, if we delete a directory that has N > 1
  hardlinks for the same file and that file has the highest inode number
  inside the directory contents, an incremental send would send N times an
  rmdir operation against the directory. This made the btrfs receive command
  fail on the second rmdir instruction, as the target directory didn't exist
  anymore.

  btrfs-progs v4.15.1
  See http://btrfs.wiki.kernel.org for more information.

  Performing full device TRIM /dev/loop0 (1.00GiB) ...
  Label:  (null)
  UUID:   b9297d7d-f8b6-469e-b3c5-64ac1bf1e3d8
  Node size:  16384
  Sector size:4096
  Filesystem size:1.00GiB
  Block group profiles:
Data: single8.00MiB
Metadata: DUP  51.19MiB
System:   DUP   8.00MiB
  SSD detected:   no
  Incompat features:  extref, skinny-metadata
  Number of devices:  1
  Devices:
 IDSIZE  PATH
  1 1.00GiB  /dev/loop0

  Create a readonly snapshot of 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5' in 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap1'
  ERROR: unable to resolve -f
  Create a readonly snapshot of 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5' in 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap2'
  ERROR: unable to resolve -f
  btrfs-progs v4.15.1
  See http://btrfs.wiki.kernel.org for more information.

  Performing full device TRIM /dev/loop0 (1.00GiB) ...
  Label:  (null)
  UUID:   e6351943-c767-4339-b662-609e80dae55b
  Node size:  16384
  Sector size:4096
  Filesystem size:1.00GiB
  Block group profiles:
Data: single8.00MiB
Metadata: DUP  51.19MiB
System:   DUP   8.00MiB
  SSD detected:   no
  Incompat features:  extref, skinny-metadata
  Number of devices:  1
  Devices:
 IDSIZE  PATH
  1 1.00GiB  /dev/loop0

  btrfs receive: too many arguments
  usage: btrfs receive [options] 
 btrfs receive --dump [options]

  Receive subvolumes from a stream

  Receives one or more subvolumes that were previously
  sent with btrfs send. The received subvolumes are stored
  into MOUNT.
  The receive will fail in case the receiving subvolume
  already exists. It will also fail in case a previously
  received subvolume has been changed after it was received.
  After receiving a subvolume, it is immediately set to
  read-only.

  -v   increase verbosity about performed actions
  -f FILE  read the stream from FILE instead of stdin
  -e   terminate after receiving an  marker in the 
stream.
   Without this option the receiver side terminates only in 
case
   of an error on end of file.
  -C|--chroot  confine the process to  using chroot
  -E|--max-errors NERR
   terminate as soon as NERR errors occur while
   stream processing commands from the stream.
   Default value is 1. A value of 0 means no limit.
  -m ROOTMOUNT the root mount point of the destination filesystem.
   If /proc is not accessible, use this to tell us where
   this file system is mounted.
  --dump   dump stream metadata, one line per operation,
   does not require the MOUNT parameter

  btrfs receive: too many arguments
  usage: btrfs receive [options] 
 btrfs receive --dump [options]

  Receive subvolumes from a stream

  Receives one or more subvolumes that were previously
  sent with btrfs send. The received subvolumes are stored
  into MOUNT.
  The receive will fail in case the receiving subvolume
  already exists. It will also fail in case a previously
  received subvolume has been changed after it was 

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

2019-01-02 Thread 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 1810276

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

Title:
  bcache TRIM support buggy - mkfs.ext4 error discarding blocks

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Sorry that this is a little vague, I ran into it and didn't run it
  down to ground; this was on the cosmic daily server installer build.


  hardware: 4 HDD;s, 1 NVMe SSD.

  configuration: 1x 512MB ESP per drive, then for the HDDs the second partition 
for an mdraid raid5 set. 
  layered on that, bcache with the SSD as cache, and md0 as backing
  layered on that, lvm with one big vg and a lv for root
  mkfs.ext4 on that lv would break, as a TRIM command it issued would error in 
bcache.

  The cache was constructed like so: make-bcache -o 7741440 -w 2k -B
  /dev/md127 -C /dev/nvme0n1p2

  I'm not familiar enough with TRIM/discard to know whether commands
  /layers are meant to not issue them unless supported, or whether they
  should be issued and discarded; either way something breaks here -
  bcache may be incorrectly advertising that bcache0 supports trim, or
  lvm may be checking in the wrong way, or mkfs.ext4 etc etc.

  Though I can rule mkfs.ext4 out - lvremove also issues a discard and
  fails in the same way.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810276/+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 1810202] [NEW] allow a patch that makes elder radeon cards UltraHD ready

2019-01-02 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

  In March 2016 I had developed a kernel patch that allows to set the TMDS 
frequency for Radeon cards by a new kernel parameter called radeon.hdmimhz if 
the automatically set frequency stays either behind of what has been advertised 
for the card or by what is achievable through overclocking. A similar parameter 
for Nvidia/Nouveau cards is already available somewhat longer. There exists a 
patched ATI driver even for Windows. However up to now the patch has not been 
accepted into the mainline kernel simply because Radeon developers are not 
encouraged to enable this feature for elder cards by the policy of their 
sponsors. Here are some of my considerations which you may take into account 
when deciding about the acceptance of the patch for Ubuntu:
   * the patch is very simple, just a few lines of code
   * behaviour of the kernel is not influenced by the patch except when the 
user gives a non-zero value for radeon.hdmimhz
   * the patch has already wheathered time; the surrounding code has more or 
less remained unchanged since March
   * long time usage experience is available at least with the Radeon R5 230 
and the Radeon HD 6770 cards (no heast issues) as well as different monitors; 
my personal experience with the patch is very good
   * the patch provides a huge advantage at least for all people who still use 
Core 2 based systems:
 - elder Radeon cards can be made UHD ready
 - the R5 230 card supported by the patch may be the only one of its type 
that has a single slot height - and it has been sold to me as DVI-UltraHD 
ready; however this feature can not be exploited without the kernel patch
 - newer Radeon cards are often incompatible with elder Core 2 systems
   * at least Nouveau developers say that by overclocking your TMDS it would 
hardly be possible to damage a card even if it shows heat issues; a way of 
proceeding considered safe can be read in the linked article 
https://www.elstel.org/software/hunt-for-4K-UHD-2160p.html.en. The patch can 
also be found on this website; see also: 
https://bugs.freedesktop.org/show_bug.cgi?id=93885#c24. Mageia was the first 
distribution to accept this patch. The patch is safe and has been proven useful 
(since then many people with positive experience have linked to my site) - so 
why do we not include it for Ubuntu?

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

-- 
allow a patch that makes elder radeon cards UltraHD ready
https://bugs.launchpad.net/bugs/1810202
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 1810239] Re: amd_iommu conflict with Marvell Sata controller

2019-01-02 Thread Steven Ellis
** Bug watch added: Debian Bug tracker #700975
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700975

** Also affects: linux (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700975
   Importance: Unknown
   Status: Unknown

** Bug watch added: Red Hat Bugzilla #1337313
   https://bugzilla.redhat.com/show_bug.cgi?id=1337313

** Also affects: linux (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1337313
   Importance: Unknown
   Status: Unknown

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

Title:
  amd_iommu conflict with  Marvell Sata controller

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in linux package in Debian:
  Unknown
Status in linux package in Fedora:
  Unknown

Bug description:
  This bug is to confirm that the Marvell 88SE9230 chipset bug presents
  under AMD's IOMMU implementation with Ubuntu 18.04 and the latest HWE
  Kernel

  This has similar characteristics to 
   - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1089768

  System
   - AMD Athlon 200GE
   - Gigabyte GA-B450M-S2H board
   - Marvell 88SE9230 SATA Controller with latest Firmware

  Kernel
   - Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17

  
  If I boot the HWE 4.18.0-13-generic Kernel I get the errors reported above

  If I boot with "amd_iommu=off" the drives appear to work correctly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mythfe 1170 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=/dev/mythnew/swap
  InstallationDate: Installed on 2016-07-02 (913 days ago)
  InstallationMedia: Mythbuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp9s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. B450M S2H
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/mythnew-root ro verbose 
drm_kms_helper.edid_firmware=HDMI-A-3:edid/panasonic.edid
  ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-07-27 (158 days ago)
  UserGroups: adm cdrom dip lpadmin mythtv nopasswdlogin plugdev sambashare 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 12/04/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2c
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M S2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2c:bd12/04/2018:svnGigabyteTechnologyCo.,Ltd.:pnB450MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1810239/+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 1810267] Re: hard lockup on multiple CPUs in spl_cache_flush

2019-01-02 Thread Robert Collins
** Description changed:

- Photo of failed machine at https://photos.app.goo.gl/UGofDoh2DdDvNTMM8
+ Photo of failed machine, and video of a second lockup at
+ https://photos.app.goo.gl/9qUxysZ4LN1NRdrA7
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D7p', 
'/dev/snd/controlC1', '/dev/snd/pcmC2D3p', '/dev/snd/controlC2', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Date: Wed Jan  2 20:14:38 2019
  InstallationDate: Installed on 2013-12-09 (1850 days ago)
  InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 
(20131016)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
-  LANGUAGE=en_NZ:en
-  TERM=xterm
-  PATH=(custom, no user)
-  LANG=en_NZ.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_NZ:en
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=en_NZ.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-43-generic 
root=ZFS=tr2srv/ROOT/ubuntu ro nomdmonddf nomdmonisw
  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.
+  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-43-generic N/A
-  linux-backports-modules-4.15.0-43-generic  N/A
-  linux-firmware 1.173.2
+  linux-restricted-modules-4.15.0-43-generic N/A
+  linux-backports-modules-4.15.0-43-generic  N/A
+  linux-firmware 1.173.2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-06-26 (189 days ago)
  dmi.bios.date: 10/12/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0808
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X399-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0808:bd10/12/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX399-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  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

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

Title:
  hard lockup on multiple CPUs in spl_cache_flush

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Photo of failed machine, and video of a second lockup at
  https://photos.app.goo.gl/9qUxysZ4LN1NRdrA7

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D7p', 
'/dev/snd/controlC1', '/dev/snd/pcmC2D3p', '/dev/snd/controlC2', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Date: Wed Jan  2 20:14:38 2019
  InstallationDate: Installed on 2013-12-09 (1850 days ago)
  InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 
(20131016)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_NZ:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-43-generic 
root=ZFS=tr2srv/ROOT/ubuntu ro nomdmonddf nomdmonisw
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not

[Kernel-packages] [Bug 1810276] [NEW] bcache TRIM support buggy - mkfs.ext4 error discarding blocks

2019-01-02 Thread Robert Collins
Public bug reported:

Sorry that this is a little vague, I ran into it and didn't run it down
to ground; this was on the cosmic daily server installer build.


hardware: 4 HDD;s, 1 NVMe SSD.

configuration: 1x 512MB ESP per drive, then for the HDDs the second partition 
for an mdraid raid5 set. 
layered on that, bcache with the SSD as cache, and md0 as backing
layered on that, lvm with one big vg and a lv for root
mkfs.ext4 on that lv would break, as a TRIM command it issued would error in 
bcache.

The cache was constructed like so: make-bcache -o 7741440 -w 2k -B
/dev/md127 -C /dev/nvme0n1p2

I'm not familiar enough with TRIM/discard to know whether commands
/layers are meant to not issue them unless supported, or whether they
should be issued and discarded; either way something breaks here -
bcache may be incorrectly advertising that bcache0 supports trim, or lvm
may be checking in the wrong way, or mkfs.ext4 etc etc.

Though I can rule mkfs.ext4 out - lvremove also issues a discard and
fails in the same way.

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

Title:
  bcache TRIM support buggy - mkfs.ext4 error discarding blocks

Status in linux package in Ubuntu:
  New

Bug description:
  Sorry that this is a little vague, I ran into it and didn't run it
  down to ground; this was on the cosmic daily server installer build.


  hardware: 4 HDD;s, 1 NVMe SSD.

  configuration: 1x 512MB ESP per drive, then for the HDDs the second partition 
for an mdraid raid5 set. 
  layered on that, bcache with the SSD as cache, and md0 as backing
  layered on that, lvm with one big vg and a lv for root
  mkfs.ext4 on that lv would break, as a TRIM command it issued would error in 
bcache.

  The cache was constructed like so: make-bcache -o 7741440 -w 2k -B
  /dev/md127 -C /dev/nvme0n1p2

  I'm not familiar enough with TRIM/discard to know whether commands
  /layers are meant to not issue them unless supported, or whether they
  should be issued and discarded; either way something breaks here -
  bcache may be incorrectly advertising that bcache0 supports trim, or
  lvm may be checking in the wrong way, or mkfs.ext4 etc etc.

  Though I can rule mkfs.ext4 out - lvremove also issues a discard and
  fails in the same way.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810276/+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 1809748] Re: 8k bcache NULL pointer deref on mount / can't boot

2019-01-02 Thread Robert Collins
hint if testing this - add module_blacklist=bcache to your kernel boot
line to boot and reset the metadata :)

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

Title:
  8k bcache NULL pointer deref on mount / can't boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After creating a bcache cache device with an 8k block size (see
  #1662407), a kernel oops happens every time device is probed.

  I'm not sure that there is any userspace bug present in #1662407 at
  all - it may just be kernel. I've attached a dmesg there, but can't
  actually get into the system at the moment to get apport-collect or
  other diagnostics.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809748/+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 1808768] Re: Initrd of pc-kernel snap contains out-of-date packages

2019-01-02 Thread Jesse Sung
** Tags added: dawson originate-from-1808480

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

Title:
  Initrd of pc-kernel snap contains out-of-date packages

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

Bug description:
  The build script does not install package updates during generate the
  pc-kernel snap.

  I met this bug #1783810 when I was verify my Ubuntu Core 18 image on KVM.
  The system stuck at resizing the writable partition. the resize script of 
initrd called sgdisk to achieve the resizing. Inside sgdisk, it use libuuid1 to 
get random bytes and generate UUIDs. After I extracted the kernel snap, I found 
it is still using libuuid1 2.31.1-0.4ubuntu3 which is not the latest version. 
At this moment, Bionic has 2.31.1-0.4ubuntu3.2.
  Then I added commands to make the build script installing package updates. 
After that, the system can boot correctly without any problem.

  I am wondering if there is any concern to pull updates before
  building?

  The attachment is my patch to pull updates.

  Snippet of console output, before patch
  [2.491404] usbcore: registered new interface driver usb-storage
  [2.503788] sdhci: Secure Digital Host Controller Interface driver
  [2.505627] sdhci: Copyright(c) Pierre Ossman
  [2.548485] initrd: found more than 10% free space on disk, resizing 
/dev/sda3
  [2.550345] initrd: partition to full disk size, see /dev/kmsg for details
  [2.912472] clocksource: tsc: mask: 0x max_cycles: 
0x255b2dea34c, max_idle_ns: 440795243480 ns
  ## several keystrokes here, or the boot process won't continue
  [  351.361426] random: crng init done
  [  351.423462] fixing backup GPT
  [  352.435735] systemd-udevd[240]: passed device to netlink monitor 
0x55e45653e330
  [  352.443221]  sda: sda1 sda2 sda3
  [  352.445486] The operation has completed successfully.

  Snippet of console output, after patch
  [2.548203] usbcore: registered new interface driver usb-storage
  [2.561439] sdhci: Secure Digital Host Controller Interface driver
  [2.562878] sdhci: Copyright(c) Pierre Ossman
  [2.602093] initrd: found more than 10% free space on disk, resizing 
/dev/sda3
  [2.603900] initrd: partition to full disk size, see /dev/kmsg for details
  ## block a few seconds, until timeout.
  [2.912418] clocksource: tsc: mask: 0x max_cycles: 
0x255b2dea34c, max_idle_ns: 440795243480 ns
  [9.174552] random: fast init done
  [9.179127] random: parted: uninitialized urandom read (16 bytes read)
  [9.183726] random: parted: uninitialized urandom read (16 bytes read)
  [9.190606] random: parted: uninitialized urandom read (16 bytes read)
  [9.230419] fixing backup GPT
  [9.236989] random: crng init done
  [9.238102] random: 5 urandom warning(s) missed due to ratelimiting
  [   10.245047] systemd-udevd[259]: passed device to netlink monitor 
0x56376c45b150
  [   10.253093]  sda: sda1 sda2 sda3
  [   10.256202] The operation has completed successfully.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1808768/+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