[Kernel-packages] [Bug 2054921] [NEW] Raspberry Pi5 fan custom curve not working.

2024-02-25 Thread Davide
Public bug reported:

Fan speed control does not work on Ubuntu 23.10 due to they are using an
old bcm2712-rpi-5-b.dtb file.

That updated file is present in the raspberry repo
https://github.com/raspberrypi/firmware/blob/master/boot/bcm2712-rpi-5-b.dtb

Will Ubuntu guys ever update that file? Is there a way to submit a bug
report to try to mitigate this problem as soon as possible?

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-1011-raspi 6.5.0-1011.14
ProcVersionSignature: Ubuntu 6.5.0-1011.14-raspi 6.5.8
Uname: Linux 6.5.0-1011-raspi aarch64
ApportVersion: 2.27.0-0ubuntu5
Architecture: arm64
CasperMD5CheckResult: unknown
CloudArchitecture: aarch64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: config-disk (/dev/sda1)
Date: Sun Feb 25 12:40:51 2024
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm
SourcePackage: linux-raspi
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug arm64 mantic

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

Title:
  Raspberry Pi5 fan custom curve not working.

Status in linux-raspi package in Ubuntu:
  New

Bug description:
  Fan speed control does not work on Ubuntu 23.10 due to they are using
  an old bcm2712-rpi-5-b.dtb file.

  That updated file is present in the raspberry repo
  https://github.com/raspberrypi/firmware/blob/master/boot/bcm2712-rpi-5-b.dtb

  Will Ubuntu guys ever update that file? Is there a way to submit a bug
  report to try to mitigate this problem as soon as possible?

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-1011-raspi 6.5.0-1011.14
  ProcVersionSignature: Ubuntu 6.5.0-1011.14-raspi 6.5.8
  Uname: Linux 6.5.0-1011-raspi aarch64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CloudArchitecture: aarch64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: config-disk (/dev/sda1)
  Date: Sun Feb 25 12:40:51 2024
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
  SourcePackage: linux-raspi
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Kernel-packages] [Bug 2048935] Re: Right speaker broken on Dell XPS 13 Plus 9320

2024-01-28 Thread Davide Scarso
Fresh install of Ubuntu 22.04.3 LTS with kernel 6.5.0-15-generic on Dell
XPS 13 Plus 9320, the right speaker does not work. More precisely, as a
user stated in the Dell forum "right channel audio is played by left
speaker (lower one), and left audio comes from [the] other left
speaker". Headphones and external speakers work fine. No apparent
discrepancies of volume balance in Alsamixer.

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

Title:
  Right speaker broken on Dell XPS 13 Plus 9320

Status in linux-meta-hwe-6.5 package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from the previous HWE kernel 6.2.0-39-generic to the
  new HWE kernel 6.5.0-14-generic, the right speaker no longer works.
  When booting back into the old HWE kernel, the right speaker functions
  again. The left speaker works in both cases.

  Hardware info:
  Dell XPS 13 Plus 9320 with Intel i7 1260P

  Software info:
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  Package info:
  apt-cache policy linux-generic-hwe-22.04
  linux-generic-hwe-22.04:
Installed: 6.5.0.14.14~22.04.7
Candidate: 6.5.0.14.14~22.04.7
Version table:
   *** 6.5.0.14.14~22.04.7 500
  500 http://nl.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://nl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  
  lspci output on kernel 6.5.0-14-generic:
  ```
  00:1f.3 Multimedia audio controller: Intel Corporation Alder Lake PCH-P High 
Definition Audio Controller (rev 01)
Subsystem: Dell Device 0af3
Flags: bus master, fast devsel, latency 64, IRQ 201, IOMMU group 15
Memory at 603e1d (64-bit, non-prefetchable) [size=16K]
Memory at 603e00 (64-bit, non-prefetchable) [size=1M]
Capabilities: [50] Power Management version 3
Capabilities: [80] Vendor Specific Information: Len=14 
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Kernel driver in use: sof-audio-pci-intel-tgl
Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl

  00:1f.4 SMBus: Intel Corporation Alder Lake PCH-P SMBus Host Controller (rev 
01)
Subsystem: Dell Device 0af3
Flags: medium devsel, IRQ 16, IOMMU group 15
Memory at 603e1dc000 (64-bit, non-prefetchable) [size=256]
I/O ports at efa0 [size=32]
  ```

  aplay -l output on kernel 6.5.0-14-generic:
  ```
   List of PLAYBACK Hardware Devices 
  card 0: sofsoundwire [sof-soundwire], device 2: Speaker (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: sofsoundwire [sof-soundwire], device 5: HDMI 1 (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: sofsoundwire [sof-soundwire], device 6: HDMI 2 (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: sofsoundwire [sof-soundwire], device 7: HDMI 3 (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-generic-hwe-22.04 6.5.0.14.14~22.04.7
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 10 21:40:02 2024
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  InstallationDate: Installed on 2022-06-25 (563 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  SourcePackage: linux-meta-hwe-6.5
  UpgradeStatus: Upgraded to jammy on 2022-08-15 (513 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048935/+subscriptions


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


[Kernel-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).

2020-11-18 Thread Davide Pessina
Yes, that’s the point

I’m try to use JBL T450BT

These are the available specs on official site

Control and Connection Specifications
Bluetooth profilesHFP v1.5, HSP v1.2, A2DP v1.2, AVRCP v1.4
Bluetooth frequency2.402GHz-2.48GHz
Bluetooth transmitted modulationGFSK,π/4DQPSK, 8DPSK
Bluetooth transmitter power0-4 d

I don’t find mSBC information, so it’s supposed they don’t support mSBC

What about Sony WH-CH700? They seems to support mSBC, but who knows.. :(

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support (Bluetooth A2DP codecs).

Status in PulseAudio:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  In Progress
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).

2020-11-18 Thread Davide Pessina
@65 - thank for explanation

Could someone post a list of headsets with mSBC support?
 
Price below 100€ if possible

Specification are hard to find, and headset market is crowded...

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support (Bluetooth A2DP codecs).

Status in PulseAudio:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  In Progress
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).

2020-11-17 Thread Davide Pessina
Recently i bought both: 1Mii B10 and Avantree Leaf

Quick review of them on my Ubuntu 16.04 64bit

- plug and play -> both OK, no issues
- audio quality with mic enabled -> bad bad bad, no significantly different 
than using pc bluetooth

Therefore... there is no solution, apart from wired headset

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support (Bluetooth A2DP codecs).

Status in PulseAudio:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  In Progress
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1849713] Re: Warning message in logs after kernel update to linux-image-4.15.0-66-generic

2020-09-15 Thread Davide Aguiari
I have the same error at every boot.

LSB Version:
core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
Distributor ID: elementary
Description:elementary OS 5.1.7 Hera
Release:5.1.7
Codename:   hera

4.15.0-117-generic

[1.427943] [ cut here ]
[1.427944] Could not determine valid watermarks for inherited state
[1.427985] WARNING: CPU: 5 PID: 210 at 
/build/linux-do9eLF/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537 
intel_modeset_init+0xfcf/0x1010 [i915]
[1.427986] Modules linked in: i915(+) rtsx_pci_sdmmc i2c_algo_bit 
drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm psmouse ahci 
libahci rtsx_pci video
[1.427991] CPU: 5 PID: 210 Comm: systemd-udevd Not tainted 
4.15.0-117-generic #118-Ubuntu
[1.427991] Hardware name: Hewlett-Packard HP OMEN Notebook PC 15/2332, BIOS 
F.48 11/14/2019
[1.428016] RIP: 0010:intel_modeset_init+0xfcf/0x1010 [i915]
[1.428017] RSP: 0018:ab8581fa39b0 EFLAGS: 00010286
[1.428018] RAX:  RBX: 8c0bc0b88000 RCX: bd263aa8
[1.428018] RDX: 0001 RSI: 0096 RDI: 0247
[1.428019] RBP: ab8581fa3a40 R08: 0290 R09: 0004
[1.428019] R10: 0040 R11: 0001 R12: 8c0bc1437800
[1.428020] R13: 8c0bcc58cc00 R14: ffea R15: 8c0bc0b88358
[1.428021] FS:  7fb39ba8b680() GS:8c0bdf34() 
knlGS:
[1.428021] CS:  0010 DS:  ES:  CR0: 80050033
[1.428022] CR2: 7fb39ba76ebd CR3: 0004408d0006 CR4: 001606e0
[1.428023] Call Trace:
[1.428053]  i915_driver_load+0xa73/0xe60 [i915]
[1.428071]  i915_pci_probe+0x42/0x70 [i915]
[1.428073]  local_pci_probe+0x47/0xa0
[1.428084]  pci_device_probe+0x10e/0x1c0
[1.428087]  driver_probe_device+0x30c/0x4a0
[1.428088]  __driver_attach+0xcc/0xf0
[1.428090]  ? driver_probe_device+0x4a0/0x4a0
[1.428092]  bus_for_each_dev+0x70/0xc0
[1.428093]  driver_attach+0x1e/0x20
[1.428095]  bus_add_driver+0x1c7/0x270
[1.428095]  ? 0xc04bb000
[1.428097]  driver_register+0x60/0xe0
[1.428097]  ? 0xc04bb000
[1.428098]  __pci_register_driver+0x5a/0x60
[1.428120]  i915_init+0x5c/0x5f [i915]
[1.428122]  do_one_initcall+0x52/0x19f
[1.428124]  ? __vunmap+0xb5/0xe0
[1.428126]  ? _cond_resched+0x19/0x40
[1.428127]  ? kmem_cache_alloc_trace+0x167/0x1d0
[1.428130]  ? do_init_module+0x27/0x213
[1.428131]  do_init_module+0x5f/0x213
[1.428133]  load_module+0x16bd/0x1f20
[1.428135]  ? ima_post_read_file+0x96/0xa0
[1.428137]  SYSC_finit_module+0xfc/0x120
[1.428138]  ? SYSC_finit_module+0xfc/0x120
[1.428140]  SyS_finit_module+0xe/0x10
[1.428141]  do_syscall_64+0x73/0x130
[1.428142]  entry_SYSCALL_64_after_hwframe+0x41/0xa6
[1.428143] RIP: 0033:0x7fb39b595959
[1.428144] RSP: 002b:7ffd062d28d8 EFLAGS: 0246 ORIG_RAX: 
0139
[1.428144] RAX: ffda RBX: 55a1e3ca5300 RCX: 7fb39b595959
[1.428145] RDX:  RSI: 7fb39b274105 RDI: 0012
[1.428145] RBP: 7fb39b274105 R08:  R09: 7ffd062d29f0
[1.428146] R10: 0012 R11: 0246 R12: 
[1.428146] R13: 55a1e3ca9340 R14: 0002 R15: 55a1e3ca5300
[1.428147] Code: e9 46 fc ff ff 48 c7 c6 f7 9d 44 c0 48 c7 c7 4f 91 44 c0 
e8 64 27 ad fb 0f 0b e9 73 fe ff ff 48 c7 c7 40 f6 45 c0 e8 51 27 ad fb <0f> 0b 
e9 4b fe ff ff 48 c7 c6 04 9e 44 c0 48 c7 c7 4f 91 44 c0 
[1.428156] ---[ end trace fbf359e6d3d7d879 ]---

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

Title:
  Warning message in logs after kernel update to linux-
  image-4.15.0-66-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi:

  After updating to latest kernel on ubuntu 18.04 I start getting the
  message below. I tried to reboot the machine but the message is
  consistent.

  [1.485680] [ cut here ]
  [1.485681] Could not determine valid watermarks for inherited state
  [1.485736] WARNING: CPU: 0 PID: 199 at 
/build/linux-WKYm23/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537 
intel_modeset_init+0xfcf/0x1010 [i915]
  [1.485737] Modules linked in: aesni_intel(+) fjes(-) nouveau(+) 
aes_x86_64 i915(+) crypto_simd glue_helper cryptd mxm_wmi ttm i2c_algo_bit 
psmouse drm_kms_helper ahci syscopyarea sysfillrect sysimgblt libahci r8169 
fb_sys_fops mii drm rtsx_pci wmi video
  [1.485748] CPU: 0 PID: 199 Comm: systemd-udevd Not tainted 
4.15.0-66-generic #75-Ubuntu
  [1.485749] Hardware name: ASUSTeK COMPUTER INC. G551JW/G551JW, BIOS 
G551JW.209 03/04/2016
  

[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-07-24 Thread Davide
Ubuntu 20.04
for me the problem started after upgrading to the kernel version 
5.4.0-42-generic,
I noticed it because the boot up failed once.

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

Title:
  initramfs unpacking failed

Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  "initramfs unpacking failed: Decoding failed",  message appears on
  boot up.

  If I "update-initramfs" using gzip instead of lz, then boot up passes
  without decoding failed message.

  ---

  However, we currently believe that the decoding error reported in
  dmesg is actually harmless and has no impact on usability on the
  system.

  Switching from lz4 to gzip compression, simply papers over the
  warning, without any benefits, and slows down boot.

  Kernel should be fixed to correctly parse lz4 compressed initrds, or
  at least lower the warning, to not be user visible as an error.

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

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


[Kernel-packages] [Bug 386799] Re: Restart required for webcam to work; how to manually restart?

2020-06-02 Thread Davide
After years and years of bug flagging from other users, 
Same Problem on 18.04.4 LTS, bionic.
Laptop: TECLAST F7.

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

Title:
  Restart required for webcam to work; how to manually restart?

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  http://ubuntuforums.org/showthread.php?p=7451356#post7451356  shows another 
user with the same problem.
  I have a lapto HP pavillion
  Linux patricio-laptop 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 
UTC 2009 i686 GNU/Linux

  From the kern.log:
  /var/log/kern.log:Jun 13 15:20:31 patricio-laptop kernel: [29606.529587] 
uvcvideo 2-4:1.1: resume error -5
  /var/log/kern.log:Jun 13 15:26:01 patricio-laptop kernel: [29937.049414] 
uvcvideo: Failed to query (135) UVC control 2 (unit 3) : -71 (exp. 2).
  /var/log/kern.log:Jun 13 15:32:04 patricio-laptop kernel: [30300.054961] 
uvcvideo: Failed to query (135) UVC control 2 (unit 3) : -71 (exp. 2).

  lsusb
  Bus 002 Device 002: ID 04f2:b015 Chicony Electronics Co., Ltd VGA 24fps UVC 
Webcam

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

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


[Kernel-packages] [Bug 1880406] [NEW] Touchpad on LEnovo IDEAPAD s145

2020-05-24 Thread Davide Angeloni
Public bug reported:

Can't install touchpad on LEnovo IDEAPAD s145

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-33-generic 5.4.0-33.37
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  snabbull   1754 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun May 24 16:03:26 2020
InstallationDate: Installed on 2020-04-29 (25 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 81W8
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=68fce319-d6fd-42b4-8792-609a709633ce ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-33-generic N/A
 linux-backports-modules-5.4.0-33-generic  N/A
 linux-firmware1.187
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/04/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: DKCN26WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
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 IdeaPad S145-15IIL
dmi.modalias: 
dmi:bvnLENOVO:bvrDKCN26WW:bd03/04/2020:svnLENOVO:pn81W8:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL:
dmi.product.family: IdeaPad S145-15IIL
dmi.product.name: 81W8
dmi.product.sku: LENOVO_MT_81W8_BU_idea_FM_IdeaPad S145-15IIL
dmi.product.version: Lenovo IdeaPad S145-15IIL
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug focal package-from-proposed

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

Title:
  Touchpad on LEnovo IDEAPAD s145

Status in linux package in Ubuntu:
  New

Bug description:
  Can't install touchpad on LEnovo IDEAPAD s145

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-33-generic 5.4.0-33.37
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  snabbull   1754 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 24 16:03:26 2020
  InstallationDate: Installed on 2020-04-29 (25 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81W8
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=68fce319-d6fd-42b4-8792-609a709633ce ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-33-generic N/A
   linux-backports-modules-5.4.0-33-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DKCN26WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  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 IdeaPad S145-15IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrDKCN26WW:bd03/04/2020:svnLENOVO:pn81W8:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL:
  dmi.product.family: IdeaPad S145-15IIL
  dmi.product.name: 81W8
  dmi.product.sku: LENOVO_MT_81W8_BU_idea_FM_IdeaPad S145-15IIL
  dmi.product.version: Lenovo IdeaPad S145-15IIL
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04

2019-12-06 Thread Davide Sangalli
Yeap it helps and it is quite clear.
Still another remark. Sorry for going on with the digression here.
If there is a more proper channel we can move there.

In my old laptop when I load it with a single thread application I get

  TURBO ENABLED on 2 Cores, Hyper Threading ON
  Max Frequency without considering Turbo 1894.72 MHz (99.72 x [19])
  Max TURBO Multiplier (if Enabled) with 1/2/3/4 Cores is  27x/25x/25x/25x
  Real Current Frequency 2663.14 MHz [99.72 x 26.71] (Max of below)
  Core [core-id]  :Actual Freq (Mult.)  C0%   Halt(C1)%  C3 %   C6 %   
C7 %  Temp  VCore
  Core 1 [0]:   2663.14 (26.71x)  99.3   0   0   0  
 058  0.9207
  Core 2 [2]:   2492.89 (25.00x)   4.85.78   1   1
85.655  0.9207


Now the remarkable difference is that the second core spends 86% of the time in 
C7 state.
On the other hand in the new laptop all cores stay in C1 state most of the time.
Same happens without load (see previous post for data on new laptop).

  TURBO ENABLED on 2 Cores, Hyper Threading ON
  Max Frequency without considering Turbo 1894.72 MHz (99.72 x [19])
  Max TURBO Multiplier (if Enabled) with 1/2/3/4 Cores is  27x/25x/25x/25x
  Real Current Frequency .72 MHz [99.72 x 11.15] (Max of below)
  Core [core-id]  :Actual Freq (Mult.)  C0%   Halt(C1)%  C3 %   C6 %   
C7 %  Temp  VCore
  Core 1 [0]:   1019.47 (10.22x)  11.99.92   1   0
82.346  0.7955
  Core 2 [2]:   .72 (11.15x)1216.1   1   0
75.550  0.7955


In both cases the driver is the intel_pstate and n boh case I'm monitoring with 
i7z, sudo and 1 sec freq
Old processor is Intel Core i5-3337U
New processor is Intel Core i7-8750H

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

Title:
  Ubuntu 18.04 is overheating after upgrade from 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu is overheating at my laptop. Opening youtube on firefox is
  enough for critical temperature shutdown.

  Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C 
with only firefox or chrome open and doing nothing. 
  On my old 16.04 with same using, the temp varies between 55 and 70°C.

  First thought was the driver nouveau is the problem, and finally I was
  able to install by add "nouveau.modeset=0" at livecd boot options,
  without temp shutdown.

  After install I disable the nouveau at modprobe blacklist, but the
  system continues overheating and shutdown with basic usage.

  
  I have no idea what's happening with the bionic at my laptop.

  My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 16:22:40 2018
  InstallationDate: Installed on 2018-04-27 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptHistorylog:
   Start-Date: 2018-04-27  15:46:02
   End-Date: 2018-04-27  15:46:02
  VarLogDistupgradeAptlog:
   Log time: 2018-04-27 15:45:39.753331
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
   Log time: 2018-04-27 15:46:04.859979
  VarLogDistupgradeApttermlog:
   Log started: 2018-04-27  15:46:02
   Log ended: 2018-04-27  15:46:02
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edir   2354 F pulseaudio
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family 
Integrated Graphics Controller [144d:c0a5]
 Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5]
  HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d
  InstallationDate: Installed on 2018-04-27 (36 days ago)
  InstallationMedia: 

[Kernel-packages] [Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04

2019-12-01 Thread Davide Sangalli
I guess you mean "there is only one PPL in the CPU, all cores get the
resulting clock". This would mean the readout of i7z in the idle case,
where each core has a different multiplier and a different clock, is
fake.

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

Title:
  Ubuntu 18.04 is overheating after upgrade from 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu is overheating at my laptop. Opening youtube on firefox is
  enough for critical temperature shutdown.

  Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C 
with only firefox or chrome open and doing nothing. 
  On my old 16.04 with same using, the temp varies between 55 and 70°C.

  First thought was the driver nouveau is the problem, and finally I was
  able to install by add "nouveau.modeset=0" at livecd boot options,
  without temp shutdown.

  After install I disable the nouveau at modprobe blacklist, but the
  system continues overheating and shutdown with basic usage.

  
  I have no idea what's happening with the bionic at my laptop.

  My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 16:22:40 2018
  InstallationDate: Installed on 2018-04-27 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptHistorylog:
   Start-Date: 2018-04-27  15:46:02
   End-Date: 2018-04-27  15:46:02
  VarLogDistupgradeAptlog:
   Log time: 2018-04-27 15:45:39.753331
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
   Log time: 2018-04-27 15:46:04.859979
  VarLogDistupgradeApttermlog:
   Log started: 2018-04-27  15:46:02
   Log ended: 2018-04-27  15:46:02
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edir   2354 F pulseaudio
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family 
Integrated Graphics Controller [144d:c0a5]
 Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5]
  HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d
  InstallationDate: Installed on 2018-04-27 (36 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-nouveau 1:1.0.15-2
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.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.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 10HX.M034.20110426.SSH
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: RF511/RF411/RF711
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: 10HX
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 

[Kernel-packages] [Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04

2019-11-30 Thread Davide Sangalli
@Doug Smythies: thanks for the reply.
I'm sampling every second.

Anyway, just to better understand.
When my system is idle all cores spend in C0 less than 10% of the time and the 
frequency of each core reported by i7z is different and below 2.2GHz. When I 
run a single core (and single thread) task, there is just core "0" which is 
100% of the time in C0 state (as it should) but I would have expected only such 
core to reach ~2.9GHz and the other to remain in below. Instead all cores goes 
to ~2.9GHz.
https://www.youtube.com/watch?v=HBKfkiOgIv4 (sorry for the oversimplified 
reference)

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

Title:
  Ubuntu 18.04 is overheating after upgrade from 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu is overheating at my laptop. Opening youtube on firefox is
  enough for critical temperature shutdown.

  Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C 
with only firefox or chrome open and doing nothing. 
  On my old 16.04 with same using, the temp varies between 55 and 70°C.

  First thought was the driver nouveau is the problem, and finally I was
  able to install by add "nouveau.modeset=0" at livecd boot options,
  without temp shutdown.

  After install I disable the nouveau at modprobe blacklist, but the
  system continues overheating and shutdown with basic usage.

  
  I have no idea what's happening with the bionic at my laptop.

  My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 16:22:40 2018
  InstallationDate: Installed on 2018-04-27 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptHistorylog:
   Start-Date: 2018-04-27  15:46:02
   End-Date: 2018-04-27  15:46:02
  VarLogDistupgradeAptlog:
   Log time: 2018-04-27 15:45:39.753331
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
   Log time: 2018-04-27 15:46:04.859979
  VarLogDistupgradeApttermlog:
   Log started: 2018-04-27  15:46:02
   Log ended: 2018-04-27  15:46:02
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edir   2354 F pulseaudio
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family 
Integrated Graphics Controller [144d:c0a5]
 Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5]
  HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d
  InstallationDate: Installed on 2018-04-27 (36 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-nouveau 1:1.0.15-2
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.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.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 10HX.M034.20110426.SSH
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: RF511/RF411/RF711
  

[Kernel-packages] [Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04

2019-11-30 Thread Davide Sangalli
I also mention that, monitoring with i7z the clock of my CPU, when intel turbo 
is not working I get different freqs for each core
Core [core-id]  :Actual Freq (Mult.)  C0%   Halt(C1)%  C3 %   C6 %  
Temp  VCore
Core 1 [0]:   1126.19 (11.23x)  7.9993.9   1   1
40  0.6274
Core 2 [1]:   1239.87 (12.36x)   3.295.1   12.11
41  0.6208
Core 3 [2]:   1577.66 (15.73x)   3.795.4   1   1
38  0.6257
Core 4 [3]:   1316.89 (13.13x)  7.2381.9   112.8
39  0.6257
Core 5 [4]:   1572.58 (15.68x)  10.2  87   14.73
39  0.6257
Core 6 [5]:   1916.98 (19.11x)  8.0290.6   11.44
39  0.6266

However, as soon as I load 1 core to 100%, all goes at the maximum frequency 
(here I'm limiting the maximum and also the core is under-volted to keep the 
temperature stable.
Core [core-id]  :Actual Freq (Mult.)  C0%   Halt(C1)%  C3 %   C6 %  
Temp  VCore
Core 1 [0]:   2891.95 (28.83x)   100   0   0   0
52  0.8234
Core 2 [1]:   2891.77 (28.83x)  2.4192.2   1 3.6
47  0.8229
Core 3 [2]:   2891.72 (28.83x)  1.7394.4   12.37
44  0.8225
Core 4 [3]:   2891.81 (28.83x) 191.5   16.46
44  0.8230
Core 5 [4]:   2892.39 (28.83x) 196.9   11.37
44  0.8242
Core 6 [5]:   2891.94 (28.83x)2562.9   1 3.3
43  0.8243

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

Title:
  Ubuntu 18.04 is overheating after upgrade from 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu is overheating at my laptop. Opening youtube on firefox is
  enough for critical temperature shutdown.

  Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C 
with only firefox or chrome open and doing nothing. 
  On my old 16.04 with same using, the temp varies between 55 and 70°C.

  First thought was the driver nouveau is the problem, and finally I was
  able to install by add "nouveau.modeset=0" at livecd boot options,
  without temp shutdown.

  After install I disable the nouveau at modprobe blacklist, but the
  system continues overheating and shutdown with basic usage.

  
  I have no idea what's happening with the bionic at my laptop.

  My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 16:22:40 2018
  InstallationDate: Installed on 2018-04-27 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptHistorylog:
   Start-Date: 2018-04-27  15:46:02
   End-Date: 2018-04-27  15:46:02
  VarLogDistupgradeAptlog:
   Log time: 2018-04-27 15:45:39.753331
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
   Log time: 2018-04-27 15:46:04.859979
  VarLogDistupgradeApttermlog:
   Log started: 2018-04-27  15:46:02
   Log ended: 2018-04-27  15:46:02
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edir   2354 F pulseaudio
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family 
Integrated Graphics Controller [144d:c0a5]
 Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5]
  HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d
  InstallationDate: Installed on 2018-04-27 (36 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711
  

[Kernel-packages] [Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04

2019-11-12 Thread Davide Sangalli
An update. After some digging the conclusion I is that the problem  in
my case is not linux but might be the Asus BIOS. Even just enetering the
BIOS the CPU temperature is rising up to 70-80 degrees. I'v e also
upgraded the BIOS, but without significant improvements.

I have the impression the BIOS has problems in dealing with the intel
turbo boost technology of my i7-8th generation. Disabling the turbo from
linux side (I couldn't from the BIOS) the temperatures of my laptop are
now fine.

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

Title:
  Ubuntu 18.04 is overheating after upgrade from 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu is overheating at my laptop. Opening youtube on firefox is
  enough for critical temperature shutdown.

  Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C 
with only firefox or chrome open and doing nothing. 
  On my old 16.04 with same using, the temp varies between 55 and 70°C.

  First thought was the driver nouveau is the problem, and finally I was
  able to install by add "nouveau.modeset=0" at livecd boot options,
  without temp shutdown.

  After install I disable the nouveau at modprobe blacklist, but the
  system continues overheating and shutdown with basic usage.

  
  I have no idea what's happening with the bionic at my laptop.

  My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 16:22:40 2018
  InstallationDate: Installed on 2018-04-27 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptHistorylog:
   Start-Date: 2018-04-27  15:46:02
   End-Date: 2018-04-27  15:46:02
  VarLogDistupgradeAptlog:
   Log time: 2018-04-27 15:45:39.753331
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
   Log time: 2018-04-27 15:46:04.859979
  VarLogDistupgradeApttermlog:
   Log started: 2018-04-27  15:46:02
   Log ended: 2018-04-27  15:46:02
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edir   2354 F pulseaudio
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family 
Integrated Graphics Controller [144d:c0a5]
 Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5]
  HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d
  InstallationDate: Installed on 2018-04-27 (36 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-nouveau 1:1.0.15-2
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.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.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 10HX.M034.20110426.SSH
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: RF511/RF411/RF711
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: 10HX
  dmi.chassis.asset.tag: No 

[Kernel-packages] [Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04

2019-10-10 Thread Davide Sangalli
** Information type changed from Public to Public Security

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

Title:
  Ubuntu 18.04 is overheating after upgrade from 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu is overheating at my laptop. Opening youtube on firefox is
  enough for critical temperature shutdown.

  Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C 
with only firefox or chrome open and doing nothing. 
  On my old 16.04 with same using, the temp varies between 55 and 70°C.

  First thought was the driver nouveau is the problem, and finally I was
  able to install by add "nouveau.modeset=0" at livecd boot options,
  without temp shutdown.

  After install I disable the nouveau at modprobe blacklist, but the
  system continues overheating and shutdown with basic usage.

  
  I have no idea what's happening with the bionic at my laptop.

  My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 16:22:40 2018
  InstallationDate: Installed on 2018-04-27 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptHistorylog:
   Start-Date: 2018-04-27  15:46:02
   End-Date: 2018-04-27  15:46:02
  VarLogDistupgradeAptlog:
   Log time: 2018-04-27 15:45:39.753331
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
   Log time: 2018-04-27 15:46:04.859979
  VarLogDistupgradeApttermlog:
   Log started: 2018-04-27  15:46:02
   Log ended: 2018-04-27  15:46:02
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edir   2354 F pulseaudio
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family 
Integrated Graphics Controller [144d:c0a5]
 Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5]
  HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d
  InstallationDate: Installed on 2018-04-27 (36 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-nouveau 1:1.0.15-2
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.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.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 10HX.M034.20110426.SSH
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: RF511/RF411/RF711
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: 10HX
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr10HX.M034.20110426.SSH:bd04/26/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pnRF511/RF411/RF711:pvr10HX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnRF511/RF411/RF711:rvr10HX:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: RF511/RF411/RF711

[Kernel-packages] [Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04

2019-10-10 Thread Davide Sangalli
Same problem here.
Ubuntu 18.04.3 LTS
I tried kernels 4.15, 5.0 and 5.3 and the problem persists.
With default installation parameters CPU temperatures goes above 95° very 
easily. 

The only way I managed to keep the CPU temp down is:
a) setting
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_pstate=disable"
and then choosing "PowerSave" mode in cpufreq

b) Installed laptop-mode-tools
Edited file: /etc/laptop-mode/laptop-mode.conf
It changed the file /proc/sys/vm/laptop_mode to 2
After that no significant changes in temperature when moving from AC to Battery

Attached hardinfo_report.html run after the doing the procedures above
mentioned

** Attachment added: "Output of hardinfo command"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768976/+attachment/5296370/+files/hardinfo_report.html

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

Title:
  Ubuntu 18.04 is overheating after upgrade from 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu is overheating at my laptop. Opening youtube on firefox is
  enough for critical temperature shutdown.

  Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C 
with only firefox or chrome open and doing nothing. 
  On my old 16.04 with same using, the temp varies between 55 and 70°C.

  First thought was the driver nouveau is the problem, and finally I was
  able to install by add "nouveau.modeset=0" at livecd boot options,
  without temp shutdown.

  After install I disable the nouveau at modprobe blacklist, but the
  system continues overheating and shutdown with basic usage.

  
  I have no idea what's happening with the bionic at my laptop.

  My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 16:22:40 2018
  InstallationDate: Installed on 2018-04-27 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptHistorylog:
   Start-Date: 2018-04-27  15:46:02
   End-Date: 2018-04-27  15:46:02
  VarLogDistupgradeAptlog:
   Log time: 2018-04-27 15:45:39.753331
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
   Log time: 2018-04-27 15:46:04.859979
  VarLogDistupgradeApttermlog:
   Log started: 2018-04-27  15:46:02
   Log ended: 2018-04-27  15:46:02
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edir   2354 F pulseaudio
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family 
Integrated Graphics Controller [144d:c0a5]
 Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5]
  HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d
  InstallationDate: Installed on 2018-04-27 (36 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-nouveau 1:1.0.15-2
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.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.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  

[Kernel-packages] [Bug 1581088] Re: Middle mouse (wheel-click) button stopped working after upgrade to 16.04

2019-06-15 Thread Davide Alberelli
Comment #91 gives me some seconds of autonomy with the central click,
but then it reverts back to being useless.

I am on Ubuntu 18.04, `uname -a`
```
Linux brenna 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux
```

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

Title:
  Middle mouse (wheel-click) button stopped working after upgrade to
  16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to 16.04 clicking the middle mouse button (scroll
  wheel) on my Logitech M185 stopped working.

  xev does not even show the event for clicking the wheel, while it
  shows other button clicks and scroll wheel up/down events.

  xinput list shows the USB receiver 2 times:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech USB Receiver   id=9[slave  pointer 
 (2)]
  ⎜   ↳ Logitech USB Receiver   id=10   [slave  pointer 
 (2)]
  ⎜   ↳ HID 046a:0023   id=13   [slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=16   [slave  pointer 
 (2)]
  ⎜   ↳ TPPS/2 IBM TrackPoint   id=17   [slave  pointer 
 (2)]

  Listing the capabilities looks like this:

  $ xinput list 9
  Logitech USB Receiver id=9[slave  pointer  (2)]
   Reporting 7 classes:
    Class originated from: 9. Type: XIButtonClass
    Buttons supported: 24
    Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel 
Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" 
"Button Side" "Button Extra" "Button Forward" "Button Back" "Button Task" 
"Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button 
Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" 
"Button Unknown" "Button Unknown" "Button Unknown"
    Button state:
    Class originated from: 9. Type: XIValuatorClass
    Detail for Valuator 0:
  Label: Rel X
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 9. Type: XIValuatorClass
    Detail for Valuator 1:
  Label: Rel Y
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 9. Type: XIValuatorClass
    Detail for Valuator 2:
  Label: Rel Horiz Wheel
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 9. Type: XIValuatorClass
    Detail for Valuator 3:
  Label: Rel Vert Wheel
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 9. Type: XIScrollClass
    Scroll info for Valuator 2
  type: 2 (horizontal)
  increment: 1.00
  flags: 0x0
    Class originated from: 9. Type: XIScrollClass
    Scroll info for Valuator 3
  type: 1 (vertical)
  increment: -1.00
  flags: 0x2 ( preferred )

  $ xinput list 10
  Logitech USB Receiver id=10   [slave  pointer  (2)]
   Reporting 6 classes:
    Class originated from: 10. Type: XIButtonClass
    Buttons supported: 7
    Button labels: "Button 0" "Button Unknown" "Button Unknown" "Button Wheel 
Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right"
    Button state:
    Class originated from: 10. Type: XIKeyClass
    Keycodes supported: 248
    Class originated from: 10. Type: XIValuatorClass
    Detail for Valuator 0:
  Label: Rel X
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 10. Type: XIValuatorClass
    Detail for Valuator 1:
  Label: Rel Y
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 10. Type: XIValuatorClass
    Detail for Valuator 2:
  Label: Rel Horiz Wheel
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 10. Type: XIScrollClass
    Scroll info for Valuator 2
  type: 2 (horizontal)
  increment: 1.00
  flags: 0x0

  Does anyone have an idea how I can attempt to further debug that issue? Or 
maybe even a solution? Should I consider this issue a bug? Can I provide more 
info?
  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  toby  11625 F pulseaudio
   /dev/snd/controlC0:  toby  11625 F pulseaudio
   /dev/snd/pcmC1D0p:   toby  11625 F...m pulseaudio
   /dev/snd/controlC1:  toby  11625 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  HibernationDevice: 

[Kernel-packages] [Bug 994248] Re: xhci stacktrace at connection of USB device to USB 3.0 port

2018-12-03 Thread Davide
I can confirm the issue is still active
It comes only after resume

Hardware: 
Dell Precision M4800 (full hardware test done to be sure to have no broken 
parts)

$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
A25
10/08/2018

$ uname -a
Linux DPM4800 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release -da
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.1 LTS
Release:18.04
Codename:   bionic

$ dmesg -l err | grep usb
[  532.802255] usb usb4-port1: cannot disable (err = -32)
[  536.890116] usb usb4-port1: Cannot enable. Maybe the USB cable is bad?
[  536.890145] usb usb4-port1: cannot disable (err = -32)
[  540.978079] usb usb4-port1: Cannot enable. Maybe the USB cable is bad?
[  540.978094] usb usb4-port1: cannot disable (err = -32)
[  545.382135] usb usb4-port1: Cannot enable. Maybe the USB cable is bad?
[  545.382164] usb usb4-port1: cannot disable (err = -32)
[  549.470069] usb usb4-port1: Cannot enable. Maybe the USB cable is bad?
[  549.470096] usb usb4-port1: cannot disable (err = -32)
[  549.470149] usb usb4-port1: unable to enumerate USB device
[  549.470169] usb usb4-port1: cannot disable (err = -32)
// also more lines like these with usb4 from port 2 to 6

$ dmesg -w (copy/paste only few lines from the end)
[ 1034.816581] xhci_hcd :00:14.0: Cannot set link state.
[ 1034.816586] usb usb4-port6: cannot disable (err = -32)
[ 1034.816636] usb usb4-port6: unable to enumerate USB device
[ 1034.816645] xhci_hcd :00:14.0: Cannot set link state.
[ 1034.816657] usb usb4-port6: cannot disable (err = -32)


$ lsusb 
Bus 002 Device 004: ID 0a5c:5801 Broadcom Corp. BCM5880 Secure Applications 
Processor with fingerprint swipe sensor
Bus 002 Device 003: ID 8087:07dc Intel Corp. 
Bus 002 Device 002: ID 8087:8000 Intel Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0c45:64d0 Microdia 
Bus 001 Device 002: ID 8087:8008 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 413c:5534 Dell Computer Corp. 
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 413c:2134 Dell Computer Corp. 
Bus 003 Device 005: ID 046e:55a5 Behavior Tech. Computer Corp. 
Bus 003 Device 004: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 003 Device 003: ID 413c:2513 Dell Computer Corp. internal USB Hub of E-Port 
Replicator
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


$ sudo lshw -C bus
  *-core
   description: Motherboard
   product: 0FVDR2
   vendor: Dell Inc.
   physical id: 0
   version: A00
   serial: /JTFFXY1/CN129633C30091/
  *-usb:0
   description: USB controller
   product: 8 Series/C220 Series Chipset Family USB xHCI
   vendor: Intel Corporation
   physical id: 14
   bus info: pci@:00:14.0
   version: 04
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi xhci bus_master cap_list
   configuration: driver=xhci_hcd latency=0
   resources: irq:26 memory:f782-f782
 *-usbhost:0
  product: xHCI Host Controller
  vendor: Linux 4.15.0-39-generic xhci-hcd
  physical id: 0
  bus info: usb@3
  logical name: usb3
  version: 4.15
  capabilities: usb-2.00
  configuration: driver=hub slots=15 speed=480Mbit/s
*-usb:0
 description: USB hub
 product: USB2134
 vendor: SMSC
 physical id: 4
 bus info: usb@3:4
 version: 41.00
 capabilities: usb-2.10
 configuration: driver=hub slots=3 speed=480Mbit/s
*-usb:1
 description: USB hub
 product: internal USB Hub of E-Port Replicator
 vendor: Dell Computer Corp.
 physical id: d
 bus info: usb@3:d
 version: 0.05
 capabilities: usb-2.00
 configuration: driver=hub maxpower=2mA slots=3 speed=480Mbit/s
 *-usbhost:1
  product: xHCI Host Controller
  vendor: Linux 4.15.0-39-generic xhci-hcd
  physical id: 1
  bus info: usb@4
  logical name: usb4
  version: 4.15
  capabilities: usb-3.00
  configuration: driver=hub slots=6 speed=5000Mbit/s
*-usb
 description: USB hub
 product: USB5534
 vendor: SMSC
 physical id: 3
 bus info: usb@4:3
 version: 41.00
 capabilities: usb-3.00
 configuration: driver=hub slots=3 speed=5000Mbit/s
  *-usb:1
   description: USB controller
   product: 8 Series/C220 Series Chipset Family USB EHCI #2
   vendor: Intel Corporation
   physical id: 1a
   bus info: pci@:00:1a.0
   version: 04
   width: 32 bits
   clock: 33MHz
   

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

2018-04-28 Thread Davide Riboli
Hi,

don't know if this can help but, as i wrote, with kernel 4.15.0-13 my
bluetooth was working.

After installing 4.15.03 (I used this utility to manage kernels:
http://www.teejeetech.in/p/ukuu-kernel-upgrade-utility.html) I've
switched on the bluetooth and then upgraded again and now bluetooth is
working even with 4.15.13.

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

Title:
  Bluetooth not working

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

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

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

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

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

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

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

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

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

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

2018-04-25 Thread Davide Riboli
Today I updated kernel to 4.15.13 and now everything is ok.

** Tags removed: kernel-bug-exists-upstream
** Tags added: kernel-fixed-upstream

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

Title:
  Bluetooth not working

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

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

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

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

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

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

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

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

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

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

2018-04-22 Thread Davide Riboli
The issue started with the first upgrade from kernel 4.15.0-13.

With kernel 4.15.0-13 bluetooth is working.

With every other after - included 4.17-rc1 (test done) - bluetooth is
disabled.

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

Title:
  Bluetooth not working

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

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

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

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

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

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

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

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

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

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

2018-04-22 Thread Davide Riboli
** Tags added: kernel-bug-exists-upstream

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

Title:
  Bluetooth not working

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

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

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

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

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

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

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

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

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

To manage notifications about this 

[Kernel-packages] [Bug 1764645] [NEW] Bluetooth not working

2018-04-17 Thread Davide Riboli
Public bug reported:

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

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

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

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

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

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

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

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

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


** Tags: amd64 apport-bug bionic

** Attachment added: "l"
   
https://bugs.launchpad.net/bugs/1764645/+attachment/5118925/+files/lspci-vnvn.log

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

Title:
  Bluetooth not working

Status in linux package in Ubuntu:
  New

Bug description:
  I've installed the Ubuntu Bionic Beta 2 and everything works fine but
  the bluetooth 

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-01-22 Thread Davide Prati
I wanna let you know that the hardware solution works.

Hope to help someone else, thanks for feedback and suggestions: Mika
Westerberg, Edenbar, Alex Friis.

Problem: UEFI mode, secure boot on, can't boot anything except netboot
but UEFI doesn't let you install a linux distro in order to update
kernel.

My solution: I ordered a new chip bios from ebay, i read the exact chip
name on the motherboard. I also ordered a usb flash programmer (CH314A).
I dissoldered the original chip from mobo (really easy with hot air
solder); i read it with the flash programmer to get a backup copy; I
erased its content; I write on the new chip a bios binary file that i
found online (feel free to send me an email and i'll provide you the
same 100% working file); I soldered the new chip on the motherboard and
IT WORKS

After this I also tried to write the same working bios file on the old
chip and I tried to resolder it on the motherboard. I can assure you
that it works in the same way! So you don't really need to replace the
chip, just erase it and write the new file on it.

If you have any questions pm me and i'll try to do my best to help you!!

Thanks all again

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

Title:
  corrupted BIOS due to Intel SPI bug in kernel

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI
  drivers results in a serial flash that is read only in Intel Broadwell
  and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set.

  Symptoms:
   * BIOS settings cannot be saved
   * USB Boot impossible
   * EFI entries read-only.

  ---

  Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
  the kernel so it is not compiled with Intel SPI support. But previous
  affected machines still suffered from a broken BIOS.

  Repair: If you still can boot into Ubuntu, you can recover your BIOS
  with the following steps:

  1. Boot into Ubuntu
  2. Download 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  3. Install the downloaded package:
    $ sudo dpkg -i 
linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  4. Make sure the kernel is installed without any error. Once installed, 
reboot.
  5. At grub, choose the newly installed kernel. You can choose the "recovery" 
mode.
  6. Reboot and go to BIOS settings to confirm your BIOS has been recovered.
  7. In case your BIOS is not recovered, reboot to the new kernel, then reboot 
*once again* to the new kernel, do not enter BIOS settings before the reboot. 
After the second reboot, check BIOS.
  8. If your BIOS issue remains, download another kernel from 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb,
 and use dpkg to install it, then repeat steps 4 to 6.

  After your BIOS is fixed, the kernel packages you just installed are
  no longer needed, you can remove it by running 'sudo dpkg -r linux-
  image-4.15.0-041500rc6-generic'.

  The patch used to build the linux v4.15 kernel in step 8 can be found
  at https://goo.gl/xUKJFR.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Yoga 3 11"
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you))
  Acer TravelMate B113
  Acer Swift SF314-52 (Fixed by 4.14.9)
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM
  HP 14-r012la

  ---

  Affected serial flash devices by manufacturer part number, JEDEC ID 
(SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c)
  /* ESMT */
     f25l32pa, 0x8c2016
     f25l32qa, 0x8c4116
     f25l64qa, 0x8c4117
  /* GigaDevice */
     gd25q16, 0xc84015
     gd25q32, 0xc84016
     gd25lq32, 0xc86016
     gd25q64, 0xc84017
     gd25lq64c, 0xc86017
     gd25q128, 0xc84018
     gd25q256, 0xc84019
  /* Winbond */
     w25q16dw, 0xef6015
     w25q32dw, 0xef6016
     w25q64dw, 

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-01-05 Thread Davide Prati
#475 Mika

Thanks, i'll give it a try and i'll let you know as soon as possible.

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

Title:
  corrupted BIOS due to Intel SPI bug in kernel

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI
  drivers results in a serial flash that is read only in Intel Broadwell
  and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set.

  Symptoms:
   * BIOS settings cannot be saved
   * USB Boot impossible
   * EFI entries read-only.

  ---

  Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
  the kernel so it is not compiled with Intel SPI support. But previous
  affected machines still suffered from a broken BIOS.

  Repair: If you still can boot into Ubuntu, you can recover your BIOS
  with the following steps:

  1. Boot into Ubuntu
  2. Download 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  3. Install the downloaded package:
    $ sudo dpkg -i 
linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  4. Make sure the kernel is installed without any error. Once installed, 
reboot.
  5. At grub, choose the newly installed kernel. You can choose the "recovery" 
mode.
  6. Reboot and go to BIOS settings to confirm your BIOS has been recovered.
  7. In case your BIOS is not recovered, reboot to the new kernel, then reboot 
*once again* to the new kernel, do not enter BIOS settings before the reboot. 
After the second reboot, check BIOS.
  8. If your BIOS issue remains, download another kernel from 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb,
 and use dpkg to install it, then repeat steps 4 to 6.

  After your BIOS is fixed, the kernel packages you just installed are
  no longer needed, you can remove it by running 'sudo dpkg -r linux-
  image-4.15.0-041500rc6-generic'.

  The patch used to build the linux v4.15 kernel in step 8 can be found
  at https://goo.gl/xUKJFR.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you))
  Acer TravelMate B113
  Acer Swift SF314-52 (Fixed by 4.14.9)
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM
  HP 14-r012la

  ---

  Affected serial flash devices by manufacturer part number, JEDEC ID 
(SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c)
  /* ESMT */
     f25l32pa, 0x8c2016
     f25l32qa, 0x8c4116
     f25l64qa, 0x8c4117
  /* GigaDevice */
     gd25q16, 0xc84015
     gd25q32, 0xc84016
     gd25lq32, 0xc86016
     gd25q64, 0xc84017
     gd25lq64c, 0xc86017
     gd25q128, 0xc84018
     gd25q256, 0xc84019
  /* Winbond */
     w25q16dw, 0xef6015
     w25q32dw, 0xef6016
     w25q64dw, 0xef6017
     w25q128fw, 0xef6018

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

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

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


[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-01-05 Thread Davide Prati
#469 Alex
So you are not going to flash the same file that you'll read from the chip on 
the board?
If not, where did you find the 'fresh' file?

#470 Mika 
I have a chip programmer, if i read the chip on the board i think i can open 
it, but which valor i have to set to CMP bit to re-enable BIOS features? And 
which valor should i find on the chip after reading it?

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

Title:
  corrupted BIOS due to Intel SPI bug in kernel

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI
  drivers results in a serial flash that is read only in Intel Broadwell
  and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set.

  Symptoms:
   * BIOS settings cannot be saved
   * USB Boot impossible
   * EFI entries read-only.

  ---

  Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
  the kernel so it is not compiled with Intel SPI support. But previous
  affected machines still suffered from a broken BIOS.

  Repair: If you still can boot into Ubuntu, you can recover your BIOS
  with the following steps:

  1. Boot into Ubuntu
  2. Download 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  3. Install the downloaded package:
    $ sudo dpkg -i 
linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  4. Make sure the kernel is installed without any error. Once installed, 
reboot.
  5. At grub, choose the newly installed kernel. You can choose the "recovery" 
mode.
  6. Reboot and go to BIOS settings to confirm your BIOS has been recovered.
  7. In case your BIOS is not recovered, reboot to the new kernel, then reboot 
*once again* to the new kernel, do not enter BIOS settings before the reboot. 
After the second reboot, check BIOS.
  8. If your BIOS issue remains, download another kernel from 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb,
 and use dpkg to install it, then repeat steps 4 to 6.

  After your BIOS is fixed, the kernel packages you just installed are
  no longer needed, you can remove it by running 'sudo dpkg -r linux-
  image-4.15.0-041500rc6-generic'.

  The patch used to build the linux v4.15 kernel in step 8 can be found
  at https://goo.gl/xUKJFR.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you))
  Acer TravelMate B113
  Acer Swift SF314-52 (Fixed by 4.14.9)
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM
  HP 14-r012la

  ---

  Affected serial flash devices by manufacturer part number, JEDEC ID 
(SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c)
  /* ESMT */
     f25l32pa, 0x8c2016
     f25l32qa, 0x8c4116
     f25l64qa, 0x8c4117
  /* GigaDevice */
     gd25q16, 0xc84015
     gd25q32, 0xc84016
     gd25lq32, 0xc86016
     gd25q64, 0xc84017
     gd25lq64c, 0xc86017
     gd25q128, 0xc84018
     gd25q256, 0xc84019
  /* Winbond */
     w25q16dw, 0xef6015
     w25q32dw, 0xef6016
     w25q64dw, 0xef6017
     w25q128fw, 0xef6018

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

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

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

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-01-05 Thread Davide Prati
#466 alexfriis

Are you sure that writing on a new chip or reflash the old chip with the
file you'll read from it can change the situation? I think you are going
to write the broken bios file with the same bug.. or not?

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

Title:
  corrupted BIOS due to Intel SPI bug in kernel

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI
  drivers results in a serial flash that is read only in Intel Broadwell
  and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set.

  Symptoms:
   * BIOS settings cannot be saved
   * USB Boot impossible
   * EFI entries read-only.

  ---

  Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
  the kernel so it is not compiled with Intel SPI support. But previous
  affected machines still suffered from a broken BIOS.

  Repair: If you still can boot into Ubuntu, you can recover your BIOS
  with the following steps:

  1. Boot into Ubuntu
  2. Download 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  3. Install the downloaded package:
    $ sudo dpkg -i 
linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  4. Make sure the kernel is installed without any error. Once installed, 
reboot.
  5. At grub, choose the newly installed kernel. You can choose the "recovery" 
mode.
  6. Reboot and go to BIOS settings to confirm your BIOS has been recovered.
  7. In case your BIOS is not recovered, reboot to the new kernel, then reboot 
*once again* to the new kernel, do not enter BIOS settings before the reboot. 
After the second reboot, check BIOS.
  8. If your BIOS issue remains, download another kernel from 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb,
 and use dpkg to install it, then repeat steps 4 to 6.

  After your BIOS is fixed, the kernel packages you just installed are
  no longer needed, you can remove it by running 'sudo dpkg -r linux-
  image-4.15.0-041500rc6-generic'.

  The patch used to build the linux v4.15 kernel in step 8 can be found
  at https://goo.gl/xUKJFR.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you))
  Acer TravelMate B113
  Acer Swift SF314-52 (Fixed by 4.14.9)
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM
  HP 14-r012la

  ---

  Affected serial flash devices by manufacturer part number, JEDEC ID 
(SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c)
  /* ESMT */
     f25l32pa, 0x8c2016
     f25l32qa, 0x8c4116
     f25l64qa, 0x8c4117
  /* GigaDevice */
     gd25q16, 0xc84015
     gd25q32, 0xc84016
     gd25lq32, 0xc86016
     gd25q64, 0xc84017
     gd25lq64c, 0xc86017
     gd25q128, 0xc84018
     gd25q256, 0xc84019
  /* Winbond */
     w25q16dw, 0xef6015
     w25q32dw, 0xef6016
     w25q64dw, 0xef6017
     w25q128fw, 0xef6018

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

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

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


[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2018-01-03 Thread Davide Prati
I really need some ideas, here's my situation:
I formatted my SSD, my BIOS is in UEFI mode with secure boot enabled and i 
can't change any settings.
I can only boot from PXE over network ipv4 / ipv6.

I tried to install ubuntu on my SSD with another computer but an user
noticed me that EFI boot is looking for an UUID partition of ubuntu that
it changed after i formatted my drive.

So i thought that the solution was install successfully ubuntu on my SSD
in my stucked laptop and then through efibootmgr command i were able to
read which UUID i need to setup into the partition to make the OS
bootable.

Using AIOBOOT i'm able to boot grub2 and creating a bootable image of
ubuntu the installation begins but it stops for some reason (i think
uefi blocked the installation).

In this situation i don't know how to do a kernel update to fix the BIOS.
If anyone have a UEFI (with secure boot) compatible guide to boot and install 
linux please tell us, i think it's the only way to fix our laptops

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Acer Swift SF314-52 (Fixed by 4.14.9)
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM
  HP 14-r012la

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

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

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


[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-30 Thread Davide Prati
#396

I'm connected the laptop with an ethernet cable, but the problem is secure boot.
Did you try it with secure boot enabled?

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

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

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


[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-30 Thread Davide Prati
#386
I tried boot into linux via netboot but secure boot forbids me from install 
anything. I can boot into grub but "ls -l" command to get UUID doesn't work for 
the same reason.

Can you tell us how to boot into linux to get UUID with secure boot
enabled? Or do you have an alternative solution?

#395
I think the biggest problem is how to get this UUID if we cannot boot in any 
way..
However i can boot ssd in another pc as first drive so i can use linux to 
change UUID when i'll discover it.


Hope in you guys..

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

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

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


[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-30 Thread Davide Prati
Thanks Artur (radium88) #386 for the precious information. I'll try to follow 
your steps and i'll report you as soon as possible.
Hope the bios will let me boot from PXE over network without problems.

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

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

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


[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-30 Thread Davide Prati
i also tried to upgrade kernel with ukuu, after the reboot on the
working computer ukuu says 4.14.9 is running. Moving ssd back to lenovo
it always show ubuntu boot failed. in attachment a screen of my bios
boot page.

** Attachment added: "bios boot page"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+attachment/5029071/+files/WhatsApp%20Image%202017-12-30%20at%2011.54.05.jpeg

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

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

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


[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-30 Thread Davide Prati
Hi alexfriis,
i have the same problem of user's post #375. I tried to remove my ssd to 
install ubuntu from another one.
When i move back my sdd to the lenovo laptop it keeps saying: ubuntu boot 
failed. In boot options i have the voice "ubuntu" in first place, so i don't 
know why it doesn't boot.

Other ideas?

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

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

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


[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-20 Thread Davide Depau
I'm running Linux 4.13.0-17-generic (nov 6th) on Bionic on a Lenovo Thinkpad X1 
Yoga 1st (20FR) and with this kernel version it seems *UNaffected*. I'm not 
going to upgrade it now that I know of this issue.
However, if anybody knows whether this kernel version already triggers the bug, 
we can tell that this machine is unaffected.

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Invalid
Status in linux-hwe-edge source package in Xenial:
  Fix Committed
Status in linux-oem source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux-hwe-edge source package in Artful:
  Invalid
Status in linux-oem source package in Artful:
  Invalid
Status in linux package in openSUSE:
  New

Bug description:
  SRU Justification

  Impact: Many users are reporting issues with bios corruption with
  17.10. This seems to stem from enabling the intel-spi-* drivers in the
  kernel, which don't appear to be ready for use on end-user machines.

  Fix: Disable this driver.

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Hi all,

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

   UPDATE (01/12/2017) 

  LENOVO machines affected so far (please add your affected model to
  this list):

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  The bug also affects Acer Aspire E5-771G.

  ---

  Temporary workaround:
  https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t
  -Save-Settings-Or-Exit/m-p/3853208#M157885

  ---

  result from apport-collect 1734147:

  ---

  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tob1608 F pulseaudio
   /dev/snd/controlC0:  tob1608 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-22 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20378
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN43WW(V3.03)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Y50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20378
  dmi.product.version: Lenovo Y50-70
  dmi.sys.vendor: LENOVO

  ---

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

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


[Kernel-packages] [Bug 1725987] [NEW] watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [ksoftirqd/3:28]

2017-10-22 Thread Costa davide
Public bug reported:

The system freezed for a while and i needed to hard reset PC

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
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
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:  gdm1091 F pulseaudio
  matlin 1415 F pulseaudio
 /dev/snd/controlC1:  gdm1091 F pulseaudio
  matlin 1415 F pulseaudio
Date: Sun Oct 22 16:00:32 2017
Failure: oops
InstallationDate: Installed on 2017-10-20 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
IwConfig:
 enp0s8no wireless extensions.
 
 lono wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=02653f53-eed9-4176-8ec8-6168848ded94 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
RfKill:
 
SourcePackage: linux
Title: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [ksoftirqd/3:28]
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/23/2010
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS M2N-E ACPI BIOS Revision 5001
dmi.board.name: M2N-E
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2N-EACPIBIOSRevision5001:bd03/23/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-E:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-kerneloops artful kernel-driver-nvidia kernel-oops

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

Title:
  watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [ksoftirqd/3:28]

Status in linux package in Ubuntu:
  New

Bug description:
  The system freezed for a while and i needed to hard reset PC

  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
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  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:  gdm1091 F pulseaudio
matlin 1415 F pulseaudio
   /dev/snd/controlC1:  gdm1091 F pulseaudio
matlin 1415 F pulseaudio
  Date: Sun Oct 22 16:00:32 2017
  Failure: oops
  InstallationDate: Installed on 2017-10-20 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IwConfig:
   enp0s8no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=02653f53-eed9-4176-8ec8-6168848ded94 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
  RfKill:
   
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [ksoftirqd/3:28]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2010
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2N-E ACPI BIOS Revision 5001
  dmi.board.name: M2N-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

[Kernel-packages] [Bug 1714930] [NEW] package linux-signed-image-4.4.0-66-generic 4.4.0-66.87 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-09-04 Thread Davide Oricchio
Public bug reported:

I cannot install any new package

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-signed-image-4.4.0-66-generic 4.4.0-66.87
ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
Uname: Linux 4.4.0-62-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Mon Sep  4 13:20:35 2017
DpkgHistoryLog:
 Start-Date: 2017-09-04  13:20:08
 Commandline: aptdaemon role='role-install-packages' sender=':1.77'
 Install: libhsqldb1.8.0-java:amd64 (1.8.0.10+dfsg-6, automatic), 
libreoffice-java-common:amd64 (1:5.1.6~rc2-0ubuntu1~xenial2, automatic), 
libreoffice-base:amd64 (1:5.1.6~rc2-0ubuntu1~xenial2), 
libreoffice-sdbc-firebird:amd64 (1:5.1.6~rc2-0ubuntu1~xenial2, automatic), 
libreoffice-sdbc-hsqldb:amd64 (1:5.1.6~rc2-0ubuntu1~xenial2, automatic), 
libreoffice-base-drivers:amd64 (1:5.1.6~rc2-0ubuntu1~xenial2, automatic)
DuplicateSignature:
 package:linux-signed-image-4.4.0-66-generic:4.4.0-66.87
 Setting up linux-signed-image-4.4.0-64-generic (4.4.0-64.85) ...
 cp: cannot stat '/boot/vmlinuz-4.4.0-64-generic': No such file or directory
 dpkg: error processing package linux-signed-image-4.4.0-64-generic 
(--configure):
  subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-06-07 (454 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: linux-signed
Title: package linux-signed-image-4.4.0-66-generic 4.4.0-66.87 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package linux-signed-image-4.4.0-66-generic 4.4.0-66.87 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in linux-signed package in Ubuntu:
  New

Bug description:
  I cannot install any new package

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-signed-image-4.4.0-66-generic 4.4.0-66.87
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Mon Sep  4 13:20:35 2017
  DpkgHistoryLog:
   Start-Date: 2017-09-04  13:20:08
   Commandline: aptdaemon role='role-install-packages' sender=':1.77'
   Install: libhsqldb1.8.0-java:amd64 (1.8.0.10+dfsg-6, automatic), 
libreoffice-java-common:amd64 (1:5.1.6~rc2-0ubuntu1~xenial2, automatic), 
libreoffice-base:amd64 (1:5.1.6~rc2-0ubuntu1~xenial2), 
libreoffice-sdbc-firebird:amd64 (1:5.1.6~rc2-0ubuntu1~xenial2, automatic), 
libreoffice-sdbc-hsqldb:amd64 (1:5.1.6~rc2-0ubuntu1~xenial2, automatic), 
libreoffice-base-drivers:amd64 (1:5.1.6~rc2-0ubuntu1~xenial2, automatic)
  DuplicateSignature:
   package:linux-signed-image-4.4.0-66-generic:4.4.0-66.87
   Setting up linux-signed-image-4.4.0-64-generic (4.4.0-64.85) ...
   cp: cannot stat '/boot/vmlinuz-4.4.0-64-generic': No such file or directory
   dpkg: error processing package linux-signed-image-4.4.0-64-generic 
(--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-06-07 (454 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: linux-signed
  Title: package linux-signed-image-4.4.0-66-generic 4.4.0-66.87 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0

2017-04-07 Thread Davide
I've reinstalled Ubuntu and now it starts. I typed dmesg and there's
this message anyway:

[0.875431] pcieport :00:1c.4: AER: Corrected error received: id=00e4
[0.875438] pcieport :00:1c.4: PCIe Bus Error: severity=Corrected, 
type=Data Link Layer, id=00e4(Transmitter ID)
[0.875440] pcieport :00:1c.4:   device [8086:a114] error 
status/mask=0100/2000
[0.875442] pcieport :00:1c.4:[ 8] RELAY_NUM Rollover
[0.879660] pcieport :00:1c.4: AER: Corrected error received: id=00e4
[0.879667] pcieport :00:1c.4: PCIe Bus Error: severity=Corrected, 
type=Data Link Layer, id=00e4(Transmitter ID)
[0.879669] pcieport :00:1c.4:   device [8086:a114] error 
status/mask=0100/2000
[0.879670] pcieport :00:1c.4:[ 8] RELAY_NUM Rollover
[0.911313] pcieport :00:1c.4: AER: Corrected error received: id=00e4
[0.911319] pcieport :00:1c.4: PCIe Bus Error: severity=Corrected, 
type=Data Link Layer, id=00e4(Transmitter ID)
[0.911320] pcieport :00:1c.4:   device [8086:a114] error 
status/mask=0100/2000
[0.911321] pcieport :00:1c.4:[ 8] RELAY_NUM Rollover
[0.923536] pcieport :00:1c.4: AER: Corrected error received: id=00e4
[0.923542] pcieport :00:1c.4: PCIe Bus Error: severity=Corrected, 
type=Data Link Layer, id=00e4(Transmitter ID)
[0.923543] pcieport :00:1c.4:   device [8086:a114] error 
status/mask=0100/2000
[0.923544] pcieport :00:1c.4:[ 8] RELAY_NUM Rollover

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

Title:
  AER: Corrected error received: id=00e0

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

Bug description:
  Note: Current workaround is to add pci=noaer to your kernel command
  line:

  1) edit /etc/default/grub and and add pci=noaer to the line starting with 
GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: 
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
  2) run "sudo update-grub"
  3) reboot

  

  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
   /dev/snd/controlC0:  david  1502 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 30 13:19:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.153
  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: 08/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.00
  dmi.board.name: 0NT3WX
  

[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0

2017-04-07 Thread Davide
My kernel version is 4.8

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

Title:
  AER: Corrected error received: id=00e0

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

Bug description:
  Note: Current workaround is to add pci=noaer to your kernel command
  line:

  1) edit /etc/default/grub and and add pci=noaer to the line starting with 
GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: 
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
  2) run "sudo update-grub"
  3) reboot

  

  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
   /dev/snd/controlC0:  david  1502 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 30 13:19:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.153
  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: 08/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0

2017-04-07 Thread Davide
The same issue: Ubuntu 16.04.2 on Asus N552VW-FY136T writes to
kernel.log and then completely freeze

Mar 24 09:02:09 localhost kernel: [ 6972.305728] pcieport :00:1c.5: AER: 
Corrected error received: id=00e5
pcieport :00:1c.5 PCIe Bus Error: severity=corrected, type=physical layer, 
id=00e4(Receiver 12)
pcieport :00:1c.5 device[8086:a112] error status/mask=0001/2

The workarounds described here don't work for me.

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

Title:
  AER: Corrected error received: id=00e0

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

Bug description:
  Note: Current workaround is to add pci=noaer to your kernel command
  line:

  1) edit /etc/default/grub and and add pci=noaer to the line starting with 
GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: 
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
  2) run "sudo update-grub"
  3) reboot

  

  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
   /dev/snd/controlC0:  david  1502 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 30 13:19:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.153
  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: 08/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1173372] Re: apt-get hangs: DKMS: install completed.

2015-10-26 Thread Davide
I can confirm that workaround in #12 works for me on upgrading a macbook
pro early 2015 from 15.04 to 15.10.

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

Title:
  apt-get hangs:  DKMS: install completed.

Status in bcmwl package in Ubuntu:
  Invalid

Bug description:
  result of bug
  a) DKMS: install completed.
  b) can no longer use apt-get nor GUI  "update manager"

  steps to reproduce:
  - get working dell laptop with broadcom wifi hardware, update firmware
  - wipe with DBAN CD
  - install 12.04 version of Ubuntu
  - use GUI app to update,  "update manager"
  - reboot
  - open terminal
  sudo apt-get update
  sudo apt-get --reinstall install bcmwl-kernel-source

  results: 
  a) DKMS: install completed.
  b) can no longer use apt-get nor GUI  "update manager"

  
  notes:
  ==

  I followed the docs on 
  https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx?action=login=1

  My hardware should support the b43 - Open source driver

  For Chip ID BCM4306 (rev 03)  BCM4311

  
  =
  below is text dump from terminal

  id@id-laptop:~$ sudo -s
  [sudo] password for id: 
  root@id-laptop:~# apt-get update
  Hit http://us.archive.ubuntu.com precise Release.gpg
  Get:1 http://us.archive.ubuntu.com precise-updates Release.gpg [198 B]
  Get:2 http://us.archive.ubuntu.com precise-backports Release.gpg [198 B]  
 
  Hit http://us.archive.ubuntu.com precise Release  
 
  Get:3 http://security.ubuntu.com precise-security Release.gpg [198 B] 
 
  Get:4 http://extras.ubuntu.com precise Release.gpg [72 B] 
 
  Get:5 http://us.archive.ubuntu.com precise-updates Release [49.6 kB]  
 
  Get:6 http://security.ubuntu.com precise-security Release [49.6 kB]   
 
  Get:7 http://us.archive.ubuntu.com precise-backports Release [49.6 kB]
 
  Hit http://extras.ubuntu.com precise Release  
 
  Hit http://us.archive.ubuntu.com precise/main Sources 
 
  Hit http://us.archive.ubuntu.com precise/restricted Sources   
 
  Hit http://us.archive.ubuntu.com precise/universe Sources 
 
  Hit http://us.archive.ubuntu.com precise/multiverse Sources   
 
  Hit http://us.archive.ubuntu.com precise/main i386 Packages   
 
  Hit http://us.archive.ubuntu.com precise/restricted i386 Packages 
 
  Hit http://us.archive.ubuntu.com precise/universe i386 Packages   
 
  Hit http://us.archive.ubuntu.com precise/multiverse i386 Packages 
 
  Hit http://us.archive.ubuntu.com precise/main TranslationIndex
 
  Hit http://extras.ubuntu.com precise/main Sources 
 
  Hit http://us.archive.ubuntu.com precise/multiverse TranslationIndex  
  Get:8 http://security.ubuntu.com precise-security/main Sources [69.9 kB]
  Hit http://us.archive.ubuntu.com precise/restricted TranslationIndex  
  Hit http://us.archive.ubuntu.com precise/universe TranslationIndex
 
  Get:9 http://us.archive.ubuntu.com precise-updates/main Sources [379 kB]  
 
  Hit http://extras.ubuntu.com precise/main i386 Packages   
 
  Ign http://extras.ubuntu.com precise/main TranslationIndex
 
  Get:10 http://security.ubuntu.com precise-security/restricted Sources [2,494 
B]
  Get:11 http://security.ubuntu.com precise-security/universe Sources [24.0 kB] 
 
  Get:12 http://security.ubuntu.com precise-security/multiverse Sources [1,389 
B]
  Get:13 http://security.ubuntu.com precise-security/main i386 Packages [259 
kB] 
  Ign http://extras.ubuntu.com precise/main Translation-en_US   
 
  Ign http://extras.ubuntu.com precise/main Translation-en  
 
  Get:14 http://us.archive.ubuntu.com precise-updates/restricted Sources [5,467 
B]
  Get:15 http://us.archive.ubuntu.com precise-updates/universe Sources [85.4 
kB] 
  Get:16 http://security.ubuntu.com precise-security/restricted i386 Packages 
[4,620 B]
  Get:17 http://security.ubuntu.com precise-security/universe i386 Packages 
[73.4 kB]
  Get:18 http://us.archive.ubuntu.com precise-updates/multiverse Sources [6,562 
B]
  Get:19 http://us.archive.ubuntu.com precise-updates/main i386 Packages [612 
kB]
  Get:20 http://security.ubuntu.com precise-security/multiverse i386 Packages 
[2,368 B]
  Hit http://security.ubuntu.com precise-security/main TranslationIndex 
 
  Hit http://security.ubuntu.com precise-security/multiverse TranslationIndex   
 
  Hit http://security.ubuntu.com precise-security/restricted TranslationIndex   
 
  Hit http://security.ubuntu.com precise-security/universe TranslationIndex 
 
  Hit 

[Kernel-packages] [Bug 1504751] Re: [HP Probook 4510s] Fan at full speed after suspend

2015-10-11 Thread Davide Depau
The bug is still around.

** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-4.3-rc5

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

Title:
  [HP Probook 4510s] Fan at full speed after suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I turn on the PC, the fan runs normally and I have no issues at
  all. However, if I suspend the computer and resume it, the fan runs at
  full speed, regardless of the actual internal temperature. This is
  very annoying in libraries.

  This bug has been around for years, I just didn't need the computer in quiet 
places back then, so I never reported it.
  I believe it didn't happen with Maverick.

  I'm running Ubuntu 15.10, with Linux 4.2.0-14-generic x86_64
  (systemd).

  Other (probably) useful information:
  https://bugzilla.redhat.com/show_bug.cgi?id=895276
  https://bbs.archlinux.org/viewtopic.php?id=89235
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1173997

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-14-generic 4.2.0-14.16
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  davideddu   3441 F pulseaudio
   /dev/snd/seq:timidity971 F timidity
  Date: Sat Oct 10 12:17:48 2015
  HibernationDevice: RESUME=UUID=91dfd5b8-4d71-4adf-bef2-b614d3874c91
  InstallationDate: Installed on 2014-12-07 (306 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  MachineType: Hewlett-Packard HP ProBook 4510s
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic.efi.signed 
root=UUID=64da7c2d-9769-48ec-b34b-22339a33c767 ro quiet splash vt.handoff=7
  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.2.0-14-generic N/A
   linux-backports-modules-4.2.0-14-generic  N/A
   linux-firmware1.149
  SourcePackage: linux
  UpgradeStatus: Upgraded to wily on 2015-09-15 (24 days ago)
  dmi.bios.date: 12/09/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PZI Ver. F.20
  dmi.board.name: 3072
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 24.0F
  dmi.chassis.asset.tag: CNU0114QT2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PZIVer.F.20:bd12/09/2011:svnHewlett-Packard:pnHPProBook4510s:pvrF.20:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0F:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4510s
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard

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

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


Re: [Kernel-packages] [Bug 1504751] Re: [HP Probook 4510s] Fan at full speed after suspend

2015-10-11 Thread Davide Depau
How am I supposed to do that? Will such an old kernel work on wily?

On Oct 12, 2015 1:25 AM, "Christopher M. Penalver" 
<christopher.m.penal...@gmail.com> wrote:
>
> Davide Depau, the next step is to fully commit bisect from kernel 2.6.35 
> to 2.6.38 in order to identify the last good kernel commit, followed 
> immediately by the first bad one. This will allow for a more expedited 
> analysis of the root cause of your issue. Could you please do this 
> following https://wiki.ubuntu.com/Kernel/KernelBisection ? 
>
> Please note, finding adjacent kernel versions is not fully commit 
> bisecting. 
>
> Thank you for your understanding. 
>
> Helpful bug reporting tips: 
> https://wiki.ubuntu.com/ReportingBugs 
>
> ** Changed in: linux (Ubuntu) 
>    Status: Confirmed => Incomplete 
>
> -- 
> You received this bug notification because you are subscribed to the bug 
> report. 
> https://bugs.launchpad.net/bugs/1504751 
>
> Title: 
>   [HP Probook 4510s] Fan at full speed after suspend 
>
> Status in linux package in Ubuntu: 
>   Incomplete 
>
> Bug description: 
>   When I turn on the PC, the fan runs normally and I have no issues at 
>   all. However, if I suspend the computer and resume it, the fan runs at 
>   full speed, regardless of the actual internal temperature. This is 
>   very annoying in libraries. 
>
>   This bug has been around for years, I just didn't need the computer in 
> quiet places back then, so I never reported it. 
>   I believe it didn't happen with Maverick. 
>
>   I'm running Ubuntu 15.10, with Linux 4.2.0-14-generic x86_64 
>   (systemd). 
>
>   Other (probably) useful information: 
>   https://bugzilla.redhat.com/show_bug.cgi?id=895276 
>   https://bbs.archlinux.org/viewtopic.php?id=89235 
>   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1173997 
>
>   ProblemType: Bug 
>   DistroRelease: Ubuntu 15.10 
>   Package: linux-image-4.2.0-14-generic 4.2.0-14.16 
>   ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2 
>   Uname: Linux 4.2.0-14-generic x86_64 
>   ApportVersion: 2.19.1-0ubuntu2 
>   Architecture: amd64 
>   AudioDevicesInUse: 
>    USER    PID ACCESS COMMAND 
>    /dev/snd/controlC0:  davideddu   3441 F pulseaudio 
>    /dev/snd/seq:    timidity    971 F timidity 
>   Date: Sat Oct 10 12:17:48 2015 
>   HibernationDevice: RESUME=UUID=91dfd5b8-4d71-4adf-bef2-b614d3874c91 
>   InstallationDate: Installed on 2014-12-07 (306 days ago) 
>   InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
> (20141022.1) 
>   MachineType: Hewlett-Packard HP ProBook 4510s 
>   ProcFB: 0 inteldrmfb 
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic.efi.signed 
> root=UUID=64da7c2d-9769-48ec-b34b-22339a33c767 ro quiet splash vt.handoff=7 
>   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.2.0-14-generic N/A 
>    linux-backports-modules-4.2.0-14-generic  N/A 
>    linux-firmware    1.149 
>   SourcePackage: linux 
>   UpgradeStatus: Upgraded to wily on 2015-09-15 (24 days ago) 
>   dmi.bios.date: 12/09/2011 
>   dmi.bios.vendor: Hewlett-Packard 
>   dmi.bios.version: 68PZI Ver. F.20 
>   dmi.board.name: 3072 
>   dmi.board.vendor: Hewlett-Packard 
>   dmi.board.version: KBC Version 24.0F 
>   dmi.chassis.asset.tag: CNU0114QT2 
>   dmi.chassis.type: 10 
>   dmi.chassis.vendor: Hewlett-Packard 
>   dmi.modalias: 
> dmi:bvnHewlett-Packard:bvr68PZIVer.F.20:bd12/09/2011:svnHewlett-Packard:pnHPProBook4510s:pvrF.20:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0F:cvnHewlett-Packard:ct10:cvr:
>  
>   dmi.product.name: HP ProBook 4510s 
>   dmi.product.version: F.20 
>   dmi.sys.vendor: Hewlett-Packard 
>
> To manage notifications about this bug go to: 
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504751/+subscriptions

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

Title:
  [HP Probook 4510s] Fan at full speed after suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When I turn on the PC, the fan runs normally and I have no issues at
  all. However, if I suspend the computer and resume it, the fan runs at
  full speed, regardless of the actual internal temperature. This is
  very annoying in libraries.

  This bug has been around for years, I just didn't need the computer in quiet 
places back then, so I never reported it.
  I believe i

[Kernel-packages] [Bug 1504751] Re: [HP Probook 4510s] Fan at full speed after suspend

2015-10-11 Thread Davide Depau
** Bug watch added: Red Hat Bugzilla #895276
   https://bugzilla.redhat.com/show_bug.cgi?id=895276

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

Title:
  [HP Probook 4510s] Fan at full speed after suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When I turn on the PC, the fan runs normally and I have no issues at
  all. However, if I suspend the computer and resume it, the fan runs at
  full speed, regardless of the actual internal temperature. This is
  very annoying in libraries.

  This bug has been around for years, I just didn't need the computer in quiet 
places back then, so I never reported it.
  I believe it didn't happen with Maverick.

  I'm running Ubuntu 15.10, with Linux 4.2.0-14-generic x86_64
  (systemd).

  Other (probably) useful information:
  https://bugzilla.redhat.com/show_bug.cgi?id=895276
  https://bbs.archlinux.org/viewtopic.php?id=89235
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1173997

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-14-generic 4.2.0-14.16
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  davideddu   3441 F pulseaudio
   /dev/snd/seq:timidity971 F timidity
  Date: Sat Oct 10 12:17:48 2015
  HibernationDevice: RESUME=UUID=91dfd5b8-4d71-4adf-bef2-b614d3874c91
  InstallationDate: Installed on 2014-12-07 (306 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  MachineType: Hewlett-Packard HP ProBook 4510s
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic.efi.signed 
root=UUID=64da7c2d-9769-48ec-b34b-22339a33c767 ro quiet splash vt.handoff=7
  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.2.0-14-generic N/A
   linux-backports-modules-4.2.0-14-generic  N/A
   linux-firmware1.149
  SourcePackage: linux
  UpgradeStatus: Upgraded to wily on 2015-09-15 (24 days ago)
  dmi.bios.date: 12/09/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PZI Ver. F.20
  dmi.board.name: 3072
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 24.0F
  dmi.chassis.asset.tag: CNU0114QT2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PZIVer.F.20:bd12/09/2011:svnHewlett-Packard:pnHPProBook4510s:pvrF.20:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0F:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4510s
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1469480] [NEW] HP pavillon zd7000 doesn't detect wifi board

2015-06-28 Thread davide
Public bug reported:

I send you more information about the system and the hardware :
02:03.0 Network controller [0280]: Broadcom Corporation BCM4306 802.11b/g 
Wireless LAN Controller [14e4:4320] (rev 03)
Subsystem: Hewlett-Packard Company Broadcom 802.11b/g WLAN [103c:12f4]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 32
Interrupt: pin A routed to IRQ 21
Region 0: Memory at d2004000 (32-bit, non-prefetchable) [size=8K]
Kernel driver in use: b43-pci-bridge
Kernel modules: ssb

davide@davide-Pavilion-zd7000-PB949EA-ABZ:~$ lsb_release -rd
Description:Ubuntu 12.04.5 LTS
Release:12.04
davide@davide-Pavilion-zd7000-PB949EA-ABZ:~$ uname -a
Linux davide-Pavilion-zd7000-PB949EA-ABZ 3.2.0-67-lowlatency-pae #70-Ubuntu SMP 
PREEMPT Tue Jul 15 06:33:44 UTC 2014 i686 i686 i386 GNU/Linux
davide@davide-Pavilion-zd7000-PB949EA-ABZ:~$ apt-cache policy 
firmware-b43-installer
firmware-b43-installer:
  Installato: 1:015-9
  Candidato:  1:015-9
  Tabella versione:
 *** 1:015-9 0
500 http://archive.ubuntu.com/ubuntu/ precise/multiverse i386 Packages
100 /var/lib/dpkg/status
davide@davide-Pavilion-zd7000-PB949EA-ABZ:~$ sudo dmidecode -s bios-version
[sudo] password for davide: 
F.34 
davide@davide-Pavilion-zd7000-PB949EA-ABZ:~$ sudo dmidecode -s 
bios-release-date 
07/12/2004

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: firmware-b43-installer 1:015-9
ProcVersionSignature: Ubuntu 3.2.0-67.70-lowlatency-pae 3.2.60
Uname: Linux 3.2.0-67-lowlatency-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu17.8
Architecture: i386
Date: Sun Jun 28 08:44:52 2015
InstallationMedia: Ubuntu-Studio 12.04.3 Precise Pangolin - Release i386 
(20130820)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=it:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SourcePackage: b43-fwcutter
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: b43-fwcutter (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 precise

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

Title:
  HP pavillon  zd7000 doesn't detect wifi board

Status in b43-fwcutter package in Ubuntu:
  New

Bug description:
  I send you more information about the system and the hardware :
  02:03.0 Network controller [0280]: Broadcom Corporation BCM4306 802.11b/g 
Wireless LAN Controller [14e4:4320] (rev 03)
Subsystem: Hewlett-Packard Company Broadcom 802.11b/g WLAN [103c:12f4]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 32
Interrupt: pin A routed to IRQ 21
Region 0: Memory at d2004000 (32-bit, non-prefetchable) [size=8K]
Kernel driver in use: b43-pci-bridge
Kernel modules: ssb

  davide@davide-Pavilion-zd7000-PB949EA-ABZ:~$ lsb_release -rd
  Description:  Ubuntu 12.04.5 LTS
  Release:  12.04
  davide@davide-Pavilion-zd7000-PB949EA-ABZ:~$ uname -a
  Linux davide-Pavilion-zd7000-PB949EA-ABZ 3.2.0-67-lowlatency-pae #70-Ubuntu 
SMP PREEMPT Tue Jul 15 06:33:44 UTC 2014 i686 i686 i386 GNU/Linux
  davide@davide-Pavilion-zd7000-PB949EA-ABZ:~$ apt-cache policy 
firmware-b43-installer
  firmware-b43-installer:
Installato: 1:015-9
Candidato:  1:015-9
Tabella versione:
   *** 1:015-9 0
  500 http://archive.ubuntu.com/ubuntu/ precise/multiverse i386 Packages
  100 /var/lib/dpkg/status
  davide@davide-Pavilion-zd7000-PB949EA-ABZ:~$ sudo dmidecode -s bios-version
  [sudo] password for davide: 
  F.34 
  davide@davide-Pavilion-zd7000-PB949EA-ABZ:~$ sudo dmidecode -s 
bios-release-date 
  07/12/2004

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firmware-b43-installer 1:015-9
  ProcVersionSignature: Ubuntu 3.2.0-67.70-lowlatency-pae 3.2.60
  Uname: Linux 3.2.0-67-lowlatency-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  Date: Sun Jun 28 08:44:52 2015
  InstallationMedia: Ubuntu-Studio 12.04.3 Precise Pangolin - Release i386 
(20130820)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=it:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: b43-fwcutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/1469480/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel

[Kernel-packages] [Bug 131094] Re: Heavy Disk I/O harms desktop responsiveness

2015-03-12 Thread Davide Depau
This issue is not getting enough attention. I don't know if you all have SSDs 
but most people don't. On hard disk drives this is a huge issue. System 
responsiveness drops when tracker is running and pretty much nothing else can 
run smoothly while it's running, even on computers with fast CPU/large amounts 
of RAM. The I/O is often the cause of system slowdown and this needs to be 
reduced as much as possible.
I'm sure this issue can be fixed, a background daemon doesn't need to run at 
full speed, it can be niced to 19, and internal fixes can be made.

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

Title:
  Heavy Disk I/O harms desktop responsiveness

Status in The Linux Kernel:
  Fix Released
Status in The Linux Mint Distribution:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: linux-source-2.6.22

  When compared with 2.6.15 in feisty, heavy disk I/O causes increased
  iowait times and affects desktop responsiveness in 2.6.22

  this appears to be a regression from 2.6.15 where iowait is much lower
  and desktop responsiveness is unaffected with the same I/O load

  Easy to reproduce with tracker - index the same set of files with
  2.6.15 kernel and 2.6.22 kernel and the difference in desktop
  responsiveness is massive

  I have not confirmed if a non-tracker process which does heavy disk
  i/o (especially writing) replicates this yet - will do further
  investigation soon

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

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


Re: [Kernel-packages] [Bug 1315221] Re: 8086:08b1 (rev 6b) [Dell XPS 13 9333] iwlwifi regularly loses connection/becomes unusable on Intel 7260

2014-11-15 Thread Davide
For me then problem solved after upgrading to 14.10

On 13:05, Sat, Nov 15, 2014 gianluca antonelli1...@gmail.com wrote:

 hello,

 same issue for me,  intermittent access, poor bandwidth, no connection
 at all with some access points. please let me know how i can be of help
 (please give me very clear instructions...)

 best,
 g.

 Dell XPS13 with Ubuntu 14.04

 $ uname -a
 Linux drogo 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 UTC 2014
 x86_64 x86_64 x86_64 GNU/Linux

 $ lshw
 ...
*-network
 description: Wireless interface
 product: Wireless 7260
 vendor: Intel Corporation
 physical id: 0
 bus info: pci@:02:00.0
 logical name: wlan0
 version: 6b
 serial: e8:b1:fc:41:49:e3
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list
 ethernet physical wireless
 configuration: broadcast=yes driver=iwlwifi
 driverversion=3.13.0-39-generic firmware=22.24.8.0 ip=192.168.1.132
 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn
 resources: irq:59 memory:f040-f0401fff
 ...

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1315221

 Title:
   8086:08b1 (rev 6b) [Dell XPS 13 9333] iwlwifi regularly loses
   connection/becomes unusable on Intel 7260

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


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

Title:
  8086:08b1 (rev 6b) [Dell XPS 13 9333] iwlwifi regularly loses
  connection/becomes unusable on Intel 7260

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  My Intel 7260 network card regularly shows very poor performance
  and/or loses its connection entirely. On several occasions I have been
  unable to reestablish an association with the AP without rebooting.
  This occurs even if the laptop is within a few feet of the AP. I did
  not have this problem on 12.04 with a quantal backport kernel.

  Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 
6b)
  Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:c470]

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.46
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  Date: Thu May  1 22:59:32 2014
  HibernationDevice: RESUME=/dev/mapper/cswap0
  InstallationDate: Installed on 2014-04-25 (6 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Dell Inc. XPS13 9333
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  elb5375 F pulseaudio
   /dev/snd/controlC0:  elb5375 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/cswap0
  InstallationDate: Installed on 2014-04-25 (94 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Dell Inc. XPS13 9333
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic 
root=/dev/mapper/root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-32-generic N/A
   linux-backports-modules-3.13.0-32-generic  N/A
   linux-firmware 1.127.5
  Tags:  trusty
  Uname: Linux 3.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/19/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 

[Kernel-packages] [Bug 1372967] Re: Touchpad not working and not recognized

2014-09-24 Thread Davide
i need to download the *image*amd64.deb  and install it right? nothing
else? im on 64bit

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

Title:
  Touchpad not working and not recognized

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Even during installation the touchpad did not work, after installing
  ubuntu 14.04 i tried to use xinput list but this is the result:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Fujitsu FUJ02E3 id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Fujitsu FUJ02B1 id=9[slave  
keyboard (3)]
  ↳ Power Buttonid=10   [slave  
keyboard (3)]
  ↳ FJ Camera   id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)

  
  The SynPS/2 Synaptics TouchPad is not present anywhere.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-36-generic 3.13.0-36.63
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dquaglio   1524 F pulseaudio
   /dev/snd/controlC0:  dquaglio   1524 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Sep 23 16:19:31 2014
  HibernationDevice: RESUME=UUID=40f80e5e-5fc1-40a8-b253-836e81028831
  InstallationDate: Installed on 2014-09-23 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: FUJITSU LIFEBOOK A544
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic.efi.signed 
root=UUID=04575c6d-aff9-4da6-8b8b-f7cdfdb0a5a4 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-36-generic N/A
   linux-backports-modules-3.13.0-36-generic  N/A
   linux-firmware 1.127.6
  SourcePackage: linux
  StagingDrivers: rts5139
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2013
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.13
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.13:bd11/18/2013:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU

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

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


[Kernel-packages] [Bug 1372967] Re: Touchpad not working and not recognized

2014-09-24 Thread Davide
Tested but the problem is still here...how do i add the tag that you
mentioned?

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

Title:
  Touchpad not working and not recognized

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Even during installation the touchpad did not work, after installing
  ubuntu 14.04 i tried to use xinput list but this is the result:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Fujitsu FUJ02E3 id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Fujitsu FUJ02B1 id=9[slave  
keyboard (3)]
  ↳ Power Buttonid=10   [slave  
keyboard (3)]
  ↳ FJ Camera   id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)

  
  The SynPS/2 Synaptics TouchPad is not present anywhere.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-36-generic 3.13.0-36.63
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dquaglio   1524 F pulseaudio
   /dev/snd/controlC0:  dquaglio   1524 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Sep 23 16:19:31 2014
  HibernationDevice: RESUME=UUID=40f80e5e-5fc1-40a8-b253-836e81028831
  InstallationDate: Installed on 2014-09-23 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: FUJITSU LIFEBOOK A544
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic.efi.signed 
root=UUID=04575c6d-aff9-4da6-8b8b-f7cdfdb0a5a4 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-36-generic N/A
   linux-backports-modules-3.13.0-36-generic  N/A
   linux-firmware 1.127.6
  SourcePackage: linux
  StagingDrivers: rts5139
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2013
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.13
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.13:bd11/18/2013:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU

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

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


[Kernel-packages] [Bug 1372967] [NEW] Touchpad not working and not recognized

2014-09-23 Thread Davide
Public bug reported:

Even during installation the touchpad did not work, after installing
ubuntu 14.04 i tried to use xinput list but this is the result:

⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Fujitsu FUJ02E3   id=7[slave  keyboard (3)]
↳ Video Bus id=8[slave  keyboard (3)]
↳ Fujitsu FUJ02B1   id=9[slave  keyboard (3)]
↳ Power Button  id=10   [slave  keyboard (3)]
↳ FJ Camera id=12   [slave  keyboard (3)]
↳ AT Translated Set 2 keyboard  id=13   [slave  keyboard (3)


The SynPS/2 Synaptics TouchPad is not present anywhere.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-36-generic 3.13.0-36.63
ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
Uname: Linux 3.13.0-36-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  dquaglio   1524 F pulseaudio
 /dev/snd/controlC0:  dquaglio   1524 F pulseaudio
CurrentDesktop: Unity
Date: Tue Sep 23 16:19:31 2014
HibernationDevice: RESUME=UUID=40f80e5e-5fc1-40a8-b253-836e81028831
InstallationDate: Installed on 2014-09-23 (0 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
MachineType: FUJITSU LIFEBOOK A544
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic.efi.signed 
root=UUID=04575c6d-aff9-4da6-8b8b-f7cdfdb0a5a4 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-36-generic N/A
 linux-backports-modules-3.13.0-36-generic  N/A
 linux-firmware 1.127.6
SourcePackage: linux
StagingDrivers: rts5139
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/18/2013
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.13
dmi.board.name: FJNBB35
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.13:bd11/18/2013:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
dmi.product.name: LIFEBOOK A544
dmi.sys.vendor: FUJITSU

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


** Tags: amd64 apport-bug staging trusty

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

Title:
  Touchpad not working and not recognized

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Even during installation the touchpad did not work, after installing
  ubuntu 14.04 i tried to use xinput list but this is the result:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Fujitsu FUJ02E3 id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Fujitsu FUJ02B1 id=9[slave  
keyboard (3)]
  ↳ Power Buttonid=10   [slave  
keyboard (3)]
  ↳ FJ Camera   id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)

  
  The SynPS/2 Synaptics TouchPad is not present anywhere.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-36-generic 3.13.0-36.63
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dquaglio   1524 F pulseaudio
   /dev/snd/controlC0:  dquaglio   1524 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Sep 23 16:19:31 2014
  HibernationDevice: RESUME=UUID=40f80e5e-5fc1-40a8-b253-836e81028831
  InstallationDate: Installed on 2014-09-23 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: FUJITSU LIFEBOOK A544
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 1314198] Re: [Asus X550LC] Touchpad not Recognized in ubuntu 14.04

2014-09-23 Thread Davide
I have the same problem, with Fujitsu A-544 , with xinput list it s not
show any touchpad

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

Title:
  [Asus X550LC] Touchpad not Recognized in ubuntu 14.04

Status in The Linux Kernel:
  New
Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  I am facing a problem of touchpad not recognized on Asus X550LC. It notes in 
dmesg:
  i8042: PNP: PS/2 Controller [PNP030b:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: 
boot/vmlinuz-3.13.0-24-generic]
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nishu  1781 F pulseaudio
   /dev/snd/controlC0:  nishu  1781 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Apr 30 00:03:34 2014
  InstallationDate: Installed on 2014-04-29 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: ASUSTeK COMPUTER INC. X550LC
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_IN
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed 
root=UUID=5f8f534f-ba63-44e9-b334-a982524fdce1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550LC.402
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550LC
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550LC.402:bd11/19/2013:svnASUSTeKCOMPUTERINC.:pnX550LC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550LC
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1314198] Re: [Asus X550LC] Touchpad not Recognized in ubuntu 14.04

2014-09-09 Thread Davide
** Also affects: linux
   Importance: Undecided
   Status: New

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

Title:
  [Asus X550LC] Touchpad not Recognized in ubuntu 14.04

Status in The Linux Kernel:
  New
Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  I am facing a problem of touchpad not recognized on Asus X550LC. It notes in 
dmesg:
  i8042: PNP: PS/2 Controller [PNP030b:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: 
boot/vmlinuz-3.13.0-24-generic]
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nishu  1781 F pulseaudio
   /dev/snd/controlC0:  nishu  1781 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Apr 30 00:03:34 2014
  InstallationDate: Installed on 2014-04-29 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: ASUSTeK COMPUTER INC. X550LC
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_IN
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed 
root=UUID=5f8f534f-ba63-44e9-b334-a982524fdce1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550LC.402
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550LC
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550LC.402:bd11/19/2013:svnASUSTeKCOMPUTERINC.:pnX550LC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550LC
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1323426] Re: HP Z8000 bluetooth mouse

2014-08-31 Thread Davide Monge
Confimed problems on Lenovo T540p and Ubuntustudio 14.04.1
Confirmed problems on a Sitecom CN-524 (CSR8510 A10) Dongle

Problems explained shortly: device HP Z8000 connects correctly, at the
mouse mouvement the pointer move crazy on the screen and desktop freeze
(xfwm4)

The image refers to T540p paired and trusted.

** Attachment added: Z8000-mouse-comm-problems.png
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1323426/+attachment/4191536/+files/Z8000-mouse-comm-problems.png

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

Title:
  HP Z8000 bluetooth mouse

Status in “bluez” package in Ubuntu:
  Confirmed

Bug description:
  This mouse is a HID over GAT recent HP low power mouse.

  It  is recognized as ALL types bluetooth peripherals not as a mouse!

  The mouse at the end of the installation process (automatic pin
  selection) results as PAIRED  but the connection option is not
  available in the bluetooth setting dialog.

  UBUNTU is last 14.04 full updated at filing bug time.

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

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


[Kernel-packages] [Bug 1315221] Re: 8086:08b1 (rev 6b) [Dell XPS 13 9333] iwlwifi regularly loses connection/becomes unusable on Intel 7260

2014-08-01 Thread Davide
In my case (Ubuntu 14.04 on dell xps13 Sputnik, kernel 3.13) the wifi
performance substantially degraded after the recent linux-firmware
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/1315221

Title:
  8086:08b1 (rev 6b) [Dell XPS 13 9333] iwlwifi regularly loses
  connection/becomes unusable on Intel 7260

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  My Intel 7260 network card regularly shows very poor performance
  and/or loses its connection entirely. On several occasions I have been
  unable to reestablish an association with the AP without rebooting.
  This occurs even if the laptop is within a few feet of the AP. I did
  not have this problem on 12.04 with a quantal backport kernel.

  Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 
6b)
  Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:c470]

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.46
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  Date: Thu May  1 22:59:32 2014
  HibernationDevice: RESUME=/dev/mapper/cswap0
  InstallationDate: Installed on 2014-04-25 (6 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Dell Inc. XPS13 9333
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  elb5375 F pulseaudio
   /dev/snd/controlC0:  elb5375 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/cswap0
  InstallationDate: Installed on 2014-04-25 (94 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Dell Inc. XPS13 9333
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic 
root=/dev/mapper/root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-32-generic N/A
   linux-backports-modules-3.13.0-32-generic  N/A
   linux-firmware 1.127.5
  Tags:  trusty
  Uname: Linux 3.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/19/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd03/19/2014:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 683133] Re: Keyboard backlight does not work on Toshiba Satellite M645

2014-03-09 Thread Davide Depau
Bump.
Still having this problem in trusty. Pressing Fn+Z shows a volume-like 
notification but nothing happens.
Please tell me what do I have to do to collect more info about the 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/683133

Title:
  Keyboard backlight does not work on Toshiba Satellite M645

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Disabling ACPI causes the keyboard backlight to work perfectly. However, this 
has the unfortunate side effect of disabling monitor brightness control and 
suspend ability (and likely other things). Is there a way we can just disable 
ACPI for the keyboard alone?
  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC259 Analog [ALC259 Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mattw  1904 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xb570 irq 49'
     Mixer name : 'Intel IbexPeak HDMI'
     Components : 'HDA:10ec0269,1179fd88,00100100 
HDA:80862804,1179ff00,0010'
     Controls  : 21
     Simple ctrls  : 10
  DistroRelease: Ubuntu 10.10
  HibernationDevice: RESUME=UUID=da79a006-ae30-436b-99f3-d819cb137a4f
  InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1)
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0bda:5801 Realtek Semiconductor Corp.
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TOSHIBA Satellite M645
  Package: linux (not installed)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-23-generic 
root=UUID=e39ee5fb-8bb0-462b-b556-95846f86c3cc ro
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.35-23.40-generic 2.6.35.7
  Regression: No
  RelatedPackageVersions: linux-firmware 1.38
  Reproducible: Yes
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags: maverick kernel-uncat needs-upstream-testing
  Uname: Linux 2.6.35-23-generic i686
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 07/05/10
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NBQAA
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 9
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.30:bd07/05/10:svnTOSHIBA:pnSatelliteM645:pvrPSMPBU-00N001:rvnTOSHIBA:rnNBQAA:rvr1.00:cvnTOSHIBA:ct9:cvrN/A:
  dmi.product.name: Satellite M645
  dmi.product.version: PSMPBU-00N001
  dmi.sys.vendor: TOSHIBA

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

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


Re: [Kernel-packages] [Bug 1203286] Re: [HP Probook 4510s] System fan not working correctly after suspend

2013-09-05 Thread Davide Depau
I currently have the development version. I will do that tomorrow or the
next week as at the moment there is a thunderstorm and my internet
connection is very unstable, and I must use my (limited) mobile broadband.
Sorry.


On Thu, Sep 5, 2013 at 1:25 PM, Christopher M. Penalver 
christopher.m.penal...@gmail.com wrote:

 Davide Depau, could you please confirm this issue exists with the latest
 development release of Ubuntu? ISO images are available from
 http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains,
 could you please run the following command in the development release
 from a Terminal (Applications-Accessories-Terminal), as it will
 automatically gather and attach updated debug information to this
 report:

 apport-collect -p linux replace-with-bug-number

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

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1203286

 Title:
   [HP Probook 4510s] System fan not working correctly after suspend

 Status in The Linux Kernel:
   Unknown
 Status in “linux” package in Ubuntu:
   Incomplete

 Bug description:
   I noticed that since Natty or Oneiric (I don't remember precisely) I
 have a strange behaviour: after resuming the PC from suspend, the fan
 starts rotating too fast, even if the PC is not hot. When I first had the
 problem, I could solve it by (dis)connecting the power cable. In latest
 versions of Ubuntu, maybe since Precise, this workaround doesn't work
 anymore.
   I have the mainline kernel downloaded from here:
 http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc1-saucy/

   I attached some logs, I don't know what else I can provide to help
   troubleshooting this bug.

   I'm using Ubuntu 13.10 amd64.

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



-- 
Davide
http://bashkaraoke.altervista.org

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

Title:
  [HP Probook 4510s] System fan not working correctly after suspend

Status in The Linux Kernel:
  Unknown
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I noticed that since Natty or Oneiric (I don't remember precisely) I have a 
strange behaviour: after resuming the PC from suspend, the fan starts rotating 
too fast, even if the PC is not hot. When I first had the problem, I could 
solve it by (dis)connecting the power cable. In latest versions of Ubuntu, 
maybe since Precise, this workaround doesn't work anymore.
  I have the mainline kernel downloaded from here: 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc1-saucy/

  I attached some logs, I don't know what else I can provide to help
  troubleshooting this bug.

  I'm using Ubuntu 13.10 amd64.

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

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


[Kernel-packages] [Bug 1203286] Re: [HP Probook 4510s] System fan not working correctly after suspend

2013-07-20 Thread Davide Depau
This is not a duplicate of 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1197311
That is another DIFFERENT bug I reported. I also included information about 
this problem but they told me to file a new bug.

Daniel Letzeisen wrote:
 You may want to look at: 
 https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.17/+bug/77370
It's different: the fan is not just always on (it is always on in any case 
because I set an option in the EFI settings); it just starts rotating very very 
fast; I've never seen it rotating so fast, even if the PC was very hot; it 
happened that the PC turned off because it was too hot and the kernel wasn't 
able to make the fan rotate at the right speed.

But after a suspend the sound is like a vacuum machine! :)

** Tags removed: needs-kernel-logs needs-upstream-testing

** Tags added: needs-kernel-logs

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

Title:
  [HP Probook 4510s] System fan not working correctly after suspend

Status in The Linux Kernel:
  Unknown
Status in “linux” package in Ubuntu:
  New

Bug description:
  I noticed that since Natty or Oneiric (I don't remember precisely) I have a 
strange behaviour: after resuming the PC from suspend, the fan starts rotating 
too fast, even if the PC is not hot. When I first had the problem, I could 
solve it by (dis)connecting the power cable. In latest versions of Ubuntu, 
maybe since Precise, this workaround doesn't work anymore.
  I have the mainline kernel downloaded from here: 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc1-saucy/

  I attached some logs, I don't know what else I can provide to help
  troubleshooting this bug.

  I'm using Ubuntu 13.10 amd64.

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

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


[Kernel-packages] [Bug 1197311] Re: [Hewlett-Packard HP ProBook 4510s] suspend/resume failure

2013-07-18 Thread Davide Depau
It happens also with the new 3.11 kernel. I noticed that I can force
this behavior by opening and closing the lid until it suspends. Also I
noticed that it always wakes up when removing/attaching the power cable,
that sometimes it wakes up automatically after about 2-3 minutes and
that sometimes, after it wakes up, it suspends again, unless the system
has finished shutting down and has sent the shutdown signal.

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

Title:
  [Hewlett-Packard HP ProBook 4510s] suspend/resume failure

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Some times, when I turn off the laptop, I close the lid and it goes to
  sleep without finishing shutting down. After a few minutes, it turns
  automatically on itself and finishes shutting down. When I turn on the
  PC again, it shows an Apport message as soon as I log in.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.10.0-1-generic 3.10.0-1.8
  ProcVersionSignature: Ubuntu 3.10.0-1.8-generic 3.10.0-rc7
  Uname: Linux 3.10.0-1-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.10.2-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  davideddu   2181 F pulseaudio
   /dev/snd/seq:timidity   1374 F timidity
  Date: Tue Jul  2 22:35:10 2013
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=7759bd56-6a0e-48dc-9bc9-730d437b7645
  InstallationDate: Installed on 2013-06-20 (12 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130618)
  InterpreterPath: /usr/bin/python3.3
  MachineType: Hewlett-Packard HP ProBook 4510s
  MarkForUpload: True
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-1-generic 
root=UUID=fd4bd625-a903-4f9b-8a23-5ab28f4553af ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  RelatedPackageVersions:
   linux-restricted-modules-3.10.0-1-generic N/A
   linux-backports-modules-3.10.0-1-generic  N/A
   linux-firmware1.110
  SourcePackage: linux
  Title: [Hewlett-Packard HP ProBook 4510s] suspend/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 12/09/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PZI Ver. F.20
  dmi.board.name: 3072
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 24.0F
  dmi.chassis.asset.tag: CNU0114QT2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PZIVer.F.20:bd12/09/2011:svnHewlett-Packard:pnHPProBook4510s:pvrF.20:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0F:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4510s
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard

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

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