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

2018-01-28 Thread JiriHorky
Hi Dan,

first of all thanks for looking into this long lasting, irritating
issue.

I have tried your kernel (4.13.0-30-generic #33+hf1711407v20180118b2-Ubuntu 
SMP) on Ubuntu 17.10 and was able to get "unregister_netdevice: waiting for lo 
to become free. Usage count = 1" in less than 5 minutes :-( 
Our environment spawns about 1 container a second that does either openvpn 
(both udp and tcp) or ipsec tunnel testing. 
I don't see any debug output in the kernel log, the lines are just old 
ordinary: 

[  910.690908] unregister_netdevice: waiting for lo to become free. Usage count 
= 1
[  920.806382] unregister_netdevice: waiting for lo to become free. Usage count 
= 1
[  930.945869] unregister_netdevice: waiting for lo to become free. Usage count 
= 1
[  941.025341] unregister_netdevice: waiting for lo to become free. Usage count 
= 1
[  951.104797] unregister_netdevice: waiting for lo to become free. Usage count 
= 1
[  961.184286] unregister_netdevice: waiting for lo to become free. Usage count 
= 1
[  971.263749] unregister_netdevice: waiting for lo to become free. Usage count 
= 1

I don't even see any "net_free:" or "net_alloc:" messages in the log
(and I checked the referrenced git and your recent patch and it does not
seem to be there either).

PLease let me know how to enable the debug messages, so we can finally
trace it down.

Thanks
Jiri Horky

-- 
You 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:
  In Progress
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 1658733] target fix for artful

2018-01-28 Thread bugproxy
Default Comment by Bridge

** Attachment added: "target fix for artful"
   
https://bugs.launchpad.net/bugs/1658733/+attachment/5044780/+files/makedumpfile_1.6.1-2ubuntu0.1.diff

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

Title:
  Ubuntu 16.04.2KVM:kdump fails to mount root file system when
  noirqdistrib is missing as dump kernel parameter

Status in The Ubuntu-power-systems project:
  Confirmed
Status in kexec-tools package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Trusty:
  New
Status in makedumpfile source package in Trusty:
  New
Status in kexec-tools source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in kexec-tools source package in Zesty:
  New
Status in makedumpfile source package in Zesty:
  New
Status in kexec-tools source package in Artful:
  Invalid
Status in makedumpfile source package in Artful:
  Fix Committed
Status in kexec-tools source package in Bionic:
  Invalid
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  On Power Systems, some interrupts are missed, and dumping the crash will 
fail. Adding the noirqdistrib kernel parameter to the kdump kernel will fix 
this.

  [Test Case]
  Setting up kdump to target a virtio-scsi device on a Power System.

  [Regression Potential]
  The parameter could be interpreted differently on a different platform and 
kdump would fail. However, it has been verified that no other platform uses 
such parameter. If another parameter would have been incorrectly removed on the 
patch, kdump could fail on other systems.


  == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 ==

  ---Problem Description---

  On a KVM guest installed to a multipath root device, the kdump kernel
  fails to mount the root file system.  This error does not occur in a
  similar guest installed to a single path device.

  Full console output of the kdump failure is attached.  These messages
  from the output may be relevant:

  Begin: Loading multipath modules ... Success: loaded module dm-multipath.
  done.
  Begin: Loading multipath hardware handlers ... Failure: failed to load module 
sc
  si_dh_alua.
  Failure: failed to load module scsi_dh_rdac.
  Failure: failed to load module scsi_dh_emc.
  done.
  Begin: Starting multipathd ... done.

  ---uname output---
  Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest

  ---Steps to Reproduce---
   - Install Ubuntu 16.04.1 to a muiltpath target disk
  - Install kdump-tools package
  - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to 
load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg
  - Run update-grub
  - Reboot
  - Initiate a system crash using "echo c > /proc/sysrq-trigger"

  == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 ==
  Here is the log level 8 kdump console log requested in comment 10.

  == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 ==
  (In reply to comment #19)
  > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I
  > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it
  > uses .img files which I didn't found as disks).
  >
  > Could you please recreate the guest for further debug?

  Yes, I recreated the guest with its correct multipath lun
  configuration.  I have also attached the guest XML to this bug.

  > Besides that could you please let us know:
  >  - is the multipath the system's root? I mean / is installed/mounted on the
  > multipath device?

  Yes, the guest has only one disk.  That disk is actually a LUN from a
  fiber channel storage device with two paths on the host side.  I have
  passed through both paths to the guest, so the multipath nature of the
  target disk is known to the guest.

  In other words, the guest sees a multipath device and is using it as a
  multipath device.  The root file system is called /dev/mapper/mpatha-
  part2 on the guest.

  >  - how did you attach the device to the guest?

  Each FC LUN path on the host is mapped to a virtio-scsi controller on
  the guest using LUN passthrough.  (See the guest XML for details on
  this.)

  == Comment: #22 - Mauro Sergio Martins Rodrigues  - 2017-01-11 09:31:38 ==
  I managed to get kdump to mount rootfs and perform its tasks by setting 
KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see 
http://pastebin.hursley.ibm.com/8239

  I'm still investigating to figure out what is the reason behind this
  behavior.

  Thanks,

  --
  maurosr

  == Comment: #23 - Mauricio Faria De Oliveira  - 2017-01-11 11:56:40 ==
  Mauro,

  (In reply to comment #22)
  > I managed to get kdump to mount rootfs and 

[Kernel-packages] [Bug 1658733] fix for bionic

2018-01-28 Thread bugproxy
Default Comment by Bridge

** Attachment added: "fix for bionic"
   
https://bugs.launchpad.net/bugs/1658733/+attachment/5044781/+files/makedumpfile_1.6.2-1ubuntu0.1.diff

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

Title:
  Ubuntu 16.04.2KVM:kdump fails to mount root file system when
  noirqdistrib is missing as dump kernel parameter

Status in The Ubuntu-power-systems project:
  Confirmed
Status in kexec-tools package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Trusty:
  New
Status in makedumpfile source package in Trusty:
  New
Status in kexec-tools source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in kexec-tools source package in Zesty:
  New
Status in makedumpfile source package in Zesty:
  New
Status in kexec-tools source package in Artful:
  Invalid
Status in makedumpfile source package in Artful:
  Fix Committed
Status in kexec-tools source package in Bionic:
  Invalid
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  On Power Systems, some interrupts are missed, and dumping the crash will 
fail. Adding the noirqdistrib kernel parameter to the kdump kernel will fix 
this.

  [Test Case]
  Setting up kdump to target a virtio-scsi device on a Power System.

  [Regression Potential]
  The parameter could be interpreted differently on a different platform and 
kdump would fail. However, it has been verified that no other platform uses 
such parameter. If another parameter would have been incorrectly removed on the 
patch, kdump could fail on other systems.


  == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 ==

  ---Problem Description---

  On a KVM guest installed to a multipath root device, the kdump kernel
  fails to mount the root file system.  This error does not occur in a
  similar guest installed to a single path device.

  Full console output of the kdump failure is attached.  These messages
  from the output may be relevant:

  Begin: Loading multipath modules ... Success: loaded module dm-multipath.
  done.
  Begin: Loading multipath hardware handlers ... Failure: failed to load module 
sc
  si_dh_alua.
  Failure: failed to load module scsi_dh_rdac.
  Failure: failed to load module scsi_dh_emc.
  done.
  Begin: Starting multipathd ... done.

  ---uname output---
  Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest

  ---Steps to Reproduce---
   - Install Ubuntu 16.04.1 to a muiltpath target disk
  - Install kdump-tools package
  - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to 
load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg
  - Run update-grub
  - Reboot
  - Initiate a system crash using "echo c > /proc/sysrq-trigger"

  == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 ==
  Here is the log level 8 kdump console log requested in comment 10.

  == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 ==
  (In reply to comment #19)
  > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I
  > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it
  > uses .img files which I didn't found as disks).
  >
  > Could you please recreate the guest for further debug?

  Yes, I recreated the guest with its correct multipath lun
  configuration.  I have also attached the guest XML to this bug.

  > Besides that could you please let us know:
  >  - is the multipath the system's root? I mean / is installed/mounted on the
  > multipath device?

  Yes, the guest has only one disk.  That disk is actually a LUN from a
  fiber channel storage device with two paths on the host side.  I have
  passed through both paths to the guest, so the multipath nature of the
  target disk is known to the guest.

  In other words, the guest sees a multipath device and is using it as a
  multipath device.  The root file system is called /dev/mapper/mpatha-
  part2 on the guest.

  >  - how did you attach the device to the guest?

  Each FC LUN path on the host is mapped to a virtio-scsi controller on
  the guest using LUN passthrough.  (See the guest XML for details on
  this.)

  == Comment: #22 - Mauro Sergio Martins Rodrigues  - 2017-01-11 09:31:38 ==
  I managed to get kdump to mount rootfs and perform its tasks by setting 
KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see 
http://pastebin.hursley.ibm.com/8239

  I'm still investigating to figure out what is the reason behind this
  behavior.

  Thanks,

  --
  maurosr

  == Comment: #23 - Mauricio Faria De Oliveira  - 2017-01-11 11:56:40 ==
  Mauro,

  (In reply to comment #22)
  > I managed to get kdump to mount rootfs and perform its 

[Kernel-packages] [Bug 1448836] Re: Bluetooth firmware missing for BCM43142A0-04ca-2009

2018-01-28 Thread Christopher M. Penalver
Kai-Heng Feng, as per Broadcom, they provide firmware via Windows update:
https://www.broadcom.com/support/bluetooth/

Hence, why not have a package in Ubuntu that scripts pulling the
relevant file from Windows update, extracts the relevant bits, and moves
it into the proper location?

This is nothing more than automating what folks already do to WORKAROUND
this issue, without forcing everyone to hold their breath waiting for a
license from Broadcom.

** Changed in: linux-firmware (Ubuntu)
   Status: New => Triaged

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

Title:
  Bluetooth firmware missing for  BCM43142A0-04ca-2009

Status in linux-firmware package in Ubuntu:
  Triaged

Bug description:
  I am using an Acer E 15. I am not sure how to find out the
  specifications of my bluetooth device. I found nothing with lsusb or
  lspci. The only thing i found was that:

  dmesg | grep bluetooth
  [   12.314809] bluetooth hci0: Direct firmware load for 
brcm/BCM43142A0-04ca-2009.hcd failed with error -2

  Until Ubuntu 14.10 the bluetooth device was not recognized at all.
  Since the update to Ubuntu 15.04 i can activate it through Gnome
  system settings and make it visible. But it will not be found by any
  device and will not find any itself.

  WORKAROUND: Download:
  
https://github.com/winterheart/broadcom-bt-firmware/blob/master/brcm/BCM43142A0-04ca-2009.hcd

  and copy it to:
  /lib/firmware/brcm/BCM.hcd

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-15-generic 3.19.0-15.15
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   jonatan2465 F...m pulseaudio
   /dev/snd/controlC1:  jonatan2465 F pulseaudio
   /dev/snd/controlC0:  jonatan2465 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Apr 26 23:56:01 2015
  HibernationDevice: RESUME=UUID=83a341ec-8e0a-48f3-b194-a58b60546f21
  InstallationDate: Installed on 2015-01-07 (109 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Acer Aspire E5-571G
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-04-23 (3 days ago)
  dmi.bios.date: 09/25/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.16
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA50_HB
  dmi.board.vendor: Acer
  dmi.board.version: V1.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.16:bd09/25/2014:svnAcer:pnAspireE5-571G:pvrV1.16:rvnAcer:rnEA50_HB:rvrV1.16:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-571G
  dmi.product.version: V1.16
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1745734] Re: kernel 4.13.0-32.35 mangles display

2018-01-28 Thread Serpico
After another reboot 4.13.0-31 problem is also present with this kernel

** Tags added: regression-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/1745734

Title:
  kernel 4.13.0-32.35 mangles display

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Today I applied the latest series of updates to 16.04.  After rebooting about 
80% of the graphics display is corrupted, leaving a strip down the right side 
which is still legible.  This was evident on the desktop and also the virtual 
consoles.  Everything seemed to be running normally apart from the display.
  After some experimentation I confirmed it was the 4.13.0-32.35 kernel, I 
reverted to 4.10.0.28-generic and all was good.
  EEE-PC 901 (Intel Atom N270 with Mobile 945GSE integrated graphics)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.23
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  Date: Sat Jan 27 23:22:12 2018
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  a-user 1416 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=c9603762-f6c9-49b1-9ec2-dd0fae3ef99b
  MachineType: ASUSTeK Computer INC. 901
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=e8a6eae1-a061-4c74-bd53-a8aed65c035d ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-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-28-generic N/A
   linux-backports-modules-4.10.0-28-generic  N/A
   linux-firmware 1.157.14
  Tags:  xenial
  Uname: Linux 4.10.0-28-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/11/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 901
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTek Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2103:bd06/11/2009:svnASUSTeKComputerINC.:pn901:pvrx.x:rvnASUSTeKComputerINC.:rn901:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
  dmi.product.name: 901
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.

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

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


[Kernel-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

2018-01-28 Thread Kai-Heng Feng
https://lkml.org/lkml/2018/1/29/22

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

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The AC adapter status is incorrectly reported when the battery is
  fully charged. It always shows as if the adapter is not plugged in. If
  the battery is drained for a while, the adapter status is shown
  correctly (both connects and disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  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.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

2018-01-28 Thread Kai-Heng Feng
** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/1745032

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in linux package in Ubuntu:
  Triaged

Bug description:
  The AC adapter status is incorrectly reported when the battery is
  fully charged. It always shows as if the adapter is not plugged in. If
  the battery is drained for a while, the adapter status is shown
  correctly (both connects and disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  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.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]

2018-01-28 Thread Daniel van Vugt
Hi all,

If you would like to see fixes for issues like this in PulseAudio then
we suggest you talk to the PulseAudio people directly. You can do that
either by logging your own upstream bug or join the conversation here:
https://bugs.freedesktop.org/show_bug.cgi?id=88827

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

Title:
  A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in
  audio stream"]

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped
  working properly. It was working fine in Jaunty.

  My headphones are detected and configured by pulse, but the audio
  skips as if it's spending half of each second paused. Music is
  buffered so that after I click stop on rhythmbox (or whatever--it
  happens with whatever player I use) the audio continues until it's
  caught up.

  syslog is full of the following lines:
  Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal 
latency to 1.00 ms
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
15128 us (= 2668 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36586 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
35593 us (= 6276 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36597 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32601 us (= 5748 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32589 us (= 5748 bytes) in audio stream

  This is with
  bluez 4.45-0ubuntu4
  pulseaudio1:0.9.15-4ubuntu2 0

  pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev
  didn't help.

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

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


[Kernel-packages] [Bug 1448836] Re: Bluetooth doesn't find any device

2018-01-28 Thread Kai-Heng Feng
Unless Broadcom release its bluetooth firmware with compatible license
with linux-firmware, we can't do much here.

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

** No longer affects: linux (Ubuntu)

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

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

Title:
  Bluetooth doesn't find any device

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  I am using an Acer E 15. I am not sure how to find out the
  specifications of my bluetooth device. I found nothing with lsusb or
  lspci. The only thing i found was that:

  dmesg | grep bluetooth
  [   12.314809] bluetooth hci0: Direct firmware load for 
brcm/BCM43142A0-04ca-2009.hcd failed with error -2

  Until Ubuntu 14.10 the bluetooth device was not recognized at all.
  Since the update to Ubuntu 15.04 i can activate it through Gnome
  system settings and make it visible. But it will not be found by any
  device and will not find any itself.

  WORKAROUND: Download:
  
https://github.com/winterheart/broadcom-bt-firmware/blob/master/brcm/BCM43142A0-04ca-2009.hcd

  and copy it to:
  /lib/firmware/brcm/BCM.hcd

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-15-generic 3.19.0-15.15
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   jonatan2465 F...m pulseaudio
   /dev/snd/controlC1:  jonatan2465 F pulseaudio
   /dev/snd/controlC0:  jonatan2465 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Apr 26 23:56:01 2015
  HibernationDevice: RESUME=UUID=83a341ec-8e0a-48f3-b194-a58b60546f21
  InstallationDate: Installed on 2015-01-07 (109 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Acer Aspire E5-571G
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-04-23 (3 days ago)
  dmi.bios.date: 09/25/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.16
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA50_HB
  dmi.board.vendor: Acer
  dmi.board.version: V1.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.16:bd09/25/2014:svnAcer:pnAspireE5-571G:pvrV1.16:rvnAcer:rnEA50_HB:rvrV1.16:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-571G
  dmi.product.version: V1.16
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1447664] Re: 14e4:1687 broadcom tg3 network driver disconnects under high load

2018-01-28 Thread Kai-Heng Feng
First please file an upstream bug at https://bugzilla.kernel.org/
Product: Drivers
Component: Network

Also, looks like it's a Ubuntu certified hardware, let me ask around.

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

Title:
  14e4:1687 broadcom tg3 network driver disconnects under high load

Status in linux package in Ubuntu:
  Triaged
Status in linux package in Debian:
  New

Bug description:
  The tg3 broadcom network driver that binds with chipset 5762 goes offline and 
unable to recover (even with tg3 watchdog timeout) when network transmit is 
under high load.  Call trace:
  https://launchpadlibrarian.net/204185480/dmesg

  When this happens, only a reboot would be able to fix it.  Sometimes,
  however, bringing the interface offline and online (via ifconfig)
  would recover networking.  I've also tested with the latest tg3 driver
  (dec 2014 version) and networking is still problematic.  I have also
  disabled TSO, GSO etc... with ethtool and the bug still surfaces.
  This bug may be related to the integrated Firmware.

  Here is the procedure to replicate the issue because it is hard to
  replicate it under moderate network load.

  1. Bootup a machine with a broadcom 5762 NIC (ie. HP DeskElite 705) using a 
Ubuntu/Kubunu Live CD 14.04-15.04.
  2. from another machine: start 5 sessions, repetitively copy (scp with public 
key authentication) a 70 meg file back and forth to the tg3 machine in each 
session. (not sure if this is necessary)
  3. create a 1GB file on the tg3 machine, with something like dd 
if=/dev/urandom of=/my/test/file bs=1024 count=$((1024*1000))
  4. from another machine: repetitively scp copy that 1GB file from the tg3 
machine. This can be done with something like:

  while [ 0 ]; do
     scp -i /my/scp/private.key u...@ip.of.tg3:/my/test/file /tmp
  done;

  Networking will mostly goes offline in about 10-30 minutes.

  WORKAROUND: Add udev rule to make the changes permanent in 
/etc/udev/rules.d/80-tg3-fix.rules :
  ACTION=="add", SUBSYSTEM=="net", ATTRS{vendor}=="0x14e4", 
ATTRS{device}=="0x1687", RUN+="/sbin/ethtool -K %k highdma off"

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-15-generic 3.19.0-15.15
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kubuntu3748 F pulseaudio
   /dev/snd/controlC0:  kubuntu3748 F pulseaudio
  CasperVersion: 1.360
  Date: Thu Apr 23 11:16:24 2015
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  LiveMediaBuild: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Hewlett-Packard HP EliteDesk 705 G1 MT
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper maybe-ubiquity quiet splash ---
  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-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  RfKill:

  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/22/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L06 v02.15
  dmi.board.asset.tag: 2UA5041TG4
  dmi.board.name: 2215
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 2UA5041TG4
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL06v02.15:bd10/22/2014:svnHewlett-Packard:pnHPEliteDesk705G1MT:pvr:rvnHewlett-Packard:rn2215:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP EliteDesk 705 G1 MT
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1482390] Re: ASUS UX305LA - Battery state not detected correctly

2018-01-28 Thread Kai-Heng Feng
https://lkml.org/lkml/2018/1/29/22

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

Title:
  ASUS UX305LA - Battery state not detected correctly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Whether the AC adapter is connected or not, the battery is always
  detected as discharging:

  When AC adapter is present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%
    AC adapter : online

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54027 mWh, 100.0%
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 0 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  When AC adapter is not present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%, 04:19:49
    AC adapter : off-line

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54005 mWh, 100.0%, 04:28:31
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 12067 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  System information:

  $ sudo dmidecode
  # dmidecode 2.12
  # SMBIOS entry point at 0xace2a898
  SMBIOS 2.8 present.
  27 structures occupying 2154 bytes.
  Table at 0xAC7C6000.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
   Vendor: American Megatrends Inc.
   Version: UX305LA.202
   Release Date: 04/16/2015
   Address: 0xF
   Runtime Size: 64 kB
   ROM Size: 6464 kB
   Characteristics:
    PCI is supported
    BIOS is upgradeable
    BIOS shadowing is allowed
    Boot from CD is supported
    Selectable boot is supported
    BIOS ROM is socketed
    EDD is supported
    5.25"/1.2 MB floppy services are supported (int 13h)
    3.5"/720 kB floppy services are supported (int 13h)
    3.5"/2.88 MB floppy services are supported (int 13h)
    Print screen service is supported (int 5h)
    8042 keyboard services are supported (int 9h)
    Serial services are supported (int 14h)
    Printer services are supported (int 17h)
    ACPI is supported
    USB legacy is supported
    Smart battery is supported
    BIOS boot specification is supported
    Targeted content distribution is supported
    UEFI is supported
   BIOS Revision: 5.6

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   UUID: xxx
   Wake-up Type: Power Switch
   SKU Number: ASUS-NotebookSKU
   Family: UX

  Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Features:
    Board is a hosting board
    Board is replaceable
   Location In Chassis: MIDDLE
   Chassis Handle: 0x0003
   Type: Motherboard
   Contained Object Handles: 0

  Handle 0x0003, DMI type 3, 25 bytes
  Chassis Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Type: Notebook
   Lock: Not Present
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Boot-up State: Safe
   Power Supply State: Safe
   Thermal State: Safe
   Security Status: None
   OEM Information: 0x
   Height: Unspecified
   Number Of Power Cords: 1
   Contained Elements: 1
     (0)
   SKU Number: To be filled by O.E.M.

  Handle 0x0004, DMI type 10, 26 bytes
  On Board Device 1 Information
   Type: Video
   Status: Enabled
   Description:  VGA
  On Board Device 2 Information
   Type: Ethernet
   Status: Enabled
   Description:  GLAN
  On Board Device 3 Information
   Type: Ethernet
   Status: Enabled
   Description:  WLAN
  On Board Device 4 Information
   Type: Sound
   Status: Enabled
   Description:  Audio CODEC
  On Board Device 5 Information
   Type: SATA Controller
   Status: Enabled
   Description:  SATA Controller
  On Board Device 6 Information
   Type: Other
   Status: Enabled
   Description:  USB 2.0 Controller
  On Board Device 7 Information
   Type: Other
   Status: Enabled
   Description:  USB 3.0 Controller
  On Board Device 8 Information
   Type: Other
   Status: Enabled
   Description:  SMBus Controller
  On Board Device 9 Information
   Type: Other
   Status: Enabled
   Description:  Card Reader
  On Board Device 10 Information
   Type: Other
   Status: Enabled
   Description:  Cmos Camera
  On Board Device 11 Information
   Type: Other
   Status: Enabled
   Description:  Bluetooth

  Handle 0x0005, DMI type 11, 5 bytes
  OEM Strings
   String 1:
   String 2:
   String 3:
   String 4: 90NB08T5-M00230
   String 5:
   String 6:
   String 7:
   String 8:
   String 9:
   String 10:

  Handle 0x000C, DMI type 32, 20 

[Kernel-packages] [Bug 1448836] Re: Bluetooth firmware missing for BCM43142A0-04ca-2009

2018-01-28 Thread Christopher M. Penalver
** Summary changed:

- Bluetooth doesn't find any device
+ Bluetooth firmware missing forBCM43142A0-04ca-2009

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

Title:
  Bluetooth firmware missing for  BCM43142A0-04ca-2009

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  I am using an Acer E 15. I am not sure how to find out the
  specifications of my bluetooth device. I found nothing with lsusb or
  lspci. The only thing i found was that:

  dmesg | grep bluetooth
  [   12.314809] bluetooth hci0: Direct firmware load for 
brcm/BCM43142A0-04ca-2009.hcd failed with error -2

  Until Ubuntu 14.10 the bluetooth device was not recognized at all.
  Since the update to Ubuntu 15.04 i can activate it through Gnome
  system settings and make it visible. But it will not be found by any
  device and will not find any itself.

  WORKAROUND: Download:
  
https://github.com/winterheart/broadcom-bt-firmware/blob/master/brcm/BCM43142A0-04ca-2009.hcd

  and copy it to:
  /lib/firmware/brcm/BCM.hcd

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-15-generic 3.19.0-15.15
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   jonatan2465 F...m pulseaudio
   /dev/snd/controlC1:  jonatan2465 F pulseaudio
   /dev/snd/controlC0:  jonatan2465 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Apr 26 23:56:01 2015
  HibernationDevice: RESUME=UUID=83a341ec-8e0a-48f3-b194-a58b60546f21
  InstallationDate: Installed on 2015-01-07 (109 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Acer Aspire E5-571G
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-04-23 (3 days ago)
  dmi.bios.date: 09/25/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.16
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA50_HB
  dmi.board.vendor: Acer
  dmi.board.version: V1.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.16:bd09/25/2014:svnAcer:pnAspireE5-571G:pvrV1.16:rvnAcer:rnEA50_HB:rvrV1.16:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-571G
  dmi.product.version: V1.16
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1447664] Re: 14e4:1687 broadcom tg3 network driver disconnects under high load

2018-01-28 Thread Paulo Abadie Guedes
Hello, I am still having this bug. I'm working with several HP machines, with 
the same model as Yngvi. Here it is (from dmesg messages):
Hardware name: HP HP EliteDesk 705 G3 Brazil Desktop Mini/8266, BIOS P26 Ver. 
02.03 12/22/2016

Interesting to notice that it always happens with a 10/100 switch, but
never occurs with a gigabit one.

I've compiled and tested the 4.15.0-rc8 release candidade, which has the
commit 4419bb1cedcda0272e1dc410345c5a1d1da0e367, but it does not solve
the issue. I added a few printk and can see that the module is correctly
compiled and loaded, but my machine is not a Dell. Hence, the "if"
condition fails and the body is not executed.

I tried also to force the patch, by keeping the "if body" and removing the 
condition, just to see what happens (with another printk to prove that it 
runs). The code runs (limiting MRRS t0 2048, I think), but it does not solve 
the bug. 
It complains that TSC is unstable, right after tg3 breaks. Here is a dmesg 
snippet, maybe it helps.


<...>
[  155.816404] clocksource: timekeeping watchdog on CPU0: Marking clocksource 
'tsc' as unstable because the skew is too large:
[  155.816447] clocksource:   'refined-jiffies' wd_now: 
fffdcbf3 wd_last: fffdc110 mask: 
[  155.816490] clocksource:   'tsc' cs_now: 7d3f16e620 
cs_last: 7b2987b172 mask: 
[  155.816533] tsc: Marking TSC unstable due to clocksource watchdog
[  155.939181] tg3 :01:00.0: tg3_stop_block timed out, ofs=4c00 enable_bit=2
[  156.103998] tg3 :01:00.0 eth0: Link is down
[  156.322988] TSC found unstable after boot, most likely due to broken BIOS. 
Use 'tsc=unstable'.
[  156.323040] sched_clock: Marking unstable (156322980975, 
5436)<-(156582881282, -259894745)
[  156.323144] clocksource: Switched to clocksource refined-jiffies
<...>

If you want to take a deeper look, there are a few logs here. Tried also
with "tsc=unstable" and other boot parameters, mostly to see if any
would help (feeling lucky, perhaps?). Nothing changed, the bug is still
in here. They show mostly the same messages, to me.

log_01_acpi_off.txt
https://pastebin.com/FGQNiLqk

log_02_maxcpus_1.txt
https://pastebin.com/2eEJnA3Z

log_03_nmi_watchdog_off.txt
https://pastebin.com/Su44AqiX

log_04_nmi_watchdog_off.txt
https://pastebin.com/4ja0UZ0c

log_05_noapic_nolapic.txt
https://pastebin.com/fZNJbME5

Well, any ideas? I can reproduce the problem 100% of the time. Would you
like me to test any other patch?

Kai-Heng Feng, you mention "it's better to ask HP and Broadcom to fix
the issue". I agree, but how can we do that?

Thank you,
Paulo

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

Title:
  14e4:1687 broadcom tg3 network driver disconnects under high load

Status in linux package in Ubuntu:
  Triaged
Status in linux package in Debian:
  New

Bug description:
  The tg3 broadcom network driver that binds with chipset 5762 goes offline and 
unable to recover (even with tg3 watchdog timeout) when network transmit is 
under high load.  Call trace:
  https://launchpadlibrarian.net/204185480/dmesg

  When this happens, only a reboot would be able to fix it.  Sometimes,
  however, bringing the interface offline and online (via ifconfig)
  would recover networking.  I've also tested with the latest tg3 driver
  (dec 2014 version) and networking is still problematic.  I have also
  disabled TSO, GSO etc... with ethtool and the bug still surfaces.
  This bug may be related to the integrated Firmware.

  Here is the procedure to replicate the issue because it is hard to
  replicate it under moderate network load.

  1. Bootup a machine with a broadcom 5762 NIC (ie. HP DeskElite 705) using a 
Ubuntu/Kubunu Live CD 14.04-15.04.
  2. from another machine: start 5 sessions, repetitively copy (scp with public 
key authentication) a 70 meg file back and forth to the tg3 machine in each 
session. (not sure if this is necessary)
  3. create a 1GB file on the tg3 machine, with something like dd 
if=/dev/urandom of=/my/test/file bs=1024 count=$((1024*1000))
  4. from another machine: repetitively scp copy that 1GB file from the tg3 
machine. This can be done with something like:

  while [ 0 ]; do
     scp -i /my/scp/private.key u...@ip.of.tg3:/my/test/file /tmp
  done;

  Networking will mostly goes offline in about 10-30 minutes.

  WORKAROUND: Add udev rule to make the changes permanent in 
/etc/udev/rules.d/80-tg3-fix.rules :
  ACTION=="add", SUBSYSTEM=="net", ATTRS{vendor}=="0x14e4", 
ATTRS{device}=="0x1687", RUN+="/sbin/ethtool -K %k highdma off"

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-15-generic 3.19.0-15.15
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS 

[Kernel-packages] [Bug 1728739] Re: Attempt to map rbd image from ceph jewel/luminous hangs

2018-01-28 Thread Aaron
Same issue for me:

root@myserver:~# uname -r
4.4.0-112-generic
root@myserver:~# ceph version
ceph version 12.2.2 (cf0baba3b47f9427c6c97e2144b094b7e5ba) luminous (stable)
root@myserver:~# rbd create testimage --size 10G
root@myserver:~# rbd ls -l
NAMESIZE PARENT FMT PROT LOCK 
testimage 10240M  2   
root@myserver:~# rbd map testimage
rbd: sysfs write failed
In some cases useful info is found in syslog - try "dmesg | tail".
rbd: map failed: (110) Connection timed out
root@myserver:~# dmesg | tail
[ 1392.958472] libceph: mon0 51.254.215.26:6789 feature set mismatch, my 
106b84a842a42 < server's 40106b84a842a42, missing 400
[ 1392.958721] libceph: mon0 51.254.215.26:6789 missing required protocol 
features

... same last two messages repeat

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

Title:
  Attempt to map rbd image from ceph jewel/luminous hangs

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Attempting to map an rbd image using the 4.4 LTS (Xenial) kernel
  client from a Jewel or Luminous Ceph cluster with optimal tunables
  fails due to feature set mismatch.

  The Jewel release of Ceph introduced a new set of CRUSH tunables.
  These tunables were first introduced in the 4.5 Linux kernel and are
  thus not available in the 16.04 LTS 4.4 Linux Kernel. Attempting to
  map RBD images as block devices will fail due to not being able to
  understand these new tunables:

  (from kern.log)

  Oct 30 21:19:05 ceph-7 kernel: [  815.674075] Key type ceph registered
  Oct 30 21:19:05 ceph-7 kernel: [  815.676862] libceph: loaded (mon/osd proto 
15/24)
  Oct 30 21:19:05 ceph-7 kernel: [  815.678970] rbd: loaded (major 251)
  Oct 30 21:19:05 ceph-7 kernel: [  815.689556] libceph: mon0 10.5.0.19:6789 
feature set mismatch, my 106b84a842a42 < server's 40106b84a842a42, missing 
400
  Oct 30 21:19:05 ceph-7 kernel: [  815.692897] libceph: mon0 10.5.0.19:6789 
missing required protocol features

  Support for the new CRUSH tunables were added in upstream kernel 4.5
  in http://www.spinics.net/lists/ceph-devel/msg28421.html.

  [Test Case]

  1. Deploy a Jewel or Luminous Ceph cluster.
  2. Create rbd image suitable for the kernel client:
$ rbd create --pool rbd --image-feature layering --size 1G test
  3. Map the rbd image to the local server:
$ rbd map --pool rbd test

  [Regression Potential]

  Minimal. Code is limited to kernel rbd driver and new code should
  primarily affect clients connecting to clusters with the new tunables
  options.

  [Additional Info]

  A workaround is to change the crush tunables configured for the Ceph
  cluster to a legacy version (hammer or lower) via:

  $ ceph osd crush tunables hammer

  However, changing the tunables to hammer fails to allow the cluster to take 
advantage of newer placement strategies which reduces the amount of data 
movement throughout the cluster.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 01:23 seq
   crw-rw 1 root audio 116, 33 Oct 31 01:23 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-0001
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic 
root=UUID=d7006b2f-ace6-464d-8b21-17180b3ed360 ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-98-generic N/A
   linux-backports-modules-4.4.0-98-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-98-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.1-1ubuntu1~cloud0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-zesty
  dmi.modalias: 

[Kernel-packages] [Bug 1745118] Re: Unable to boot with i386 4.13.0-25 / 4.13.0-26 / 4.13.0-31 kernel on Xenial / Artful

2018-01-28 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1745118

** Tags added: iso-testing

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

Title:
  Unable to boot with i386 4.13.0-25 / 4.13.0-26 / 4.13.0-31 kernel on
  Xenial / Artful

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  Some SRU testing node cannot boot with the latest 32bit 4.13 linux-hwe
  kernel.

  Take node "fozzie"(Dell PowerEdge R320) for example, it works with
  4.13.0-21.24~16.04.1 but not 4.13.0-25 / 4.13.0-26 / 4.13.0-31 kernel
  on Xenial.

  From the BMC console, I can see the grub menu on boot and after that
  it will drop into a boot loop.

  This can be reproduced on Artful 4.13 as well.

  Note that this kernel works for some of the node in our test pool
  (Intel SDP - Denlow)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-21-generic 4.13.0-21.24~16.04.1
  ProcVersionSignature: User Name 4.13.0-21.24~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Wed Jan 24 08:49:57 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe-edge
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 24 09:17 seq
   crw-rw 1 root audio 116, 33 Jan 24 09:17 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: Dell Inc. PowerEdge R320
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=0845f9a0-ab8c-4dfa-8385-af21f2f2b9ad ro
  ProcVersionSignature: User Name 4.13.0-21.24~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.157.14
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images
  Uname: Linux 4.13.0-21-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/11/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.4
  dmi.board.name: 0DY523
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.4:bd05/11/2012:svnDellInc.:pnPowerEdgeR320:pvr:rvnDellInc.:rn0DY523:rvrA03:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R320
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1738736] Re: ACPI error message flooding syslog

2018-01-28 Thread Alex Garel
Ok I finally got the time to test it on upstream kernel.

$ uname -a
Linux tignasse 4.15.0-041500rc9-generic #201801212130 SMP Mon Jan 22 02:31:37 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux


# lsb_release -a
LSB Version:
core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:printing-9.20160110ubuntu5-amd64:printing-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
Distributor ID: Ubuntu
Description:Ubuntu 17.10
Release:17.10
Codename:   artful


The bug is still there, flooding my syslog very fast

$ tail -f /var/log/syslog
Jan 28 21:15:00 tignasse kernel: [  115.269198] ACPI Error: Needed type 
[Reference], found [Integer] a4664840 (20170831/exresop-103)
Jan 28 21:15:00 tignasse kernel: [  115.269227] ACPI Exception: 
AE_AML_OPERAND_TYPE, While resolving operands for [Store] (20170831/dswexec-461)
Jan 28 21:15:00 tignasse kernel: [  115.269254] No Local Variables are 
initialized for Method [_Q50]
Jan 28 21:15:00 tignasse kernel: [  115.269260] No Arguments are initialized 
for method [_Q50]
Jan 28 21:15:00 tignasse kernel: [  115.269269] ACPI Error: Method 
parse/execution failed \_SB.PCI0.LPCB.H_EC._Q50, AE_AML_OPERAND_TYPE 
(20170831/psparse-550)



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

Title:
  ACPI error message flooding syslog

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This message :

  Dec 18 09:20:13 tignasse kernel: [   85.652805] ACPI Error: Needed type 
[Reference], found [Integer] 99eae08481f8 (20170531/exresop-103)
  Dec 18 09:20:13 tignasse kernel: [   85.652831] ACPI Exception: 
AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] 
(20170531/dswexec-461)
  Dec 18 09:20:13 tignasse kernel: [   85.652847] ACPI Error: Method 
parse/execution failed \_SB.PCI0.LPCB.H_EC._Q50, AE_AML_OPERAND_TYPE 
(20170531/psparse-550)

  Is flooding my syslog at a pace of on message every 200 ms !

  This is really annoying.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-19-generic 4.13.0-19.22
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alex   5166 F pulseaudio
   /dev/snd/controlC1:  alex   5166 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Dec 18 09:22:16 2017
  HibernationDevice: RESUME=UUID=870c2fd1-8a8f-49bb-9bf4-dbefaa08e583
  InstallationDate: Installed on 2015-11-10 (768 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Intel Corporation Skylake Platform
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=6814e3c1-8cea-4ecc-964d-535fd18782e9 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-23 (24 days ago)
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: WhiteTip Mountain1 Fab2
  dmi.board.vendor: Topstar
  dmi.board.version: RVP7
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 9
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd11/06/2015:svnIntelCorporation:pnSkylakePlatform:pvr0.1:rvnTopstar:rnWhiteTipMountain1Fab2:rvrRVP7:cvnDefaultstring:ct9:cvrDefaultstring:
  dmi.product.family: Skylake System
  dmi.product.name: Skylake Platform
  dmi.product.version: 0.1
  dmi.sys.vendor: Intel Corporation

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

-- 
Mailing list: https://launchpad.net/~kernel-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) due to PTI

2018-01-28 Thread Steve
Works fine for me with 4.14.15-041415-generic. I did not try disabling
PTI with 4.13.0-26-generic. Also, I'll note that I only noticed this
problem after updating my BIOS (including the latest Intel microcode
update and Intel ME patch). Computer: Dell XPS 9360

-- 
You 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) due to PTI

Status in linux package in Ubuntu:
  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 1744806] Re: Bluetooth is turned off at boot with latest update (bluez 5.37-0ubuntu5.2)

2018-01-28 Thread Daniel van Vugt
** Package changed: bluez (Ubuntu) => linux (Ubuntu)

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

Title:
  Bluetooth is turned off at boot with latest update (bluez
  5.37-0ubuntu5.2)

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  With latest update, BLUEZ is now off right after boot, as opposed to
  previous behaviour that was on/off depending on last setting.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5.2
  ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan 22 16:08:20 2018
  InstallationDate: Installed on 2017-09-29 (115 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 003: ID 04f2:b59d Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76 Lemur
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-31-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=/dev/mapper/ubuntu--vg-swap_1 vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/17/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.12
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Lemur
  dmi.board.vendor: System76
  dmi.board.version: lemu7
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd02/17/2017:svnSystem76:pnLemur:pvrlemu7:rvnSystem76:rnLemur:rvrlemu7:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Lemur
  dmi.product.version: lemu7
  dmi.sys.vendor: System76
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: AC:ED:5C:F6:32:44  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:667 acl:0 sco:0 events:38 errors:0
TX bytes:405 acl:0 sco:0 commands:38 errors:0
  mtime.conffile..etc.bluetooth.input.conf: 2017-12-06T11:16:58.937870
  mtime.conffile..etc.bluetooth.main.conf: 2018-01-18T18:34:20.102879

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

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


[Kernel-packages] [Bug 1734172] Re: Upgrade ZFS to 0.7.3

2018-01-28 Thread Sam Van den Eynde
What is the policy for ZFS release updates? Are they limited to LTS
releases? Will all HWE kernels get upgraded eventually?

As an example, would Xenial eventually see ZFS 0.7 or even 0.8 or 0.9 ?

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

Title:
  Upgrade ZFS to 0.7.3

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  ZFS v0.7 is out, current version is 0.7.3:

  https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.7.3 .

  
  It is desired to have the latest stable version at least in LTS.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: zfsutils-linux 0.6.5.11-1ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  Date: Thu Nov 23 19:03:47 2017
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: zfs-linux
  UpgradeStatus: Upgraded to bionic on 2017-05-20 (187 days ago)

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

-- 
Mailing list: https://launchpad.net/~kernel-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) due to PTI

2018-01-28 Thread DenisP
For me hibernation doesn't work with 4.14.15-041415-generic Kernel.
However the symptoms are different than with other kernels that have
problems with hibernation post 4.13.0-21 kernel, with 4.14.15 the resume
from hibernation is performed but my gnome session is broken and lost
after the resume. Tested on Lenovo T470 on Ubuntu 17.10.

-- 
You 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) due to PTI

Status in linux package in Ubuntu:
  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) due to PTI

2018-01-28 Thread richbl
@denisp, what do you mean "broken and lost after the resume?" What
specifically is occurring? What errors are getting generated, etc?

-- 
You 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) due to PTI

Status in linux package in Ubuntu:
  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 1728739] Re: Attempt to map rbd image from ceph jewel/luminous hangs

2018-01-28 Thread Aaron
Actually, upgrading my kernel to 4.13 fixed the issue for me.

root@myserver:~$ uname -r
4.13.0-32-generic
root@myserver:~$ rbd ls
testimage
root@myserver:~$ rbd map testimage
/dev/rbd0
root@myserver:~$

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

Title:
  Attempt to map rbd image from ceph jewel/luminous hangs

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Attempting to map an rbd image using the 4.4 LTS (Xenial) kernel
  client from a Jewel or Luminous Ceph cluster with optimal tunables
  fails due to feature set mismatch.

  The Jewel release of Ceph introduced a new set of CRUSH tunables.
  These tunables were first introduced in the 4.5 Linux kernel and are
  thus not available in the 16.04 LTS 4.4 Linux Kernel. Attempting to
  map RBD images as block devices will fail due to not being able to
  understand these new tunables:

  (from kern.log)

  Oct 30 21:19:05 ceph-7 kernel: [  815.674075] Key type ceph registered
  Oct 30 21:19:05 ceph-7 kernel: [  815.676862] libceph: loaded (mon/osd proto 
15/24)
  Oct 30 21:19:05 ceph-7 kernel: [  815.678970] rbd: loaded (major 251)
  Oct 30 21:19:05 ceph-7 kernel: [  815.689556] libceph: mon0 10.5.0.19:6789 
feature set mismatch, my 106b84a842a42 < server's 40106b84a842a42, missing 
400
  Oct 30 21:19:05 ceph-7 kernel: [  815.692897] libceph: mon0 10.5.0.19:6789 
missing required protocol features

  Support for the new CRUSH tunables were added in upstream kernel 4.5
  in http://www.spinics.net/lists/ceph-devel/msg28421.html.

  [Test Case]

  1. Deploy a Jewel or Luminous Ceph cluster.
  2. Create rbd image suitable for the kernel client:
$ rbd create --pool rbd --image-feature layering --size 1G test
  3. Map the rbd image to the local server:
$ rbd map --pool rbd test

  [Regression Potential]

  Minimal. Code is limited to kernel rbd driver and new code should
  primarily affect clients connecting to clusters with the new tunables
  options.

  [Additional Info]

  A workaround is to change the crush tunables configured for the Ceph
  cluster to a legacy version (hammer or lower) via:

  $ ceph osd crush tunables hammer

  However, changing the tunables to hammer fails to allow the cluster to take 
advantage of newer placement strategies which reduces the amount of data 
movement throughout the cluster.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 01:23 seq
   crw-rw 1 root audio 116, 33 Oct 31 01:23 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-0001
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic 
root=UUID=d7006b2f-ace6-464d-8b21-17180b3ed360 ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-98-generic N/A
   linux-backports-modules-4.4.0-98-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-98-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.1-1ubuntu1~cloud0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-zesty
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.1-1ubuntu1~cloud0:bd04/01/2014:svnOpenStackFoundation:pnOpenStackNova:pvr15.0.6:cvnQEMU:ct1:cvrpc-i440fx-zesty:
  dmi.product.name: OpenStack Nova
  dmi.product.version: 15.0.6
  dmi.sys.vendor: OpenStack Foundation

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

-- 
Mailing list: https://launchpad.net/~kernel-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) due to PTI

2018-01-28 Thread Krystian Maculewicz
Not working on Dell Inspirion 7328 and Lenovo Yoga 520, last working
kernel 4.13.0.21. Nopti doesn't solve issue.

-- 
You 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) due to PTI

Status in linux package in Ubuntu:
  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 1510570] Re: Bluetooth LE pairing fail

2018-01-28 Thread Daniel van Vugt
Good news: Bug 1744806 has been resolved with a kernel update. So we're
still able to continue testing and releasing this one.

** Tags removed: verification-failed verification-failed-xenial
** Tags added: verification-needed-xenial

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

Title:
  Bluetooth LE pairing fail

Status in OEM Priority Project:
  Confirmed
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  When the Bluetooth adapter is not powered on it is not possible to use
  it in normal way. We used to have a hack to force powering on by using
  an udev rule but this doe snot work anymore. Luckily the BlueZ has
  introduced "AutoEnable" option that makes the stack power on adapters by
  itself.

  Backporting this to xenial will improve life of the desktop users and
  will not require them to hack the solution on their own. The fix itself
  uses the well known solution to this problem that is floating around
  there for a while.

  The upload fixes the bug by enabling the 'AutoEnable' option in the
  bluetoothd config file.

  [Original Report]

  . 15.10 we now have bluez 5 so we can pair BLE devices like the
  Microsoft Arc Touch Bluetooth Mouse.

  But this pairing doesn't work very well. Mouse is seen but pairing fail.
  More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5

  This is due to udev rule that use "hcitool" to power on device.
  Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used
  instead of udev rules.

  here is a commit with this parameter:
  http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138

  [Test Case]

  On xenial install from ppa:
  https://launchpad.net/~bluetooth/+archive/ubuntu/bluez

  Now reboot the machine. The BT adapter shall be
  powered on.

  [Regression Potential]

  If things go wrong the adapter will not be powered on after the system
  boots up. Therefore while testing please focus on the adapter state,
  i.e. powered on or off.

  [Other Info]

  This fix is included in the development release, see:
  http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22

  [What to upload]

  For xenial as in:

  ) https://launchpad.net/~bluetooth/+archive/ubuntu/bluez
  ) 
https://launchpadlibrarian.net/347480725/bluez_5.37-0ubuntu5_5.37-0ubuntu5.2~build1.diff.gz

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

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


[Kernel-packages] [Bug 1729389] Re: [Intel 8260/8265] Bluetooth peripherals work for a few seconds, then don't react

2018-01-28 Thread Daniel van Vugt
This bug is effectively closed, rightly or wrongly. So unless you're the
original reporter (Jeppe Bundsgaard), please open a new bug using this
command:

  ubuntu-bug linux

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

Title:
  [Intel 8260/8265] Bluetooth peripherals work for a few seconds, then
  don't react

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Confirmed
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Confirmed
Status in linux-firmware source package in Artful:
  Fix Released

Bug description:
  SRU Justification

  Impact: Bluetooth peripherals work initially but stop working shortly
  with Linux 4.13.

  Fix: Updated firmware from Intel containing a fix for the issue.

  Regression Potential: Any firmware updates may bring regressions,
  however this is a bug fix update and therefore regression potential is
  expected to be minimal.

  ---

  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  ---
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp.
   Bus 001 Device 005: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 13d3:5664 IMC Networks
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
    UP RUNNING PSCAN ISCAN INQUIRY
    RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
    TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

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

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


[Kernel-packages] [Bug 1720842] Re: USB Keyboard "Masione VMJ-02" ID 1c4f:0056 SiGma Micro: Ctrl / Super / Alt incorrectly recognized as L-Shift

2018-01-28 Thread PeterDaveHello
I have the same problem with device id 1c4f:0101, but I have no problem
with my Win10 on the same machine

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

Title:
  USB Keyboard "Masione VMJ-02" ID 1c4f:0056 SiGma Micro: Ctrl / Super /
  Alt incorrectly recognized as L-Shift

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It's a new keyboard and basically unusable due to the incorrect key
  recognition by usbhid module. I have scoured the net for similar
  problems, and found an identical sounding bug for an Azio keyboard. I
  tried that driver after modifying the source code to apply to
  1c4f:0056, but to no avail.

  See
  https://askubuntu.com/questions/648798/ctrl-and-alt-works-as-shift

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  peter  1368 F pulseaudio
   /dev/snd/controlC1:  peter  1368 F pulseaudio
   /dev/snd/controlC0:  peter  1368 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  2 18:40:54 2017
  InstallationDate: Installed on 2017-10-01 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic.efi.signed 
root=UUID=3f1207ff-f3cc-4230-961b-9f35ffd0da4c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Kernel-packages] [Bug 1682731] Re: package bluez 5.43-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 [invoke-rc.d: initscript bluetooth

2018-01-28 Thread Daniel van Vugt
razvananca,

You were automatically subscribed to this bug because two bugs you
reported are duplicates of this one. If you wish to not receive mail
about this any more then you will need to click on "Mute bug mail" for
this bug:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1682731/+mute

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

Title:
  package bluez 5.43-0ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1
  [invoke-rc.d: initscript bluetooth, action "restart" failed.]

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  passwd root

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: bluez 5.43-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Apr 14 10:38:35 2017
  DpkgHistoryLog: Start-Date: 2017-04-14  10:35:52
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-04-02 (12 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Micro-Star International Co., Ltd. CR61 2M/CX61 2OC/CX61 2OD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=f5a8ba7b-5759-4d4c-99a4-6cad4db08728 ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: bluez
  Title: package bluez 5.43-0ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16GDIMS.20G
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-16GD
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: CR61 2M/CX61 2OC/CX61 2OD
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16GDIMS.20G:bd01/18/2014:svnMicro-StarInternationalCo.,Ltd.:pnCR612M/CX612OC/CX612OD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16GD:rvrREV1.0:cvnCR612M/CX612OC/CX612OD:ct10:cvrN/A:
  dmi.product.name: CR61 2M/CX61 2OC/CX61 2OD
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 54:27:1E:9E:18:49  ACL MTU: 820:8  SCO MTU: 255:16
DOWN 
RX bytes:1274 acl:0 sco:0 events:129 errors:0
TX bytes:25311 acl:0 sco:0 commands:129 errors:0

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

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


[Kernel-packages] [Bug 1740855] Re: Ubuntu 17.10 freeze after a while after startup

2018-01-28 Thread Thomas Plorin
I tested this kernel for 12 days. 
I have always the "flittering" from time to time (subjectiv not so often). I 
think there are not so  much total-freezes than before. But I have had one or 
two with this kernel.

It is very diffcult to say, when the flittering begins. Sometimes it
began, when I opened google-maps in chrome. Often I hear often with
rhythmbox over upnp. Probably this information could be helpfull. But I
could determine how to reproduce it with concret steps.

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

Title:
  Ubuntu 17.10 freeze after a while after startup

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  after upgrading to ubuntu 17.10, my pc freezes every time after a
  while after startup. Mostly when browsing webpages (google-chrome);
  playing videos (youtube) oder while development with eclipse / java.
  Some Times the screens begin to "flittering", sometimes the desktop
  freezes completly. The only thing, that works ist : ALT+PRINT+REISUB
  to reset an restart the pc. Sometimes this Magic-Keys doensn't work.
  Before 17.10 I use 17.04 Ubuntu, and everything was fine!

  I've got a gigabyte Graficcard with 2 TFT-Displays connected. One with
  dvi, one with hdmi. This worked fine in 17.04 and also in 17.10,
  instead of the freezing in 17.10.

  lsb-release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-21-generic 4.13.0-21.24
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  thomas 1470 F pulseaudio
   /dev/snd/controlC0:  thomas 1470 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan  2 12:23:31 2018
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=3880cd93-060f-4216-aefa-20044b4df8ee ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-26 (36 days ago)
  dmi.bios.date: 11/25/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-USB3 6.0
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3 6.0
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Kernel-packages] [Bug 1742316] Re: DVB Card with SAA7146 chipset not working

2018-01-28 Thread TauSo
Thanks for trying, but unfortunately your kernel does not resolve the
problem:

4.13.0-32-generic #35~lp1742316 SMP Fri Jan 26 21:40:59 CST 2018 i686
i686 i686 GNU/Linux


[6.429543] [ cut here ]
[6.429548] kernel BUG at 
/home/khfeng/Sources/linux-lp1742316-saa7146/drivers/media/common/saa7146/saa7146_core.c:163!
[6.429561] invalid opcode:  [#1] SMP
[6.429708] Modules linked in: snd_hda_codec_hdmi(+) snd_hda_codec_realtek 
budget_av(+) saa7146_vv snd_hda_codec_generic budget_core ttpci_eeprom 
snd_hda_intel saa7146 ppdev videobuf_dma_sg videobuf_core dvb_core v4l2_common 
snd_hda_codec videodev snd_hda_core snd_hwdep intel_powerclamp media joydev 
input_leds snd_pcm lpc_ich snd_timer snd soundcore shpchp parport_pc parport 
nuvoton_cir mac_hid rc_core nct6775 hwmon_vid coretemp ip_tables x_tables 
autofs4 hid_generic usbhid hid gma500_gfx i2c_algo_bit drm_kms_helper 
syscopyarea sysfillrect sysimgblt ahci fb_sys_fops libahci drm r8169 mii video
[6.431394] CPU: 3 PID: 306 Comm: systemd-udevd Not tainted 
4.13.0-32-generic #35~lp1742316
[6.431654] Hardware name: To Be Filled By O.E.M. To Be Filled By 
O.E.M./AD2700-ITX, BIOS P1.60 04/19/2013
[6.431949] task: f5202700 task.stack: f4886000
[6.432108] EIP: saa7146_vmalloc_build_pgtable+0x180/0x1020 [saa7146]
[6.432301] EFLAGS: 00010246 CPU: 3
[6.432406] EAX: f21e2568 EBX: f8365000 ECX: 0002 EDX: fff1c000
[6.432592] ESI:  EDI: f871f000 EBP: f4887c44 ESP: f4887c20
[6.432784]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[6.432954] CR0: 80050033 CR2: 00b6e924 CR3: 35048940 CR4: 06f0
[6.433142] Call Trace:
[6.433229]  ttpci_budget_init+0x26c/0x530 [budget_core]
[6.433398]  budget_av_attach+0x75/0x4e8 [budget_av]
[6.433556]  ? vprintk_func+0x29/0x70
[6.433666]  ? printk+0x13/0x15
[6.433767]  ? saa7146_init_one+0x69f/0x770 [saa7146]
[6.433925]  saa7146_init_one+0x70b/0x770 [saa7146]
[6.434080]  ? __pm_runtime_resume+0x51/0x80
[6.434213]  pci_device_probe+0xc2/0x160
[6.434328]  driver_probe_device+0x2b9/0x410
[6.434457]  __driver_attach+0x99/0xe0
[6.434575]  ? driver_probe_device+0x410/0x410
[6.434708]  bus_for_each_dev+0x57/0x90
[6.434832]  driver_attach+0x19/0x20
[6.434937]  ? driver_probe_device+0x410/0x410
[6.440934]  bus_add_driver+0x187/0x230
[6.440938]  ? 0xf8522000
[6.440943]  driver_register+0x56/0xd0
[6.440946]  ? 0xf8522000
[6.440950]  __pci_register_driver+0x33/0x40
[6.440957]  saa7146_register_extension+0x50/0x80 [saa7146]
[6.440966]  budget_av_init+0xd/0x1000 [budget_av]
[6.440971]  do_one_initcall+0x46/0x180
[6.440977]  ? kfree+0x134/0x140
[6.440980]  ? kfree+0x134/0x140
[6.440983]  ? kfree+0x134/0x140
[6.440987]  ? kmem_cache_alloc_trace+0x13d/0x1a0
[6.440992]  ? do_init_module+0x21/0x1cc
[6.440995]  ? do_init_module+0x21/0x1cc
[6.441000]  do_init_module+0x50/0x1cc
[6.441004]  load_module+0x1533/0x1aa0
[6.441011]  ? kernel_read_file+0x26e/0x2a0
[6.441018]  SyS_finit_module+0x8a/0xe0
[6.441025]  do_fast_syscall_32+0x71/0x150
[6.441032]  entry_SYSENTER_32+0x4e/0x7c
[6.441034] EIP: 0xb7f5acf9
[6.441036] EFLAGS: 0292 CPU: 3
[6.441039] EAX: ffda EBX: 0018 ECX: b7d4ba71 EDX: 
[6.441042] ESI: 01a60ec0 EDI: 01a5e940 EBP:  ESP: bfc713bc
[6.441045]  DS: 007b ES: 007b FS:  GS: 0033 SS: 007b
[6.441049] Code: e8 e8 c5 eb ff ff 85 c0 59 75 7c 8b 45 ec 8d 65 f4 5b 5e 
5f 5d c3 90 8d 74 26 00 83 3d f0 ec e1 dd 02 0f 85 07 ff ff ff 8d 76 00 <0f> 0b 
8d b6 00 00 00 00 0f 0b 8d b6 00 00 00 00 c7 45 dc 00 00
[6.441125] EIP: saa7146_vmalloc_build_pgtable+0x180/0x1020 [saa7146] 
SS:ESP: 0068:f4887c20
[6.441210] ---[ end trace 4087a60d1b1a4971 ]---

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

Title:
  DVB Card with SAA7146 chipset not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 17.10 (from 16.04 with 4.4 kernel) my PCI DVB card
  Terratec Cinergy DVB-1200 with SAA7146 chipset is not working anymore.
  There is a kernel bug message while booting and no /dev/dvb device is
  created. Tried also with newest mainline 4.14 kernel - same error.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-25-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 

[Kernel-packages] [Bug 1743908] Re: MODSIGN: Couldn't get UEFI db list

2018-01-28 Thread Wellington Uemura
Not in my case.

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

Title:
  MODSIGN: Couldn't get UEFI db list

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Kernel is having problem loading or validating certificates. Looking
  over the internet looks like this is a kernel issue.

  Patchs from other distro:
  https://bugzilla.redhat.com/show_bug.cgi?id=1497559
  - 0001-Make-get_cert_list-not-complain-about-cert-lists-tha.patch
  - 0002-Add-efi_status_to_str-and-rework-efi_status_to_err.patch
  - 0003-Make-get_cert_list-use-efi_status_to_str-to-print-er.patch

  
  [1.203191] Loaded X.509 cert 'Build time autogenerated kernel key: 
ecdf0c3ef21a8b4ca325a4d1db7d45108ca78734'
  [1.203352] Couldn't get size: 0x800e
  [1.203354] MODSIGN: Couldn't get UEFI db list
  [1.205030] Loaded UEFI:MokListRT cert 'Canonical Ltd. Master Certificate 
Authority: ad91990bc22ab1f517048c23b6655a268e345a63' linked to secondary sys 
keyring
  [1.205102] Couldn't get size: 0x800e
  [1.205103] MODSIGN: Couldn't get UEFI dbx list

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  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:  wellington   1429 F pulseaudio
   /dev/snd/pcmC1D3p:   wellington   1429 F...m pulseaudio
   /dev/snd/controlC1:  wellington   1429 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 17 22:37:13 2018
  HibernationDevice: RESUME=UUID=192fbe7e-0dbf-47fc-8277-75569f69f16e
  InstallationDate: Installed on 2018-01-16 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  IwConfig:
   lono wireless extensions.
   
   enp7s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic.efi.signed 
root=UUID=aa7179de-345d-4e48-8bbd-6397120a155a ro amd_iommu=fullflush iommu=pt
  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.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 990FXA-UD5 R5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd04/01/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn990FXA-UD5R5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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 filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Kernel-packages] [Bug 1745734] Re: kernel 4.13.0-32.35 mangles display

2018-01-28 Thread Serpico
Installed kernel 4.13.0-31 via Synaptic, booted up with it --> display works 
fine 
Shutted down --> booted up with kernel 4.13.0-32 ( the one from the update ) 
--> no display issue, display works fine...strange

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

Title:
  kernel 4.13.0-32.35 mangles display

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Today I applied the latest series of updates to 16.04.  After rebooting about 
80% of the graphics display is corrupted, leaving a strip down the right side 
which is still legible.  This was evident on the desktop and also the virtual 
consoles.  Everything seemed to be running normally apart from the display.
  After some experimentation I confirmed it was the 4.13.0-32.35 kernel, I 
reverted to 4.10.0.28-generic and all was good.
  EEE-PC 901 (Intel Atom N270 with Mobile 945GSE integrated graphics)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.23
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  Date: Sat Jan 27 23:22:12 2018
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  a-user 1416 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=c9603762-f6c9-49b1-9ec2-dd0fae3ef99b
  MachineType: ASUSTeK Computer INC. 901
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=e8a6eae1-a061-4c74-bd53-a8aed65c035d ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-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-28-generic N/A
   linux-backports-modules-4.10.0-28-generic  N/A
   linux-firmware 1.157.14
  Tags:  xenial
  Uname: Linux 4.10.0-28-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/11/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 901
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTek Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2103:bd06/11/2009:svnASUSTeKComputerINC.:pn901:pvrx.x:rvnASUSTeKComputerINC.:rn901:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
  dmi.product.name: 901
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.

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

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


[Kernel-packages] [Bug 1745734] Re: kernel 4.13.0-32.35 mangles display

2018-01-28 Thread Serpico
** 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/1745734

Title:
  kernel 4.13.0-32.35 mangles display

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Today I applied the latest series of updates to 16.04.  After rebooting about 
80% of the graphics display is corrupted, leaving a strip down the right side 
which is still legible.  This was evident on the desktop and also the virtual 
consoles.  Everything seemed to be running normally apart from the display.
  After some experimentation I confirmed it was the 4.13.0-32.35 kernel, I 
reverted to 4.10.0.28-generic and all was good.
  EEE-PC 901 (Intel Atom N270 with Mobile 945GSE integrated graphics)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.23
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  Date: Sat Jan 27 23:22:12 2018
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  a-user 1416 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=c9603762-f6c9-49b1-9ec2-dd0fae3ef99b
  MachineType: ASUSTeK Computer INC. 901
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=e8a6eae1-a061-4c74-bd53-a8aed65c035d ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-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-28-generic N/A
   linux-backports-modules-4.10.0-28-generic  N/A
   linux-firmware 1.157.14
  Tags:  xenial
  Uname: Linux 4.10.0-28-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/11/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 901
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTek Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2103:bd06/11/2009:svnASUSTeKComputerINC.:pn901:pvrx.x:rvnASUSTeKComputerINC.:rn901:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
  dmi.product.name: 901
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.

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

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


[Kernel-packages] [Bug 1724997] Re: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [ibus-x11:1165]

2018-01-28 Thread Elven Decker
*** This bug is a duplicate of bug 1724994 ***
https://bugs.launchpad.net/bugs/1724994

Seeing the same lockup on an old Gateway just after I log in through
"Ubuntu through Wayland".  If I log in through "Ubuntu with X11" things
work fine.  One note from the logs file is that the Wayland login path
tries to start up vino vnc but fails.  Not sure why this is even trying
to start up as it is an X11 application.

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

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [ibus-x11:1165]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  From the first boot after the fresh installation.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 803 F pulseaudio
erick  1164 F pulseaudio
  Date: Thu Oct 19 14:18:10 2017
  Failure: oops
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Hewlett-Packard Compaq Presario F700 Notebook PC
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=cf4a41e4-6a32-4a38-9fd2-9f4a87328676 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [ibus-x11:1165]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.08
  dmi.board.name: 30EA
  dmi.board.vendor: Quanta
  dmi.board.version: 86.09
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.08:bd04/25/2008:svnHewlett-Packard:pnCompaqPresarioF700NotebookPC:pvrRev1:rvnQuanta:rn30EA:rvr86.09:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Compaq Presario F700 Notebook PC
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1743279] Re: QCA6174 stops working on newer kernels after second group rekeying

2018-01-28 Thread oLoBoLGeR
Hi, I do confrirm that linux-firmware 1.157.16 indeed fixes this
problem, and it doesn't introduce any regression to previous version. My
laptop is a Dell XPS, which includes a Qualcomm Atheros QCA6174 Wireless
Network Adapter.

I am on kernel 4.13.0-32 and by using firmware ver
WLAN.RM.4.4.1-00051-QCARMSWP-1 api 6, I can check that the connection
lasts and it can performs smoothly for some hours now (when it was
dropping silently after 10/15 minutes before).

Thank you very much to everyone involved in solving this annoying bug.

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

Title:
  QCA6174 stops working on newer kernels after second group rekeying

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-firmware source package in Artful:
  Fix Committed

Bug description:
  After upgrading to the 4.13 kernel on Ubuntu 16.04.3, I've noticed my
  WiFi would stop working after every 20 minutes or so. The problem
  initially seems related to some DNS services crashing because of what
  happend in browsers and other software that usually rely on DNS but
  I've noticed I couldn't ping my router and other local devices for
  which I knew the IP addresses. The connection is still presented as
  being connected, but it just doesn't work.

  After googling a lot, I came across this question on askubuntu.com

  https://askubuntu.com/questions/967355/wifi-unstable-
  after-17-10-update

  Which led me to this bug report on Debian's bug tracker:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879184

  Which led me to this bug in upstream:

  http://lists.infradead.org/pipermail/ath10k/2017-September/010088.html

  I've tested the proposed fixes myself and I can confirm they work.

  What causes the WiFi to stop working is a bug related to the group
  rekeying routines.

  It seems it only happens in >4.12 kernels, hence why I've only had
  problems after 4.13 was pushed as the current rolling HWE kernel for
  16.04.3.

  kvalo made the fix available in version WLAN.RM.4.4.1-00051-QCARMSWP-1
  of the firmware-6.bin file, which is the current one present in
  upstream.

  Updating the firmware-6.bin (and board-2.bin, optionally) to any
  version equal or later than that fixes the issue completely.

  -

  SRU Justification:
  [Impact]
  Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter, available in 
numerous laptops, including ones that ship with Ubuntu 16.04 pre-installed, 
silently stops working after the second group rekeying, which is usually few 
minutes after the user has connected to a WiFi network. The connection status 
remains unchanged but there's no connectivity at all. This effectively 
disconnects the user without notifying it of what's occurred.

  Additionally, this happens for the only HWE kernel that's been patched
  against the recent Meltdown vulnerability, leaving the user without
  the option of using a recent kernel and a secure kernel at the same
  time.

  [Test Case]
  After applying the required firmwares, check if the connectivity is 
unaffected after the second group rekeying, which can be checked with

  $ cat /var/log/syslog | grep wpa_.*rekeying

  [How to fix it]

  Update the firmware-6.bin file to version
  WLAN.RM.4.4.1-00051-QCARMSWP-1 or later.

  [Regression Potential]
  The new firmware overwrites the old one, but since it's been in upstream 
since October 2017, it should be good.

  -

  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  linux-firmware:
    Instalado: 1.157.14
    Candidato: 1.157.14
    Tabela de versão:
   *** 1.157.14 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/main i386 
Packages
  100 /var/lib/dpkg/status
   1.157 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages

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

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


[Kernel-packages] [Bug 1729389] Re: [Intel 8260/8265] Bluetooth peripherals work for a few seconds, then don't react

2018-01-28 Thread Justin Ferguson
I can confirm that I am still running into this problem with kernel
4.13.0-32-generic and linux-firmware 1.169.2.

Running `rfkill block bluetooth; rfkill unblock bluetooth` gets my mouse
working again until I put the laptop to sleep, at which point it works
for some period of time after wake but then stops again.  (Usually 30
seconds to a minute.)  The sort of weird part is that I don't actually
see any relevant messages in dmesg at the time when it stops working.

Is there further information I can provide to help troubleshoot?

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

Title:
  [Intel 8260/8265] Bluetooth peripherals work for a few seconds, then
  don't react

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Confirmed
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Confirmed
Status in linux-firmware source package in Artful:
  Fix Released

Bug description:
  SRU Justification

  Impact: Bluetooth peripherals work initially but stop working shortly
  with Linux 4.13.

  Fix: Updated firmware from Intel containing a fix for the issue.

  Regression Potential: Any firmware updates may bring regressions,
  however this is a bug fix update and therefore regression potential is
  expected to be minimal.

  ---

  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  ---
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp.
   Bus 001 Device 005: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 13d3:5664 IMC Networks
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
    UP RUNNING PSCAN ISCAN INQUIRY
    RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
    TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

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

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


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

2018-01-28 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 1745841

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

Title:
  touchpad not detecting

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using Lenovo yoga 720.touchpad is not detecting when i run cat
  /proc/bus/input/devices

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

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


[Kernel-packages] [Bug 1745841] [NEW] touchpad not detecting

2018-01-28 Thread shivaraman asoda
Public bug reported:

I'm using Lenovo yoga 720.touchpad is not detecting when i run cat
/proc/bus/input/devices

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

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

Title:
  touchpad not detecting

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using Lenovo yoga 720.touchpad is not detecting when i run cat
  /proc/bus/input/devices

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

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


[Kernel-packages] [Bug 1579918] Re: Smart Card Reader BCM 5880 with kernel 4.2

2018-01-28 Thread Christopher M. Penalver
Karl Hill, regarding your comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579918/comments/32
did you update the firmware with your hardware, and confirmed afterwards
it started to work with no modifications?

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

Title:
  Smart Card Reader BCM 5880 with kernel 4.2

Status in linux package in Ubuntu:
  Expired

Bug description:
  Native to Ubuntu 14.04 and 16.04 (kernel 4.2.0) on Dell Precision 7510
  with Broadcom 5880 (internal card reader). Card reads successfully
  from SCRx31 USB reader (external). Card also works on kernel 3.13.0
  (Dell Latitude E6430, 14.04) with same Broadcom 5880 reader.

  snippet from syslog:

  May 1 19:06:41 m-Precision pcscd: eventhandler.c:313:EHStatusHandlerThread() 
Error communicating to: Broadcom Corp 5880 [Contacted SmartCard] 
(0123456789ABCD) 00 00
  May 1 19:06:46 m-Precision kernel: [15276.197331] xhci_hcd :00:14.0: WARN 
Event TRB for slot 1 ep 4 with no TDs queued?
  May 1 19:06:46 m-Precision kernel: [15276.426405] xhci_hcd :00:14.0: WARN 
Event TRB for slot 1 ep 4 with no TDs queued?
  May 1 19:06:46 m-Precision kernel: [15276.442649] xhci_hcd :00:14.0: WARN 
Event TRB for slot 1 ep 4 with no TDs queued?
  May 1 19:06:46 m-Precision kernel: [15276.465888] xhci_hcd :00:14.0: WARN 
Event TRB for slot 1 ep 4 with no TDs queued?
  May 1 19:06:46 m-Precision pcscd: commands.c:1456:CCID_Receive() Can't read 
all data (54 out of 92 expected)
  May 1 19:06:46 m-Precision pcscd: openct/proto-t1.c:214:t1_transceive() 
fatal: transmit/receive failed
  May 1 19:06:46 m-Precision pcscd: ifdwrapper.c:527:IFDTransmit() Card not 
transacted: 612
  May 1 19:06:46 m-Precision pcscd: winscard.c:1612:SCardTransmit() Card not 
transacted: 0x80100016
  May 1 19:06:46 m-Precision pcscd: openct/proto-t1.c:170:t1_transceive() T=1 
state machine is DEAD. Reset the card first.
  May 1 19:06:46 m-Precision pcscd: ifdwrapper.c:527:IFDTransmit() Card not 
transacted: 612
  May 1 19:06:46 m-Precision pcscd: winscard.c:1612:SCardTransmit() Card not 
transacted: 0x80100016
  May 1 19:06:46 m-Precision pcscd: openct/proto-t1.c:170:t1_transceive() T=1 
state machine is DEAD. Reset the card first.
  May 1 19:06:46 m-Precision pcscd: ifdwrapper.c:527:IFDTransmit() Card not 
transacted: 612
  May 1 19:06:46 m-Precision pcscd: winscard.c:1612:SCardTransmit() Card not 
transacted: 0x80100016
  May 1 19:06:46 m-Precision pcscd: openct/proto-t1.c:170:t1_transceive() T=1 
state machine is DEAD. Reset the card first.
  May 1 19:06:46 m-Precision pcscd: ifdwrapper.c:527:IFDTransmit() Card not 
transacted: 612
  May 1 19:06:46 m-Precision pcscd: winscard.c:1612:SCardTransmit() Card not 
transacted: 0x80100016
  May 1 19:06:46 m-Precision pcscd: openct/proto-t1.c:170:t1_transceive() T=1 
state machine is DEAD. Reset the card first.
  May 1 19:06:46 m-Precision pcscd: ifdwrapper.c:527:IFDTransmit() Card not 
transacted: 612
  May 1 19:06:46 m-Precision pcscd: winscard.c:1612:SCardTransmit() Card not 
transacted: 0x80100016
  May 1 19:06:47 m-Precision pcscd: ccid_usb.c:790:ReadUSB() read failed (1/2): 
-8 Resource temporarily unavailable
  May 1 19:06:47 m-Precision pcscd: ifdwrapper.c:348:IFDStatusICC() Card not 
transacted: 612
  May 1 19:06:47 m-Precision pcscd: eventhandler.c:313:EHStatusHandlerThread() 
Error communicating to: Broadcom Corp 5880 [Contacted SmartCard] 
(0123456789ABCD) 00 00
  May 1 19:06:52 m-Precision kernel: [15281.960976] xhci_hcd :00:14.0: WARN 
Event TRB for slot 1 ep 4 with no TDs queued?

  The above cycles on syslog roughly every second until card is removed.

  pcsc_scan shows card as alternating between successfully read to card
  reader not available, also on the roughly 1 sec interval.

  ---
  ApportVersion: 2.14.1-0ubuntu3.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  grumpy 2207 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-21 (0 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1bcf:28b8 Sunplus Innovation Technology Inc.
   Bus 001 Device 002: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications 
Processor
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 7510
  Package: linux (not installed)
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-36-generic.efi.signed 
root=UUID=62ed5a52-92de-456c-8a4b-433666572702 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-36.42~14.04.1-generic 4.2.8-ckt8
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-36-generic N/A
   

[Kernel-packages] [Bug 1448836] Re: Bluetooth doesn't find any device

2018-01-28 Thread Christopher M. Penalver
** Description changed:

  I am using an Acer E 15. I am not sure how to find out the
  specifications of my bluetooth device. I found nothing with lsusb or
  lspci. The only thing i found was that:
  
  dmesg | grep bluetooth
  [   12.314809] bluetooth hci0: Direct firmware load for 
brcm/BCM43142A0-04ca-2009.hcd failed with error -2
  
  Until Ubuntu 14.10 the bluetooth device was not recognized at all. Since
  the update to Ubuntu 15.04 i can activate it through Gnome system
  settings and make it visible. But it will not be found by any device and
  will not find any itself.
  
- Yours sincerly
- Jonius
+ WORKAROUND: Download:
+ 
https://github.com/winterheart/broadcom-bt-firmware/blob/master/brcm/BCM43142A0-04ca-2009.hcd
+ 
+ and copy it to:
+ /lib/firmware/brcm/BCM.hcd
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-15-generic 3.19.0-15.15
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   jonatan2465 F...m pulseaudio
   /dev/snd/controlC1:  jonatan2465 F pulseaudio
   /dev/snd/controlC0:  jonatan2465 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Apr 26 23:56:01 2015
  HibernationDevice: RESUME=UUID=83a341ec-8e0a-48f3-b194-a58b60546f21
  InstallationDate: Installed on 2015-01-07 (109 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Acer Aspire E5-571G
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-04-23 (3 days ago)
  dmi.bios.date: 09/25/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.16
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA50_HB
  dmi.board.vendor: Acer
  dmi.board.version: V1.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.16:bd09/25/2014:svnAcer:pnAspireE5-571G:pvrV1.16:rvnAcer:rnEA50_HB:rvrV1.16:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-571G
  dmi.product.version: V1.16
  dmi.sys.vendor: Acer

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

Title:
  Bluetooth doesn't find any device

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using an Acer E 15. I am not sure how to find out the
  specifications of my bluetooth device. I found nothing with lsusb or
  lspci. The only thing i found was that:

  dmesg | grep bluetooth
  [   12.314809] bluetooth hci0: Direct firmware load for 
brcm/BCM43142A0-04ca-2009.hcd failed with error -2

  Until Ubuntu 14.10 the bluetooth device was not recognized at all.
  Since the update to Ubuntu 15.04 i can activate it through Gnome
  system settings and make it visible. But it will not be found by any
  device and will not find any itself.

  WORKAROUND: Download:
  
https://github.com/winterheart/broadcom-bt-firmware/blob/master/brcm/BCM43142A0-04ca-2009.hcd

  and copy it to:
  /lib/firmware/brcm/BCM.hcd

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-15-generic 3.19.0-15.15
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   jonatan2465 F...m pulseaudio
   /dev/snd/controlC1:  jonatan2465 F pulseaudio
   /dev/snd/controlC0:  jonatan2465 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Apr 26 23:56:01 2015
  HibernationDevice: RESUME=UUID=83a341ec-8e0a-48f3-b194-a58b60546f21
  InstallationDate: Installed on 2015-01-07 (109 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Acer Aspire E5-571G
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-04-23 (3 days ago)
  dmi.bios.date: 09/25/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.16
  dmi.board.asset.tag: Type2 - 

[Kernel-packages] [Bug 1742675] Re: after upgrade to linux-image-extra-4.13.0-26-generic the system does not start at all

2018-01-28 Thread Leszek
I can confirm that kernel 4.14.0-17 runs also on my hardware (in fact
even without any additional boot options).

As I understand it's mainly because this kernel haven't received any
Spectre+Meltdown patches. So time will show how it will be with these
patches. But for now it's best option to have current kernel easy and
automatic way from PPA.

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

Title:
  after upgrade to linux-image-extra-4.13.0-26-generic  the system does
  not start at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrade to linux-image-extra-4.13.0-26-generic  the system does not 
start at all.
  Only restart through Advanced Options with 
linux-image-extra-4.10.0-42-generic helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.23
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Thu Jan 11 15:20:26 2018
  InstallationDate: Installed on 2017-06-23 (201 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-manager.release-upgrades: 
2017-06-24T18:05:02.372991

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

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


[Kernel-packages] [Bug 1637709] Re: Lenovo Ideapad 100 webcam always on

2018-01-28 Thread Fifis
Dear all,

My friend also has a Lenovo Ideapad 100 15IBD. I have just installed
Ubuntu with 4.13.0-32 kernel and added a line

blacklist uvcvideo

to /etc/modprobe.d/blacklist.conf, as you advised, and rebooted, but it
did not help. The white eye of the camera is still on. Is there a more
reliable way to disable it? It is so bloody disturbing!

What information can I provide further to help this issue 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/1637709

Title:
  Lenovo Ideapad 100 webcam always on

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a lenovo Ideapad 100 model 15IBD 80 QQ
  The webcam led it stays always on from when i start the pc, it stops only, it 
seems, when i open some software that has a working with it in some way...like  
software or even google chrome (i think thanks to hangouts)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ale1361 F pulseaudio
   /dev/snd/controlC1:  ale1361 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=39a50866-e309-4acc-b70f-19f745ab0c9e
  InstallationDate: Installed on 2016-10-22 (6 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 80QQ
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=it
   TERM=xterm
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=86cd71e4-1562-488f-afa6-290f354d4f7a ro
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  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.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.157.4
  Tags:  xenial
  Uname: Linux 4.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/12/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E0CN61WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Nano 5B6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 100-15IBD
  dmi.modalias: 
dmi:bvnLENOVO:bvrE0CN61WW:bd08/12/2016:svnLENOVO:pn80QQ:pvrLenovoideapad100-15IBD:rvnLENOVO:rnNano5B6:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad100-15IBD:
  dmi.product.name: 80QQ
  dmi.product.version: Lenovo ideapad 100-15IBD
  dmi.sys.vendor: LENOVO

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

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