date:20170908

[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/1614038

Title:
  o2cb configuration options ignored in 16.04

Status in linux package in Ubuntu:
  Expired

Bug description:
  We've been trying to add a 16.04 node (ocfs2-tools 1.6.4-3.1) to our
  existing OCFS2 filesystem based on Ubuntu 13.04 (ocfs2-tools
  1.6.4-2ubuntu1) and , Ubuntu 14.04 (ocfs2-tool 1.6.4-3ubuntu1)

   * Node1: Ubuntu 16.04, Slot 1, 10.22.44.21
   * Node2: Ubuntu 13.04, Slot 2, 10.22.44.22
   * Node3: Ubuntu 14.04, Slot 6, 10.22.44.23
   * Node4: Ubuntu 14.04, Slot 7, 10.22.44.24

  
  The exiting system has a O2CB_HEARTBEAT_THRESHOLD=61 setting, but when adding 
the new system these tweaks seem to be ignored.  Here's the syslog section:

  
  Aug 16 15:58:02 node1 kernel: [  936.294820] 
(o2hb-37AAEB0304,5741,7):o2hb_check_slot:895 ERROR: Node 2 on device sdc has a 
dead count of 122000 ms, but our count is 62000 ms.
  Aug 16 15:58:02 node1 kernel: [  936.294820] Please double check your 
configuration values for 'O2CB_HEARTBEAT_THRESHOLD'
  Aug 16 15:58:02 node1 kernel: [  936.294949] 
(o2hb-37AAEB0304,5741,7):o2hb_check_slot:895 ERROR: Node 6 on device sdc has a 
dead count of 122000 ms, but our count is 62000 ms.
  Aug 16 15:58:02 node1 kernel: [  936.294949] Please double check your 
configuration values for 'O2CB_HEARTBEAT_THRESHOLD'
  Aug 16 15:58:02 node1 kernel: [  936.295071] 
(o2hb-37AAEB0304,5741,7):o2hb_check_slot:895 ERROR: Node 7 on device sdc has a 
dead count of 122000 ms, but our count is 62000 ms.
  Aug 16 15:58:02 node1 kernel: [  936.295071] Please double check your 
configuration values for 'O2CB_HEARTBEAT_THRESHOLD'
  Aug 16 15:58:03 node1 kernel: [  937.123350] o2net: node node3 (num 6) at 
10.22.44.23: uses a heartbeat timeout of 12 ms, but we use 6 ms 
locally. Disconnecting.
  Aug 16 15:58:03 node1 kernel: [  937.393608] o2net: node node2 (num 2) at 
10.22.44.22: uses a heartbeat timeout of 12 ms, but we use 6 ms 
locally. Disconnecting.
  Aug 16 15:58:04 node1 kernel: [  938.055983] o2net: node node4 (num 7) at 
10.22.44.24: uses a heartbeat timeout of 12 ms, but we use 6 ms 
locally. Disconnecting.
  Aug 16 15:58:29 node1 kernel: [  963.213554] o2net: node node3 (num 6) at 
10.22.44.23: uses a heartbeat timeout of 12 ms, but we use 6 ms 
locally. Disconnecting.
  Aug 16 15:58:30 node1 kernel: [  964.057995] o2net: node node4 (num 7) at 
10.22.44.24: uses a heartbeat timeout of 12 ms, but we use 6 ms 
locally. Disconnecting.
  Aug 16 15:58:32 node1 kernel: [  966.404380] o2net: No connection established 
with node 2 after 30.0 seconds, check network and cluster configuration.
  Aug 16 15:58:32 node1 kernel: [  966.404390] o2net: No connection established 
with node 6 after 30.0 seconds, check network and cluster configuration.
  Aug 16 15:58:32 node1 kernel: [  966.404393] o2net: No connection established 
with node 7 after 30.0 seconds, check network and cluster configuration.
  Aug 16 15:58:59 node1 kernel: [  993.296012] o2net: node node3 (num 6) at 
10.22.44.23: uses a heartbeat timeout of 12 ms, but we use 6 ms 
locally. Disconnecting.
  Aug 16 15:59:00 node1 kernel: [  994.060435] o2net: node node4 (num 7) at 
10.22.44.24: uses a heartbeat timeout of 12 ms, but we use 6 ms 
locally. Disconnecting.
  Aug 16 15:59:02 node1 kernel: [  996.486396] o2net: No connection established 
with node 2 after 30.0 seconds, check network and cluster configuration.
  Aug 16 15:59:02 node1 kernel: [  996.486405] o2net: No connection established 
with node 6 after 30.0 seconds, check network and cluster configuration.
  Aug 16 15:59:02 node1 kernel: [  996.486409] o2net: No connection established 
with node 7 after 30.0 seconds, check network and cluster configuration.
  Aug 16 15:59:05 node1 kernel: [  999.582560] o2cb: This node could not 
connect to nodes: 2 6 7.
  Aug 16 15:59:05 node1 kernel: [  999.582607] o2cb: Cluster check failed. Fix 
errors before retrying.
  Aug 16 15:59:05 node1 kernel: [  999.582647] 
(mount.ocfs2,5740,1):ocfs2_dlm_init:3025 ERROR: status = -107
  Aug 16 15:59:05 node1 kernel: [  999.582814] 
(mount.ocfs2,5740,1):ocfs2_mount_volume:1863 ERROR: status = -107
  Aug 16 15:59:05 node1 kernel: [  999.582895] ocfs2: Unmounting device (8,32) 
on (node 0)
  Aug 16 15:59:05 node1 kernel: [  999.582905] 
(mount.ocfs2,5740,1):ocfs2_fill_super:1219 ERROR: status = -107

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

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

[Kernel-packages] [Bug 1676990] Re: new kernals wont boot

[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/1676990

Title:
  new kernals wont boot

Status in linux package in Ubuntu:
  Expired

Bug description:
  system wont boot unless i use an older kernal at time of booting. even
  after today i got a new kernal ending in .44 I think but it and .42do
  Not work  I have to select .40 to get the thing going.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-40.43-generic 4.8.17
  Uname: Linux 4.8.0-40-generic i686
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Mar 28 11:09:59 2017
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660G] [1002:9900] 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Trinity [Radeon HD 7660G] [17aa:3970]
  InstallationDate: Installed on 2017-01-25 (62 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2)
  MachineType: LENOVO IdeaPad Z585
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-40-generic 
root=UUID=d4d7b3d8-f6c3-48f6-b0d0-5473a63fe6f3 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/03/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 60CN95WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo
  dmi.board.vendor: LENOVO
  dmi.board.version: 3196FRU WIN8 STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad Z585
  dmi.modalias: 
dmi:bvnLENOVO:bvr60CN95WW:bd01/03/2013:svnLENOVO:pnIdeaPadZ585:pvrIdeaPadZ585:rvnLENOVO:rnLenovo:rvr3196FRUWIN8STD:cvnLENOVO:ct10:cvrIdeaPadZ585:
  dmi.product.name: IdeaPad Z585
  dmi.product.version: IdeaPad Z585
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.10.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Tue Mar 28 10:29:38 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6.1
  xserver.video_driver: radeon

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

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

[Kernel-packages] [Bug 1702803] Re: package linux-image-4.10.0-26-generic 4.10.0-26.30 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[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/1702803

Title:
  package linux-image-4.10.0-26-generic 4.10.0-26.30 failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Expired

Bug description:
  I hope this helps.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-26-generic 4.10.0-26.30
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  toshiba1755 F pulseaudio
   /dev/snd/controlC1:  toshiba1755 F pulseaudio
  Date: Fri Jun 30 20:57:33 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=96aaa576-2356-4c06-b2a5-1ff4dae50ca9
  InstallationDate: Installed on 2017-03-18 (110 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: TOSHIBA Satellite Pro C50-B
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=b9f02eff-8458-42d2-a4bb-22bba3c2fee4 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.1
  SourcePackage: linux
  Title: package linux-image-4.10.0-26-generic 4.10.0-26.30 failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: Upgraded to zesty on 2017-04-25 (72 days ago)
  dmi.bios.date: 04/11/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.20
  dmi.board.asset.tag: *
  dmi.board.name: ZSWAA
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: *
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.20:bd04/11/2014:svnTOSHIBA:pnSatelliteProC50-B:pvrPSCLVA-002001:rvnTOSHIBA:rnZSWAA:rvr1.00:cvnTOSHIBA:ct10:cvr*:
  dmi.product.name: Satellite Pro C50-B
  dmi.product.version: PSCLVA-002001
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1701994] Re: package linux-image-4.10.0-26-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[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/1701994

Title:
  package linux-image-4.10.0-26-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Expired

Bug description:
  I have ubuntu 17.04 ,but many time my laptop hanged. and many
  applications atomaticaly off.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-26-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mahipal1932 F pulseaudio
  Date: Mon Jul  3 01:23:04 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2017-04-23 (70 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Inspiron 3521
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic 
root=UUID=6fa1b222-ab75-434c-b4bb-83c481628432 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.1
  SourcePackage: linux
  Title: package linux-image-4.10.0-26-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0H579X
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd10/25/2013:svnDellInc.:pnInspiron3521:pvrA12:rvnDellInc.:rn0H579X:rvrA00:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron 3521
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1712867] Re: [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

The following packages/versions are available in the PPA
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/azure/ for
testing:

- crash - 7.1.4-1ubuntu4.2~rc1
- kexec-tools - 1:2.0.10-1ubuntu2.4~rc1
- linux-azure - 4.11.0-1010.10~rc2
- linux-meta-azure - 4.11.0.1010.10~rc1

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

Title:
  [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

Status in crash package in Ubuntu:
  In Progress
Status in kexec-tools package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  In Progress
Status in kexec-tools source package in Xenial:
  In Progress
Status in linux-azure source package in Xenial:
  In Progress

Bug description:
  Because the linux-azure kernel is based on 4.11, kexec on 16.04 gives the 
following error:
  kdump-tools[1436]: ELF core (kcore) parse failed

  Perhaps the artful kexec-tools should be backported?

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

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

[Kernel-packages] [Bug 1712867] Re: [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

I was able to make the xenial version of crash to work with both the
linux-generic and linux-azure kernels applying the following upstream
changes:

Commit: 7e0cb8b516788c7ba1ef9f32556df347ba0da187
Fix for Linux commit 0100301bfdf56a2a370c7157b5ab0fbf9313e1cd, which rewrote 
the X86_64 switch_to() code by embedding the __switch_to() call inside a new 
__switch_to_asm() assembly code ENTRY() function. Without the patch, the 
message "crash: cannot determine thread return address" gets displayed during 
initialization, and the "bt" command shows frame #0 starting at "schedule" 
instead of "__schedule". (ander...@redhat.com)
Commit: 63f7707d2b534bab2a18c52db41daae7e9c5e505
Fix for the "ps -t" option in 3.17 and later kernels that contain commit 
ccbf62d8a284cf181ac28c8e8407dd077d90dd4b, which changed the 
task_struct.start_time member from a struct timespec to a u64. Without the 
patch, the "RUN TIME" value is nonsensical. (ander...@redhat.com)

Commit: c1eb2b99e2d9201583aac5a664126d83039bddff
Fix for the "irq -s" option for Linux 4.2 and later kernels.  Without the 
patch, the irq_chip.name string (e.g. "IO-APIC", "PCI-MSI", etc.) is missing 
from the display. (rabin.vinc...@axis.com)

Commit: 76a71fed90c6304110dbce61d6c833543f2f1ac8
Improvement of the accuracy of the allocated objects count for each kmem_cache 
shown by "kmem -s" in kernels configured with CONFIG_SLUB. Without the patch, 
the values under the ALLOCATED column may be too large because cached per-cpu 
objects are counted as allocated. (vinayakm.l...@gmail.com)

Commit: 569002249b1d57162a1e94f529d295828d4e0253
When reading a task's task_struct.flags field, check for its size, which was 
changed from an unsigned long to an unsigned int. (dave.kleik...@oracle.com)

Commit: 10192898cf59b7b4bb102ef39c72ab65bd401471
Fix for Linux 4.8-rc1 commit 500462a9de657f86edaa102f8ab6bff7f7e43fc2, in which 
Thomas Gleixner redesigned the kernel timer mechanism to switch to a 
non-cascading wheel.  Without the patch, the "timer" command fails with the 
message "timer: zero-size memory allocation! (called from )" 
(ander...@redhat.com)

Commit: df08978f31ba39e94b3096804f4e0776373c8b53
Improvement of the "dev -d" option to display I/O statics for disks whose 
device driver uses the blk-mq interface.  Currently "dev -d" always displays 0 
in all fields for the blk-mq disk because blk-mq does not increment/decrement 
request_list.count[2] on I/O creation and I/O completion.  The following values 
are used in blk-mq in such situations:   - I/O creation:   
blk_mq_ctx.rq_dispatched[2]   - I/O completion: blk_mq_ctx.rq_completed[2] So, 
we can get the counter of in-progress I/Os as follows:   in progress I/Os == 
rq_dispatched - rq_completed This patch displays the result of above 
calculation for the disk. It determines whether the device driver uses blk-mq 
if the request_queue.mq_ops is not NULL.  The "DRV" field is displayed as 
"N/A(MQ)" if the value for in-flight in the device driver does not exist for 
blk-mq. (m.miz...@jp.fujitsu.com)

Commit: db552975315fec06a957c937803935d8fbddfd2d
Introduction of a new "bt -v" option that checks the kernel stack of all tasks 
for evidence of stack overflows.  It does so by verifying the thread_info.task 
address, ensuring the thread_info.cpu value is a valid cpu number, and checking 
the end of the stack for the STACK_END_MAGIC value. (ander...@redhat.com)

Commit: c9f932440bd06f0a3d6d3ecc30d5c670021d5e5a
Fix for Linux 4.9-rc1 commits 15f4eae70d365bba26854c90b6002aaabb18c8aa and 
c65eacbe290b8141554c71b2c94489e73ade8c8d, which have introduced a new 
CONFIG_THREAD_INFO_IN_TASK configuration.  This configuration moves each task's 
thread_info structure from the base of its kernel stack into its task_struct.  
Without the patch, the crash session fails during initialization with the error 
"crash: invalid structure member offset: thread_info_cpu". (ander...@redhat.com)

Commit: 24a696228c56fd4354d29abe05b206373e0c8bfb
Fix for Linux 4.10 commit 7fd8329ba502ef76dd91db561c7aed696b2c7720 
"taint/module: Clean up global and module taint flags handling". Without the 
patch, when running against Linux 4.10-rc1 and later kernels, the crash utility 
fails during session initialization with the message "crash: invalid structure 
size: tnt". (pan...@redhat.com)

Commit: e37dd7852f590e3334420e5b41a833085ab1d0b0
Prepare for the kernel's "taint_flag.true" and "taint_flag.false" member names 
to be changed to "c_true" and "c_false", which fixes build problems when an 
out-of-tree module defines "true" or "false". (ander...@redhat.com)

Commit: 651c824ffe2fd7eb8e416dbf4ff5c9a1da6ef7c6
Prevent the livepatch taint flag check during the system banner display from 
generating a fatal session-killing error if relevant kernel symbol names or 
data structures change in the future (again). (ander...@redhat.com)

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

[Kernel-packages] [Bug 1715655] Re: linux-aws: 4.4.0-1034.43 -proposed tracker

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

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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 series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  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: 1715651
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1715651] Re: linux: 4.4.0-95.118 -proposed tracker

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

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

Title:
  linux: 4.4.0-95.118 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  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: 1715652
  derivatives: 1715653,1715654,1715655,1715656,1715659
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1715651] Re: linux: 4.4.0-95.118 -proposed tracker

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

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

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

Title:
  linux: 4.4.0-95.118 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  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: 1715652
  derivatives: 1715653,1715654,1715655,1715656,1715659
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1715655] Re: linux-aws: 4.4.0-1034.43 -proposed tracker

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

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

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in 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: 1715651
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

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 1716065

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

Title:
  did not install properly

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  start button and other panel features missing in 4.11.14.  Themes,
  desktop, etc..., not there

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

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

[Kernel-packages] [Bug 1716065] [NEW] did not install properly

2017-09-08 Thread yonnie

Public bug reported:

start button and other panel features missing in 4.11.14.  Themes,
desktop, etc..., not there

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: 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/1716065

Title:
  did not install properly

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  start button and other panel features missing in 4.11.14.  Themes,
  desktop, etc..., not there

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

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

[Kernel-packages] [Bug 1715651] Re: linux: 4.4.0-95.118 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

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

** Changed in: kernel-sru-workflow/verification-testing
   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
  
  backports: 1715652
  derivatives: 1715653,1715654,1715655,1715656,1715659
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Thursday, 07. September 2017 16:30 UTC
- 
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Friday, 08. September 2017 22:31 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1715652
  derivatives: 1715653,1715654,1715655,1715656,1715659
  -- swm properties --
  boot-testing-requested: true
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Friday, 08. September 2017 22:31 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux: 4.4.0-95.118 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  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: 1715652
  derivatives: 1715653,1715654,1715655,1715656,1715659
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1715655] Re: linux-aws: 4.4.0-1034.43 -proposed tracker

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

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  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: 1715651
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1687262] Re: 16.10, 17.04, 17.10 Wired connection stopped working RTL 8111/8168/8411

2017-09-08 Thread Alexey Balmashnov

** Tags removed: kernel-request-4.10.0-22.24
** Tags added: regression-release

** Description changed:

+ == Regression details ==
+ Discovered in version: yakkety
+ Last known good version: xenial
+ 
  This is a regression.
  
  Upon upgrading 16.04 -> 16.10. Wired connection provided by
  "RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller" has stopped
  working.
  
  Quickly looked around for possible solution, and decided to go on with
  upgrade to 17.04, since it was my initial upgrade target anyway, and
  wireless on the system continued to function. So, ended up in this
  situation: running 17.04, wireless adapter is working, while wired does
  not work any more.
  
  Extra observation: I've also tried live session from USB based on 17.04
  ISO-image, wired network adapter just works in the live session.
  
  Conclusion: it is a software issue.
  
  Note that similar problem was reported be other user on the forum:
  
  https://ubuntuforums.org/showthread.php?t=2354675
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-generic 4.10.0.20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  alexei 1894 F pulseaudio
-  /dev/snd/controlC0:  alexei 1894 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  alexei 1894 F pulseaudio
+  /dev/snd/controlC0:  alexei 1894 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Sun Apr 30 09:33:01 2017
  HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546
  InstallationDate: Installed on 2016-01-06 (479 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-4.10.0-20-generic N/A
-  linux-backports-modules-4.10.0-20-generic  N/A
-  linux-firmware 1.164
+  linux-restricted-modules-4.10.0-20-generic N/A
+  linux-backports-modules-4.10.0-20-generic  N/A
+  linux-firmware 1.164
  RfKill:
-  0: phy0: Wireless LAN
-   Soft blocked: no
-   Hard blocked: no
+  0: phy0: Wireless LAN
+   Soft blocked: no
+   Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-23 (6 days ago)
  dmi.bios.date: 09/16/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: HM65-MXM
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

Title:
  16.10, 17.04, 17.10 Wired connection stopped working RTL
  8111/8168/8411

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Zesty:
  Confirmed

Bug description:
  == Regression details ==
  Discovered in version: yakkety
  Last known good version: xenial

  This is a regression.

  Upon upgrading 16.04 -> 16.10. Wired connection provided by
  "RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller" has
  stopped working.

  Quickly looked around for possible solution, and decided to go on with
  upgrade to 17.04, since it was my initial upgrade target anyway, and
  wireless on the system continued to function. So, ended up in this
  situation: running 17.04, wireless adapter is working, while wired
  does not work any more.

  Extra observation: I've also tried live session from USB based on
  17.04 ISO-image, wired network adapter just works in the live session.

  Conclusion: it is a software issue.

  Note that similar problem was reported be other user on the forum:

  https://ubuntuforums.org/showthread.php?t=2354675

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-generic 4.10.0.20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND

[Kernel-packages] [Bug 1687262] Re: 16.10, 17.04, 17.10 Wired connection stopped working RTL 8111/8168/8411

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is such a request.

We have noted that there is a newer version of the development kernel
than the one you last tested when this issue was found. Please test
again with the newer kernel and indicate in the bug if this issue still
exists or not.

You can update to the latest development kernel by simply running the
following commands in a terminal window:

sudo apt-get update
sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to
Confirmed. If the bug no longer exists, change the bug status from
Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add
a tag named: bot-stop-nagging.

Thank you for your help, we really do appreciate it.

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

** Tags added: kernel-request-4.10.0-22.24

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

Title:
16.10, 17.04, 17.10 Wired connection stopped working RTL
8111/8168/8411

Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Zesty:
Confirmed

Bug description:
== Regression details ==
Discovered in version: yakkety
Last known good version: xenial

This is a regression.

Upon upgrading 16.04 -> 16.10. Wired connection provided by
"RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller" has
stopped working.

Quickly looked around for possible solution, and decided to go on with
upgrade to 17.04, since it was my initial upgrade target anyway, and
wireless on the system continued to function. So, ended up in this
situation: running 17.04, wireless adapter is working, while wired
does not work any more.

Extra observation: I've also tried live session from USB based on
17.04 ISO-image, wired network adapter just works in the live session.

Conclusion: it is a software issue.

Note that similar problem was reported be other user on the forum:

https://ubuntuforums.org/showthread.php?t=2354675

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-generic 4.10.0.20.22
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: alexei 1894 F pulseaudio
/dev/snd/controlC0: alexei 1894 F pulseaudio
CurrentDesktop: Unity:Unity7
Date: Sun Apr 30 09:33:01 2017
HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546
InstallationDate: Installed on 2016-01-06 (479 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed
root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet
splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.10.0-20-generic N/A
linux-backports-modules-4.10.0-20-generic N/A
linux-firmware 1.164
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to zesty on 2017-04-23 (6 days ago)
dmi.bios.date: 09/16/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.10
dmi.board.name: HM65-MXM
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1687262] Re: 16.10, 17.04 Wired connection stopped working RTL 8111/8168/8411

2017-09-08 Thread Alexey Balmashnov

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

** Summary changed:

- 16.10, 17.04 Wired connection stopped working RTL 8111/8168/8411
+ 16.10, 17.04, 17.10 Wired connection stopped working RTL 8111/8168/8411

** Tags added: artful

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

Title:
  16.10, 17.04, 17.10 Wired connection stopped working RTL
  8111/8168/8411

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This is a regression.

  Upon upgrading 16.04 -> 16.10. Wired connection provided by
  "RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller" has
  stopped working.

  Quickly looked around for possible solution, and decided to go on with
  upgrade to 17.04, since it was my initial upgrade target anyway, and
  wireless on the system continued to function. So, ended up in this
  situation: running 17.04, wireless adapter is working, while wired
  does not work any more.

  Extra observation: I've also tried live session from USB based on
  17.04 ISO-image, wired network adapter just works in the live session.

  Conclusion: it is a software issue.

  Note that similar problem was reported be other user on the forum:

  https://ubuntuforums.org/showthread.php?t=2354675

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-generic 4.10.0.20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alexei 1894 F pulseaudio
   /dev/snd/controlC0:  alexei 1894 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Sun Apr 30 09:33:01 2017
  HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546
  InstallationDate: Installed on 2016-01-06 (479 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-23 (6 days ago)
  dmi.bios.date: 09/16/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: HM65-MXM
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1687262] Re: 16.10, 17.04 Wired connection stopped working RTL 8111/8168/8411

2017-09-08 Thread Alexey Balmashnov

Upgraded to artful beta - the issue persists.

$ lsb_release -a
LSB Version:
core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:printing-9.20160110ubuntu5-amd64:printing-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
Distributor ID: Ubuntu
Description:Ubuntu Artful Aardvark (development branch)
Release:17.10
Codename:   artful


Moreover, it became worse. Now if I disable manual configuration in 
/etc/network/interfaces (as described in comment above 
https://bugs.launchpad.net/ubuntu/zesty/+source/linux/+bug/1687262/comments/4) 
the system does not boot.

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

Title:
  16.10, 17.04 Wired connection stopped working RTL 8111/8168/8411

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

Bug description:
  This is a regression.

  Upon upgrading 16.04 -> 16.10. Wired connection provided by
  "RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller" has
  stopped working.

  Quickly looked around for possible solution, and decided to go on with
  upgrade to 17.04, since it was my initial upgrade target anyway, and
  wireless on the system continued to function. So, ended up in this
  situation: running 17.04, wireless adapter is working, while wired
  does not work any more.

  Extra observation: I've also tried live session from USB based on
  17.04 ISO-image, wired network adapter just works in the live session.

  Conclusion: it is a software issue.

  Note that similar problem was reported be other user on the forum:

  https://ubuntuforums.org/showthread.php?t=2354675

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-generic 4.10.0.20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alexei 1894 F pulseaudio
   /dev/snd/controlC0:  alexei 1894 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Sun Apr 30 09:33:01 2017
  HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546
  InstallationDate: Installed on 2016-01-06 (479 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-23 (6 days ago)
  dmi.bios.date: 09/16/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: HM65-MXM
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1712867] Re: [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

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

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

Title:
  [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

Status in crash package in Ubuntu:
  In Progress
Status in kexec-tools package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  In Progress
Status in kexec-tools source package in Xenial:
  In Progress
Status in linux-azure source package in Xenial:
  In Progress

Bug description:
  Because the linux-azure kernel is based on 4.11, kexec on 16.04 gives the 
following error:
  kdump-tools[1436]: ELF core (kcore) parse failed

  Perhaps the artful kexec-tools should be backported?

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

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

[Kernel-packages] [Bug 882147] Re: overlayfs does not implement inotify interfaces correctly

2017-09-08 Thread Bryan Quigley

tail -f /var/log/syslog worked for me with 17.10 dev | kernel 4.12.
(Tested by turning network on and off).

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

Title:
  overlayfs does not implement inotify interfaces correctly

Status in coreutils package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Triaged
Status in coreutils source package in Precise:
  Confirmed
Status in linux source package in Precise:
  Triaged

Bug description:
  When using tail on the liveCD some updates are not reported.  This
  seems to be triggered by tail using inotify to identify modified
  files.  Overlayfs does not appear to be implementing inotify quite the
  way you might hope reporting only against the underlying filesystems.

  Related bugs:
   * bug 1213925:  upstart should notice "/etc" inode change

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: linux-image-3.0.0-12-generic 3.0.0-12.20
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
     Subdevices: 0/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  apw2296 F pulseaudio
   /dev/snd/pcmC0D0c:   apw2296 F...m pulseaudio
   /dev/snd/pcmC0D0p:   apw2296 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfc70 irq 47'
     Mixer name : 'Intel Cantiga HDMI'
     Components : 'HDA:111d7675,1028029f,00100103 
HDA:80862802,80860101,0010'
     Controls  : 20
     Simple ctrls  : 11
  Date: Wed Oct 26 17:46:16 2011
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=d8328455-deac-4bae-877d-c408d371cefe
  MachineType: Dell Inc. Studio 1537
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic 
root=UUID=cf503727-25f2-4ecd-b0f3-2b894523bcba ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-12-generic N/A
   linux-backports-modules-3.0.0-12-generic  N/A
   linux-firmware1.60
  SourcePackage: linux
  UpgradeStatus: Upgraded to oneiric on 2011-10-17 (9 days ago)
  WpaSupplicantLog:

  dmi.bios.date: 09/22/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A03
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd09/22/2008:svnDellInc.:pnStudio1537:pvrA03:rvnDellInc.:rn:rvrA03:cvnDellInc.:ct8:cvrA03:
  dmi.product.name: Studio 1537
  dmi.product.version: A03
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1713576] Comment bridged from LTC Bugzilla

2017-09-08 Thread bugproxy

--- Comment From jhop...@us.ibm.com 2017-09-08 15:59 EDT---
Yes I installed all 9 .debs, I just re-dowloaded, installed, booted but still 
no luck.

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

Title:
  More migrations with constant load

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

Bug description:
  == Comment: #0 - PUVICHAKRAVARTHY RAMACHANDRAN  - 2017-08-06 13:44:45 ==
  ---Problem Description---
  Significantly higher number of task migrations when the load is fixed but not 
balanced across cores.
   
  ---uname output---
  Linux isvbos3 4.10.0-29-generic #33~16.04.1-Ubuntu SMP Tue Jul 25 18:17:06 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  Power9 dd2.0 

  Machine Type = Power9 
   
  ---Steps to Reproduce---
   Benchmark : Multithreaded - cpu intensive. The system had 2 socket/ 32 
cores/ SMT4 mode.

  When 64 threads was run - the migrations were less over 10s interval.
  when 80 threads were run - the migrations were very high.

  Ideally, it should have been very minimal, as the over all load was constant
   
  == Comment: #3 - SRIKAR DRONAMRAJU - 2017-08-11 06:56:47 ==
  As suspected (commit :  05b40e0577 : "sched/fair: Prefer sibiling only if 
local group is under-utilized")
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=05b40e0577
  should fix the problem

  Ran ' perf stat -a -r 5 -e sched:sched_migrate_task 
/home/srikar/work/ebizzy-0.3/ebizzy -t 35 -S 100'
  to detect the problem and verify the fix

  Here is perf stat without fix.

  Performance counter stats for 'system wide' (5 runs):

   7,758  sched:sched_migrate_task
  ( +-  1.28% )

   100.015658079 seconds time elapsed
  ( +-  0.00% )

  perf stat with fix.

  Performance counter stats for 'system wide' (5 runs):

 415  sched:sched_migrate_task
  ( +- 11.74% )

   100.016021787 seconds time elapsed
  ( +-  0.00% )

  
  git describe on upstream kernel says v4.11-rc2
  # git describe 05b40e0577
  v4.11-rc2-227-g05b40e0

  == Comment: #4 - SRIKAR DRONAMRAJU - 2017-08-11 07:05:37 ==
  Attaching the patch that needs to be applied to fix this bug.
  Verified that patch fixes the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1713576/+subscriptions

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

[Kernel-packages] [Bug 1712867] Re: [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

2017-09-08 Thread Joshua R. Poulson

Looks good! Glad we're making progress.

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

Title:
  [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

Status in crash package in Ubuntu:
  Confirmed
Status in kexec-tools package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  In Progress
Status in kexec-tools source package in Xenial:
  In Progress
Status in linux-azure source package in Xenial:
  In Progress

Bug description:
  Because the linux-azure kernel is based on 4.11, kexec on 16.04 gives the 
following error:
  kdump-tools[1436]: ELF core (kcore) parse failed

  Perhaps the artful kexec-tools should be backported?

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

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

[Kernel-packages] [Bug 1712867] Re: [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

linux-azure kernel patch: https://lists.ubuntu.com/archives/kernel-
team/2017-September/086944.html

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

Title:
  [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

Status in crash package in Ubuntu:
  Confirmed
Status in kexec-tools package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  In Progress
Status in kexec-tools source package in Xenial:
  In Progress
Status in linux-azure source package in Xenial:
  In Progress

Bug description:
  Because the linux-azure kernel is based on 4.11, kexec on 16.04 gives the 
following error:
  kdump-tools[1436]: ELF core (kcore) parse failed

  Perhaps the artful kexec-tools should be backported?

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

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

[Kernel-packages] [Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue

Will it not load by default?

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

Title:
  Not Suspending When Lid is Closed Causing Heat Issue

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I installed Ubuntu Budgie 17.04 64-bit. I installed the operating
  system and then when booted, I apt-get update and apt-get upgrade. I
  went to the coffee shop and used the system for a while. When I came
  home I left my laptop Dell XPS 9360 in its leather case and inside my
  laptop bag. I left to do some errands and came back to a really hot
  laptop and case. The system had not gone to sleep when I closed the
  lid and the computer was very hot. I have attached a copy of the log
  files.

  I then:

  sudo vi /etc/systemd/logind.conf

  Changed: HandleLidSwitchDocked=suspend

  when I close the lid now it gives me a password to login when I open the lid, 
but I am not sure if it is sleeping properly. Please assist, as I do not want 
my laptop battery damaged by this heat again.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shawn  1786 F pulseaudio
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-04 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/02/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.0
  dmi.board.name: 05JK94
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.0:bd08/02/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1715655] Re: linux-aws: 4.4.0-1034.43 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1715651
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Friday, 08. September 2017 19:31 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1715651
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Friday, 08. September 2017 19:31 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  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: 1715651
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1697556] Re: Computer freezes after login - 4.10.0-22-generic

2017-09-08 Thread Hagen Kuehn

I have reviewed the kernel source code that was committed between the
Ubuntu-4.10.0-21.23 and Ubuntu-4.10.0-22.24 and I believe commit
b93843fcde501b9264ac5dbe2c980eb0b479 introduced bug #1697556.

Commit b93843fcde501b9264ac5dbe2c980eb0b479 corresponds to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687045

In the light of this I believe that Thierry Reding 
and Stefan Bader  would be the best people
to look into this.

BTW, as it was not mentioned so far, Dell XPS 15 (9560) uses Intel HD
630 NVidia GeForce GTX 1050 with 4GB GDDR5.

** Attachment added: "Suspected commit that causes bug #1697556"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+attachment/4946672/+files/ubuntu-zesty-kernel-commit-b93843fcde501b9264ac5dbe2c980eb0b479.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/1697556

Title:
  Computer freezes after login - 4.10.0-22-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have got a new Ubuntu 17.04 install on a Dell XPS 15 (Intel(R)
  Core(TM) i7-7700HQ CPU @ 2.80GHz) that was installed a couple of days
  ago. Login worked fine too.

  A couple of days later I installed the suggested kernel update
  "4.10.0-22-generic". With kernel 4.10.0-22-generic, the computer
  freezes right after login (i.e. after pressing enter, the background
  image with the mouse is shown, no responses to any key strokes).

  Syslog excerpt:

  Jun 12 22:12:48 computername kernel: [   47.603358] NMI watchdog: BUG: soft 
lockup - CPU#1 stuck for 23s! [Xorg.wrap:1672]
  Jun 12 22:12:48 computername kernel: [   47.603360] Modules linked in: ccm 
msr arc4 cmac rfcomm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev media btusb btrtl bnep hid_multitouch nls_iso8859_1 
i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi dell_wmi 
dell_led dell_smbios snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel 
dcdbas ath10k_pci snd_hda_codec ath10k_core intel_rapl snd_hda_core ath 
x86_pkg_temp_thermal snd_hwdep intel_powerclamp mac80211 snd_pcm coretemp 
snd_seq_midi snd_seq_midi_event cfg80211 snd_rawmidi rtsx_pci_ms kvm_intel 
memstick kvm irqbypass crct10dif_pclmul joydev crc32_pclmul snd_seq 
ghash_clmulni_intel snd_seq_device input_leds snd_timer serio_raw snd soundcore 
idma64 virt_dma mei_me mei shpchp processor_thermal_device intel_soc_dts_iosf 
intel_lpss_pci intel_pch_thermal
  Jun 12 22:12:48 computername kernel: [   47.603422]  hci_uart btbcm btqca 
btintel bluetooth dell_smo8800 intel_hid intel_lpss_acpi sparse_keymap 
intel_lpss tpm_crb int3403_thermal int3400_thermal acpi_als 
int340x_thermal_zone acpi_thermal_rel acpi_pad kfifo_buf industrialio mac_hid 
pcbc aesni_intel crypto_simd glue_helper cryptd aes_x86_64 dm_crypt parport_pc 
ppdev lp parport ip_tables x_tables autofs4 nouveau rtsx_pci_sdmmc i915 ttm 
i2c_algo_bit drm_kms_helper syscopyarea mxm_wmi sysfillrect psmouse sysimgblt 
fb_sys_fops nvme drm nvme_core rtsx_pci ahci libahci i2c_hid hid 
pinctrl_sunrisepoint video wmi pinctrl_intel fjes
  Jun 12 22:12:48 computername kernel: [   47.603453] CPU: 1 PID: 1672 Comm: 
Xorg.wrap Not tainted 4.10.0-22-generic #24-Ubuntu
  Jun 12 22:12:48 computername kernel: [   47.603453] Hardware name: Dell Inc. 
XPS 15 9560/05FFDN, BIOS 1.3.3 05/08/2017

  
  Note, this problem is observed with kernel 4.10.0-22-generic whereas it's not 
observed with 4.10.0-21-generic. As I was not able to login to my computer I am 
writing this bug report while it runs on kernel 4.10.0-21-generic. Therefore 
the information attached through the "ubuntu-bug linux" command here, are 
referring to the kernel that is actually working. I decided to nonetheless 
include that information as it might contain other kernel unrelated information 
that would help you troubleshooting.

  Please see attached file "syslog-4.10.0-22-generic-freeze-after-
  login.log" for the full syslog.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-21-generic 4.10.0-21.23
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hkuehn 1796 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jun 12 23:17:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-05-30 (13 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. 
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[Kernel-packages] [Bug 1716033] Re: [SRU][Zesty] enable TPM CRB driver on ARM64 for Qualcomm Centriq 2400

2017-09-08 Thread Manoj Iyer

** Description changed:

  [Impact]
  Enable TPM CRB driver on ARM64 for Qualcomm Centriq 2400. Where, control area 
buffer address is greater than 32-bit.
  
  [Test]
  
  [Fix]
  This is upstream:
- 
- commit 19b7bf51fc3dcd8b743da72cfb69578de6eb9877
- Author: Jiandi An 
- Date: Sun Dec 18 22:20:53 2016 -0600
- 
- tpm, tpm_crb: Handle 64-bit resource in crb_check_resource()
+ 19b7bf51fc3d tpm, tpm_crb: Handle 64-bit resource in crb_check_resource()
+ 08eff49d63ca tpm/tpm_crb: Enable TPM CRB interface for ARM64
  
  [Regression Potential]
  None.

** Description changed:

  [Impact]
  Enable TPM CRB driver on ARM64 for Qualcomm Centriq 2400. Where, control area 
buffer address is greater than 32-bit.
  
  [Test]
+ Currently only built for X64 & ACPI. 
  
  [Fix]
  This is upstream:
  19b7bf51fc3d tpm, tpm_crb: Handle 64-bit resource in crb_check_resource()
  08eff49d63ca tpm/tpm_crb: Enable TPM CRB interface for ARM64
  
  [Regression Potential]
  None.

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

Title:
  [SRU][Zesty]  enable TPM CRB driver on ARM64 for Qualcomm Centriq 2400

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  Enable TPM CRB driver on ARM64 for Qualcomm Centriq 2400. Where, control area 
buffer address is greater than 32-bit.

  [Test]
  Currently only built for X64 & ACPI. 

  [Fix]
  This is upstream:
  19b7bf51fc3d tpm, tpm_crb: Handle 64-bit resource in crb_check_resource()
  08eff49d63ca tpm/tpm_crb: Enable TPM CRB interface for ARM64

  [Regression Potential]
  None.

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

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

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

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 1716033

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

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

Title:
  [SRU][Zesty]  enable TPM CRB driver on ARM64 for Qualcomm Centriq 2400

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  Enable TPM CRB driver on ARM64 for Qualcomm Centriq 2400. Where, control area 
buffer address is greater than 32-bit.

  [Test]

  [Fix]
  This is upstream:

  commit 19b7bf51fc3dcd8b743da72cfb69578de6eb9877
  Author: Jiandi An 
  Date: Sun Dec 18 22:20:53 2016 -0600

  tpm, tpm_crb: Handle 64-bit resource in crb_check_resource()

  [Regression Potential]
  None.

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

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

[Kernel-packages] [Bug 1712867] Re: [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

I was able to properly dump a vmcore with the following steps:

1. kexec-tools patches with:
   - ed15ba1b9977 build_mem_phdrs(): check if p_paddr is invalid
   - 9f62cbfc kexec/arch/i386: Add support for KASLR memory randomization
   - dbb99d938810 kexec-tools/x86: get_kernel_vaddr_and_size off-by-one fix

2. crashkernel increased to 192M

3. linux-azure patched with:
   - da63b6b20077 x86/KASLR: Fix kexec kernel boot crash when KASLR 
randomization fails

4. Forced storvsc instead of ata_piix.

With those changes, I was able to consistently dump vmcore images
without any issues using several types of azure instances.

Besides that the utility crash also needs to be updated. Currently the
xenial version of crash is not able to parse a linux-azure vmcore but
the artful version is.

I'm running some tests with the artful crash utility and the linux-
generic kernel to check if it's viable to bring that version to xenial.

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

** Changed in: kexec-tools (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: kexec-tools (Ubuntu Xenial)
   Status: Confirmed => In Progress

** Changed in: kexec-tools (Ubuntu)
   Importance: Undecided => High

** Changed in: kexec-tools (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: kexec-tools (Ubuntu)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

** Changed in: kexec-tools (Ubuntu Xenial)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

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

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

** Changed in: crash (Ubuntu)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

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

Title:
  [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

Status in crash package in Ubuntu:
  Confirmed
Status in kexec-tools package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  In Progress
Status in kexec-tools source package in Xenial:
  In Progress
Status in linux-azure source package in Xenial:
  In Progress

Bug description:
  Because the linux-azure kernel is based on 4.11, kexec on 16.04 gives the 
following error:
  kdump-tools[1436]: ELF core (kcore) parse failed

  Perhaps the artful kexec-tools should be backported?

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

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

[Kernel-packages] [Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue

2017-09-08 Thread Kai-Heng Feng

Did you reboot into the v4.13 kernel before suspend?

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

Title:
  Not Suspending When Lid is Closed Causing Heat Issue

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I installed Ubuntu Budgie 17.04 64-bit. I installed the operating
  system and then when booted, I apt-get update and apt-get upgrade. I
  went to the coffee shop and used the system for a while. When I came
  home I left my laptop Dell XPS 9360 in its leather case and inside my
  laptop bag. I left to do some errands and came back to a really hot
  laptop and case. The system had not gone to sleep when I closed the
  lid and the computer was very hot. I have attached a copy of the log
  files.

  I then:

  sudo vi /etc/systemd/logind.conf

  Changed: HandleLidSwitchDocked=suspend

  when I close the lid now it gives me a password to login when I open the lid, 
but I am not sure if it is sleeping properly. Please assist, as I do not want 
my laptop battery damaged by this heat again.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shawn  1786 F pulseaudio
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-04 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/02/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.0
  dmi.board.name: 05JK94
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.0:bd08/02/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1716033] [NEW] [SRU][Zesty] enable TPM CRB driver on ARM64 for Qualcomm Centriq 2400

2017-09-08 Thread Manoj Iyer

Public bug reported:

[Impact]
Enable TPM CRB driver on ARM64 for Qualcomm Centriq 2400. Where, control area 
buffer address is greater than 32-bit.

[Test]

[Fix]
This is upstream:

commit 19b7bf51fc3dcd8b743da72cfb69578de6eb9877
Author: Jiandi An 
Date: Sun Dec 18 22:20:53 2016 -0600

tpm, tpm_crb: Handle 64-bit resource in crb_check_resource()

[Regression Potential]
None.

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Manoj Iyer (manjo)
 Status: Incomplete


** Tags: qdf2400 zesty

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

Title:
  [SRU][Zesty]  enable TPM CRB driver on ARM64 for Qualcomm Centriq 2400

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  Enable TPM CRB driver on ARM64 for Qualcomm Centriq 2400. Where, control area 
buffer address is greater than 32-bit.

  [Test]

  [Fix]
  This is upstream:

  commit 19b7bf51fc3dcd8b743da72cfb69578de6eb9877
  Author: Jiandi An 
  Date: Sun Dec 18 22:20:53 2016 -0600

  tpm, tpm_crb: Handle 64-bit resource in crb_check_resource()

  [Regression Potential]
  None.

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

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

[Kernel-packages] [Bug 1712867] Re: [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

** No longer affects: makedumpfile (Ubuntu)

** No longer affects: makedumpfile (Ubuntu Xenial)

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

Title:
  [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

Status in kexec-tools package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  In Progress
Status in kexec-tools source package in Xenial:
  Confirmed
Status in linux-azure source package in Xenial:
  In Progress

Bug description:
  Because the linux-azure kernel is based on 4.11, kexec on 16.04 gives the 
following error:
  kdump-tools[1436]: ELF core (kcore) parse failed

  Perhaps the artful kexec-tools should be backported?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1712867/+subscriptions

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

[Kernel-packages] [Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue

Also, the log file. Sorry for all the posts.

** Attachment added: "log.on.suspend"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+attachment/4946659/+files/log.on.suspend

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

Title:
  Not Suspending When Lid is Closed Causing Heat Issue

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I installed Ubuntu Budgie 17.04 64-bit. I installed the operating
  system and then when booted, I apt-get update and apt-get upgrade. I
  went to the coffee shop and used the system for a while. When I came
  home I left my laptop Dell XPS 9360 in its leather case and inside my
  laptop bag. I left to do some errands and came back to a really hot
  laptop and case. The system had not gone to sleep when I closed the
  lid and the computer was very hot. I have attached a copy of the log
  files.

  I then:

  sudo vi /etc/systemd/logind.conf

  Changed: HandleLidSwitchDocked=suspend

  when I close the lid now it gives me a password to login when I open the lid, 
but I am not sure if it is sleeping properly. Please assist, as I do not want 
my laptop battery damaged by this heat again.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shawn  1786 F pulseaudio
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-04 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/02/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.0
  dmi.board.name: 05JK94
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.0:bd08/02/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue

I installed the kernel and clicked suspend on the taskbar at the top.

Then did "journalctl" and shift+g.

Sep 08 14:13:50 budgie gsd-sharing[1527]: Failed to StopUnit service: 
GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not 
Sep 08 14:13:50 budgie gsd-sharing[1527]: Failed to StopUnit service: 
GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit vino-server.servic
Sep 08 14:13:50 budgie systemd-resolved[941]: Switching to DNS server 
130.85.1.23 for interface wlp58s0.
Sep 08 14:13:50 budgie dbus[729]: [system] Successfully activated service 
'org.freedesktop.nm_dispatcher'
Sep 08 14:13:50 budgie systemd[1]: Started Network Manager Script Dispatcher 
Service.
Sep 08 14:13:50 budgie nm-dispatcher[3239]: req:1 'connectivity-change': new 
request (2 scripts)
Sep 08 14:13:50 budgie nm-dispatcher[3239]: req:1 'connectivity-change': start 
running ordered scripts...
Sep 08 14:13:50 budgie nm-dispatcher[3239]: req:2 'up' [wlp58s0]: new request 
(2 scripts)
Sep 08 14:13:50 budgie whoopsie[1084]: [14:13:50] The default IPv4 route is: 
/org/freedesktop/NetworkManager/ActiveConnection/1
Sep 08 14:13:50 budgie nm-dispatcher[3239]: req:2 'up' [wlp58s0]: start running 
ordered scripts...
Sep 08 14:13:50 budgie whoopsie[1084]: [14:13:50] Not a paid data plan: 
/org/freedesktop/NetworkManager/ActiveConnection/1
Sep 08 14:13:50 budgie whoopsie[1084]: [14:13:50] Found usable connection: 
/org/freedesktop/NetworkManager/ActiveConnection/1
Sep 08 14:13:50 budgie whoopsie[1084]: [14:13:50] online
Sep 08 14:13:51 budgie dbus-daemon[1333]: Activating service 
name='com.gexperts.Terminix'
Sep 08 14:13:51 budgie dbus-daemon[1333]: Successfully activated service 
'com.gexperts.Terminix'
Sep 08 14:13:51 budgie terminix[3275]: ../../../../gobject/gsignal.c:2523: 
signal 'notification-received' is invalid for instance '0x55b31b050
Sep 08 14:13:52 budgie avahi-daemon[723]: Joining mDNS multicast group on 
interface wlp58s0.IPv6 with address fe80::f50a:cc1e:f4f1:12cc.
Sep 08 14:13:52 budgie avahi-daemon[723]: New relevant interface wlp58s0.IPv6 
for mDNS.
Sep 08 14:13:52 budgie avahi-daemon[723]: Registering new address record for 
fe80::f50a:cc1e:f4f1:12cc on wlp58s0.*.
~
~
~
~
~
~
lines 1974-1996/1996 (END)
Sep 08 14:13:50 budgie NetworkManager[736]:   [1504894430.5641] manager: 
NetworkManager state is now CONNECTED_GLOBAL
Sep 08 14:13:50 budgie NetworkManager[736]:   [1504894430.5647] policy: 
set 'UMBC Visitor' (wlp58s0) as default for IPv4 routing and DNS
Sep 08 14:13:50 budgie NetworkManager[736]:   [1504894430.5667] device 
(wlp58s0): Activation: successful, device activated.
Sep 08 14:13:50 budgie systemd[1]: Starting Network Manager Script Dispatcher 
Service...
Sep 08 14:13:50 budgie gsd-sharing[1527]: Failed to StopUnit service: 
GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not l
Sep 08 14:13:50 budgie gsd-sharing[1527]: Failed to StopUnit service: 
GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit vino-server.service
Sep 08 14:13:50 budgie systemd-resolved[941]: Switching to DNS server 
130.85.1.23 for interface wlp58s0.
Sep 08 14:13:50 budgie dbus[729]: [system] Successfully activated service 
'org.freedesktop.nm_dispatcher'
Sep 08 14:13:50 budgie systemd[1]: Started Network Manager Script Dispatcher 
Service.
Sep 08 14:13:50 budgie nm-dispatcher[3239]: req:1 'connectivity-change': new 
request (2 scripts)
Sep 08 14:13:50 budgie nm-dispatcher[3239]: req:1 'connectivity-change': start 
running ordered scripts...
Sep 08 14:13:50 budgie nm-dispatcher[3239]: req:2 'up' [wlp58s0]: new request 
(2 scripts)
Sep 08 14:13:50 budgie whoopsie[1084]: [14:13:50] The default IPv4 route is: 
/org/freedesktop/NetworkManager/ActiveConnection/1
Sep 08 14:13:50 budgie nm-dispatcher[3239]: req:2 'up' [wlp58s0]: start running 
ordered scripts...
Sep 08 14:13:50 budgie whoopsie[1084]: [14:13:50] Not a paid data plan: 
/org/freedesktop/NetworkManager/ActiveConnection/1
Sep 08 14:13:50 budgie whoopsie[1084]: [14:13:50] Found usable connection: 
/org/freedesktop/NetworkManager/ActiveConnection/1
Sep 08 14:13:50 budgie whoopsie[1084]: [14:13:50] online
Sep 08 14:13:51 budgie dbus-daemon[1333]: Activating service 
name='com.gexperts.Terminix'
Sep 08 14:13:51 budgie dbus-daemon[1333]: Successfully activated service 
'com.gexperts.Terminix'
Sep 08 14:13:51 budgie terminix[3275]: ../../../../gobject/gsignal.c:2523: 
signal 'notification-received' is invalid for instance '0x55b31b050a
Sep 08 14:13:52 budgie avahi-daemon[723]: Joining mDNS multicast group on 
interface wlp58s0.IPv6 with address fe80::f50a:cc1e:f4f1:12cc.
Sep 08 14:13:52 budgie avahi-daemon[723]: New relevant interface wlp58s0.IPv6 
for mDNS.
Sep 08 14:13:52 budgie avahi-daemon[723]: Registering new address record for 
fe80::f50a:cc1e:f4f1:12cc on wlp58s0.*.
~
~
~
~
~
~
lines 1974-1996/1996 (END)
Sep 08 14:13:50 budgie NetworkManager[736]:   [1504894430.5641] manager: 
NetworkManager state is now CONNECTED_GLOBAL
Sep 08 14:13:50

[Kernel-packages] [Bug 1712831] Re: 4.12.0-11-generic - crashing in infrastructure on i386 openvswitch tests

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

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

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

Title:
  4.12.0-11-generic - crashing in infrastructure on i386 openvswitch
  tests

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

Bug description:
  Hi,
  this seems to me to be a kernel crash of some sorts.
  Somewhat in the spirit of older bugs:
  - bug 1630940
  - bug 1630578

  Xnox asked me to look into a hang on openvswitch dep8 tests.
  What I found initially was in the log just
"ERROR: Removing temporary files on testbed timed out"
  That message brought me to the two bugs above.

  But in there I read that this was the infra running dep8 crashing.
  So for a better bug report I tried to reproduce locally and that actually 
seems to work very reliable.

  To reproduce do:
  $ autopkgtest-buildvm-ubuntu-cloud -a i386 -r artful -s 10G
  $ pull-lp-source openvswitch
  $ autopkgtest --apt-upgrade --shell --no-built-binaries 
openvswitch_2.8.0~git20170809.7aa47a19d-0ubuntu1.dsc -- qemu 
~/work/autopkgtest-artful-i386.img
  # This guest currently will crash after a while of testing

  
  But with that running you can attach to the console and monitor of that guest.
  For example:
  $ sudo nc -U /tmp/autopkgtest-virt-qemu.*/ttyS0

  That gave me a crash on the hang which kind of matches the older bugs, here 
the console:
  [   54.256253] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [   54.257156] IP: add_grec+0x28/0x440
  [   54.257553] *pdpt = 1a869001 *pde =  
  [   54.257555] 
  [   54.258338] Oops:  [#1] SMP
  [   54.258638] Modules linked in: veth openvswitch nf_conntrack_ipv6 
nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat 
nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm irqbypass joydev 
input_leds serio_raw 9pnet_virtio parport_pc 9pnet parport qemu_fw_cfg 
i2c_piix4 mac_hid ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse 
virtio_blk virtio_net floppy pata_acpi
  [   54.261891] CPU: 0 PID: 0 Comm: swapper/0 Tainted: GW   
4.12.0-11-generic #12-Ubuntu
  [   54.262715] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.1-1ubuntu1~cloud0 04/01/2014
  [   54.263610] task: c7b622c0 task.stack: c7b5a000
  [   54.264039] EIP: add_grec+0x28/0x440
  [   54.264378] EFLAGS: 00010202 CPU: 0
  [   54.264711] EAX:  EBX: dd062540 ECX: 0006 EDX: dd062540
  [   54.265308] ESI: dd1e6e00 EDI: dd1e6e00 EBP: dbcc5f30 ESP: dbcc5ef0
  [   54.265793]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [   54.266297] CR0: 80050033 CR2:  CR3: 1e930d80 CR4: 06f0
  [   54.266885] Call Trace:
  [   54.267120]  
  [   54.267349]  mld_ifc_timer_expire+0xfe/0x250
  [   54.267754]  ? mld_dad_timer_expire+0x50/0x50
  [   54.268173]  call_timer_fn+0x30/0x120
  [   54.268524]  ? mld_dad_timer_expire+0x50/0x50
  [   54.268942]  ? mld_dad_timer_expire+0x50/0x50
  [   54.269364]  run_timer_softirq+0x3c5/0x420
  [   54.269760]  ? __softirqentry_text_start+0x8/0x8
  [   54.270198]  __do_softirq+0xa9/0x245
  [   54.270539]  ? __softirqentry_text_start+0x8/0x8
  [   54.270976]  do_softirq_own_stack+0x24/0x30
  [   54.271373]  
  [   54.271611]  irq_exit+0xad/0xb0
  [   54.271913]  smp_apic_timer_interrupt+0x38/0x50
  [   54.272344]  apic_timer_interrupt+0x39/0x40
  [   54.272745] EIP: native_safe_halt+0x5/0x10
  [   54.273139] EFLAGS: 0246 CPU: 0
  [   54.273624] EAX:  EBX:  ECX: 0001 EDX: 
  [   54.274000] ESI:  EDI: c7b622c0 EBP: c7b5bf10 ESP: c7b5bf10
  [   54.274361]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [   54.274687]  default_idle+0x1c/0xf0
  [   54.274896]  arch_cpu_idle+0xe/0x10
  [   54.275286]  default_idle_call+0x1e/0x30
  [   54.275787]  do_idle+0x145/0x1c0
  [   54.276092]  cpu_startup_entry+0x65/0x70
  [   54.276441]  rest_init+0x62/0x70
  [   54.276718]  start_kernel+0x3be/0x3d7
  [   54.276974]  i386_start_kernel+0x9d/0xa1
  [   54.277260]  startup_32_smp+0x16b/0x16d
  [   54.277509] Code: 00 00 00 3e 8d 74 26 00 55 89 e5 57 56 53 89 c6 83 ec 34 
89 4d e8 65 a1 14 00 00 00 89 45 f0 31 c0 8b 42 10 f6 42 48 08 89 45 cc <8b> 00 
c7 45 ec 00 00 00 00 89 45 c8 89 f0 0f 85 b4 02 00 00 8b
  [   54.279314] EIP: add_grec+0x28/0x440 SS:ESP: 0068:dbcc5ef0
  [   54.279829] CR2: 
  [   54.280143] ---[ end trace 3164b1c0dd7745bc ]---
  [   54.280550] Kernel panic - not syncing: Fatal exception in interrupt
  [   54.281078] Kernel Offset: 0x600 from 0xc100 (relocation range: 
0xc000-0xdfbfdfff)
  [   54.281797] ---[ end Kernel panic - not syncing: Fatal exception in 
interrupt

  But since this is lovely qemu the machine isn't as dead as real HW now, so

[Kernel-packages] [Bug 1713576] Re: More migrations with constant load

Did you happen to install both the linux-image and linux-image-extra
.deb packages?

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

Title:
  More migrations with constant load

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

Bug description:
  == Comment: #0 - PUVICHAKRAVARTHY RAMACHANDRAN  - 2017-08-06 13:44:45 ==
  ---Problem Description---
  Significantly higher number of task migrations when the load is fixed but not 
balanced across cores.
   
  ---uname output---
  Linux isvbos3 4.10.0-29-generic #33~16.04.1-Ubuntu SMP Tue Jul 25 18:17:06 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  Power9 dd2.0 

  Machine Type = Power9 
   
  ---Steps to Reproduce---
   Benchmark : Multithreaded - cpu intensive. The system had 2 socket/ 32 
cores/ SMT4 mode.

  When 64 threads was run - the migrations were less over 10s interval.
  when 80 threads were run - the migrations were very high.

  Ideally, it should have been very minimal, as the over all load was constant
   
  == Comment: #3 - SRIKAR DRONAMRAJU - 2017-08-11 06:56:47 ==
  As suspected (commit :  05b40e0577 : "sched/fair: Prefer sibiling only if 
local group is under-utilized")
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=05b40e0577
  should fix the problem

  Ran ' perf stat -a -r 5 -e sched:sched_migrate_task 
/home/srikar/work/ebizzy-0.3/ebizzy -t 35 -S 100'
  to detect the problem and verify the fix

  Here is perf stat without fix.

  Performance counter stats for 'system wide' (5 runs):

   7,758  sched:sched_migrate_task
  ( +-  1.28% )

   100.015658079 seconds time elapsed
  ( +-  0.00% )

  perf stat with fix.

  Performance counter stats for 'system wide' (5 runs):

 415  sched:sched_migrate_task
  ( +- 11.74% )

   100.016021787 seconds time elapsed
  ( +-  0.00% )

  
  git describe on upstream kernel says v4.11-rc2
  # git describe 05b40e0577
  v4.11-rc2-227-g05b40e0

  == Comment: #4 - SRIKAR DRONAMRAJU - 2017-08-11 07:05:37 ==
  Attaching the patch that needs to be applied to fix this bug.
  Verified that patch fixes the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1713576/+subscriptions

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

[Kernel-packages] [Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue

I do not have anything plugged into the USB type-c port. I will try that
kernel out and report back.

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

Title:
  Not Suspending When Lid is Closed Causing Heat Issue

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I installed Ubuntu Budgie 17.04 64-bit. I installed the operating
  system and then when booted, I apt-get update and apt-get upgrade. I
  went to the coffee shop and used the system for a while. When I came
  home I left my laptop Dell XPS 9360 in its leather case and inside my
  laptop bag. I left to do some errands and came back to a really hot
  laptop and case. The system had not gone to sleep when I closed the
  lid and the computer was very hot. I have attached a copy of the log
  files.

  I then:

  sudo vi /etc/systemd/logind.conf

  Changed: HandleLidSwitchDocked=suspend

  when I close the lid now it gives me a password to login when I open the lid, 
but I am not sure if it is sleeping properly. Please assist, as I do not want 
my laptop battery damaged by this heat again.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shawn  1786 F pulseaudio
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-04 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/02/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.0
  dmi.board.name: 05JK94
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.0:bd08/02/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1715758] Re: Enable BFQ at build time

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

** Also affects: linux (Ubuntu Artful)
   Importance: Wishlist
   Status: Confirmed

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

** Tags added: artful

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

Title:
  Enable BFQ at build time

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

Bug description:
  Since 4.12 BFQ is included in upstream Linux kernel.
  I'd like to see Ubuntu's kernel built with BFQ support, even if not used by 
default.
  I'm tired to see my system freezing when copying large files from/to USB 
device or sometimes even within regular SATA drives.

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

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

[Kernel-packages] [Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue

shawn@budgie:~/Downloads$ sudo dpkg -i 
linux-image-4.13.0-041300-generic_4.13.0-041300.201709031731_amd64.deb 
[sudo] password for shawn: 
Selecting previously unselected package linux-image-4.13.0-041300-generic.
(Reading database ... 258306 files and directories currently installed.)
Preparing to unpack 
linux-image-4.13.0-041300-generic_4.13.0-041300.201709031731_amd64.deb ...
Examining /etc/kernel/preinst.d/
run-parts: executing /etc/kernel/preinst.d/intel-microcode 
4.13.0-041300-generic /boot/vmlinuz-4.13.0-041300-generic
Done.
Unpacking linux-image-4.13.0-041300-generic (4.13.0-041300.201709031731) ...
Setting up linux-image-4.13.0-041300-generic (4.13.0-041300.201709031731) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
4.13.0-041300-generic /boot/vmlinuz-4.13.0-041300-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 
4.13.0-041300-generic /boot/vmlinuz-4.13.0-041300-generic
update-initramfs: Generating /boot/initrd.img-4.13.0-041300-generic
W: Possible missing firmware /lib/firmware/i915/kbl_huc_ver02_00_1810.bin for 
module i915
W: Possible missing firmware /lib/firmware/i915/bxt_huc_ver01_07_1398.bin for 
module i915
W: Possible missing firmware /lib/firmware/i915/skl_huc_ver01_07_1398.bin for 
module i915
run-parts: executing /etc/kernel/postinst.d/pm-utils 4.13.0-041300-generic 
/boot/vmlinuz-4.13.0-041300-generic
run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 
4.13.0-041300-generic /boot/vmlinuz-4.13.0-041300-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 
4.13.0-041300-generic /boot/vmlinuz-4.13.0-041300-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 
4.13.0-041300-generic /boot/vmlinuz-4.13.0-041300-generic
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.13.0-041300-generic
Found initrd image: /boot/initrd.img-4.13.0-041300-generic
Found linux image: /boot/vmlinuz-4.10.0-33-generic
Found initrd image: /boot/initrd.img-4.10.0-33-generic
Found linux image: /boot/vmlinuz-4.10.0-19-generic
Found initrd image: /boot/initrd.img-4.10.0-19-generic
Found Windows Boot Manager on /dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for EFI firmware configuration
done
shawn@budgie:~/Downloads$ 



Will report back..

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

Title:
  Not Suspending When Lid is Closed Causing Heat Issue

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I installed Ubuntu Budgie 17.04 64-bit. I installed the operating
  system and then when booted, I apt-get update and apt-get upgrade. I
  went to the coffee shop and used the system for a while. When I came
  home I left my laptop Dell XPS 9360 in its leather case and inside my
  laptop bag. I left to do some errands and came back to a really hot
  laptop and case. The system had not gone to sleep when I closed the
  lid and the computer was very hot. I have attached a copy of the log
  files.

  I then:

  sudo vi /etc/systemd/logind.conf

  Changed: HandleLidSwitchDocked=suspend

  when I close the lid now it gives me a password to login when I open the lid, 
but I am not sure if it is sleeping properly. Please assist, as I do not want 
my laptop battery damaged by this heat again.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shawn  1786 F pulseaudio
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-04 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present

[Kernel-packages] [Bug 1715866] Re: Ralink wifi RT3290 on Ubuntu 17.04 critical driver issues

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.13 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13

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

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

** Tags added: kernel-da-key

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

Title:
  Ralink wifi RT3290 on Ubuntu 17.04 critical driver issues

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When ubuntu 17.04 is installed wifi Ralink RT3290 is recognized
  immediately but it doesn't work at all even it "connects" and says
  connection established with good quality - it's poor and almost zero
  quality with frequent disconnections. All this makes equipments with
  ralink wifi cards unable to work under linux distros and there're
  thousands of them.

  Recently found modded drivers for RT3290 which installed without any
  issues and wifi worked after that like a charm, but after system
  reinstall I can't install theese modded drivers anymore and there're
  some issues during installation and loading kernel modules (maybe it's
  something with latest linux kernels)...

  Anyway it's pointess to use RT2800pci driver for physical RT3290 chip
  cause it's a wrong piece of code and Ubuntu maintainers should fix
  this.

  BTW Bluetooth RT3290 doesn't work at all but making RT3290 wifi works is 
seriously critical.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pawel  2113 F pulseaudio
   /dev/snd/controlC0:  pawel  2113 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-08 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. X750JB
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=cb519ab1-5f5d-444e-9f92-b628ae93156e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/14/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X750JB.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X750JB
  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.:bvrX750JB.208:bd08/14/2013:svnASUSTeKCOMPUTERINC.:pnX750JB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX750JB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X750JB
  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/1715866/+subscriptions

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

[Kernel-packages] [Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue

2017-09-08 Thread Kai-Heng Feng

Do you have anything plugged in the USB type-c port?

Also, please try latest mainline kernel [1].

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13/linux-
image-4.13.0-041300-generic_4.13.0-041300.201709031731_amd64.deb

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

Title:
  Not Suspending When Lid is Closed Causing Heat Issue

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I installed Ubuntu Budgie 17.04 64-bit. I installed the operating
  system and then when booted, I apt-get update and apt-get upgrade. I
  went to the coffee shop and used the system for a while. When I came
  home I left my laptop Dell XPS 9360 in its leather case and inside my
  laptop bag. I left to do some errands and came back to a really hot
  laptop and case. The system had not gone to sleep when I closed the
  lid and the computer was very hot. I have attached a copy of the log
  files.

  I then:

  sudo vi /etc/systemd/logind.conf

  Changed: HandleLidSwitchDocked=suspend

  when I close the lid now it gives me a password to login when I open the lid, 
but I am not sure if it is sleeping properly. Please assist, as I do not want 
my laptop battery damaged by this heat again.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shawn  1786 F pulseaudio
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-04 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/02/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.0
  dmi.board.name: 05JK94
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.0:bd08/02/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1715552] Re: VMWare does not start

2017-09-08 Thread Wolf Rogner

I agree with Seth:

/usr/lib/vmware/bin/vmware-modconfig: Relink `/lib/x86_64-linux-
gnu/libbsd.so.0' with `/lib/x86_64-linux-gnu/librt.so.1' for IFUNC
symbol `clock_gettime'

seems to be an issue related to the build process of librt and libbsd

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

Title:
  VMWare does not start

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Under Ubuntu 17.10 beta VMWare 12.5.7 cannot be started:

  /usr/lib/vmware/bin/vmware-modconfig: Relink `/lib/x86_64-linux-
  gnu/libbsd.so.0' with `/lib/x86_64-linux-gnu/librt.so.1' for IFUNC
  symbol `clock_gettime'

  Works under Ubuntu 17.04

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.12.0-13-generic 4.12.0-13.14
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wolf   9336 F pulseaudio
   /dev/snd/controlC0:  wolf   9336 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  7 07:53:43 2017
  HibernationDevice: RESUME=UUID=88d69bc7-ac96-42c6-bf6d-5c912964a63b
  InstallationDate: Installed on 2017-09-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-13-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.12.0-13-generic N/A
   linux-backports-modules-4.12.0-13-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B33.1706181928
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue

journalctl and shift g, as well.


Sep 08 13:10:14 budgie avahi-daemon[715]: New relevant interface wlp58s0.IPv6 
for mDNS.
Sep 08 13:10:14 budgie avahi-daemon[715]: Registering new address record for 
fe80::f50a:cc1e:f4f1:12cc on wlp58s0.*.
Sep 08 13:10:22 budgie systemd-logind[719]: Lid opened.
Sep 08 13:10:22 budgie budgie-plank.desktop[1747]: 
[0908/131022.671860:ERROR:ticl-message-validator.cc(212)] registration_digest
Sep 08 13:10:22 budgie budgie-plank.desktop[1747]: 
[0908/131022.671892:ERROR:ticl-message-validator.cc(319)] field registration_
Sep 08 13:10:22 budgie budgie-plank.desktop[1747]: 
[0908/131022.671908:ERROR:ticl-message-validator.cc(361)] field header failed
Sep 08 13:10:22 budgie budgie-plank.desktop[1747]: 
[0908/131022.671922:ERROR:protocol-handler.cc(145)] Received invalid message:
Sep 08 13:10:23 budgie systemd[1]: Reloading.
Sep 08 13:10:25 budgie gnome-screensaver-dialog[19008]: gkr-pam: unlocked login 
keyring
Sep 08 13:10:29 budgie dbus-daemon[1327]: Activating service 
name='com.gexperts.Terminix'
Sep 08 13:10:29 budgie dbus-daemon[1327]: Successfully activated service 
'com.gexperts.Terminix'
Sep 08 13:10:29 budgie terminix[21453]: ../../../../gobject/gsignal.c:2523: 
signal 'notification-received' is invalid for instan
Sep 08 13:10:31 budgie kernel: pcieport :02:00.0: Refused to change power 
state, currently in D3
Sep 08 13:10:33 budgie systemd[1]: Reloading.
Sep 08 13:10:34 budgie terminix[21453]: Allocating size to GtkScrollbar 
0x55ad36983880 without calling gtk_widget_get_preferred_
Sep 08 13:10:34 budgie terminix[21453]: Allocating size to GtkScrollbar 
0x55ad36983880 without calling gtk_widget_get_preferred_
Sep 08 13:11:28 budgie terminix[21453]: Allocating size to GtkScrollbar 
0x55ad36983880 without calling gtk_widget_get_preferred_
Sep 08 13:11:29 budgie terminix[21453]: Allocating size to GtkScrollbar 
0x55ad36983880 without calling gtk_widget_get_preferred_
Sep 08 13:11:34 budgie terminix[21453]: Allocating size to GtkScrollbar 
0x55ad36983880 without calling gtk_widget_get_preferred_
Sep 08 13:11:35 budgie terminix[21453]: Allocating size to GtkScrollbar 
0x55ad36983880 without calling gtk_widget_get_preferred_
Sep 08 13:11:35 budgie terminix[21453]: Allocating size to GtkScrollbar 
0x55ad36983880 without calling gtk_widget_get_preferred_
Sep 08 13:11:35 budgie terminix[21453]: Allocating size to GtkScrollbar 
0x55ad36983880 without calling gtk_widget_get_preferred_
Sep 08 13:11:35 budgie terminix[21453]: Allocating size to GtkScrollbar 
0x55ad36983880 without calling gtk_widget_get_preferred_
Sep 08 13:11:35 budgie terminix[21453]: Allocating size to GtkScrollbar 
0x55ad36983880 without calling gtk_widget_get_preferred_
lines 28081-28110/28110 (END)
Sep 08 13:10:13 budgie gsd-sharing[1473]: Failed to StopUnit service: 
GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit vino-serve
Sep 08 13:10:13 budgie whoopsie[1020]: [13:10:13] Not a paid data plan: 
/org/freedesktop/NetworkManager/ActiveConnection/126
Sep 08 13:10:13 budgie whoopsie[1020]: [13:10:13] Found usable connection: 
/org/freedesktop/NetworkManager/ActiveConnection/126
Sep 08 13:10:13 budgie whoopsie[1020]: [13:10:13] online
Sep 08 13:10:13 budgie systemd-resolved[948]: Switching to DNS server 
130.85.1.23 for interface wlp58s0.
Sep 08 13:10:14 budgie avahi-daemon[715]: Joining mDNS multicast group on 
interface wlp58s0.IPv6 with address fe80::f50a:cc1e:f4f1:12c
Sep 08 13:10:14 budgie avahi-daemon[715]: New relevant interface wlp58s0.IPv6 
for mDNS.
Sep 08 13:10:14 budgie avahi-daemon[715]: Registering new address record for 
fe80::f50a:cc1e:f4f1:12cc on wlp58s0.*.
Sep 08 13:10:22 budgie systemd-logind[719]: Lid opened.
Sep 08 13:10:22 budgie budgie-plank.desktop[1747]: 
[0908/131022.671860:ERROR:ticl-message-validator.cc(212)] registration_digest 
must 
Sep 08 13:10:22 budgie budgie-plank.desktop[1747]: 
[0908/131022.671892:ERROR:ticl-message-validator.cc(319)] field 
registration_summar
Sep 08 13:10:22 budgie budgie-plank.desktop[1747]: 
[0908/131022.671908:ERROR:ticl-message-validator.cc(361)] field header failed 
valid
Sep 08 13:10:22 budgie budgie-plank.desktop[1747]: 
[0908/131022.671922:ERROR:protocol-handler.cc(145)] Received invalid message: { 
hea
Sep 08 13:10:23 budgie systemd[1]: Reloading.
Sep 08 13:10:25 budgie gnome-screensaver-dialog[19008]: gkr-pam: unlocked login 
keyring
Sep 08 13:10:29 budgie dbus-daemon[1327]: Activating service 
name='com.gexperts.Terminix'
Sep 08 13:10:29 budgie dbus-daemon[1327]: Successfully activated service 
'com.gexperts.Terminix'
Sep 08 13:10:29 budgie terminix[21453]: ../../../../gobject/gsignal.c:2523: 
signal 'notification-received' is invalid for instance '0x
Sep 08 13:10:31 budgie kernel: pcieport :02:00.0: Refused to change power 
state, currently in D3
Sep 08 13:10:33 budgie systemd[1]: Reloading.
Sep 08 13:10:34 budgie terminix[21453]: Allocating size to GtkScrollbar 
0x55ad36983880 without calling gtk_widget_get_preferred_width/
Sep

[Kernel-packages] [Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue

shawn@budgie:~$ lspci
00:00.0 Host bridge: Intel Corporation Device 5904 (rev 02)
00:02.0 VGA compatible controller: Intel Corporation Device 5916 (rev 02)
00:04.0 Signal processing controller: Intel Corporation Skylake Processor 
Thermal Subsystem (rev 02)
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Thermal subsystem (rev 21)
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial 
IO I2C Controller #0 (rev 21)
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial 
IO I2C Controller #1 (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI 
#1 (rev 21)
00:1c.0 PCI bridge: Intel Corporation Device 9d10 (rev f1)
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 
(rev f1)
00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 
(rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 
(rev f1)
00:1f.0 ISA bridge: Intel Corporation Device 9d58 (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
01:00.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine 
Ridge 2C 2015] (rev ff)
02:00.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine 
Ridge 2C 2015] (rev ff)
02:01.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine 
Ridge 2C 2015] (rev ff)
02:02.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine 
Ridge 2C 2015] (rev ff)
03:00.0 System peripheral: Intel Corporation DSL6340 Thunderbolt 3 NHI [Alpine 
Ridge 2C 2015] (rev ff)
39:00.0 USB controller: Intel Corporation DSL6340 USB 3.1 Controller [Alpine 
Ridge] (rev ff)
3a:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network 
Adapter (rev 32)
3b:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI 
Express Card Reader (rev 01)
3c:00.0 Non-Volatile memory controller: Device 1c5c:1283
shawn@budgie:~$ ^C
shawn@budgie:~$

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

Title:
  Not Suspending When Lid is Closed Causing Heat Issue

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I installed Ubuntu Budgie 17.04 64-bit. I installed the operating
  system and then when booted, I apt-get update and apt-get upgrade. I
  went to the coffee shop and used the system for a while. When I came
  home I left my laptop Dell XPS 9360 in its leather case and inside my
  laptop bag. I left to do some errands and came back to a really hot
  laptop and case. The system had not gone to sleep when I closed the
  lid and the computer was very hot. I have attached a copy of the log
  files.

  I then:

  sudo vi /etc/systemd/logind.conf

  Changed: HandleLidSwitchDocked=suspend

  when I close the lid now it gives me a password to login when I open the lid, 
but I am not sure if it is sleeping properly. Please assist, as I do not want 
my laptop battery damaged by this heat again.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shawn  1786 F pulseaudio
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-04 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/02/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.0

[Kernel-packages] [Bug 1696154] Comment bridged from LTC Bugzilla

2017-09-08 Thread bugproxy

--- Comment From l...@us.ibm.com 2017-09-08 13:05 EDT---
(In reply to comment #27)
> (In reply to comment #25)
> > Does IBM have any feedback for us regarding the test kernel Andy provided?
> >
>
> We're planning to test this month.  We'll give feedback as soon as the test
> is completed.  The tentative target will be Sept. 29 or sooner.
>
>
> > Can you please clarify if this means you are expecting the db entry to be
> > delivered as an x509 certificate issued by the CA key listed in KEK, or if
> > it should be delivered according to the format defined in the UEFI spec for
> > authenticated variable updates?
>
> Our team needs to have some discussions before finalizing the expected
> format.  We'll get back to you soon.  Thanks!

Our team confirms that it should be delivered according to ESL format.

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

Title:
  [17.10 FEAT] Sign POWER host/NV kernels

Status in Launchpad itself:
  Fix Committed
Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-signed package in Ubuntu:
  In Progress

Bug description:
  Feature Description:

  Sign POWER host and NV kernels with sign-file in anticipation of POWER
  secure boot.  Provide the  associated certificate.  Ideally it would
  be possible to reuse the UEFI shim private key and certificate used to
  sign and verify x86_64 kernels.  More details to follow.  Guest
  kernels will be addressed in a future separate feature request.

  
  Business Case: 

  As a system administrator I want to verify the integrity of my kernels
  so that I can prevent malicious kernels from being executed.

  Use Case:

  Signed POWER kernels will be validated by OPAL as OpenPOWER systems
  boot when keys are properly installed and the system is booted in
  secure mode.

  
  Test Case:

  Sign and install a POWER kernel on an OpenPOWER machine with a
  firmware level that supports secure boot.  Install a PK, distro KEK
  certificat, and distro DB certificate.  Boot the system and verify
  that it will boot the kernel.  Negative tests:  Separately remove the
  signature, install an usigned kernel, and modify the kernel image and
  test that the kernel will not boot.

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

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

[Kernel-packages] [Bug 1715655] Re: linux-aws: 4.4.0-1034.43 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Committed

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

Title:
  linux-aws: 4.4.0-1034.43 -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 promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1715651
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1715651] Re: linux: 4.4.0-95.118 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Committed

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

Title:
  linux: 4.4.0-95.118 -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:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  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: 1715652
  derivatives: 1715653,1715654,1715655,1715656,1715659
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Thursday, 07. September 2017 16:30 UTC

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1712867] Re: [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

** Also affects: kexec-tools (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: kexec-tools (Ubuntu)
   Status: New => Confirmed

** Changed in: kexec-tools (Ubuntu Xenial)
   Status: New => Confirmed

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

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

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

Title:
  [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

Status in kexec-tools package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  In Progress
Status in makedumpfile package in Ubuntu:
  Confirmed
Status in kexec-tools source package in Xenial:
  Confirmed
Status in linux-azure source package in Xenial:
  In Progress
Status in makedumpfile source package in Xenial:
  Confirmed

Bug description:
  Because the linux-azure kernel is based on 4.11, kexec on 16.04 gives the 
following error:
  kdump-tools[1436]: ELF core (kcore) parse failed

  Perhaps the artful kexec-tools should be backported?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1712867/+subscriptions

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

[Kernel-packages] [Bug 1715655] Re: linux-aws: 4.4.0-1034.43 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

Title:
  linux-aws: 4.4.0-1034.43 -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 promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1715651
  phase: Uploaded

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

-- 
Mailing list: https://launchpad.net/~kernel-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] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

2017-09-08 Thread xb5i7o

Hi guys,

Im getting the same issues, brand new build.

Ryzen 1800x
Asrock X370 Taichi
BIOS: 3.10 (latest)
I tried disabling cool n quiet and c-state

However there is another option under advanced - for GLOBAL C-States
that i just disabled today and i am waiting to see what will happen.

On BIOS v3.00 PC would freeze after 6 hours of idling or not touching anything. 
Come back to see my keyboard and mouse and everything was frozen.
With BIOS v.3.10  now i get random reboots atleast once a day.

Im running Ubuntu 16.04.3 Kernel 4.4.0-93

Anyone know to direct me where the SoC voltage would be in BIOS? is it the VDD 
SoC?
Anyone know how to update my kernel to 4.10 if it tells me i have the latest?

-- 
You 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:
  Unknown
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

[Kernel-packages] [Bug 1715651] Re: linux: 4.4.0-95.118 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

Title:
  linux: 4.4.0-95.118 -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:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  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: 1715652
  derivatives: 1715653,1715654,1715655,1715656,1715659
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Thursday, 07. September 2017 16:30 UTC

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1696102] Re: xfs/073 test fails with Metadata corruption detected on xfs file system (xfsprogs)

Hello bugproxy, or anyone else affected,

Accepted xfsprogs into zesty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/xfsprogs/4.3.0+nmu1ubuntu4.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-zesty to verification-done-zesty. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-zesty. In either case, details of your testing
will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: xfsprogs (Ubuntu Zesty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-zesty

** Changed in: xfsprogs (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  xfs/073 test fails with Metadata corruption detected on xfs file
  system (xfsprogs)

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in xfsprogs package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in xfsprogs source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Invalid
Status in xfsprogs source package in Zesty:
  Fix Committed

Bug description:
  Impact
  ==
  When making multiple copies of a V5 filesystem with xfs_copy those copies 
will be corrupt due to incorrect UUIDs.

  Test Case
  =
  See the detailed steps to create the test environment in comment #20.

  Regression Potential
  
  From the patch "Most of this patch is changing comments and re-ordering tests 
to match; the functional change is to simply use the *sb rather than the 
*ag_hdr to identify the proper metadata UUID." So this seems pretty 
straightforward and given that copy process is currently broken, because the 
copies are corrupt, this will be an improvement.

  Original Description
  

  Problem Description
  
  xfs/073 test fails with Metadata corruption detected on xfs file system. Test 
fails with _check_xfs_filesystem: filesystem on /mnt/test/84004.image2 is 
inconsistent.

  # diff -u tests/xfs/073.out /root/xfstests-dev/results//xfs/073.out.bad
  --- tests/xfs/073.out 2017-03-23 12:13:05.288877197 +0530
  +++ /root/xfstests-dev/results//xfs/073.out.bad   2017-03-27 
11:11:43.023059702 +0530
  @@ -59,8 +59,7 @@
   comparing new image geometry to old
   unmounting and removing new image
   checking new image
  -mounting new image on loopback
  -comparing new image files to old
  -comparing new image directories to old
  -comparing new image geometry to old
  -unmounting and removing new image
  +_check_xfs_filesystem: filesystem on /mnt/test/15413.image2 is inconsistent 
(c)
  +(see /root/xfstests-dev/results//xfs/073.full for details)
  +_check_xfs_filesystem: filesystem on /mnt/test/15413.image2 is inconsistent 
(r)
  +(see /root/xfstests-dev/results//xfs/073.full for details)

  Metadata corruption detected at xfs_agf block 0x1/0x200

  # uname -a
  Linux ltc-tuleta12 4.10.0-21-generic #23~16.04.1-Ubuntu SMP Tue May 2 
12:54:57 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Steps to reproduce:
  
  1. Create a loop device with xfs filesystem
  2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd 
xfstests-dev
  3. make
  4. Create a local.conf for running with created loop device
  5.. Run xfstests-dev test  : ./check tests/xfs/073

  Full log is attached.

  == Comment: #2 - Harish Sriram  - 2017-05-31 01:22:11 ==
  (In reply to comment #1)
  > Hi Harish,
  > Can you share the steps used in creating the loop device with xfs filesystem
  > ?
  >
  > Thank you.

  Create loop device:
  # mkdir /mnt/loop-device /mnt/test /mnt/scratch

  # for i in $(seq 0 1); do fallocate -o 0 -l 5GiB 
/mnt/loop-device/file-$i.img; done
  # for i in $(seq 0 1); do losetup /dev/loop$i /mnt/loop-device/file-$i.img; 
done

  Create File system:
  # for i in $(seq 0 1); do mkfs.ext4 -F /dev/loop$i; done

  # cat local.config
  export TEST_DEV=/dev/loop0
  export TEST_DIR=/mnt/test
  export SCRATCH_DEV=/dev/loop1
  export SCRATCH_MNT=/mnt/scratch

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1696102] Please test proposed package

Hello bugproxy, or anyone else affected,

Accepted xfsprogs into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/xfsprogs/4.3.0+nmu1ubuntu1.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  xfs/073 test fails with Metadata corruption detected on xfs file
  system (xfsprogs)

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in xfsprogs package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in xfsprogs source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Invalid
Status in xfsprogs source package in Zesty:
  Fix Committed

Bug description:
  Impact
  ==
  When making multiple copies of a V5 filesystem with xfs_copy those copies 
will be corrupt due to incorrect UUIDs.

  Test Case
  =
  See the detailed steps to create the test environment in comment #20.

  Regression Potential
  
  From the patch "Most of this patch is changing comments and re-ordering tests 
to match; the functional change is to simply use the *sb rather than the 
*ag_hdr to identify the proper metadata UUID." So this seems pretty 
straightforward and given that copy process is currently broken, because the 
copies are corrupt, this will be an improvement.

  Original Description
  

  Problem Description
  
  xfs/073 test fails with Metadata corruption detected on xfs file system. Test 
fails with _check_xfs_filesystem: filesystem on /mnt/test/84004.image2 is 
inconsistent.

  # diff -u tests/xfs/073.out /root/xfstests-dev/results//xfs/073.out.bad
  --- tests/xfs/073.out 2017-03-23 12:13:05.288877197 +0530
  +++ /root/xfstests-dev/results//xfs/073.out.bad   2017-03-27 
11:11:43.023059702 +0530
  @@ -59,8 +59,7 @@
   comparing new image geometry to old
   unmounting and removing new image
   checking new image
  -mounting new image on loopback
  -comparing new image files to old
  -comparing new image directories to old
  -comparing new image geometry to old
  -unmounting and removing new image
  +_check_xfs_filesystem: filesystem on /mnt/test/15413.image2 is inconsistent 
(c)
  +(see /root/xfstests-dev/results//xfs/073.full for details)
  +_check_xfs_filesystem: filesystem on /mnt/test/15413.image2 is inconsistent 
(r)
  +(see /root/xfstests-dev/results//xfs/073.full for details)

  Metadata corruption detected at xfs_agf block 0x1/0x200

  # uname -a
  Linux ltc-tuleta12 4.10.0-21-generic #23~16.04.1-Ubuntu SMP Tue May 2 
12:54:57 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Steps to reproduce:
  
  1. Create a loop device with xfs filesystem
  2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd 
xfstests-dev
  3. make
  4. Create a local.conf for running with created loop device
  5.. Run xfstests-dev test  : ./check tests/xfs/073

  Full log is attached.

  == Comment: #2 - Harish Sriram  - 2017-05-31 01:22:11 ==
  (In reply to comment #1)
  > Hi Harish,
  > Can you share the steps used in creating the loop device with xfs filesystem
  > ?
  >
  > Thank you.

  Create loop device:
  # mkdir /mnt/loop-device /mnt/test /mnt/scratch

  # for i in $(seq 0 1); do fallocate -o 0 -l 5GiB 
/mnt/loop-device/file-$i.img; done
  # for i in $(seq 0 1); do losetup /dev/loop$i /mnt/loop-device/file-$i.img; 
done

  Create File system:
  # for i in $(seq 0 1); do mkfs.ext4 -F /dev/loop$i; done

  # cat local.config
  export TEST_DEV=/dev/loop0
  export TEST_DIR=/mnt/test
  export SCRATCH_DEV=/dev/loop1
  export SCRATCH_MNT=/mnt/scratch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696102/+subscriptions

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

[Kernel-packages] [Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue

2017-09-08 Thread Kai-Heng Feng

Please attach `lspci` after failed suspend. I guess :39:00.0 is a TB
controller.

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

Title:
  Not Suspending When Lid is Closed Causing Heat Issue

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I installed Ubuntu Budgie 17.04 64-bit. I installed the operating
  system and then when booted, I apt-get update and apt-get upgrade. I
  went to the coffee shop and used the system for a while. When I came
  home I left my laptop Dell XPS 9360 in its leather case and inside my
  laptop bag. I left to do some errands and came back to a really hot
  laptop and case. The system had not gone to sleep when I closed the
  lid and the computer was very hot. I have attached a copy of the log
  files.

  I then:

  sudo vi /etc/systemd/logind.conf

  Changed: HandleLidSwitchDocked=suspend

  when I close the lid now it gives me a password to login when I open the lid, 
but I am not sure if it is sleeping properly. Please assist, as I do not want 
my laptop battery damaged by this heat again.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shawn  1786 F pulseaudio
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-04 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/02/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.0
  dmi.board.name: 05JK94
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.0:bd08/02/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue

Sep  8 11:37:12 budgie NetworkManager[746]:   [1504885032.6272] dhcp4 
(wlp58s0):   domain name 'umbc.edu'
Sep  8 11:37:12 budgie NetworkManager[746]:   [1504885032.6273] dhcp4 
(wlp58s0):   wins '130.85.11.19'
Sep  8 11:37:12 budgie NetworkManager[746]:   [1504885032.6273] dhcp4 
(wlp58s0):   wins '130.85.11.30'
Sep  8 11:37:12 budgie avahi-daemon[715]: Joining mDNS multicast group on 
interface wlp58s0.IPv4 with address 10.200.154.116.
Sep  8 11:37:12 budgie NetworkManager[746]:   [1504885032.6273] dhcp4 
(wlp58s0):   wins '130.85.11.7'
Sep  8 11:37:12 budgie avahi-daemon[715]: New relevant interface wlp58s0.IPv4 
for mDNS.
Sep  8 11:37:12 budgie NetworkManager[746]:   [1504885032.6273] dhcp4 
(wlp58s0): state changed unknown -> bound
Sep  8 11:37:12 budgie avahi-daemon[715]: Registering new address record for 
10.200.154.116 on wlp58s0.IPv4.
Sep  8 11:37:12 budgie NetworkManager[746]:   [1504885032.6344] device 
(wlp58s0): state change: ip-config -> ip-check (reason 'none') [70 80 0]
Sep  8 11:37:12 budgie NetworkManager[746]:   [1504885032.6354] device 
(wlp58s0): state change: ip-check -> secondaries (reason 'none') [80 90 0]
Sep  8 11:37:12 budgie NetworkManager[746]:   [1504885032.6389] device 
(wlp58s0): state change: secondaries -> activated (reason 'none') [90 100 0]
Sep  8 11:37:12 budgie NetworkManager[746]:   [1504885032.6427] manager: 
NetworkManager state is now CONNECTED_LOCAL
Sep  8 11:37:12 budgie dhclient[13776]: bound to 10.200.154.116 -- renewal in 
1755 seconds.
Sep  8 11:37:12 budgie kernel: [ 4546.263489] wlp58s0: Limiting TX power to 17 
(17 - 0) dBm as advertised by 64:a0:e7:ff:45:cf
Sep  8 11:37:12 budgie nm-dispatcher: req:295 'connectivity-change': new 
request (2 scripts)
Sep  8 11:37:12 budgie nm-dispatcher: req:295 'connectivity-change': start 
running ordered scripts...
Sep  8 11:37:12 budgie NetworkManager[746]:   [1504885032.6510] manager: 
NetworkManager state is now CONNECTED_GLOBAL
Sep  8 11:37:12 budgie NetworkManager[746]:   [1504885032.6513] policy: 
set 'UMBC Visitor' (wlp58s0) as default for IPv4 routing and DNS
Sep  8 11:37:12 budgie NetworkManager[746]:   [1504885032.6520] device 
(wlp58s0): Activation: successful, device activated.
Sep  8 11:37:12 budgie nm-dispatcher: req:296 'up' [wlp58s0]: new request (2 
scripts)
Sep  8 11:37:12 budgie nm-dispatcher: req:296 'up' [wlp58s0]: start running 
ordered scripts...
Sep  8 11:37:12 budgie gsd-sharing[1473]: Failed to StopUnit service: 
GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not loaded.
Sep  8 11:37:12 budgie whoopsie[1020]: [11:37:12] The default IPv4 route is: 
/org/freedesktop/NetworkManager/ActiveConnection/113
Sep  8 11:37:12 budgie gsd-sharing[1473]: Failed to StopUnit service: 
GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit vino-server.service not 
loaded.
Sep  8 11:37:12 budgie whoopsie[1020]: [11:37:12] Not a paid data plan: 
/org/freedesktop/NetworkManager/ActiveConnection/113
Sep  8 11:37:12 budgie whoopsie[1020]: [11:37:12] Found usable connection: 
/org/freedesktop/NetworkManager/ActiveConnection/113
Sep  8 11:37:12 budgie whoopsie[1020]: [11:37:12] online
Sep  8 11:37:12 budgie systemd-resolved[948]: Switching to DNS server 
130.85.1.23 for interface wlp58s0.
Sep  8 11:37:13 budgie avahi-daemon[715]: Joining mDNS multicast group on 
interface wlp58s0.IPv6 with address fe80::f50a:cc1e:f4f1:12cc.
Sep  8 11:37:13 budgie avahi-daemon[715]: New relevant interface wlp58s0.IPv6 
for mDNS.
Sep  8 11:37:13 budgie avahi-daemon[715]: Registering new address record for 
fe80::f50a:cc1e:f4f1:12cc on wlp58s0.*.
Sep  8 11:37:22 budgie systemd[1]: Reloading.
Sep  8 11:37:32 budgie NetworkManager[746]:   [1504885052.2047] manager: 
sleep requested (sleeping: no  enabled: yes)
Sep  8 11:37:32 budgie NetworkManager[746]:   [1504885052.2048] manager: 
sleeping...
Sep  8 11:37:32 budgie NetworkManager[746]:   [1504885052.2050] manager: 
NetworkManager state is now ASLEEP
Sep  8 11:37:32 budgie NetworkManager[746]:   [1504885052.2063] device 
(wlp58s0): state change: activated -> deactivating (reason 'sleeping') [100 110 
37]
Sep  8 11:37:32 budgie whoopsie[1020]: [11:37:32] offline
Sep  8 11:37:32 budgie nm-dispatcher: req:297 'connectivity-change': new 
request (2 scripts)
Sep  8 11:37:32 budgie NetworkManager[746]:   [1504885052.2187] device 
(wlp58s0): state change: deactivating -> disconnected (reason 'sleeping') [110 
30 37]
Sep  8 11:37:32 budgie avahi-daemon[715]: Withdrawing address record for 
fe80::f50a:cc1e:f4f1:12cc on wlp58s0.
Sep  8 11:37:32 budgie avahi-daemon[715]: Leaving mDNS multicast group on 
interface wlp58s0.IPv6 with address fe80::f50a:cc1e:f4f1:12cc.
Sep  8 11:37:32 budgie avahi-daemon[715]: Interface wlp58s0.IPv6 no longer 
relevant for mDNS.
Sep  8 11:37:32 budgie NetworkManager[746]:   [1504885052.2546] dhcp4 
(wlp58s0): canceled DHCP transaction, DHCP client pid 13776
Sep  8 11:37:32 budgie NetworkManager[746]:   [1504885052.2547] dhcp4 
(wlp58s0): state

[Kernel-packages] [Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue

This is still an issue. Not suspending. Please assist.

** Attachment added: "Screenshot from 2017-09-08 12-10-01.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+attachment/4946602/+files/Screenshot%20from%202017-09-08%2012-10-01.png

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

Title:
  Not Suspending When Lid is Closed Causing Heat Issue

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I installed Ubuntu Budgie 17.04 64-bit. I installed the operating
  system and then when booted, I apt-get update and apt-get upgrade. I
  went to the coffee shop and used the system for a while. When I came
  home I left my laptop Dell XPS 9360 in its leather case and inside my
  laptop bag. I left to do some errands and came back to a really hot
  laptop and case. The system had not gone to sleep when I closed the
  lid and the computer was very hot. I have attached a copy of the log
  files.

  I then:

  sudo vi /etc/systemd/logind.conf

  Changed: HandleLidSwitchDocked=suspend

  when I close the lid now it gives me a password to login when I open the lid, 
but I am not sure if it is sleeping properly. Please assist, as I do not want 
my laptop battery damaged by this heat again.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shawn  1786 F pulseaudio
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-04 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/02/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.0
  dmi.board.name: 05JK94
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.0:bd08/02/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1696102] Re: xfs/073 test fails with Metadata corruption detected on xfs file system (xfsprogs)

2017-09-08 Thread Brian Murray

** Description changed:

+ Impact
+ ==
+ When making multiple copies of a V5 filesystem with xfs_copy those copies 
will be corrupt due to incorrect UUIDs.
+ 
+ Test Case
+ =
+ See the detailed steps to create the test environment in comment #20.
+ 
+ Regression Potential
+ 
+ From the patch "Most of this patch is changing comments and re-ordering tests 
to match; the functional change is to simply use the *sb rather than the 
*ag_hdr to identify the proper metadata UUID." So this seems pretty 
straightforward and given that copy process is currently broken, because the 
copies are corrupt, this will be an improvement.
+ 
+ Original Description
+ 
+ 
  Problem Description
  
  xfs/073 test fails with Metadata corruption detected on xfs file system. Test 
fails with _check_xfs_filesystem: filesystem on /mnt/test/84004.image2 is 
inconsistent.
  
  # diff -u tests/xfs/073.out /root/xfstests-dev/results//xfs/073.out.bad
  --- tests/xfs/073.out 2017-03-23 12:13:05.288877197 +0530
  +++ /root/xfstests-dev/results//xfs/073.out.bad   2017-03-27 
11:11:43.023059702 +0530
  @@ -59,8 +59,7 @@
-  comparing new image geometry to old
-  unmounting and removing new image
-  checking new image
+  comparing new image geometry to old
+  unmounting and removing new image
+  checking new image
  -mounting new image on loopback
  -comparing new image files to old
  -comparing new image directories to old
  -comparing new image geometry to old
  -unmounting and removing new image
  +_check_xfs_filesystem: filesystem on /mnt/test/15413.image2 is inconsistent 
(c)
  +(see /root/xfstests-dev/results//xfs/073.full for details)
  +_check_xfs_filesystem: filesystem on /mnt/test/15413.image2 is inconsistent 
(r)
  +(see /root/xfstests-dev/results//xfs/073.full for details)
  
  Metadata corruption detected at xfs_agf block 0x1/0x200
  
  # uname -a
  Linux ltc-tuleta12 4.10.0-21-generic #23~16.04.1-Ubuntu SMP Tue May 2 
12:54:57 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
  
  Steps to reproduce:
  
  1. Create a loop device with xfs filesystem
  2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd 
xfstests-dev
  3. make
  4. Create a local.conf for running with created loop device
  5.. Run xfstests-dev test  : ./check tests/xfs/073
  
  Full log is attached.
  
  == Comment: #2 - Harish Sriram  - 2017-05-31 01:22:11 ==
  (In reply to comment #1)
  > Hi Harish,
  > Can you share the steps used in creating the loop device with xfs filesystem
  > ?
- > 
+ >
  > Thank you.
  
  Create loop device:
  # mkdir /mnt/loop-device /mnt/test /mnt/scratch
  
  # for i in $(seq 0 1); do fallocate -o 0 -l 5GiB 
/mnt/loop-device/file-$i.img; done
  # for i in $(seq 0 1); do losetup /dev/loop$i /mnt/loop-device/file-$i.img; 
done
  
  Create File system:
  # for i in $(seq 0 1); do mkfs.ext4 -F /dev/loop$i; done
  
  # cat local.config
  export TEST_DEV=/dev/loop0
  export TEST_DIR=/mnt/test
  export SCRATCH_DEV=/dev/loop1
  export SCRATCH_MNT=/mnt/scratch

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

Title:
  xfs/073 test fails with Metadata corruption detected on xfs file
  system (xfsprogs)

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in xfsprogs package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in xfsprogs source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  Invalid
Status in xfsprogs source package in Zesty:
  In Progress

Bug description:
  Impact
  ==
  When making multiple copies of a V5 filesystem with xfs_copy those copies 
will be corrupt due to incorrect UUIDs.

  Test Case
  =
  See the detailed steps to create the test environment in comment #20.

  Regression Potential
  
  From the patch "Most of this patch is changing comments and re-ordering tests 
to match; the functional change is to simply use the *sb rather than the 
*ag_hdr to identify the proper metadata UUID." So this seems pretty 
straightforward and given that copy process is currently broken, because the 
copies are corrupt, this will be an improvement.

  Original Description
  

  Problem Description
  
  xfs/073 test fails with Metadata corruption detected on xfs file system. Test 
fails with _check_xfs_filesystem: filesystem on /mnt/test/84004.image2 is 
inconsistent.

  # diff -u tests/xfs/073.out /root/xfstests-dev/results//xfs/073.out.bad
  --- tests/xfs/073.out 2017-03-23 12:13:05.288877197 +0530
  +++ /root/xfstests-dev/results//xfs/073.out.bad   2017-03-27 
11:11:43.023059702 +0530
  @@ -59,8 +59,7 @@
   comparing new image geometry to old
   unmounting

[Kernel-packages] [Bug 1715441] Re: linux-lts-trusty: 3.13.0-131.180~precise1 -proposed tracker

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

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

Title:
  linux-lts-trusty: 3.13.0-131.180~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  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: 1715439
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1714687] Re: linux: 4.12.0-13.14 -proposed tracker

** Changed in: kernel-development-workflow/automated-testing
   Status: Incomplete => Fix Released

** Changed in: kernel-development-workflow/regression-testing
   Status: Confirmed => Fix Released

** Changed in: kernel-development-workflow/promote-to-release
   Status: New => Confirmed

** Tags removed: block-proposed-artful

** Tags removed: block-proposed

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

Title:
  linux: 4.12.0-13.14 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  Confirmed
Status in Kernel Development Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  This bug is for tracking the 4.12.0-13.14 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 --
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1715439] Re: linux: 3.13.0-131.180 -proposed tracker

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

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

Title:
  linux: 3.13.0-131.180 -proposed tracker

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

  backports: 1715441
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1714687] Re: linux: 4.12.0-13.14 -proposed tracker

** Tags added: regression-testing-passed

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

Title:
  linux: 4.12.0-13.14 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  This bug is for tracking the 4.12.0-13.14 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 --
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1715861] Re: r592 & r852 IRQ: DMA errors cause excessive log file entries

2017-09-08 Thread Christopher M. Penalver

Pontus Gråskæg, in order to allow additional upstream developers to examine the 
issue, at your earliest convenience, could you please test the latest upstream 
kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? 
Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the 
daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was 
released upstream.
4) Install instructions are available at: 
https://wiki.ubuntu.com/Kernel/MainlineBuilds

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the upstream kernel, please comment on which kernel version 
specifically you tested. If this issue is fixed in the mainline kernel, please 
add the following tags by clicking on the yellow circle with a black pencil 
icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

It is most helpful that after testing of the latest upstream kernel is
complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test
the latest mainline kernel as it becomes available.

Thank you for your help.

** Description changed:

- Issue on a newly installed Lubuntu 16.04.3 with 'apt upgrade' freshly
- applied.
- 
   -- /var/log/syslog and /var/log/kern.log grow to 100s of MiB in less
  than a day. --
  
- Typical excessive syslog entry is attached (hostname redacted). I am not
- making hardware changes at the times these entries are made. Entires are
- of the form:
- 
+ Typical excessive syslog entry is attached (hostname redacted). I am not 
making hardware changes at the times these entries are made. Entires are of the 
form:
  Sep  7 20:05:55  kernel: [14098.011547] r592: IRQ: card added
  Sep  7 20:05:55  kernel: [14098.011548] r592: IRQ: DMA error
  
  followed by 38 lines of trace information
  
- 
- Note that the kernel reports itself as tainted. This is due to a previous 
kernel warning issued during the boot-up, which I believe to be unrelated - 
kern.log extract (hostname redacted) of warning and taint also attached.
- 
- The laptop reports itself as having the problematic Ricoh devices.
- Relevant hwinfo attached. grepped extract follows
- 
+ The laptop reports itself as having the problematic Ricoh devices. Relevant 
hwinfo attached. grepped extract follows
Model: "Ricoh R5C832 IEEE 1394 Controller"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh xD-Picture Card Controller"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh R5C592 Memory Stick Bus Host Adapter"
Vendor: pci 0x1180 "Ricoh Co Ltd"
  
- Workaround is blacklisting devices by adding the following lines at the
- end of /etc/modprobe.d/blacklist.conf
+ WORKAROUND: Blacklist devices by adding the following lines at the end
+ of /etc/modprobe.d/blacklist.conf
  
  # Stop errors filling up log - see
  # https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530187
  # Blacklist Ricoh card reader
  blacklist r592
  blacklist r852
  
  This stops messages from appearing in /var/log/kern.log and
  /var/log/syslog. The Ricoh cardreader built into the laptop still reads
  SD cards after such blacklisting.
  
- (lsb_release -rd output is
- Description:  Ubuntu 16.04.3 LTS
- Release:  16.04
- 
- 
- graaskaeg
- 
- ProblemType: Bug
- DistroRelease: Ubuntu 16.04
- Package: linux-image-4.10.0-33-generic 4.10.0-33.37~16.04.1
- ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
- Uname: Linux 4.10.0-33-generic x86_64
- ApportVersion: 2.20.1-0ubuntu2.10
- Architecture: amd64
- Date: Fri Sep  8 13:30:06 2017
- InstallationDate: Installed on 2017-09-05 (3 days ago)
- InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
- SourcePackage: linux-hwe
- UpgradeStatus: No upgrade log present (probably fresh install)
- --- 
+ ---
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND

[Kernel-packages] [Bug 1715073] Re: SRIOV: warning if unload VFs

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

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

Title:
  SRIOV: warning if unload VFs

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  Fix Committed

Bug description:
  == Comment: #0 - Carol L. Soto  - 2017-02-23 16:11:47 ==
  ---Problem Description---
  When doing SRIOV if I unload VFs will see a warning:

  Feb 23 16:05:56 powerio-le11 kernel: [  201.343397] 
mlx5_3:wait_for_async_commands:674:(pid 6272): done with all pending requests
  Feb 23 16:05:56 powerio-le11 kernel: [  201.603999] iommu: Removing device 
0004:01:00.2 from group 7
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604078] pci 0004:01: 0.2: [PE# 
00] Removing DMA window #0
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604084] pci 0004:01: 0.2: [PE# 
00] Disabling 64-bit DMA bypass
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604350] mlx5_core 0004:01:00.0: 
VF BAR0: [mem 0x2400-0x2401 64bit pref] shifted to [mem 
0x2400-0x2401 64bit pref] (Disabling 1 VFs shifted by 0)
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604363] mlx5_core 0004:01:00.0: 
can't update enabled VF BAR0 [mem 0x2400-0x2401 64bit pref]
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604379] [ cut here 
]
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604386] WARNING: CPU: 14 PID: 
6272 at /build/linux-twbIHf/linux-4.10.0/drivers/pci/iov.c:584 
pci_iov_update_resource+0x178/0x1d0
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604388] Modules linked in: 
mlx5_ib xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack 
nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp kvm_hv kvm_pr kvm 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bridge stp 
llc binfmt_misc ipmi_powernv ipmi_devintf uio_pdrv_genirq ipmi_msghandler uio 
vmx_crypto powernv_rng powernv_op_panel leds_powernv ibmpowernv ib_iser rdma_cm 
iw_cm ib_cm ib_core configfs iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi knem(OE) ip_tables x_tables autofs4 btrfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear mlx4_en ses enclosure scsi_transport_sas 
crc32c_vpmsum mlx5_core mlx4_core
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604451]  tg3 ipr devlink
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604456] CPU: 14 PID: 6272 Comm: 
bash Tainted: G   OE   4.10.0-8-generic #10-Ubuntu
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604457] task: c00f40a6d600 
task.stack: c00f40ac8000
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604459] NIP: c06721b8 LR: 
c06721b4 CTR: 
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604461] REGS: c00f40acb590 
TRAP: 0700   Tainted: G   OE(4.10.0-8-generic)
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604462] MSR: 9282b033 

  Feb 23 16:05:56 powerio-le11 kernel: [  201.604470]   CR: 42424422  XER: 
2000
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] CFAR: c0b49db4 
SOFTE: 1
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR00: c06721b4 
c00f40acb810 c143c900 0063
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR04: 0001 
0539 c01fff70 00021a50
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR08: 0007 
0007 0001 656d5b2030524142
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR12: 4400 
cfb87e00 10180df8 10189e60
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR16: 10189ed8 
c00fdd0a2400 c01fff97d180 c0d46268
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR20: c0d4e410 
c0d41df8 c01fff97d190 c0d4d8d8
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR24: c0d4d8e0 
c00fe8f460a0 0001 
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR28: c00fe8f80f80 
 c00fe8f46580 c00fe8f46000
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604498] NIP [c06721b8] 
pci_iov_update_resource+0x178/0x1d0
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604501] LR [c06721b4] 
pci_iov_update_resource+0x174/0x1d0
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604501] Call Trace:
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604504] [c00f40acb810] 
[c06721b4] pci_iov_update_resource+0x174/0x1d0 (unreliable)
  Feb 23 16:05:56

[Kernel-packages] [Bug 1646277] Re: Xenial server 16.04.x will have a black screen after PXE installation

And you are also able to reproduce this bug with the various test
kernels I post?  If so, we should be able to narrow this down without
having to install every time.

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

Title:
  Xenial server 16.04.x will have a black screen after PXE installation

Status in debian-installer package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in debian-installer source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  The display will keep black screen after install 16.04.x via PXE(need
  use "Ctrl+Alt+F1" to change to terminal 1, then can see text mode
  screen)

  Quanta team is installing Xenial server using PXE boot.   After the
  installation, the console will show a black screen.   Hitting ctl-
  alt-f1 displays the text mode screen OK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1646277/+subscriptions

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

[Kernel-packages] [Bug 1716002] [NEW] linux 4.12.0-13.14 ADT test failure with linux 4.12.0-13.14

Public bug reported:

Testing failed on:
ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/l/linux/20170908_143833_78e28@/log.gz

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  linux 4.12.0-13.14 ADT test failure with linux 4.12.0-13.14

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Testing failed on:
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/l/linux/20170908_143833_78e28@/log.gz

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

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

[Kernel-packages] [Bug 1715119] Re: ubuntu_blktrace_smoke_test complains about insufficient trace events on Trusty kernel

2017-09-08 Thread Colin Ian King

Fix committed: http://kernel.ubuntu.com/git/ubuntu/autotest-client-
tests.git/commit/?id=91ba3d8dadb429430990ad15cb748aa6a6ff24b1

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

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

Title:
  ubuntu_blktrace_smoke_test complains about insufficient trace events
  on Trusty kernel

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  It has passed the first two tests, but failed with the last two:

  PASSED (got 130842 block trace events)
  FAILED (expecting at least 1024 block read traces events, got 0)
  FAILED (expecting at least 1024 block write traces events, got 0)

  This issue can be found on amd64 and arm64 systems.

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

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

[Kernel-packages] [Bug 1715439] Re: linux: 3.13.0-131.180 -proposed tracker

2017-09-08 Thread Kleber Sacilotto de Souza

** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

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

Title:
  linux: 3.13.0-131.180 -proposed tracker

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

  backports: 1715441
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1709749] Re: Docker hangs with xfs using aufs storage driver

2017-09-08 Thread Kleber Sacilotto de Souza

Hello Akihiro,

Thank you verifying the fix.

** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty

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

Title:
  Docker hangs with xfs using aufs storage driver

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Running the yum command in a Centos/RHEL container causes the
  process to hang enter uninterruptible sleep mode if /var/lib/docker is
  hosted on an XFS filesystem while the AUFS storage driver is used.

  Fix: Commit e34c81ff96415c64ca827ec30e7935454d26c1d3 from upstream
  aufs-standalone. Requires prerequisite commit
  b4d3dcc92a13d53952fe6e9a640201ef87475302.

  Test Case: Test scenario described above. Kernel with fixes applied
  has been confirmed by reporter to fix the issue.

  Regression Potential: Both patches have been in upstream aufs-
  standalone for a while now and included in the artful kernel as well
  as currently being included in the upstream branch for 4.10. Therefore
  they are well tested and unlikely to cause regressions.

  ---

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Ubuntu 16.04 and 17.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  kernel 4.10.0-28-generic

  3) What you expected to happen

  Docker with AUFS on XFS works.

  4) What happened instead

  It hangs up

  ---

  As reported in https://github.com/moby/moby/issues/34361 , AUFS on XFS
  needs this fix for kernel 4.10:
  
https://github.com/sfjro/aufs4-standalone/commit/e34c81ff96415c64ca827ec30e7935454d26c1d3

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

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

[Kernel-packages] [Bug 1715441] Re: linux-lts-trusty: 3.13.0-131.180~precise1 -proposed tracker

** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

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

Title:
  linux-lts-trusty: 3.13.0-131.180~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  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: 1715439
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

apport information

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

Title:
  Ralink wifi RT3290 on Ubuntu 17.04 critical driver issues

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When ubuntu 17.04 is installed wifi Ralink RT3290 is recognized
  immediately but it doesn't work at all even it "connects" and says
  connection established with good quality - it's poor and almost zero
  quality with frequent disconnections. All this makes equipments with
  ralink wifi cards unable to work under linux distros and there're
  thousands of them.

  Recently found modded drivers for RT3290 which installed without any
  issues and wifi worked after that like a charm, but after system
  reinstall I can't install theese modded drivers anymore and there're
  some issues during installation and loading kernel modules (maybe it's
  something with latest linux kernels)...

  Anyway it's pointess to use RT2800pci driver for physical RT3290 chip
  cause it's a wrong piece of code and Ubuntu maintainers should fix
  this.

  BTW Bluetooth RT3290 doesn't work at all but making RT3290 wifi works is 
seriously critical.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pawel  2113 F pulseaudio
   /dev/snd/controlC0:  pawel  2113 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-08 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. X750JB
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=cb519ab1-5f5d-444e-9f92-b628ae93156e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/14/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X750JB.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X750JB
  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.:bvrX750JB.208:bd08/14/2013:svnASUSTeKCOMPUTERINC.:pnX750JB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX750JB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X750JB
  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/1715866/+subscriptions

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

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

apport information

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

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

Title:
  Ralink wifi RT3290 on Ubuntu 17.04 critical driver issues

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When ubuntu 17.04 is installed wifi Ralink RT3290 is recognized
  immediately but it doesn't work at all even it "connects" and says
  connection established with good quality - it's poor and almost zero
  quality with frequent disconnections. All this makes equipments with
  ralink wifi cards unable to work under linux distros and there're
  thousands of them.

  Recently found modded drivers for RT3290 which installed without any
  issues and wifi worked after that like a charm, but after system
  reinstall I can't install theese modded drivers anymore and there're
  some issues during installation and loading kernel modules (maybe it's
  something with latest linux kernels)...

  Anyway it's pointess to use RT2800pci driver for physical RT3290 chip
  cause it's a wrong piece of code and Ubuntu maintainers should fix
  this.

  BTW Bluetooth RT3290 doesn't work at all but making RT3290 wifi works is 
seriously critical.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pawel  2113 F pulseaudio
   /dev/snd/controlC0:  pawel  2113 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-08 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. X750JB
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=cb519ab1-5f5d-444e-9f92-b628ae93156e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/14/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X750JB.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X750JB
  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.:bvrX750JB.208:bd08/14/2013:svnASUSTeKCOMPUTERINC.:pnX750JB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX750JB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X750JB
  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/1715866/+subscriptions

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

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

apport information

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

Title:
  Ralink wifi RT3290 on Ubuntu 17.04 critical driver issues

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When ubuntu 17.04 is installed wifi Ralink RT3290 is recognized
  immediately but it doesn't work at all even it "connects" and says
  connection established with good quality - it's poor and almost zero
  quality with frequent disconnections. All this makes equipments with
  ralink wifi cards unable to work under linux distros and there're
  thousands of them.

  Recently found modded drivers for RT3290 which installed without any
  issues and wifi worked after that like a charm, but after system
  reinstall I can't install theese modded drivers anymore and there're
  some issues during installation and loading kernel modules (maybe it's
  something with latest linux kernels)...

  Anyway it's pointess to use RT2800pci driver for physical RT3290 chip
  cause it's a wrong piece of code and Ubuntu maintainers should fix
  this.

  BTW Bluetooth RT3290 doesn't work at all but making RT3290 wifi works is 
seriously critical.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pawel  2113 F pulseaudio
   /dev/snd/controlC0:  pawel  2113 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-08 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. X750JB
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=cb519ab1-5f5d-444e-9f92-b628ae93156e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/14/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X750JB.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X750JB
  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.:bvrX750JB.208:bd08/14/2013:svnASUSTeKCOMPUTERINC.:pnX750JB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX750JB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X750JB
  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/1715866/+subscriptions

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

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

apport information

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

Title:
  Ralink wifi RT3290 on Ubuntu 17.04 critical driver issues

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When ubuntu 17.04 is installed wifi Ralink RT3290 is recognized
  immediately but it doesn't work at all even it "connects" and says
  connection established with good quality - it's poor and almost zero
  quality with frequent disconnections. All this makes equipments with
  ralink wifi cards unable to work under linux distros and there're
  thousands of them.

  Recently found modded drivers for RT3290 which installed without any
  issues and wifi worked after that like a charm, but after system
  reinstall I can't install theese modded drivers anymore and there're
  some issues during installation and loading kernel modules (maybe it's
  something with latest linux kernels)...

  Anyway it's pointess to use RT2800pci driver for physical RT3290 chip
  cause it's a wrong piece of code and Ubuntu maintainers should fix
  this.

  BTW Bluetooth RT3290 doesn't work at all but making RT3290 wifi works is 
seriously critical.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pawel  2113 F pulseaudio
   /dev/snd/controlC0:  pawel  2113 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-08 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. X750JB
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=cb519ab1-5f5d-444e-9f92-b628ae93156e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/14/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X750JB.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X750JB
  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.:bvrX750JB.208:bd08/14/2013:svnASUSTeKCOMPUTERINC.:pnX750JB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX750JB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X750JB
  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/1715866/+subscriptions

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

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

apport information

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

Title:
  Ralink wifi RT3290 on Ubuntu 17.04 critical driver issues

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When ubuntu 17.04 is installed wifi Ralink RT3290 is recognized
  immediately but it doesn't work at all even it "connects" and says
  connection established with good quality - it's poor and almost zero
  quality with frequent disconnections. All this makes equipments with
  ralink wifi cards unable to work under linux distros and there're
  thousands of them.

  Recently found modded drivers for RT3290 which installed without any
  issues and wifi worked after that like a charm, but after system
  reinstall I can't install theese modded drivers anymore and there're
  some issues during installation and loading kernel modules (maybe it's
  something with latest linux kernels)...

  Anyway it's pointess to use RT2800pci driver for physical RT3290 chip
  cause it's a wrong piece of code and Ubuntu maintainers should fix
  this.

  BTW Bluetooth RT3290 doesn't work at all but making RT3290 wifi works is 
seriously critical.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pawel  2113 F pulseaudio
   /dev/snd/controlC0:  pawel  2113 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-08 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. X750JB
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=cb519ab1-5f5d-444e-9f92-b628ae93156e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/14/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X750JB.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X750JB
  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.:bvrX750JB.208:bd08/14/2013:svnASUSTeKCOMPUTERINC.:pnX750JB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX750JB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X750JB
  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/1715866/+subscriptions

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

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

apport information

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

Title:
  Ralink wifi RT3290 on Ubuntu 17.04 critical driver issues

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When ubuntu 17.04 is installed wifi Ralink RT3290 is recognized
  immediately but it doesn't work at all even it "connects" and says
  connection established with good quality - it's poor and almost zero
  quality with frequent disconnections. All this makes equipments with
  ralink wifi cards unable to work under linux distros and there're
  thousands of them.

  Recently found modded drivers for RT3290 which installed without any
  issues and wifi worked after that like a charm, but after system
  reinstall I can't install theese modded drivers anymore and there're
  some issues during installation and loading kernel modules (maybe it's
  something with latest linux kernels)...

  Anyway it's pointess to use RT2800pci driver for physical RT3290 chip
  cause it's a wrong piece of code and Ubuntu maintainers should fix
  this.

  BTW Bluetooth RT3290 doesn't work at all but making RT3290 wifi works is 
seriously critical.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pawel  2113 F pulseaudio
   /dev/snd/controlC0:  pawel  2113 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-08 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. X750JB
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=cb519ab1-5f5d-444e-9f92-b628ae93156e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/14/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X750JB.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X750JB
  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.:bvrX750JB.208:bd08/14/2013:svnASUSTeKCOMPUTERINC.:pnX750JB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX750JB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X750JB
  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/1715866/+subscriptions

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

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

apport information

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

Title:
  Ralink wifi RT3290 on Ubuntu 17.04 critical driver issues

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When ubuntu 17.04 is installed wifi Ralink RT3290 is recognized
  immediately but it doesn't work at all even it "connects" and says
  connection established with good quality - it's poor and almost zero
  quality with frequent disconnections. All this makes equipments with
  ralink wifi cards unable to work under linux distros and there're
  thousands of them.

  Recently found modded drivers for RT3290 which installed without any
  issues and wifi worked after that like a charm, but after system
  reinstall I can't install theese modded drivers anymore and there're
  some issues during installation and loading kernel modules (maybe it's
  something with latest linux kernels)...

  Anyway it's pointess to use RT2800pci driver for physical RT3290 chip
  cause it's a wrong piece of code and Ubuntu maintainers should fix
  this.

  BTW Bluetooth RT3290 doesn't work at all but making RT3290 wifi works is 
seriously critical.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pawel  2113 F pulseaudio
   /dev/snd/controlC0:  pawel  2113 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-08 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. X750JB
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=cb519ab1-5f5d-444e-9f92-b628ae93156e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/14/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X750JB.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X750JB
  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.:bvrX750JB.208:bd08/14/2013:svnASUSTeKCOMPUTERINC.:pnX750JB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX750JB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X750JB
  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/1715866/+subscriptions

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

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

apport information

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

Title:
  Ralink wifi RT3290 on Ubuntu 17.04 critical driver issues

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When ubuntu 17.04 is installed wifi Ralink RT3290 is recognized
  immediately but it doesn't work at all even it "connects" and says
  connection established with good quality - it's poor and almost zero
  quality with frequent disconnections. All this makes equipments with
  ralink wifi cards unable to work under linux distros and there're
  thousands of them.

  Recently found modded drivers for RT3290 which installed without any
  issues and wifi worked after that like a charm, but after system
  reinstall I can't install theese modded drivers anymore and there're
  some issues during installation and loading kernel modules (maybe it's
  something with latest linux kernels)...

  Anyway it's pointess to use RT2800pci driver for physical RT3290 chip
  cause it's a wrong piece of code and Ubuntu maintainers should fix
  this.

  BTW Bluetooth RT3290 doesn't work at all but making RT3290 wifi works is 
seriously critical.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pawel  2113 F pulseaudio
   /dev/snd/controlC0:  pawel  2113 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-08 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. X750JB
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=cb519ab1-5f5d-444e-9f92-b628ae93156e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/14/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X750JB.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X750JB
  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.:bvrX750JB.208:bd08/14/2013:svnASUSTeKCOMPUTERINC.:pnX750JB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX750JB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X750JB
  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/1715866/+subscriptions

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

[Kernel-packages] [Bug 1715866] Re: Ralink wifi RT3290 on Ubuntu 17.04 critical driver issues

apport information

** Tags added: apport-collected

** Description changed:

  When ubuntu 17.04 is installed wifi Ralink RT3290 is recognized
  immediately but it doesn't work at all even it "connects" and says
  connection established with good quality - it's poor and almost zero
  quality with frequent disconnections. All this makes equipments with
  ralink wifi cards unable to work under linux distros and there're
  thousands of them.
  
  Recently found modded drivers for RT3290 which installed without any
  issues and wifi worked after that like a charm, but after system
  reinstall I can't install theese modded drivers anymore and there're
  some issues during installation and loading kernel modules (maybe it's
  something with latest linux kernels)...
  
  Anyway it's pointess to use RT2800pci driver for physical RT3290 chip
  cause it's a wrong piece of code and Ubuntu maintainers should fix this.
  
- BTW Bluetooth RT3290 doesn't work at all but making RT3290 wifi works is
- seriously critical.
+ BTW Bluetooth RT3290 doesn't work at all but making RT3290 wifi works is 
seriously critical.
+ --- 
+ ApportVersion: 2.20.4-0ubuntu4.5
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  pawel  2113 F pulseaudio
+  /dev/snd/controlC0:  pawel  2113 F pulseaudio
+ CurrentDesktop: Unity:Unity7
+ DistroRelease: Ubuntu 17.04
+ InstallationDate: Installed on 2017-09-08 (0 days ago)
+ InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
+ MachineType: ASUSTeK COMPUTER INC. X750JB
+ NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=cb519ab1-5f5d-444e-9f92-b628ae93156e ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
+ RelatedPackageVersions:
+  linux-restricted-modules-4.10.0-33-generic N/A
+  linux-backports-modules-4.10.0-33-generic  N/A
+  linux-firmware 1.164.1
+ RfKill:
+  0: phy0: Wireless LAN
+   Soft blocked: no
+   Hard blocked: no
+ Tags:  zesty
+ Uname: Linux 4.10.0-33-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 08/14/2013
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: X750JB.208
+ dmi.board.asset.tag: ATN12345678901234567
+ dmi.board.name: X750JB
+ 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.:bvrX750JB.208:bd08/14/2013:svnASUSTeKCOMPUTERINC.:pnX750JB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX750JB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
+ dmi.product.name: X750JB
+ dmi.product.version: 1.0
+ dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1715866/+attachment/4946542/+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/1715866

Title:
  Ralink wifi RT3290 on Ubuntu 17.04 critical driver issues

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When ubuntu 17.04 is installed wifi Ralink RT3290 is recognized
  immediately but it doesn't work at all even it "connects" and says
  connection established with good quality - it's poor and almost zero
  quality with frequent disconnections. All this makes equipments with
  ralink wifi cards unable to work under linux distros and there're
  thousands of them.

  Recently found modded drivers for RT3290 which installed without any
  issues and wifi worked after that like a charm, but after system
  reinstall I can't install theese modded drivers anymore and there're
  some issues during installation and loading kernel modules (maybe it's
  something with latest linux kernels)...

  Anyway it's pointess to use RT2800pci driver for physical RT3290 chip
  cause it's a wrong piece of code and Ubuntu maintainers should fix
  this.

  BTW Bluetooth RT3290 doesn't work at all but making RT3290 wifi works is 
seriously critical.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pawel  2113 F pulseaudio
   /dev/snd/controlC0:  pawel  2113 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-08 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. X750JB
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0

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

apport information

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

Title:
  Ralink wifi RT3290 on Ubuntu 17.04 critical driver issues

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When ubuntu 17.04 is installed wifi Ralink RT3290 is recognized
  immediately but it doesn't work at all even it "connects" and says
  connection established with good quality - it's poor and almost zero
  quality with frequent disconnections. All this makes equipments with
  ralink wifi cards unable to work under linux distros and there're
  thousands of them.

  Recently found modded drivers for RT3290 which installed without any
  issues and wifi worked after that like a charm, but after system
  reinstall I can't install theese modded drivers anymore and there're
  some issues during installation and loading kernel modules (maybe it's
  something with latest linux kernels)...

  Anyway it's pointess to use RT2800pci driver for physical RT3290 chip
  cause it's a wrong piece of code and Ubuntu maintainers should fix
  this.

  BTW Bluetooth RT3290 doesn't work at all but making RT3290 wifi works is 
seriously critical.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pawel  2113 F pulseaudio
   /dev/snd/controlC0:  pawel  2113 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-08 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. X750JB
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=cb519ab1-5f5d-444e-9f92-b628ae93156e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/14/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X750JB.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X750JB
  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.:bvrX750JB.208:bd08/14/2013:svnASUSTeKCOMPUTERINC.:pnX750JB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX750JB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X750JB
  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/1715866/+subscriptions

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

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

apport information

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

Title:
  Ralink wifi RT3290 on Ubuntu 17.04 critical driver issues

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When ubuntu 17.04 is installed wifi Ralink RT3290 is recognized
  immediately but it doesn't work at all even it "connects" and says
  connection established with good quality - it's poor and almost zero
  quality with frequent disconnections. All this makes equipments with
  ralink wifi cards unable to work under linux distros and there're
  thousands of them.

  Recently found modded drivers for RT3290 which installed without any
  issues and wifi worked after that like a charm, but after system
  reinstall I can't install theese modded drivers anymore and there're
  some issues during installation and loading kernel modules (maybe it's
  something with latest linux kernels)...

  Anyway it's pointess to use RT2800pci driver for physical RT3290 chip
  cause it's a wrong piece of code and Ubuntu maintainers should fix
  this.

  BTW Bluetooth RT3290 doesn't work at all but making RT3290 wifi works is 
seriously critical.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pawel  2113 F pulseaudio
   /dev/snd/controlC0:  pawel  2113 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-08 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. X750JB
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=cb519ab1-5f5d-444e-9f92-b628ae93156e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/14/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X750JB.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X750JB
  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.:bvrX750JB.208:bd08/14/2013:svnASUSTeKCOMPUTERINC.:pnX750JB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX750JB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X750JB
  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/1715866/+subscriptions

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

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

apport information

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

Title:
  Ralink wifi RT3290 on Ubuntu 17.04 critical driver issues

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When ubuntu 17.04 is installed wifi Ralink RT3290 is recognized
  immediately but it doesn't work at all even it "connects" and says
  connection established with good quality - it's poor and almost zero
  quality with frequent disconnections. All this makes equipments with
  ralink wifi cards unable to work under linux distros and there're
  thousands of them.

  Recently found modded drivers for RT3290 which installed without any
  issues and wifi worked after that like a charm, but after system
  reinstall I can't install theese modded drivers anymore and there're
  some issues during installation and loading kernel modules (maybe it's
  something with latest linux kernels)...

  Anyway it's pointess to use RT2800pci driver for physical RT3290 chip
  cause it's a wrong piece of code and Ubuntu maintainers should fix
  this.

  BTW Bluetooth RT3290 doesn't work at all but making RT3290 wifi works is 
seriously critical.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pawel  2113 F pulseaudio
   /dev/snd/controlC0:  pawel  2113 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-08 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. X750JB
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=cb519ab1-5f5d-444e-9f92-b628ae93156e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/14/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X750JB.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X750JB
  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.:bvrX750JB.208:bd08/14/2013:svnASUSTeKCOMPUTERINC.:pnX750JB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX750JB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X750JB
  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/1715866/+subscriptions

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

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

apport information

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

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

Title:
  Ralink wifi RT3290 on Ubuntu 17.04 critical driver issues

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When ubuntu 17.04 is installed wifi Ralink RT3290 is recognized
  immediately but it doesn't work at all even it "connects" and says
  connection established with good quality - it's poor and almost zero
  quality with frequent disconnections. All this makes equipments with
  ralink wifi cards unable to work under linux distros and there're
  thousands of them.

  Recently found modded drivers for RT3290 which installed without any
  issues and wifi worked after that like a charm, but after system
  reinstall I can't install theese modded drivers anymore and there're
  some issues during installation and loading kernel modules (maybe it's
  something with latest linux kernels)...

  Anyway it's pointess to use RT2800pci driver for physical RT3290 chip
  cause it's a wrong piece of code and Ubuntu maintainers should fix
  this.

  BTW Bluetooth RT3290 doesn't work at all but making RT3290 wifi works is 
seriously critical.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pawel  2113 F pulseaudio
   /dev/snd/controlC0:  pawel  2113 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-08 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. X750JB
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=cb519ab1-5f5d-444e-9f92-b628ae93156e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/14/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X750JB.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X750JB
  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.:bvrX750JB.208:bd08/14/2013:svnASUSTeKCOMPUTERINC.:pnX750JB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX750JB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X750JB
  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/1715866/+subscriptions

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

[Kernel-packages] [Bug 1715866] JournalErrors.txt

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1715866/+attachment/4946546/+files/JournalErrors.txt

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

Title:
  Ralink wifi RT3290 on Ubuntu 17.04 critical driver issues

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When ubuntu 17.04 is installed wifi Ralink RT3290 is recognized
  immediately but it doesn't work at all even it "connects" and says
  connection established with good quality - it's poor and almost zero
  quality with frequent disconnections. All this makes equipments with
  ralink wifi cards unable to work under linux distros and there're
  thousands of them.

  Recently found modded drivers for RT3290 which installed without any
  issues and wifi worked after that like a charm, but after system
  reinstall I can't install theese modded drivers anymore and there're
  some issues during installation and loading kernel modules (maybe it's
  something with latest linux kernels)...

  Anyway it's pointess to use RT2800pci driver for physical RT3290 chip
  cause it's a wrong piece of code and Ubuntu maintainers should fix
  this.

  BTW Bluetooth RT3290 doesn't work at all but making RT3290 wifi works is 
seriously critical.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pawel  2113 F pulseaudio
   /dev/snd/controlC0:  pawel  2113 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-08 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. X750JB
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=cb519ab1-5f5d-444e-9f92-b628ae93156e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/14/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X750JB.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X750JB
  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.:bvrX750JB.208:bd08/14/2013:svnASUSTeKCOMPUTERINC.:pnX750JB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX750JB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X750JB
  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/1715866/+subscriptions

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

[Kernel-packages] [Bug 1715866] IwConfig.txt

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1715866/+attachment/4946545/+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/1715866

Title:
  Ralink wifi RT3290 on Ubuntu 17.04 critical driver issues

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When ubuntu 17.04 is installed wifi Ralink RT3290 is recognized
  immediately but it doesn't work at all even it "connects" and says
  connection established with good quality - it's poor and almost zero
  quality with frequent disconnections. All this makes equipments with
  ralink wifi cards unable to work under linux distros and there're
  thousands of them.

  Recently found modded drivers for RT3290 which installed without any
  issues and wifi worked after that like a charm, but after system
  reinstall I can't install theese modded drivers anymore and there're
  some issues during installation and loading kernel modules (maybe it's
  something with latest linux kernels)...

  Anyway it's pointess to use RT2800pci driver for physical RT3290 chip
  cause it's a wrong piece of code and Ubuntu maintainers should fix
  this.

  BTW Bluetooth RT3290 doesn't work at all but making RT3290 wifi works is 
seriously critical.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pawel  2113 F pulseaudio
   /dev/snd/controlC0:  pawel  2113 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-08 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. X750JB
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=cb519ab1-5f5d-444e-9f92-b628ae93156e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/14/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X750JB.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X750JB
  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.:bvrX750JB.208:bd08/14/2013:svnASUSTeKCOMPUTERINC.:pnX750JB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX750JB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X750JB
  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/1715866/+subscriptions

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

[Kernel-packages] [Bug 1709749] Re: Docker hangs with xfs using aufs storage driver

2017-09-08 Thread Akihiro Suda

Confirmed 4.10.0-34-generic (x86_64) works, sorry for late reply

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

Title:
  Docker hangs with xfs using aufs storage driver

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Running the yum command in a Centos/RHEL container causes the
  process to hang enter uninterruptible sleep mode if /var/lib/docker is
  hosted on an XFS filesystem while the AUFS storage driver is used.

  Fix: Commit e34c81ff96415c64ca827ec30e7935454d26c1d3 from upstream
  aufs-standalone. Requires prerequisite commit
  b4d3dcc92a13d53952fe6e9a640201ef87475302.

  Test Case: Test scenario described above. Kernel with fixes applied
  has been confirmed by reporter to fix the issue.

  Regression Potential: Both patches have been in upstream aufs-
  standalone for a while now and included in the artful kernel as well
  as currently being included in the upstream branch for 4.10. Therefore
  they are well tested and unlikely to cause regressions.

  ---

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Ubuntu 16.04 and 17.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  kernel 4.10.0-28-generic

  3) What you expected to happen

  Docker with AUFS on XFS works.

  4) What happened instead

  It hangs up

  ---

  As reported in https://github.com/moby/moby/issues/34361 , AUFS on XFS
  needs this fix for kernel 4.10:
  
https://github.com/sfjro/aufs4-standalone/commit/e34c81ff96415c64ca827ec30e7935454d26c1d3

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

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

[Kernel-packages] [Bug 1715271] Re: Middle button of trackpoint doesn't work

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

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

Title:
  Middle button of trackpoint doesn't work

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  Fix Committed

Bug description:
  Middle button doesn't work on several Thinkpad laptops like E570,
  E475, E470, E575 and X1Carbon.

  When middle button fails to work, logs show:
  psmouse serio2: trackpoint: failed to get extended button data

  It fails to read out ext button info via PS2 command.
  Almost all the Thinkpad have 3 buttons, so set it to 3 button when it fails 
to read button info.

  And on Lenovo X1, there is a new version of trackpoint, add this ID
  for this new device.

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

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

[Kernel-packages] [Bug 1713884] Re: [CIFS] Fix maximum SMB2 header size

SRU requests submitted:

https://lists.ubuntu.com/archives/kernel-team/2017-September/086929.html
https://lists.ubuntu.com/archives/kernel-team/2017-September/086932.html

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

Title:
  [CIFS] Fix maximum SMB2 header size

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  In Progress

Bug description:
  Currently the maximum size of SMB2/3 header is set incorrectly which
  leads to hanging of directory listing operations on encrypted SMB3
  connections. Fix this by setting the maximum size to 170 bytes that
  is calculated as RFC1002 length field size (4) + transform header
  size (52) + SMB2 header size (64) + create response size (56).

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/?id=47690ab81f4f29b12bbb0676d3579e61ab4d84de

  This applies across the board 3.16, 4.4, 4.10, artful, and azure.
  Microsoft would be happy to help test.

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

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

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

apport information

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

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

Title:
  r592 & r852 IRQ: DMA errors cause excessive log file entries

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Issue on a newly installed Lubuntu 16.04.3 with 'apt upgrade' freshly
  applied.

   -- /var/log/syslog and /var/log/kern.log grow to 100s of MiB in less
  than a day. --

  Typical excessive syslog entry is attached (hostname redacted). I am
  not making hardware changes at the times these entries are made.
  Entires are of the form:

  Sep  7 20:05:55  kernel: [14098.011547] r592: IRQ: card added
  Sep  7 20:05:55  kernel: [14098.011548] r592: IRQ: DMA error

  followed by 38 lines of trace information

  
  Note that the kernel reports itself as tainted. This is due to a previous 
kernel warning issued during the boot-up, which I believe to be unrelated - 
kern.log extract (hostname redacted) of warning and taint also attached.

  The laptop reports itself as having the problematic Ricoh devices.
  Relevant hwinfo attached. grepped extract follows

Model: "Ricoh R5C832 IEEE 1394 Controller"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh xD-Picture Card Controller"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh R5C592 Memory Stick Bus Host Adapter"
Vendor: pci 0x1180 "Ricoh Co Ltd"

  Workaround is blacklisting devices by adding the following lines at
  the end of /etc/modprobe.d/blacklist.conf

  # Stop errors filling up log - see
  # https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530187
  # Blacklist Ricoh card reader
  blacklist r592
  blacklist r852

  This stops messages from appearing in /var/log/kern.log and
  /var/log/syslog. The Ricoh cardreader built into the laptop still
  reads SD cards after such blacklisting.

  (lsb_release -rd output is
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  
  graaskaeg

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-33-generic 4.10.0-33.37~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Sep  8 13:30:06 2017
  InstallationDate: Installed on 2017-09-05 (3 days ago)
  InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  pgrb   2220 F pulseaudio
   /dev/snd/controlC1:  pgrb   2220 F pulseaudio
   /dev/snd/controlC0:  pgrb   2220 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=2b7792b7-4eda-4b10-b21c-ad775ff397b3
  InstallationDate: Installed on 2017-09-05 (3 days ago)
  InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 0769BMG
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-33-generic 
root=/dev/mapper/herd-root ro 
cryptdevice=/dev/disk/by-uuid/081dc90a-6dbc-486a-8141-6635c99caca5:mithraeum 
quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.12
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/15/2007
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 68ET24WW
  dmi.board.name: IEL10
  dmi.board.vendor: LENOVO
  dmi.board.version: REFERENCE
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr68ET24WW:bd08/15/2007:svnLENOVO:pn0769BMG:pvr3000N200:rvnLENOVO:rnIEL10:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: 0769BMG
  dmi.product.version: 3000 N200
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

Title:
  r592 & r852 IRQ: DMA errors cause excessive log file entries

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Issue on a newly installed Lubuntu 16.04.3 with 'apt upgrade' freshly
  applied.

   -- /var/log/syslog and /var/log/kern.log grow to 100s of MiB in less
  than a day. --

  Typical excessive syslog entry is attached (hostname redacted). I am
  not making hardware changes at the times these entries are made.
  Entires are of the form:

  Sep  7 20:05:55  kernel: [14098.011547] r592: IRQ: card added
  Sep  7 20:05:55  kernel: [14098.011548] r592: IRQ: DMA error

  followed by 38 lines of trace information

  
  Note that the kernel reports itself as tainted. This is due to a previous 
kernel warning issued during the boot-up, which I believe to be unrelated - 
kern.log extract (hostname redacted) of warning and taint also attached.

  The laptop reports itself as having the problematic Ricoh devices.
  Relevant hwinfo attached. grepped extract follows

Model: "Ricoh R5C832 IEEE 1394 Controller"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh xD-Picture Card Controller"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh R5C592 Memory Stick Bus Host Adapter"
Vendor: pci 0x1180 "Ricoh Co Ltd"

  Workaround is blacklisting devices by adding the following lines at
  the end of /etc/modprobe.d/blacklist.conf

  # Stop errors filling up log - see
  # https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530187
  # Blacklist Ricoh card reader
  blacklist r592
  blacklist r852

  This stops messages from appearing in /var/log/kern.log and
  /var/log/syslog. The Ricoh cardreader built into the laptop still
  reads SD cards after such blacklisting.

  (lsb_release -rd output is
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  
  graaskaeg

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-33-generic 4.10.0-33.37~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Sep  8 13:30:06 2017
  InstallationDate: Installed on 2017-09-05 (3 days ago)
  InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  pgrb   2220 F pulseaudio
   /dev/snd/controlC1:  pgrb   2220 F pulseaudio
   /dev/snd/controlC0:  pgrb   2220 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=2b7792b7-4eda-4b10-b21c-ad775ff397b3
  InstallationDate: Installed on 2017-09-05 (3 days ago)
  InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 0769BMG
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-33-generic 
root=/dev/mapper/herd-root ro 
cryptdevice=/dev/disk/by-uuid/081dc90a-6dbc-486a-8141-6635c99caca5:mithraeum 
quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.12
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/15/2007
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 68ET24WW
  dmi.board.name: IEL10
  dmi.board.vendor: LENOVO
  dmi.board.version: REFERENCE
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr68ET24WW:bd08/15/2007:svnLENOVO:pn0769BMG:pvr3000N200:rvnLENOVO:rnIEL10:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: 0769BMG
  dmi.product.version: 3000 N200
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

Title:
  r592 & r852 IRQ: DMA errors cause excessive log file entries

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Issue on a newly installed Lubuntu 16.04.3 with 'apt upgrade' freshly
  applied.

   -- /var/log/syslog and /var/log/kern.log grow to 100s of MiB in less
  than a day. --

  Typical excessive syslog entry is attached (hostname redacted). I am
  not making hardware changes at the times these entries are made.
  Entires are of the form:

  Sep  7 20:05:55  kernel: [14098.011547] r592: IRQ: card added
  Sep  7 20:05:55  kernel: [14098.011548] r592: IRQ: DMA error

  followed by 38 lines of trace information

  
  Note that the kernel reports itself as tainted. This is due to a previous 
kernel warning issued during the boot-up, which I believe to be unrelated - 
kern.log extract (hostname redacted) of warning and taint also attached.

  The laptop reports itself as having the problematic Ricoh devices.
  Relevant hwinfo attached. grepped extract follows

Model: "Ricoh R5C832 IEEE 1394 Controller"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh xD-Picture Card Controller"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh R5C592 Memory Stick Bus Host Adapter"
Vendor: pci 0x1180 "Ricoh Co Ltd"

  Workaround is blacklisting devices by adding the following lines at
  the end of /etc/modprobe.d/blacklist.conf

  # Stop errors filling up log - see
  # https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530187
  # Blacklist Ricoh card reader
  blacklist r592
  blacklist r852

  This stops messages from appearing in /var/log/kern.log and
  /var/log/syslog. The Ricoh cardreader built into the laptop still
  reads SD cards after such blacklisting.

  (lsb_release -rd output is
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  
  graaskaeg

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-33-generic 4.10.0-33.37~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Sep  8 13:30:06 2017
  InstallationDate: Installed on 2017-09-05 (3 days ago)
  InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  pgrb   2220 F pulseaudio
   /dev/snd/controlC1:  pgrb   2220 F pulseaudio
   /dev/snd/controlC0:  pgrb   2220 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=2b7792b7-4eda-4b10-b21c-ad775ff397b3
  InstallationDate: Installed on 2017-09-05 (3 days ago)
  InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 0769BMG
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-33-generic 
root=/dev/mapper/herd-root ro 
cryptdevice=/dev/disk/by-uuid/081dc90a-6dbc-486a-8141-6635c99caca5:mithraeum 
quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.12
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/15/2007
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 68ET24WW
  dmi.board.name: IEL10
  dmi.board.vendor: LENOVO
  dmi.board.version: REFERENCE
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr68ET24WW:bd08/15/2007:svnLENOVO:pn0769BMG:pvr3000N200:rvnLENOVO:rnIEL10:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: 0769BMG
  dmi.product.version: 3000 N200
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

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

Title:
  r592 & r852 IRQ: DMA errors cause excessive log file entries

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Issue on a newly installed Lubuntu 16.04.3 with 'apt upgrade' freshly
  applied.

   -- /var/log/syslog and /var/log/kern.log grow to 100s of MiB in less
  than a day. --

  Typical excessive syslog entry is attached (hostname redacted). I am
  not making hardware changes at the times these entries are made.
  Entires are of the form:

  Sep  7 20:05:55  kernel: [14098.011547] r592: IRQ: card added
  Sep  7 20:05:55  kernel: [14098.011548] r592: IRQ: DMA error

  followed by 38 lines of trace information

  
  Note that the kernel reports itself as tainted. This is due to a previous 
kernel warning issued during the boot-up, which I believe to be unrelated - 
kern.log extract (hostname redacted) of warning and taint also attached.

  The laptop reports itself as having the problematic Ricoh devices.
  Relevant hwinfo attached. grepped extract follows

Model: "Ricoh R5C832 IEEE 1394 Controller"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh xD-Picture Card Controller"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh R5C592 Memory Stick Bus Host Adapter"
Vendor: pci 0x1180 "Ricoh Co Ltd"

  Workaround is blacklisting devices by adding the following lines at
  the end of /etc/modprobe.d/blacklist.conf

  # Stop errors filling up log - see
  # https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530187
  # Blacklist Ricoh card reader
  blacklist r592
  blacklist r852

  This stops messages from appearing in /var/log/kern.log and
  /var/log/syslog. The Ricoh cardreader built into the laptop still
  reads SD cards after such blacklisting.

  (lsb_release -rd output is
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  
  graaskaeg

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-33-generic 4.10.0-33.37~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Sep  8 13:30:06 2017
  InstallationDate: Installed on 2017-09-05 (3 days ago)
  InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  pgrb   2220 F pulseaudio
   /dev/snd/controlC1:  pgrb   2220 F pulseaudio
   /dev/snd/controlC0:  pgrb   2220 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=2b7792b7-4eda-4b10-b21c-ad775ff397b3
  InstallationDate: Installed on 2017-09-05 (3 days ago)
  InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 0769BMG
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-33-generic 
root=/dev/mapper/herd-root ro 
cryptdevice=/dev/disk/by-uuid/081dc90a-6dbc-486a-8141-6635c99caca5:mithraeum 
quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.12
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/15/2007
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 68ET24WW
  dmi.board.name: IEL10
  dmi.board.vendor: LENOVO
  dmi.board.version: REFERENCE
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr68ET24WW:bd08/15/2007:svnLENOVO:pn0769BMG:pvr3000N200:rvnLENOVO:rnIEL10:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: 0769BMG
  dmi.product.version: 3000 N200
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

Title:
  r592 & r852 IRQ: DMA errors cause excessive log file entries

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Issue on a newly installed Lubuntu 16.04.3 with 'apt upgrade' freshly
  applied.

   -- /var/log/syslog and /var/log/kern.log grow to 100s of MiB in less
  than a day. --

  Typical excessive syslog entry is attached (hostname redacted). I am
  not making hardware changes at the times these entries are made.
  Entires are of the form:

  Sep  7 20:05:55  kernel: [14098.011547] r592: IRQ: card added
  Sep  7 20:05:55  kernel: [14098.011548] r592: IRQ: DMA error

  followed by 38 lines of trace information

  
  Note that the kernel reports itself as tainted. This is due to a previous 
kernel warning issued during the boot-up, which I believe to be unrelated - 
kern.log extract (hostname redacted) of warning and taint also attached.

  The laptop reports itself as having the problematic Ricoh devices.
  Relevant hwinfo attached. grepped extract follows

Model: "Ricoh R5C832 IEEE 1394 Controller"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh xD-Picture Card Controller"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh R5C592 Memory Stick Bus Host Adapter"
Vendor: pci 0x1180 "Ricoh Co Ltd"

  Workaround is blacklisting devices by adding the following lines at
  the end of /etc/modprobe.d/blacklist.conf

  # Stop errors filling up log - see
  # https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530187
  # Blacklist Ricoh card reader
  blacklist r592
  blacklist r852

  This stops messages from appearing in /var/log/kern.log and
  /var/log/syslog. The Ricoh cardreader built into the laptop still
  reads SD cards after such blacklisting.

  (lsb_release -rd output is
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  
  graaskaeg

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-33-generic 4.10.0-33.37~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Sep  8 13:30:06 2017
  InstallationDate: Installed on 2017-09-05 (3 days ago)
  InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  pgrb   2220 F pulseaudio
   /dev/snd/controlC1:  pgrb   2220 F pulseaudio
   /dev/snd/controlC0:  pgrb   2220 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=2b7792b7-4eda-4b10-b21c-ad775ff397b3
  InstallationDate: Installed on 2017-09-05 (3 days ago)
  InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 0769BMG
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-33-generic 
root=/dev/mapper/herd-root ro 
cryptdevice=/dev/disk/by-uuid/081dc90a-6dbc-486a-8141-6635c99caca5:mithraeum 
quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.12
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/15/2007
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 68ET24WW
  dmi.board.name: IEL10
  dmi.board.vendor: LENOVO
  dmi.board.version: REFERENCE
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr68ET24WW:bd08/15/2007:svnLENOVO:pn0769BMG:pvr3000N200:rvnLENOVO:rnIEL10:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: 0769BMG
  dmi.product.version: 3000 N200
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1715861] JournalErrors.txt

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1715861/+attachment/4946528/+files/JournalErrors.txt

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

Title:
  r592 & r852 IRQ: DMA errors cause excessive log file entries

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Issue on a newly installed Lubuntu 16.04.3 with 'apt upgrade' freshly
  applied.

   -- /var/log/syslog and /var/log/kern.log grow to 100s of MiB in less
  than a day. --

  Typical excessive syslog entry is attached (hostname redacted). I am
  not making hardware changes at the times these entries are made.
  Entires are of the form:

  Sep  7 20:05:55  kernel: [14098.011547] r592: IRQ: card added
  Sep  7 20:05:55  kernel: [14098.011548] r592: IRQ: DMA error

  followed by 38 lines of trace information

  
  Note that the kernel reports itself as tainted. This is due to a previous 
kernel warning issued during the boot-up, which I believe to be unrelated - 
kern.log extract (hostname redacted) of warning and taint also attached.

  The laptop reports itself as having the problematic Ricoh devices.
  Relevant hwinfo attached. grepped extract follows

Model: "Ricoh R5C832 IEEE 1394 Controller"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh xD-Picture Card Controller"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh R5C592 Memory Stick Bus Host Adapter"
Vendor: pci 0x1180 "Ricoh Co Ltd"

  Workaround is blacklisting devices by adding the following lines at
  the end of /etc/modprobe.d/blacklist.conf

  # Stop errors filling up log - see
  # https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530187
  # Blacklist Ricoh card reader
  blacklist r592
  blacklist r852

  This stops messages from appearing in /var/log/kern.log and
  /var/log/syslog. The Ricoh cardreader built into the laptop still
  reads SD cards after such blacklisting.

  (lsb_release -rd output is
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  
  graaskaeg

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-33-generic 4.10.0-33.37~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Sep  8 13:30:06 2017
  InstallationDate: Installed on 2017-09-05 (3 days ago)
  InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  pgrb   2220 F pulseaudio
   /dev/snd/controlC1:  pgrb   2220 F pulseaudio
   /dev/snd/controlC0:  pgrb   2220 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=2b7792b7-4eda-4b10-b21c-ad775ff397b3
  InstallationDate: Installed on 2017-09-05 (3 days ago)
  InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 0769BMG
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-33-generic 
root=/dev/mapper/herd-root ro 
cryptdevice=/dev/disk/by-uuid/081dc90a-6dbc-486a-8141-6635c99caca5:mithraeum 
quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.12
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/15/2007
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 68ET24WW
  dmi.board.name: IEL10
  dmi.board.vendor: LENOVO
  dmi.board.version: REFERENCE
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr68ET24WW:bd08/15/2007:svnLENOVO:pn0769BMG:pvr3000N200:rvnLENOVO:rnIEL10:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: 0769BMG
  dmi.product.version: 3000 N200
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

Title:
  r592 & r852 IRQ: DMA errors cause excessive log file entries

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Issue on a newly installed Lubuntu 16.04.3 with 'apt upgrade' freshly
  applied.

   -- /var/log/syslog and /var/log/kern.log grow to 100s of MiB in less
  than a day. --

  Typical excessive syslog entry is attached (hostname redacted). I am
  not making hardware changes at the times these entries are made.
  Entires are of the form:

  Sep  7 20:05:55  kernel: [14098.011547] r592: IRQ: card added
  Sep  7 20:05:55  kernel: [14098.011548] r592: IRQ: DMA error

  followed by 38 lines of trace information

  
  Note that the kernel reports itself as tainted. This is due to a previous 
kernel warning issued during the boot-up, which I believe to be unrelated - 
kern.log extract (hostname redacted) of warning and taint also attached.

  The laptop reports itself as having the problematic Ricoh devices.
  Relevant hwinfo attached. grepped extract follows

Model: "Ricoh R5C832 IEEE 1394 Controller"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh xD-Picture Card Controller"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh R5C592 Memory Stick Bus Host Adapter"
Vendor: pci 0x1180 "Ricoh Co Ltd"

  Workaround is blacklisting devices by adding the following lines at
  the end of /etc/modprobe.d/blacklist.conf

  # Stop errors filling up log - see
  # https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530187
  # Blacklist Ricoh card reader
  blacklist r592
  blacklist r852

  This stops messages from appearing in /var/log/kern.log and
  /var/log/syslog. The Ricoh cardreader built into the laptop still
  reads SD cards after such blacklisting.

  (lsb_release -rd output is
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  
  graaskaeg

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-33-generic 4.10.0-33.37~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Sep  8 13:30:06 2017
  InstallationDate: Installed on 2017-09-05 (3 days ago)
  InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  pgrb   2220 F pulseaudio
   /dev/snd/controlC1:  pgrb   2220 F pulseaudio
   /dev/snd/controlC0:  pgrb   2220 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=2b7792b7-4eda-4b10-b21c-ad775ff397b3
  InstallationDate: Installed on 2017-09-05 (3 days ago)
  InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 0769BMG
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-33-generic 
root=/dev/mapper/herd-root ro 
cryptdevice=/dev/disk/by-uuid/081dc90a-6dbc-486a-8141-6635c99caca5:mithraeum 
quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.12
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/15/2007
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 68ET24WW
  dmi.board.name: IEL10
  dmi.board.vendor: LENOVO
  dmi.board.version: REFERENCE
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr68ET24WW:bd08/15/2007:svnLENOVO:pn0769BMG:pvr3000N200:rvnLENOVO:rnIEL10:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: 0769BMG
  dmi.product.version: 3000 N200
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

Title:
  r592 & r852 IRQ: DMA errors cause excessive log file entries

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Issue on a newly installed Lubuntu 16.04.3 with 'apt upgrade' freshly
  applied.

   -- /var/log/syslog and /var/log/kern.log grow to 100s of MiB in less
  than a day. --

  Typical excessive syslog entry is attached (hostname redacted). I am
  not making hardware changes at the times these entries are made.
  Entires are of the form:

  Sep  7 20:05:55  kernel: [14098.011547] r592: IRQ: card added
  Sep  7 20:05:55  kernel: [14098.011548] r592: IRQ: DMA error

  followed by 38 lines of trace information

  
  Note that the kernel reports itself as tainted. This is due to a previous 
kernel warning issued during the boot-up, which I believe to be unrelated - 
kern.log extract (hostname redacted) of warning and taint also attached.

  The laptop reports itself as having the problematic Ricoh devices.
  Relevant hwinfo attached. grepped extract follows

Model: "Ricoh R5C832 IEEE 1394 Controller"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh xD-Picture Card Controller"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh R5C592 Memory Stick Bus Host Adapter"
Vendor: pci 0x1180 "Ricoh Co Ltd"

  Workaround is blacklisting devices by adding the following lines at
  the end of /etc/modprobe.d/blacklist.conf

  # Stop errors filling up log - see
  # https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530187
  # Blacklist Ricoh card reader
  blacklist r592
  blacklist r852

  This stops messages from appearing in /var/log/kern.log and
  /var/log/syslog. The Ricoh cardreader built into the laptop still
  reads SD cards after such blacklisting.

  (lsb_release -rd output is
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  
  graaskaeg

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-33-generic 4.10.0-33.37~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Sep  8 13:30:06 2017
  InstallationDate: Installed on 2017-09-05 (3 days ago)
  InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  pgrb   2220 F pulseaudio
   /dev/snd/controlC1:  pgrb   2220 F pulseaudio
   /dev/snd/controlC0:  pgrb   2220 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=2b7792b7-4eda-4b10-b21c-ad775ff397b3
  InstallationDate: Installed on 2017-09-05 (3 days ago)
  InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 0769BMG
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-33-generic 
root=/dev/mapper/herd-root ro 
cryptdevice=/dev/disk/by-uuid/081dc90a-6dbc-486a-8141-6635c99caca5:mithraeum 
quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.12
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/15/2007
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 68ET24WW
  dmi.board.name: IEL10
  dmi.board.vendor: LENOVO
  dmi.board.version: REFERENCE
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr68ET24WW:bd08/15/2007:svnLENOVO:pn0769BMG:pvr3000N200:rvnLENOVO:rnIEL10:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: 0769BMG
  dmi.product.version: 3000 N200
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

Title:
  r592 & r852 IRQ: DMA errors cause excessive log file entries

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Issue on a newly installed Lubuntu 16.04.3 with 'apt upgrade' freshly
  applied.

   -- /var/log/syslog and /var/log/kern.log grow to 100s of MiB in less
  than a day. --

  Typical excessive syslog entry is attached (hostname redacted). I am
  not making hardware changes at the times these entries are made.
  Entires are of the form:

  Sep  7 20:05:55  kernel: [14098.011547] r592: IRQ: card added
  Sep  7 20:05:55  kernel: [14098.011548] r592: IRQ: DMA error

  followed by 38 lines of trace information

  
  Note that the kernel reports itself as tainted. This is due to a previous 
kernel warning issued during the boot-up, which I believe to be unrelated - 
kern.log extract (hostname redacted) of warning and taint also attached.

  The laptop reports itself as having the problematic Ricoh devices.
  Relevant hwinfo attached. grepped extract follows

Model: "Ricoh R5C832 IEEE 1394 Controller"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh xD-Picture Card Controller"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh R5C592 Memory Stick Bus Host Adapter"
Vendor: pci 0x1180 "Ricoh Co Ltd"

  Workaround is blacklisting devices by adding the following lines at
  the end of /etc/modprobe.d/blacklist.conf

  # Stop errors filling up log - see
  # https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530187
  # Blacklist Ricoh card reader
  blacklist r592
  blacklist r852

  This stops messages from appearing in /var/log/kern.log and
  /var/log/syslog. The Ricoh cardreader built into the laptop still
  reads SD cards after such blacklisting.

  (lsb_release -rd output is
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  
  graaskaeg

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-33-generic 4.10.0-33.37~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Sep  8 13:30:06 2017
  InstallationDate: Installed on 2017-09-05 (3 days ago)
  InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  pgrb   2220 F pulseaudio
   /dev/snd/controlC1:  pgrb   2220 F pulseaudio
   /dev/snd/controlC0:  pgrb   2220 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=2b7792b7-4eda-4b10-b21c-ad775ff397b3
  InstallationDate: Installed on 2017-09-05 (3 days ago)
  InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 0769BMG
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-33-generic 
root=/dev/mapper/herd-root ro 
cryptdevice=/dev/disk/by-uuid/081dc90a-6dbc-486a-8141-6635c99caca5:mithraeum 
quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.12
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/15/2007
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 68ET24WW
  dmi.board.name: IEL10
  dmi.board.vendor: LENOVO
  dmi.board.version: REFERENCE
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr68ET24WW:bd08/15/2007:svnLENOVO:pn0769BMG:pvr3000N200:rvnLENOVO:rnIEL10:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: 0769BMG
  dmi.product.version: 3000 N200
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

Title:
  r592 & r852 IRQ: DMA errors cause excessive log file entries

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Issue on a newly installed Lubuntu 16.04.3 with 'apt upgrade' freshly
  applied.

   -- /var/log/syslog and /var/log/kern.log grow to 100s of MiB in less
  than a day. --

  Typical excessive syslog entry is attached (hostname redacted). I am
  not making hardware changes at the times these entries are made.
  Entires are of the form:

  Sep  7 20:05:55  kernel: [14098.011547] r592: IRQ: card added
  Sep  7 20:05:55  kernel: [14098.011548] r592: IRQ: DMA error

  followed by 38 lines of trace information

  
  Note that the kernel reports itself as tainted. This is due to a previous 
kernel warning issued during the boot-up, which I believe to be unrelated - 
kern.log extract (hostname redacted) of warning and taint also attached.

  The laptop reports itself as having the problematic Ricoh devices.
  Relevant hwinfo attached. grepped extract follows

Model: "Ricoh R5C832 IEEE 1394 Controller"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh xD-Picture Card Controller"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh R5C592 Memory Stick Bus Host Adapter"
Vendor: pci 0x1180 "Ricoh Co Ltd"

  Workaround is blacklisting devices by adding the following lines at
  the end of /etc/modprobe.d/blacklist.conf

  # Stop errors filling up log - see
  # https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530187
  # Blacklist Ricoh card reader
  blacklist r592
  blacklist r852

  This stops messages from appearing in /var/log/kern.log and
  /var/log/syslog. The Ricoh cardreader built into the laptop still
  reads SD cards after such blacklisting.

  (lsb_release -rd output is
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  
  graaskaeg

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-33-generic 4.10.0-33.37~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Sep  8 13:30:06 2017
  InstallationDate: Installed on 2017-09-05 (3 days ago)
  InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  pgrb   2220 F pulseaudio
   /dev/snd/controlC1:  pgrb   2220 F pulseaudio
   /dev/snd/controlC0:  pgrb   2220 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=2b7792b7-4eda-4b10-b21c-ad775ff397b3
  InstallationDate: Installed on 2017-09-05 (3 days ago)
  InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 0769BMG
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-33-generic 
root=/dev/mapper/herd-root ro 
cryptdevice=/dev/disk/by-uuid/081dc90a-6dbc-486a-8141-6635c99caca5:mithraeum 
quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.12
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/15/2007
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 68ET24WW
  dmi.board.name: IEL10
  dmi.board.vendor: LENOVO
  dmi.board.version: REFERENCE
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr68ET24WW:bd08/15/2007:svnLENOVO:pn0769BMG:pvr3000N200:rvnLENOVO:rnIEL10:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: 0769BMG
  dmi.product.version: 3000 N200
  dmi.sys.vendor: LENOVO

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

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

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