[Kernel-packages] [Bug 1812159] Re: SCHED_STACK_END_CHECK should be enabled in B-kvm

2019-01-16 Thread Po-Hsu Lin
This option checks for a stack overrun on calls to schedule(). If the
stack end location is found to be over written always panic as the
content of the corrupted region can no longer be trusted. This is to
ensure no erroneous behaviour occurs which could result in data
corruption or a sporadic crash at a later stage once the region is
examined. The runtime overhead introduced is minimal.

Ref: https://cateee.net/lkddb/web-lkddb/SCHED_STACK_END_CHECK.html

Looks like this is debug related, not sure if we want this on KVM
kernels.

** 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-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1812159

Title:
  SCHED_STACK_END_CHECK should be enabled in B-kvm

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

Bug description:
  The test_380_config_sched_stack_end_check test failed on the Bionic
  KVM kernel

FAIL: test_380_config_sched_stack_end_check 
(__main__.KernelSecurityConfigTest)
Ensure SCHED_STACK_END_CHECK is set
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2628, in 
test_380_config_sched_stack_end_check
self.assertKernelConfig('SCHED_STACK_END_CHECK', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: SCHED_STACK_END_CHECK option was expected to be set in 
the kernel config

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28
  ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18
  Uname: Linux 4.15.0-1028-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Thu Jan 17 06:44:41 2019
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1811417] Re: linux-kvm: 4.18.0-1007.7 -proposed tracker

2019-01-16 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811406
- phase: Testing -- verification-testing in progress
- phase-changed: Thursday, 17. January 2019 07:07 UTC
+ phase: Testing -- regression-testing in progress
+ phase-changed: Thursday, 17. January 2019 07:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-kvm: 4.18.0-1007.7 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811406
  phase: Testing -- regression-testing in progress
  phase-changed: Thursday, 17. January 2019 07:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811417/+subscriptions

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


[Kernel-packages] [Bug 1812086] Re: kernel BUG at /build/linux-vxxS7y/linux-4.15.0/mm/slub.c:296!

2019-01-16 Thread Juerg Haefliger
** 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/1812086

Title:
  kernel BUG at /build/linux-vxxS7y/linux-4.15.0/mm/slub.c:296!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Rebooting an iSCSI target while the initiator is writing to a LUN
  leads to the following trace:

  [   59.879202] [ cut here ]
  [   59.879202] kernel BUG at /build/linux-vxxS7y/linux-4.15.0/mm/slub.c:296!
  [   59.880636] invalid opcode:  [#1] SMP PTI
  [   59.881569] Modules linked in: iscsi_target_mod target_core_pscsi 
target_core_file target_core_iblock target_core_user uio target_core_mod 
nls_iso8859_1 kvm_intel isofs kvm irqbypass joydev input_leds serio_raw 
sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp 
libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear psmouse virtio_blk virtio_net 
floppy
  [   59.891096] CPU: 0 PID: 1027 Comm: iscsi_np Not tainted 4.15.0-43-generic 
#46-Ubuntu
  [   59.892726] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.11.1-1ubuntu1 04/01/2014
  [   59.894606] RIP: 0010:kfree+0x16a/0x180
  [   59.895429] RSP: 0018:ac0d8050fe58 EFLAGS: 00010246
  [   59.896531] RAX: 9cf099475800 RBX: 9cf099475800 RCX: 
9cf099475800
  [   59.898083] RDX: 00011bbb RSI: 9cf09fc27140 RDI: 
9cf09f002000
  [   59.899627] RBP: ac0d8050fe70 R08:  R09: 
c07a329b
  [   59.901186] R10: e95780651d40 R11: a511dc90 R12: 
9cf099625600
  [   59.902769] R13: c07a329b R14: 9cf09ee07600 R15: 
9cf099475800
  [   59.904321] FS:  () GS:9cf09fc0() 
knlGS:
  [   59.906120] CS:  0010 DS:  ES:  CR0: 80050033
  [   59.907806] CR2: 7f7153b88470 CR3: 1babe000 CR4: 
06f0
  [   59.909376] DR0:  DR1:  DR2: 

  [   59.910950] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   59.913098] Call Trace:
  [   59.913783]  iscsi_target_login_sess_out+0x1fb/0x250 [iscsi_target_mod]
  [   59.915292]  iscsi_target_login_thread+0x44d/0x1060 [iscsi_target_mod]
  [   59.916775]  kthread+0x121/0x140
  [   59.917622]  ? iscsi_target_login_sess_out+0x250/0x250 [iscsi_target_mod]
  [   59.919244]  ? kthread_create_worker_on_cpu+0x70/0x70
  [   59.920483]  ? do_syscall_64+0x73/0x130
  [   59.921460]  ? SyS_exit_group+0x14/0x20
  [   59.922583]  ret_from_fork+0x35/0x40
  [   59.923523] Code: c4 80 74 04 41 8b 72 6c 4c 89 d7 e8 61 1c f9 ff eb 86 41 
b8 01 00 00 00 48 89 d9 48 89 da 4c 89 d6 e8 8b f6 ff ff e9 6d ff ff ff <0f> 0b 
48 8b 3d 6d c4 1c 01 e9 c9 fe ff ff 0f 1f 84 00 00 00 00 
  [   59.927778] RIP: kfree+0x16a/0x180 RSP: ac0d8050fe58
  [   59.929063] ---[ end trace 082da4d341633d3e ]---

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

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


[Kernel-packages] [Bug 1811425] Re: linux-kvm: 4.15.0-1029.29 -proposed tracker

2019-01-16 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811419
- phase: Testing -- verification-testing in progress
- phase-changed: Thursday, 17. January 2019 07:01 UTC
+ phase: Testing -- regression-testing in progress
+ phase-changed: Thursday, 17. January 2019 07:34 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-kvm: 4.15.0-1029.29 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811419
  phase: Testing -- regression-testing in progress
  phase-changed: Thursday, 17. January 2019 07:34 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811425/+subscriptions

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


[Kernel-packages] [Bug 1812161] Re: Screen backlight control does not work in Disco on Dell XPS 9560

2019-01-16 Thread Daniel van Vugt
Rocko,

You seem to have some newer kernels installed. Does booting those have
the same problem?

Also, maybe you can try downgrading to cosmic's upower version: 
  https://launchpad.net/ubuntu/+source/upower/0.99.8-2ubuntu0.1
to see if it was a regression in upower.

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

** Changed in: upower (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/1812161

Title:
  Screen backlight control does not work in Disco on Dell XPS 9560

Status in linux package in Ubuntu:
  Incomplete
Status in upower package in Ubuntu:
  Incomplete

Bug description:
  When I press the screen backlight up/down buttons, gnome-shell pops up
  the backlight control window saying that the backlight is being
  adjusted, but the actual screen brightness does not change.

  The problem is that gnome is adjusting
  /sys/class/backlight/acpi_video0/brightness instead of
  /sys/class/backlight/intel_backlight/brightness. If I manually change
  the latter as root with, say:

  root@xps-9560:~ echo 600 >
  /sys/class/backlight/intel_backlight/brightness

  then the brightness changes.

  The brightness control worked fine in Cosmic on this laptop, so this
  is a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 17 14:47:37 2019
  DistUpgraded: 2019-01-15 23:10:12,938 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.18.0-13-generic, x86_64: installed
   bbswitch, 0.8, 4.20.0-042000-generic, x86_64: installed
   bbswitch, 0.8, 4.20.3-042003-generic, x86_64: installed
   nvidia, 415.27, 4.20.0-042000-generic, x86_64: installed
   nvidia, 415.27, 4.20.3-042003-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:07be]
 Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be]
  InstallationDate: Installed on 2017-08-16 (518 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. XPS 15 9560
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-13-generic 
root=UUID=0eb64261-6dff-464a-8373-596794c1fafe ro rootflags=subvol=@ quiet 
splash acpi_rev_override=5 scsi_mod.use_blk_mq=1 i915.modeset=1 nouveau.runpm=0 
rcutree.rcu_idle_gp_delay=1 acpi_osi=! "acpi_osi=Windows 2009"
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-01-15 (1 days ago)
  dmi.bios.date: 10/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  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.12.1:bd10/02/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.product.sku: 07BE
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+19.04.20190103-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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


[Kernel-packages] [Bug 1812161] Re: Screen backlight control does not work in Disco on Dell XPS 9560

2019-01-16 Thread Daniel van Vugt
Ah, yes, Kai-Heng Feng probably makes a better point in comment #2.

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

Title:
  Screen backlight control does not work in Disco on Dell XPS 9560

Status in linux package in Ubuntu:
  Incomplete
Status in upower package in Ubuntu:
  Incomplete

Bug description:
  When I press the screen backlight up/down buttons, gnome-shell pops up
  the backlight control window saying that the backlight is being
  adjusted, but the actual screen brightness does not change.

  The problem is that gnome is adjusting
  /sys/class/backlight/acpi_video0/brightness instead of
  /sys/class/backlight/intel_backlight/brightness. If I manually change
  the latter as root with, say:

  root@xps-9560:~ echo 600 >
  /sys/class/backlight/intel_backlight/brightness

  then the brightness changes.

  The brightness control worked fine in Cosmic on this laptop, so this
  is a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 17 14:47:37 2019
  DistUpgraded: 2019-01-15 23:10:12,938 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.18.0-13-generic, x86_64: installed
   bbswitch, 0.8, 4.20.0-042000-generic, x86_64: installed
   bbswitch, 0.8, 4.20.3-042003-generic, x86_64: installed
   nvidia, 415.27, 4.20.0-042000-generic, x86_64: installed
   nvidia, 415.27, 4.20.3-042003-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:07be]
 Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be]
  InstallationDate: Installed on 2017-08-16 (518 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. XPS 15 9560
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-13-generic 
root=UUID=0eb64261-6dff-464a-8373-596794c1fafe ro rootflags=subvol=@ quiet 
splash acpi_rev_override=5 scsi_mod.use_blk_mq=1 i915.modeset=1 nouveau.runpm=0 
rcutree.rcu_idle_gp_delay=1 acpi_osi=! "acpi_osi=Windows 2009"
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-01-15 (1 days ago)
  dmi.bios.date: 10/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  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.12.1:bd10/02/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.product.sku: 07BE
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+19.04.20190103-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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


[Kernel-packages] [Bug 1812161] Re: Screen backlight control does not work in Disco on Dell XPS 9560

2019-01-16 Thread Kai-Heng Feng
Please remove all acpi* kernel parameters and see if it helps.

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

Title:
  Screen backlight control does not work in Disco on Dell XPS 9560

Status in linux package in Ubuntu:
  Incomplete
Status in upower package in Ubuntu:
  Incomplete

Bug description:
  When I press the screen backlight up/down buttons, gnome-shell pops up
  the backlight control window saying that the backlight is being
  adjusted, but the actual screen brightness does not change.

  The problem is that gnome is adjusting
  /sys/class/backlight/acpi_video0/brightness instead of
  /sys/class/backlight/intel_backlight/brightness. If I manually change
  the latter as root with, say:

  root@xps-9560:~ echo 600 >
  /sys/class/backlight/intel_backlight/brightness

  then the brightness changes.

  The brightness control worked fine in Cosmic on this laptop, so this
  is a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 17 14:47:37 2019
  DistUpgraded: 2019-01-15 23:10:12,938 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.18.0-13-generic, x86_64: installed
   bbswitch, 0.8, 4.20.0-042000-generic, x86_64: installed
   bbswitch, 0.8, 4.20.3-042003-generic, x86_64: installed
   nvidia, 415.27, 4.20.0-042000-generic, x86_64: installed
   nvidia, 415.27, 4.20.3-042003-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:07be]
 Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be]
  InstallationDate: Installed on 2017-08-16 (518 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. XPS 15 9560
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-13-generic 
root=UUID=0eb64261-6dff-464a-8373-596794c1fafe ro rootflags=subvol=@ quiet 
splash acpi_rev_override=5 scsi_mod.use_blk_mq=1 i915.modeset=1 nouveau.runpm=0 
rcutree.rcu_idle_gp_delay=1 acpi_osi=! "acpi_osi=Windows 2009"
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-01-15 (1 days ago)
  dmi.bios.date: 10/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  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.12.1:bd10/02/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.product.sku: 07BE
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+19.04.20190103-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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


[Kernel-packages] [Bug 1812161] Re: Screen backlight control does not work in Disco on Dell XPS 9560

2019-01-16 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => linux (Ubuntu)

** Also affects: upower (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/1812161

Title:
  Screen backlight control does not work in Disco on Dell XPS 9560

Status in linux package in Ubuntu:
  Incomplete
Status in upower package in Ubuntu:
  Incomplete

Bug description:
  When I press the screen backlight up/down buttons, gnome-shell pops up
  the backlight control window saying that the backlight is being
  adjusted, but the actual screen brightness does not change.

  The problem is that gnome is adjusting
  /sys/class/backlight/acpi_video0/brightness instead of
  /sys/class/backlight/intel_backlight/brightness. If I manually change
  the latter as root with, say:

  root@xps-9560:~ echo 600 >
  /sys/class/backlight/intel_backlight/brightness

  then the brightness changes.

  The brightness control worked fine in Cosmic on this laptop, so this
  is a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 17 14:47:37 2019
  DistUpgraded: 2019-01-15 23:10:12,938 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.18.0-13-generic, x86_64: installed
   bbswitch, 0.8, 4.20.0-042000-generic, x86_64: installed
   bbswitch, 0.8, 4.20.3-042003-generic, x86_64: installed
   nvidia, 415.27, 4.20.0-042000-generic, x86_64: installed
   nvidia, 415.27, 4.20.3-042003-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:07be]
 Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be]
  InstallationDate: Installed on 2017-08-16 (518 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. XPS 15 9560
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-13-generic 
root=UUID=0eb64261-6dff-464a-8373-596794c1fafe ro rootflags=subvol=@ quiet 
splash acpi_rev_override=5 scsi_mod.use_blk_mq=1 i915.modeset=1 nouveau.runpm=0 
rcutree.rcu_idle_gp_delay=1 acpi_osi=! "acpi_osi=Windows 2009"
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-01-15 (1 days ago)
  dmi.bios.date: 10/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  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.12.1:bd10/02/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.product.sku: 07BE
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+19.04.20190103-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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


[Kernel-packages] [Bug 1812161] [NEW] Screen backlight control does not work in Disco on Dell XPS 9560

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

When I press the screen backlight up/down buttons, gnome-shell pops up
the backlight control window saying that the backlight is being
adjusted, but the actual screen brightness does not change.

The problem is that gnome is adjusting
/sys/class/backlight/acpi_video0/brightness instead of
/sys/class/backlight/intel_backlight/brightness. If I manually change
the latter as root with, say:

root@xps-9560:~ echo 600 >
/sys/class/backlight/intel_backlight/brightness

then the brightness changes.

The brightness control worked fine in Cosmic on this laptop, so this is
a regression.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.10-0ubuntu18
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 17 14:47:37 2019
DistUpgraded: 2019-01-15 23:10:12,938 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: disco
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.18.0-13-generic, x86_64: installed
 bbswitch, 0.8, 4.20.0-042000-generic, x86_64: installed
 bbswitch, 0.8, 4.20.3-042003-generic, x86_64: installed
 nvidia, 415.27, 4.20.0-042000-generic, x86_64: installed
 nvidia, 415.27, 4.20.3-042003-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:07be]
   Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be]
InstallationDate: Installed on 2017-08-16 (518 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: Dell Inc. XPS 15 9560
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-13-generic 
root=UUID=0eb64261-6dff-464a-8373-596794c1fafe ro rootflags=subvol=@ quiet 
splash acpi_rev_override=5 scsi_mod.use_blk_mq=1 i915.modeset=1 nouveau.runpm=0 
rcutree.rcu_idle_gp_delay=1 acpi_osi=! "acpi_osi=Windows 2009"
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to disco on 2019-01-15 (1 days ago)
dmi.bios.date: 10/02/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.12.1
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.12.1:bd10/02/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9560
dmi.product.sku: 07BE
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+19.04.20190103-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-2ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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


** Tags: amd64 apport-bug disco gnome-shell regression reproducible 
third-party-packages ubuntu
-- 
Screen backlight control does not work in Disco on Dell XPS 9560
https://bugs.launchpad.net/bugs/1812161
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 1811417] Re: linux-kvm: 4.18.0-1007.7 -proposed tracker

2019-01-16 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811406
- phase: Testing -- regression-testing in progress
- phase-changed: Thursday, 17. January 2019 03:33 UTC
+ phase: Testing -- verification-testing in progress
+ phase-changed: Thursday, 17. January 2019 07:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-kvm: 4.18.0-1007.7 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811406
  phase: Testing -- verification-testing in progress
  phase-changed: Thursday, 17. January 2019 07:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811417/+subscriptions

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


[Kernel-packages] [Bug 1812163] Re: package linux-firmware 1.173.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2019-01-16 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package linux-firmware 1.173.3 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  ackage linux-firmware 1.173.3 failed to install/upgrade: package is in
  a very bad inconsistent state; you should  reinstall it before
  attempting configuration

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.173.3
  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
  Architecture: amd64
  Date: Thu Jan 17 00:53:58 2019
  Dependencies:
   
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  DpkgHistoryLog:
   Start-Date: 2019-01-17  00:53:03
   Requested-By: yiannis (1001)
   Upgrade: gvfs-backends:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), 
gvfs-bin:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), 
gnome-software-plugin-snap:amd64 (3.28.1-0ubuntu4.18.04.4, 
3.28.1-0ubuntu4.18.04.8), gnome-software:amd64 (3.28.1-0ubuntu4.18.04.4, 
3.28.1-0ubuntu4.18.04.8), gvfs-libs:amd64 (1.36.1-0ubuntu1.1, 
1.36.1-0ubuntu1.2), gvfs-fuse:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), 
ubuntu-software:amd64 (3.28.1-0ubuntu4.18.04.4, 3.28.1-0ubuntu4.18.04.8), 
gvfs:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), gvfs-common:amd64 
(1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), gnome-software-common:amd64 
(3.28.1-0ubuntu4.18.04.4, 3.28.1-0ubuntu4.18.04.8), gvfs-daemons:amd64 
(1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2)
  DuplicateSignature:
   package:linux-firmware:1.173.3
   Processing triggers for hicolor-icon-theme (0.17-2) ...
   dpkg: error processing package linux-firmware (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2013-02-22 (2155 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
  PackageArchitecture: all
  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: linux-firmware
  Title: package linux-firmware 1.173.3 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1812164] Re: package linux-firmware 1.173.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2019-01-16 Thread Apport retracing service
*** This bug is a duplicate of bug 1812163 ***
https://bugs.launchpad.net/bugs/1812163

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1812163, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1812163
   package linux-firmware 1.173.3 failed to install/upgrade: package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration

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

Title:
  package linux-firmware 1.173.3 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  ackage linux-firmware 1.173.3 failed to install/upgrade: package is in
  a very bad inconsistent state; you should  reinstall it before
  attempting configuration

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.173.3
  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
  Architecture: amd64
  Date: Thu Jan 17 00:53:58 2019
  Dependencies:
   
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  DpkgHistoryLog:
   Start-Date: 2019-01-17  00:53:03
   Requested-By: yiannis (1001)
   Upgrade: gvfs-backends:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), 
gvfs-bin:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), 
gnome-software-plugin-snap:amd64 (3.28.1-0ubuntu4.18.04.4, 
3.28.1-0ubuntu4.18.04.8), gnome-software:amd64 (3.28.1-0ubuntu4.18.04.4, 
3.28.1-0ubuntu4.18.04.8), gvfs-libs:amd64 (1.36.1-0ubuntu1.1, 
1.36.1-0ubuntu1.2), gvfs-fuse:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), 
ubuntu-software:amd64 (3.28.1-0ubuntu4.18.04.4, 3.28.1-0ubuntu4.18.04.8), 
gvfs:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), gvfs-common:amd64 
(1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), gnome-software-common:amd64 
(3.28.1-0ubuntu4.18.04.4, 3.28.1-0ubuntu4.18.04.8), gvfs-daemons:amd64 
(1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2)
  DuplicateSignature:
   package:linux-firmware:1.173.3
   Processing triggers for hicolor-icon-theme (0.17-2) ...
   dpkg: error processing package linux-firmware (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2013-02-22 (2155 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
  PackageArchitecture: all
  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: linux-firmware
  Title: package linux-firmware 1.173.3 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1811431] Re: linux-azure: 4.15.0-1037.39~16.04.1 -proposed tracker

2019-01-16 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811419
- phase: Promote to Proposed -- snap release to edge ready
- phase-changed: Thursday, 17. January 2019 06:00 UTC
+ phase: Promote to Proposed -- snap release to beta ready
+ phase-changed: Thursday, 17. January 2019 07:04 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in beta channel
snap-release-to-edge: Pending -- snap not in edge channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.15.0-1037.39~16.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811419
  phase: Promote to Proposed -- snap release to beta ready
  phase-changed: Thursday, 17. January 2019 07:04 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in beta channel
snap-release-to-edge: Pending -- snap not in edge channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811431/+subscriptions

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


[Kernel-packages] [Bug 1811425] Re: linux-kvm: 4.15.0-1029.29 -proposed tracker

2019-01-16 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811419
- phase: Testing -- regression-testing in progress
- phase-changed: Thursday, 17. January 2019 03:38 UTC
+ phase: Testing -- verification-testing in progress
+ phase-changed: Thursday, 17. January 2019 07:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-kvm: 4.15.0-1029.29 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811419
  phase: Testing -- verification-testing in progress
  phase-changed: Thursday, 17. January 2019 07:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811425/+subscriptions

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


[Kernel-packages] [Bug 1812164] [NEW] package linux-firmware 1.173.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2019-01-16 Thread Yiannis
*** This bug is a duplicate of bug 1812163 ***
https://bugs.launchpad.net/bugs/1812163

Public bug reported:

ackage linux-firmware 1.173.3 failed to install/upgrade: package is in a
very bad inconsistent state; you should  reinstall it before attempting
configuration

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-firmware 1.173.3
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
Architecture: amd64
Date: Thu Jan 17 00:53:58 2019
Dependencies:
 
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-precise-amd64-20120703-2
DpkgHistoryLog:
 Start-Date: 2019-01-17  00:53:03
 Requested-By: yiannis (1001)
 Upgrade: gvfs-backends:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), 
gvfs-bin:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), 
gnome-software-plugin-snap:amd64 (3.28.1-0ubuntu4.18.04.4, 
3.28.1-0ubuntu4.18.04.8), gnome-software:amd64 (3.28.1-0ubuntu4.18.04.4, 
3.28.1-0ubuntu4.18.04.8), gvfs-libs:amd64 (1.36.1-0ubuntu1.1, 
1.36.1-0ubuntu1.2), gvfs-fuse:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), 
ubuntu-software:amd64 (3.28.1-0ubuntu4.18.04.4, 3.28.1-0ubuntu4.18.04.8), 
gvfs:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), gvfs-common:amd64 
(1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), gnome-software-common:amd64 
(3.28.1-0ubuntu4.18.04.4, 3.28.1-0ubuntu4.18.04.8), gvfs-daemons:amd64 
(1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2)
DuplicateSignature:
 package:linux-firmware:1.173.3
 Processing triggers for hicolor-icon-theme (0.17-2) ...
 dpkg: error processing package linux-firmware (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2013-02-22 (2155 days ago)
InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
PackageArchitecture: all
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: linux-firmware
Title: package linux-firmware 1.173.3 failed to install/upgrade: package is in 
a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-firmware (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 linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1812164

Title:
  package linux-firmware 1.173.3 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  ackage linux-firmware 1.173.3 failed to install/upgrade: package is in
  a very bad inconsistent state; you should  reinstall it before
  attempting configuration

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.173.3
  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
  Architecture: amd64
  Date: Thu Jan 17 00:53:58 2019
  Dependencies:
   
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  DpkgHistoryLog:
   Start-Date: 2019-01-17  00:53:03
   Requested-By: yiannis (1001)
   Upgrade: gvfs-backends:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), 
gvfs-bin:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), 
gnome-software-plugin-snap:amd64 (3.28.1-0ubuntu4.18.04.4, 
3.28.1-0ubuntu4.18.04.8), gnome-software:amd64 (3.28.1-0ubuntu4.18.04.4, 
3.28.1-0ubuntu4.18.04.8), gvfs-libs:amd64 (1.36.1-0ubuntu1.1, 
1.36.1-0ubuntu1.2), gvfs-fuse:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), 
ubuntu-software:amd64 (3.28.1-0ubuntu4.18.04.4, 3.28.1-0ubuntu4.18.04.8), 
gvfs:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), gvfs-common:amd64 
(1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), gnome-software-common:amd64 
(3.28.1-0ubuntu4.18.04.4, 3.28.1-0ubuntu4.18.04.8), gvfs-daemons:amd64 
(1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2)
  DuplicateSignature:
   package:linux-firmware:1.173.3
   Processing triggers for hicolor-icon-theme (0.17-2) ...
   dpkg: error processing package linux-firmware (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 

[Kernel-packages] [Bug 1811929] Re: Fix not working Goodix touchpad

2019-01-16 Thread Kai-Heng Feng
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  Fix not working Goodix touchpad

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

Bug description:
  [Impact]
  Goodix I2C PTP touchpad doesn't work.

  [Fix]
  Disable runtime PM can fix it.

  [Test]
  I verified the touchpad starts working with the fix.

  [Regression Potential]
  Low. The fix limits to a specific device which doesn't work without it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1811929/+subscriptions

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


[Kernel-packages] [Bug 1812163] [NEW] package linux-firmware 1.173.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2019-01-16 Thread Yiannis
Public bug reported:

ackage linux-firmware 1.173.3 failed to install/upgrade: package is in a
very bad inconsistent state; you should  reinstall it before attempting
configuration

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-firmware 1.173.3
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
Architecture: amd64
Date: Thu Jan 17 00:53:58 2019
Dependencies:
 
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-precise-amd64-20120703-2
DpkgHistoryLog:
 Start-Date: 2019-01-17  00:53:03
 Requested-By: yiannis (1001)
 Upgrade: gvfs-backends:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), 
gvfs-bin:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), 
gnome-software-plugin-snap:amd64 (3.28.1-0ubuntu4.18.04.4, 
3.28.1-0ubuntu4.18.04.8), gnome-software:amd64 (3.28.1-0ubuntu4.18.04.4, 
3.28.1-0ubuntu4.18.04.8), gvfs-libs:amd64 (1.36.1-0ubuntu1.1, 
1.36.1-0ubuntu1.2), gvfs-fuse:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), 
ubuntu-software:amd64 (3.28.1-0ubuntu4.18.04.4, 3.28.1-0ubuntu4.18.04.8), 
gvfs:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), gvfs-common:amd64 
(1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), gnome-software-common:amd64 
(3.28.1-0ubuntu4.18.04.4, 3.28.1-0ubuntu4.18.04.8), gvfs-daemons:amd64 
(1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2)
DuplicateSignature:
 package:linux-firmware:1.173.3
 Processing triggers for hicolor-icon-theme (0.17-2) ...
 dpkg: error processing package linux-firmware (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2013-02-22 (2155 days ago)
InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
PackageArchitecture: all
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: linux-firmware
Title: package linux-firmware 1.173.3 failed to install/upgrade: package is in 
a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-firmware (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 linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1812163

Title:
  package linux-firmware 1.173.3 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  ackage linux-firmware 1.173.3 failed to install/upgrade: package is in
  a very bad inconsistent state; you should  reinstall it before
  attempting configuration

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.173.3
  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
  Architecture: amd64
  Date: Thu Jan 17 00:53:58 2019
  Dependencies:
   
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  DpkgHistoryLog:
   Start-Date: 2019-01-17  00:53:03
   Requested-By: yiannis (1001)
   Upgrade: gvfs-backends:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), 
gvfs-bin:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), 
gnome-software-plugin-snap:amd64 (3.28.1-0ubuntu4.18.04.4, 
3.28.1-0ubuntu4.18.04.8), gnome-software:amd64 (3.28.1-0ubuntu4.18.04.4, 
3.28.1-0ubuntu4.18.04.8), gvfs-libs:amd64 (1.36.1-0ubuntu1.1, 
1.36.1-0ubuntu1.2), gvfs-fuse:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), 
ubuntu-software:amd64 (3.28.1-0ubuntu4.18.04.4, 3.28.1-0ubuntu4.18.04.8), 
gvfs:amd64 (1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), gvfs-common:amd64 
(1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2), gnome-software-common:amd64 
(3.28.1-0ubuntu4.18.04.4, 3.28.1-0ubuntu4.18.04.8), gvfs-daemons:amd64 
(1.36.1-0ubuntu1.1, 1.36.1-0ubuntu1.2)
  DuplicateSignature:
   package:linux-firmware:1.173.3
   Processing triggers for hicolor-icon-theme (0.17-2) ...
   dpkg: error processing package linux-firmware (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2013-02-22 (2155 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 

[Kernel-packages] [Bug 1811777] Re: Fix non-working pinctrl-intel

2019-01-16 Thread Kai-Heng Feng
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  Fix non-working pinctrl-intel

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

Bug description:
  [Impact]
  Intel pinctrl doesn't work.
  There's a WWAN card needs to use pinctrl to reset itself after firmware 
update. Currently we can't use pinctrl to reset it.

  [Fix]
  Translate GPIO to pinctrl pins correctly.

  [Test]
  The WWAN reset function works once the fix is applied.

  [Regression Potential]
  Low. Limits to pinctrl-intel and it's in mainline for a while.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1811777/+subscriptions

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


[Kernel-packages] [Bug 1812159] [NEW] SCHED_STACK_END_CHECK should be enabled in B-kvm

2019-01-16 Thread Po-Hsu Lin
Public bug reported:

The test_380_config_sched_stack_end_check test failed on the Bionic
KVM kernel

FAIL: test_380_config_sched_stack_end_check 
(__main__.KernelSecurityConfigTest)
Ensure SCHED_STACK_END_CHECK is set
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2628, in 
test_380_config_sched_stack_end_check
self.assertKernelConfig('SCHED_STACK_END_CHECK', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: SCHED_STACK_END_CHECK option was expected to be set in 
the kernel config

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28
ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18
Uname: Linux 4.15.0-1028-kvm x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Thu Jan 17 06:44:41 2019
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic uec-images

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

Title:
  SCHED_STACK_END_CHECK should be enabled in B-kvm

Status in linux-kvm package in Ubuntu:
  New

Bug description:
  The test_380_config_sched_stack_end_check test failed on the Bionic
  KVM kernel

FAIL: test_380_config_sched_stack_end_check 
(__main__.KernelSecurityConfigTest)
Ensure SCHED_STACK_END_CHECK is set
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2628, in 
test_380_config_sched_stack_end_check
self.assertKernelConfig('SCHED_STACK_END_CHECK', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: SCHED_STACK_END_CHECK option was expected to be set in 
the kernel config

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28
  ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18
  Uname: Linux 4.15.0-1028-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Thu Jan 17 06:44:41 2019
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1812153] Re: CONFIG_SECURITY_SELINUX_DISABLE should be disabled on KVM kernel

2019-01-16 Thread Po-Hsu Lin
** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

** Changed in: ubuntu-kernel-tests
   Status: New => In Progress

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

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

Title:
  CONFIG_SECURITY_SELINUX_DISABLE should be disabled on KVM kernel

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

Bug description:
  The test_081_config_security_selinux_disable test failed on the Bionic
  KVM kernel

FAIL: test_081_config_security_selinux_disable 
(__main__.KernelSecurityConfigTest)
Ensure CONFIG_SECURITY_SELINUX_DISABLE is disabled (LP: #1680315)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2152, in 
test_081_config_security_selinux_disable
self.assertKernelConfig('SECURITY_SELINUX_DISABLE', expected)
File "./test-kernel-security.py", line 209, in assertKernelConfig
self.assertKernelConfigUnset(name)
File "./test-kernel-security.py", line 200, in assertKernelConfigUnset
'%s option was expected to be unset in the kernel config' % name)
AssertionError: SECURITY_SELINUX_DISABLE option was expected to be 
unset in the kernel config

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28
  ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18
  Uname: Linux 4.15.0-1028-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Thu Jan 17 04:31:59 2019
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1811777] Re: Fix non-working pinctrl-intel

2019-01-16 Thread AceLan Kao
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1811777

Title:
  Fix non-working pinctrl-intel

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

Bug description:
  [Impact]
  Intel pinctrl doesn't work.
  There's a WWAN card needs to use pinctrl to reset itself after firmware 
update. Currently we can't use pinctrl to reset it.

  [Fix]
  Translate GPIO to pinctrl pins correctly.

  [Test]
  The WWAN reset function works once the fix is applied.

  [Regression Potential]
  Low. Limits to pinctrl-intel and it's in mainline for a while.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1811777/+subscriptions

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


[Kernel-packages] [Bug 1811721] Re: Mainline Kernel Builds Failing for > v4.20 for amd64 on kernel.ubuntu.com

2019-01-16 Thread Rocko
I can build the mainline 4.20.3 kernel locally if I set "do_dkms_nvidia
= false" in its 0001-base-packaging.patch.

Why would we even want to build the nvidia driver for recent kernels?
Even the most up-to-date nvidia drivers rarely compile for -rc kernels,
and ubuntu typically has an older version of the nvidia driver anyway
(currently nvidia-390 from last August), so kernel build failure seems
highly likely to occur if it relies on the nvidia driver building
successfully.

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

Title:
  Mainline Kernel Builds Failing for > v4.20 for amd64 on
  kernel.ubuntu.com

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It appears that mainline kernel builds (on kernel.ubuntu.com) have
  been failing for amd64 since v4.20.1.  Interestingly enough v4.20 was
  able to build successfully.

  Note: this also includes 5.0rc builds as well.

  You can see the build logs here:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.1/BUILD.LOG.amd64
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.2/BUILD.LOG.amd64

  Looking at the build logs it appears that the kernel and all the in-
  tree modules build successfully, but the build fails when trying to
  build the proprietary nvidia kernel modules.  With v4.20 building
  these modules does not appear in the log.  Perhaps this build step was
  added more recently?

  Here are the relevant lines from the end of the build log for v4.20.2 (which 
I've also attached):
  
-

  2019-01-10 03:38:12 (105 MB/s) - 'nvidia-kernel-source-
  390_390.87-0ubuntu4_amd64.deb' saved [8433608/8433608]

  II: dkms-build downloading nvidia-390 
(nvidia-dkms-390_390.87-0ubuntu4_amd64.deb)
  --2019-01-10 03:38:13--  
http://us.archive.ubuntu.com/ubuntu/pool/restricted/n/nvidia-graphics-drivers-390/nvidia-dkms-390_390.87-0ubuntu4_amd64.deb
  Resolving us.archive.ubuntu.com (us.archive.ubuntu.com)... 91.189.91.26, 
91.189.91.23, 2001:67c:1562::16, ...
  Connecting to us.archive.ubuntu.com 
(us.archive.ubuntu.com)|91.189.91.26|:80... connected.
  HTTP request sent, awaiting response... 200 OK
  Length: 27288 (27K) [application/x-debian-package]
  Saving to: 'nvidia-dkms-390_390.87-0ubuntu4_amd64.deb'

   0K .. .. ..  100%
  9.46M=0.003s

  2019-01-10 03:38:13 (9.46 MB/s) - 'nvidia-dkms-
  390_390.87-0ubuntu4_amd64.deb' saved [27288/27288]

  linux:BuiltUsing=nvidia-kernel-source-390 (= 390.87-0ubuntu4), 
  II: dkms-build building nvidia-390

  Creating symlink 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/source
 ->
   
/home/kernel/COD/linux/debian/build/build-generic/__dkms/source/nvidia-390.87

  DKMS: add completed.
  applying patch buildfix_kernel_4.18.patch...patching file conftest.sh
  patching file nvidia-drm/nvidia-drm-connector.c
  patching file nvidia-drm/nvidia-drm-encoder.c
  patching file nvidia-drm/nvidia-drm-helper.h
  patching file nvidia-drm/nvidia-drm.Kbuild

  
  Building module:
  cleaning build area...(bad exit status: 2)
  unset ARCH; env NV_VERBOSE=1 'make' -j16 NV_EXCLUDE_BUILD_MODULES='' 
KERNEL_UNAME=4.20.1-042001-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 
SYSSRC=/home/kernel/COD/linux/debian/build/build-generic/__dkms/headers/linux-headers-4.20.1-042001-generic
 LD=/usr/bin/ld.bfd modules.(bad exit status: 2)
  Error! Bad return status for module build on kernel: 4.20.1-042001-generic 
(x86_64)
  Consult 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/build/make.log
 for more information.
  debian/scripts/dkms-build: line 121: 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/4.20.1-042001-generic/*/log/make.log:
 No such file or directory
  make: *** [debian/rules.d/2-binary-arch.mk:201: install-generic] Error 1

  Thanks!
  Rob

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

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


[Kernel-packages] [Bug 1808729] Re: MAC address pass through on RTL8153-BND for docking station

2019-01-16 Thread AceLan Kao
** Tags removed: verification-needed-bionic verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic

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

Title:
  MAC address pass through on RTL8153-BND for docking station

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  A new chip RTL8153-BND on docks require to be added to the whitelist to 
support MAC address pass through.

  [Fix]
  This commit adds check for RTL8153-BND chip which is in v4.20.
  9c27369f4a13 r8152: Add support for MAC address pass through on RTL8153-BND

  [Regression Potential]
  Low. It doesn't change the code flow for the old RTL8153-AD chip, so it won't 
lead to regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1808729/+subscriptions

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


[Kernel-packages] [Bug 1809847] Re: Ethernet[10ec:8136] doesn't work after S3 with kernel 4.15.0.43.64

2019-01-16 Thread AceLan Kao
** Tags removed: verification-needed-bionic verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic

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

Title:
  Ethernet[10ec:8136] doesn't work after S3 with kernel 4.15.0.43.64

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  The Ethernet works after S3 with kernel 4.15.0-33.36, and fails with kernel 
4.15.0.43.64.
  There is no interrupt while plug/unplug Ethernet cable after S3, so it looks 
like a regression after 4.15.0-33.36.

  [Fix]
  Check changelog and found there are 2 commits introduced from 4.15.0-35.38 
might be suspicious
    * r8169 no internet after suspending (LP: #1779817)
  - r8169: don't use MSI-X on RTL8168g
  - r8169: don't use MSI-X on RTL8106e
  And check the upstream log and found the 2 MSI-X commits had been all 
reverted, since below commit claims it fixes the MSI-X interrupt issue which is 
already in Bionic kernel.
     083874549fdf PCI: Reprogram bridge prefetch registers on resume
  So, I reverted the 2 MSI-X commits and found the Ethernet works again after 
S3.

  [Regression Potential]
  Low, the 2 disable MSI-X commits are workarounds, and now we have proper way 
to fix the issue, so it should be fine to revert them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1809847/+subscriptions

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


[Kernel-packages] [Bug 1805088] Re: iwlwifi fails to work on 16 or more logical CPUs machines

2019-01-16 Thread AceLan Kao
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  iwlwifi fails to work on 16 or more logical CPUs machines

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

Bug description:
  [Impact]
  Got dmesg kernel BUG while loading iwlwifi driver on machines which has 16 or 
more logical CPUs
 kernel: RIP: 0010:iwl_pcie_rxq_alloc_rbs+0x1d0/0x1f0 [iwlwifi]
  And it leads to wifi can't scan any APs, and leads to system hangs while 
suspending.

  [Fix]
  Below commit contained in v4.17 fix the issue.
 ab1068d6866e iwlwifi: pcie: compare with number of IRQs requested for, not 
number of CPUs

  [Regression Potential]
  Low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1805088/+subscriptions

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


[Kernel-packages] [Bug 1811335] Re: ELAN900C:00 04F3:2844 touchscreen doesn't work

2019-01-16 Thread AceLan Kao
** Tags removed: verification-needed-bionic verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic

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

Title:
  ELAN900C:00 04F3:2844 touchscreen doesn't work

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

Bug description:
  [Impact]
  [ELAN900C:00 04F3:2844] doesn't work

  [Fix]
  It works under kernel v4.19, so after bisect the kernel and got the first bad 
commit
     e50d95e2ad12 pinctrl: cannonlake: Fix HOSTSW_OWN register offset of H 
variant

  [Test]
  Verified on the DELL machine, the touchscreen works well.

  [Regression Potential]
  Low, the 2 commits are all
 Fixes: a663ccf0fea1 ("pinctrl: intel: Add Intel Cannon Lake PCH-H pin 
controller support")
  Should be safe to be included.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1811335/+subscriptions

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


[Kernel-packages] [Bug 1811337] Re: To reduce the Realtek USB cardreader power consumption

2019-01-16 Thread AceLan Kao
** Tags removed: verification-needed-bionic verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic

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

Title:
  To reduce the Realtek USB cardreader power consumption

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  Fix Committed
Status in linux-oem source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  Invalid

Bug description:
  [Impact]
  Realtek USB cardreader consumes more than 1 Watt during long idle if it's not 
suspended. And it's runtime PM functions are available after v4.20.

  [Fix]
  To avoid conflicts, have to backport some patches for mmc core.

  [Test]
  Note: Inside () are the previous value (non-patch)
  Sort idle: 7.76W (7.88)
  Long idle: 4.658W (5.79)
  S3: 0.5W (0.5)
  S5: 0.20W (0.208)

  [Regression Potential]
  Low, most commits are for rtsx_usb_{sdmmc,ms} and are all small changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1811337/+subscriptions

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


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

2019-01-16 Thread AceLan Kao
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux 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:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

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 1811929] Re: Fix not working Goodix touchpad

2019-01-16 Thread AceLan Kao
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1811929

Title:
  Fix not working Goodix touchpad

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

Bug description:
  [Impact]
  Goodix I2C PTP touchpad doesn't work.

  [Fix]
  Disable runtime PM can fix it.

  [Test]
  I verified the touchpad starts working with the fix.

  [Regression Potential]
  Low. The fix limits to a specific device which doesn't work without it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1811929/+subscriptions

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


[Kernel-packages] [Bug 1690085]

2019-01-16 Thread nucrap
Hey guys so finally I found this bugreport which I guess explains those
soft lockups on my Ryzen 7 1700 based system. I had temporarily switched
to Win10 since I hoped this bug would be resolved after some time, but
now 1,5 years later it is still there on the latest kernel.. At least I
can finally use my system again knowing that I need to disable the C6
state.

Can we finally bring some attention to this bug; at least set it to
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/1690085

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning 
and waiting for crash...
  For now, the machine is not "used", at least, it's not CPU stressed...

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   

[Kernel-packages] [Bug 1690085]

2019-01-16 Thread russianneuromancer
Maybe we need to contact AMD support and ask them to implement
workaround they suggested (document in Comment 459) in Linux?

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning 
and waiting for crash...
  For now, the machine is not "used", at least, it's not CPU stressed...

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-041100-generic 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:

[Kernel-packages] [Bug 1811431] Re: linux-azure: 4.15.0-1037.39~16.04.1 -proposed tracker

2019-01-16 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811419
- phase: Promote to Proposed -- snap release to beta ready
- phase-changed: Thursday, 17. January 2019 05:07 UTC
+ phase: Promote to Proposed -- snap release to edge ready
+ phase-changed: Thursday, 17. January 2019 06:00 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in beta channel
snap-release-to-edge: Pending -- snap not in edge channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.15.0-1037.39~16.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811419
  phase: Promote to Proposed -- snap release to edge ready
  phase-changed: Thursday, 17. January 2019 06:00 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in beta channel
snap-release-to-edge: Pending -- snap not in edge channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811431/+subscriptions

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


[Kernel-packages] [Bug 1776563]

2019-01-16 Thread eutychios23
Created attachment 280537
dmesg from gentoo based distro

[0.131050] [Firmware Bug]: AMD-Vi: IOAPIC[4] not in IVRS table
[0.131052] [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
[0.131053] [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found
[0.131054] AMD-Vi: Disabling interrupt remapping
[0.131076] Switched APIC routing to physical flat.

They seem to disable interrupt remapping like windows 10 does.

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  Fix Released
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions

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


[Kernel-packages] [Bug 1776563]

2019-01-16 Thread eutychios23
gentoo dmesg :[0.205850] ACPI: 14 ACPI AML tables successfully acquired and 
loaded
In other distros 13 ACPI AML tables load and 1 fails for some reason despite 
the same bios bugs.

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  Fix Released
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions

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


[Kernel-packages] [Bug 1776563]

2019-01-16 Thread eutychios23
Hello all gentoo and gentoo based distros can boot on my laptop without
any parameters

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  Fix Released
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions

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


[Kernel-packages] [Bug 1776563]

2019-01-16 Thread eutychios23
Acer Aspire A315-41G notebook

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  Fix Released
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions

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


[Kernel-packages] [Bug 1812128] Re: No IRC handler for Vector

2019-01-16 Thread Juhani Numminen
That is probably a kernel message, reassihned to linux.

Based on a google search, it might be irq instead of IRC.

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

Title:
  No IRC handler for Vector

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This message appears on screen first during bootup.

  
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

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

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


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

2019-01-16 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 1812128

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

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

Title:
  No IRC handler for Vector

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This message appears on screen first during bootup.

  
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

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

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


[Kernel-packages] [Bug 1812128] Re: No IRC handler for Vector

2019-01-16 Thread Juhani Numminen
** 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/1812128

Title:
  No IRC handler for Vector

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This message appears on screen first during bootup.

  
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

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

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


[Kernel-packages] [Bug 1812128] [NEW] No IRC handler for Vector

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

This message appears on screen first during bootup.


Description:Ubuntu 16.04.5 LTS
Release:16.04

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


** Tags: bot-comment handler irc vector
-- 
No IRC handler for Vector
https://bugs.launchpad.net/bugs/1812128
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 1697789] Re: Xorg: page allocation failure: order:0, mode:0x14210d2(GFP_HIGHUSER|__GFP_NORETRY|__GFP_RECLAIMABLE), nodemask=(null)

2019-01-16 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


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

** Changed in: linux (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Xorg: page allocation failure: order:0,
  mode:0x14210d2(GFP_HIGHUSER|__GFP_NORETRY|__GFP_RECLAIMABLE),
  nodemask=(null)

Status in X.Org X server:
  Unknown
Status in linux package in Ubuntu:
  Won't Fix
Status in xorg-server package in Arch Linux:
  New

Bug description:
  dmesg:
  [23559.058500] Xorg: page allocation failure: order:0, 
mode:0x14210d2(GFP_HIGHUSER|__GFP_NORETRY|__GFP_RECLAIMABLE), nodemask=(null)
  [23559.058509] Xorg cpuset=/ mems_allowed=0
  [23559.058516] CPU: 1 PID: 1797 Comm: Xorg Not tainted 
4.12.0-041200rc5-generic #201706112031
  [23559.058517] Hardware name: SAMSUNG ELECTRONICS CO., LTD. 
530U3C/530U4C/SAMSUNG_NP1234567890, BIOS P14AAJ 04/15/2013
  [23559.058519] Call Trace:
  [23559.058528]  dump_stack+0x63/0x8d
  [23559.058532]  warn_alloc+0x114/0x1c0
  [23559.058535]  __alloc_pages_slowpath+0xe07/0xe10
  [23559.058539]  __alloc_pages_nodemask+0x233/0x250
  [23559.058543]  alloc_pages_vma+0xab/0x250
  [23559.058547]  shmem_alloc_page+0x70/0xc0
  [23559.058550]  ? __radix_tree_insert+0x45/0x220
  [23559.058553]  ? __vm_enough_memory+0x29/0x130
  [23559.058555]  shmem_alloc_and_acct_page+0x72/0x1b0
  [23559.058558]  ? find_get_entry+0x1e/0xc0
  [23559.058561]  shmem_getpage_gfp+0x195/0xbd0
  [23559.058564]  shmem_read_mapping_page_gfp+0x44/0x80
  [23559.058611]  i915_gem_object_get_pages_gtt+0x204/0x5a0 [i915]
  [23559.058643]  i915_gem_object_get_pages+0x20/0x60 [i915]
  [23559.058673]  __i915_gem_object_get_pages+0x5c/0x70 [i915]
  [23559.058706]  __i915_vma_do_pin+0x1c6/0x3a0 [i915]
  [23559.058737]  i915_gem_execbuffer_reserve_vma.isra.29+0x14d/0x1b0 [i915]
  [23559.058765]  i915_gem_execbuffer_reserve.isra.30+0x3b7/0x3e0 [i915]
  [23559.058794]  i915_gem_do_execbuffer.isra.36+0x577/0x16c0 [i915]
  [23559.058799]  ? unix_stream_recvmsg+0x54/0x70
  [23559.058801]  ? unix_state_double_lock+0x70/0x70
  [23559.058830]  i915_gem_execbuffer2+0x96/0x1b0 [i915]
  [23559.058849]  drm_ioctl+0x216/0x4c0 [drm]
  [23559.058877]  ? i915_gem_execbuffer+0x2f0/0x2f0 [i915]
  [23559.058881]  ? __remove_hrtimer+0x3c/0x70
  [23559.058885]  do_vfs_ioctl+0xa3/0x600
  [23559.05]  ? do_setitimer+0xe0/0x240
  [23559.058891]  ? SyS_setitimer+0xf1/0x120
  [23559.058894]  SyS_ioctl+0x79/0x90
  [23559.058897]  entry_SYSCALL_64_fastpath+0x1e/0xa9
  [23559.058900] RIP: 0033:0x7fd8c5c7e987
  [23559.058901] RSP: 002b:7ffd494ac738 EFLAGS: 0246 ORIG_RAX: 
0010
  [23559.058904] RAX: ffda RBX: 0006 RCX: 
7fd8c5c7e987
  [23559.058905] RDX: 7ffd494ac790 RSI: 40406469 RDI: 
000c
  [23559.058907] RBP: 0028 R08: 0001 R09: 
000c
  [23559.058908] R10: 0001 R11: 0246 R12: 
0040
  [23559.058909] R13: 0008 R14: 5581c086a6c0 R15: 

  [23559.058912] Mem-Info:
  [23559.058918] active_anon:1016643 inactive_anon:298858 isolated_anon:0
  active_file:395940 inactive_file:1147459 isolated_file:0
  unevictable:129 dirty:124022 writeback:21146 unstable:0
  slab_reclaimable:57926 slab_unreclaimable:23062
  mapped:283483 shmem:248113 pagetables:23247 bounce:0
  free:29069 free_pcp:245 free_cma:0
  [23559.058923] Node 0 active_anon:4066572kB inactive_anon:1195432kB 
active_file:1583760kB inactive_file:4589836kB unevictable:516kB 
isolated(anon):0kB isolated(file):0kB mapped:1133932kB dirty:496088kB 
writeback:84584kB shmem:992452kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 
976896kB writeback_tmp:0kB unstable:0kB all_unreclaimable? no
  [23559.058924] Node 0 DMA free:15360kB min:84kB low:104kB high:124kB 
active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB 
unevictable:0kB writepending:0kB present:15984kB managed:15360kB mlocked:0kB 
slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB 
bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
  [23559.058930] lowmem_reserve[]: 0 3226 11726 11726 11726
  [23559.058935] Node 0 DMA32 free:52176kB min:18568kB low:23208kB high:27848kB 
active_anon:718716kB 

[Kernel-packages] [Bug 1722355] Re: Despite power/display settings on never, screen turns off

2019-01-16 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Won't Fix

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

** Changed in: nvidia-graphics-drivers-384 (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Despite power/display settings on never, screen turns off

Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Won't Fix
Status in xorg-server package in Ubuntu:
  Won't Fix

Bug description:
  Running 17.10 64bit on Syx/MSI 16Gb desktop with Geforce GTX950 on
  Samsung monitor.  When left unattended, screen blanks after a few
  minutes, as if it was set to.  Wakes with no issues, but sometimes i
  find that it has logged me out.  I have triple-checked all settings
  and see no problem there.  Problem began a few days ago after a recent
  update.  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.90  Tue Sep 19 19:17:35 
PDT 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu2)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  9 12:57:46 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GM206 [GeForce GTX 950] [10de:1402] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GM206 [GeForce GTX 950] [3842:2957]
  InstallationDate: Installed on 2017-04-07 (184 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: MSI MS-7673
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=7aaf85cc-4052-49d5-ba13-4e3a8c8ff17d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.28B6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P67A-C43 (MS-7673)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.28B6:bd08/31/2011:svnMSI:pnMS-7673:pvr1.0:rvnMSI:rnP67A-C43(MS-7673):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7673
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Oct  9 12:44:58 2017
  

[Kernel-packages] [Bug 1811431] Re: linux-azure: 4.15.0-1037.39~16.04.1 -proposed tracker

2019-01-16 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811419
- phase: Promote to Proposed -- snap release to edge ready
- phase-changed: Thursday, 17. January 2019 04:35 UTC
+ phase: Promote to Proposed -- snap release to beta ready
+ phase-changed: Thursday, 17. January 2019 05:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in beta channel
snap-release-to-edge: Pending -- snap not in edge channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.15.0-1037.39~16.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811419
  phase: Promote to Proposed -- snap release to beta ready
  phase-changed: Thursday, 17. January 2019 05:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in beta channel
snap-release-to-edge: Pending -- snap not in edge channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811431/+subscriptions

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


[Kernel-packages] [Bug 1722987] Re: screen brightness control is backwards

2019-01-16 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


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

** Changed in: linux (Ubuntu)
   Status: New => Won't Fix

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

Title:
  screen brightness control is backwards

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  Increase brightness key on my keyboard (func-f3) makes the screen more dim.
  Decrease brightness key on my keyboard (func-f2) makes the screen more bright.
  The gnome-shell on-screen display of brightness is backwards also.

  I see on google search results that this was a problem with older
  kernels. I guess the problem is back / possible regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 11 20:52:44 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [103c:2209]
  InstallationDate: Installed on 2017-10-08 (3 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0cf3:3121 Atheros Communications, Inc. 
   Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 001 Device 002: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion 11 x360 PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic.efi.signed 
root=UUID=3db6d4f1-3d95-4b8c-93d1-ab9465947670 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/11/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.15
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2209
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 57.37
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.15:bd11/11/2014:svnHewlett-Packard:pnHPPavilion11x360PC:pvr096F100800405F00010420180:rvnHewlett-Packard:rn2209:rvr57.37:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=MIN
  dmi.product.name: HP Pavilion 11 x360 PC
  dmi.product.version: 096F100800405F00010420180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Kernel-packages] [Bug 1811846] Re: linux: 4.4.0-142.168 -proposed tracker

2019-01-16 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-xenial

** Tags added: block-proposed

** 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: bug 1811847 (linux-aws), bug 1811848 (linux-lts-xenial)
  derivatives: bug 1811851 (linux-aws), bug 1811852 (linux-euclid), bug 1811853 
(linux-kvm), bug 1811854 (linux-raspi2), bug 1811855 (linux-snapdragon)
  -- swm properties --
- phase: Packaging -- uploaded
- phase-changed: Wednesday, 16. January 2019 22:08 UTC
+ boot-testing-requested: true
+ phase: Promote to Proposed -- release to Proposed ready
+ phase-changed: Thursday, 17. January 2019 05:06 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete
+   promote-to-proposed: Pending -- ready for review

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

Title:
  linux: 4.4.0-142.168 -proposed tracker

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

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

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

  backports: bug 1811847 (linux-aws), bug 1811848 (linux-lts-xenial)
  derivatives: bug 1811851 (linux-aws), bug 1811852 (linux-euclid), bug 1811853 
(linux-kvm), bug 1811854 (linux-raspi2), bug 1811855 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  phase: Promote to Proposed -- release to Proposed ready
  phase-changed: Thursday, 17. January 2019 05:06 UTC
  reason:
promote-to-proposed: Pending -- ready for review

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811846/+subscriptions

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


[Kernel-packages] [Bug 1722987] [NEW] screen brightness control is backwards

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

Increase brightness key on my keyboard (func-f3) makes the screen more dim.
Decrease brightness key on my keyboard (func-f2) makes the screen more bright.
The gnome-shell on-screen display of brightness is backwards also.

I see on google search results that this was a problem with older
kernels. I guess the problem is back / possible regression.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
Uname: Linux 4.13.0-15-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 11 20:52:44 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [103c:2209]
InstallationDate: Installed on 2017-10-08 (3 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 005: ID 0cf3:3121 Atheros Communications, Inc. 
 Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub
 Bus 001 Device 002: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) Webcam
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Hewlett-Packard HP Pavilion 11 x360 PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic.efi.signed 
root=UUID=3db6d4f1-3d95-4b8c-93d1-ab9465947670 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/11/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.15
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 2209
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 57.37
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.15:bd11/11/2014:svnHewlett-Packard:pnHPPavilion11x360PC:pvr096F100800405F00010420180:rvnHewlett-Packard:rn2209:rvr57.37:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=MIN
dmi.product.name: HP Pavilion 11 x360 PC
dmi.product.version: 096F100800405F00010420180
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Won't Fix


** Tags: amd64 apport-bug artful ubuntu wayland-session
-- 
screen brightness control is backwards
https://bugs.launchpad.net/bugs/1722987
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 1697789] [NEW] Xorg: page allocation failure: order:0, mode:0x14210d2(GFP_HIGHUSER|__GFP_NORETRY|__GFP_RECLAIMABLE), nodemask=(null)

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

dmesg:
[23559.058500] Xorg: page allocation failure: order:0, 
mode:0x14210d2(GFP_HIGHUSER|__GFP_NORETRY|__GFP_RECLAIMABLE), nodemask=(null)
[23559.058509] Xorg cpuset=/ mems_allowed=0
[23559.058516] CPU: 1 PID: 1797 Comm: Xorg Not tainted 4.12.0-041200rc5-generic 
#201706112031
[23559.058517] Hardware name: SAMSUNG ELECTRONICS CO., LTD. 
530U3C/530U4C/SAMSUNG_NP1234567890, BIOS P14AAJ 04/15/2013
[23559.058519] Call Trace:
[23559.058528]  dump_stack+0x63/0x8d
[23559.058532]  warn_alloc+0x114/0x1c0
[23559.058535]  __alloc_pages_slowpath+0xe07/0xe10
[23559.058539]  __alloc_pages_nodemask+0x233/0x250
[23559.058543]  alloc_pages_vma+0xab/0x250
[23559.058547]  shmem_alloc_page+0x70/0xc0
[23559.058550]  ? __radix_tree_insert+0x45/0x220
[23559.058553]  ? __vm_enough_memory+0x29/0x130
[23559.058555]  shmem_alloc_and_acct_page+0x72/0x1b0
[23559.058558]  ? find_get_entry+0x1e/0xc0
[23559.058561]  shmem_getpage_gfp+0x195/0xbd0
[23559.058564]  shmem_read_mapping_page_gfp+0x44/0x80
[23559.058611]  i915_gem_object_get_pages_gtt+0x204/0x5a0 [i915]
[23559.058643]  i915_gem_object_get_pages+0x20/0x60 [i915]
[23559.058673]  __i915_gem_object_get_pages+0x5c/0x70 [i915]
[23559.058706]  __i915_vma_do_pin+0x1c6/0x3a0 [i915]
[23559.058737]  i915_gem_execbuffer_reserve_vma.isra.29+0x14d/0x1b0 [i915]
[23559.058765]  i915_gem_execbuffer_reserve.isra.30+0x3b7/0x3e0 [i915]
[23559.058794]  i915_gem_do_execbuffer.isra.36+0x577/0x16c0 [i915]
[23559.058799]  ? unix_stream_recvmsg+0x54/0x70
[23559.058801]  ? unix_state_double_lock+0x70/0x70
[23559.058830]  i915_gem_execbuffer2+0x96/0x1b0 [i915]
[23559.058849]  drm_ioctl+0x216/0x4c0 [drm]
[23559.058877]  ? i915_gem_execbuffer+0x2f0/0x2f0 [i915]
[23559.058881]  ? __remove_hrtimer+0x3c/0x70
[23559.058885]  do_vfs_ioctl+0xa3/0x600
[23559.05]  ? do_setitimer+0xe0/0x240
[23559.058891]  ? SyS_setitimer+0xf1/0x120
[23559.058894]  SyS_ioctl+0x79/0x90
[23559.058897]  entry_SYSCALL_64_fastpath+0x1e/0xa9
[23559.058900] RIP: 0033:0x7fd8c5c7e987
[23559.058901] RSP: 002b:7ffd494ac738 EFLAGS: 0246 ORIG_RAX: 
0010
[23559.058904] RAX: ffda RBX: 0006 RCX: 7fd8c5c7e987
[23559.058905] RDX: 7ffd494ac790 RSI: 40406469 RDI: 000c
[23559.058907] RBP: 0028 R08: 0001 R09: 000c
[23559.058908] R10: 0001 R11: 0246 R12: 0040
[23559.058909] R13: 0008 R14: 5581c086a6c0 R15: 
[23559.058912] Mem-Info:
[23559.058918] active_anon:1016643 inactive_anon:298858 isolated_anon:0
active_file:395940 inactive_file:1147459 isolated_file:0
unevictable:129 dirty:124022 writeback:21146 unstable:0
slab_reclaimable:57926 slab_unreclaimable:23062
mapped:283483 shmem:248113 pagetables:23247 bounce:0
free:29069 free_pcp:245 free_cma:0
[23559.058923] Node 0 active_anon:4066572kB inactive_anon:1195432kB 
active_file:1583760kB inactive_file:4589836kB unevictable:516kB 
isolated(anon):0kB isolated(file):0kB mapped:1133932kB dirty:496088kB 
writeback:84584kB shmem:992452kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 
976896kB writeback_tmp:0kB unstable:0kB all_unreclaimable? no
[23559.058924] Node 0 DMA free:15360kB min:84kB low:104kB high:124kB 
active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB 
unevictable:0kB writepending:0kB present:15984kB managed:15360kB mlocked:0kB 
slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB 
bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
[23559.058930] lowmem_reserve[]: 0 3226 11726 11726 11726
[23559.058935] Node 0 DMA32 free:52176kB min:18568kB low:23208kB high:27848kB 
active_anon:718716kB inactive_anon:177564kB active_file:228516kB 
inactive_file:2067540kB unevictable:0kB writepending:203112kB present:3438520kB 
managed:3354852kB mlocked:0kB slab_reclaimable:98764kB 
slab_unreclaimable:3004kB kernel_stack:576kB pagetables:4384kB bounce:0kB 
free_pcp:0kB local_pcp:0kB free_cma:0kB
[23559.058941] lowmem_reserve[]: 0 0 8500 8500 8500
[23559.058945] Node 0 Normal free:48740kB min:48924kB low:61152kB high:73380kB 
active_anon:3347648kB inactive_anon:1017448kB active_file:1354180kB 
inactive_file:2521736kB unevictable:516kB writepending:377444kB 
present:8902656kB managed:8704148kB mlocked:516kB slab_reclaimable:132940kB 
slab_unreclaimable:89244kB kernel_stack:17296kB pagetables:88604kB bounce:0kB 
free_pcp:980kB local_pcp:736kB free_cma:0kB
[23559.058951] lowmem_reserve[]: 0 0 0 0 0
[23559.058954] Node 0 DMA: 0*4kB 0*8kB 0*16kB 0*32kB 0*64kB 0*128kB 0*256kB 
0*512kB 1*1024kB (U) 1*2048kB (M) 3*4096kB (M) = 15360kB
[23559.058967] Node 0 DMA32: 10*4kB (UME) 8*8kB (UME) 1520*16kB (UME) 830*32kB 
(UME) 13*64kB (UM) 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 51816kB
[23559.058980] Node 0 Normal: 51*4kB (UM) 282*8kB (UME) 646*16kB (UMEH) 
983*32kB (UMEH) 

[Kernel-packages] [Bug 1812153] Re: CONFIG_SECURITY_SELINUX_DISABLE should be disabled on KVM kernel

2019-01-16 Thread Po-Hsu Lin
** Changed in: linux-kvm (Ubuntu)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: linux-kvm (Ubuntu)
   Status: New => In Progress

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

Title:
  CONFIG_SECURITY_SELINUX_DISABLE should be disabled on KVM kernel

Status in linux-kvm package in Ubuntu:
  In Progress

Bug description:
  The test_081_config_security_selinux_disable test failed on the Bionic
  KVM kernel

FAIL: test_081_config_security_selinux_disable 
(__main__.KernelSecurityConfigTest)
Ensure CONFIG_SECURITY_SELINUX_DISABLE is disabled (LP: #1680315)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2152, in 
test_081_config_security_selinux_disable
self.assertKernelConfig('SECURITY_SELINUX_DISABLE', expected)
File "./test-kernel-security.py", line 209, in assertKernelConfig
self.assertKernelConfigUnset(name)
File "./test-kernel-security.py", line 200, in assertKernelConfigUnset
'%s option was expected to be unset in the kernel config' % name)
AssertionError: SECURITY_SELINUX_DISABLE option was expected to be 
unset in the kernel config

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28
  ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18
  Uname: Linux 4.15.0-1028-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Thu Jan 17 04:31:59 2019
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1812153] [NEW] CONFIG_SECURITY_SELINUX_DISABLE should be disabled on KVM kernel

2019-01-16 Thread Po-Hsu Lin
Public bug reported:

The test_081_config_security_selinux_disable test failed on the Bionic
KVM kernel

FAIL: test_081_config_security_selinux_disable 
(__main__.KernelSecurityConfigTest)
Ensure CONFIG_SECURITY_SELINUX_DISABLE is disabled (LP: #1680315)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2152, in 
test_081_config_security_selinux_disable
self.assertKernelConfig('SECURITY_SELINUX_DISABLE', expected)
File "./test-kernel-security.py", line 209, in assertKernelConfig
self.assertKernelConfigUnset(name)
File "./test-kernel-security.py", line 200, in assertKernelConfigUnset
'%s option was expected to be unset in the kernel config' % name)
AssertionError: SECURITY_SELINUX_DISABLE option was expected to be 
unset in the kernel config

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28
ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18
Uname: Linux 4.15.0-1028-kvm x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Thu Jan 17 04:31:59 2019
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-kvm (Ubuntu)
 Importance: Undecided
 Assignee: Po-Hsu Lin (cypressyew)
 Status: In Progress


** Tags: amd64 apport-bug bionic uec-images

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

Title:
  CONFIG_SECURITY_SELINUX_DISABLE should be disabled on KVM kernel

Status in linux-kvm package in Ubuntu:
  In Progress

Bug description:
  The test_081_config_security_selinux_disable test failed on the Bionic
  KVM kernel

FAIL: test_081_config_security_selinux_disable 
(__main__.KernelSecurityConfigTest)
Ensure CONFIG_SECURITY_SELINUX_DISABLE is disabled (LP: #1680315)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2152, in 
test_081_config_security_selinux_disable
self.assertKernelConfig('SECURITY_SELINUX_DISABLE', expected)
File "./test-kernel-security.py", line 209, in assertKernelConfig
self.assertKernelConfigUnset(name)
File "./test-kernel-security.py", line 200, in assertKernelConfigUnset
'%s option was expected to be unset in the kernel config' % name)
AssertionError: SECURITY_SELINUX_DISABLE option was expected to be 
unset in the kernel config

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28
  ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18
  Uname: Linux 4.15.0-1028-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Thu Jan 17 04:31:59 2019
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1811431] Re: linux-azure: 4.15.0-1037.39~16.04.1 -proposed tracker

2019-01-16 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811419
- phase: Promote to Proposed -- snap release to beta ready
- phase-changed: Thursday, 17. January 2019 04:06 UTC
+ phase: Promote to Proposed -- snap release to edge ready
+ phase-changed: Thursday, 17. January 2019 04:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in beta channel
snap-release-to-edge: Pending -- snap not in edge channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.15.0-1037.39~16.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811419
  phase: Promote to Proposed -- snap release to edge ready
  phase-changed: Thursday, 17. January 2019 04:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in beta channel
snap-release-to-edge: Pending -- snap not in edge channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811431/+subscriptions

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


[Kernel-packages] [Bug 1812152] Status changed to Confirmed

2019-01-16 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/1812152

Title:
  USB 2.0 keyboard not driven directly from USB 3.1 port

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Messages issued during boot:

  usb 1-4: chopping to 0 config(s)
  usb: port power management may be unreliable

  "lsusb -v" command shows keyboard recognized but no active driver.
  Keyboard works when routed through a USB 2.0 hub.  Problem also exists
  under v4.20 kernel (12/23/2018 20:30 build, commit level
  8fe28cb58bcb235034b64cbbb7550a8a43fd88be).  Other USB 1.1 (mouse) and
  2.0 (DVD writer) devices work when plugged into 3.1 ports.  Latest
  level of Intel Visual BIOS (BECFL357.86A.0056.2018.1128.1717) properly
  handles keyboard edits of BIOS.

  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
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  charlie1513 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 16 21:52:01 2019
  InstallationDate: Installed on 2019-01-02 (14 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Intel(R) Client Systems NUC8i5BEH
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=a58e6950-4cfa-4ebc-abdc-8f66caf06ba7 ro quiet splash vt.handoff=1
  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
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/28/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0056.2018.1128.1717
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72692-303
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0056.2018.1128.1717:bd11/28/2018:svnIntel(R)ClientSystems:pnNUC8i5BEH:pvrJ72747-302:rvnIntelCorporation:rnNUC8BEB:rvrJ72692-303:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i5BEH
  dmi.product.version: J72747-302
  dmi.sys.vendor: Intel(R) Client Systems

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

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


[Kernel-packages] [Bug 1802382] Re: [860399.181468] watchdog: BUG: soft lockup - CPU#4 stuck for 23s! [kworker/4:2:9700]

2019-01-16 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/1802382

Title:
  [860399.181468] watchdog: BUG: soft lockup - CPU#4 stuck for 23s!
  [kworker/4:2:9700]

Status in linux package in Ubuntu:
  Expired

Bug description:
  system was halt after resume. I had to boot via Magic SysRq
  R-E-I-S-U-B routine.

  $ cat /proc/version_signature
  Ubuntu 4.15.0-38.41-generic 4.15.18

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Thu Nov  8 22:27:35 2018
  Failure: oops
  InstallationDate: Installed on 2018-06-01 (160 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. N550JV
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=d62c0813-bece-408d-8a4c-773ce7fbe368 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: [860399.181468] watchdog: BUG: soft lockup - CPU#4 stuck for 23s! 
[kworker/4:2:9700]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N550JV.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N550JV
  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.:bvrN550JV.208:bd11/19/2013:svnASUSTeKCOMPUTERINC.:pnN550JV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N550JV
  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/1802382/+subscriptions

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


[Kernel-packages] [Bug 1811431] Re: linux-azure: 4.15.0-1037.39~16.04.1 -proposed tracker

2019-01-16 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811419
- phase: Promote to Proposed -- snap release to edge ready
- phase-changed: Thursday, 17. January 2019 03:35 UTC
+ phase: Promote to Proposed -- snap release to beta ready
+ phase-changed: Thursday, 17. January 2019 04:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in beta channel
snap-release-to-edge: Pending -- snap not in edge channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.15.0-1037.39~16.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811419
  phase: Promote to Proposed -- snap release to beta ready
  phase-changed: Thursday, 17. January 2019 04:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in beta channel
snap-release-to-edge: Pending -- snap not in edge channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811431/+subscriptions

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


[Kernel-packages] [Bug 1806534] Re: Fix USB2 device wrongly detected as USB1

2019-01-16 Thread Ike Panhc
The -proposed kernel works fine. Thanks

** Tags removed: verification-needed-bionic verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic

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

Title:
  Fix USB2 device wrongly detected as USB1

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

Bug description:
  [Impact]
  USB 2 device may come up as USB 1 if a connection to a USB 1 device is 
followed by another connection to a USB 2 device, the link will come up as USB 
1 for the USB 2 device.

  [Test Case]
  Insert 2 USB devices and they shall appear on lsusb with correct address

  [Fix]
  11644a76 xhci: Add quirk to workaround the errata seen on Cavium Thunder-X2 
Soc

  [Regression Risk]
  It only affect device PCI_VENDOR_ID_CAVIUM:0x9026 and 
PCI_VENDOR_ID_BROADCOM:0x9026.
  Low regression to other device.

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

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


[Kernel-packages] [Bug 1812152] [NEW] USB 2.0 keyboard not driven directly from USB 3.1 port

2019-01-16 Thread Amapele
Public bug reported:

Messages issued during boot:

usb 1-4: chopping to 0 config(s)
usb: port power management may be unreliable

"lsusb -v" command shows keyboard recognized but no active driver.
Keyboard works when routed through a USB 2.0 hub.  Problem also exists
under v4.20 kernel (12/23/2018 20:30 build, commit level
8fe28cb58bcb235034b64cbbb7550a8a43fd88be).  Other USB 1.1 (mouse) and
2.0 (DVD writer) devices work when plugged into 3.1 ports.  Latest level
of Intel Visual BIOS (BECFL357.86A.0056.2018.1128.1717) properly handles
keyboard edits of BIOS.

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
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  charlie1513 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 16 21:52:01 2019
InstallationDate: Installed on 2019-01-02 (14 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: Intel(R) Client Systems NUC8i5BEH
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=a58e6950-4cfa-4ebc-abdc-8f66caf06ba7 ro quiet splash vt.handoff=1
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
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/28/2018
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BECFL357.86A.0056.2018.1128.1717
dmi.board.name: NUC8BEB
dmi.board.vendor: Intel Corporation
dmi.board.version: J72692-303
dmi.chassis.type: 3
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 2.0
dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0056.2018.1128.1717:bd11/28/2018:svnIntel(R)ClientSystems:pnNUC8i5BEH:pvrJ72747-302:rvnIntelCorporation:rnNUC8BEB:rvrJ72692-303:cvnIntelCorporation:ct3:cvr2.0:
dmi.product.family: Intel NUC
dmi.product.name: NUC8i5BEH
dmi.product.version: J72747-302
dmi.sys.vendor: Intel(R) Client Systems

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


** Tags: amd64 apport-bug bionic

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

Title:
  USB 2.0 keyboard not driven directly from USB 3.1 port

Status in linux package in Ubuntu:
  New

Bug description:
  Messages issued during boot:

  usb 1-4: chopping to 0 config(s)
  usb: port power management may be unreliable

  "lsusb -v" command shows keyboard recognized but no active driver.
  Keyboard works when routed through a USB 2.0 hub.  Problem also exists
  under v4.20 kernel (12/23/2018 20:30 build, commit level
  8fe28cb58bcb235034b64cbbb7550a8a43fd88be).  Other USB 1.1 (mouse) and
  2.0 (DVD writer) devices work when plugged into 3.1 ports.  Latest
  level of Intel Visual BIOS (BECFL357.86A.0056.2018.1128.1717) properly
  handles keyboard edits of BIOS.

  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
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  charlie1513 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 16 21:52:01 2019
  InstallationDate: Installed on 2019-01-02 (14 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Intel(R) Client Systems NUC8i5BEH
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=a58e6950-4cfa-4ebc-abdc-8f66caf06ba7 ro quiet splash vt.handoff=1
  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
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/28/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0056.2018.1128.1717
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72692-303
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0056.2018.1128.1717:bd11/28/2018:svnIntel(R)ClientSystems:pnNUC8i5BEH:pvrJ72747-302:rvnIntelCorporation:rnNUC8BEB:rvrJ72692-303:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  

[Kernel-packages] [Bug 1811200] Re: Add Cavium ThunderX2 SoC UNCORE PMU driver

2019-01-16 Thread Ike Panhc
perf works fine with -proposed kernel.

** Tags removed: verification-needed-bionic verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic

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

Title:
  Add Cavium ThunderX2 SoC UNCORE PMU driver

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

Bug description:
  [Impact]
  No driver for PMU of L3 cache controller (L3C) and the DDR4 Memory Controller 
(DMC) for Cavium ThunderX2 SoC

  [Test Case]
  sudo perf stat -a -e \
  > uncore_dmc_0/cnt_cycles/,\
  > uncore_dmc_0/data_transfers/,\
  > uncore_dmc_0/read_txns/,\
  > uncore_dmc_0/write_txns/ sleep 1

  sudo perf stat -a -e \
  > uncore_l3c_0/read_request/,\
  > uncore_l3c_0/read_hit/,\
  > uncore_l3c_0/inv_request/,\
  > uncore_l3c_0/inv_hit/ sleep 1

  sudo perf stat -a -e uncore_dmc_0/cnt_cycles/ sleep 1

  [Fix]
  Backport patches
  82975c46da  perf: Export perf_event_update_userpage (only for bionic)
  d6310a3f33  Documentation: perf: Add documentation for ThunderX2 PMU uncore 
driver
  69c32972d5  drivers/perf: Add Cavium ThunderX2 SoC UNCORE PMU driver
  and enable CONFIG_THUNDERX2_PMU=m

  [Regression Risk]
  This driver only loaded when CAV901C in ACPI table, lowest risk for other 
platform.

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

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


[Kernel-packages] [Bug 1811425] Re: linux-kvm: 4.15.0-1029.29 -proposed tracker

2019-01-16 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811419
- phase: Testing -- verification-testing in progress
- phase-changed: Thursday, 17. January 2019 03:05 UTC
+ phase: Testing -- regression-testing in progress
+ phase-changed: Thursday, 17. January 2019 03:38 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-kvm: 4.15.0-1029.29 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811419
  phase: Testing -- regression-testing in progress
  phase-changed: Thursday, 17. January 2019 03:38 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811425/+subscriptions

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


[Kernel-packages] [Bug 1811431] Re: linux-azure: 4.15.0-1037.39~16.04.1 -proposed tracker

2019-01-16 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811419
- phase: Promote to Proposed -- snap release to beta ready
- phase-changed: Thursday, 17. January 2019 03:01 UTC
+ phase: Promote to Proposed -- snap release to edge ready
+ phase-changed: Thursday, 17. January 2019 03:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in beta channel
snap-release-to-edge: Pending -- snap not in edge channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.15.0-1037.39~16.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811419
  phase: Promote to Proposed -- snap release to edge ready
  phase-changed: Thursday, 17. January 2019 03:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in beta channel
snap-release-to-edge: Pending -- snap not in edge channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811431/+subscriptions

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


[Kernel-packages] [Bug 1811417] Re: linux-kvm: 4.18.0-1007.7 -proposed tracker

2019-01-16 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811406
- phase: Testing -- verification-testing in progress
- phase-changed: Thursday, 17. January 2019 03:02 UTC
+ phase: Testing -- regression-testing in progress
+ phase-changed: Thursday, 17. January 2019 03:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-kvm: 4.18.0-1007.7 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811406
  phase: Testing -- regression-testing in progress
  phase-changed: Thursday, 17. January 2019 03:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811417/+subscriptions

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


[Kernel-packages] [Bug 1811981] Re: test_410_config_lock_down_kernel in ubuntu_kernel_security test failed on Bionic with PowerPC

2019-01-16 Thread Po-Hsu Lin
This could be found on KVM kernel as well.

** Also affects: linux-kvm (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/1811981

Title:
  test_410_config_lock_down_kernel in ubuntu_kernel_security test failed
  on Bionic with PowerPC

Status in QA Regression Testing:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-kvm package in Ubuntu:
  New

Bug description:
  Kernel Version: 4.15.0-44.47

  This test has passed on s390x / AMD64 / ARM64 / i386, but failed with
  Power8 and Power9

  FAIL: test_410_config_lock_down_kernel (__main__.KernelSecurityConfigTest)
  Ensure kernel efi lockdown is enabled
  --
  Traceback (most recent call last):
    File "./test-kernel-security.py", line 2668, in 
test_410_config_lock_down_kernel
  self.assertKernelConfig('LOCK_DOWN_KERNEL', expected)
    File "./test-kernel-security.py", line 207, in assertKernelConfig
  self.assertKernelConfigSet(name)
    File "./test-kernel-security.py", line 194, in assertKernelConfigSet
  '%s option was expected to be set in the kernel config' % name)
  AssertionError: LOCK_DOWN_KERNEL option was expected to be set in the kernel 
config

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1811981/+subscriptions

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


[Kernel-packages] [Bug 1811425] Re: linux-kvm: 4.15.0-1029.29 -proposed tracker

2019-01-16 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811419
- phase: Testing -- regression-testing in progress
- phase-changed: Thursday, 17. January 2019 02:36 UTC
+ phase: Testing -- verification-testing in progress
+ phase-changed: Thursday, 17. January 2019 03:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-kvm: 4.15.0-1029.29 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811419
  phase: Testing -- verification-testing in progress
  phase-changed: Thursday, 17. January 2019 03:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811425/+subscriptions

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


[Kernel-packages] [Bug 1811431] Re: linux-azure: 4.15.0-1037.39~16.04.1 -proposed tracker

2019-01-16 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811419
- phase: Promote to Proposed -- snap release to edge ready
- phase-changed: Thursday, 17. January 2019 02:32 UTC
+ phase: Promote to Proposed -- snap release to beta ready
+ phase-changed: Thursday, 17. January 2019 03:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in beta channel
snap-release-to-edge: Pending -- snap not in edge channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.15.0-1037.39~16.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811419
  phase: Promote to Proposed -- snap release to beta ready
  phase-changed: Thursday, 17. January 2019 03:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in beta channel
snap-release-to-edge: Pending -- snap not in edge channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811431/+subscriptions

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


[Kernel-packages] [Bug 1811417] Re: linux-kvm: 4.18.0-1007.7 -proposed tracker

2019-01-16 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811406
- phase: Testing -- regression-testing in progress
- phase-changed: Thursday, 17. January 2019 02:31 UTC
+ phase: Testing -- verification-testing in progress
+ phase-changed: Thursday, 17. January 2019 03:02 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-kvm: 4.18.0-1007.7 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811406
  phase: Testing -- verification-testing in progress
  phase-changed: Thursday, 17. January 2019 03:02 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811417/+subscriptions

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


[Kernel-packages] [Bug 1811425] Re: linux-kvm: 4.15.0-1029.29 -proposed tracker

2019-01-16 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811419
- phase: Testing -- verification-testing in progress
- phase-changed: Wednesday, 16. January 2019 23:05 UTC
+ phase: Testing -- regression-testing in progress
+ phase-changed: Thursday, 17. January 2019 02:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-kvm: 4.15.0-1029.29 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811419
  phase: Testing -- regression-testing in progress
  phase-changed: Thursday, 17. January 2019 02:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811425/+subscriptions

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


[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

2019-01-16 Thread siyia
i used kernel 4.20.1 from vanilla sources with the config from 4.19 and
openrc, i also tried artix linux which is arch and the udev
service stuck like in other systemd linuxes.

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  Fix Released
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions

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


[Kernel-packages] [Bug 1811431] Re: linux-azure: 4.15.0-1037.39~16.04.1 -proposed tracker

2019-01-16 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811419
- phase: Promote to Proposed -- snap release to beta ready
- phase-changed: Thursday, 17. January 2019 01:08 UTC
+ phase: Promote to Proposed -- snap release to edge ready
+ phase-changed: Thursday, 17. January 2019 02:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in beta channel
snap-release-to-edge: Pending -- snap not in edge channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.15.0-1037.39~16.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811419
  phase: Promote to Proposed -- snap release to edge ready
  phase-changed: Thursday, 17. January 2019 02:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in beta channel
snap-release-to-edge: Pending -- snap not in edge channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811431/+subscriptions

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


[Kernel-packages] [Bug 1811417] Re: linux-kvm: 4.18.0-1007.7 -proposed tracker

2019-01-16 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811406
- phase: Testing -- verification-testing in progress
- phase-changed: Wednesday, 16. January 2019 23:01 UTC
+ phase: Testing -- regression-testing in progress
+ phase-changed: Thursday, 17. January 2019 02:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-kvm: 4.18.0-1007.7 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811406
  phase: Testing -- regression-testing in progress
  phase-changed: Thursday, 17. January 2019 02:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811417/+subscriptions

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


[Kernel-packages] [Bug 1811999] Re: [USB-Audio - Audioengine D3, playback] fails after a while (a second)

2019-01-16 Thread Daniel van Vugt
Maybe it works in that other system because 18.10 contains some bug fix
that is missing from your first system (that is 18.04).

I think more likely though it's just that your first system physically
isn't maintaining a clean USB connection. If that's a software problem
then this is a kernel bug but it sounds more like a hardware problem to
me:

[ 5937.978117] usb 1-1.4.2: USB disconnect, device number 16

Please try a different USB port, and/or a different machine that is
running 18.04 rather than 18.10.

** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)

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

Title:
  [USB-Audio - Audioengine D3, playback] fails after a while (a second)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  USB DAC stops playing sound after a second.
  I had problem with kernel 4.15. 
  So, I tried upgrading to 4.19 but still issue persists. 
  I think, we might need to add it to sound/usb/quirks.c

  I see following in dmesg

  [ 5937.978117] usb 1-1.4.2: USB disconnect, device number 16
  [ 5955.721597] usb 1-1.4.1: new full-speed USB device number 17 using xhci_hcd
  [ 5956.302910] usb 1-1.4.1: New USB device found, idVendor=2912, 
idProduct=120b, bcdDevice= 1.0c
  [ 5956.302917] usb 1-1.4.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [ 5956.302921] usb 1-1.4.1: Product: Audioengine D3
  [ 5956.302926] usb 1-1.4.1: Manufacturer: Audioengine
  [ 5956.302929] usb 1-1.4.1: SerialNumber: Audioengine
  [ 5956.320621] usb 1-1.4.1: 1:1: cannot get freq at ep 0x1
  [ 5956.920844] usb 1-1.4.1: 1:1: cannot get freq at ep 0x1
  [ 5956.938929] usb 1-1.4.1: 1:1: cannot get freq at ep 0x1

  And lsusb -v has following entry for the device.

  Bus 001 Device 017: ID 2912:120b
  Couldn't open device, some information will be missing
  Device Descriptor:
    bLength18
    bDescriptorType 1
    bcdUSB   1.00
    bDeviceClass0 (Defined at Interface level)
    bDeviceSubClass 0
    bDeviceProtocol 0
    bMaxPacketSize0 8
    idVendor   0x2912
    idProduct  0x120b
    bcdDevice1.0c
    iManufacturer   1
    iProduct2
    iSerial 3
    bNumConfigurations  1
    Configuration Descriptor:
  bLength 9
  bDescriptorType 2
  wTotalLength  131
  bNumInterfaces  2
  bConfigurationValue 1
  iConfiguration  0
  bmAttributes 0x80
    (Bus Powered)
  MaxPower  200mA
  Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber0
    bAlternateSetting   0
    bNumEndpoints   0
    bInterfaceClass 1 Audio
    bInterfaceSubClass  1 Control Device
    bInterfaceProtocol  0
    iInterface  0
    AudioControl Interface Descriptor:
  bLength 9
  bDescriptorType36
  bDescriptorSubtype  1 (HEADER)
  bcdADC   1.00
  wTotalLength   43
  bInCollection   1
  baInterfaceNr( 0)   1
    AudioControl Interface Descriptor:
  bLength12
  bDescriptorType36
  bDescriptorSubtype  2 (INPUT_TERMINAL)
  bTerminalID 5
  wTerminalType  0x0101 USB Streaming
  bAssocTerminal  0
  bNrChannels 2
  wChannelConfig 0x0003
    Left Front (L)
    Right Front (R)
  iChannelNames   0
  iTerminal   0
    AudioControl Interface Descriptor:
  bLength13
  bDescriptorType36
  bDescriptorSubtype  6 (FEATURE_UNIT)
  bUnitID 7
  bSourceID   5
  bControlSize2
  bmaControls( 0)  0x01
  bmaControls( 0)  0x00
    Mute Control
  bmaControls( 1)  0x02
  bmaControls( 1)  0x00
    Volume Control
  bmaControls( 2)  0x02
  bmaControls( 2)  0x00
    Volume Control
  iFeature0
    AudioControl Interface Descriptor:
  bLength 9
  bDescriptorType36
  bDescriptorSubtype  3 (OUTPUT_TERMINAL)
  bTerminalID 8
  wTerminalType  0x0301 Speaker
  bAssocTerminal  0
  bSourceID   7
  iTerminal   0
  Interface Descriptor:
    bLength 9
    bDescriptorType 4
    

[Kernel-packages] [Bug 1811979] Re: My bluetooth is not working since i am using ubuntu 18.04, it works fine in windows 7

2019-01-16 Thread Daniel van Vugt
It appears that you do have Bluetooth hardware (Ralink corp. RT3290),
but it is turned off:

2: hp-bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: no

Maybe it's staying off because the kernel driver isn't up to scratch yet
in 18.04, or missing firmware. To test this theory please try installing
a newer kernel from:

https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D


** Summary changed:

- My bluetooth is not working since i am using ubuntu 14.04,it works fine in 
windows 7
+ My bluetooth is not working since i am using ubuntu 18.04, it works fine in 
windows 7

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

** Changed in: bluez (Ubuntu)
   Status: New => Invalid

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

** Summary changed:

- My bluetooth is not working since i am using ubuntu 18.04, it works fine in 
windows 7
+ My bluetooth (RT3290) is not working since i am using ubuntu 18.04, it works 
fine in windows 7

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

Title:
  My bluetooth (RT3290) is not working since i am using ubuntu 18.04, it
  works fine in windows 7

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  bluetooth network in my ubuntu is not working.actually the on button in the 
setting does not turn bluetooth button in to ON, it remains OFF even if i click 
on it.i already installed bluez and blueman .
  i am using this version of ubuntu

  Description:Ubuntu 18.04.1 LTS

  Release:18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluetooth (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
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 16 15:10:56 2019
  InterestingModules: bluetooth
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=1a5a1726-0948-424a-a01e-de88efc704ca ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.18
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 226E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 74.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.18:bd05/21/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn226E:rvr74.19:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 0991100600087
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:

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

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


[Kernel-packages] [Bug 1811999] [NEW] [USB-Audio - Audioengine D3, playback] fails after a while (a second)

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

USB DAC stops playing sound after a second.
I had problem with kernel 4.15. 
So, I tried upgrading to 4.19 but still issue persists. 
I think, we might need to add it to sound/usb/quirks.c

I see following in dmesg

[ 5937.978117] usb 1-1.4.2: USB disconnect, device number 16
[ 5955.721597] usb 1-1.4.1: new full-speed USB device number 17 using xhci_hcd
[ 5956.302910] usb 1-1.4.1: New USB device found, idVendor=2912, 
idProduct=120b, bcdDevice= 1.0c
[ 5956.302917] usb 1-1.4.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[ 5956.302921] usb 1-1.4.1: Product: Audioengine D3
[ 5956.302926] usb 1-1.4.1: Manufacturer: Audioengine
[ 5956.302929] usb 1-1.4.1: SerialNumber: Audioengine
[ 5956.320621] usb 1-1.4.1: 1:1: cannot get freq at ep 0x1
[ 5956.920844] usb 1-1.4.1: 1:1: cannot get freq at ep 0x1
[ 5956.938929] usb 1-1.4.1: 1:1: cannot get freq at ep 0x1

And lsusb -v has following entry for the device.

Bus 001 Device 017: ID 2912:120b
Couldn't open device, some information will be missing
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   1.00
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 8
  idVendor   0x2912
  idProduct  0x120b
  bcdDevice1.0c
  iManufacturer   1
  iProduct2
  iSerial 3
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength  131
bNumInterfaces  2
bConfigurationValue 1
iConfiguration  0
bmAttributes 0x80
  (Bus Powered)
MaxPower  200mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   0
  bInterfaceClass 1 Audio
  bInterfaceSubClass  1 Control Device
  bInterfaceProtocol  0
  iInterface  0
  AudioControl Interface Descriptor:
bLength 9
bDescriptorType36
bDescriptorSubtype  1 (HEADER)
bcdADC   1.00
wTotalLength   43
bInCollection   1
baInterfaceNr( 0)   1
  AudioControl Interface Descriptor:
bLength12
bDescriptorType36
bDescriptorSubtype  2 (INPUT_TERMINAL)
bTerminalID 5
wTerminalType  0x0101 USB Streaming
bAssocTerminal  0
bNrChannels 2
wChannelConfig 0x0003
  Left Front (L)
  Right Front (R)
iChannelNames   0
iTerminal   0
  AudioControl Interface Descriptor:
bLength13
bDescriptorType36
bDescriptorSubtype  6 (FEATURE_UNIT)
bUnitID 7
bSourceID   5
bControlSize2
bmaControls( 0)  0x01
bmaControls( 0)  0x00
  Mute Control
bmaControls( 1)  0x02
bmaControls( 1)  0x00
  Volume Control
bmaControls( 2)  0x02
bmaControls( 2)  0x00
  Volume Control
iFeature0
  AudioControl Interface Descriptor:
bLength 9
bDescriptorType36
bDescriptorSubtype  3 (OUTPUT_TERMINAL)
bTerminalID 8
wTerminalType  0x0301 Speaker
bAssocTerminal  0
bSourceID   7
iTerminal   0
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber1
  bAlternateSetting   0
  bNumEndpoints   0
  bInterfaceClass 1 Audio
  bInterfaceSubClass  2 Streaming
  bInterfaceProtocol  0
  iInterface  0
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber1
  bAlternateSetting   1
  bNumEndpoints   2
  bInterfaceClass 1 Audio
  bInterfaceSubClass  2 Streaming
  bInterfaceProtocol  0
  iInterface  0
  AudioStreaming Interface Descriptor:
bLength 7
bDescriptorType36
bDescriptorSubtype  1 (AS_GENERAL)
bTerminalLink   5
bDelay  1 frames
wFormatTag  1 PCM
  AudioStreaming Interface Descriptor:
bLength20
bDescriptorType36
bDescriptorSubtype  2 (FORMAT_TYPE)
bFormatType 1 (FORMAT_TYPE_I)
bNrChannels 2
bSubframeSize   3
  

[Kernel-packages] [Bug 1811431] Re: linux-azure: 4.15.0-1037.39~16.04.1 -proposed tracker

2019-01-16 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811419
- phase: Promote to Proposed -- snap release to edge ready
- phase-changed: Thursday, 17. January 2019 00:37 UTC
+ phase: Promote to Proposed -- snap release to beta ready
+ phase-changed: Thursday, 17. January 2019 01:08 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in beta channel
snap-release-to-edge: Pending -- snap not in edge channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.15.0-1037.39~16.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811419
  phase: Promote to Proposed -- snap release to beta ready
  phase-changed: Thursday, 17. January 2019 01:08 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in beta channel
snap-release-to-edge: Pending -- snap not in edge channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811431/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-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-16 Thread Hui Wang
@vincezoml,

You also met the hissing problem? could you elaborate a little bit on
it?  And in what kernel versions did you meet this 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/1805079

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

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  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 1811431] Re: linux-azure: 4.15.0-1037.39~16.04.1 -proposed tracker

2019-01-16 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811419
- phase: Promote to Proposed -- snap release to beta ready
- phase-changed: Wednesday, 16. January 2019 21:03 UTC
+ phase: Promote to Proposed -- snap release to edge ready
+ phase-changed: Thursday, 17. January 2019 00:37 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in beta channel
snap-release-to-edge: Pending -- snap not in edge channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.15.0-1037.39~16.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811419
  phase: Promote to Proposed -- snap release to edge ready
  phase-changed: Thursday, 17. January 2019 00:37 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in beta channel
snap-release-to-edge: Pending -- snap not in edge channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811431/+subscriptions

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


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

2019-01-16 Thread Dipak
I also faced this same bug. I was casting video from my laptop to chrome
cast- for about one hour it worked fine and then suddenly video stopped
and laptop did not respond at all. It did not take any input. So, I had
to hit the power button and switch it off and start it again.

-Was using Chrome browser to cast the tab to watch the video online.
-My computer is Dell Inspiron 7000 with Intel core i7 8th gen cpu

-- 
You 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 1811417] Re: linux-kvm: 4.18.0-1007.7 -proposed tracker

2019-01-16 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811406
- phase: Testing -- regression-testing in progress
- phase-changed: Wednesday, 16. January 2019 22:30 UTC
+ phase: Testing -- verification-testing in progress
+ phase-changed: Wednesday, 16. January 2019 23:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-kvm: 4.18.0-1007.7 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811406
  phase: Testing -- verification-testing in progress
  phase-changed: Wednesday, 16. January 2019 23:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811417/+subscriptions

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


[Kernel-packages] [Bug 1811425] Re: linux-kvm: 4.15.0-1029.29 -proposed tracker

2019-01-16 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811419
- phase: Testing -- regression-testing in progress
- phase-changed: Wednesday, 16. January 2019 22:38 UTC
+ phase: Testing -- verification-testing in progress
+ phase-changed: Wednesday, 16. January 2019 23:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-kvm: 4.15.0-1029.29 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811419
  phase: Testing -- verification-testing in progress
  phase-changed: Wednesday, 16. January 2019 23:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811425/+subscriptions

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


[Kernel-packages] [Bug 1811425] Re: linux-kvm: 4.15.0-1029.29 -proposed tracker

2019-01-16 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811419
- phase: Testing -- verification-testing in progress
- phase-changed: Wednesday, 16. January 2019 21:31 UTC
+ phase: Testing -- regression-testing in progress
+ phase-changed: Wednesday, 16. January 2019 22:38 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-kvm: 4.15.0-1029.29 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811419
  phase: Testing -- regression-testing in progress
  phase-changed: Wednesday, 16. January 2019 22:38 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811425/+subscriptions

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


[Kernel-packages] [Bug 1652101] Re: Can't create nested AppArmor namespaces

2019-01-16 Thread brian mullan
>From what I understand, LXD is moving toward SNAP LXD as a default, so
not being able to run SNAP in an LXD container configured for "nesting":

re -

lxc config set  security.nesting true


Is basically going to prevent LXD from being used for Nested Containers.

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

Title:
  Can't create nested AppArmor namespaces

Status in AppArmor:
  Confirmed
Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A user with CAP_MAC_ADMIN in the init namespace can create an AppArmor
  policy namespace and load a profile belonging to that AppArmor
  namespace. Once that's done, the user can confine a process with that
  namespaced AppArmor profile and enter into a user namespace. That
  process can then load additional AppArmor profiles inside of the
  AppArmor and user namespace. Here's an example:

  We need to set up the namespace, n1, and load the profile, p1.
  $ export rules="file, signal, unix, dbus, ptrace, mount, pivot_root, 
capability,"
  $ sudo mkdir /sys/kernel/security/apparmor/policy/namespaces/n1
  $ echo "profile p1 { $rules }" | sudo apparmor_parser -qrn n1

  Now we enter into confinement using the AppArmor namespace and profile and 
then enter into an unprivileged user namespace
  $ aa-exec -n n1 -p p1 -- unshare -Ur

  We can now load profiles as the privileged user inside of the unprivileged 
user namespace
  # echo "profile test {}" | apparmor_parser -qr

  The reason for this bug report is that we cannot create a nested
  AppArmor policy namespace inside of the unprivileged user namespace

  # mkdir /sys/kernel/security/apparmor/policy/namespaces/n1/namespaces/p1
  mkdir: cannot create directory 
‘/sys/kernel/security/apparmor/policy/namespaces/n1/namespaces/p1’: Permission 
denied

  If that worked, we could adjust LXD to read
  /sys/kernel/security/apparmor/.ns_name to get the current AppArmor
  namespace, then create a new namespace under the current namespace,
  and leverage the nested namespace for its nested containers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1652101/+subscriptions

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


[Kernel-packages] [Bug 1811417] Re: linux-kvm: 4.18.0-1007.7 -proposed tracker

2019-01-16 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811406
- phase: Testing -- verification-testing in progress
- phase-changed: Wednesday, 16. January 2019 21:32 UTC
+ phase: Testing -- regression-testing in progress
+ phase-changed: Wednesday, 16. January 2019 22:30 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-kvm: 4.18.0-1007.7 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1811406
  phase: Testing -- regression-testing in progress
  phase-changed: Wednesday, 16. January 2019 22:30 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811417/+subscriptions

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


[Kernel-packages] [Bug 1811847] Re: linux-aws: -proposed tracker

2019-01-16 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Confirmed

** 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: 1811846
+ phase: Packaging -- ready to package
+ phase-changed: Wednesday, 16. January 2019 22:32 UTC
  reason:
-   prepare-package: Stalled -- waiting for master bug
+   prepare-package: Pending -- version not specified

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

Title:
  linux-aws:  -proposed tracker

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

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: 1811846
  phase: Packaging -- ready to package
  phase-changed: Wednesday, 16. January 2019 22:32 UTC
  reason:
prepare-package: Pending -- version not specified

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811847/+subscriptions

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


[Kernel-packages] [Bug 1811851] Re: linux-aws: -proposed tracker

2019-01-16 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Confirmed

** 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: 1811846
+ phase: Packaging -- ready to package
+ phase-changed: Wednesday, 16. January 2019 22:33 UTC
  reason:
-   prepare-package: Stalled -- waiting for master bug
+   prepare-package: Pending -- version not specified

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

Title:
  linux-aws:  -proposed tracker

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

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: 1811846
  phase: Packaging -- ready to package
  phase-changed: Wednesday, 16. January 2019 22:33 UTC
  reason:
prepare-package: Pending -- version not specified

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811851/+subscriptions

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


[Kernel-packages] [Bug 1812123] [NEW] Upstream Commits Needed for DPDK on Azure

2019-01-16 Thread Joseph Salisbury
Public bug reported:

The following two patches are related to multi-queue.  They are needed
in the linux-azure kernels for DPDK to work properly on Azure.

b5679cebf780 ("vmbus: fix subchannel removal")
5e3c420dcca5 ("uio_hv_generic: set callbacks on open")


Both commits have also been cc'd to upstream stable.  Commit 5e3c420dcca5 is in 
mainline as of v4.20.  Commit b5679cebf780 is still in linux-next.

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


** Tags: kernel-hyper-v

** Package changed: linux (Ubuntu) => linux-azure (Ubuntu)

** Tags added: kernel-hyper-v

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

Title:
  Upstream Commits Needed for DPDK on Azure

Status in linux-azure package in Ubuntu:
  New

Bug description:
  The following two patches are related to multi-queue.  They are needed
  in the linux-azure kernels for DPDK to work properly on Azure.

  b5679cebf780 ("vmbus: fix subchannel removal")
  5e3c420dcca5 ("uio_hv_generic: set callbacks on open")

  
  Both commits have also been cc'd to upstream stable.  Commit 5e3c420dcca5 is 
in mainline as of v4.20.  Commit b5679cebf780 is still in linux-next.

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

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


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

2019-01-16 Thread Tom Chiverton
apport information

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

Title:
  Dell 7275 integrated webcam not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Duel booting with Windows shows the hardware works out-of-the-box
  there. Windows device manager calls it 'Intel AVSteam Camera 2500' on
  'Intel HD Graphics 515'.

  It claims the attach path is video\ven_8086\subsys\06D61028

  Upgrading to the 18.04 HWE kernel hasn't changed things.

  syslog, lspci and lsusb attached.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rachael1424 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-07-01 (564 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 044e:120f Alps Electric Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 7275
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=dbb9db13-e808-4c74-9929-04b7deb9c4c7 ro quiet splash 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: Upgraded to bionic on 2018-04-25 (266 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/12/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.1
  dmi.board.name: 0PDKYR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.1:bd09/12/2018:svnDellInc.:pnLatitude7275:pvr:rvnDellInc.:rn0PDKYR:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7275
  dmi.product.sku: 06D6
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1812114] RfKill.txt

2019-01-16 Thread Tom Chiverton
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1812114/+attachment/5229760/+files/RfKill.txt

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

Title:
  Dell 7275 integrated webcam not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Duel booting with Windows shows the hardware works out-of-the-box
  there. Windows device manager calls it 'Intel AVSteam Camera 2500' on
  'Intel HD Graphics 515'.

  It claims the attach path is video\ven_8086\subsys\06D61028

  Upgrading to the 18.04 HWE kernel hasn't changed things.

  syslog, lspci and lsusb attached.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rachael1424 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-07-01 (564 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 044e:120f Alps Electric Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 7275
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=dbb9db13-e808-4c74-9929-04b7deb9c4c7 ro quiet splash 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: Upgraded to bionic on 2018-04-25 (266 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/12/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.1
  dmi.board.name: 0PDKYR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.1:bd09/12/2018:svnDellInc.:pnLatitude7275:pvr:rvnDellInc.:rn0PDKYR:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7275
  dmi.product.sku: 06D6
  dmi.sys.vendor: Dell Inc.

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

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


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

2019-01-16 Thread Tom Chiverton
apport information

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

Title:
  Dell 7275 integrated webcam not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Duel booting with Windows shows the hardware works out-of-the-box
  there. Windows device manager calls it 'Intel AVSteam Camera 2500' on
  'Intel HD Graphics 515'.

  It claims the attach path is video\ven_8086\subsys\06D61028

  Upgrading to the 18.04 HWE kernel hasn't changed things.

  syslog, lspci and lsusb attached.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rachael1424 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-07-01 (564 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 044e:120f Alps Electric Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 7275
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=dbb9db13-e808-4c74-9929-04b7deb9c4c7 ro quiet splash 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: Upgraded to bionic on 2018-04-25 (266 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/12/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.1
  dmi.board.name: 0PDKYR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.1:bd09/12/2018:svnDellInc.:pnLatitude7275:pvr:rvnDellInc.:rn0PDKYR:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7275
  dmi.product.sku: 06D6
  dmi.sys.vendor: Dell Inc.

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

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


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

2019-01-16 Thread Tom Chiverton
apport information

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

Title:
  Dell 7275 integrated webcam not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Duel booting with Windows shows the hardware works out-of-the-box
  there. Windows device manager calls it 'Intel AVSteam Camera 2500' on
  'Intel HD Graphics 515'.

  It claims the attach path is video\ven_8086\subsys\06D61028

  Upgrading to the 18.04 HWE kernel hasn't changed things.

  syslog, lspci and lsusb attached.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rachael1424 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-07-01 (564 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 044e:120f Alps Electric Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 7275
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=dbb9db13-e808-4c74-9929-04b7deb9c4c7 ro quiet splash 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: Upgraded to bionic on 2018-04-25 (266 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/12/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.1
  dmi.board.name: 0PDKYR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.1:bd09/12/2018:svnDellInc.:pnLatitude7275:pvr:rvnDellInc.:rn0PDKYR:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7275
  dmi.product.sku: 06D6
  dmi.sys.vendor: Dell Inc.

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

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


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

2019-01-16 Thread Tom Chiverton
apport information

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

Title:
  Dell 7275 integrated webcam not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Duel booting with Windows shows the hardware works out-of-the-box
  there. Windows device manager calls it 'Intel AVSteam Camera 2500' on
  'Intel HD Graphics 515'.

  It claims the attach path is video\ven_8086\subsys\06D61028

  Upgrading to the 18.04 HWE kernel hasn't changed things.

  syslog, lspci and lsusb attached.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rachael1424 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-07-01 (564 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 044e:120f Alps Electric Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 7275
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=dbb9db13-e808-4c74-9929-04b7deb9c4c7 ro quiet splash 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: Upgraded to bionic on 2018-04-25 (266 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/12/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.1
  dmi.board.name: 0PDKYR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.1:bd09/12/2018:svnDellInc.:pnLatitude7275:pvr:rvnDellInc.:rn0PDKYR:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7275
  dmi.product.sku: 06D6
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1811846] Re: linux: 4.4.0-142.168 -proposed tracker

2019-01-16 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

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

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

** 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: bug 1811847 (linux-aws), bug 1811848 (linux-lts-xenial)
  derivatives: bug 1811851 (linux-aws), bug 1811852 (linux-euclid), bug 1811853 
(linux-kvm), bug 1811854 (linux-raspi2), bug 1811855 (linux-snapdragon)
  -- swm properties --
- phase: Packaging -- packaging in progress
- phase-changed: Wednesday, 16. January 2019 03:38 UTC
+ phase: Packaging -- uploaded
+ phase-changed: Wednesday, 16. January 2019 22:08 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
+   promote-to-proposed: Ongoing -- builds not complete

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

Title:
  linux: 4.4.0-142.168 -proposed tracker

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

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

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

  backports: bug 1811847 (linux-aws), bug 1811848 (linux-lts-xenial)
  derivatives: bug 1811851 (linux-aws), bug 1811852 (linux-euclid), bug 1811853 
(linux-kvm), bug 1811854 (linux-raspi2), bug 1811855 (linux-snapdragon)
  -- swm properties --
  phase: Packaging -- uploaded
  phase-changed: Wednesday, 16. January 2019 22:08 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811846/+subscriptions

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


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

2019-01-16 Thread Tom Chiverton
apport information

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

Title:
  Dell 7275 integrated webcam not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Duel booting with Windows shows the hardware works out-of-the-box
  there. Windows device manager calls it 'Intel AVSteam Camera 2500' on
  'Intel HD Graphics 515'.

  It claims the attach path is video\ven_8086\subsys\06D61028

  Upgrading to the 18.04 HWE kernel hasn't changed things.

  syslog, lspci and lsusb attached.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rachael1424 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-07-01 (564 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 044e:120f Alps Electric Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 7275
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=dbb9db13-e808-4c74-9929-04b7deb9c4c7 ro quiet splash 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: Upgraded to bionic on 2018-04-25 (266 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/12/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.1
  dmi.board.name: 0PDKYR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.1:bd09/12/2018:svnDellInc.:pnLatitude7275:pvr:rvnDellInc.:rn0PDKYR:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7275
  dmi.product.sku: 06D6
  dmi.sys.vendor: Dell Inc.

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

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


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

2019-01-16 Thread Tom Chiverton
apport information

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

Title:
  Dell 7275 integrated webcam not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Duel booting with Windows shows the hardware works out-of-the-box
  there. Windows device manager calls it 'Intel AVSteam Camera 2500' on
  'Intel HD Graphics 515'.

  It claims the attach path is video\ven_8086\subsys\06D61028

  Upgrading to the 18.04 HWE kernel hasn't changed things.

  syslog, lspci and lsusb attached.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rachael1424 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-07-01 (564 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 044e:120f Alps Electric Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 7275
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=dbb9db13-e808-4c74-9929-04b7deb9c4c7 ro quiet splash 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: Upgraded to bionic on 2018-04-25 (266 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/12/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.1
  dmi.board.name: 0PDKYR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.1:bd09/12/2018:svnDellInc.:pnLatitude7275:pvr:rvnDellInc.:rn0PDKYR:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7275
  dmi.product.sku: 06D6
  dmi.sys.vendor: Dell Inc.

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

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


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

2019-01-16 Thread Tom Chiverton
apport information

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

Title:
  Dell 7275 integrated webcam not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Duel booting with Windows shows the hardware works out-of-the-box
  there. Windows device manager calls it 'Intel AVSteam Camera 2500' on
  'Intel HD Graphics 515'.

  It claims the attach path is video\ven_8086\subsys\06D61028

  Upgrading to the 18.04 HWE kernel hasn't changed things.

  syslog, lspci and lsusb attached.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rachael1424 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-07-01 (564 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 044e:120f Alps Electric Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 7275
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=dbb9db13-e808-4c74-9929-04b7deb9c4c7 ro quiet splash 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: Upgraded to bionic on 2018-04-25 (266 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/12/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.1
  dmi.board.name: 0PDKYR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.1:bd09/12/2018:svnDellInc.:pnLatitude7275:pvr:rvnDellInc.:rn0PDKYR:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7275
  dmi.product.sku: 06D6
  dmi.sys.vendor: Dell Inc.

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

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


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

2019-01-16 Thread Tom Chiverton
apport information

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

Title:
  Dell 7275 integrated webcam not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Duel booting with Windows shows the hardware works out-of-the-box
  there. Windows device manager calls it 'Intel AVSteam Camera 2500' on
  'Intel HD Graphics 515'.

  It claims the attach path is video\ven_8086\subsys\06D61028

  Upgrading to the 18.04 HWE kernel hasn't changed things.

  syslog, lspci and lsusb attached.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rachael1424 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-07-01 (564 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 044e:120f Alps Electric Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 7275
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=dbb9db13-e808-4c74-9929-04b7deb9c4c7 ro quiet splash 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: Upgraded to bionic on 2018-04-25 (266 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/12/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.1
  dmi.board.name: 0PDKYR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.1:bd09/12/2018:svnDellInc.:pnLatitude7275:pvr:rvnDellInc.:rn0PDKYR:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7275
  dmi.product.sku: 06D6
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1812114] Re: Dell 7275 integrated webcam not detected

2019-01-16 Thread Tom Chiverton
apport information

** Tags added: apport-collected bionic

** Description changed:

  Duel booting with Windows shows the hardware works out-of-the-box there.
  Windows device manager calls it 'Intel AVSteam Camera 2500' on 'Intel HD
  Graphics 515'.
  
  It claims the attach path is video\ven_8086\subsys\06D61028
  
  Upgrading to the 18.04 HWE kernel hasn't changed things.
  
  syslog, lspci and lsusb attached.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.5
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  rachael1424 F pulseaudio
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2017-07-01 (564 days ago)
+ InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
+  Bus 001 Device 002: ID 044e:120f Alps Electric Co., Ltd 
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: Dell Inc. Latitude 7275
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=dbb9db13-e808-4c74-9929-04b7deb9c4c7 ro quiet splash 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: Upgraded to bionic on 2018-04-25 (266 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
+ _MarkForUpload: True
+ dmi.bios.date: 09/12/2018
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 1.4.1
+ dmi.board.name: 0PDKYR
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A00
+ dmi.chassis.type: 8
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.1:bd09/12/2018:svnDellInc.:pnLatitude7275:pvr:rvnDellInc.:rn0PDKYR:rvrA00:cvnDellInc.:ct8:cvr:
+ dmi.product.family: Latitude
+ dmi.product.name: Latitude 7275
+ dmi.product.sku: 06D6
+ dmi.sys.vendor: Dell Inc.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1812114/+attachment/5229749/+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/1812114

Title:
  Dell 7275 integrated webcam not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Duel booting with Windows shows the hardware works out-of-the-box
  there. Windows device manager calls it 'Intel AVSteam Camera 2500' on
  'Intel HD Graphics 515'.

  It claims the attach path is video\ven_8086\subsys\06D61028

  Upgrading to the 18.04 HWE kernel hasn't changed things.

  syslog, lspci and lsusb attached.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rachael1424 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-07-01 (564 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 044e:120f Alps Electric Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 7275
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=dbb9db13-e808-4c74-9929-04b7deb9c4c7 ro quiet splash 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: Upgraded to bionic on 2018-04-25 (266 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/12/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.1
  dmi.board.name: 0PDKYR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.1:bd09/12/2018:svnDellInc.:pnLatitude7275:pvr:rvnDellInc.:rn0PDKYR:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7275
  dmi.product.sku: 06D6
  dmi.sys.vendor: Dell Inc.

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

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

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

2019-01-16 Thread Tom Chiverton
apport information

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

Title:
  Dell 7275 integrated webcam not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Duel booting with Windows shows the hardware works out-of-the-box
  there. Windows device manager calls it 'Intel AVSteam Camera 2500' on
  'Intel HD Graphics 515'.

  It claims the attach path is video\ven_8086\subsys\06D61028

  Upgrading to the 18.04 HWE kernel hasn't changed things.

  syslog, lspci and lsusb attached.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rachael1424 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-07-01 (564 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 044e:120f Alps Electric Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 7275
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=dbb9db13-e808-4c74-9929-04b7deb9c4c7 ro quiet splash 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: Upgraded to bionic on 2018-04-25 (266 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/12/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.1
  dmi.board.name: 0PDKYR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.1:bd09/12/2018:svnDellInc.:pnLatitude7275:pvr:rvnDellInc.:rn0PDKYR:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7275
  dmi.product.sku: 06D6
  dmi.sys.vendor: Dell Inc.

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

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


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

2019-01-16 Thread Tom Chiverton
apport information

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

Title:
  Dell 7275 integrated webcam not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Duel booting with Windows shows the hardware works out-of-the-box
  there. Windows device manager calls it 'Intel AVSteam Camera 2500' on
  'Intel HD Graphics 515'.

  It claims the attach path is video\ven_8086\subsys\06D61028

  Upgrading to the 18.04 HWE kernel hasn't changed things.

  syslog, lspci and lsusb attached.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rachael1424 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-07-01 (564 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 044e:120f Alps Electric Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 7275
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=dbb9db13-e808-4c74-9929-04b7deb9c4c7 ro quiet splash 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: Upgraded to bionic on 2018-04-25 (266 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/12/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.1
  dmi.board.name: 0PDKYR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.1:bd09/12/2018:svnDellInc.:pnLatitude7275:pvr:rvnDellInc.:rn0PDKYR:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7275
  dmi.product.sku: 06D6
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1812114] IwConfig.txt

2019-01-16 Thread Tom Chiverton
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1812114/+attachment/5229752/+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/1812114

Title:
  Dell 7275 integrated webcam not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Duel booting with Windows shows the hardware works out-of-the-box
  there. Windows device manager calls it 'Intel AVSteam Camera 2500' on
  'Intel HD Graphics 515'.

  It claims the attach path is video\ven_8086\subsys\06D61028

  Upgrading to the 18.04 HWE kernel hasn't changed things.

  syslog, lspci and lsusb attached.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rachael1424 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-07-01 (564 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 044e:120f Alps Electric Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 7275
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=dbb9db13-e808-4c74-9929-04b7deb9c4c7 ro quiet splash 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: Upgraded to bionic on 2018-04-25 (266 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/12/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.1
  dmi.board.name: 0PDKYR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.1:bd09/12/2018:svnDellInc.:pnLatitude7275:pvr:rvnDellInc.:rn0PDKYR:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7275
  dmi.product.sku: 06D6
  dmi.sys.vendor: Dell Inc.

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

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


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

2019-01-16 Thread Tom Chiverton
apport information

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

Title:
  Dell 7275 integrated webcam not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Duel booting with Windows shows the hardware works out-of-the-box
  there. Windows device manager calls it 'Intel AVSteam Camera 2500' on
  'Intel HD Graphics 515'.

  It claims the attach path is video\ven_8086\subsys\06D61028

  Upgrading to the 18.04 HWE kernel hasn't changed things.

  syslog, lspci and lsusb attached.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rachael1424 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-07-01 (564 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 044e:120f Alps Electric Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 7275
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=dbb9db13-e808-4c74-9929-04b7deb9c4c7 ro quiet splash 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: Upgraded to bionic on 2018-04-25 (266 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/12/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.1
  dmi.board.name: 0PDKYR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.1:bd09/12/2018:svnDellInc.:pnLatitude7275:pvr:rvnDellInc.:rn0PDKYR:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7275
  dmi.product.sku: 06D6
  dmi.sys.vendor: Dell Inc.

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

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


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

2019-01-16 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 1812114

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

Title:
  Dell 7275 integrated webcam not detected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Duel booting with Windows shows the hardware works out-of-the-box
  there. Windows device manager calls it 'Intel AVSteam Camera 2500' on
  'Intel HD Graphics 515'.

  It claims the attach path is video\ven_8086\subsys\06D61028

  Upgrading to the 18.04 HWE kernel hasn't changed things.

  syslog, lspci and lsusb attached.

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

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


[Kernel-packages] [Bug 1812114] Re: Dell 7275 integrated webcam not detected

2019-01-16 Thread Tom Chiverton
** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812114/+attachment/5229744/+files/syslog

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

Title:
  Dell 7275 integrated webcam not detected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Duel booting with Windows shows the hardware works out-of-the-box
  there. Windows device manager calls it 'Intel AVSteam Camera 2500' on
  'Intel HD Graphics 515'.

  It claims the attach path is video\ven_8086\subsys\06D61028

  Upgrading to the 18.04 HWE kernel hasn't changed things.

  syslog, lspci and lsusb attached.

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

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


[Kernel-packages] [Bug 1812114] Re: Dell 7275 integrated webcam not detected

2019-01-16 Thread Tom Chiverton
** Attachment added: "lsusb"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812114/+attachment/5229743/+files/lsusb

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

Title:
  Dell 7275 integrated webcam not detected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Duel booting with Windows shows the hardware works out-of-the-box
  there. Windows device manager calls it 'Intel AVSteam Camera 2500' on
  'Intel HD Graphics 515'.

  It claims the attach path is video\ven_8086\subsys\06D61028

  Upgrading to the 18.04 HWE kernel hasn't changed things.

  syslog, lspci and lsusb attached.

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

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


  1   2   3   >