date:20180527

[Kernel-packages] [Bug 1767857] Re: Kernel 4.4.0-122 Breaks qemu-system-x86

2018-05-27 Thread  Christian Ehrhardt 

And given we have two reporters that point to the upgrade lets tag it a
regression due to that.

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

Title:
  Kernel 4.4.0-122 Breaks qemu-system-x86

Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  Fully updated xubuntu 16.04 running kernel 4.4.0-122 breaks qemu-
  system-x86: black screen displays and qemu-system-x86 runs at 100% cpu
  indefinitely. Boot the same system with kernel 4.4.0-119 and qemu-
  system-x86 works fine running a Windows 10 VM.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qemu-system-x86 1:2.5+dfsg-5ubuntu10.25
  ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic i686
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sun Apr 29 15:58:25 2018
  InstallationDate: Installed on 2014-04-29 (1460 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  KvmCmdLine:
   COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
   kvm-irqfd-clean S<   0 0   394 2  0.0 [kvm-irqfd-clean]
  MachineType: Dell Inc. Inspiron 518
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-122-generic 
root=UUID=7cffb293-c044-4b2c-8343-dc50fd16db97 ro --verbose nosplash 
nmi_watchdog=0
  SourcePackage: qemu
  UpgradeStatus: Upgraded to xenial on 2016-08-10 (627 days ago)
  dmi.bios.date: 03/30/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.8
  dmi.board.name: 0K068D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.8:bd03/30/2009:svnDellInc.:pnInspiron518:pvr00:rvnDellInc.:rn0K068D:rvrA00:cvnDellInc.:ct3:cvrOEM:
  dmi.product.name: Inspiron 518
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1767857] Re: Kernel 4.4.0-122 Breaks qemu-system-x86

2018-05-27 Thread  Christian Ehrhardt 

You also said this only applies to the full 32bit stack for you (32bit host + 
guest) is that correct?
Had you the chance to try the same on 64bit host to know if this is a real 
constraint to see this issue? It would at least explain why I didn't see it as 
I had 32bit-Guest on 64-bit Host.

Never the less, this more and more seems to be a kernel bug if
a) you all can point it so clearly to these kernel versions
b) affecting qemu's from Trusty to Bionic

I'll directly ask one in the kernel Team to pop up on their radar.

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

Title:
  Kernel 4.4.0-122 Breaks qemu-system-x86

Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  Fully updated xubuntu 16.04 running kernel 4.4.0-122 breaks qemu-
  system-x86: black screen displays and qemu-system-x86 runs at 100% cpu
  indefinitely. Boot the same system with kernel 4.4.0-119 and qemu-
  system-x86 works fine running a Windows 10 VM.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qemu-system-x86 1:2.5+dfsg-5ubuntu10.25
  ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic i686
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sun Apr 29 15:58:25 2018
  InstallationDate: Installed on 2014-04-29 (1460 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  KvmCmdLine:
   COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
   kvm-irqfd-clean S<   0 0   394 2  0.0 [kvm-irqfd-clean]
  MachineType: Dell Inc. Inspiron 518
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-122-generic 
root=UUID=7cffb293-c044-4b2c-8343-dc50fd16db97 ro --verbose nosplash 
nmi_watchdog=0
  SourcePackage: qemu
  UpgradeStatus: Upgraded to xenial on 2016-08-10 (627 days ago)
  dmi.bios.date: 03/30/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.8
  dmi.board.name: 0K068D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.8:bd03/30/2009:svnDellInc.:pnInspiron518:pvr00:rvnDellInc.:rn0K068D:rvrA00:cvnDellInc.:ct3:cvrOEM:
  dmi.product.name: Inspiron 518
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1773162] Re: 4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec supported)

2018-05-27 Thread Frank Heimes

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

** Tags added: triage-g

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

Title:
  4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec
  supported)

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:
  Upgrading from 16.04 to 18.04 on a IBM S822LC the system does not boot
  with 4.15.0-22-generic and is in a reboot cycle.

  ```
  Exiting petitboot. Type 'exit' to return.
  The system is going down NOW!
  Sent SIGTERM to all processes
  Sent SIGKILL to all processes
  [31775213631,3] OPAL: Trying a CPU re-init with flags: 0x1
  [32097001879,3] OPAL: Trying a CPU re-init with flags: 0x2
  [2.660186] Bad kernel stack pointer 7fffcd511100 at c000b9ec
  [2.660382] Oops: Bad kernel stack pointer, sig: 6 [#1]
  [2.660422] LE SMP NR_CPUS=2048 NUMA PowerNV
  [2.660462] Modules linked in:
  [2.660494] CPU: 63 PID: 1201 Comm: modprobe Not tainted 4.15.0-22-generic 
#24-Ubuntu
  [2.660549] NIP:  c000b9ec LR:  CTR: 

  [2.660603] REGS: c0003fd0bd40 TRAP: 0300   Not tainted  
(4.15.0-22-generic)
  [2.660657] MSR:  90001031   CR:   XER: 

  [2.660713] CFAR: c000b934 DAR: 000200f0 DSISR: 4000 
SOFTE: -4611686018408771536 
  [2.660713] GPR00:  7fffcd511100  
 
  [2.660713] GPR04:    
 
  [2.660713] GPR08:    
 
  [2.660713] GPR12: 75501b231700 000200f0  
 
  [2.660713] GPR16:    
 
  [2.660713] GPR20:    
 
  [2.660713] GPR24:    
 
  [2.660713] GPR28:    
 
  [2.661203] NIP [c000b9ec] fast_exception_return+0x9c/0x184
  [2.661249] LR []   (null)
  [2.661285] Call Trace:
  [2.661303] Instruction dump:
  [2.661331] e84101a0 7c4ff120 e8410170 7c5a03a6 e8010070 e8410080 e8610088 
e8810090 
  [2.661387] e8210078 7db243a6 7db142a6 7c0004ac  63ff 
7db242a6 4810 
  [2.661445] ---[ end trace b607b09fe6490607 ]---
  […]
  ```

  Please find the full log attached. Selecting Linux 4.4.0-124-generic
  works.

  ```
  $ uname -a
  Linux flughafenberlinbrandenburgwillybrandt 4.4.0-124-generic #148-Ubuntu SMP 
Wed May 2 13:02:22 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux
  $ dpkg -l linux-image-4.15.0-22-generic
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version
Architecture   Description
  
+++-==-==-==-=
  ii  linux-image-4.15.0-22-generic  4.15.0-22.24   
ppc64elSigned kernel image generic
  $ more /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
  ```
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 23 16:40 seq
   crw-rw 1 root audio 116, 33 May 23 16:40 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: ppc64el
  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:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=2c3dd738-785a-469b-843e-9f0ba8b47b0d ro 
rootflags=subvol=@ quiet splash
  ProcLoadAvg: 0.01 0.08 0.04

[Kernel-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU

2018-05-27 Thread Andrea Bocci

And it seems to be fixed also in the current stable kernel, 4.16.11 .

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

Title:
  systemd-udevd consumes 100% of CPU

Status in Bluez Utilities:
  Unknown
Status in linux:
  Unknown
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The systemd-udevd proccess consumes 100% of a thread everytime, but
  i'm not noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1766940] Re: Wifi interface does often not show up after reboot

2018-05-27 Thread Julian Bieringer-Hinterbuchinger

Yes, I followed all the above steps, then apport started running after I
gave authorization in the browser and it crashed...

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

Title:
  Wifi interface does often not show up after reboot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since i got a new laptop (ThinkPad L580) and installed Kubuntu 16.04.4
  LTS with kernel 4.13.0-38-generic, i sometimes had to reboot so that
  the wifi interface showed up. Once it showed up it worked continuously
  for hours without an issue. When the update came to kernel
  4.13.0-39-generic, it got worse. Now i have to reboot at least 5 times
  until my wifi interface shows up. Once it shows up it works
  continuously like on the previous kernel for the whole session but on
  next reboot the interface is missing again. It seems random whether
  the interface is loaded (or found) when booting. Don't know if this is
  an kernel issue but since it got lot worse right after the latest
  kernel update i assume so. Wired connections are working well without
  any issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Apr 25 19:16:23 2018
  InstallationDate: Installed on 2018-04-16 (9 days ago)
  InstallationMedia: Kubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free

2018-05-27 Thread Gonzalo Servat

Many thanks, Dan! Going to roll it out to a few test boxes and try it
out over the next few days. Will report back as soon as I have some
feedback.

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  See comment 16, reproducer provided at https://github.com/fho/docker-
  samba-loop

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

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

[Kernel-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU

2018-05-27 Thread Andrea Bocci

FYI: running with the 4.17-rc6 release candidate of the new kernel from
https://wiki.ubuntu.com/Kernel/MainlineBuilds seems to have fixed the
issue for me.

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

Title:
  systemd-udevd consumes 100% of CPU

Status in Bluez Utilities:
  Unknown
Status in linux:
  Unknown
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The systemd-udevd proccess consumes 100% of a thread everytime, but
  i'm not noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1766940] Re: Wifi interface does often not show up after reboot

2018-05-27 Thread Christopher M. Penalver

Julian Bieringer-Hinterbuchinger, unfortunately, it didn't appear to
work.

As per below, what is supposed to happen is a web browser opens to a
Launchpad URL where you log in, and then give permission to upload the
requested data.

Did you do all of these steps?

apport-collect 1766940
The authorization page:

(https://launchpad.net/+authorize-token?oauth_token=6lG2RjxHrf90VRgLFxQl_permission=DESKTOP_INTEGRATION)
should be opening in your browser. Use your browser to authorize
this program to access Launchpad on your behalf.
Waiting to hear from Launchpad about your decision...

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

Title:
Wifi interface does often not show up after reboot

Status in linux package in Ubuntu:
Incomplete

Bug description:
Since i got a new laptop (ThinkPad L580) and installed Kubuntu 16.04.4
LTS with kernel 4.13.0-38-generic, i sometimes had to reboot so that
the wifi interface showed up. Once it showed up it worked continuously
for hours without an issue. When the update came to kernel
4.13.0-39-generic, it got worse. Now i have to reboot at least 5 times
until my wifi interface shows up. Once it shows up it works
continuously like on the previous kernel for the whole session but on
next reboot the interface is missing again. It seems random whether
the interface is loaded (or found) when booting. Don't know if this is
an kernel issue but since it got lot worse right after the latest
kernel update i assume so. Wired connections are working well without
any issues.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-39-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Apr 25 19:16:23 2018
InstallationDate: Installed on 2018-04-16 (9 days ago)
InstallationMedia: Kubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64
(20180228)
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Kernel-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU

2018-05-27 Thread QuentinHartman

You need to actually downgrade your running kernel to 4.13. Just
downgrading the headers isn't enough.

QH

On Sat, May 26, 2018 at 1:22 PM, Jesse McNichol 
wrote:

> Similar problem for me. Dell E6530, Ubuntu 18.04
>
> Downgraded to 4.13 headers as suggested above, disabled bluetooth in
> BIOS as suggested by others. Neither workaround helped. Computer still
> producing excess heat and systemd-udevd climbs to nearly 100% CPU usage
> gradually from startup.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1759836
>
> Title:
>   systemd-udevd consumes 100% of CPU
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/bluez/+bug/1759836/+subscriptions
>

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

Title:
  systemd-udevd consumes 100% of CPU

Status in Bluez Utilities:
  Unknown
Status in linux:
  Unknown
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The systemd-udevd proccess consumes 100% of a thread everytime, but
  i'm not noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1759254] Re: BUG: unable to handle kernel paging request at ffff895ec6c60600

2018-05-27 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/1759254

Title:
  BUG: unable to handle kernel paging request at 895ec6c60600

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

Bug description:
  Ubuntu Bionic Beaver (development branch)

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13 [modified: 
boot/vmlinuz-4.15.0-12-generic]
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1109 F pulseaudio
delpianod   6436 F pulseaudio
  Date: Tue Mar 27 09:58:14 2018
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
RIP: 0x895ec6c60600 RSP: b87201717c40
  Failure: oops
  InstallationDate: Installed on 2018-03-26 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325)
  MachineType: ZOTAC XX
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=fab05f7e-b132-4a86-8464-6b5d05925d80 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: BUG: unable to handle kernel paging request at 895ec6c60600
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B301P016
  dmi.board.asset.tag: N/A
  dmi.board.name: XX
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 2
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB301P016:bd03/14/2016:svnZOTAC:pnXX:pvrXX:rvnZOTAC:rnXX:rvrXX:cvnDefaultstring:ct2:cvrDefaultstring:
  dmi.product.family: N/A
  dmi.product.name: XX
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC

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

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

[Kernel-packages] [Bug 1759254] Re: BUG: unable to handle kernel paging request at ffff895ec6c60600

2018-05-27 Thread Launchpad Bug Tracker

[Expired for linux (Ubuntu Bionic) because there has been no activity
for 60 days.]

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

Title:
  BUG: unable to handle kernel paging request at 895ec6c60600

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

Bug description:
  Ubuntu Bionic Beaver (development branch)

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13 [modified: 
boot/vmlinuz-4.15.0-12-generic]
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1109 F pulseaudio
delpianod   6436 F pulseaudio
  Date: Tue Mar 27 09:58:14 2018
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
RIP: 0x895ec6c60600 RSP: b87201717c40
  Failure: oops
  InstallationDate: Installed on 2018-03-26 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325)
  MachineType: ZOTAC XX
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=fab05f7e-b132-4a86-8464-6b5d05925d80 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: BUG: unable to handle kernel paging request at 895ec6c60600
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B301P016
  dmi.board.asset.tag: N/A
  dmi.board.name: XX
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 2
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB301P016:bd03/14/2016:svnZOTAC:pnXX:pvrXX:rvnZOTAC:rnXX:rvrXX:cvnDefaultstring:ct2:cvrDefaultstring:
  dmi.product.family: N/A
  dmi.product.name: XX
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC

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

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

[Kernel-packages] [Bug 1759641] Re: Kernel 4.13.0-37 - Hibernation Does Not Work in the Kernel

2018-05-27 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/1759641

Title:
  Kernel 4.13.0-37 - Hibernation Does Not Work in the Kernel

Status in linux package in Ubuntu:
  Expired

Bug description:
  When using Kernel 4.13.0-37 on several notebooks, Hibernation does not
  work correctly. The notebook hibernates but does not return from
  hibernation.

  Already in Kernel 4.10.0-38 it works correctly, both hibernation and
  suspending even hybrid.

  The tests were done with all versions of Mint (MATE, XFCE, Cinnamon, LMDE 2 
in their latest versions).
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dvorack1807 F pulseaudio
   /dev/snd/controlC1:  dvorack1807 F pulseaudio
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=fc6bf713-50b3-45c9-b60a-6faa6216222d
  InstallationDate: Installed on 2018-03-27 (1 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: Itautec S.A. Infoway w7545
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic 
root=UUID=e9ab4037-af9f-4e6a-99cf-b938ec3b41ce ro quiet splash
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-38-generic N/A
   linux-backports-modules-4.10.0-38-generic  N/A
   linux-firmware 1.157.17
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  sylvia
  Uname: Linux 4.10.0-38-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 19/05/2011
  dmi.bios.vendor: Infoway Note W7545, 1.01.03TIS3-SLP2.1
  dmi.bios.version: 1.01.03TIS
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W7545
  dmi.board.vendor: Itautec S.A.
  dmi.board.version: Padrao
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInfowayNoteW7545,1.01.03TIS3-SLP2.1:bvr1.01.03TIS:bd19/05/2011:svnItautecS.A.:pnInfowayw7545:pvrCorp:rvnItautecS.A.:rnW7545:rvrPadrao:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: Infoway w7545
  dmi.product.version: Corp
  dmi.sys.vendor: Itautec S.A.

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

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

[Kernel-packages] [Bug 1766940] Re: Wifi interface does often not show up after reboot

2018-05-27 Thread Julian Bieringer-Hinterbuchinger

@Christopher M. Penalver
Just executed the command "apport-collect 1766940".

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

Title:
  Wifi interface does often not show up after reboot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since i got a new laptop (ThinkPad L580) and installed Kubuntu 16.04.4
  LTS with kernel 4.13.0-38-generic, i sometimes had to reboot so that
  the wifi interface showed up. Once it showed up it worked continuously
  for hours without an issue. When the update came to kernel
  4.13.0-39-generic, it got worse. Now i have to reboot at least 5 times
  until my wifi interface shows up. Once it shows up it works
  continuously like on the previous kernel for the whole session but on
  next reboot the interface is missing again. It seems random whether
  the interface is loaded (or found) when booting. Don't know if this is
  an kernel issue but since it got lot worse right after the latest
  kernel update i assume so. Wired connections are working well without
  any issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Apr 25 19:16:23 2018
  InstallationDate: Installed on 2018-04-16 (9 days ago)
  InstallationMedia: Kubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1769980] Re: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement

2018-05-27 Thread Anthony Wong

** Description changed:

  Intel wireless driver and firmware require updates in order to meet the
  new ETSI regulation [1] for OEM machines shipped from factories.
  
  Intel provided us the following information for what are required to
  update:
  
  1. Kernel driver:
  
  https://patchwork.kernel.org/patch/10322121/
  https://patchwork.kernel.org/patch/10312731/
  https://patchwork.kernel.org/patch/10312735/
  https://patchwork.kernel.org/patch/10312733/
  
  - 7260, 7265, 7265D and 3168 NICs, 4.15 plus above driver patches
  - 8000 series requires 4.16.
  - 9000 series requires 4.17.
  
  2. linux-firmware
  Requires latest versions from linux-firmware.git
  
  3. wireless-regdb update
  
  [1]
  
http://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf
  
  ---
  == SRU Justification for linux-firmware ==
  [Impact]
  Intel released these firmware updates to support the new ETSI 5GHz Adaptivity 
Requirement, OEM has to meet it in order to ship.
  
  [Test Case]
  Check dmesg to confirm the correct firmware is loaded, make sure the revision 
is correct, and check wifi can functions properly.
  
  [Regression Potential]
  It is possible that there is regression introduced by Intel's firmware, so 
should make sure wifi still works properly after the new firmware is used. We 
have verified the new firmwares of 7260 and 7265D on 4.4
  and 4.15 kernels. The 8000 and 9000 series firmwares have newer API versions 
and will need to confirm with subsequent driver changes.
- 
- == SRU Justification for crda ==
- [Impact]
- We need crda to include Seth Forshee's public key to support wireless-regdb's 
new format.
- 
- [Test Case]
- Check the key is installed at /lib/crda/pubkeys/sforshee.key.pub.pem.
- 
- [Regression Potential]
- As this is a new file, no regression should happen.

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

Title:
  Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in crda package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  New
Status in wireless-regdb package in Ubuntu:
  Fix Released
Status in crda source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Won't Fix
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-oem source package in Xenial:
  In Progress
Status in wireless-regdb source package in Xenial:
  New
Status in crda source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  Confirmed
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  In Progress
Status in wireless-regdb source package in Bionic:
  New

Bug description:
  Intel wireless driver and firmware require updates in order to meet
  the new ETSI regulation [1] for OEM machines shipped from factories.

  Intel provided us the following information for what are required to
  update:

  1. Kernel driver:

  https://patchwork.kernel.org/patch/10322121/
  https://patchwork.kernel.org/patch/10312731/
  https://patchwork.kernel.org/patch/10312735/
  https://patchwork.kernel.org/patch/10312733/

  - 7260, 7265, 7265D and 3168 NICs, 4.15 plus above driver patches
  - 8000 series requires 4.16.
  - 9000 series requires 4.17.

  2. linux-firmware
  Requires latest versions from linux-firmware.git

  3. wireless-regdb update

  [1]
  
http://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf

  ---
  == SRU Justification for linux-firmware ==
  [Impact]
  Intel released these firmware updates to support the new ETSI 5GHz Adaptivity 
Requirement, OEM has to meet it in order to ship.

  [Test Case]
  Check dmesg to confirm the correct firmware is loaded, make sure the revision 
is correct, and check wifi can functions properly.

  [Regression Potential]
  It is possible that there is regression introduced by Intel's firmware, so 
should make sure wifi still works properly after the new firmware is used. We 
have verified the new firmwares of 7260 and 7265D on 4.4
  and 4.15 kernels. The 8000 and 9000 series firmwares have newer API versions 
and will need to confirm with subsequent driver changes.

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

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

[Kernel-packages] [Bug 1773718] Re: mouse ponter disappear after screen off

2018-05-27 Thread Hans P Möller

I didn't knew which log to attach. Already done what you asked for. I'm
also attaching lspci -vnvn log

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

** Attachment added: "lspci -vnv"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773718/+attachment/5145369/+files/lspci-vnvn.log

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

Title:
  mouse ponter disappear after screen off

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With nouveau driver (doesn't happened with propietary nvidia) after
  screen switch off because of power management, the mouse pointer
  disappear. Mouse still works, you can hover, select, click, but the
  pointer is invisible.

  In a dual monitor configuration, this only happened in the screen
  where the mouse was when it turned off. If It firs happened in one
  monitor and tehn I left the mouse in the other and it also turn off,
  mouse end up disappearing in both.

  My video card is an nvidia GeForce Go6150 (NV4E C51).

  Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16

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

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

[Kernel-packages] [Bug 1727235] Re: Dell new AIO requires a new uart backlight driver

2018-05-27 Thread Yuan-Chen Cheng

** Changed in: oem-priority
   Importance: High => 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/1727235

Title:
  Dell new AIO requires a new uart backlight driver

Status in HWE Next:
  New
Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  In Progress

Bug description:
  New Dell AIO platforms requires a driver that can communicate with
  the scalar IC FW by UART interface to get and set the brightness
  level.

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

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

[Kernel-packages] [Bug 1762385] Re: dell_wmi: Unknown key codes

2018-05-27 Thread Yuan-Chen Cheng

** Changed in: oem-priority
   Status: Confirmed => Triaged

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

Title:
  dell_wmi: Unknown key codes

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Xenial:
  New
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * Bogus keycode messages produced by the kernel / user annoyance
   * rfkill keyboard shortcuts not working as intended on some Dell machines

  [Test Case]

   * check that there are no spurious kernel messages about unknown keys
  in journalctl upon RFKill key presses

   * check that RFKill key presses work correctly and kill/restore RF
  capabilities

  [Regression Potential]

   * The change is scoped to particular SKUs and thus should only affect them
   * It is related to matching gsd support, which is in-place on xenial and up

  [Solution]
  Cherrypick upstream commit 
https://github.com/systemd/systemd/commit/cab01e9ecf1c69656785e64f5fc94cd4ed09e57f

  [Original Bug report]

  RFKill key produces these messages in kernel log:

  dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed

  This key code is a notification and should be added as KEY_IGNORE
  here:
  https://github.com/torvalds/linux/blob/master/drivers/platform/x86
  /dell-wmi.c#L263

  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
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmig   2737 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 18:09:03 2018
  InstallationDate: Installed on 2018-03-27 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  MachineType: Dell Inc. Inspiron 5379
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-generic 
root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ 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: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 0C6J64
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5379
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1762385/+subscriptions

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

[Kernel-packages] [Bug 1769120] Re: [Dell Precision 5520] wifi is very unreliable to connect over b and g protocol

2018-05-27 Thread Yuan-Chen Cheng

@Taihsiang, how is the failed rate ?

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

Title:
  [Dell Precision 5520] wifi is very unreliable to connect over b and g
  protocol

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dell Precision 5520 (CID 201610-25144)
  pre-installed (oem) image (16.04)

  [Description]

  When the wifi tries to connect SSID over b and g protocol, it is very
  hard to build connection successfully. The reproducing rate is 9/10.

  [Steps to Reproduce]

  1. Update the system to use the last stack.
  2. Reboot
  3. Connect the bg wifi by network-manager applet

  [Expected Result]

  The network-manager builds the connection.

  [Actual Result]

  The network-manger could not connect to the target SSID.





  
  -

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-123-generic 4.4.0-123.147
  ProcVersionSignature: Ubuntu 4.4.0-123.147-generic 4.4.128
  Uname: Linux 4.4.0-123-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1972 F pulseaudio
  Date: Fri May  4 19:16:50 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  HibernationDevice: RESUME=UUID=395dc72d-da55-4d11-8875-2240537ead7f
  InstallationDate: Installed on 2018-05-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Precision 5520
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-123-generic.efi.signed 
root=UUID=f71a7ab1-fcc5-4873-839b-1b7955196b53 ro automatic-oem-config quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-123-generic N/A
   linux-backports-modules-4.4.0-123-generic  N/A
   linux-firmware 1.157.18
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.4:bd06/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1769120/+subscriptions

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

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

2018-05-27 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 1773718

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

Title:
  mouse ponter disappear after screen off

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With nouveau driver (doesn't happened with propietary nvidia) after
  screen switch off because of power management, the mouse pointer
  disappear. Mouse still works, you can hover, select, click, but the
  pointer is invisible.

  In a dual monitor configuration, this only happened in the screen
  where the mouse was when it turned off. If It firs happened in one
  monitor and tehn I left the mouse in the other and it also turn off,
  mouse end up disappearing in both.

  My video card is an nvidia GeForce Go6150 (NV4E C51).

  Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16

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

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

[Kernel-packages] [Bug 1773718] [NEW] mouse ponter disappear after screen off

2018-05-27 Thread Hans P Möller

Public bug reported:

With nouveau driver (doesn't happened with propietary nvidia) after
screen switch off because of power management, the mouse pointer
disappear. Mouse still works, you can hover, select, click, but the
pointer is invisible.

In a dual monitor configuration, this only happened in the screen where
the mouse was when it turned off. If It firs happened in one monitor and
tehn I left the mouse in the other and it also turn off, mouse end up
disappearing in both.

My video card is an nvidia GeForce Go6150 (NV4E C51).

Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16

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


** Tags: disappear mouse nouveau nvidia pointer

** Description changed:

  With nouveau driver (doesn't happened with propietary nvidia) after
  screen switch off because of power management, the mouse pointer
  disappear. Mouse still works, you can hover, select, click, but the
  pointer is invisible.
  
  In a dual monitor configuration, this only happened in the screen where
  the mouse was when it turned off. If It firs happened in one monitor and
  tehn I left the mouse in the other and it also turn off, mouse end up
  disappearing in both.
  
  My video card is an nvidia GeForce Go6150 (NV4E C51).
+ 
+ Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16

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

Title:
  mouse ponter disappear after screen off

Status in linux package in Ubuntu:
  New

Bug description:
  With nouveau driver (doesn't happened with propietary nvidia) after
  screen switch off because of power management, the mouse pointer
  disappear. Mouse still works, you can hover, select, click, but the
  pointer is invisible.

  In a dual monitor configuration, this only happened in the screen
  where the mouse was when it turned off. If It firs happened in one
  monitor and tehn I left the mouse in the other and it also turn off,
  mouse end up disappearing in both.

  My video card is an nvidia GeForce Go6150 (NV4E C51).

  Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16

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

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

[Kernel-packages] [Bug 1773715] [NEW] cable DVI en su dockstation pero el VGA si

2018-05-27 Thread Priscila

Public bug reported:

Mi laptop Dell E6440 no reconoce que tiene conectado un cable DVI en el
dockstation para un segundo monitor, esto paso deszpues de hacer upgrade
a la version 18.04.

root@pr:/home/pr# xrandr
Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 8192 x 8192
LVDS-1 connected 1280x720+0+0 (normal left inverted right x axis y axis) 309mm 
x 174mm
   1366x768  60.05 +  40.31  
   1360x768  59.8059.96  
   1280x720  60.0059.9959.86*   59.74  
   1024x768  60.0460.00  
   960x720   60.00  
   928x696   60.05  
   896x672   60.01  
   1024x576  59.9559.9659.9059.82  
   960x600   59.9360.00  
   960x540   59.9659.9959.6359.82  
   800x600   60.0060.3256.25  
   840x525   60.0159.88  
   864x486   59.9259.57  
   800x512   60.17  
   700x525   59.98  
   800x450   59.9559.82  
   640x512   60.02  
   720x450   59.89  
   700x450   59.9659.88  
   640x480   60.0059.94  
   720x405   59.5158.99  
   684x384   59.8859.85  
   680x384   59.8059.96  
   640x400   59.8859.98  
   576x432   60.06  
   640x360   59.8659.8359.8459.32  
   512x384   60.00  
   512x288   60.0059.92  
   480x270   59.6359.82  
   400x300   60.3256.34  
   432x243   59.9259.57  
   320x240   60.05  
   360x202   59.5159.13  
   320x180   59.8459.32  
VGA-1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 376mm 
x 301mm
   1280x1024 60.02*+  75.02  
   1024x768  75.0360.00  
   800x600   75.0060.32  
   640x480   75.0059.94  
   720x400   70.08  

root@pr:/home/pr# xrandr --addmode DVI-1 1280x1024_70.00
xrandr: cannot find output "DVI-1"

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
Architecture: amd64
Date: Sun May 27 18:50:51 2018
InstallationDate: Installed on 2017-12-14 (164 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: linux-signed
UpgradeStatus: Upgraded to bionic on 2018-05-16 (11 days ago)

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


** Tags: amd64 apport-bug bionic

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

Title:
   cable DVI en su dockstation pero el VGA si

Status in linux-signed package in Ubuntu:
  New

Bug description:
  Mi laptop Dell E6440 no reconoce que tiene conectado un cable DVI en
  el dockstation para un segundo monitor, esto paso deszpues de hacer
  upgrade a la version 18.04.

  root@pr:/home/pr# xrandr
  Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 8192 x 8192
  LVDS-1 connected 1280x720+0+0 (normal left inverted right x axis y axis) 
309mm x 174mm
 1366x768  60.05 +  40.31  
 1360x768  59.8059.96  
 1280x720  60.0059.9959.86*   59.74  
 1024x768  60.0460.00  
 960x720   60.00  
 928x696   60.05  
 896x672   60.01  
 1024x576  59.9559.9659.9059.82  
 960x600   59.9360.00  
 960x540   59.9659.9959.6359.82  
 800x600   60.0060.3256.25  
 840x525   60.0159.88  
 864x486   59.9259.57  
 800x512   60.17  
 700x525   59.98  
 800x450   59.9559.82  
 640x512   60.02  
 720x450   59.89  
 700x450   59.9659.88  
 640x480   60.0059.94  
 720x405   59.5158.99  
 684x384   59.8859.85  
 680x384   59.8059.96  
 640x400   59.8859.98  
 576x432   60.06  
 640x360   59.8659.8359.8459.32  
 512x384   60.00  
 512x288   60.0059.92  
 480x270   59.6359.82  
 400x300   60.3256.34  
 432x243   59.9259.57  
 320x240   60.05  
 360x202   59.5159.13  
 320x180   59.8459.32  
  VGA-1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 
376mm x 301mm
 1280x1024 60.02*+  75.02  
 1024x768  75.0360.00  
 800x600   75.0060.32  
 640x480   75.0059.94  
 720x400   70.08  

  root@pr:/home/pr# xrandr --addmode DVI-1 1280x1024_70.00
  xrandr: cannot find output "DVI-1"

  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
  Architecture: amd64
  Date: Sun May 27 18:50:51 2018

[Kernel-packages] [Bug 1773476] Re: linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.ing-4.8.0 when no corresponding vmlinuz present

2018-05-27 Thread B. C. Schmerker

Update:  A purge and reinstall of linux-firmware produces same results.
Summary therefore:

Reproducible:  Always
Steps to reproduce:  sudo apt install (--reinstall) linux-firmware or sudo 
dpkg-reconfigure linux-firmware.
Actual results, excepting actually installed Kernel Image packages:

update-initramfs: Generating /boot/initrd.img-4.8.0-56
WARNING: missing /lib/modules/4.8.0-56
Ensure all necessary drivers are built into the linux image!
depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file or 
directory
depmod: FATAL: could not search modules: No such file or directory
depmod: WARNING: could not open 
/var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or 
directory
depmod: WARNING: could not open 
/var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file 
or directory
update-initramfs: Generating /boot/initrd.img-4.8.0
WARNING: missing /lib/modules/4.8.0
Ensure all necessary drivers are built into the linux image!
depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or 
directory
depmod: FATAL: could not search modules: No such file or directory
depmod: WARNING: could not open 
/var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or 
directory
depmod: WARNING: could not open 
/var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or 
directory

Expected results, excepting actually installed Kernel Image packages:

No warning, errors or fatals.

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

Title:
  linux-firmware 1.157.19 attempts to generate
  /boot/initrd.img-4.8.0-56, /boot/initrd.ing-4.8.0 when no
  corresponding vmlinuz present

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  With LinUX Images/-Extras 4.15.0-22-generic, 4.13.0-43-generic,
  4.8.0-58-generic, 4.8.0-56-generic, and 4.4.0-127-generic installed,
  sudo dpkg-reconfigure linux-firmware returns the following to Console:

  update-initramfs: Generating /boot/initrd.img-4.15.0-22-generic
  update-initramfs: Generating /boot/initrd.img-4.13.0-43-generic
  update-initramfs: Generating /boot/initrd.img-4.8.0-58-generic
  update-initramfs: Generating /boot/initrd.img-4.8.0-56-generic
  update-initramfs: Generating /boot/initrd.img-4.8.0-56
  WARNING: missing /lib/modules/4.8.0-56
  Ensure all necessary drivers are built into the linux image!
  depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file 
or directory
  depmod: FATAL: could not search modules: No such file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or 
directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file 
or directory
  update-initramfs: Generating /boot/initrd.img-4.8.0
  WARNING: missing /lib/modules/4.8.0
  Ensure all necessary drivers are built into the linux image!
  depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or 
directory
  depmod: FATAL: could not search modules: No such file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or 
directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or 
directory
  update-initramfs: Generating /boot/initrd.img-4.4.0-127-generic

  Same configuration report for "Setting up linux-firmware..." with sudo 
apt(-get) install (--reinstall) linux-firmware.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CurrentDesktop: Unity
  Dependencies:
   
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2017-05-17 (373 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Package: linux-firmware 1.157.19 [origin: unknown]
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.15.0-22.24~16.04.1-generic 4.15.17
  Tags: xenial third-party-packages
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  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-firmware/+bug/1773476/+subscriptions

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

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

2018-05-27 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 1773704

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

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

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

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

** Tags added: bionic

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

Title:
  Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset
  in Bionic 18.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  A typo at line 184 in /drivers/usb/host/xhci-pci.c trashes a good fix.

  
  183 if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  184 pdev->device == 0x0014)
  185 xhci->quirks |= XHCI_TRUST_TX_LENGTH;
  186 if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  187 pdev->device == 0x0015)
  188 xhci->quirks |= XHCI_RESET_ON_RESUME;

  Line 184 should be identical to line 187, ie: should read pdev->device
  == 0x0015)

  I've compiled the kernel both with and without the typo. As written,
  hundreds of messages fill dmesg suggesting XHCI_TRUST_TX_LENGTH may be
  needed when zoneminder tries to access my USB webcams. With the fix
  applied as I've suggested the messages disappear.

  The typo is still present in 4.15.0-22.24

  For more background, you may refer to bug ID #1710548

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

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

[Kernel-packages] [Bug 1773704] [NEW] Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset in Bionic 18.04

2018-05-27 Thread Jeffrey Miller

Public bug reported:

A typo at line 184 in /drivers/usb/host/xhci-pci.c trashes a good fix.


183 if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
184 pdev->device == 0x0014)
185 xhci->quirks |= XHCI_TRUST_TX_LENGTH;
186 if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
187 pdev->device == 0x0015)
188 xhci->quirks |= XHCI_RESET_ON_RESUME;

Line 184 should be identical to line 187, ie: should read pdev->device
== 0x0015)

I've compiled the kernel both with and without the typo. As written,
hundreds of messages fill dmesg suggesting XHCI_TRUST_TX_LENGTH may be
needed when zoneminder tries to access my USB webcams. With the fix
applied as I've suggested the messages disappear.

The typo is still present in 4.15.0-22.24

For more background, you may refer to bug ID #1710548

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

Title:
  Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset
  in Bionic 18.04

Status in linux package in Ubuntu:
  New

Bug description:
  A typo at line 184 in /drivers/usb/host/xhci-pci.c trashes a good fix.

  
  183 if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  184 pdev->device == 0x0014)
  185 xhci->quirks |= XHCI_TRUST_TX_LENGTH;
  186 if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  187 pdev->device == 0x0015)
  188 xhci->quirks |= XHCI_RESET_ON_RESUME;

  Line 184 should be identical to line 187, ie: should read pdev->device
  == 0x0015)

  I've compiled the kernel both with and without the typo. As written,
  hundreds of messages fill dmesg suggesting XHCI_TRUST_TX_LENGTH may be
  needed when zoneminder tries to access my USB webcams. With the fix
  applied as I've suggested the messages disappear.

  The typo is still present in 4.15.0-22.24

  For more background, you may refer to bug ID #1710548

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

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

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

2018-05-27 Thread Christopher M. Penalver

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

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

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

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

If the issue is reproducible with the mainline kernel, please add the following 
tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

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

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

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

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

Thank you for your help.

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

[Kernel-packages] [Bug 1773692] [NEW] right touchpad does not work. lenovo yoga 510 notebook

2018-05-27 Thread Karneiro

Public bug reported:

I installed Ubuntu 18.04 on Lenovo Yoga 510 notebook.
the right touchapad button did not work.

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
Architecture: amd64
Date: Sun May 27 15:32:49 2018
InstallationDate: Installed on 2018-05-26 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: linux-signed
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  right touchpad does not work. lenovo yoga 510 notebook

Status in linux-signed package in Ubuntu:
  New

Bug description:
  I installed Ubuntu 18.04 on Lenovo Yoga 510 notebook.
  the right touchapad button did not work.

  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
  Architecture: amd64
  Date: Sun May 27 15:32:49 2018
  InstallationDate: Installed on 2018-05-26 (0 days ago)
  InstallationMedia: Ubuntu 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-signed/+bug/1773692/+subscriptions

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

[Kernel-packages] [Bug 1767857] Re: Kernel 4.4.0-122 Breaks qemu-system-x86

2018-05-27 Thread Ante Karamatić

I can confirm that, while 4.4.0-119 works just fine, 4.4.0-121 doesn't
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/1767857

Title:
  Kernel 4.4.0-122 Breaks qemu-system-x86

Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  Fully updated xubuntu 16.04 running kernel 4.4.0-122 breaks qemu-
  system-x86: black screen displays and qemu-system-x86 runs at 100% cpu
  indefinitely. Boot the same system with kernel 4.4.0-119 and qemu-
  system-x86 works fine running a Windows 10 VM.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qemu-system-x86 1:2.5+dfsg-5ubuntu10.25
  ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic i686
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sun Apr 29 15:58:25 2018
  InstallationDate: Installed on 2014-04-29 (1460 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  KvmCmdLine:
   COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
   kvm-irqfd-clean S<   0 0   394 2  0.0 [kvm-irqfd-clean]
  MachineType: Dell Inc. Inspiron 518
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-122-generic 
root=UUID=7cffb293-c044-4b2c-8343-dc50fd16db97 ro --verbose nosplash 
nmi_watchdog=0
  SourcePackage: qemu
  UpgradeStatus: Upgraded to xenial on 2016-08-10 (627 days ago)
  dmi.bios.date: 03/30/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.8
  dmi.board.name: 0K068D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.8:bd03/30/2009:svnDellInc.:pnInspiron518:pvr00:rvnDellInc.:rn0K068D:rvrA00:cvnDellInc.:ct3:cvrOEM:
  dmi.product.name: Inspiron 518
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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

94 matches

Mail list logo