[Kernel-packages] [Bug 1767124] Re: bluetoothd crashed with SIGILL in agent_get() from adapter_register()

2018-06-05 Thread Bearsh
any news on this?
is there something I can do to help?

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

Title:
  bluetoothd crashed with SIGILL in agent_get() from adapter_register()

Status in bluez package in Ubuntu:
  New

Bug description:
  systemctl status bluetooth.service 
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: core-dump) since Don 2018-04-26 16:16:36 CEST; 
2min 25s ago
   Docs: man:bluetoothd(8)
Process: 1458 ExecStart=/usr/lib/bluetooth/bluetoothd (code=dumped, 
signal=ILL)
   Main PID: 1458 (code=dumped, signal=ILL)
 Status: "Running"

  Apr 26 16:16:35 tiger systemd[1]: Starting Bluetooth service...
  Apr 26 16:16:35 tiger bluetoothd[1458]: Bluetooth daemon 5.37
  Apr 26 16:16:35 tiger systemd[1]: Started Bluetooth service.
  Apr 26 16:16:35 tiger bluetoothd[1458]: Starting SDP server
  Apr 26 16:16:35 tiger bluetoothd[1458]: Bluetooth management interface 1.14 
initialized
  Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Main process exited, 
code=dumped, status=4/ILL
  Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Unit entered failed 
state.
  Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Failed with result 
'core-dump'.
  Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Start request repeated 
too quickly.
  Apr 26 16:16:36 tiger systemd[1]: Failed to start Bluetooth service.

  sudo gdb /usr/lib/bluetooth/bluetoothd
  ...
  Program received signal SIGILL, Illegal instruction.
  agent_get (owner=owner@entry=0x0) at src/agent.c:267
  267 src/agent.c: Datei oder Verzeichnis nicht gefunden.
  (gdb) bt
  #0  agent_get (owner=owner@entry=0x0) at src/agent.c:267
  #1  0x555d861b in adapter_register (adapter=0x5587fed0) at 
src/adapter.c:7434
  #2  read_info_complete (status=, length=, 
param=, user_data=0x5587fed0) at src/adapter.c:7897
  #3  0x55602656 in request_complete (mgmt=mgmt@entry=0x55879ef0, 
status=, opcode=opcode@entry=4, index=index@entry=0, 
length=length@entry=280, param=0x55879f79) at src/shared/mgmt.c:261
  #4  0x5560311c in can_read_data (io=, 
user_data=0x55879ef0) at src/shared/mgmt.c:353
  #5  0x5560ee25 in watch_callback (channel=, 
cond=, user_data=) at src/shared/io-glib.c:170
  #6  0x77b1004a in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #7  0x77b103f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #8  0x77b10712 in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #9  0x5557009d in main (argc=1, argv=0x7fffe658) at src/main.c:687

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

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


[Kernel-packages] [Bug 1745282] Re: Freezes XPS 13

2018-06-05 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Freezes XPS 13

Status in linux package in Ubuntu:
  Expired

Bug description:
  This kernel boots on the XPS 13 but in less than a minute it hard
  freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ahron  2235 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 24 22:41:26 2018
  InstallationDate: Installed on 2018-01-04 (20 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Dell Inc. XPS 13 9360
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic.efi.signed 
root=UUID=5b8ac06d-8cf5-4417-85d2-df12f2d0dc30 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.0
  dmi.board.name: 0PVG6D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.0:bd12/12/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0PVG6D:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  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/1745282/+subscriptions

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


[Kernel-packages] [Bug 1761619] Re: eventfd / poll interaction bug

2018-06-05 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  eventfd / poll interaction bug

Status in linux package in Ubuntu:
  Expired

Bug description:
  In 17.10, I'm running into a new problem.  This didn't happen to me on
  16.04.

  I have some code that uses eventfds to signal things, and the code is
  not working -- after writing the eventfd, it does not come back
  readable from another thread using poll().

  Here's a snippet from strace:

  ```
  eventfd2(0, 0)  = 5
  fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 1), ...}) = 0
  write(1, "OPEN FD 5\n", 10OPEN FD 5
  ) = 10
  write(5, "\1\0\0\0\0\0\0\0", 8) = 8
  nanosleep({tv_sec=0, tv_nsec=1}, 0x7fffd0cea1a0) = 0
  poll([{fd=5, events=POLLRDNORM}], 1, 100) = 0 (Timeout)
  ```

  The write(1,... ) is debugging output.  The nanosleep was intended to
  see if sleeping a bit before polling would help.  Note that the
  write(5, ...) and the poll() come from different threads.

  Note that using two descriptors from a pipe() (which I do for other
  platforms) is fine, so this is some kind of issue specific to eventfd.

  Also, trying to reproduce this with a simpler single threaded program
  did not succeed.  I'm wondering if there is some underlying cache
  synchronization problem?

  I'm testing this in a VMware Fusion virtual machine (Fusion 10.1.1)
  running on 2017 macbook pro (underlying OS is macOS 10.13).

  For now I'm going to switch back to pipes, since eventfd() seems
  unreliable -- if you can spot anything obviously wrong about the
  system call sequence above, I'd love to hear it.

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

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


[Kernel-packages] [Bug 1761583] Re: Asus 200ha, no keyboard or touchpad support

2018-06-05 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Asus 200ha, no keyboard or touchpad support

Status in linux package in Ubuntu:
  Expired

Bug description:
  17.10.1 - Asus 200ha, keyboard and touchpad not supported, working
  under 16.04.4

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

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


[Kernel-packages] [Bug 1761694] Re: Ubuntu-Server does not launch after kernel update to 4.4.0-116

2018-06-05 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Ubuntu-Server does not launch after kernel update to 4.4.0-116

Status in linux package in Ubuntu:
  Expired

Bug description:
  I am running Ubuntu-Server 14.04.5 LTS in a HyperV-VM with the Xenial
  HWE-Stack enabled. Until the kernel 4.4.0-112 everything ran smoothly,
  but with the kernel update to 4.4.0-116 the system cannot be launched
  and stops during the boot with the following error message:

  Gave up waiting for root device. Common problems:
   - Boot args (cat /proc/cmdline)
    - Check rootdelay= (did the system wait for the right device?)
    - Check root= (did the system wait for the right device?)
   - Missing modules (cat /proc/modules; ls /dev)
  ALERT! /dev/disk/by-uuid/99acf869-911c-47ae-917f-7e82d3c99b8e does not 
exists. Dropping to a shell!

  Also same behaviour with the latest kernel 4.4.0-119.

  I already tried to boot with the rootdelay=10 argument but this has no 
effect. 
  If you need further informations please tell me. Thanks for your support.

  Best regards
  Falk

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

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


[Kernel-packages] [Bug 1775326] Re: The kernel NULL pointer dereference happens when accessing the task_struct by task_cpu() in function cpuacct_charge()

2018-06-05 Thread Gavin Guo
** Summary changed:

- The kernel NULL pointer dereference happens when accessing the task by 
task_cpu() in function cpuacct_charge()
+ The kernel NULL pointer dereference happens when accessing the task_struct by 
task_cpu() in function cpuacct_charge()

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

Title:
  The kernel NULL pointer dereference happens when accessing the
  task_struct by task_cpu() in function cpuacct_charge()

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]

  In function cpuacct_charge(), the NULL pointer dereference happens
  with the stack pointer being zero inside the task_struct when the
  task_cpu() is trying to access the member CPU of the struct
  thread_info inside the stack. It's a use-after-free corruption
  happening in the situation that the task_struct is released almost
  concurrently before accessing the task_struct->stack.

  void cpuacct_charge(struct task_struct *tsk, u64 cputime)
   {
  struct cpuacct *ca;
  int cpu;
   
  cpu = task_cpu(tsk);
   
  rcu_read_lock();
   
  ca = task_ca(tsk);
   
  while (true) {
  u64 *cpuusage = per_cpu_ptr(ca->cpuusage, cpu);
  *cpuusage += cputime;
   
  ca = parent_ca(ca);
  if (!ca)
  break;
  }

rcu_read_unlock();
  }

  
  BUG: unable to handle kernel NULL pointer dereference at 0010
  IP: [] cpuacct_charge+0x14/0x40
  PGD 0 
  Oops:  [#1] SMP  
  CPU: 10 PID: 148614 Comm: qemu-system-x86 Tainted: PW  OE   
4.4.0-45-generic #66~14.04.1-Ubuntu
  Hardware name: Dell Inc. PowerEdge R630/02C2CP, BIOS 2.1.7 06/16/2016
  task: 881ff0f01b80 ti: 88018fd7 task.ti: 88018fd7
  RIP: 0010:[]  [] cpuacct_charge+0x14/0x40
  RSP: 0018:88018fd73d10  EFLAGS: 00010246
  RAX:  RBX: 8801931e8000 RCX: 88010caff200
  RDX: 880124508000 RSI: 0066f757398831d6 RDI: 8801931e7fa0
  RBP: 88018fd73d10 R08: c04b8320 R09: 0001
  R10: 0001 R11:  R12: 0066f757398831d6
  R13: 0066f757398b8997 R14: 8801931e7fa0 R15: 0001
  FS:  7f162aaf7700() GS:881ffe74() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 0010 CR3: 00011d86e000 CR4: 003426e0
  DR0:  DR1:  DR2: 
  DR3:  DR6: fffe0ff0 DR7: 0400
  Stack:
   88018fd73d28 810b1a9f 8801931e8000 88018fd73d40
   c069df72 8801931e8000 88018fd73da8 c069f121
   881ff0f01b80  881ff0f01b80 810bddc0
  Call Trace:
   [] update_curr+0xdf/0x170
   [] kvm_vcpu_check_block+0x12/0x60 [kvm]
   [] kvm_vcpu_block+0x191/0x2d0 [kvm]
   [] ? prepare_to_wait_event+0xf0/0xf0
   [] kvm_arch_vcpu_ioctl_run+0x17e/0x3d0 [kvm]
   [] kvm_vcpu_ioctl+0x2ab/0x640 [kvm]
   [] ? perf_event_context_sched_in+0x87/0xa0
   [] do_vfs_ioctl+0x2dd/0x4c0
   [] ? __audit_syscall_entry+0xaf/0x100
   [] ? do_audit_syscall_entry+0x66/0x70
   [] SyS_ioctl+0x79/0x90
   [] entry_SYSCALL_64_fastpath+0x16/0x75
  Code: 9a 11 00 5b 48 c7 c0 f4 ff ff ff 5d eb df 66 0f 1f 84 00 00 00 00 00 0f 
1f 44 00 00 55 48 8b 47 08 48 8b 97 78 07 00 00 48 89 e5 <48> 63 48 10 48 8b 52 
60 48 8b 82 b8 00 00 00 48 03 04 cd c0 7a
  RIP  [] cpuacct_charge+0x14/0x40
   RSP 
  CR2: 0010
  ---[ end trace 419a30375d0e4622 ]---


  [Fix]

  The patch uses this_cpu_ptr() instead of getting the CPU number by 
  task_cpu() and proceeds to get the cpu_usage by per_cpu_ptr(). And
  that can avoid accessing the thread_info inside the stack. 

  commit 73e6aafd9ea81498d31361f01db84a0118da2d1c
  Author: Zhao Lei 
  Date:   Thu Mar 17 12:19:43 2016 +0800

  sched/cpuacct: Simplify the cpuacct code
  
   - Use for() instead of while() loop in some functions
 to make the code simpler.
  
   - Use this_cpu_ptr() instead of per_cpu_ptr() to make the code
 cleaner and a bit faster.
  
  Suggested-by: Peter Zijlstra 
  Signed-off-by: Zhao Lei 
  Signed-off-by: Peter Zijlstra (Intel) 
  Cc: Linus Torvalds 
  Cc: Tejun Heo 
  Cc: Thomas Gleixner 
  Link: 
http://lkml.kernel.org/r/d8a7ef9592f55224630cb26dea239f05b6398a4e.1458187654.git.zhao...@cn.fujitsu.com
  Signed-off-by: Ingo Molnar 


  [Test]
  The test kernel has been tested by the Qemu and cannot be reproduced.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775326/+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 1775316] Re: add_key04 in LTP syscall test cause kernel oops (NULL pointer dereference) with T kernel

2018-06-05 Thread Po-Hsu Lin
This seems to be related to CVE-2017-12193

A test kernel with the fix (ea678998) could be found here:
http://people.canonical.com/~phlin/kernel/lp-1775316/

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

Title:
  add_key04 in LTP syscall test cause kernel oops (NULL pointer
  dereference) with T kernel

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

Bug description:
  The "add_key04" from the LTP syscall tests will cause kernel oops on a
  testing node with Trusty kernel installed. And it will make incoming
  ssh connection hang (bug 1775158)

  Steps (with root):
1. sudo apt-get install git xfsprogs -y
2. git clone --depth=1 https://github.com/linux-test-project/ltp.git
3. cd ltp
4. make autotools
5. ./configure
6. make; make install
7. cd /opt/ltp/testcases/bin
8. ./add_key04

  Test result:
  ubuntu@amaura:/opt/ltp/testcases/bin$ sudo ./add_key04
  tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s
  add_key04.c:82: FAIL: kernel oops while filling keyring

  Summary:
  passed   0
  failed   1
  skipped  0
  warnings 0

  [52399.298894] BUG: unable to handle kernel NULL pointer dereference at 
0010
  [52399.298918] IP: [] assoc_array_apply_edit+0x67/0x110
  [52399.298938] PGD 800455a3a067 PUD 45725f067 PMD 0 
  [52399.298952] Oops: 0002 [#1] SMP 
  [52399.298963] Modules linked in: cfg80211 ib_iser rdma_cm iw_cm ib_cm ib_sa 
ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
dm_crypt joydev hid_generic x86_pkg_temp_thermal coretemp kvm_intel kvm usbhid 
hid lpc_ich shpchp mac_hid crct10dif_pclmul crc32_pclmul i915_bdw 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
igb cryptd ahci dca ptp libahci pps_core intel_ips i2c_algo_bit drm_kms_helper 
video drm
  [52399.299100] CPU: 7 PID: 9559 Comm: add_key04 Not tainted 
3.13.0-149-generic #199-Ubuntu
  [52399.299118] Hardware name: Intel Corporation S1200RP/S1200RP, BIOS 
S1200RP.86B.03.02.0003.070120151022 07/01/2015
  [52399.299142] task: 880457b43000 ti: 88045a2e2000 task.ti: 
88045a2e2000
  [52399.299159] RIP: 0010:[]  [] 
assoc_array_apply_edit+0x67/0x110
  [52399.299182] RSP: 0018:88045a2e3df0  EFLAGS: 00010202
  [52399.299194] RAX: 0010 RBX: 88045a2e3e78 RCX: 

  [52399.299211] RDX: 88045a1d1741 RSI: 880456028880 RDI: 
880456028800
  [52399.299228] RBP: 88045a2e3df0 R08: 00016880 R09: 
812dba97
  [52399.299244] R10: 880460803c00 R11: ddf32900 R12: 
880456f7f680
  [52399.299261] R13: 88045a1d09c0 R14:  R15: 

  [52399.299278] FS:  7ff43fc39740() GS:8804704e() 
knlGS:
  [52399.299297] CS:  0010 DS:  ES:  CR0: 80050033
  [52399.299311] CR2: 0010 CR3: 00045514c000 CR4: 
00360770
  [52399.299328] DR0:  DR1:  DR2: 

  [52399.299344] DR3:  DR6: fffe0ff0 DR7: 
0400
  [52399.299361] Stack:
  [52399.299366]  88045a2e3e08 812d7a33  
88045a2e3e50
  [52399.299387]  812d57a7 88045a1d0a30 88045a2e3e78 
880456f7f681
  [52399.299407]  3f01 880456f7f380 88045a1d09c0 
880457b43000
  [52399.299427] Call Trace:
  [52399.299436]  [] __key_link+0x33/0x40
  [52399.299450]  [] __key_instantiate_and_link+0x87/0xf0
  [52399.299467]  [] key_create_or_update+0x32e/0x420
  [52399.299482]  [] SyS_add_key+0x110/0x210
  [52399.299497]  [] ? schedule_tail+0x5c/0xb0
  [52399.299512]  [] system_call_fastpath+0x1a/0x1f
  [52399.299526] Code: 48 85 d2 74 0a 48 8b 8f e8 00 00 00 48 89 0a 48 83 c0 08 
48 39 f0 75 e4 48 8b 87 00 01 00 00 48 85 c0 74 0a 48 8b 97 08 01 00 00 <48> 89 
10 48 8b 87 10 01 00 00 48 85 c0 74 0a 48 8b 97 18 01 00 
  [52399.299625] RIP  [] assoc_array_apply_edit+0x67/0x110
  [52399.299642]  RSP 
  [52399.299650] CR2: 0010
  [52399.302015] ---[ end trace 0f3e00901ea9f056 ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-149-generic 3.13.0-149.199
  ProcVersionSignature: User Name 3.13.0-149.199-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-149-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun  5 12:22 seq
   crw-rw 1 root audio 116, 33 Jun  5 12:22 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg: [3.475549] init: plymouth-upstart-bridge main process 
ended, respawning
  Date: 

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

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

apport-collect 1775326

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

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

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

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

** Tags added: xenial

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

Title:
  The kernel NULL pointer dereference happens when accessing the
  task_struct by task_cpu() in function cpuacct_charge()

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]

  In function cpuacct_charge(), the NULL pointer dereference happens
  with the stack pointer being zero inside the task_struct when the
  task_cpu() is trying to access the member CPU of the struct
  thread_info inside the stack. It's a use-after-free corruption
  happening in the situation that the task_struct is released almost
  concurrently before accessing the task_struct->stack.

  void cpuacct_charge(struct task_struct *tsk, u64 cputime)
   {
  struct cpuacct *ca;
  int cpu;
   
  cpu = task_cpu(tsk);
   
  rcu_read_lock();
   
  ca = task_ca(tsk);
   
  while (true) {
  u64 *cpuusage = per_cpu_ptr(ca->cpuusage, cpu);
  *cpuusage += cputime;
   
  ca = parent_ca(ca);
  if (!ca)
  break;
  }

rcu_read_unlock();
  }

  
  BUG: unable to handle kernel NULL pointer dereference at 0010
  IP: [] cpuacct_charge+0x14/0x40
  PGD 0 
  Oops:  [#1] SMP  
  CPU: 10 PID: 148614 Comm: qemu-system-x86 Tainted: PW  OE   
4.4.0-45-generic #66~14.04.1-Ubuntu
  Hardware name: Dell Inc. PowerEdge R630/02C2CP, BIOS 2.1.7 06/16/2016
  task: 881ff0f01b80 ti: 88018fd7 task.ti: 88018fd7
  RIP: 0010:[]  [] cpuacct_charge+0x14/0x40
  RSP: 0018:88018fd73d10  EFLAGS: 00010246
  RAX:  RBX: 8801931e8000 RCX: 88010caff200
  RDX: 880124508000 RSI: 0066f757398831d6 RDI: 8801931e7fa0
  RBP: 88018fd73d10 R08: c04b8320 R09: 0001
  R10: 0001 R11:  R12: 0066f757398831d6
  R13: 0066f757398b8997 R14: 8801931e7fa0 R15: 0001
  FS:  7f162aaf7700() GS:881ffe74() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 0010 CR3: 00011d86e000 CR4: 003426e0
  DR0:  DR1:  DR2: 
  DR3:  DR6: fffe0ff0 DR7: 0400
  Stack:
   88018fd73d28 810b1a9f 8801931e8000 88018fd73d40
   c069df72 8801931e8000 88018fd73da8 c069f121
   881ff0f01b80  881ff0f01b80 810bddc0
  Call Trace:
   [] update_curr+0xdf/0x170
   [] kvm_vcpu_check_block+0x12/0x60 [kvm]
   [] kvm_vcpu_block+0x191/0x2d0 [kvm]
   [] ? prepare_to_wait_event+0xf0/0xf0
   [] kvm_arch_vcpu_ioctl_run+0x17e/0x3d0 [kvm]
   [] kvm_vcpu_ioctl+0x2ab/0x640 [kvm]
   [] ? perf_event_context_sched_in+0x87/0xa0
   [] do_vfs_ioctl+0x2dd/0x4c0
   [] ? __audit_syscall_entry+0xaf/0x100
   [] ? do_audit_syscall_entry+0x66/0x70
   [] SyS_ioctl+0x79/0x90
   [] entry_SYSCALL_64_fastpath+0x16/0x75
  Code: 9a 11 00 5b 48 c7 c0 f4 ff ff ff 5d eb df 66 0f 1f 84 00 00 00 00 00 0f 
1f 44 00 00 55 48 8b 47 08 48 8b 97 78 07 00 00 48 89 e5 <48> 63 48 10 48 8b 52 
60 48 8b 82 b8 00 00 00 48 03 04 cd c0 7a
  RIP  [] cpuacct_charge+0x14/0x40
   RSP 
  CR2: 0010
  ---[ end trace 419a30375d0e4622 ]---


  [Fix]

  The patch uses this_cpu_ptr() instead of getting the CPU number by 
  task_cpu() and proceeds to get the cpu_usage by per_cpu_ptr(). And
  that can avoid accessing the thread_info inside the stack. 

  commit 73e6aafd9ea81498d31361f01db84a0118da2d1c
  Author: Zhao Lei 
  Date:   Thu Mar 17 12:19:43 2016 +0800

  sched/cpuacct: Simplify the cpuacct code
  
   - Use for() instead of while() loop in some functions
 to make the code simpler.
  
   - Use this_cpu_ptr() instead of per_cpu_ptr() to make the code
 cleaner and a bit faster.
  
  Suggested-by: Peter Zijlstra 
  Signed-off-by: Zhao Lei 
  Signed-off-by: Peter Zijlstra (Intel) 
  Cc: Linus Torvalds 
  Cc: Tejun Heo 
  Cc: Thomas Gleixner 
  Link: 
http://lkml.kernel.org/r/d8a7ef9592f55224630cb26dea239f05b6398a4e.1458187654.git.zhao...@cn.fujitsu.com
  Signed-off-by: Ingo Molnar 


  

[Kernel-packages] [Bug 1775326] [NEW] The kernel NULL pointer dereference happens when accessing the task_struct by task_cpu() in function cpuacct_charge()

2018-06-05 Thread Gavin Guo
Public bug reported:

[Impact]

In function cpuacct_charge(), the NULL pointer dereference happens
with the stack pointer being zero inside the task_struct when the
task_cpu() is trying to access the member CPU of the struct
thread_info inside the stack. It's a use-after-free corruption
happening in the situation that the task_struct is released almost
concurrently before accessing the task_struct->stack.

void cpuacct_charge(struct task_struct *tsk, u64 cputime)
 {
struct cpuacct *ca;
int cpu;
 
cpu = task_cpu(tsk);
 
rcu_read_lock();
 
ca = task_ca(tsk);
 
while (true) {
u64 *cpuusage = per_cpu_ptr(ca->cpuusage, cpu);
*cpuusage += cputime;
 
ca = parent_ca(ca);
if (!ca)
break;
}

rcu_read_unlock();
}


BUG: unable to handle kernel NULL pointer dereference at 0010
IP: [] cpuacct_charge+0x14/0x40
PGD 0 
Oops:  [#1] SMP  
CPU: 10 PID: 148614 Comm: qemu-system-x86 Tainted: PW  OE   
4.4.0-45-generic #66~14.04.1-Ubuntu
Hardware name: Dell Inc. PowerEdge R630/02C2CP, BIOS 2.1.7 06/16/2016
task: 881ff0f01b80 ti: 88018fd7 task.ti: 88018fd7
RIP: 0010:[]  [] cpuacct_charge+0x14/0x40
RSP: 0018:88018fd73d10  EFLAGS: 00010246
RAX:  RBX: 8801931e8000 RCX: 88010caff200
RDX: 880124508000 RSI: 0066f757398831d6 RDI: 8801931e7fa0
RBP: 88018fd73d10 R08: c04b8320 R09: 0001
R10: 0001 R11:  R12: 0066f757398831d6
R13: 0066f757398b8997 R14: 8801931e7fa0 R15: 0001
FS:  7f162aaf7700() GS:881ffe74() knlGS:
CS:  0010 DS:  ES:  CR0: 80050033
CR2: 0010 CR3: 00011d86e000 CR4: 003426e0
DR0:  DR1:  DR2: 
DR3:  DR6: fffe0ff0 DR7: 0400
Stack:
 88018fd73d28 810b1a9f 8801931e8000 88018fd73d40
 c069df72 8801931e8000 88018fd73da8 c069f121
 881ff0f01b80  881ff0f01b80 810bddc0
Call Trace:
 [] update_curr+0xdf/0x170
 [] kvm_vcpu_check_block+0x12/0x60 [kvm]
 [] kvm_vcpu_block+0x191/0x2d0 [kvm]
 [] ? prepare_to_wait_event+0xf0/0xf0
 [] kvm_arch_vcpu_ioctl_run+0x17e/0x3d0 [kvm]
 [] kvm_vcpu_ioctl+0x2ab/0x640 [kvm]
 [] ? perf_event_context_sched_in+0x87/0xa0
 [] do_vfs_ioctl+0x2dd/0x4c0
 [] ? __audit_syscall_entry+0xaf/0x100
 [] ? do_audit_syscall_entry+0x66/0x70
 [] SyS_ioctl+0x79/0x90
 [] entry_SYSCALL_64_fastpath+0x16/0x75
Code: 9a 11 00 5b 48 c7 c0 f4 ff ff ff 5d eb df 66 0f 1f 84 00 00 00 00 00 0f 
1f 44 00 00 55 48 8b 47 08 48 8b 97 78 07 00 00 48 89 e5 <48> 63 48 10 48 8b 52 
60 48 8b 82 b8 00 00 00 48 03 04 cd c0 7a
RIP  [] cpuacct_charge+0x14/0x40
 RSP 
CR2: 0010
---[ end trace 419a30375d0e4622 ]---


[Fix]

The patch uses this_cpu_ptr() instead of getting the CPU number by 
task_cpu() and proceeds to get the cpu_usage by per_cpu_ptr(). And
that can avoid accessing the thread_info inside the stack. 

commit 73e6aafd9ea81498d31361f01db84a0118da2d1c
Author: Zhao Lei 
Date:   Thu Mar 17 12:19:43 2016 +0800

sched/cpuacct: Simplify the cpuacct code

 - Use for() instead of while() loop in some functions
   to make the code simpler.

 - Use this_cpu_ptr() instead of per_cpu_ptr() to make the code
   cleaner and a bit faster.

Suggested-by: Peter Zijlstra 
Signed-off-by: Zhao Lei 
Signed-off-by: Peter Zijlstra (Intel) 
Cc: Linus Torvalds 
Cc: Tejun Heo 
Cc: Thomas Gleixner 
Link: 
http://lkml.kernel.org/r/d8a7ef9592f55224630cb26dea239f05b6398a4e.1458187654.git.zhao...@cn.fujitsu.com
Signed-off-by: Ingo Molnar 


[Test]
The test kernel has been tested by the Qemu and cannot be reproduced.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Gavin Guo (mimi0213kimo)
 Status: Incomplete


** Tags: sts 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/1775326

Title:
  The kernel NULL pointer dereference happens when accessing the
  task_struct by task_cpu() in function cpuacct_charge()

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]

  In function cpuacct_charge(), the NULL pointer dereference happens
  with the stack pointer being zero inside the task_struct when the
  task_cpu() is trying to access the member CPU of the struct
  thread_info inside the stack. It's a use-after-free corruption
  happening in the situation that the task_struct is released almost
  concurrently before accessing the task_struct->stack.

  void cpuacct_charge(struct task_struct *tsk, u64 cputime)
   {
  struct cpuacct *ca;
  int cpu;
   
  cpu = task_cpu(tsk);
   
  

[Kernel-packages] [Bug 1775316] Re: add_key04 in LTP syscall test cause kernel oops (NULL pointer dereference) with T kernel

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

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

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

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

Title:
  add_key04 in LTP syscall test cause kernel oops (NULL pointer
  dereference) with T kernel

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

Bug description:
  The "add_key04" from the LTP syscall tests will cause kernel oops on a
  testing node with Trusty kernel installed. And it will make incoming
  ssh connection hang (bug 1775158)

  Steps (with root):
1. sudo apt-get install git xfsprogs -y
2. git clone --depth=1 https://github.com/linux-test-project/ltp.git
3. cd ltp
4. make autotools
5. ./configure
6. make; make install
7. cd /opt/ltp/testcases/bin
8. ./add_key04

  Test result:
  ubuntu@amaura:/opt/ltp/testcases/bin$ sudo ./add_key04
  tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s
  add_key04.c:82: FAIL: kernel oops while filling keyring

  Summary:
  passed   0
  failed   1
  skipped  0
  warnings 0

  [52399.298894] BUG: unable to handle kernel NULL pointer dereference at 
0010
  [52399.298918] IP: [] assoc_array_apply_edit+0x67/0x110
  [52399.298938] PGD 800455a3a067 PUD 45725f067 PMD 0 
  [52399.298952] Oops: 0002 [#1] SMP 
  [52399.298963] Modules linked in: cfg80211 ib_iser rdma_cm iw_cm ib_cm ib_sa 
ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
dm_crypt joydev hid_generic x86_pkg_temp_thermal coretemp kvm_intel kvm usbhid 
hid lpc_ich shpchp mac_hid crct10dif_pclmul crc32_pclmul i915_bdw 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
igb cryptd ahci dca ptp libahci pps_core intel_ips i2c_algo_bit drm_kms_helper 
video drm
  [52399.299100] CPU: 7 PID: 9559 Comm: add_key04 Not tainted 
3.13.0-149-generic #199-Ubuntu
  [52399.299118] Hardware name: Intel Corporation S1200RP/S1200RP, BIOS 
S1200RP.86B.03.02.0003.070120151022 07/01/2015
  [52399.299142] task: 880457b43000 ti: 88045a2e2000 task.ti: 
88045a2e2000
  [52399.299159] RIP: 0010:[]  [] 
assoc_array_apply_edit+0x67/0x110
  [52399.299182] RSP: 0018:88045a2e3df0  EFLAGS: 00010202
  [52399.299194] RAX: 0010 RBX: 88045a2e3e78 RCX: 

  [52399.299211] RDX: 88045a1d1741 RSI: 880456028880 RDI: 
880456028800
  [52399.299228] RBP: 88045a2e3df0 R08: 00016880 R09: 
812dba97
  [52399.299244] R10: 880460803c00 R11: ddf32900 R12: 
880456f7f680
  [52399.299261] R13: 88045a1d09c0 R14:  R15: 

  [52399.299278] FS:  7ff43fc39740() GS:8804704e() 
knlGS:
  [52399.299297] CS:  0010 DS:  ES:  CR0: 80050033
  [52399.299311] CR2: 0010 CR3: 00045514c000 CR4: 
00360770
  [52399.299328] DR0:  DR1:  DR2: 

  [52399.299344] DR3:  DR6: fffe0ff0 DR7: 
0400
  [52399.299361] Stack:
  [52399.299366]  88045a2e3e08 812d7a33  
88045a2e3e50
  [52399.299387]  812d57a7 88045a1d0a30 88045a2e3e78 
880456f7f681
  [52399.299407]  3f01 880456f7f380 88045a1d09c0 
880457b43000
  [52399.299427] Call Trace:
  [52399.299436]  [] __key_link+0x33/0x40
  [52399.299450]  [] __key_instantiate_and_link+0x87/0xf0
  [52399.299467]  [] key_create_or_update+0x32e/0x420
  [52399.299482]  [] SyS_add_key+0x110/0x210
  [52399.299497]  [] ? schedule_tail+0x5c/0xb0
  [52399.299512]  [] system_call_fastpath+0x1a/0x1f
  [52399.299526] Code: 48 85 d2 74 0a 48 8b 8f e8 00 00 00 48 89 0a 48 83 c0 08 
48 39 f0 75 e4 48 8b 87 00 01 00 00 48 85 c0 74 0a 48 8b 97 08 01 00 00 <48> 89 
10 48 8b 87 10 01 00 00 48 85 c0 74 0a 48 8b 97 18 01 00 
  [52399.299625] RIP  [] assoc_array_apply_edit+0x67/0x110
  [52399.299642]  RSP 
  [52399.299650] CR2: 0010
  [52399.302015] ---[ end trace 0f3e00901ea9f056 ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-149-generic 3.13.0-149.199
  ProcVersionSignature: User Name 3.13.0-149.199-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-149-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun  5 12:22 seq
   crw-rw 1 root audio 116, 33 Jun  5 12:22 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg: [

[Kernel-packages] [Bug 1775316] Re: add_key04 in LTP syscall test cause kernel oops (NULL pointer dereference) with T kernel

2018-06-05 Thread Po-Hsu Lin
** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

** No longer affects: ubuntu-kernel-tests

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

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-12193

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

Title:
  add_key04 in LTP syscall test cause kernel oops (NULL pointer
  dereference) with T kernel

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

Bug description:
  The "add_key04" from the LTP syscall tests will cause kernel oops on a
  testing node with Trusty kernel installed. And it will make incoming
  ssh connection hang (bug 1775158)

  Steps (with root):
1. sudo apt-get install git xfsprogs -y
2. git clone --depth=1 https://github.com/linux-test-project/ltp.git
3. cd ltp
4. make autotools
5. ./configure
6. make; make install
7. cd /opt/ltp/testcases/bin
8. ./add_key04

  Test result:
  ubuntu@amaura:/opt/ltp/testcases/bin$ sudo ./add_key04
  tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s
  add_key04.c:82: FAIL: kernel oops while filling keyring

  Summary:
  passed   0
  failed   1
  skipped  0
  warnings 0

  [52399.298894] BUG: unable to handle kernel NULL pointer dereference at 
0010
  [52399.298918] IP: [] assoc_array_apply_edit+0x67/0x110
  [52399.298938] PGD 800455a3a067 PUD 45725f067 PMD 0 
  [52399.298952] Oops: 0002 [#1] SMP 
  [52399.298963] Modules linked in: cfg80211 ib_iser rdma_cm iw_cm ib_cm ib_sa 
ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
dm_crypt joydev hid_generic x86_pkg_temp_thermal coretemp kvm_intel kvm usbhid 
hid lpc_ich shpchp mac_hid crct10dif_pclmul crc32_pclmul i915_bdw 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
igb cryptd ahci dca ptp libahci pps_core intel_ips i2c_algo_bit drm_kms_helper 
video drm
  [52399.299100] CPU: 7 PID: 9559 Comm: add_key04 Not tainted 
3.13.0-149-generic #199-Ubuntu
  [52399.299118] Hardware name: Intel Corporation S1200RP/S1200RP, BIOS 
S1200RP.86B.03.02.0003.070120151022 07/01/2015
  [52399.299142] task: 880457b43000 ti: 88045a2e2000 task.ti: 
88045a2e2000
  [52399.299159] RIP: 0010:[]  [] 
assoc_array_apply_edit+0x67/0x110
  [52399.299182] RSP: 0018:88045a2e3df0  EFLAGS: 00010202
  [52399.299194] RAX: 0010 RBX: 88045a2e3e78 RCX: 

  [52399.299211] RDX: 88045a1d1741 RSI: 880456028880 RDI: 
880456028800
  [52399.299228] RBP: 88045a2e3df0 R08: 00016880 R09: 
812dba97
  [52399.299244] R10: 880460803c00 R11: ddf32900 R12: 
880456f7f680
  [52399.299261] R13: 88045a1d09c0 R14:  R15: 

  [52399.299278] FS:  7ff43fc39740() GS:8804704e() 
knlGS:
  [52399.299297] CS:  0010 DS:  ES:  CR0: 80050033
  [52399.299311] CR2: 0010 CR3: 00045514c000 CR4: 
00360770
  [52399.299328] DR0:  DR1:  DR2: 

  [52399.299344] DR3:  DR6: fffe0ff0 DR7: 
0400
  [52399.299361] Stack:
  [52399.299366]  88045a2e3e08 812d7a33  
88045a2e3e50
  [52399.299387]  812d57a7 88045a1d0a30 88045a2e3e78 
880456f7f681
  [52399.299407]  3f01 880456f7f380 88045a1d09c0 
880457b43000
  [52399.299427] Call Trace:
  [52399.299436]  [] __key_link+0x33/0x40
  [52399.299450]  [] __key_instantiate_and_link+0x87/0xf0
  [52399.299467]  [] key_create_or_update+0x32e/0x420
  [52399.299482]  [] SyS_add_key+0x110/0x210
  [52399.299497]  [] ? schedule_tail+0x5c/0xb0
  [52399.299512]  [] system_call_fastpath+0x1a/0x1f
  [52399.299526] Code: 48 85 d2 74 0a 48 8b 8f e8 00 00 00 48 89 0a 48 83 c0 08 
48 39 f0 75 e4 48 8b 87 00 01 00 00 48 85 c0 74 0a 48 8b 97 08 01 00 00 <48> 89 
10 48 8b 87 10 01 00 00 48 85 c0 74 0a 48 8b 97 18 01 00 
  [52399.299625] RIP  [] assoc_array_apply_edit+0x67/0x110
  [52399.299642]  RSP 
  [52399.299650] CR2: 0010
  [52399.302015] ---[ end trace 0f3e00901ea9f056 ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-149-generic 3.13.0-149.199
  ProcVersionSignature: User Name 3.13.0-149.199-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-149-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun  5 12:22 seq
   crw-rw 1 root audio 116, 33 Jun  5 12:22 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  

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

2018-06-05 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  add_key04 in LTP syscall test cause kernel oops (NULL pointer
  dereference) with T kernel

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

Bug description:
  The "add_key04" from the LTP syscall tests will cause kernel oops on a
  testing node with Trusty kernel installed. And it will make incoming
  ssh connection hang (bug 1775158)

  Steps (with root):
1. sudo apt-get install git xfsprogs -y
2. git clone --depth=1 https://github.com/linux-test-project/ltp.git
3. cd ltp
4. make autotools
5. ./configure
6. make; make install
7. cd /opt/ltp/testcases/bin
8. ./add_key04

  Test result:
  ubuntu@amaura:/opt/ltp/testcases/bin$ sudo ./add_key04
  tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s
  add_key04.c:82: FAIL: kernel oops while filling keyring

  Summary:
  passed   0
  failed   1
  skipped  0
  warnings 0

  [52399.298894] BUG: unable to handle kernel NULL pointer dereference at 
0010
  [52399.298918] IP: [] assoc_array_apply_edit+0x67/0x110
  [52399.298938] PGD 800455a3a067 PUD 45725f067 PMD 0 
  [52399.298952] Oops: 0002 [#1] SMP 
  [52399.298963] Modules linked in: cfg80211 ib_iser rdma_cm iw_cm ib_cm ib_sa 
ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
dm_crypt joydev hid_generic x86_pkg_temp_thermal coretemp kvm_intel kvm usbhid 
hid lpc_ich shpchp mac_hid crct10dif_pclmul crc32_pclmul i915_bdw 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
igb cryptd ahci dca ptp libahci pps_core intel_ips i2c_algo_bit drm_kms_helper 
video drm
  [52399.299100] CPU: 7 PID: 9559 Comm: add_key04 Not tainted 
3.13.0-149-generic #199-Ubuntu
  [52399.299118] Hardware name: Intel Corporation S1200RP/S1200RP, BIOS 
S1200RP.86B.03.02.0003.070120151022 07/01/2015
  [52399.299142] task: 880457b43000 ti: 88045a2e2000 task.ti: 
88045a2e2000
  [52399.299159] RIP: 0010:[]  [] 
assoc_array_apply_edit+0x67/0x110
  [52399.299182] RSP: 0018:88045a2e3df0  EFLAGS: 00010202
  [52399.299194] RAX: 0010 RBX: 88045a2e3e78 RCX: 

  [52399.299211] RDX: 88045a1d1741 RSI: 880456028880 RDI: 
880456028800
  [52399.299228] RBP: 88045a2e3df0 R08: 00016880 R09: 
812dba97
  [52399.299244] R10: 880460803c00 R11: ddf32900 R12: 
880456f7f680
  [52399.299261] R13: 88045a1d09c0 R14:  R15: 

  [52399.299278] FS:  7ff43fc39740() GS:8804704e() 
knlGS:
  [52399.299297] CS:  0010 DS:  ES:  CR0: 80050033
  [52399.299311] CR2: 0010 CR3: 00045514c000 CR4: 
00360770
  [52399.299328] DR0:  DR1:  DR2: 

  [52399.299344] DR3:  DR6: fffe0ff0 DR7: 
0400
  [52399.299361] Stack:
  [52399.299366]  88045a2e3e08 812d7a33  
88045a2e3e50
  [52399.299387]  812d57a7 88045a1d0a30 88045a2e3e78 
880456f7f681
  [52399.299407]  3f01 880456f7f380 88045a1d09c0 
880457b43000
  [52399.299427] Call Trace:
  [52399.299436]  [] __key_link+0x33/0x40
  [52399.299450]  [] __key_instantiate_and_link+0x87/0xf0
  [52399.299467]  [] key_create_or_update+0x32e/0x420
  [52399.299482]  [] SyS_add_key+0x110/0x210
  [52399.299497]  [] ? schedule_tail+0x5c/0xb0
  [52399.299512]  [] system_call_fastpath+0x1a/0x1f
  [52399.299526] Code: 48 85 d2 74 0a 48 8b 8f e8 00 00 00 48 89 0a 48 83 c0 08 
48 39 f0 75 e4 48 8b 87 00 01 00 00 48 85 c0 74 0a 48 8b 97 08 01 00 00 <48> 89 
10 48 8b 87 10 01 00 00 48 85 c0 74 0a 48 8b 97 18 01 00 
  [52399.299625] RIP  [] assoc_array_apply_edit+0x67/0x110
  [52399.299642]  RSP 
  [52399.299650] CR2: 0010
  [52399.302015] ---[ end trace 0f3e00901ea9f056 ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-149-generic 3.13.0-149.199
  ProcVersionSignature: User Name 3.13.0-149.199-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-149-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun  5 12:22 seq
   crw-rw 1 root audio 116, 33 Jun  5 12:22 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg: [3.475549] init: plymouth-upstart-bridge main process 
ended, respawning
  Date: Wed Jun  6 02:54:24 2018
  IwConfig: Error: [Errno 2] No such file or 

[Kernel-packages] [Bug 1775153] Re: fanotify09 in LTP syscall test failed with A/T kernel

2018-06-05 Thread Po-Hsu Lin
** Description changed:

  The "fanotify09" from the LTP syscall tests has failed on a testing node
- with Xenial kernel installed.
+ with A/T kernel installed.
  
  Steps (with root):
-   1. sudo apt-get install git xfsprogs -y
-   2. git clone --depth=1 https://github.com/linux-test-project/ltp.git
-   3. cd ltp
-   4. make autotools
-   5. ./configure
-   6. make; make install
-   7. cd /opt/ltp
-   8. echo "fanotify09" > /tmp/jobs
-   9. ./runltp -f /tmp/jobs
+   1. sudo apt-get install git xfsprogs -y
+   2. git clone --depth=1 https://github.com/linux-test-project/ltp.git
+   3. cd ltp
+   4. make autotools
+   5. ./configure
+   6. make; make install
+   7. cd /opt/ltp
+   8. echo "fanotify09" > /tmp/jobs
+   9. ./runltp -f /tmp/jobs
  
  <<>>
  tag=fanotify09 stime=1528192114
  cmdline="fanotify09"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s
  fanotify09.c:134: PASS: group 0 get event: mask 2 pid=43803 fd=9
  fanotify09.c:182: FAIL: group 1 got event
  fanotify09.c:182: FAIL: group 2 got event
  
  Summary:
  passed   1
  failed   2
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=0
  <<>>
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-43-generic 4.13.0-43.48
  ProcVersionSignature: User Name 4.13.0-43.48-generic 4.13.16
  Uname: Linux 4.13.0-43-generic aarch64
  AlsaDevices:
-  total 0
-  crw-rw 1 root audio 116,  1 Jun  5 08:30 seq
-  crw-rw 1 root audio 116, 33 Jun  5 08:30 timer
+  total 0
+  crw-rw 1 root audio 116,  1 Jun  5 08:30 seq
+  crw-rw 1 root audio 116, 33 Jun  5 08:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.9
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Jun  5 09:14:07 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Cavium ThunderX CRB
  PciMultimedia:
-  
+ 
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=C.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=C.UTF-8
+  SHELL=/bin/bash
  ProcFB:
-  0 EFI VGA
-  1 astdrmfb
+  0 EFI VGA
+  1 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic 
root=UUID=ddcb8b36-6267-4392-a1f9-74d9203b742e ro
  RelatedPackageVersions:
-  linux-restricted-modules-4.13.0-43-generic N/A
-  linux-backports-modules-4.13.0-43-generic  N/A
-  linux-firmware 1.169.3
+  linux-restricted-modules-4.13.0-43-generic N/A
+  linux-backports-modules-4.13.0-43-generic  N/A
+  linux-firmware 1.169.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 0
  dmi.chassis.vendor: Cavium
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/12/2012:svnCavium:pnThunderXCRB:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnCavium:ct0:cvrTobefilledbyO.E.M.:
  dmi.product.family: Default string
  dmi.product.name: ThunderX CRB
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cavium

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

Title:
  fanotify09 in LTP syscall test failed with A/T kernel

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  The "fanotify09" from the LTP syscall tests has failed on a testing
  node with A/T kernel installed.

  Steps (with root):
    1. sudo apt-get install git xfsprogs -y
    2. git clone --depth=1 https://github.com/linux-test-project/ltp.git
    3. cd ltp
    4. make autotools
    5. ./configure
    6. make; make install
    7. cd /opt/ltp
    8. echo "fanotify09" > /tmp/jobs
    9. ./runltp -f /tmp/jobs

  <<>>
  tag=fanotify09 stime=1528192114
  cmdline="fanotify09"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s
  fanotify09.c:134: PASS: group 0 get event: mask 2 pid=43803 fd=9
  

[Kernel-packages] [Bug 1775316] [NEW] add_key04 in LTP syscall test cause kernel oops (NULL pointer dereference) with T kernel

2018-06-05 Thread Po-Hsu Lin
Public bug reported:

The "add_key04" from the LTP syscall tests will cause kernel oops on a
testing node with Trusty kernel installed. And it will make incoming ssh
connection hang (bug 1775158)

Steps (with root):
  1. sudo apt-get install git xfsprogs -y
  2. git clone --depth=1 https://github.com/linux-test-project/ltp.git
  3. cd ltp
  4. make autotools
  5. ./configure
  6. make; make install
  7. cd /opt/ltp/testcases/bin
  8. ./add_key04

Test result:
ubuntu@amaura:/opt/ltp/testcases/bin$ sudo ./add_key04
tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s
add_key04.c:82: FAIL: kernel oops while filling keyring

Summary:
passed   0
failed   1
skipped  0
warnings 0

[52399.298894] BUG: unable to handle kernel NULL pointer dereference at 
0010
[52399.298918] IP: [] assoc_array_apply_edit+0x67/0x110
[52399.298938] PGD 800455a3a067 PUD 45725f067 PMD 0 
[52399.298952] Oops: 0002 [#1] SMP 
[52399.298963] Modules linked in: cfg80211 ib_iser rdma_cm iw_cm ib_cm ib_sa 
ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
dm_crypt joydev hid_generic x86_pkg_temp_thermal coretemp kvm_intel kvm usbhid 
hid lpc_ich shpchp mac_hid crct10dif_pclmul crc32_pclmul i915_bdw 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
igb cryptd ahci dca ptp libahci pps_core intel_ips i2c_algo_bit drm_kms_helper 
video drm
[52399.299100] CPU: 7 PID: 9559 Comm: add_key04 Not tainted 3.13.0-149-generic 
#199-Ubuntu
[52399.299118] Hardware name: Intel Corporation S1200RP/S1200RP, BIOS 
S1200RP.86B.03.02.0003.070120151022 07/01/2015
[52399.299142] task: 880457b43000 ti: 88045a2e2000 task.ti: 
88045a2e2000
[52399.299159] RIP: 0010:[]  [] 
assoc_array_apply_edit+0x67/0x110
[52399.299182] RSP: 0018:88045a2e3df0  EFLAGS: 00010202
[52399.299194] RAX: 0010 RBX: 88045a2e3e78 RCX: 
[52399.299211] RDX: 88045a1d1741 RSI: 880456028880 RDI: 880456028800
[52399.299228] RBP: 88045a2e3df0 R08: 00016880 R09: 812dba97
[52399.299244] R10: 880460803c00 R11: ddf32900 R12: 880456f7f680
[52399.299261] R13: 88045a1d09c0 R14:  R15: 
[52399.299278] FS:  7ff43fc39740() GS:8804704e() 
knlGS:
[52399.299297] CS:  0010 DS:  ES:  CR0: 80050033
[52399.299311] CR2: 0010 CR3: 00045514c000 CR4: 00360770
[52399.299328] DR0:  DR1:  DR2: 
[52399.299344] DR3:  DR6: fffe0ff0 DR7: 0400
[52399.299361] Stack:
[52399.299366]  88045a2e3e08 812d7a33  
88045a2e3e50
[52399.299387]  812d57a7 88045a1d0a30 88045a2e3e78 
880456f7f681
[52399.299407]  3f01 880456f7f380 88045a1d09c0 
880457b43000
[52399.299427] Call Trace:
[52399.299436]  [] __key_link+0x33/0x40
[52399.299450]  [] __key_instantiate_and_link+0x87/0xf0
[52399.299467]  [] key_create_or_update+0x32e/0x420
[52399.299482]  [] SyS_add_key+0x110/0x210
[52399.299497]  [] ? schedule_tail+0x5c/0xb0
[52399.299512]  [] system_call_fastpath+0x1a/0x1f
[52399.299526] Code: 48 85 d2 74 0a 48 8b 8f e8 00 00 00 48 89 0a 48 83 c0 08 
48 39 f0 75 e4 48 8b 87 00 01 00 00 48 85 c0 74 0a 48 8b 97 08 01 00 00 <48> 89 
10 48 8b 87 10 01 00 00 48 85 c0 74 0a 48 8b 97 18 01 00 
[52399.299625] RIP  [] assoc_array_apply_edit+0x67/0x110
[52399.299642]  RSP 
[52399.299650] CR2: 0010
[52399.302015] ---[ end trace 0f3e00901ea9f056 ]---

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-149-generic 3.13.0-149.199
ProcVersionSignature: User Name 3.13.0-149.199-generic 3.13.11-ckt39
Uname: Linux 3.13.0-149-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Jun  5 12:22 seq
 crw-rw 1 root audio 116, 33 Jun  5 12:22 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.14.1-0ubuntu3.27
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDmesg: [3.475549] init: plymouth-upstart-bridge main process ended, 
respawning
Date: Wed Jun  6 02:54:24 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Intel Corporation S1200RP
PciMultimedia:
 
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic 
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-149-generic N/A
 linux-backports-modules-3.13.0-149-generic  N/A
 linux-firmware  1.127.24
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No 

[Kernel-packages] [Bug 1743094] Re: [regression] hibernation (freezes on resume) since 4.13.0-25.29

2018-06-05 Thread Rus Sh
I manually install 4.13.0-21 from here https://launchpad.net/~canonical-
kernel-team/+archive/ubuntu/ppa/+build/13870500 and hibernate began to
work!

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

Title:
  [regression] hibernation (freezes on resume) since 4.13.0-25.29

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  After hibernating the system and than resuming it the system reboots
  notifying that it is resuming and than stops/freezes. The system does
  not respond to anything (no tty's other notifying textg are
  available).

  
  After booting kernel 4.10-042 the hibernation and hibride hibernation/sleep 
functions as proposed.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jb 1717 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=00059f88-0cf2-44a0-a23d-f0a995cb1478
  InstallationDate: Installed on 2017-12-10 (34 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: Acer Aspire S3-391
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic 
root=UUID=5397ffb7-8114-45c4-824f-b1da7cce468c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-26-generic N/A
   linux-backports-modules-4.13.0-26-generic  N/A
   linux-firmware 1.157.14
  Tags:  sylvia
  Uname: Linux 4.13.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Hummingbird2
  dmi.board.vendor: Acer
  dmi.board.version: V2.10
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.10
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.10:bd10/31/2012:svnAcer:pnAspireS3-391:pvrV2.10:rvnAcer:rnHummingbird2:rvrV2.10:cvnAcer:ct10:cvrV2.10:
  dmi.product.family: ChiefRiver System
  dmi.product.name: Aspire S3-391
  dmi.product.version: V2.10
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension

2018-06-05 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: linux (Ubuntu Bionic)
   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/1752772

Title:
  r8169 ethernet card don't work after returning from suspension

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

Bug description:
  ===SRU Justification===
  [Impact]
  Ethernet r8169 stops working after system resumed from suspend.

  [Test]
  User confirmed these patches fix the issue. r8169 continues to work
  after resume from suspend.

  [Regression Potential]
  Medium. The fix is limited to one device, all patches are in mainline.
  The WOL default change might cause regression for users that depend on
  BIOS settings. We can advice them to use userspace tool (systemd,
  ethtool, etc.) instead.

  ===Original Bug Report===
  I have noticed that the network stopped working on my desktop after I've 
suspended the system and woke it up. On dmesg there are messages like:

  [  150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
  [  150.944101] do_IRQ: 3.37 No irq handler for vector
  [  150.944105] r8169 :01:00.0 enp1s0: link down
  [  150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready

  When using Xenial (from a different install), this problem is not
  happening. This is happening on Bionic.

  There are only two ways to restore connectivity:
  1) Reboot the system;
  2) Remove the r8169 module and reinsert it with modprobe.

  The motherboard is a AsRock H55M-LE and the Ethernet controller is:

  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.172
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Mar  2 00:21:57 2018
  Dependencies:

  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-10-generic.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1153 F pulseaudio
   /dev/snd/controlC1:  usuario1153 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26'
     Mixer name : 'VIA VT1818S'
     Components : 'HDA:11060440,18492818,0010'
     Controls  : 40
     Simple ctrls  : 17
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27'
     Mixer name : 'ATI R6xx HDMI'
     Components : 'HDA:1002aa01,00aa0100,00100200'
     Controls  : 7
     Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
     Capabilities: pswitch pswitch-joined
     Playback channels: Mono
     Mono: Playback [on]
  CurrentDesktop: LXDE
  Dependencies:

  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux-firmware 1.172
  PackageArchitecture: all
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz 
root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:

  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: H55M-LE
  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: 

[Kernel-packages] [Bug 1775301] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4: bcmwl kernel module failed to build [internal compiler error: Bus error]

2018-06-05 Thread Daniel van Vugt
Also, is the rest of your system stable? The problem could be in
hardware too, like faulty RAM.

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

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

Title:
  bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4: bcmwl kernel module
  failed to build [internal compiler error: Bus error]

Status in bcmwl package in Ubuntu:
  Incomplete

Bug description:
  My Ubuntu says I'm using bcmwl when I go into the drivers section, but
  it also says I have no wifi driver

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-20-generic
  Date: Wed Jun  6 01:23:28 2018
  InstallationDate: Installed on 2018-06-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageVersion: 6.30.223.271+bdcom-0ubuntu4
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4: bcmwl kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1775301] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4: bcmwl kernel module failed to build [internal compiler error: Bus error]

2018-06-05 Thread Daniel van Vugt
Please also run this on the machine:

  dmesg > dmesg.txt

and send us the resulting file.

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

Title:
  bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4: bcmwl kernel module
  failed to build [internal compiler error: Bus error]

Status in bcmwl package in Ubuntu:
  Incomplete

Bug description:
  My Ubuntu says I'm using bcmwl when I go into the drivers section, but
  it also says I have no wifi driver

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-20-generic
  Date: Wed Jun  6 01:23:28 2018
  InstallationDate: Installed on 2018-06-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageVersion: 6.30.223.271+bdcom-0ubuntu4
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4: bcmwl kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1772960] Re: linux: 4.4.0-128.154 -proposed tracker

2018-06-05 Thread Taihsiang Ho
Hardware Certification have begun testing this -proposed kernel.

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

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

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

Title:
  linux: 4.4.0-128.154 -proposed tracker

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

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

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

  backports: bug 1772962 (linux-lts-xenial), bug 1772963 (linux-aws)
  derivatives: bug 1772964 (linux-kvm), bug 1772965 (linux-snapdragon), bug 
1772966 (linux-aws), bug 1772968 (linux-raspi2), bug 1772969 (linux-euclid)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1775301] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4: bcmwl kernel module failed to build [internal compiler error: Bus error]

2018-06-05 Thread Daniel van Vugt
The problem seems to be that your compiler is crashing.

Please run 'cc -v' and send us the output.


** Summary changed:

- bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4: bcmwl kernel module failed 
to build
+ bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4: bcmwl kernel module failed 
to build [internal compiler error: Bus error]

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

Title:
  bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4: bcmwl kernel module
  failed to build [internal compiler error: Bus error]

Status in bcmwl package in Ubuntu:
  Incomplete

Bug description:
  My Ubuntu says I'm using bcmwl when I go into the drivers section, but
  it also says I have no wifi driver

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-20-generic
  Date: Wed Jun  6 01:23:28 2018
  InstallationDate: Installed on 2018-06-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageVersion: 6.30.223.271+bdcom-0ubuntu4
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4: bcmwl kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1774640] Re: Bluetooth turns off automatically Ubuntu 18.04 LTS

2018-06-05 Thread Daniel van Vugt
** Changed in: bluez (Ubuntu)
   Status: Incomplete => New

** Tags added: a2dp

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

Title:
  Bluetooth turns off automatically Ubuntu 18.04 LTS

Status in bluez package in Ubuntu:
  New

Bug description:
  Whenever I start up my laptop and connect my JBL-speaker, the device stays 
connected. However, when I turn de speaker off, and try to reconnect to the 
speaker, the Bluetooth automatically turns off. I then need to restart my 
laptop and then only Bluetooth works again.
  --- 
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-27 (39 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X555LAB
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2c696fdd-83b4-4daf-b864-3c9a68f8c2dc ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555LAB.503
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.503:bd08/04/2015:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:1A:7D:DA:71:0A  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:55347 acl:67 sco:0 events:7591 errors:0
TX bytes:4599486 acl:14880 sco:0 commands:100 errors:0

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

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


[Kernel-packages] [Bug 1775187] Re: bluetooth headset gets imitatively disconnected

2018-06-05 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1775187

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

** Tags added: a2dp

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

Title:
  bluetooth headset gets imitatively disconnected

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I upgraded from artful to bionic (just run apt update && apt upgrade
  and rebooted before testing the below) and since then my sennheiser
  pxc550 was immediately disconnected after a connect.

  Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd 
complete (0x0f)
  Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: 
Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8
  Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with 
an error: org.bluez.Error.InvalidArguments, Unable to handle new connection
  Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: 
Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid
  Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 
matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 
comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") 
interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" 
destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " 
label="unconfined")
  Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: 
Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid
  Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 
matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 
comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") 
interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" 
destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " 
label="unconfined")
  Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd 
complete (0x0f)
  Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd 
complete (0x0f)
  Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd 
complete (0x0f)
  [...same message a few more time until I had a new version installed ...]

  
  I since then applied the patch from 
https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> 
https://marc.info/?l=linux-bluetooth=151801178209679=raw to bluez (apt 
source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now 
my headset works again.

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

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


[Kernel-packages] [Bug 1772787] Re: lspci command cannot work normally in ubuntu16.04.4 with 4.10.0-40 kernel

2018-06-05 Thread seven-wang
hi Adam, thanks for your reply. we found the reson for this issue is due
to the intel VMD feature in BIOS. Now we disable the intel VMD feature,
and the lspci command can work normally.

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

** Changed in: linux (Ubuntu)
   Status: Opinion => Invalid

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

Title:
  lspci command cannot work normally in ubuntu16.04.4 with 4.10.0-40
  kernel

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Execute lspci command in ubuntu 16.04.4 with kernel update
  (kernel:4.10.0-40-generic), but always prompt error that cannot open
  /sys/bus/pci/devices/0001:00:02.0/resource: no such file or directory.

  Execute lspci command in ubuntu 16.04.4 without kernel update
  (kernel:4.4.0-116-generic), issue not exist.

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

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


[Kernel-packages] [Bug 1772940] Re: linux-azure: 4.15.0-1013.13~16.04.2 -proposed tracker

2018-06-05 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

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

Title:
  linux-azure: 4.15.0-1013.13~16.04.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-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-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1772927
  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/1772940/+subscriptions

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


[Kernel-packages] [Bug 1743094] Re: [regression] hibernation (freezes on resume) since 4.13.0-25.29

2018-06-05 Thread Rus Sh
Have a same bug on desktop PC
Motherboard HB7-Plus, 16Mb RAM, Intel i7-4770 3.4 CPU

uname -a
Linux rtuser-break-G 4.13.0-43-generic #48~16.04.1-Ubuntu SMP Thu May 17 
12:56:46 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

After each restoring hibernate PC freeze tight.

** Attachment added: "IMAG1147.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743094/+attachment/5149119/+files/IMAG1147.jpg

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

Title:
  [regression] hibernation (freezes on resume) since 4.13.0-25.29

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  After hibernating the system and than resuming it the system reboots
  notifying that it is resuming and than stops/freezes. The system does
  not respond to anything (no tty's other notifying textg are
  available).

  
  After booting kernel 4.10-042 the hibernation and hibride hibernation/sleep 
functions as proposed.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jb 1717 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=00059f88-0cf2-44a0-a23d-f0a995cb1478
  InstallationDate: Installed on 2017-12-10 (34 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: Acer Aspire S3-391
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic 
root=UUID=5397ffb7-8114-45c4-824f-b1da7cce468c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-26-generic N/A
   linux-backports-modules-4.13.0-26-generic  N/A
   linux-firmware 1.157.14
  Tags:  sylvia
  Uname: Linux 4.13.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Hummingbird2
  dmi.board.vendor: Acer
  dmi.board.version: V2.10
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.10
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.10:bd10/31/2012:svnAcer:pnAspireS3-391:pvrV2.10:rvnAcer:rnHummingbird2:rvrV2.10:cvnAcer:ct10:cvrV2.10:
  dmi.product.family: ChiefRiver System
  dmi.product.name: Aspire S3-391
  dmi.product.version: V2.10
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1743094] Re: [regression] hibernation (freezes on resume) since 4.13.0-25.29

2018-06-05 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nvidia-graphics-drivers-384 (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/1743094

Title:
  [regression] hibernation (freezes on resume) since 4.13.0-25.29

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  After hibernating the system and than resuming it the system reboots
  notifying that it is resuming and than stops/freezes. The system does
  not respond to anything (no tty's other notifying textg are
  available).

  
  After booting kernel 4.10-042 the hibernation and hibride hibernation/sleep 
functions as proposed.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jb 1717 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=00059f88-0cf2-44a0-a23d-f0a995cb1478
  InstallationDate: Installed on 2017-12-10 (34 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: Acer Aspire S3-391
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic 
root=UUID=5397ffb7-8114-45c4-824f-b1da7cce468c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-26-generic N/A
   linux-backports-modules-4.13.0-26-generic  N/A
   linux-firmware 1.157.14
  Tags:  sylvia
  Uname: Linux 4.13.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Hummingbird2
  dmi.board.vendor: Acer
  dmi.board.version: V2.10
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.10
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.10:bd10/31/2012:svnAcer:pnAspireS3-391:pvrV2.10:rvnAcer:rnHummingbird2:rvrV2.10:cvnAcer:ct10:cvrV2.10:
  dmi.product.family: ChiefRiver System
  dmi.product.name: Aspire S3-391
  dmi.product.version: V2.10
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1775301] [NEW] bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4: bcmwl kernel module failed to build

2018-06-05 Thread Andy Ayres
Public bug reported:

My Ubuntu says I'm using bcmwl when I go into the drivers section, but
it also says I have no wifi driver

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
DKMSKernelVersion: 4.15.0-20-generic
Date: Wed Jun  6 01:23:28 2018
InstallationDate: Installed on 2018-06-05 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageVersion: 6.30.223.271+bdcom-0ubuntu4
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: bcmwl
Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4: bcmwl kernel module 
failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4: bcmwl kernel module
  failed to build

Status in bcmwl package in Ubuntu:
  New

Bug description:
  My Ubuntu says I'm using bcmwl when I go into the drivers section, but
  it also says I have no wifi driver

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-20-generic
  Date: Wed Jun  6 01:23:28 2018
  InstallationDate: Installed on 2018-06-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageVersion: 6.30.223.271+bdcom-0ubuntu4
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4: bcmwl kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1772930] Re: linux-azure: 4.15.0-1013.13 -proposed tracker

2018-06-05 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

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

Title:
  linux-azure: 4.15.0-1013.13 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1772927
  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/1772930/+subscriptions

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


[Kernel-packages] [Bug 1760173] Re: zfs, zpool commands hangs for 10 seconds without a /dev/zfs

2018-06-05 Thread Stéphane Graber
Actually, LXC/LXD can't set environment variables in that way as systemd
strips all inherited environment.

Looking at the backlog it sounds like it'd be safe for us to just turn
off that timeout entirely in Ubuntu given that we can assume we'll
always have devtmpfs where it matters and so there's no potential race
between module loading and device node appearing.

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

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

Title:
  zfs, zpool commands hangs for 10 seconds without a /dev/zfs

Status in lxd package in Ubuntu:
  Invalid
Status in zfs-linux package in Ubuntu:
  Triaged

Bug description:
  1. # lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  2. # apt-cache policy zfsutils-linux
  zfsutils-linux:
Installed: 0.6.5.6-0ubuntu19
Candidate: 0.6.5.6-0ubuntu19
Version table:
   *** 0.6.5.6-0ubuntu19 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status

  3. When inside a lxd container with zfs storage, zfs list or zpool
  status either return or report what's going on.

  4. When inside a lxd container with zfs storage, zfs list or zpool
  status appears to hang, no output for 10 seconds.

  strace reveals that without a /dev/zfs the tools wait for it to appear
  for 10 seconds but do not provide a command line switch to disable or
  make it more verbose.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: zfsutils-linux 0.6.5.6-0ubuntu19
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Mar 30 18:09:29 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension

2018-06-05 Thread Kleber Sacilotto de Souza
Nominating for Bionic.

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

Title:
  r8169 ethernet card don't work after returning from suspension

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

Bug description:
  ===SRU Justification===
  [Impact]
  Ethernet r8169 stops working after system resumed from suspend.

  [Test]
  User confirmed these patches fix the issue. r8169 continues to work
  after resume from suspend.

  [Regression Potential]
  Medium. The fix is limited to one device, all patches are in mainline.
  The WOL default change might cause regression for users that depend on
  BIOS settings. We can advice them to use userspace tool (systemd,
  ethtool, etc.) instead.

  ===Original Bug Report===
  I have noticed that the network stopped working on my desktop after I've 
suspended the system and woke it up. On dmesg there are messages like:

  [  150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
  [  150.944101] do_IRQ: 3.37 No irq handler for vector
  [  150.944105] r8169 :01:00.0 enp1s0: link down
  [  150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready

  When using Xenial (from a different install), this problem is not
  happening. This is happening on Bionic.

  There are only two ways to restore connectivity:
  1) Reboot the system;
  2) Remove the r8169 module and reinsert it with modprobe.

  The motherboard is a AsRock H55M-LE and the Ethernet controller is:

  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.172
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Mar  2 00:21:57 2018
  Dependencies:

  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-10-generic.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1153 F pulseaudio
   /dev/snd/controlC1:  usuario1153 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26'
     Mixer name : 'VIA VT1818S'
     Components : 'HDA:11060440,18492818,0010'
     Controls  : 40
     Simple ctrls  : 17
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27'
     Mixer name : 'ATI R6xx HDMI'
     Components : 'HDA:1002aa01,00aa0100,00100200'
     Controls  : 7
     Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
     Capabilities: pswitch pswitch-joined
     Playback channels: Mono
     Mono: Playback [on]
  CurrentDesktop: LXDE
  Dependencies:

  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux-firmware 1.172
  PackageArchitecture: all
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz 
root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:

  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: H55M-LE
  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.80:bd10/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55M-LE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be 

[Kernel-packages] [Bug 744916] Re: [STAGING] NETDEV WATCHDOG: usb0 (cdc_subset): transmit queue 0 timed out

2018-06-05 Thread Christopher M. Penalver
Harsh Patel, there is no support for 2.x kernels either downstream or upstream. 
For more on this, please see:
https://wiki.ubuntu.com/Releases
https://www.kernel.org/

For more on ARM and Ubuntu, please see
https://www.ubuntu.com/download/server/arm

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

Title:
  [STAGING] NETDEV WATCHDOG: usb0 (cdc_subset): transmit queue 0 timed
  out

Status in linux package in Ubuntu:
  Expired

Bug description:
  I have 3 time in a week, an alert that say kernel has a critical error
  and ask if i want to report.

  
  PS: on the last step of the bug report (apport) i had a blank yes/no popup 
that i awnsered 'no' but i don't know what it is (maybe translate error?)

  ProblemType: KernelOops
  DistroRelease: Ubuntu 11.04
  Package: linux-image-2.6.38-7-generic 2.6.38-7.39
  Regression: Yes
  Reproducible: No
  ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
  Uname: Linux 2.6.38-7-generic x86_64
  NonfreeKernelModules: wl
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Annotation: Your system might become unstable now and might need to be 
restarted.
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cm-t  19103 F pulseaudio
  CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xc450 irq 44'
 Mixer name : 'IDT 92HD81B1X5'
 Components : 'HDA:111d7605,103c1486,00100402'
 Controls  : 14
 Simple ctrls  : 9
  Card1.Amixer.info:
   Card hw:1 'Generic'/'HD-Audio Generic at 0xc442 irq 46'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 4
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Date: Tue Mar 29 13:14:46 2011
  Failure: oops
  Frequency: Once every few days.
  HibernationDevice: RESUME=UUID=98370a42-be2e-4bd4-8447-bd773b21ede2
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: Hewlett-Packard HP TouchSmart tm2 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-7-generic 
root=UUID=93978fe3-2bff-4202-9ac1-634dbdacca5c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-2.6.38-7-generic N/A
   linux-backports-modules-2.6.38-7-generic  N/A
   linux-firmware1.49
  SourcePackage: linux
  StagingDrivers: brcm80211
  Title: [STAGING]
  UpgradeStatus: Upgraded to natty on 2011-03-25 (3 days ago)
  dmi.bios.date: 08/16/2010
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1486
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 83.1A
  dmi.chassis.asset.tag: CNU0363P44
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd08/16/2010:svnHewlett-Packard:pnHPTouchSmarttm2NotebookPC:pvr058A21242A1120100:rvnHewlett-Packard:rn1486:rvr83.1A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP TouchSmart tm2 Notebook PC
  dmi.product.version: 058A21242A1120100
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension

2018-06-05 Thread Kleber Sacilotto de Souza
** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  r8169 ethernet card don't work after returning from suspension

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

Bug description:
  ===SRU Justification===
  [Impact]
  Ethernet r8169 stops working after system resumed from suspend.

  [Test]
  User confirmed these patches fix the issue. r8169 continues to work
  after resume from suspend.

  [Regression Potential]
  Medium. The fix is limited to one device, all patches are in mainline.
  The WOL default change might cause regression for users that depend on
  BIOS settings. We can advice them to use userspace tool (systemd,
  ethtool, etc.) instead.

  ===Original Bug Report===
  I have noticed that the network stopped working on my desktop after I've 
suspended the system and woke it up. On dmesg there are messages like:

  [  150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
  [  150.944101] do_IRQ: 3.37 No irq handler for vector
  [  150.944105] r8169 :01:00.0 enp1s0: link down
  [  150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready

  When using Xenial (from a different install), this problem is not
  happening. This is happening on Bionic.

  There are only two ways to restore connectivity:
  1) Reboot the system;
  2) Remove the r8169 module and reinsert it with modprobe.

  The motherboard is a AsRock H55M-LE and the Ethernet controller is:

  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.172
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Mar  2 00:21:57 2018
  Dependencies:

  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-10-generic.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1153 F pulseaudio
   /dev/snd/controlC1:  usuario1153 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26'
     Mixer name : 'VIA VT1818S'
     Components : 'HDA:11060440,18492818,0010'
     Controls  : 40
     Simple ctrls  : 17
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27'
     Mixer name : 'ATI R6xx HDMI'
     Components : 'HDA:1002aa01,00aa0100,00100200'
     Controls  : 7
     Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
     Capabilities: pswitch pswitch-joined
     Playback channels: Mono
     Mono: Playback [on]
  CurrentDesktop: LXDE
  Dependencies:

  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux-firmware 1.172
  PackageArchitecture: all
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz 
root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:

  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: H55M-LE
  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.80:bd10/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55M-LE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  

[Kernel-packages] [Bug 1773643] Re: [Clevo W253EUQ] Turn on bluetooth with Fn+F12 not working

2018-06-05 Thread Battant
Hello,

On my ubuntu 18.04 no kernel under 4.0 work

according the old bug report. It seems that 4.0.22 work but I could not
found this kernel version to test it

Could you help me please

Thanks for your support

Best regards

Battant

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

Title:
   [Clevo W253EUQ] Turn on bluetooth with Fn+F12 not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  Since long time my  [Clevo W253EUQ] Turn on bluetooth with Fn+F12 not
  working

  For more information see this link bellow

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

  Could you help me to fix this bug ?

  Best regards

  Battant

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-23-generic 4.15.0-23.25
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 27 13:21:46 2018
  InstallationDate: Installed on 2018-04-29 (27 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mparchet   1714 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-29 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=9d6286f1-598b-46c8-a491-3e29fc732cb9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/11/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W240EU/W250EUQ/W270EUQ
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: V3.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd11/11/2013:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W240EU/W250EUQ/W270EUQ
  dmi.product.version: Not Applicable
  dmi.sys.vendor: CLEVO CO.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mparchet   1714 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-29 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=9d6286f1-598b-46c8-a491-3e29fc732cb9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/11/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W240EU/W250EUQ/W270EUQ
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: V3.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd11/11/2013:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W240EU/W250EUQ/W270EUQ
  

[Kernel-packages] [Bug 1313279] Re: xHCI host not responding to stop endpoint command

2018-06-05 Thread Keerthi Raj
Output of lsb_release -a

No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.5 LTS
Release:14.04
Codename:   trusty

output of uname -a

Linux  4.4.0-127-lowlatency #153~14.04.1-Ubuntu SMP PREEMPT Sat
May 19 15:05:22 UTC 2018 x86_64 x86_64 x8

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

Title:
  xHCI host not responding to stop endpoint command

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

Bug description:
  Description:  Ubuntu 14.04 LTS
  Release:  14.04
  Hardware: Intel NUC D34010WYK (Core i3 4010U)
  Memory: 4 gigabytes
  USD device: PCTV 292e DVB-T tuner

  I have 2 PCTV 292e DVB-T tuners connected to the system. When I start
  to use either of the tuner, the xHCI host crashes. Since I'm booting
  from an USB disk. If I only connect 1 of the tuners, the system works
  ok. It does not matter which one of the tuners I connect.

  [   68.990396] xhci_hcd :00:14.0: xHCI host not responding to stop 
endpoint command.
  [   68.990402] xhci_hcd :00:14.0: Assuming host is dying, halting host.

  Sometimes this also leads to this:

  [  638.183002] IP: [] usb_enable_link_state+0x2d/0x2f0
  [  638.183057] PGD 0 
  [  638.183077] Oops:  [#1] SMP 

  I can also observe the same fault with OpenELEC Linux distribution
  that runs kernel 3.14 when I run the system from an internal SATA SSD
  drive (not from an external USB disk).

  lsusb -v: http://paste.ubuntu.com/7343384/
  dmesg: http://sprunge.us/HMXH
  dmesg (crash type 2): http://sprunge.us/PSiX

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lubuntu-desktop 0.55
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  Date: Sun Apr 27 11:12:22 2014
  InstallationDate: Installed on 2014-04-07 (19 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: lubuntu-meta
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (0 days ago)

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

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


[Kernel-packages] [Bug 1313279] Re: xHCI host not responding to stop endpoint command

2018-06-05 Thread Keerthi Raj
I am using kernel 4.4.0-127-lowlatency (Ubuntu 14.04) and I have this
bug. When we run an UVC camera, the host controller dies randomly after
some point. The symptoms are exactly as described by other users above.

I would like to know which kernels this bug affects and where a patch
has been applied.

The link below describes a fix but I couldn't figure out which kernel it has 
been applied to. May I know which kernel fixes it?
https://www.spinics.net/lists/linux-usb/msg122678.html 

Hardware: 
Asus X99-E-10G WS Motherboard
Intel Xeon E5-2687W v4 3.0 GHz

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

Title:
  xHCI host not responding to stop endpoint command

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

Bug description:
  Description:  Ubuntu 14.04 LTS
  Release:  14.04
  Hardware: Intel NUC D34010WYK (Core i3 4010U)
  Memory: 4 gigabytes
  USD device: PCTV 292e DVB-T tuner

  I have 2 PCTV 292e DVB-T tuners connected to the system. When I start
  to use either of the tuner, the xHCI host crashes. Since I'm booting
  from an USB disk. If I only connect 1 of the tuners, the system works
  ok. It does not matter which one of the tuners I connect.

  [   68.990396] xhci_hcd :00:14.0: xHCI host not responding to stop 
endpoint command.
  [   68.990402] xhci_hcd :00:14.0: Assuming host is dying, halting host.

  Sometimes this also leads to this:

  [  638.183002] IP: [] usb_enable_link_state+0x2d/0x2f0
  [  638.183057] PGD 0 
  [  638.183077] Oops:  [#1] SMP 

  I can also observe the same fault with OpenELEC Linux distribution
  that runs kernel 3.14 when I run the system from an internal SATA SSD
  drive (not from an external USB disk).

  lsusb -v: http://paste.ubuntu.com/7343384/
  dmesg: http://sprunge.us/HMXH
  dmesg (crash type 2): http://sprunge.us/PSiX

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lubuntu-desktop 0.55
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  Date: Sun Apr 27 11:12:22 2014
  InstallationDate: Installed on 2014-04-07 (19 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: lubuntu-meta
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (0 days ago)

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

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


[Kernel-packages] [Bug 1774575] Re: hwinfo --framebuffer | VirtualBox 5.2.12 | empty output

2018-06-05 Thread linux64kb
apport information

** Tags added: apport-collected uec-images

** Description changed:

  1) Ubuntu 4.15.0-22.24-generic 4.15.17; Description:Ubuntu 18.04 LTS 
Release:18.04
  2) lspci-vnvn+hwinfo_policy.log attached
  3) What happens: The command "sudo hwinfo --framebuffer" provides an empty 
output. (Possibly can't find framebuffer info.)
  4) Expected: a list of supported video modes 
(https://askubuntu.com/a/824182/621093)
  
  Some additional info
  A) Enviroment:
  A1) Ubuntu 18.04 server
  A2) VirtualBox 5.2.12; installing guest packages and host extensions didn't 
help.
  B) VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox 
Graphics Adapter
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-22-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=UUID=2a72b513-4a62-11e8-b10a-080027d89d39 ro 
keyboard-configuration/layoutcode=hu
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
+ --- 
+ ApportVersion: 2.20.9-0ubuntu7.1
+ Architecture: amd64
+ DistroRelease: Ubuntu 18.04
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ Tags:  bionic uec-images
+ Uname: Linux 4.17.0-041700rc7-generic x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lxd plugdev sudo
+ _MarkForUpload: True

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1774575/+attachment/5149086/+files/ProcCpuinfoMinimal.txt

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

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

Title:
  hwinfo --framebuffer | VirtualBox 5.2.12 | empty output

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

Bug description:
  1) Ubuntu 4.15.0-22.24-generic 4.15.17; Description:Ubuntu 18.04 LTS 
Release:18.04
  2) lspci-vnvn+hwinfo_policy.log attached
  3) What happens: The command "sudo hwinfo --framebuffer" provides an empty 
output. (Possibly can't find framebuffer info.)
  4) Expected: a list of supported video modes 
(https://askubuntu.com/a/824182/621093)

  Some additional info
  A) Enviroment:
  A1) Ubuntu 18.04 server
  A2) VirtualBox 5.2.12; installing guest packages and host extensions didn't 
help.
  B) VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox 
Graphics Adapter
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-22-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  ArecordDevices: Error: 

[Kernel-packages] [Bug 1773232] Re: Not booting at all times

2018-06-05 Thread steven krol
I've did some more testing with multiple versions. I've figgured out the bug 
got introduced between kernel 4.15.0-rc1 and 4.15.0-rc2
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc1/ 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc2/
If there is a clear way somewhere that explains me how to do a git bisect, I'd 
love to help out and narrowing the bug down to the commit.

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

Title:
  Not booting at all times

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

Bug description:
  I'm running Linux kernel 4.17rc5. (this problem is also with the 4.16
  kernel and 4.15). My computer randomly freezes up after a hour of less
  and sometimes it works for more then a day. But when I check the
  kern.log or syslog it does not show any messages at the time of
  crashing. So is there a way that I can find you why it crashes?

  Also, after a crash it sometimes refuses to boot at all. It will give
  me a black screen. After restarting for 20 or more times it boots up.
  Sometimes my password doesn't work while booting even though I use the
  same (correct) password after the restart.

  I have made a video on this issue here: 
https://www.youtube.com/watch?v=gqH8ySXOUmk=youtu.be
  (the video is a bit out of focus, forgot the manual focus. I have speeded up 
someparts to make it more pleasant to watch)

  I'd like to include some logs but Can't find any relevant logs since
  it does not log during the period of the error. I Have attached a
  picture of my screen that it will sometimes show.

  The moment it did boot up I was using kernel 4.15 (but with that version not 
all of my screens work)
  After the reboot I used the kernel 4.17r5 again and it did work.
  This happens to me a lot and it can take a lot of restarting in order to boot.

  In the video it didnt show the problem that my password would not be
  recognised. However this sometimes happens too.

  One more bug I'm having is that my thrird screen is not being recognised to 
it sets a lower screen resolution. I have solved this with forcing the screen 
resolution to 1080x1920 but then the menu bar is not shown correctly. and I 
have to drag the screen to the right place in the settings in order to have the 
menu's correctly.
  (video: https://youtu.be/Tq-TEeAAIGA) this is what I have to do at startup
  Is there anything more I can do to make this bug report more specific?
  ---
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-06 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: linux (not installed)
  Tags:  bionic
  Uname: Linux 4.17.0-041700rc5-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-06 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: linux (not installed)
  Tags:  bionic
  Uname: Linux 4.17.0-041700rc5-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-06 (18 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: linux (not installed)
  Tags:  bionic
  Uname: Linux 4.14.0-041400-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Kernel-packages] [Bug 1764194] Re: Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

2018-06-05 Thread Igor Shuvalov
bionic-proposed (4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux) is OK on my Latitude 5590.
Thanks

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

Title:
  Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==
  This bug causes a Dell Latitude 5490/5590 with BIOS update 1.1.9 to get a
  black screen at boot. Specifying 'nomodeset' on the kernel command line works
  around the problem.

  Intel resolved the problem in upstream commit a3520b8992e5.  This commit
  is now in mainline as of 4.17.rc2.  It has also been cc'd to upstream
  stable.

  
  == Fix ==
  a3520b8992e5 ("drm/i915/bios: filter out invalid DDC pins from VBT child 
devices")

  == Regression Potential ==
  Low.  This commit was also cc'd to upstream stable, so it recieved
  additional upstream review.


  
  Description:Ubuntu 16.04.4 LTS
  Release:16.04

  Ubuntu 16.04.4 LTS was installed to some Dell Latitude 5490 & 5590
  laptops, originally running BIOS version 1.0.8. The install media and
  the installed OS was running linux-generic-hwe kernel 4.13.0.

  After upgrading BIOS to latest version 1.1.9, the kernel no longer
  boots: right after loading the i915 drm driver, the screen goes black,
  and the machine can only be reset or power cycled. This is true for
  both the installation media, and the OS instance previously installed
  to the disk and updated to the latest hwe kernel 4.13.0-38.

  Specifying 'nomodeset' on the kernel command line works around the
  problem by disabling the i915 drm driver functionality. In that case,
  several display driver function are obviously missing (eg GLX &
  xrandr).

  The problem manifested itself even when using the drm upstream latest 
git-head version. A custom built kernel was used to provide logs for this 
upstream bug report:
  https://bugs.freedesktop.org/show_bug.cgi?id=105549

  The upstream Intel developers provided a patch, which was successfully tested 
by both the original reporter and me.
  https://patchwork.freedesktop.org/patch/216371/
  
https://github.com/freedesktop/drm-tip/commit/f212bf9abe5de9f938fecea7df07046e74052dde

  I backported this fix to ubuntu-xenial hwe git-head, and tested the
  result successfully. I'd like this fix to be added to the ubuntu-
  xenial linux-generic-hwe kernel.

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

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


[Kernel-packages] [Bug 1774575] Re: hwinfo --framebuffer | VirtualBox 5.2.12 | empty output

2018-06-05 Thread linux64kb
I've forgot to add this.
sudo hwinfo --pci
...
17: PCI 02.0: 0300 VGA compatible controller (VGA)
  [Created at pci.378]
  Unique ID: _Znp.mHjpIGaFQV1
  SysFS ID: /devices/pci:00/:00:02.0
  SysFS BusID: :00:02.0
  Hardware Class: graphics card
  Model: "InnoTek Systemberatung VirtualBox Graphics Adapter"
  Vendor: pci 0x80ee "InnoTek Systemberatung GmbH"
  Device: pci 0xbeef "VirtualBox Graphics Adapter"
  Driver: "vboxvideo"
  Driver Modules: "vboxvideo"
  Memory Range: 0xe000-0xe1ff (ro,non-prefetchable)
  Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled)
  IRQ: 18 (8 events)
  I/O Ports: 0x3c0-0x3df (rw)
  Module Alias: "pci:v80EEdBEEFsvsdbc03sc00i00"
  Driver Info #0:
Driver Status: vboxvideo is active
Driver Activation Cmd: "modprobe vboxvideo"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
...

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

Title:
  hwinfo --framebuffer | VirtualBox 5.2.12 | empty output

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 4.15.0-22.24-generic 4.15.17; Description:Ubuntu 18.04 LTS 
Release:18.04
  2) lspci-vnvn+hwinfo_policy.log attached
  3) What happens: The command "sudo hwinfo --framebuffer" provides an empty 
output. (Possibly can't find framebuffer info.)
  4) Expected: a list of supported video modes 
(https://askubuntu.com/a/824182/621093)

  Some additional info
  A) Enviroment:
  A1) Ubuntu 18.04 server
  A2) VirtualBox 5.2.12; installing guest packages and host extensions didn't 
help.
  B) VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox 
Graphics Adapter
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-22-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=UUID=2a72b513-4a62-11e8-b10a-080027d89d39 ro 
keyboard-configuration/layoutcode=hu
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


[Kernel-packages] [Bug 1774575] Re: hwinfo --framebuffer | VirtualBox 5.2.12 | empty output

2018-06-05 Thread linux64kb
apport-collect 1774575 - done - Confirmed
kernel-bug-exists-upstream - Confirmed
---
@Joseph Salisbury (jsalisbury) Thank you for taking care of this issue! To 
answer your questions...
___
I've updated the Ubuntu 18.04 LTS server in question to the latest stable 
version (as of today, 5th of June 2018) and nstalled mainline kernel v4.17.
uname -a
Linux u1804svr-t1 4.17.0-041700rc7-generic #201806041848 SMP Mon Jun 4 22:51:06 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
lsb_release -rd
Description:Ubuntu 18.04 LTS
Release:18.04
___
Hwinfo is also the latest stable version which comes from the official ubuntu 
repo via "apt install hwinfo"
dpkg -l hwinfo
||/ Name Version   Architecture  Description
+++--=-=-=
ii  hwinfo   21.52-1   amd64 Hardware identification system
apt-cache policy hwinfo
hwinfo:
  Installed: 21.52-1
  Candidate: 21.52-1
  Version table:
 *** 21.52-1 500
500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
100 /var/lib/dpkg/status
___
"sudo hwinfo --framebuffer" is working on Ubuntu 16.04 server. I started to 
evaluate Ubuntu 18.04 server and found that this isn't working contrary to the 
previous LTS.
I've even tried "sudo hwinfo --framebuffer --verbose", but still no output.
___
The previous kernel version is "uname -r" -> 4.4.0-116-generic on 16.04 LTS.
The mainline kernel version is "uname -r" -> 4.17.0-041700rc7-generic on 18.04 
LTS
___


** Tags removed: apport-collected uec-images
** Tags added: kernel-bug-exists-upstream

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

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

Title:
  hwinfo --framebuffer | VirtualBox 5.2.12 | empty output

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 4.15.0-22.24-generic 4.15.17; Description:Ubuntu 18.04 LTS 
Release:18.04
  2) lspci-vnvn+hwinfo_policy.log attached
  3) What happens: The command "sudo hwinfo --framebuffer" provides an empty 
output. (Possibly can't find framebuffer info.)
  4) Expected: a list of supported video modes 
(https://askubuntu.com/a/824182/621093)

  Some additional info
  A) Enviroment:
  A1) Ubuntu 18.04 server
  A2) VirtualBox 5.2.12; installing guest packages and host extensions didn't 
help.
  B) VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox 
Graphics Adapter
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-22-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=UUID=2a72b513-4a62-11e8-b10a-080027d89d39 ro 
keyboard-configuration/layoutcode=hu
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about 

[Kernel-packages] [Bug 1775242] Re: [Bionic/Artful][Qlogic NIC] RDMA/qedr: application hang due to missing doorbell

2018-06-05 Thread Manoj Iyer
A test kernel with the patch applied is available in:
https://launchpad.net/~manjo/+archive/ubuntu/lp1775242

To enable this ppa: 
$ sudo add-apt-repository -y ppa:manjo/lp1775242
$ sudo apt-get update

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

Title:
  [Bionic/Artful][Qlogic NIC] RDMA/qedr: application hang due to missing
  doorbell

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  RDMA applications might hang with qlogic cards. This happens because
  of a bug in the doorbell implementation.

  [Test]
  1) Set IP addresses on both server and client
  2) On RoCE Server run "ib_send_bw -d qedr0 -x 2 -R"
  3) On RoCE client run "ib_send_bw -d qedr0 -x 2  -R"
  4) Notice that the command fails to run

  [Fix]
  30bf066cd998 RDMA/qedr: Fix doorbell bar mapping for dpi > 1

  [Regression Potential]
  None

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

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


[Kernel-packages] [Bug 1772787] Re: lspci command cannot work normally in ubuntu16.04.4 with 4.10.0-40 kernel

2018-06-05 Thread Adam Conrad
Linux 4.10.0-40 is wildly out of date.  The current HWE kernel on 16.04
is 4.13.0-43.  Do you still see issues if you upgrade?

** Package changed: debian-installer (Ubuntu) => linux (Ubuntu)

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

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

Title:
  lspci command cannot work normally in ubuntu16.04.4 with 4.10.0-40
  kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Execute lspci command in ubuntu 16.04.4 with kernel update
  (kernel:4.10.0-40-generic), but always prompt error that cannot open
  /sys/bus/pci/devices/0001:00:02.0/resource: no such file or directory.

  Execute lspci command in ubuntu 16.04.4 without kernel update
  (kernel:4.4.0-116-generic), issue not exist.

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

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


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

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

apport-collect 1775242

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: 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/1775242

Title:
  [Bionic/Artful][Qlogic NIC] RDMA/qedr: application hang due to missing
  doorbell

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  RDMA applications might hang with qlogic cards. This happens because
  of a bug in the doorbell implementation.

  [Test]
  1) Set IP addresses on both server and client
  2) On RoCE Server run "ib_send_bw -d qedr0 -x 2 -R"
  3) On RoCE client run "ib_send_bw -d qedr0 -x 2  -R"
  4) Notice that the command fails to run

  [Fix]
  30bf066cd998 RDMA/qedr: Fix doorbell bar mapping for dpi > 1

  [Regression Potential]
  None

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

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


[Kernel-packages] [Bug 1581890] Re: Boot registers protocol family 40, which is not in configs

2018-06-05 Thread Kenneth R. Crudup
"net-pf-40" is VMWare- they're apparently using it as a sort of IPC
between VMs and it gets installed when the vmnet(?) module loads.

(Old bug, I know, but this was the first search result, so I'd figured I
should answer this.)

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

Title:
  Boot registers protocol family 40, which is not in configs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I noticed this line in the system log after boot:
  "May 14 14:41:08 ubuntu kernel: [8.677878] NET: Registered protocol 
family 40"
  I tried to find out what protocol that was, and eventually determined that 
the IANA thinks it's the IL protocol, which is deprecated and unusual in any 
case. Protocol number 40 doesn't appear in the expected config or alias files 
(for modprobe in /etc or /etc/modprobe.d/). Enabling a dead protocol without 
being told seems to be a thing an OS shouldn't be doing.

  More context for the log line is below:
  ...
  May 14 14:41:08 ubuntu vmsvc[1607]: [ warning] [GLib-GObject] Attempt to add 
property ToolsCoreService::tcs-app-ctx after class was initialised
  May 14 14:41:08 ubuntu vmsvc[1607]: [ warning] [GLib-GObject] Attempt to add 
property ToolsCoreService::tcs-prop-thread-pool after class was initialised
  May 14 14:41:08 ubuntu kernel: [8.677878] NET: Registered protocol family 
40
  May 14 14:48:36 ubuntu dbus[465]: [system] Activating service 
name='org.freedesktop.UPower' (using servicehelper)
  May 14 14:48:36 ubuntu dbus[465]: [system] Successfully activated service 
'org.freedesktop.UPower'
  ...
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  blair  2640 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=38a747e6-6da8-4ab9-b2c5-d7613992fbfb
  InstallationDate: Installed on 2012-05-15 (1464 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-86-generic 
root=UUID=b4002a34-68be-4c40-a549-17edb4a1f7e9 ro quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-86.130-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-86-generic N/A
   linux-backports-modules-3.13.0-86-generic  N/A
   linux-firmware 1.127.22
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-86-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (753 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/20/2014
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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


[Kernel-packages] [Bug 1772787] [NEW] lspci command cannot work normally in ubuntu16.04.4 with 4.10.0-40 kernel

2018-06-05 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Execute lspci command in ubuntu 16.04.4 with kernel update
(kernel:4.10.0-40-generic), but always prompt error that cannot open
/sys/bus/pci/devices/0001:00:02.0/resource: no such file or directory.

Execute lspci command in ubuntu 16.04.4 without kernel update
(kernel:4.4.0-116-generic), issue not exist.

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

-- 
lspci command cannot work normally in ubuntu16.04.4 with 4.10.0-40 kernel
https://bugs.launchpad.net/bugs/1772787
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 1775242] [NEW] [Bionic/Artful][Qlogic NIC] RDMA/qedr: application hang due to missing doorbell

2018-06-05 Thread Manoj Iyer
Public bug reported:

[Impact]
RDMA applications might hang with qlogic cards. This happens because
of a bug in the doorbell implementation.

[Test]
1) Set IP addresses on both server and client
2) On RoCE Server run "ib_send_bw -d qedr0 -x 2 -R"
3) On RoCE client run "ib_send_bw -d qedr0 -x 2  -R"
4) Notice that the command fails to run

[Fix]
30bf066cd998 RDMA/qedr: Fix doorbell bar mapping for dpi > 1

[Regression Potential]
None

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


** Tags: artful cavium

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

Title:
  [Bionic/Artful][Qlogic NIC] RDMA/qedr: application hang due to missing
  doorbell

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  RDMA applications might hang with qlogic cards. This happens because
  of a bug in the doorbell implementation.

  [Test]
  1) Set IP addresses on both server and client
  2) On RoCE Server run "ib_send_bw -d qedr0 -x 2 -R"
  3) On RoCE client run "ib_send_bw -d qedr0 -x 2  -R"
  4) Notice that the command fails to run

  [Fix]
  30bf066cd998 RDMA/qedr: Fix doorbell bar mapping for dpi > 1

  [Regression Potential]
  None

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

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


[Kernel-packages] [Bug 1775235] Re: Ubuntu 16.04 (4.4.0-127) hangs on boot with virtio-scsi MQ enabled

2018-06-05 Thread Felipe Franciosi
** 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/1775235

Title:
  Ubuntu 16.04 (4.4.0-127) hangs on boot with virtio-scsi MQ enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We noticed that Ubuntu 16.04 guests running on Nutanix AHV stopped
  booting after they were upgraded to the latest kernel (4.4.0-127).
  Only guests with scsi mq enabled suffered from this problem. AHV is
  one of the few hypervisor products to offer multiqueue for virtio-scsi
  devices.

  Upon further investigation, we could see that the kernel would hang
  during the scanning of scsi targets. More specifically, immediately
  after coming across a target without any luns present. That's the
  first time the kernel destroys a target (given it doesn't have luns).
  This could be confirmed with gdb (attached to qemu's gdbserver):

  #0  0xc0045039 in ?? ()
  #1  0x88022c753c98 in ?? ()
  #2  0x815d1de6 in scsi_target_destroy (starget=0x88022ad62400)
  at /build/linux-E14mqW/linux-4.4.0/drivers/scsi/scsi_scan.c:322

  This shows the guest vCPU stuck on virtio-scsi's implementation of
  target_destroy. Despite lacking symbols, we managed to examine the
  virtio_scsi_target_state to see that the 'reqs' counter was invalid:

  (gdb) p *(struct virtio_scsi_target_state  *)starget->hostdata
  $6 = {tgt_seq = {sequence = 0}, reqs = {counter = -1}, req_vq = 
0x88022cbdd9e8}
  (gdb)

  This drew our attention to the following patch which is exclusive to the 
Ubuntu kernel:
  commit f1f609d8015e1d34d39458924dcd9524fccd4307
  Author: Jay Vosburgh 
  Date:   Thu Apr 19 21:40:00 2018 +0200

  In a nutshell, the patch spins on the target's 'reqs' counter waiting for the 
target to quiesce:
  --- a/drivers/scsi/virtio_scsi.c
  +++ b/drivers/scsi/virtio_scsi.c
  @@ -785,6 +785,10 @@ static int virtscsi_target_alloc(struct scsi_target 
*starget)
   static void virtscsi_target_destroy(struct scsi_target *starget)
   {
  struct virtio_scsi_target_state *tgt = starget->hostdata;
  +
  +   /* we can race with concurrent virtscsi_complete_cmd */
  +   while (atomic_read(>reqs))
  +   cpu_relax();
  kfree(tgt);
   }

  Personally, I think this is a catastrophic way of waiting for a target
  to quiesce since virtscsi_target_destroy() is called with IRQs
  disabled from scsi_scan.c:scsi_target_destroy(). Devices which take a
  long time to quiesce during a target_destroy() could hog the CPU for
  relatively long periods of time.

  Nevertheless, further study revealed that virtio-scsi itself is broken
  in a way that it doesn't increment the 'reqs' counter when submitting
  requests on MQ in certain conditions. That caused the counter to go to
  -1 (on the completion of the first request) and the CPU to hang
  indefinitely.

  The following patch fixes the issue:

  --- new/linux-4.4.0/drivers/scsi/virtio_scsi.c2018-06-05 
10:03:29.083428545 -0700
  +++ old/linux-4.4.0/drivers/scsi/virtio_scsi.c2018-06-04 
10:23:07.0 -0700
  @@ -641,10 +641,9 @@
  scsi_target(sc->device)->hostdata;
  struct virtio_scsi_vq *req_vq;

  -   if (shost_use_blk_mq(sh)) {
  +   if (shost_use_blk_mq(sh))
  req_vq = virtscsi_pick_vq_mq(vscsi, sc);
  -   atomic_inc(>reqs);
  -   } else
  +   else
  req_vq = virtscsi_pick_vq(vscsi, tgt);

  return virtscsi_queuecommand(vscsi, req_vq, sc);

  Signed-off-by: Felipe Franciosi 

  
  Please consider this a urgent fix as all of our customers which use Ubuntu 
16.04 and have MQ enabled for better performance will be affected by your 
latest update. Our workaround is to recommend that they disable SCSI MQ while 
you work on the issue.

  Best regards,
  Felipe

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

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


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

2018-06-05 Thread bugproxy
--- Comment From cdead...@us.ibm.com 2018-06-05 14:35 EDT---
 State: Working by: yadlapat on 05 June 2018 13:32:15 

Opened https://w3.rchland.ibm.com/projects/bestquest/?defect=SW432166 to
track if this patch is needed for Pegas

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

Title:
  IPL: ppc64_cpu --frequency hang with INFO: rcu_sched detected stalls
  on CPUs/tasks on w34 and wsbmc016 with 920.1714.20170330n

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  == Comment: #0 - Application Cdeadmin <> - 2018-05-22 09:36:12 ==

  == Comment: #1 - Application Cdeadmin <> - 2018-05-22 09:36:14 ==
   State: Open by: swanman on 22 May 2018 09:17:33 

  Both w34 and wsbmc016 are stopped on this failure, where we get hung
  up on the following FFDC gathering step in the OS:

  #(CDT) 2018/05/22 05:07:19.398218 - 0.211662 - Issuing: OS Execute Command 
ppc64_cpu --frequency ignore_err=1
  #(CDT) 2018/05/22 05:07:19.437808 - 0.024108 - Issuing: ppc64_cpu --frequency 

  , and the last console output shows:
  # tail -200 /var/log/obmc-console.log 
  s this GP) idle=82a/140/0 softirq=2689/2689 fqs=241989 
  [13668.719850]  (detected by 3, t=3075620 jiffies, g=30289, c=30288, q=796881)
  [13732.630691] INFO: rcu_sched detected stalls on CPUs/tasks:
  [13732.630727]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=242996 
  [13732.630757]  (detected by 3, t=3091597 jiffies, g=30289, c=30288, q=799822)
  [13795.649568] INFO: rcu_sched detected stalls on CPUs/tasks:
  [13795.649597]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=243942 
  [13795.649631]  (detected by 7, t=3107351 jiffies, g=30289, c=30288, q=802916)
  [13860.140483] INFO: rcu_sched detected stalls on CPUs/tasks:
  [13860.140516]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=244940 
  [13860.140557]  (detected by 3, t=3123473 jiffies, g=30289, c=30288, q=806646)
  [13924.731404] INFO: rcu_sched detected stalls on CPUs/tasks:
  [13924.731438]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=245874 
  [13924.731484]  (detected by 3, t=3139620 jiffies, g=30289, c=30288, q=809909)
  [13988.642290] INFO: rcu_sched detected stalls on CPUs/tasks:
  [13988.642321]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=246892 
  [13988.642362]  (detected by 3, t=3155596 jiffies, g=30289, c=30288, q=813048)
  [14052.661176] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14052.661211]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=247857 
  [14052.661266]  (detected by 3, t=3171600 jiffies, g=30289, c=30288, q=816185)
  [14115.680024] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14115.680051]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=248819 
  [14115.680085]  (detected by 4, t=3187355 jiffies, g=30289, c=30288, q=819190)
  [14180.154911] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14180.154945]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=249833 
  [14180.154986]  (detected by 132, t=3203473 jiffies, g=30289, c=30288, 
q=822138)
  [14244.968067]I F: Ne talls onCPUs/tasks
  [14244669838]   75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=2[14244.669944]  (detected by 3, t=3219600 jiffies, 
g=30289, c=30288, q=825384)
  [14308.748680] Id detected stalls on CPUs/tasks:
  [14308.748719]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=251755 
  [14308.748755]  (detected by 3, t=3235620 jiffies, g=30289, c=30288, q=828445)
  [14333.081775] Watchdog CPU:132 Hard LOCKUP
  [14344.750295] Watchdog CPU:132 became unstuck
  [14372.735558] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14372.735587]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=252722 
  [14372.735611]  (detected by 6, t=3251616 jiffies, g=30289, c=30288, q=831375)
  [14435.910193] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14435.910219]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=253675 
  [14435.910253]  (detected by 3, t=3267409 jiffies, g=30289, c=30288, q=834375)
  [14500.167195] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14500.167230]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=254601 
  [14500.167273]  (detected by 134, t=3283473 jiffies, g=30289, c=30288, 
q=837600)
  [14564.664395] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14564.664427]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=255493 
  [14564.664470]  

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

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

apport-collect 1775235

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

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

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

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

** Tags added: xenial

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

Title:
  Ubuntu 16.04 (4.4.0-127) hangs on boot with virtio-scsi MQ enabled

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We noticed that Ubuntu 16.04 guests running on Nutanix AHV stopped
  booting after they were upgraded to the latest kernel (4.4.0-127).
  Only guests with scsi mq enabled suffered from this problem. AHV is
  one of the few hypervisor products to offer multiqueue for virtio-scsi
  devices.

  Upon further investigation, we could see that the kernel would hang
  during the scanning of scsi targets. More specifically, immediately
  after coming across a target without any luns present. That's the
  first time the kernel destroys a target (given it doesn't have luns).
  This could be confirmed with gdb (attached to qemu's gdbserver):

  #0  0xc0045039 in ?? ()
  #1  0x88022c753c98 in ?? ()
  #2  0x815d1de6 in scsi_target_destroy (starget=0x88022ad62400)
  at /build/linux-E14mqW/linux-4.4.0/drivers/scsi/scsi_scan.c:322

  This shows the guest vCPU stuck on virtio-scsi's implementation of
  target_destroy. Despite lacking symbols, we managed to examine the
  virtio_scsi_target_state to see that the 'reqs' counter was invalid:

  (gdb) p *(struct virtio_scsi_target_state  *)starget->hostdata
  $6 = {tgt_seq = {sequence = 0}, reqs = {counter = -1}, req_vq = 
0x88022cbdd9e8}
  (gdb)

  This drew our attention to the following patch which is exclusive to the 
Ubuntu kernel:
  commit f1f609d8015e1d34d39458924dcd9524fccd4307
  Author: Jay Vosburgh 
  Date:   Thu Apr 19 21:40:00 2018 +0200

  In a nutshell, the patch spins on the target's 'reqs' counter waiting for the 
target to quiesce:
  --- a/drivers/scsi/virtio_scsi.c
  +++ b/drivers/scsi/virtio_scsi.c
  @@ -785,6 +785,10 @@ static int virtscsi_target_alloc(struct scsi_target 
*starget)
   static void virtscsi_target_destroy(struct scsi_target *starget)
   {
  struct virtio_scsi_target_state *tgt = starget->hostdata;
  +
  +   /* we can race with concurrent virtscsi_complete_cmd */
  +   while (atomic_read(>reqs))
  +   cpu_relax();
  kfree(tgt);
   }

  Personally, I think this is a catastrophic way of waiting for a target
  to quiesce since virtscsi_target_destroy() is called with IRQs
  disabled from scsi_scan.c:scsi_target_destroy(). Devices which take a
  long time to quiesce during a target_destroy() could hog the CPU for
  relatively long periods of time.

  Nevertheless, further study revealed that virtio-scsi itself is broken
  in a way that it doesn't increment the 'reqs' counter when submitting
  requests on MQ in certain conditions. That caused the counter to go to
  -1 (on the completion of the first request) and the CPU to hang
  indefinitely.

  The following patch fixes the issue:

  --- new/linux-4.4.0/drivers/scsi/virtio_scsi.c2018-06-05 
10:03:29.083428545 -0700
  +++ old/linux-4.4.0/drivers/scsi/virtio_scsi.c2018-06-04 
10:23:07.0 -0700
  @@ -641,10 +641,9 @@
  scsi_target(sc->device)->hostdata;
  struct virtio_scsi_vq *req_vq;

  -   if (shost_use_blk_mq(sh)) {
  +   if (shost_use_blk_mq(sh))
  req_vq = virtscsi_pick_vq_mq(vscsi, sc);
  -   atomic_inc(>reqs);
  -   } else
  +   else
  req_vq = virtscsi_pick_vq(vscsi, tgt);

  return virtscsi_queuecommand(vscsi, req_vq, sc);

  Signed-off-by: Felipe Franciosi 

  
  Please consider this a urgent fix as all of our customers which use Ubuntu 
16.04 and have MQ enabled for better performance will be affected by your 
latest update. Our workaround is to recommend that they disable SCSI MQ while 
you work on the issue.

  Best regards,
  Felipe

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

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


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

2018-06-05 Thread bugproxy
--- Comment From bren...@br.ibm.com 2018-06-05 14:15 EDT---
hi David,

> The failure was intermittent.  Automated tests are running on the system.
> Time will tell if this resolves the issue.

Any update on the failures?

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

Title:
  IPL: ppc64_cpu --frequency hang with INFO: rcu_sched detected stalls
  on CPUs/tasks on w34 and wsbmc016 with 920.1714.20170330n

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  == Comment: #0 - Application Cdeadmin <> - 2018-05-22 09:36:12 ==

  == Comment: #1 - Application Cdeadmin <> - 2018-05-22 09:36:14 ==
   State: Open by: swanman on 22 May 2018 09:17:33 

  Both w34 and wsbmc016 are stopped on this failure, where we get hung
  up on the following FFDC gathering step in the OS:

  #(CDT) 2018/05/22 05:07:19.398218 - 0.211662 - Issuing: OS Execute Command 
ppc64_cpu --frequency ignore_err=1
  #(CDT) 2018/05/22 05:07:19.437808 - 0.024108 - Issuing: ppc64_cpu --frequency 

  , and the last console output shows:
  # tail -200 /var/log/obmc-console.log 
  s this GP) idle=82a/140/0 softirq=2689/2689 fqs=241989 
  [13668.719850]  (detected by 3, t=3075620 jiffies, g=30289, c=30288, q=796881)
  [13732.630691] INFO: rcu_sched detected stalls on CPUs/tasks:
  [13732.630727]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=242996 
  [13732.630757]  (detected by 3, t=3091597 jiffies, g=30289, c=30288, q=799822)
  [13795.649568] INFO: rcu_sched detected stalls on CPUs/tasks:
  [13795.649597]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=243942 
  [13795.649631]  (detected by 7, t=3107351 jiffies, g=30289, c=30288, q=802916)
  [13860.140483] INFO: rcu_sched detected stalls on CPUs/tasks:
  [13860.140516]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=244940 
  [13860.140557]  (detected by 3, t=3123473 jiffies, g=30289, c=30288, q=806646)
  [13924.731404] INFO: rcu_sched detected stalls on CPUs/tasks:
  [13924.731438]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=245874 
  [13924.731484]  (detected by 3, t=3139620 jiffies, g=30289, c=30288, q=809909)
  [13988.642290] INFO: rcu_sched detected stalls on CPUs/tasks:
  [13988.642321]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=246892 
  [13988.642362]  (detected by 3, t=3155596 jiffies, g=30289, c=30288, q=813048)
  [14052.661176] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14052.661211]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=247857 
  [14052.661266]  (detected by 3, t=3171600 jiffies, g=30289, c=30288, q=816185)
  [14115.680024] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14115.680051]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=248819 
  [14115.680085]  (detected by 4, t=3187355 jiffies, g=30289, c=30288, q=819190)
  [14180.154911] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14180.154945]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=249833 
  [14180.154986]  (detected by 132, t=3203473 jiffies, g=30289, c=30288, 
q=822138)
  [14244.968067]I F: Ne talls onCPUs/tasks
  [14244669838]   75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=2[14244.669944]  (detected by 3, t=3219600 jiffies, 
g=30289, c=30288, q=825384)
  [14308.748680] Id detected stalls on CPUs/tasks:
  [14308.748719]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=251755 
  [14308.748755]  (detected by 3, t=3235620 jiffies, g=30289, c=30288, q=828445)
  [14333.081775] Watchdog CPU:132 Hard LOCKUP
  [14344.750295] Watchdog CPU:132 became unstuck
  [14372.735558] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14372.735587]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=252722 
  [14372.735611]  (detected by 6, t=3251616 jiffies, g=30289, c=30288, q=831375)
  [14435.910193] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14435.910219]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=253675 
  [14435.910253]  (detected by 3, t=3267409 jiffies, g=30289, c=30288, q=834375)
  [14500.167195] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14500.167230]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=254601 
  [14500.167273]  (detected by 134, t=3283473 jiffies, g=30289, c=30288, 
q=837600)
  [14564.664395] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14564.664427]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=255493 
  [14564.664470]  (detected by 3, 

[Kernel-packages] [Bug 1768139] Re: Kernel crash when booting laptop with hdmi monitor connected

2018-06-05 Thread Sandy Patterson
Timo Aaltonen:

I had tested rc7 I think for 4.17. I'm attaching the dmesg from startup
using 4.17.0 with drm.debug=0x4 too (I just tried 4.17.0).

I'll start on the unstable repo, It'll take a few days probably as I
haven't figured out how to do a really incremental build. Please let me
know if you think this won't be helpful but I assume it would be of
value.

** Attachment added: "drm.debug.0x4_4.17.0_nocrash.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768139/+attachment/5149072/+files/drm.debug.0x4_4.17.0_nocrash.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/1768139

Title:
  Kernel crash when booting laptop with hdmi monitor connected

Status in linux package in Ubuntu:
  Triaged

Bug description:
  When I boot a Dell Inspiron 7559 with an external monitor connected to
  the hdmi port, it usually shows only a blank screen after grub and I
  have to hard power off the laptop. The issue is present when the bios
  and grub are in mirror mode to both screens. I can see the following
  stack trace in journalctl:

  syslog contains:
   kernel: Missing switch case (6) in intel_prepare_dp_ddi_buffers

  This occurs with both a Dell U2515H using an HDMI cord, and a HP
  Compaq LA2405wg connected via HDMI-to-DVI adapter.

  WORKAROUND: Keep the monitor unplugged until the Ubuntu loading screen
  shows up.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 30 17:22:20 2018
  InstallationDate: Installed on 2018-04-28 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

  This is a fresh install. I have modified grub defaults to include 
"acpi_osi=!Windows 2015" But I tested without the acpi_osi parameter and see 
the same issue although the system now randomly crashes later on.
  ---
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  apatterson   1965 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=7b947b8e-de50-4ab6-b7f3-254a5dea924a
  InstallationDate: Installed on 2018-04-28 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Inspiron 7559
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=77f1cfec-1fe4-4201-9a91-9f00a5d7782b ro quiet splash 
"acpi_osi=!Windows 2015"
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/26/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 0H0CC0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd09/26/2017:svnDellInc.:pnInspiron7559:pvr1.2.5:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7559
  dmi.product.version: 1.2.5
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1775235] [NEW] Ubuntu 16.04 (4.4.0-127) hangs on boot with virtio-scsi MQ enabled

2018-06-05 Thread Felipe Franciosi
Public bug reported:

We noticed that Ubuntu 16.04 guests running on Nutanix AHV stopped
booting after they were upgraded to the latest kernel (4.4.0-127). Only
guests with scsi mq enabled suffered from this problem. AHV is one of
the few hypervisor products to offer multiqueue for virtio-scsi devices.

Upon further investigation, we could see that the kernel would hang
during the scanning of scsi targets. More specifically, immediately
after coming across a target without any luns present. That's the first
time the kernel destroys a target (given it doesn't have luns). This
could be confirmed with gdb (attached to qemu's gdbserver):

#0  0xc0045039 in ?? ()
#1  0x88022c753c98 in ?? ()
#2  0x815d1de6 in scsi_target_destroy (starget=0x88022ad62400)
at /build/linux-E14mqW/linux-4.4.0/drivers/scsi/scsi_scan.c:322

This shows the guest vCPU stuck on virtio-scsi's implementation of
target_destroy. Despite lacking symbols, we managed to examine the
virtio_scsi_target_state to see that the 'reqs' counter was invalid:

(gdb) p *(struct virtio_scsi_target_state  *)starget->hostdata
$6 = {tgt_seq = {sequence = 0}, reqs = {counter = -1}, req_vq = 
0x88022cbdd9e8}
(gdb)

This drew our attention to the following patch which is exclusive to the Ubuntu 
kernel:
commit f1f609d8015e1d34d39458924dcd9524fccd4307
Author: Jay Vosburgh 
Date:   Thu Apr 19 21:40:00 2018 +0200

In a nutshell, the patch spins on the target's 'reqs' counter waiting for the 
target to quiesce:
--- a/drivers/scsi/virtio_scsi.c
+++ b/drivers/scsi/virtio_scsi.c
@@ -785,6 +785,10 @@ static int virtscsi_target_alloc(struct scsi_target 
*starget)
 static void virtscsi_target_destroy(struct scsi_target *starget)
 {
struct virtio_scsi_target_state *tgt = starget->hostdata;
+
+   /* we can race with concurrent virtscsi_complete_cmd */
+   while (atomic_read(>reqs))
+   cpu_relax();
kfree(tgt);
 }

Personally, I think this is a catastrophic way of waiting for a target
to quiesce since virtscsi_target_destroy() is called with IRQs disabled
from scsi_scan.c:scsi_target_destroy(). Devices which take a long time
to quiesce during a target_destroy() could hog the CPU for relatively
long periods of time.

Nevertheless, further study revealed that virtio-scsi itself is broken
in a way that it doesn't increment the 'reqs' counter when submitting
requests on MQ in certain conditions. That caused the counter to go to
-1 (on the completion of the first request) and the CPU to hang
indefinitely.

The following patch fixes the issue:

--- new/linux-4.4.0/drivers/scsi/virtio_scsi.c2018-06-05 
10:03:29.083428545 -0700
+++ old/linux-4.4.0/drivers/scsi/virtio_scsi.c2018-06-04 
10:23:07.0 -0700
@@ -641,10 +641,9 @@
scsi_target(sc->device)->hostdata;
struct virtio_scsi_vq *req_vq;

-   if (shost_use_blk_mq(sh)) {
+   if (shost_use_blk_mq(sh))
req_vq = virtscsi_pick_vq_mq(vscsi, sc);
-   atomic_inc(>reqs);
-   } else
+   else
req_vq = virtscsi_pick_vq(vscsi, tgt);

return virtscsi_queuecommand(vscsi, req_vq, sc);

Signed-off-by: Felipe Franciosi 


Please consider this a urgent fix as all of our customers which use Ubuntu 
16.04 and have MQ enabled for better performance will be affected by your 
latest update. Our workaround is to recommend that they disable SCSI MQ while 
you work on the issue.

Best regards,
Felipe

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

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

Title:
  Ubuntu 16.04 (4.4.0-127) hangs on boot with virtio-scsi MQ enabled

Status in linux package in Ubuntu:
  New

Bug description:
  We noticed that Ubuntu 16.04 guests running on Nutanix AHV stopped
  booting after they were upgraded to the latest kernel (4.4.0-127).
  Only guests with scsi mq enabled suffered from this problem. AHV is
  one of the few hypervisor products to offer multiqueue for virtio-scsi
  devices.

  Upon further investigation, we could see that the kernel would hang
  during the scanning of scsi targets. More specifically, immediately
  after coming across a target without any luns present. That's the
  first time the kernel destroys a target (given it doesn't have luns).
  This could be confirmed with gdb (attached to qemu's gdbserver):

  #0  0xc0045039 in ?? ()
  #1  0x88022c753c98 in ?? ()
  #2  0x815d1de6 in scsi_target_destroy (starget=0x88022ad62400)
  at /build/linux-E14mqW/linux-4.4.0/drivers/scsi/scsi_scan.c:322

  This shows the guest vCPU stuck on virtio-scsi's implementation of
  target_destroy. Despite lacking symbols, we managed to examine the
  virtio_scsi_target_state to see that the 'reqs' counter was invalid:

  (gdb) p *(struct virtio_scsi_target_state  

[Kernel-packages] [Bug 1764645] Re: Bluetooth not working

2018-06-05 Thread Jeremy
http://bugzilla.opensuse.org/show_bug.cgi?id=1082504
Opensuse bug link

** Bug watch added: bugzilla.opensuse.org/ #1082504
   https://bugzilla.opensuse.org/show_bug.cgi?id=1082504

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

Title:
  Bluetooth not working

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

Bug description:
  I've installed the Ubuntu Bionic Beta 2 and everything works fine but
  the bluetooth (perfectly working with Xenial). In bluetooth control
  panel the slider is impossible to move to "on".

  1) Ubuntu Release (via 'lsb_release -rd')
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  2) Version of package (apt-cache policy gnome-bluetooth)
  gnome-bluetooth:
Installato: 3.28.0-2
Candidato:  3.28.0-2
Tabella versione:
   *** 3.28.0-2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen
  I expected to switch on the bluetooth.

  4) What happened instead
  Bluetooth won't switch on.

  5) Output of rfkill list is:
  0: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no
  1: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no

  6) Output of lspci -knn | grep Net -A3; lsusb; dmesg | grep -i blue is:
  03:00.0 Network controller [0280]: Qualcomm Atheros AR9462 Wireless 
  Network Adapter [168c:0034] (rev 01)
  Subsystem: Bigfoot Networks, Inc. Killer Wireless-N 1202 Half- 
  size Mini PCIe Card [1a56:2003]
  Kernel driver in use: ath9k
  Kernel modules: ath9k
  04:00.0 Ethernet controller [0200]: Qualcomm Atheros QCA8171 Gigabit 
  Ethernet [1969:10a1] (rev 10)
  Bus 002 Device 002: ID 8087:8000 Intel Corp. 
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 002: ID 8087:8008 Intel Corp. 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 04f2:b414 Chicony Electronics Co., Ltd 
  Bus 003 Device 003: ID 0cf3:3004 Atheros Communications, Inc. 
   
  AR3012 Bluetooth 4.0
  Bus 003 Device 002: ID 0b05:17c4 ASUSTek Computer, Inc. 
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [   17.715399] Bluetooth: Core ver 2.22
  [   17.715414] Bluetooth: HCI device and connection manager initialized
  [   17.715416] Bluetooth: HCI socket layer initialized
  [   17.715418] Bluetooth: L2CAP socket layer initialized
  [   17.715422] Bluetooth: SCO socket layer initialized
  [   17.723207] Bluetooth: hci0: don't support firmware rome 0x1102
  [   18.600648] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   18.600649] Bluetooth: BNEP filters: protocol multicast
  [   18.600651] Bluetooth: BNEP socket layer initialized

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stormy 1484 F pulseaudio
   /dev/snd/controlC0:  stormy 1484 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 17 08:46:30 2018
  HibernationDevice: RESUME=UUID=3f513ca9-6817-4099-9718-fee68d68ec11
  InstallationDate: Installed on 2018-04-16 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  MachineType: ASUSTeK COMPUTER INC. G750JH
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-15-generic N/A
   linux-backports-modules-4.15.0-15-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G750JH.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G750JH
  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.:bvrG750JH.206:bd12/02/2013:svnASUSTeKCOMPUTERINC.:pnG750JH:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG750JH:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  

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

2018-06-05 Thread linux64kb
apport information

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

Title:
  hwinfo --framebuffer | VirtualBox 5.2.12 | empty output

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 4.15.0-22.24-generic 4.15.17; Description:Ubuntu 18.04 LTS 
Release:18.04
  2) lspci-vnvn+hwinfo_policy.log attached
  3) What happens: The command "sudo hwinfo --framebuffer" provides an empty 
output. (Possibly can't find framebuffer info.)
  4) Expected: a list of supported video modes 
(https://askubuntu.com/a/824182/621093)

  Some additional info
  A) Enviroment:
  A1) Ubuntu 18.04 server
  A2) VirtualBox 5.2.12; installing guest packages and host extensions didn't 
help.
  B) VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox 
Graphics Adapter
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-22-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=UUID=2a72b513-4a62-11e8-b10a-080027d89d39 ro 
keyboard-configuration/layoutcode=hu
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


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

2018-06-05 Thread linux64kb
apport information

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

Title:
  hwinfo --framebuffer | VirtualBox 5.2.12 | empty output

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 4.15.0-22.24-generic 4.15.17; Description:Ubuntu 18.04 LTS 
Release:18.04
  2) lspci-vnvn+hwinfo_policy.log attached
  3) What happens: The command "sudo hwinfo --framebuffer" provides an empty 
output. (Possibly can't find framebuffer info.)
  4) Expected: a list of supported video modes 
(https://askubuntu.com/a/824182/621093)

  Some additional info
  A) Enviroment:
  A1) Ubuntu 18.04 server
  A2) VirtualBox 5.2.12; installing guest packages and host extensions didn't 
help.
  B) VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox 
Graphics Adapter
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-22-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=UUID=2a72b513-4a62-11e8-b10a-080027d89d39 ro 
keyboard-configuration/layoutcode=hu
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


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

2018-06-05 Thread linux64kb
apport information

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

Title:
  hwinfo --framebuffer | VirtualBox 5.2.12 | empty output

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 4.15.0-22.24-generic 4.15.17; Description:Ubuntu 18.04 LTS 
Release:18.04
  2) lspci-vnvn+hwinfo_policy.log attached
  3) What happens: The command "sudo hwinfo --framebuffer" provides an empty 
output. (Possibly can't find framebuffer info.)
  4) Expected: a list of supported video modes 
(https://askubuntu.com/a/824182/621093)

  Some additional info
  A) Enviroment:
  A1) Ubuntu 18.04 server
  A2) VirtualBox 5.2.12; installing guest packages and host extensions didn't 
help.
  B) VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox 
Graphics Adapter
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-22-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=UUID=2a72b513-4a62-11e8-b10a-080027d89d39 ro 
keyboard-configuration/layoutcode=hu
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


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

2018-06-05 Thread linux64kb
apport information

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

Title:
  hwinfo --framebuffer | VirtualBox 5.2.12 | empty output

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 4.15.0-22.24-generic 4.15.17; Description:Ubuntu 18.04 LTS 
Release:18.04
  2) lspci-vnvn+hwinfo_policy.log attached
  3) What happens: The command "sudo hwinfo --framebuffer" provides an empty 
output. (Possibly can't find framebuffer info.)
  4) Expected: a list of supported video modes 
(https://askubuntu.com/a/824182/621093)

  Some additional info
  A) Enviroment:
  A1) Ubuntu 18.04 server
  A2) VirtualBox 5.2.12; installing guest packages and host extensions didn't 
help.
  B) VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox 
Graphics Adapter
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-22-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=UUID=2a72b513-4a62-11e8-b10a-080027d89d39 ro 
keyboard-configuration/layoutcode=hu
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


[Kernel-packages] [Bug 1774575] Card0.Codecs.codec97.0.ac97.0-0.regs.txt

2018-06-05 Thread linux64kb
apport information

** Attachment added: "Card0.Codecs.codec97.0.ac97.0-0.regs.txt"
   
https://bugs.launchpad.net/bugs/1774575/+attachment/5149062/+files/Card0.Codecs.codec97.0.ac97.0-0.regs.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/1774575

Title:
  hwinfo --framebuffer | VirtualBox 5.2.12 | empty output

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 4.15.0-22.24-generic 4.15.17; Description:Ubuntu 18.04 LTS 
Release:18.04
  2) lspci-vnvn+hwinfo_policy.log attached
  3) What happens: The command "sudo hwinfo --framebuffer" provides an empty 
output. (Possibly can't find framebuffer info.)
  4) Expected: a list of supported video modes 
(https://askubuntu.com/a/824182/621093)

  Some additional info
  A) Enviroment:
  A1) Ubuntu 18.04 server
  A2) VirtualBox 5.2.12; installing guest packages and host extensions didn't 
help.
  B) VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox 
Graphics Adapter
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-22-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=UUID=2a72b513-4a62-11e8-b10a-080027d89d39 ro 
keyboard-configuration/layoutcode=hu
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


[Kernel-packages] [Bug 1774575] PciMultimedia.txt

2018-06-05 Thread linux64kb
apport information

** Attachment added: "PciMultimedia.txt"
   
https://bugs.launchpad.net/bugs/1774575/+attachment/5149065/+files/PciMultimedia.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/1774575

Title:
  hwinfo --framebuffer | VirtualBox 5.2.12 | empty output

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 4.15.0-22.24-generic 4.15.17; Description:Ubuntu 18.04 LTS 
Release:18.04
  2) lspci-vnvn+hwinfo_policy.log attached
  3) What happens: The command "sudo hwinfo --framebuffer" provides an empty 
output. (Possibly can't find framebuffer info.)
  4) Expected: a list of supported video modes 
(https://askubuntu.com/a/824182/621093)

  Some additional info
  A) Enviroment:
  A1) Ubuntu 18.04 server
  A2) VirtualBox 5.2.12; installing guest packages and host extensions didn't 
help.
  B) VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox 
Graphics Adapter
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-22-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=UUID=2a72b513-4a62-11e8-b10a-080027d89d39 ro 
keyboard-configuration/layoutcode=hu
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


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

2018-06-05 Thread linux64kb
apport information

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

Title:
  hwinfo --framebuffer | VirtualBox 5.2.12 | empty output

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 4.15.0-22.24-generic 4.15.17; Description:Ubuntu 18.04 LTS 
Release:18.04
  2) lspci-vnvn+hwinfo_policy.log attached
  3) What happens: The command "sudo hwinfo --framebuffer" provides an empty 
output. (Possibly can't find framebuffer info.)
  4) Expected: a list of supported video modes 
(https://askubuntu.com/a/824182/621093)

  Some additional info
  A) Enviroment:
  A1) Ubuntu 18.04 server
  A2) VirtualBox 5.2.12; installing guest packages and host extensions didn't 
help.
  B) VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox 
Graphics Adapter
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-22-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=UUID=2a72b513-4a62-11e8-b10a-080027d89d39 ro 
keyboard-configuration/layoutcode=hu
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


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

2018-06-05 Thread linux64kb
apport information

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

Title:
  hwinfo --framebuffer | VirtualBox 5.2.12 | empty output

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 4.15.0-22.24-generic 4.15.17; Description:Ubuntu 18.04 LTS 
Release:18.04
  2) lspci-vnvn+hwinfo_policy.log attached
  3) What happens: The command "sudo hwinfo --framebuffer" provides an empty 
output. (Possibly can't find framebuffer info.)
  4) Expected: a list of supported video modes 
(https://askubuntu.com/a/824182/621093)

  Some additional info
  A) Enviroment:
  A1) Ubuntu 18.04 server
  A2) VirtualBox 5.2.12; installing guest packages and host extensions didn't 
help.
  B) VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox 
Graphics Adapter
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-22-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=UUID=2a72b513-4a62-11e8-b10a-080027d89d39 ro 
keyboard-configuration/layoutcode=hu
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


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

2018-06-05 Thread linux64kb
apport information

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

Title:
  hwinfo --framebuffer | VirtualBox 5.2.12 | empty output

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 4.15.0-22.24-generic 4.15.17; Description:Ubuntu 18.04 LTS 
Release:18.04
  2) lspci-vnvn+hwinfo_policy.log attached
  3) What happens: The command "sudo hwinfo --framebuffer" provides an empty 
output. (Possibly can't find framebuffer info.)
  4) Expected: a list of supported video modes 
(https://askubuntu.com/a/824182/621093)

  Some additional info
  A) Enviroment:
  A1) Ubuntu 18.04 server
  A2) VirtualBox 5.2.12; installing guest packages and host extensions didn't 
help.
  B) VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox 
Graphics Adapter
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-22-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=UUID=2a72b513-4a62-11e8-b10a-080027d89d39 ro 
keyboard-configuration/layoutcode=hu
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


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

2018-06-05 Thread linux64kb
apport information

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

Title:
  hwinfo --framebuffer | VirtualBox 5.2.12 | empty output

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 4.15.0-22.24-generic 4.15.17; Description:Ubuntu 18.04 LTS 
Release:18.04
  2) lspci-vnvn+hwinfo_policy.log attached
  3) What happens: The command "sudo hwinfo --framebuffer" provides an empty 
output. (Possibly can't find framebuffer info.)
  4) Expected: a list of supported video modes 
(https://askubuntu.com/a/824182/621093)

  Some additional info
  A) Enviroment:
  A1) Ubuntu 18.04 server
  A2) VirtualBox 5.2.12; installing guest packages and host extensions didn't 
help.
  B) VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox 
Graphics Adapter
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-22-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=UUID=2a72b513-4a62-11e8-b10a-080027d89d39 ro 
keyboard-configuration/layoutcode=hu
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


[Kernel-packages] [Bug 1774575] Card0.Codecs.codec97.0.ac97.0-0.txt

2018-06-05 Thread linux64kb
apport information

** Attachment added: "Card0.Codecs.codec97.0.ac97.0-0.txt"
   
https://bugs.launchpad.net/bugs/1774575/+attachment/5149061/+files/Card0.Codecs.codec97.0.ac97.0-0.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/1774575

Title:
  hwinfo --framebuffer | VirtualBox 5.2.12 | empty output

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 4.15.0-22.24-generic 4.15.17; Description:Ubuntu 18.04 LTS 
Release:18.04
  2) lspci-vnvn+hwinfo_policy.log attached
  3) What happens: The command "sudo hwinfo --framebuffer" provides an empty 
output. (Possibly can't find framebuffer info.)
  4) Expected: a list of supported video modes 
(https://askubuntu.com/a/824182/621093)

  Some additional info
  A) Enviroment:
  A1) Ubuntu 18.04 server
  A2) VirtualBox 5.2.12; installing guest packages and host extensions didn't 
help.
  B) VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox 
Graphics Adapter
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-22-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=UUID=2a72b513-4a62-11e8-b10a-080027d89d39 ro 
keyboard-configuration/layoutcode=hu
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


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

2018-06-05 Thread linux64kb
apport information

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

Title:
  hwinfo --framebuffer | VirtualBox 5.2.12 | empty output

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 4.15.0-22.24-generic 4.15.17; Description:Ubuntu 18.04 LTS 
Release:18.04
  2) lspci-vnvn+hwinfo_policy.log attached
  3) What happens: The command "sudo hwinfo --framebuffer" provides an empty 
output. (Possibly can't find framebuffer info.)
  4) Expected: a list of supported video modes 
(https://askubuntu.com/a/824182/621093)

  Some additional info
  A) Enviroment:
  A1) Ubuntu 18.04 server
  A2) VirtualBox 5.2.12; installing guest packages and host extensions didn't 
help.
  B) VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox 
Graphics Adapter
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-22-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=UUID=2a72b513-4a62-11e8-b10a-080027d89d39 ro 
keyboard-configuration/layoutcode=hu
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


[Kernel-packages] [Bug 1774575] Re: hwinfo --framebuffer | VirtualBox 5.2.12 | empty output

2018-06-05 Thread linux64kb
apport information

** Tags added: apport-collected uec-images

** Description changed:

  1) Ubuntu 4.15.0-22.24-generic 4.15.17; Description:Ubuntu 18.04 LTS 
Release:18.04
  2) lspci-vnvn+hwinfo_policy.log attached
  3) What happens: The command "sudo hwinfo --framebuffer" provides an empty 
output. (Possibly can't find framebuffer info.)
  4) Expected: a list of supported video modes 
(https://askubuntu.com/a/824182/621093)
  
  Some additional info
  A) Enviroment:
  A1) Ubuntu 18.04 server
  A2) VirtualBox 5.2.12; installing guest packages and host extensions didn't 
help.
  B) VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox 
Graphics Adapter
+ --- 
+ AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-22-generic.
+ AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
+ ApportVersion: 2.20.9-0ubuntu7.1
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
+ Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
+ Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
+ DistroRelease: Ubuntu 18.04
+ IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
+ Lsusb:
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+ MachineType: innotek GmbH VirtualBox
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 vboxdrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=UUID=2a72b513-4a62-11e8-b10a-080027d89d39 ro 
keyboard-configuration/layoutcode=hu
+ ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-22-generic N/A
+  linux-backports-modules-4.15.0-22-generic  N/A
+  linux-firmware 1.173.1
+ RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
+ Tags:  bionic uec-images
+ Uname: Linux 4.15.0-22-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lxd plugdev sudo
+ _MarkForUpload: True
+ dmi.bios.date: 12/01/2006
+ dmi.bios.vendor: innotek GmbH
+ dmi.bios.version: VirtualBox
+ dmi.board.name: VirtualBox
+ dmi.board.vendor: Oracle Corporation
+ dmi.board.version: 1.2
+ dmi.chassis.type: 1
+ dmi.chassis.vendor: Oracle Corporation
+ dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
+ dmi.product.family: Virtual Machine
+ dmi.product.name: VirtualBox
+ dmi.product.version: 1.2
+ dmi.sys.vendor: innotek GmbH

** Attachment added: "AlsaDevices.txt"
   
https://bugs.launchpad.net/bugs/1774575/+attachment/5149059/+files/AlsaDevices.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/1774575

Title:
  hwinfo --framebuffer | VirtualBox 5.2.12 | empty output

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 4.15.0-22.24-generic 4.15.17; Description:Ubuntu 18.04 LTS 
Release:18.04
  2) lspci-vnvn+hwinfo_policy.log attached
  3) What happens: The command "sudo hwinfo --framebuffer" provides an empty 
output. (Possibly can't find framebuffer info.)
  4) Expected: a list of supported video modes 
(https://askubuntu.com/a/824182/621093)

  Some additional info
  A) Enviroment:
  A1) Ubuntu 18.04 server
  A2) VirtualBox 5.2.12; installing guest packages and host extensions didn't 
help.
  B) VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox 
Graphics Adapter
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-22-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 

[Kernel-packages] [Bug 1775217] Re: bluetooth controller fail after suspend with USB autosuspend on XPS 13 9360

2018-06-05 Thread Joseph Salisbury
I built a test kernel with commit 596b07a9a22656493726edf1739569102bd3e136.  
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1775217

Can you test this kernel and see if it resolves this bug?

Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the 
linux-image and linux-image-extra .deb packages.
• If the test kernel is 4.15(Bionic) or newer, you need to install the 
linux-modules, linux-modules-extra and linux-image-unsigned .deb packages.

Thanks in advance!

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

Title:
  bluetooth controller fail after suspend with USB autosuspend on XPS 13
  9360

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

Bug description:
  More information here:
  https://bugzilla.redhat.com/show_bug.cgi?id=1514836

  Patch:
  
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git/commit/?id=596b07a9a22656493726edf1739569102bd3e136

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-generic 4.15.0.22.23
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  guilhem2319 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun  5 18:19:20 2018
  HibernationDevice: RESUME=UUID=bfa874ab-9c2f-4228-9fd1-51267b4ea3c3
  InstallationDate: Installed on 2018-02-26 (99 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225)
  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:e300 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic 
root=UUID=287736d3-3b35-4262-a175-3254aa366f41 ro rootflags=subvol=@ quiet 
splash i915.enable_rc6=1 i915.enable_psr=2 i915.enable_guc_loading=1 
i915.enable_guc_submission=1 i915.semaphores=1 i915.disable_power_well=0 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.2
  dmi.board.name: 02PG84
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.2:bd02/26/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn02PG84:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  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/1775217/+subscriptions

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


[Kernel-packages] [Bug 1774575] Re: hwinfo --framebuffer | VirtualBox 5.2.12 | empty output

2018-06-05 Thread linux64kb
This is working on Ubuntu 16.04 LTS.
___
which hwinfo
/usr/sbin/hwinfo
___
lsb_release -rd
Description:Ubuntu 16.04.4 LTS
Release:16.04
___
apt-cache policy hwinfo
hwinfo:
  Installed: 21.23-1
  Candidate: 21.23-1
  Version table:
 *** 21.23-1 500
500 http://hu.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
100 /var/lib/dpkg/status
___
sudo hwinfo --pci
...
10: PCI 02.0: 0300 VGA compatible controller (VGA)
  [Created at pci.366]
  Unique ID: _Znp.mHjpIGaFQV1
  SysFS ID: /devices/pci:00/:00:02.0
  SysFS BusID: :00:02.0
  Hardware Class: graphics card
  Model: "InnoTek Systemberatung VirtualBox Graphics Adapter"
  Vendor: pci 0x80ee "InnoTek Systemberatung GmbH"
  Device: pci 0xbeef "VirtualBox Graphics Adapter"
  Memory Range: 0xe000-0xe1ff (ro,non-prefetchable)
  IRQ: 18 (no events)
  I/O Ports: 0x3c0-0x3df (rw)
  Module Alias: "pci:v80EEdBEEFsvsdbc03sc00i00"
  Driver Info #0:
Driver Status: vboxvideo is active
Driver Activation Cmd: "modprobe vboxvideo"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
...

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

Title:
  hwinfo --framebuffer | VirtualBox 5.2.12 | empty output

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 4.15.0-22.24-generic 4.15.17; Description:Ubuntu 18.04 LTS 
Release:18.04
  2) lspci-vnvn+hwinfo_policy.log attached
  3) What happens: The command "sudo hwinfo --framebuffer" provides an empty 
output. (Possibly can't find framebuffer info.)
  4) Expected: a list of supported video modes 
(https://askubuntu.com/a/824182/621093)

  Some additional info
  A) Enviroment:
  A1) Ubuntu 18.04 server
  A2) VirtualBox 5.2.12; installing guest packages and host extensions didn't 
help.
  B) VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox 
Graphics Adapter

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

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


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

2018-06-05 Thread Brady Garvin
apport information

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

Title:
  No brightness controls and /sys/class/backlight empty after upgrade to
  Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter
  acpi_osi= is a workaround)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a case of "Backlight control does not work, and there are no
  entries in /sys/class/backlight" for what lspci reports as "NVIDIA
  Corporation GP106M [GeForce GTX 1060 Mobile] (rev a1)" where the
  kernel parameter acpi_osi= is a workaround.  (The workaround is also
  recorded on Ask Ubuntu at https://askubuntu.com/questions/1030526
  /brightness-on-laptop-msi-gt72vr-in-ubuntu-18-04-with-nvidia-gtx-1060
  -mobile-does/1043598#1043598.)

  The problem is new for me after upgrade to Bionic, although the cause
  might be the corresponding update to the NVIDIA drivers.

  I will add attachments following the instructions at
  https://wiki.ubuntu.com/Kernel/Debugging/Backlight, though most of
  them seem to be uninteresting.  If I can provide further information,
  please let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  4 14:20:34 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-06-04 (0 days ago)
  --- 
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bgarvin2442 F pulseaudio
   /dev/snd/controlC0:  bgarvin2442 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1b60cccb-eea7-4d0b-a32b-97d236a5177f
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b5a7 Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76, Inc. Oryx Pro
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=557ebdfc-3380-4721-a494-65c34cb70b2f ro i8042.nomux i8042.reset 
acpi_osi=
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-06-04 (1 days ago)
  UserGroups: adm lpadmin sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 09/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.03RSA
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76, Inc.
  dmi.board.version: oryp2
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.03RSA:bd09/08/2016:svnSystem76,Inc.:pnOryxPro:pvroryp2:rvnSystem76,Inc.:rnOryxPro:rvroryp2:cvnSystem76,Inc.:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.version: oryp2
  dmi.sys.vendor: System76, Inc.

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

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


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

2018-06-05 Thread Brady Garvin
apport information

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

Title:
  No brightness controls and /sys/class/backlight empty after upgrade to
  Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter
  acpi_osi= is a workaround)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a case of "Backlight control does not work, and there are no
  entries in /sys/class/backlight" for what lspci reports as "NVIDIA
  Corporation GP106M [GeForce GTX 1060 Mobile] (rev a1)" where the
  kernel parameter acpi_osi= is a workaround.  (The workaround is also
  recorded on Ask Ubuntu at https://askubuntu.com/questions/1030526
  /brightness-on-laptop-msi-gt72vr-in-ubuntu-18-04-with-nvidia-gtx-1060
  -mobile-does/1043598#1043598.)

  The problem is new for me after upgrade to Bionic, although the cause
  might be the corresponding update to the NVIDIA drivers.

  I will add attachments following the instructions at
  https://wiki.ubuntu.com/Kernel/Debugging/Backlight, though most of
  them seem to be uninteresting.  If I can provide further information,
  please let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  4 14:20:34 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-06-04 (0 days ago)
  --- 
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bgarvin2442 F pulseaudio
   /dev/snd/controlC0:  bgarvin2442 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1b60cccb-eea7-4d0b-a32b-97d236a5177f
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b5a7 Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76, Inc. Oryx Pro
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=557ebdfc-3380-4721-a494-65c34cb70b2f ro i8042.nomux i8042.reset 
acpi_osi=
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-06-04 (1 days ago)
  UserGroups: adm lpadmin sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 09/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.03RSA
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76, Inc.
  dmi.board.version: oryp2
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.03RSA:bd09/08/2016:svnSystem76,Inc.:pnOryxPro:pvroryp2:rvnSystem76,Inc.:rnOryxPro:rvroryp2:cvnSystem76,Inc.:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.version: oryp2
  dmi.sys.vendor: System76, Inc.

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

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


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

2018-06-05 Thread Brady Garvin
apport information

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

Title:
  No brightness controls and /sys/class/backlight empty after upgrade to
  Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter
  acpi_osi= is a workaround)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a case of "Backlight control does not work, and there are no
  entries in /sys/class/backlight" for what lspci reports as "NVIDIA
  Corporation GP106M [GeForce GTX 1060 Mobile] (rev a1)" where the
  kernel parameter acpi_osi= is a workaround.  (The workaround is also
  recorded on Ask Ubuntu at https://askubuntu.com/questions/1030526
  /brightness-on-laptop-msi-gt72vr-in-ubuntu-18-04-with-nvidia-gtx-1060
  -mobile-does/1043598#1043598.)

  The problem is new for me after upgrade to Bionic, although the cause
  might be the corresponding update to the NVIDIA drivers.

  I will add attachments following the instructions at
  https://wiki.ubuntu.com/Kernel/Debugging/Backlight, though most of
  them seem to be uninteresting.  If I can provide further information,
  please let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  4 14:20:34 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-06-04 (0 days ago)
  --- 
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bgarvin2442 F pulseaudio
   /dev/snd/controlC0:  bgarvin2442 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1b60cccb-eea7-4d0b-a32b-97d236a5177f
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b5a7 Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76, Inc. Oryx Pro
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=557ebdfc-3380-4721-a494-65c34cb70b2f ro i8042.nomux i8042.reset 
acpi_osi=
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-06-04 (1 days ago)
  UserGroups: adm lpadmin sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 09/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.03RSA
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76, Inc.
  dmi.board.version: oryp2
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.03RSA:bd09/08/2016:svnSystem76,Inc.:pnOryxPro:pvroryp2:rvnSystem76,Inc.:rnOryxPro:rvroryp2:cvnSystem76,Inc.:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.version: oryp2
  dmi.sys.vendor: System76, Inc.

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

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


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

2018-06-05 Thread Brady Garvin
apport information

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

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

Title:
  No brightness controls and /sys/class/backlight empty after upgrade to
  Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter
  acpi_osi= is a workaround)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a case of "Backlight control does not work, and there are no
  entries in /sys/class/backlight" for what lspci reports as "NVIDIA
  Corporation GP106M [GeForce GTX 1060 Mobile] (rev a1)" where the
  kernel parameter acpi_osi= is a workaround.  (The workaround is also
  recorded on Ask Ubuntu at https://askubuntu.com/questions/1030526
  /brightness-on-laptop-msi-gt72vr-in-ubuntu-18-04-with-nvidia-gtx-1060
  -mobile-does/1043598#1043598.)

  The problem is new for me after upgrade to Bionic, although the cause
  might be the corresponding update to the NVIDIA drivers.

  I will add attachments following the instructions at
  https://wiki.ubuntu.com/Kernel/Debugging/Backlight, though most of
  them seem to be uninteresting.  If I can provide further information,
  please let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  4 14:20:34 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-06-04 (0 days ago)
  --- 
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bgarvin2442 F pulseaudio
   /dev/snd/controlC0:  bgarvin2442 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1b60cccb-eea7-4d0b-a32b-97d236a5177f
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b5a7 Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76, Inc. Oryx Pro
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=557ebdfc-3380-4721-a494-65c34cb70b2f ro i8042.nomux i8042.reset 
acpi_osi=
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-06-04 (1 days ago)
  UserGroups: adm lpadmin sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 09/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.03RSA
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76, Inc.
  dmi.board.version: oryp2
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.03RSA:bd09/08/2016:svnSystem76,Inc.:pnOryxPro:pvroryp2:rvnSystem76,Inc.:rnOryxPro:rvroryp2:cvnSystem76,Inc.:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.version: oryp2
  dmi.sys.vendor: System76, Inc.

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

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


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

2018-06-05 Thread Brady Garvin
apport information

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

Title:
  No brightness controls and /sys/class/backlight empty after upgrade to
  Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter
  acpi_osi= is a workaround)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a case of "Backlight control does not work, and there are no
  entries in /sys/class/backlight" for what lspci reports as "NVIDIA
  Corporation GP106M [GeForce GTX 1060 Mobile] (rev a1)" where the
  kernel parameter acpi_osi= is a workaround.  (The workaround is also
  recorded on Ask Ubuntu at https://askubuntu.com/questions/1030526
  /brightness-on-laptop-msi-gt72vr-in-ubuntu-18-04-with-nvidia-gtx-1060
  -mobile-does/1043598#1043598.)

  The problem is new for me after upgrade to Bionic, although the cause
  might be the corresponding update to the NVIDIA drivers.

  I will add attachments following the instructions at
  https://wiki.ubuntu.com/Kernel/Debugging/Backlight, though most of
  them seem to be uninteresting.  If I can provide further information,
  please let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  4 14:20:34 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-06-04 (0 days ago)
  --- 
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bgarvin2442 F pulseaudio
   /dev/snd/controlC0:  bgarvin2442 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1b60cccb-eea7-4d0b-a32b-97d236a5177f
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b5a7 Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76, Inc. Oryx Pro
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=557ebdfc-3380-4721-a494-65c34cb70b2f ro i8042.nomux i8042.reset 
acpi_osi=
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-06-04 (1 days ago)
  UserGroups: adm lpadmin sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 09/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.03RSA
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76, Inc.
  dmi.board.version: oryp2
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.03RSA:bd09/08/2016:svnSystem76,Inc.:pnOryxPro:pvroryp2:rvnSystem76,Inc.:rnOryxPro:rvroryp2:cvnSystem76,Inc.:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.version: oryp2
  dmi.sys.vendor: System76, Inc.

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

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


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

2018-06-05 Thread Brady Garvin
apport information

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

Title:
  No brightness controls and /sys/class/backlight empty after upgrade to
  Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter
  acpi_osi= is a workaround)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a case of "Backlight control does not work, and there are no
  entries in /sys/class/backlight" for what lspci reports as "NVIDIA
  Corporation GP106M [GeForce GTX 1060 Mobile] (rev a1)" where the
  kernel parameter acpi_osi= is a workaround.  (The workaround is also
  recorded on Ask Ubuntu at https://askubuntu.com/questions/1030526
  /brightness-on-laptop-msi-gt72vr-in-ubuntu-18-04-with-nvidia-gtx-1060
  -mobile-does/1043598#1043598.)

  The problem is new for me after upgrade to Bionic, although the cause
  might be the corresponding update to the NVIDIA drivers.

  I will add attachments following the instructions at
  https://wiki.ubuntu.com/Kernel/Debugging/Backlight, though most of
  them seem to be uninteresting.  If I can provide further information,
  please let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  4 14:20:34 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-06-04 (0 days ago)
  --- 
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bgarvin2442 F pulseaudio
   /dev/snd/controlC0:  bgarvin2442 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1b60cccb-eea7-4d0b-a32b-97d236a5177f
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b5a7 Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76, Inc. Oryx Pro
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=557ebdfc-3380-4721-a494-65c34cb70b2f ro i8042.nomux i8042.reset 
acpi_osi=
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-06-04 (1 days ago)
  UserGroups: adm lpadmin sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 09/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.03RSA
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76, Inc.
  dmi.board.version: oryp2
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.03RSA:bd09/08/2016:svnSystem76,Inc.:pnOryxPro:pvroryp2:rvnSystem76,Inc.:rnOryxPro:rvroryp2:cvnSystem76,Inc.:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.version: oryp2
  dmi.sys.vendor: System76, Inc.

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

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


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

2018-06-05 Thread Brady Garvin
apport information

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

Title:
  No brightness controls and /sys/class/backlight empty after upgrade to
  Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter
  acpi_osi= is a workaround)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a case of "Backlight control does not work, and there are no
  entries in /sys/class/backlight" for what lspci reports as "NVIDIA
  Corporation GP106M [GeForce GTX 1060 Mobile] (rev a1)" where the
  kernel parameter acpi_osi= is a workaround.  (The workaround is also
  recorded on Ask Ubuntu at https://askubuntu.com/questions/1030526
  /brightness-on-laptop-msi-gt72vr-in-ubuntu-18-04-with-nvidia-gtx-1060
  -mobile-does/1043598#1043598.)

  The problem is new for me after upgrade to Bionic, although the cause
  might be the corresponding update to the NVIDIA drivers.

  I will add attachments following the instructions at
  https://wiki.ubuntu.com/Kernel/Debugging/Backlight, though most of
  them seem to be uninteresting.  If I can provide further information,
  please let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  4 14:20:34 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-06-04 (0 days ago)
  --- 
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bgarvin2442 F pulseaudio
   /dev/snd/controlC0:  bgarvin2442 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1b60cccb-eea7-4d0b-a32b-97d236a5177f
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b5a7 Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76, Inc. Oryx Pro
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=557ebdfc-3380-4721-a494-65c34cb70b2f ro i8042.nomux i8042.reset 
acpi_osi=
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-06-04 (1 days ago)
  UserGroups: adm lpadmin sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 09/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.03RSA
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76, Inc.
  dmi.board.version: oryp2
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.03RSA:bd09/08/2016:svnSystem76,Inc.:pnOryxPro:pvroryp2:rvnSystem76,Inc.:rnOryxPro:rvroryp2:cvnSystem76,Inc.:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.version: oryp2
  dmi.sys.vendor: System76, Inc.

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

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


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

2018-06-05 Thread Brady Garvin
apport information

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

Title:
  No brightness controls and /sys/class/backlight empty after upgrade to
  Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter
  acpi_osi= is a workaround)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a case of "Backlight control does not work, and there are no
  entries in /sys/class/backlight" for what lspci reports as "NVIDIA
  Corporation GP106M [GeForce GTX 1060 Mobile] (rev a1)" where the
  kernel parameter acpi_osi= is a workaround.  (The workaround is also
  recorded on Ask Ubuntu at https://askubuntu.com/questions/1030526
  /brightness-on-laptop-msi-gt72vr-in-ubuntu-18-04-with-nvidia-gtx-1060
  -mobile-does/1043598#1043598.)

  The problem is new for me after upgrade to Bionic, although the cause
  might be the corresponding update to the NVIDIA drivers.

  I will add attachments following the instructions at
  https://wiki.ubuntu.com/Kernel/Debugging/Backlight, though most of
  them seem to be uninteresting.  If I can provide further information,
  please let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  4 14:20:34 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-06-04 (0 days ago)
  --- 
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bgarvin2442 F pulseaudio
   /dev/snd/controlC0:  bgarvin2442 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1b60cccb-eea7-4d0b-a32b-97d236a5177f
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b5a7 Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76, Inc. Oryx Pro
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=557ebdfc-3380-4721-a494-65c34cb70b2f ro i8042.nomux i8042.reset 
acpi_osi=
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-06-04 (1 days ago)
  UserGroups: adm lpadmin sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 09/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.03RSA
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76, Inc.
  dmi.board.version: oryp2
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.03RSA:bd09/08/2016:svnSystem76,Inc.:pnOryxPro:pvroryp2:rvnSystem76,Inc.:rnOryxPro:rvroryp2:cvnSystem76,Inc.:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.version: oryp2
  dmi.sys.vendor: System76, Inc.

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

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


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

2018-06-05 Thread Brady Garvin
apport information

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

Title:
  No brightness controls and /sys/class/backlight empty after upgrade to
  Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter
  acpi_osi= is a workaround)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a case of "Backlight control does not work, and there are no
  entries in /sys/class/backlight" for what lspci reports as "NVIDIA
  Corporation GP106M [GeForce GTX 1060 Mobile] (rev a1)" where the
  kernel parameter acpi_osi= is a workaround.  (The workaround is also
  recorded on Ask Ubuntu at https://askubuntu.com/questions/1030526
  /brightness-on-laptop-msi-gt72vr-in-ubuntu-18-04-with-nvidia-gtx-1060
  -mobile-does/1043598#1043598.)

  The problem is new for me after upgrade to Bionic, although the cause
  might be the corresponding update to the NVIDIA drivers.

  I will add attachments following the instructions at
  https://wiki.ubuntu.com/Kernel/Debugging/Backlight, though most of
  them seem to be uninteresting.  If I can provide further information,
  please let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  4 14:20:34 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-06-04 (0 days ago)
  --- 
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bgarvin2442 F pulseaudio
   /dev/snd/controlC0:  bgarvin2442 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1b60cccb-eea7-4d0b-a32b-97d236a5177f
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b5a7 Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76, Inc. Oryx Pro
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=557ebdfc-3380-4721-a494-65c34cb70b2f ro i8042.nomux i8042.reset 
acpi_osi=
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-06-04 (1 days ago)
  UserGroups: adm lpadmin sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 09/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.03RSA
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76, Inc.
  dmi.board.version: oryp2
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.03RSA:bd09/08/2016:svnSystem76,Inc.:pnOryxPro:pvroryp2:rvnSystem76,Inc.:rnOryxPro:rvroryp2:cvnSystem76,Inc.:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.version: oryp2
  dmi.sys.vendor: System76, Inc.

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

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


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

2018-06-05 Thread Brady Garvin
apport information

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

Title:
  No brightness controls and /sys/class/backlight empty after upgrade to
  Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter
  acpi_osi= is a workaround)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a case of "Backlight control does not work, and there are no
  entries in /sys/class/backlight" for what lspci reports as "NVIDIA
  Corporation GP106M [GeForce GTX 1060 Mobile] (rev a1)" where the
  kernel parameter acpi_osi= is a workaround.  (The workaround is also
  recorded on Ask Ubuntu at https://askubuntu.com/questions/1030526
  /brightness-on-laptop-msi-gt72vr-in-ubuntu-18-04-with-nvidia-gtx-1060
  -mobile-does/1043598#1043598.)

  The problem is new for me after upgrade to Bionic, although the cause
  might be the corresponding update to the NVIDIA drivers.

  I will add attachments following the instructions at
  https://wiki.ubuntu.com/Kernel/Debugging/Backlight, though most of
  them seem to be uninteresting.  If I can provide further information,
  please let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  4 14:20:34 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-06-04 (0 days ago)
  --- 
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bgarvin2442 F pulseaudio
   /dev/snd/controlC0:  bgarvin2442 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1b60cccb-eea7-4d0b-a32b-97d236a5177f
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b5a7 Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76, Inc. Oryx Pro
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=557ebdfc-3380-4721-a494-65c34cb70b2f ro i8042.nomux i8042.reset 
acpi_osi=
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-06-04 (1 days ago)
  UserGroups: adm lpadmin sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 09/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.03RSA
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76, Inc.
  dmi.board.version: oryp2
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.03RSA:bd09/08/2016:svnSystem76,Inc.:pnOryxPro:pvroryp2:rvnSystem76,Inc.:rnOryxPro:rvroryp2:cvnSystem76,Inc.:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.version: oryp2
  dmi.sys.vendor: System76, Inc.

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

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


[Kernel-packages] [Bug 1775065] AlsaInfo.txt

2018-06-05 Thread Brady Garvin
apport information

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

Title:
  No brightness controls and /sys/class/backlight empty after upgrade to
  Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter
  acpi_osi= is a workaround)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a case of "Backlight control does not work, and there are no
  entries in /sys/class/backlight" for what lspci reports as "NVIDIA
  Corporation GP106M [GeForce GTX 1060 Mobile] (rev a1)" where the
  kernel parameter acpi_osi= is a workaround.  (The workaround is also
  recorded on Ask Ubuntu at https://askubuntu.com/questions/1030526
  /brightness-on-laptop-msi-gt72vr-in-ubuntu-18-04-with-nvidia-gtx-1060
  -mobile-does/1043598#1043598.)

  The problem is new for me after upgrade to Bionic, although the cause
  might be the corresponding update to the NVIDIA drivers.

  I will add attachments following the instructions at
  https://wiki.ubuntu.com/Kernel/Debugging/Backlight, though most of
  them seem to be uninteresting.  If I can provide further information,
  please let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  4 14:20:34 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-06-04 (0 days ago)
  --- 
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bgarvin2442 F pulseaudio
   /dev/snd/controlC0:  bgarvin2442 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1b60cccb-eea7-4d0b-a32b-97d236a5177f
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b5a7 Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76, Inc. Oryx Pro
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=557ebdfc-3380-4721-a494-65c34cb70b2f ro i8042.nomux i8042.reset 
acpi_osi=
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-06-04 (1 days ago)
  UserGroups: adm lpadmin sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 09/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.03RSA
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76, Inc.
  dmi.board.version: oryp2
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.03RSA:bd09/08/2016:svnSystem76,Inc.:pnOryxPro:pvroryp2:rvnSystem76,Inc.:rnOryxPro:rvroryp2:cvnSystem76,Inc.:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.version: oryp2
  dmi.sys.vendor: System76, Inc.

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

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


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

2018-06-05 Thread Brady Garvin
apport information

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

Title:
  No brightness controls and /sys/class/backlight empty after upgrade to
  Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter
  acpi_osi= is a workaround)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a case of "Backlight control does not work, and there are no
  entries in /sys/class/backlight" for what lspci reports as "NVIDIA
  Corporation GP106M [GeForce GTX 1060 Mobile] (rev a1)" where the
  kernel parameter acpi_osi= is a workaround.  (The workaround is also
  recorded on Ask Ubuntu at https://askubuntu.com/questions/1030526
  /brightness-on-laptop-msi-gt72vr-in-ubuntu-18-04-with-nvidia-gtx-1060
  -mobile-does/1043598#1043598.)

  The problem is new for me after upgrade to Bionic, although the cause
  might be the corresponding update to the NVIDIA drivers.

  I will add attachments following the instructions at
  https://wiki.ubuntu.com/Kernel/Debugging/Backlight, though most of
  them seem to be uninteresting.  If I can provide further information,
  please let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  4 14:20:34 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-06-04 (0 days ago)
  --- 
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bgarvin2442 F pulseaudio
   /dev/snd/controlC0:  bgarvin2442 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1b60cccb-eea7-4d0b-a32b-97d236a5177f
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b5a7 Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76, Inc. Oryx Pro
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=557ebdfc-3380-4721-a494-65c34cb70b2f ro i8042.nomux i8042.reset 
acpi_osi=
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-06-04 (1 days ago)
  UserGroups: adm lpadmin sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 09/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.03RSA
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76, Inc.
  dmi.board.version: oryp2
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.03RSA:bd09/08/2016:svnSystem76,Inc.:pnOryxPro:pvroryp2:rvnSystem76,Inc.:rnOryxPro:rvroryp2:cvnSystem76,Inc.:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.version: oryp2
  dmi.sys.vendor: System76, Inc.

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

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


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

2018-06-05 Thread Brady Garvin
apport information

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

Title:
  No brightness controls and /sys/class/backlight empty after upgrade to
  Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter
  acpi_osi= is a workaround)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a case of "Backlight control does not work, and there are no
  entries in /sys/class/backlight" for what lspci reports as "NVIDIA
  Corporation GP106M [GeForce GTX 1060 Mobile] (rev a1)" where the
  kernel parameter acpi_osi= is a workaround.  (The workaround is also
  recorded on Ask Ubuntu at https://askubuntu.com/questions/1030526
  /brightness-on-laptop-msi-gt72vr-in-ubuntu-18-04-with-nvidia-gtx-1060
  -mobile-does/1043598#1043598.)

  The problem is new for me after upgrade to Bionic, although the cause
  might be the corresponding update to the NVIDIA drivers.

  I will add attachments following the instructions at
  https://wiki.ubuntu.com/Kernel/Debugging/Backlight, though most of
  them seem to be uninteresting.  If I can provide further information,
  please let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  4 14:20:34 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-06-04 (0 days ago)
  --- 
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bgarvin2442 F pulseaudio
   /dev/snd/controlC0:  bgarvin2442 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1b60cccb-eea7-4d0b-a32b-97d236a5177f
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b5a7 Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76, Inc. Oryx Pro
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=557ebdfc-3380-4721-a494-65c34cb70b2f ro i8042.nomux i8042.reset 
acpi_osi=
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-06-04 (1 days ago)
  UserGroups: adm lpadmin sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 09/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.03RSA
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76, Inc.
  dmi.board.version: oryp2
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.03RSA:bd09/08/2016:svnSystem76,Inc.:pnOryxPro:pvroryp2:rvnSystem76,Inc.:rnOryxPro:rvroryp2:cvnSystem76,Inc.:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.version: oryp2
  dmi.sys.vendor: System76, Inc.

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

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


[Kernel-packages] [Bug 1775065] Re: No brightness controls and /sys/class/backlight empty after upgrade to Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter acpi_osi= is a workaround)

2018-06-05 Thread Brady Garvin
Yes, this was after an upgrade to Ubuntu 18.04 LTS (Bionic Beaver) from
Ubuntu 17.10.1 (Artful Aardvark).

The bug is fixed in the mainline kernel; I have added the appropriate
tag and marked the bug as confirmed.


** Tags added: kernel-fixed-upstream

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

** Tags added: apport-collected

** Description changed:

  This is a case of "Backlight control does not work, and there are no
  entries in /sys/class/backlight" for what lspci reports as "NVIDIA
  Corporation GP106M [GeForce GTX 1060 Mobile] (rev a1)" where the kernel
  parameter acpi_osi= is a workaround.  (The workaround is also recorded
  on Ask Ubuntu at https://askubuntu.com/questions/1030526/brightness-on-
  laptop-msi-gt72vr-in-ubuntu-18-04-with-nvidia-gtx-1060-mobile-
  does/1043598#1043598.)
  
  The problem is new for me after upgrade to Bionic, although the cause
  might be the corresponding update to the NVIDIA drivers.
  
  I will add attachments following the instructions at
  https://wiki.ubuntu.com/Kernel/Debugging/Backlight, though most of them
  seem to be uninteresting.  If I can provide further information, please
  let me know.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  4 14:20:34 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-06-04 (0 days ago)
+ --- 
+ ApportVersion: 2.20.9-0ubuntu7.1
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  bgarvin2442 F pulseaudio
+  /dev/snd/controlC0:  bgarvin2442 F pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ HibernationDevice: RESUME=UUID=1b60cccb-eea7-4d0b-a32b-97d236a5177f
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 04f2:b5a7 Chicony Electronics Co., Ltd 
+  Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
+  Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: System76, Inc. Oryx Pro
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 EFI VGA
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=557ebdfc-3380-4721-a494-65c34cb70b2f ro i8042.nomux i8042.reset 
acpi_osi=
+ ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-22-generic N/A
+  linux-backports-modules-4.15.0-22-generic  N/A
+  linux-firmware 1.173.1
+ Tags:  bionic
+ Uname: Linux 4.15.0-22-generic x86_64
+ UpgradeStatus: Upgraded to bionic on 2018-06-04 (1 days ago)
+ UserGroups: adm lpadmin sambashare sudo vboxusers
+ _MarkForUpload: True
+ dmi.bios.date: 09/08/2016
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 1.05.03RSA
+ dmi.board.asset.tag: Tag 12345
+ dmi.board.name: Oryx Pro
+ dmi.board.vendor: System76, Inc.
+ dmi.board.version: oryp2
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: System76, Inc.
+ dmi.chassis.version: N/A
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.03RSA:bd09/08/2016:svnSystem76,Inc.:pnOryxPro:pvroryp2:rvnSystem76,Inc.:rnOryxPro:rvroryp2:cvnSystem76,Inc.:ct10:cvrN/A:
+ dmi.product.family: Not Applicable
+ dmi.product.name: Oryx Pro
+ dmi.product.version: oryp2
+ dmi.sys.vendor: System76, Inc.

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

Title:
  No brightness controls and /sys/class/backlight empty after upgrade to
  Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter
  acpi_osi= is a workaround)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a case of "Backlight control does not work, and there are no
  entries in /sys/class/backlight" for what lspci reports as "NVIDIA
  Corporation GP106M [GeForce GTX 1060 Mobile] (rev a1)" where the
  kernel parameter acpi_osi= is a workaround.  (The workaround is also
  recorded on Ask Ubuntu at https://askubuntu.com/questions/1030526
  /brightness-on-laptop-msi-gt72vr-in-ubuntu-18-04-with-nvidia-gtx-1060
  -mobile-does/1043598#1043598.)

  The problem is new for me after upgrade to Bionic, although the cause
  might be the corresponding update to the NVIDIA drivers.

  I will add attachments following the 

[Kernel-packages] [Bug 1772963] Re: linux-aws: 4.4.0-1023.23 -proposed tracker

2018-06-05 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => 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/1772963

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

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

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


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

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

apport-collect 1775150

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

Title:
  screen flickering getting black and blinking while booting in ubuntu
  17.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  screen is getting black and starting flickering qnd keeping awaited
  forfewmins before ligin page appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun  5 15:06:51 2018
  InstallationDate: Installed on 2018-06-04 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

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

apport-collect 1775124

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

Title:
  static noise at login and after screen blanking

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  At the login screen, and after screen blanking, there often (but not
  always) is loud static noise from the screen's speaker.

  In the login-screen, it stops after logging in.

  After turning the screen back on after blanking (my system settings
  have "Screen energy saving: Switch off after 10 min" set and "Suspend"
  disabled), there is the same static noise. One way I found to make is
  disappear is to invoke "pavucontrol". As soon as it opens, the noise
  is gone.

  Seems to me like some gain setting or the like is not properly
  (re)initialized after screen blanking. Strangely enough, pavucontrol
  seems to fix this by just starting, with no further user interaction.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Jun  5 08:01:58 2018
  InstallationDate: Installed on 2018-06-01 (3 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

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

apport-collect 1775065

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

Title:
  No brightness controls and /sys/class/backlight empty after upgrade to
  Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter
  acpi_osi= is a workaround)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a case of "Backlight control does not work, and there are no
  entries in /sys/class/backlight" for what lspci reports as "NVIDIA
  Corporation GP106M [GeForce GTX 1060 Mobile] (rev a1)" where the
  kernel parameter acpi_osi= is a workaround.  (The workaround is also
  recorded on Ask Ubuntu at https://askubuntu.com/questions/1030526
  /brightness-on-laptop-msi-gt72vr-in-ubuntu-18-04-with-nvidia-gtx-1060
  -mobile-does/1043598#1043598.)

  The problem is new for me after upgrade to Bionic, although the cause
  might be the corresponding update to the NVIDIA drivers.

  I will add attachments following the instructions at
  https://wiki.ubuntu.com/Kernel/Debugging/Backlight, though most of
  them seem to be uninteresting.  If I can provide further information,
  please let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  4 14:20:34 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-06-04 (0 days ago)

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

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


[Kernel-packages] [Bug 1775065] Re: No brightness controls and /sys/class/backlight empty after upgrade to Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter acpi_osi= is a workaround)

2018-06-05 Thread Brady Garvin
Yes, this was after an upgrade to Ubuntu 18.04 LTS (Bionic Beaver) from
Ubuntu 17.10.1 (Artful Aardvark).

I will test with the latest upstream kernel.

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

Title:
  No brightness controls and /sys/class/backlight empty after upgrade to
  Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter
  acpi_osi= is a workaround)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is a case of "Backlight control does not work, and there are no
  entries in /sys/class/backlight" for what lspci reports as "NVIDIA
  Corporation GP106M [GeForce GTX 1060 Mobile] (rev a1)" where the
  kernel parameter acpi_osi= is a workaround.  (The workaround is also
  recorded on Ask Ubuntu at https://askubuntu.com/questions/1030526
  /brightness-on-laptop-msi-gt72vr-in-ubuntu-18-04-with-nvidia-gtx-1060
  -mobile-does/1043598#1043598.)

  The problem is new for me after upgrade to Bionic, although the cause
  might be the corresponding update to the NVIDIA drivers.

  I will add attachments following the instructions at
  https://wiki.ubuntu.com/Kernel/Debugging/Backlight, though most of
  them seem to be uninteresting.  If I can provide further information,
  please let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  4 14:20:34 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-06-04 (0 days ago)

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

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


[Kernel-packages] [Bug 1775217] Re: bluetooth controller fail after suspend with USB autosuspend on XPS 13 9360

2018-06-05 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

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

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

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

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

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

Title:
  bluetooth controller fail after suspend with USB autosuspend on XPS 13
  9360

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

Bug description:
  More information here:
  https://bugzilla.redhat.com/show_bug.cgi?id=1514836

  Patch:
  
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git/commit/?id=596b07a9a22656493726edf1739569102bd3e136

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-generic 4.15.0.22.23
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  guilhem2319 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun  5 18:19:20 2018
  HibernationDevice: RESUME=UUID=bfa874ab-9c2f-4228-9fd1-51267b4ea3c3
  InstallationDate: Installed on 2018-02-26 (99 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225)
  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:e300 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic 
root=UUID=287736d3-3b35-4262-a175-3254aa366f41 ro rootflags=subvol=@ quiet 
splash i915.enable_rc6=1 i915.enable_psr=2 i915.enable_guc_loading=1 
i915.enable_guc_submission=1 i915.semaphores=1 i915.disable_power_well=0 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.2
  dmi.board.name: 02PG84
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.2:bd02/26/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn02PG84:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  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/1775217/+subscriptions

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


[Kernel-packages] [Bug 1775166] Re: NETDEV WATCHDOG: usb0 (cdc_ether): transmit queue 0 timed out

2018-06-05 Thread Joseph Salisbury
The 2.6.37 kernel is not supported in any Ubuntu releases.  Does this
bug exist on any supported kernels?  Maybe give the current mainline
kernel a try?

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

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

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

Title:
  NETDEV WATCHDOG: usb0 (cdc_ether): transmit queue 0 timed out

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello Team

  We are using linux kernel 2.6.37 due to Hardware dependency. while
  transmitting data (.json, .mp4, .jpeg) using curl we are facing
  following following issue randomly in a week:

  Mar 19 22:01:55 RO402355_V4 user.warn kernel: [ cut here 
]
  Mar 19 22:01:55 RO402355_V4 user.warn kernel: WARNING: at 
net/sched/sch_generic.c:258 dev_watchdog+0x148/0x230()
  Mar 19 22:01:55 RO402355_V4 user.info kernel: NETDEV WATCHDOG: usb0 
(cdc_ether): transmit queue 0 timed out
  Mar 19 22:01:55 RO402355_V4 user.warn kernel: Modules linked in: ti81xxhdmi 
vpss osa_kermod syslink temp_sens_udu mxc_mma adxl37x_i2c adxl37x
  Mar 19 22:01:55 RO402355_V4 user.warn kernel: Backtrace: 
  Mar 19 22:01:55 RO402355_V4 user.warn kernel: [] 
(dump_backtrace+0x0/0x110) from [] (dump_stack+0x18/0x1c)
  Mar 19 22:01:55 RO402355_V4 user.warn kernel:  r6:c0667f1f r5:0102 
r4:ea07fe88 r3:6113
  Mar 19 22:01:55 RO402355_V4 user.warn kernel: [] 
(dump_stack+0x0/0x1c) from [] (warn_slowpath_common+0x54/0x6c)
  Mar 19 22:01:55 RO402355_V4 user.warn kernel: [] 
(warn_slowpath_common+0x0/0x6c) from [] (warn_slowpath_fmt+0x38/0x40)
  Mar 19 22:01:55 RO402355_V4 user.warn kernel:  r8:c0441f5c r7:0100 
r6: r5:c0732778 r4:eaa64000
  Mar 19 22:01:55 RO402355_V4 user.warn kernel: r3:0009
  Mar 19 22:01:55 RO402355_V4 user.warn kernel: [] 
(warn_slowpath_fmt+0x0/0x40) from [] (dev_watchdog+0x148/0x230)
  Mar 19 22:01:55 RO402355_V4 user.warn kernel:  r3:eaa64000 r2:c0667f37
  Mar 19 22:01:55 RO402355_V4 user.warn kernel: [] 
(dev_watchdog+0x0/0x230) from [] (run_timer_softirq+0x130/0x1c8)
  Mar 19 22:01:55 RO402355_V4 user.warn kernel:  r6:0100 r5:ea07e000 
r4:c0714a40
  Mar 19 22:01:55 RO402355_V4 user.warn kernel: [] 
(run_timer_softirq+0x0/0x1c8) from [] (__do_softirq+0x84/0x114)
  Mar 19 22:01:55 RO402355_V4 user.warn kernel: [] 
(__do_softirq+0x0/0x114) from [] (irq_exit+0x48/0x98)
  Mar 19 22:01:55 RO402355_V4 user.warn kernel: [] 
(irq_exit+0x0/0x98) from [] (asm_do_IRQ+0x7c/0x9c)
  Mar 19 22:01:55 RO402355_V4 user.warn kernel: [] 
(asm_do_IRQ+0x0/0x9c) from [] (__irq_usr+0x3c/0xa0)
  Mar 19 22:01:55 RO402355_V4 user.warn kernel: Exception stack(0xea07ffb0 to 
0xea07fff8)
  Mar 19 22:01:55 RO402355_V4 user.warn kernel: ffa0:   
  41bd92d9 41bd9307 0070 41bd9306
  Mar 19 22:01:55 RO402355_V4 user.warn kernel: ffc0: 41bd9306 0020 
0009 000a 005c 41bd92d5  00ff
  Mar 19 22:01:55 RO402355_V4 user.warn kernel: ffe0: 0070 41bd8e78 
401da59c 401da030 2010 
  Mar 19 22:01:55 RO402355_V4 user.warn kernel:  r5:fa20 r4:
  Mar 19 22:01:55 RO402355_V4 user.warn kernel: ---[ end trace c6866a34f1f582f4 
]---

  
  We have tried to find out root cause but still not getting cause and solution.
  Let me know if any..

  Thank you

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

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


[Kernel-packages] [Bug 1775065] Re: No brightness controls and /sys/class/backlight empty after upgrade to Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter acpi_osi= is a workaround)

2018-06-05 Thread Joseph Salisbury
Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 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.17


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

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

** Tags added: kernel-da-key

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

Title:
  No brightness controls and /sys/class/backlight empty after upgrade to
  Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter
  acpi_osi= is a workaround)

Status in linux package in Ubuntu:
  New

Bug description:
  This is a case of "Backlight control does not work, and there are no
  entries in /sys/class/backlight" for what lspci reports as "NVIDIA
  Corporation GP106M [GeForce GTX 1060 Mobile] (rev a1)" where the
  kernel parameter acpi_osi= is a workaround.  (The workaround is also
  recorded on Ask Ubuntu at https://askubuntu.com/questions/1030526
  /brightness-on-laptop-msi-gt72vr-in-ubuntu-18-04-with-nvidia-gtx-1060
  -mobile-does/1043598#1043598.)

  The problem is new for me after upgrade to Bionic, although the cause
  might be the corresponding update to the NVIDIA drivers.

  I will add attachments following the instructions at
  https://wiki.ubuntu.com/Kernel/Debugging/Backlight, though most of
  them seem to be uninteresting.  If I can provide further information,
  please let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  4 14:20:34 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-06-04 (0 days ago)

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

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


[Kernel-packages] [Bug 1775150] Re: screen flickering getting black and blinking while booting in ubuntu 17.04

2018-06-05 Thread Joseph Salisbury
Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 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.17


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

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

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

Title:
  screen flickering getting black and blinking while booting in ubuntu
  17.04

Status in linux package in Ubuntu:
  New

Bug description:
  screen is getting black and starting flickering qnd keeping awaited
  forfewmins before ligin page appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun  5 15:06:51 2018
  InstallationDate: Installed on 2018-06-04 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1775165] Re: fanotify07 in LTP syscall test generates kernel trace with T kernel

2018-06-05 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

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

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

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

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

Title:
  fanotify07 in LTP syscall test generates kernel trace with T kernel

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Triaged

Bug description:
  The "fanotify07" from the LTP syscall tests has failed on a testing
  node with Trusty kernel installed.

  Steps (with root):
1. sudo apt-get install git xfsprogs -y
2. git clone --depth=1 https://github.com/linux-test-project/ltp.git
3. cd ltp
4. make autotools
5. ./configure
6. make; make install
7. cd /opt/ltp
8. echo "fanotify07 fanotify07" > /tmp/jobs
9. ./runltp -f /tmp/jobs

  <<>>
  tag=fanotify07 stime=1528197132
  cmdline="fanotify07"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Cannot kill test processes!
  Congratulation, likely test hit a kernel bug.
  Exitting uncleanly...
  <<>>
  initiation_status="ok"
  duration=350 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=0
  <<>>
  INFO: ltp-pan reported some tests FAIL
  LTP Version: 20180515

  [  841.063676] INFO: task fanotify07:3660 blocked for more than 120 seconds.
  [  841.063692]   Not tainted 3.13.0-149-generic #199-Ubuntu
  [  841.063705] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  841.063723] fanotify07  D 8804584742f0 0  3660   3652 
0x
  [  841.063724]  880459e9bd00 0086 88045556b000 
00013b00
  [  841.063726]  880459e9bfd8 00013b00 88045556b000 
880459b4e690
  [  841.063728]   880458474200 8804584742f0 
0002
  [  841.063730] Call Trace:
  [  841.063731]  [] schedule+0x29/0x70
  [  841.063733]  [] fanotify_handle_event+0x110/0x1d0
  [  841.063735]  [] ? prepare_to_wait_event+0x100/0x100
  [  841.063737]  [] send_to_group+0x166/0x240
  [  841.063738]  [] ? touch_atime+0x71/0x140
  [  841.063740]  [] fsnotify+0x2e5/0x320
  [  841.063742]  [] security_file_permission+0x94/0xb0
  [  841.063743]  [] rw_verify_area+0x52/0xd0
  [  841.063745]  [] vfs_read+0x6a/0x160
  [  841.063746]  [] SyS_read+0x49/0xa0
  [  841.063748]  [] system_call_fastpath+0x1a/0x1f
  [ 1304.848642] ltp-pan[3809]: segfault at 0 ip 7f07c8aafdfa sp 
7ffc1da92078 error 4 in libc-2.19.so[7f07c8a27000+1be000]

  dmesg: http://paste.ubuntu.com/p/FRZnV5smGh/

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-149-generic 3.13.0-149.199
  ProcVersionSignature: User Name 3.13.0-149.199-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-149-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun  5 11:01 seq
   crw-rw 1 root audio 116, 33 Jun  5 11:01 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg: [3.553366] init: plymouth-upstart-bridge main process 
ended, respawning
  Date: Tue Jun  5 11:06:45 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Intel Corporation S1200RP
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic 
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-149-generic N/A
   linux-backports-modules-3.13.0-149-generic  N/A
   linux-firmware  1.127.24
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
  dmi.board.asset.tag: 

[Kernel-packages] [Bug 1775153] Re: fanotify09 in LTP syscall test failed with A/T kernel

2018-06-05 Thread Joseph Salisbury
** Also affects: linux (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

Title:
  fanotify09 in LTP syscall test failed with A/T kernel

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  The "fanotify09" from the LTP syscall tests has failed on a testing
  node with Xenial kernel installed.

  Steps (with root):
1. sudo apt-get install git xfsprogs -y
2. git clone --depth=1 https://github.com/linux-test-project/ltp.git
3. cd ltp
4. make autotools
5. ./configure
6. make; make install
7. cd /opt/ltp
8. echo "fanotify09" > /tmp/jobs
9. ./runltp -f /tmp/jobs

  <<>>
  tag=fanotify09 stime=1528192114
  cmdline="fanotify09"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s
  fanotify09.c:134: PASS: group 0 get event: mask 2 pid=43803 fd=9
  fanotify09.c:182: FAIL: group 1 got event
  fanotify09.c:182: FAIL: group 2 got event

  Summary:
  passed   1
  failed   2
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=0
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-43-generic 4.13.0-43.48
  ProcVersionSignature: User Name 4.13.0-43.48-generic 4.13.16
  Uname: Linux 4.13.0-43-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun  5 08:30 seq
   crw-rw 1 root audio 116, 33 Jun  5 08:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.9
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Jun  5 09:14:07 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Cavium ThunderX CRB
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 EFI VGA
   1 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic 
root=UUID=ddcb8b36-6267-4392-a1f9-74d9203b742e ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-43-generic N/A
   linux-backports-modules-4.13.0-43-generic  N/A
   linux-firmware 1.169.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 0
  dmi.chassis.vendor: Cavium
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/12/2012:svnCavium:pnThunderXCRB:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnCavium:ct0:cvrTobefilledbyO.E.M.:
  dmi.product.family: Default string
  dmi.product.name: ThunderX CRB
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cavium

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

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


[Kernel-packages] [Bug 1775124] Re: static noise at login and after screen blanking

2018-06-05 Thread Joseph Salisbury
Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 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.17


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

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

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

Title:
  static noise at login and after screen blanking

Status in linux package in Ubuntu:
  New

Bug description:
  At the login screen, and after screen blanking, there often (but not
  always) is loud static noise from the screen's speaker.

  In the login-screen, it stops after logging in.

  After turning the screen back on after blanking (my system settings
  have "Screen energy saving: Switch off after 10 min" set and "Suspend"
  disabled), there is the same static noise. One way I found to make is
  disappear is to invoke "pavucontrol". As soon as it opens, the noise
  is gone.

  Seems to me like some gain setting or the like is not properly
  (re)initialized after screen blanking. Strangely enough, pavucontrol
  seems to fix this by just starting, with no further user interaction.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Jun  5 08:01:58 2018
  InstallationDate: Installed on 2018-06-01 (3 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2018-06-05 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  bluetooth controller fail after suspend with USB autosuspend on XPS 13
  9360

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

Bug description:
  More information here:
  https://bugzilla.redhat.com/show_bug.cgi?id=1514836

  Patch:
  
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git/commit/?id=596b07a9a22656493726edf1739569102bd3e136

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-generic 4.15.0.22.23
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  guilhem2319 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun  5 18:19:20 2018
  HibernationDevice: RESUME=UUID=bfa874ab-9c2f-4228-9fd1-51267b4ea3c3
  InstallationDate: Installed on 2018-02-26 (99 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225)
  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:e300 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic 
root=UUID=287736d3-3b35-4262-a175-3254aa366f41 ro rootflags=subvol=@ quiet 
splash i915.enable_rc6=1 i915.enable_psr=2 i915.enable_guc_loading=1 
i915.enable_guc_submission=1 i915.semaphores=1 i915.disable_power_well=0 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.2
  dmi.board.name: 02PG84
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.2:bd02/26/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn02PG84:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  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/1775217/+subscriptions

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


[Kernel-packages] [Bug 1774964] Re: [LTCTest][OPAL][OP910.20] WARNING: CPU: 97 PID: 11965 at /build/linux-0zaMZw/linux-4.15.0/kernel/sched/core.c:1189 set_task_cpu+0x240/0x250

2018-06-05 Thread Joseph Salisbury
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-June/093016.html

** Description changed:

+ == SRU Justification ==
+ IBM reports seeing the following during their testing:
+ WARNING: CPU: 97 PID: 11965 at 
/build/linux-0zaMZw/linux-4.15.0/kernel/sched/core.c:1189 
set_task_cpu+0x240/0x250
+ 
+ This is a regression and was introduced by the following two commits in
+ v4.15-rc1:
+ 01eaac2b0591 ("powerpc/mce: Hookup ierror (instruction) UE errors")
+ ba41e1e1ccb9 ("powerpc/mce: Hookup derror (load/store) UE errors")
+ 
+ This regression is fixed by commit 75ecfb49516c in v4.17-rc3.  The
+ commit was also cc'd to upstream stable, but it is being SRU'd to get
+ the fix into Ubuntu without waiting for it to come down via stable
+ updates.
+ 
+ 
+ == Fix ==
+ 75ecfb49516c ("powerpc/mce: Fix a bug where mce loops on memory UE.")
+ 
+ == Regression Potential ==
+ Low.  Limited to powerpc.  The commit was also cc'd to upstream stable
+ so it will recieve additional upstream stable review.
+ 
+ == Test Case ==
+ A test kernel was built with this patch and tested by the original bug 
reporter.
+ The bug reporter states the test kernel resolved the bug.
+ 
+ 
+ == Original Bug Descriptions ==
  == Comment: #0 - PAVAMAN SUBRAMANIYAM <> - 2018-04-25 01:59:10 ==
  ---Problem Description---
  WARNING: CPU: 97 PID: 11965 at 
/build/linux-0zaMZw/linux-4.15.0/kernel/sched/core.c:1189 
set_task_cpu+0x240/0x250
  
-  
  ---uname output---
  Linux ltc-wspoon8 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
-  
- Machine Type = P9 
-  
+ 
+ Machine Type = P9
+ 
  ---Debugger---
  A debugger is not configured
-  
+ 
  ---Steps to Reproduce---
  Install a P9 Open Power Hardware with the latest OP910.20 Firmware images.
  
  root@witherspoon:~# cat /etc/os-release
  ID="openbmc-phosphor"
  NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)"
  VERSION="ibm-v2.0"
  VERSION_ID="ibm-v2.0-0-r46-0-gbed584c"
  PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) 
ibm-v2.0"
  BUILD_ID="ibm-v2.0-0-r46"
  root@witherspoon:~# cat /var/lib/phosphor-software-manager/pnor/ro/VERSION
  open-power-witherspoon-v1.21.2-251-ge2e9363-dirty
- buildroot-2017.11-5-g65679be
- skiboot-v5.10.3-op910-1-p240231e
- hostboot-0aa5bed
- linux-4.14.24-openpower1-p3e84190
- petitboot-v1.6.6-pd7224b4
- machine-xml-4af
- occ-8c5b727
- hostboot-binaries-9bd4056
- capp-ucode-p9-dd2-v3
- sbe-7e02c23
- 
+ buildroot-2017.11-5-g65679be
+ skiboot-v5.10.3-op910-1-p240231e
+ hostboot-0aa5bed
+ linux-4.14.24-openpower1-p3e84190
+ petitboot-v1.6.6-pd7224b4
+ machine-xml-4af
+ occ-8c5b727
+ hostboot-binaries-9bd4056
+ capp-ucode-p9-dd2-v3
+ sbe-7e02c23
  
  Then we have installed the Ubuntu 18.04 OS on the machine.
  
  root@ltc-wspoon8:~# uname -a
  Linux ltc-wspoon8 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
  root@ltc-wspoon8:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="18.04 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 18.04 LTS"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic
  root@ltc-wspoon8:~# cat /proc/cpuinfo | tail
  cpu : POWER9, altivec supported
  clock   : 2300.00MHz
  revision: 2.1 (pvr 004e 1201)
  
  timebase: 51200
  platform: PowerNV
  model   : 8335-GTC
  machine : PowerNV 8335-GTC
  firmware: OPAL
  MMU : Radix
  root@ltc-wspoon8:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
-/var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-20-generic
+    /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-20-generic
  kdump initrd:
-/var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-20-generic
+    /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-20-generic
  current state:ready to kdump
  
  kexec command:
-   /sbin/kexec -p 
--command-line="root=UUID=a2cd572c-9047-4f0a-843b-6996fae3e999 ro quiet splash 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
+   /sbin/kexec -p 
--command-line="root=UUID=a2cd572c-9047-4f0a-843b-6996fae3e999 ro quiet splash 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  
  

[Kernel-packages] [Bug 1775217] [NEW] bluetooth controller fail after suspend with USB autosuspend on XPS 13 9360

2018-06-05 Thread Guilhem Lettron
Public bug reported:

More information here:
https://bugzilla.redhat.com/show_bug.cgi?id=1514836

Patch:
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git/commit/?id=596b07a9a22656493726edf1739569102bd3e136

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-generic 4.15.0.22.23
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  guilhem2319 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun  5 18:19:20 2018
HibernationDevice: RESUME=UUID=bfa874ab-9c2f-4228-9fd1-51267b4ea3c3
InstallationDate: Installed on 2018-02-26 (99 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225)
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:e300 Atheros Communications, Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9360
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic 
root=UUID=287736d3-3b35-4262-a175-3254aa366f41 ro rootflags=subvol=@ quiet 
splash i915.enable_rc6=1 i915.enable_psr=2 i915.enable_guc_loading=1 
i915.enable_guc_submission=1 i915.semaphores=1 i915.disable_power_well=0 
vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-22-generic N/A
 linux-backports-modules-4.15.0-22-generic  N/A
 linux-firmware 1.173.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/26/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.6.2
dmi.board.name: 02PG84
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.2:bd02/26/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn02PG84:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9360
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug bionic wayland-session

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

Title:
  bluetooth controller fail after suspend with USB autosuspend on XPS 13
  9360

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  More information here:
  https://bugzilla.redhat.com/show_bug.cgi?id=1514836

  Patch:
  
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git/commit/?id=596b07a9a22656493726edf1739569102bd3e136

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-generic 4.15.0.22.23
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  guilhem2319 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun  5 18:19:20 2018
  HibernationDevice: RESUME=UUID=bfa874ab-9c2f-4228-9fd1-51267b4ea3c3
  InstallationDate: Installed on 2018-02-26 (99 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225)
  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:e300 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic 
root=UUID=287736d3-3b35-4262-a175-3254aa366f41 ro rootflags=subvol=@ quiet 
splash i915.enable_rc6=1 i915.enable_psr=2 i915.enable_guc_loading=1 
i915.enable_guc_submission=1 i915.semaphores=1 i915.disable_power_well=0 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.2
  dmi.board.name: 02PG84
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.2:bd02/26/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn02PG84:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  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/1775217/+subscriptions

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

[Kernel-packages] [Bug 1626689] Re: During boot process, system goes to sleep

2018-06-05 Thread Marty Alan Mooney
I am having the. Same issue (in the logs it even says suspend system)
and the big problem with me is the sleep function is (or seems to be)
broken and it can't get out of sleep mode... So this essentially makes
my system a paperweight till this can be figured out or till the sleep
function is working properly...

The issue though is it didn't do that right after install. It just
randomly started doing that after I booted from a parted magic live CD.

I'm on 18.04 and I have a Lenovo yoga 11e 3rd gen winbox (i got rid of
windows) type 20GA if needed can get other info if needed

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

Title:
  During boot process, system goes to sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 16.04, my computer goes to sleep during the boot process, 
shortly after I entered the passphrase to unlock my LVM. When I wake it up, I’m 
at the graphical login prompt. I type my user password, press enter and it goes 
to sleep again. When I wake it up, I’m in my working Lubuntu desktop. This 
happens every time I boot. And it’s quite annoying.
  Please tell me which additional information I can provide to help fix this 
bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steffi 2155 F lxpanel
  CurrentDesktop: LXDE
  Date: Thu Sep 22 20:24:31 2016
  HibernationDevice: RESUME=UUID=9e305c00-cee8-4703-9352-abc5fb755282
  InstallationDate: Installed on 2016-09-21 (1 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  MachineType: Acer Aspire one
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic 
root=/dev/mapper/lubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-09-22 (0 days ago)
  dmi.bios.date: 02/20/2009
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.05
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Aspire one
  dmi.board.vendor: Acer
  dmi.board.version: V1.05
  dmi.chassis.type: 1
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.05
  dmi.modalias: 
dmi:bvnAcer:bvrV1.05:bd02/20/2009:svnAcer:pnAspireone:pvrV1.05:rvnAcer:rnAspireone:rvrV1.05:cvnAcer:ct1:cvrV1.05:
  dmi.product.name: Aspire one
  dmi.product.version: V1.05
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1768103] Re: Lancer A0 Asic HBA's won't boot with 18.04

2018-06-05 Thread Joseph Salisbury
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-June/093013.html

I believe the current schedule for this cadence is June 14th.

** Description changed:

+ == SRU Justification ==
+ It was reported by Broadcom that an early asic model (A0) of their 16/32GB
+ HBA's doesn't boot with the lpfc driver in Ubuntu 18.04.
  
- We have discovered that an early asic model (A0) of our 16/32GB HBA's doesn't 
boot with the lpfc driver in Ubuntu 18.04.   
+ Bionic with the lpfc driver 12.0.0.0 can't see LPe16002-M6 but can see
+ LPe16002B-M6.
+ 
+ This bug is fixed by commits bf316c78517d and c221768bd49a, which are
+ both still in linux-next.  Broadcom tested with this two commits and
+ confirmed they resolve the bug and allow the system to boot.
+ 
+ == Fixes ==
+ Currently in linux-next:
+ bf316c78517d ("scsi: lpfc: Fix WQ/CQ creation for older asic's.")
+ c221768bd49a ("scsi: lpfc: Fix 16gb hbas failing cq create.")
+ 
+ == Regression Potential ==
+ Low.  Patches fix a current regression and are limited to lpfc.
+ 
+ == Test Case ==
+ A test kernel was built with these patches and tested by the original bug 
reporter.
+ The bug reporter states the test kernel resolved the bug.
+ 
+ 
+ 
+ We have discovered that an early asic model (A0) of our 16/32GB HBA's doesn't 
boot with the lpfc driver in Ubuntu 18.04.
  
  After further review and discussion, this has been deemed a low risk
  issue since early A0 HBA's were only ever shipped to OEMs for test
  purposes.  These cards were never shipped to end customers.   We have
  been working to replace those cards whenever we discover them.
  
  We'll leave it up to Canonical to decide whether they want to pull this
  in this single patch to an 18.04 subsequent update.
  
  Symptom: Ubuntu 18.04 with lpfc driver 12.0.0.0 they can't see LPe16002-M6 
but can see LPe16002B-M6
- Resolution: new lpfc driver patch update. 
+ Resolution: new lpfc driver patch update.
  
  scsi: lpfc: Fix WQ/CQ creation for older asic's.
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=4.18/scsi-queue=83fae8ca4ae09403bfb99542f1aaa292c06cb111

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

Title:
  Lancer A0 Asic HBA's won't boot with 18.04

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

Bug description:
  == SRU Justification ==
  It was reported by Broadcom that an early asic model (A0) of their 16/32GB
  HBA's doesn't boot with the lpfc driver in Ubuntu 18.04.

  Bionic with the lpfc driver 12.0.0.0 can't see LPe16002-M6 but can see
  LPe16002B-M6.

  This bug is fixed by commits bf316c78517d and c221768bd49a, which are
  both still in linux-next.  Broadcom tested with this two commits and
  confirmed they resolve the bug and allow the system to boot.

  == Fixes ==
  Currently in linux-next:
  bf316c78517d ("scsi: lpfc: Fix WQ/CQ creation for older asic's.")
  c221768bd49a ("scsi: lpfc: Fix 16gb hbas failing cq create.")

  == Regression Potential ==
  Low.  Patches fix a current regression and are limited to lpfc.

  == Test Case ==
  A test kernel was built with these patches and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  
  We have discovered that an early asic model (A0) of our 16/32GB HBA's doesn't 
boot with the lpfc driver in Ubuntu 18.04.

  After further review and discussion, this has been deemed a low risk
  issue since early A0 HBA's were only ever shipped to OEMs for test
  purposes.  These cards were never shipped to end customers.   We have
  been working to replace those cards whenever we discover them.

  We'll leave it up to Canonical to decide whether they want to pull
  this in this single patch to an 18.04 subsequent update.

  Symptom: Ubuntu 18.04 with lpfc driver 12.0.0.0 they can't see LPe16002-M6 
but can see LPe16002B-M6
  Resolution: new lpfc driver patch update.

  scsi: lpfc: Fix WQ/CQ creation for older asic's.
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=4.18/scsi-queue=83fae8ca4ae09403bfb99542f1aaa292c06cb111

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

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


[Kernel-packages] [Bug 1774964] Re: [LTCTest][OPAL][OP910.20] WARNING: CPU: 97 PID: 11965 at /build/linux-0zaMZw/linux-4.15.0/kernel/sched/core.c:1189 set_task_cpu+0x240/0x250

2018-06-05 Thread Joseph Salisbury
** No longer affects: linux (Ubuntu Cosmic)

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

Title:
  [LTCTest][OPAL][OP910.20] WARNING: CPU: 97 PID: 11965 at /build/linux-
  0zaMZw/linux-4.15.0/kernel/sched/core.c:1189 set_task_cpu+0x240/0x250

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  == Comment: #0 - PAVAMAN SUBRAMANIYAM <> - 2018-04-25 01:59:10 ==
  ---Problem Description---
  WARNING: CPU: 97 PID: 11965 at 
/build/linux-0zaMZw/linux-4.15.0/kernel/sched/core.c:1189 
set_task_cpu+0x240/0x250

   
  ---uname output---
  Linux ltc-wspoon8 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = P9 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  Install a P9 Open Power Hardware with the latest OP910.20 Firmware images.

  root@witherspoon:~# cat /etc/os-release
  ID="openbmc-phosphor"
  NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)"
  VERSION="ibm-v2.0"
  VERSION_ID="ibm-v2.0-0-r46-0-gbed584c"
  PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) 
ibm-v2.0"
  BUILD_ID="ibm-v2.0-0-r46"
  root@witherspoon:~# cat /var/lib/phosphor-software-manager/pnor/ro/VERSION
  open-power-witherspoon-v1.21.2-251-ge2e9363-dirty
  buildroot-2017.11-5-g65679be
  skiboot-v5.10.3-op910-1-p240231e
  hostboot-0aa5bed
  linux-4.14.24-openpower1-p3e84190
  petitboot-v1.6.6-pd7224b4
  machine-xml-4af
  occ-8c5b727
  hostboot-binaries-9bd4056
  capp-ucode-p9-dd2-v3
  sbe-7e02c23

  
  Then we have installed the Ubuntu 18.04 OS on the machine.

  root@ltc-wspoon8:~# uname -a
  Linux ltc-wspoon8 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
  root@ltc-wspoon8:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="18.04 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 18.04 LTS"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic
  root@ltc-wspoon8:~# cat /proc/cpuinfo | tail
  cpu : POWER9, altivec supported
  clock   : 2300.00MHz
  revision: 2.1 (pvr 004e 1201)

  timebase: 51200
  platform: PowerNV
  model   : 8335-GTC
  machine : PowerNV 8335-GTC
  firmware: OPAL
  MMU : Radix
  root@ltc-wspoon8:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-20-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-20-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=a2cd572c-9047-4f0a-843b-6996fae3e999 ro quiet splash 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@ltc-wspoon8:~# ps -ef | grep opal
  root880  2  0 01:25 ?00:00:00 [kopald]
  root   3604  1  2 01:25 ?00:00:03 /usr/sbin/opal-prd
  root   4858   4278  0 01:28 pts/000:00:00 grep --color=auto opal

  root@ltc-wspoon8:~# service opal-prd status
  ? opal-prd.service - OPAL PRD daemon
 Loaded: loaded (/lib/systemd/system/opal-prd.service; enabled; vendor 
preset: enabled)
 Active: active (running) since Wed 2018-04-25 01:25:48 CDT; 2min 43s ago
   Docs: man:opal-prd(8)
   Main PID: 3604 (opal-prd)
  Tasks: 1 (limit: 22118)
 CGroup: /system.slice/opal-prd.service
 ??3604 /usr/sbin/opal-prd

  Apr 25 01:25:52 ltc-wspoon8 opal-prd[3604]: IMAGE: hbrt_init complete, 
version 0290
  Apr 25 01:25:52 ltc-wspoon8 opal-prd[3604]: HBRT: hservices_init done
  Apr 25 01:25:52 ltc-wspoon8 opal-prd[3604]: HBRT: calling enable_attns
  Apr 25 01:25:52 ltc-wspoon8 opal-prd[3604]: HBRT: 
ATTN_SLOW:I>>>ATTN_RT::enableAttns
  Apr 25 01:25:52 ltc-wspoon8 opal-prd[3604]: HBRT: 
ATTN_SLOW:I>Service::enableAttns() enter
  Apr 25 01:25:52 ltc-wspoon8 opal-prd[3604]: HBRT: 
ATTN_SLOW:I>Service::enableAttns() exit
  Apr 25 01:25:52 ltc-wspoon8 opal-prd[3604]: HBRT: 
ATTN_SLOW:I><  CR: 24002882 
 XER: 
  [  191.741188] CFAR: c0181b54 DAR: 2018faf69194 DSISR: 8000 
SOFTE: 1 
  [  191.741188] GPR00: c0cfa740 c000201857d47a30 c16eae00 

  1   2   >