[Kernel-packages] [Bug 1753371] [NEW] Ubuntu 18.04 - Kernel crash on nvme subsystem-reset /dev/nvme0 (Bolt / NVMe)

2018-03-04 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

== Comment: #1 - NAVEED A. UPPINANGADY SALIH  -
2018-02-25 23:45:13 ==


== Comment: #6 - Wen Xiong  - 2018-02-27 10:41:23 ==
hi Naveed,

nvme subsystem-reset calls EEH recovery path. Is EEH recovery working
with Bolt on this machine?

Thanks,
Wendy

== Comment: #11 - Wen Xiong  - 2018-03-02 16:03:46 ==
The following patch should fix the issue.

http://lists.infradead.org/pipermail/linux-
nvme/2018-February/015745.html

It should be accepted into community soon. Keith has agreed to queue up
for 4.16.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-165124 severity-critical 
targetmilestone-inin1804
-- 
Ubuntu 18.04 - Kernel crash on nvme subsystem-reset /dev/nvme0 (Bolt / NVMe)
https://bugs.launchpad.net/bugs/1753371
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 1743529] Re: Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic -not syncing: Out of memory message when crash is triggered.

2018-03-04 Thread Mathew Hodson
** No longer affects: linux (Ubuntu)

** No longer affects: linux (Ubuntu Xenial)

** No longer affects: linux (Ubuntu Artful)

** No longer affects: linux (Ubuntu Bionic)

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

Title:
  Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic
  -not syncing: Out of memory message when crash is triggered.

Status in The Ubuntu-power-systems project:
  Triaged
Status in kexec-tools package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Xenial:
  New
Status in kexec-tools source package in Artful:
  New
Status in kexec-tools source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - INDIRA P. JOGA
  Problem Description:
  ===
  System hung with kernel panic Kernel panic - not syncing: Out of memory 
message when crash is triggered

  Steps to re-create:
  ==
  > Installed ubuntu1804 daily build on Witherspoon test system
  root@whip:~# uname -a
  Linux whip 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
  root@whip:~# uname -r
  4.13.0-17-generic

  > root@whip:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   507G2.0G504G 19M728M
503G
  Swap:  2.0G  0B2.0G

  
  > Edited the grub /etc/default/grub.d/kexec-tools.cfg file and set the crash 
kernel parameter=4096M

  > Updated grub using update-grub command and reboot system.

  cat root@whip:~# cat /proc/cmdline
  root=UUID=46c6aa02-8215-44cc-b3fc-0bc79c3c8815 ro splash quiet 
crashkernel=4096M

  > kdump status before triggering crash

  root@whip:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.13.0-17-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.13.0-17-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=46c6aa02-8215-44cc-b3fc-0bc79c3c8815 ro splash quiet 
irqpoll noirqdistrib nr_cpus=1 nousb systemd.unit=kdump-tools.service 
ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img 
/var/lib/kdump/vmlinuz

  root@whip:~# kdump-config status
  current state   : ready to kdump

  >  Enabled sysrq
  root@whip:~# sysctl -w kernel.sysrq=1
  kernel.sysrq = 1

  > Triggered crash and it hangs with kernel panic- OOM message as below

  root@whip:~# echo c > /proc/sysrq-trigger
  [   85.731415] sysrq: SysRq : Trigger a crash
  [   85.731472] Unable to handle kernel paging request for data at address 
0x
  [   85.731584] Faulting instruction address: 0xc078f588
  [   85.731670] Oops: Kernel access of bad area, sig: 11 [#1]
  [   85.731744] SMP NR_CPUS=2048 
  [   85.731745] NUMA 
  [   85.731790] PowerNV
  [   85.731853] Modules linked in: rpcsec_gss_krb5 nfsv4 nfs fscache sctp_diag 
sctp dccp_diag dccp tcp_diag udp_diag raw_diag inet_diag unix_diag 
af_packet_diag netlink_diag binfmt_misc vmx_crypto crct10dif_vpmsum ofpart 
cmdlinepart idt_89hpesx powernv_flash ipmi_powernv opal_prd ibmpowernv mtd 
ipmi_devintf ipmi_msghandler at24 uio_pdrv_genirq uio dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua nfsd auth_rpcgss sch_fq_codel nfs_acl lockd grace 
sunrpc ip_tables x_tables autofs4 btrfs xor raid6_pq nouveau bnx2x ast 
i2c_algo_bit ttm drm_kms_helper mdio libcrc32c crc32c_vpmsum mlx5_core 
syscopyarea sysfillrect sysimgblt fb_sys_fops tg3 drm ahci mlxfw libahci nvme 
devlink nvme_core
  [   85.732704] CPU: 10 PID: 4316 Comm: bash Not tainted 4.13.0-17-generic 
#20-Ubuntu
  [   85.732764] task: c03fcb141700 task.stack: c03fc2374000
  [   85.732858] NIP: c078f588 LR: c07904b8 CTR: 
c078f560
  [   85.732977] REGS: c03fc23779f0 TRAP: 0300   Not tainted  
(4.13.0-17-generic)
  [   85.733066] MSR: 90009033 
  [   85.733075]   CR: 2842  XER: 2004
  [   85.733201] CFAR: c07904b4 DAR:  DSISR: 4200 
SOFTE: 1 
  [   85.733201] GPR00: c07904b8 c03fc2377c70 c15f6000 
0063 
  [   85.733201] GPR04: c03feedfade8 c03feee12068 90009033 
000a 
  [   85.733201] GPR08: 0007 0001  
90001003 
  [   85.733201] GPR12: c078f560 c7a66900 10180df8 
10189e30 
  [   85.733201] GPR16: 10189ea8 10151210 1018bd58 
1018de48 
  [   85.733201] GPR20: 321168d8 0001 10164590 
10163bb0 
  [   85.733201] GPR24: 7fffcfa6e7d4 7fffcfa6e7d0 c14fa570 
0002 
  [   85.733201] GPR2

[Kernel-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18

2018-03-04 Thread Mathew Hodson
** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Medium

** Changed in: network-manager (Ubuntu Artful)
   Importance: Undecided => Medium

** No longer affects: linux (Ubuntu Artful)

** No longer affects: linux (Ubuntu)

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Artful:
  New

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock. Adding a sleep before calling nmcli fixes the issue.

  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  
  [Test Case]

  2.1. Download network-manager package source code
  $ apt-get source network-manager

  2.2. Run killswitches-no-urfkill testcase
  $ cd network-manager-1.8.4
  $ sudo ./debian/tests/killswitches-no-urfkill

  
  [Regression Potential]

  No regression potential. The fix touches only the testcase shipped
  with the source package and it doesn't change the binary package. The
  sleep time added is very small, so no possibility of causing testcase
  timeout.

  
  [Other Info]

  On ppc64el architecture, it was observed that a fix for systemd is
  also needed (see bug 1734908) for the testcase to be successful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1733321/+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 1683445] Re: E6430 brightness control not working

2018-03-04 Thread Mathew Hodson
** No longer affects: linux (Ubuntu)

** Project changed: linux => nouveau

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

Title:
  E6430 brightness control not working

Status in GNOME Settings Daemon:
  Fix Released
Status in Nouveau Xorg driver:
  Won't Fix
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-settings-daemon source package in Zesty:
  Fix Released
Status in unity-settings-daemon source package in Zesty:
  Triaged

Bug description:
  Impact
  --
  It looks like GNOME's brightness control simply used the first backlight 
device it saw instead of one currently in use. This meant that the brightness 
control would not work on some computers with multiple GPUs.

  Test Case
  -
  From Ubuntu GNOME 17.04 on a dual-GPU computer, install the update.
  Restart.
  Does the brightness control now work correctly?

  Regression Potential
  
  This looks like a minimal fix for this issue. It was accepted as part of 
gnome-settings-daemon 3.24.2 which all GNOME 3.24 distros  will be upgrading to.

  Original Bug Report
  ---
  The Dell E6430 with Nvidia Optimus enables in BIOS, using the Open Source 
Nouveau driver shows the brightness slider moving but does not affect the 
brightness.

  When using the kernel boot option acpi_backlight=vendor , the
  brightness control works.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2081 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon Apr 17 20:00:56 2017
  HibernationDevice: RESUME=UUID=66528b53-0f42-4043-9ff8-da8f86036be6
  InstallationDate: Installed on 2017-04-10 (7 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Dell Inc. Latitude E6430
  ProcFB:
   0 nouveaufb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=4e08c33d-f8cf-4159-a559-a0463d67b96c ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 0H3MT5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd01/18/2016:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn0H3MT5:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6430
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1683445/+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 1753298] ProcCpuinfoMinimal.txt

2018-03-04 Thread iBART
apport information

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

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

Title:
  audio not working, apollo lake 4.16 kernel

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I tried a lot of 4.16 ubuntu kenerls and audio is not working.

  Jumper EZ book v4, Ubuntu 16.04.4.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  Uname: Linux 4.16.0-994-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mich   2171 F pulseaudio
  Date: Sun Mar  4 19:48:50 2018
  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.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: JUMPER2x.P8.WP313R.NHNAUHN05
  dmi.board.asset.tag: Default string
  dmi.board.name: P313R
  dmi.board.vendor: INET
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJUMPER2x.P8.WP313R.NHNAUHN05:bd09/30/2017:svnJumper:pnEZbook:pvrDefaultstring:rvnINET:rnP313R:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: EZbook
  dmi.product.version: Default string
  dmi.sys.vendor: Jumper
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 
2017-11-05T18:46:40.564172
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  PackageArchitecture: amd64
  Tags:  xenial
  Uname: Linux 4.16.0-994-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753298/+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 1753298] ProcEnviron.txt

2018-03-04 Thread iBART
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1753298/+attachment/5069538/+files/ProcEnviron.txt

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

Title:
  audio not working, apollo lake 4.16 kernel

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I tried a lot of 4.16 ubuntu kenerls and audio is not working.

  Jumper EZ book v4, Ubuntu 16.04.4.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  Uname: Linux 4.16.0-994-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mich   2171 F pulseaudio
  Date: Sun Mar  4 19:48:50 2018
  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.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: JUMPER2x.P8.WP313R.NHNAUHN05
  dmi.board.asset.tag: Default string
  dmi.board.name: P313R
  dmi.board.vendor: INET
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJUMPER2x.P8.WP313R.NHNAUHN05:bd09/30/2017:svnJumper:pnEZbook:pvrDefaultstring:rvnINET:rnP313R:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: EZbook
  dmi.product.version: Default string
  dmi.sys.vendor: Jumper
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 
2017-11-05T18:46:40.564172
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  PackageArchitecture: amd64
  Tags:  xenial
  Uname: Linux 4.16.0-994-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753298/+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 1753298] JournalErrors.txt

2018-03-04 Thread iBART
apport information

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

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

Title:
  audio not working, apollo lake 4.16 kernel

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I tried a lot of 4.16 ubuntu kenerls and audio is not working.

  Jumper EZ book v4, Ubuntu 16.04.4.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  Uname: Linux 4.16.0-994-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mich   2171 F pulseaudio
  Date: Sun Mar  4 19:48:50 2018
  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.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: JUMPER2x.P8.WP313R.NHNAUHN05
  dmi.board.asset.tag: Default string
  dmi.board.name: P313R
  dmi.board.vendor: INET
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJUMPER2x.P8.WP313R.NHNAUHN05:bd09/30/2017:svnJumper:pnEZbook:pvrDefaultstring:rvnINET:rnP313R:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: EZbook
  dmi.product.version: Default string
  dmi.sys.vendor: Jumper
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 
2017-11-05T18:46:40.564172
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  PackageArchitecture: amd64
  Tags:  xenial
  Uname: Linux 4.16.0-994-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753298/+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 1753298] Re: audio not working, apollo lake 4.16 kernel

2018-03-04 Thread iBART
apport information

** Tags added: apport-collected

** Description changed:

  I tried a lot of 4.16 ubuntu kenerls and audio is not working.
  
  Jumper EZ book v4, Ubuntu 16.04.4.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  Uname: Linux 4.16.0-994-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mich   2171 F pulseaudio
  Date: Sun Mar  4 19:48:50 2018
  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.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: JUMPER2x.P8.WP313R.NHNAUHN05
  dmi.board.asset.tag: Default string
  dmi.board.name: P313R
  dmi.board.vendor: INET
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJUMPER2x.P8.WP313R.NHNAUHN05:bd09/30/2017:svnJumper:pnEZbook:pvrDefaultstring:rvnINET:rnP313R:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: EZbook
  dmi.product.version: Default string
  dmi.sys.vendor: Jumper
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 
2017-11-05T18:46:40.564172
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.15
+ Architecture: amd64
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 16.04
+ Package: pulseaudio 1:8.0-0ubuntu3.8
+ PackageArchitecture: amd64
+ Tags:  xenial
+ Uname: Linux 4.16.0-994-generic x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1753298/+attachment/5069535/+files/Dependencies.txt

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

Title:
  audio not working, apollo lake 4.16 kernel

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I tried a lot of 4.16 ubuntu kenerls and audio is not working.

  Jumper EZ book v4, Ubuntu 16.04.4.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  Uname: Linux 4.16.0-994-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mich   2171 F pulseaudio
  Date: Sun Mar  4 19:48:50 2018
  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.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: JUMPER2x.P8.WP313R.NHNAUHN05
  dmi.board.asset.tag: Default string
  dmi.board.name: P313R
  dmi.board.vendor: INET
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJUMPER2x.P8.WP313R.NHNAUHN05:bd09/30/2017:svnJumper:pnEZbook:pvrDefaultstring:rvnINET:rnP313R:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: EZbook
  dmi.product.version: Default string
  dmi.sys.vendor: Jumper
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 
2017-11-05T18:46:40.564172
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  PackageArchitecture: amd64
  Tags:  xenial
  Uname: Linux 4.16.0-994-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753298/+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 1739765] Re: xt_TCPMSS buffer overflow bug

2018-03-04 Thread Steve Beattie
Sorry, the kernel commit to fix this didn't pick up the launchpad bug number, 
so this bug didn't get auto-closed. It's been addressed in all Ubuntu releases 
e.g. https://usn.ubuntu.com/usn/usn-3583-1/ .
You can see the state at 
https://people.canonical.com/~ubuntu-security/cve/2017/CVE-2017-18017.html.

Thanks again for the report!

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

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

Title:
  xt_TCPMSS buffer overflow bug

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Bug was reported in LKML here: https://lkml.org/lkml/2017/4/2/13
  In few words - corrupted packet might be used to modify memory at router who 
has xt_TCPMSS used as iptables action.
  This is really nasty bug, and can be triggered remotely by malicious person 
on anything that usually use this iptables action (PPPoE/PPTP-enabled ISP or 
VPN provider, for example).
  This bug existed for several years, i guess.
  I waited for a while since April, as it's already pushed to stable, and 
probably all distributions have it updated, so now it's time to do bugreport, 
to make sure it is really fixed everywhere.
  Maybe worth to assign CVE for it?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739765/+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 1751887] Re: The brightness of the screen cannot be adjusted with either the buttons or the slider.

2018-03-04 Thread Kai-Heng Feng
What's the output of `find /sys/class/backlight`?

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

Title:
  The brightness of the screen cannot be adjusted with either the
  buttons or the slider.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Brightness is always at 100% and cannot be adjusted with either the FN
  brightness buttons or the Unity top bar slider.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-36-generic 4.13.0-36.40
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  albertoinet   1199 F pulseaudio
   /dev/snd/controlC0:  albertoinet   1199 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 20:49:16 2018
  HibernationDevice: RESUME=UUID=56535002-bba2-4658-b57f-75ba5bb87d4f
  InstallationDate: Installed on 2018-02-25 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Micro-Star International Co., Ltd. GT72VR 7RD
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi=Linux vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1785IMS.30E
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-1785
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1785IMS.30E:bd10/27/2017:svnMicro-StarInternationalCo.,Ltd.:pnGT72VR7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1785:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:
  dmi.product.family: GT
  dmi.product.name: GT72VR 7RD
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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


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

2018-03-04 Thread AzureRaptor
I see the exact same boot log as Marc Dziadek above, and I can't find
this recorded anywhere on next boot either.

It has been asked before here:  "Is it possible to test 4.15 from
bionic-proposed on xenial?"  Can anyone offer input on this?  I know how
to add xenial's proposed repository; is it safe to just substitute
"bionic" in that line in sources.list?  What else, if anything, might
need to be done to get this kernel working?

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

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

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

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

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

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

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


[Kernel-packages] [Bug 1732056] Re: Touchpad stops working after a few seconds in Lenovo ideapad 320

2018-03-04 Thread Kai-Heng Feng
** Changed in: linux (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: hwe-next
 Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned)

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

Title:
  Touchpad stops working after a few seconds in Lenovo ideapad 320

Status in HWE Next:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Committed
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  === SRU Justifications ===

  [Impact]
  Touchpad freezes after a brief usage.

  [Fix]
  Quote from the commit log:
  "The stale cached value written at the final stage undoes the masking.
  Fix this by re-reading the register before clearing the interrupt.

  I also spotted that the interrupt-clearing code can race against
  amd_gpio_irq_mask() / amd_gpio_irq_unmask(), so add locking there.
  Presumably this race was leading to the loss of interrupts."

  [Test Case]
  Touchpad no longer freezes on ideapad 320-15ABR, a new Dell Latitude and
  a new Dell Inspiron.

  [Regression Potential]
  Low. It limits to AMD laptops

  === Original Bug Report ===

  I have installed ubuntu bionic on a Lenovo ideapad 320. The touchpad
  stops working a few seconds after I log in.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rebeca 1440 F pulseaudio
   /dev/snd/controlC0:  rebeca 1440 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 13 20:03:41 2017
  InstallationDate: Installed on 2017-09-22 (53 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170918)
  MachineType: LENOVO 80XS
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=1e55f665-bd98-4113-9ae8-ec766bfc424f ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-11-14 (0 days ago)
  dmi.bios.date: 05/22/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5QCN16WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15ABR
  dmi.modalias: 
dmi:bvnLENOVO:bvr5QCN16WW:bd05/22/2017:svnLENOVO:pn80XS:pvrLenovoideapad320-15ABR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15ABR:
  dmi.product.family: ideapad 320-15ABR
  dmi.product.name: 80XS
  dmi.product.version: Lenovo ideapad 320-15ABR
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1732056/+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 1734744] Re: OOM killer with kernel 4.4.0-92

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

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

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

Title:
  OOM killer with kernel 4.4.0-92

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

Bug description:
  When putting pressure on a Linux Node in Azure we see OOM killers (similar 
to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842 but not this 
is a different kernel)
  Reverting the kernel to 4.4.0-57 fixes the problem.

  dmesg and kernel.log attached
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 11 15:21 seq
   crw-rw 1 root audio 116, 33 Dec 11 15:21 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic 
root=UUID=512611f4-b05a-4d8a-b743-438b71c5385d ro console=tty1 console=ttyS0 
earlyprintk=ttyS0 rootdelay=300
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-92-generic N/A
   linux-backports-modules-4.4.0-92-generic  N/A
   linux-firmware1.157.13
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images xenial uec-images
  Uname: Linux 4.4.0-92-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/02/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090007
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.uuid: D88904A9-DF88-454F-9F50-7A8DE8964445
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734744/+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 1739678] Re: HDMI audio makes loud popping noises while playing audio

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

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

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

Title:
  HDMI audio makes loud popping noises while playing audio

Status in linux package in Ubuntu:
  Expired

Bug description:
  When playing audio via HDMI, I get very loud pops and/or periods of
  silence. The frequency of this behaviour seems to go way up while
  playing video with a lot of motion, and especially YouTube videos. I
  can reliably reproduce the problem by playing the video
  https://www.youtube.com/watch?v=vt9UZo32KMk and maximising/minimising
  the video size rapidly.

  Testing older kernels, I can reproduce the problem on the linux-
  image-4.10.0-041000rc1-generic from http://kernel.ubuntu.com/~kernel-
  ppa/mainline/, but the previous version, linux-
  image-4.9.71-040971-generic, plays audio without any problems.

  The problem didn't exist on 17.04; it only started happening after I
  upgraded to 17.10. (I know 17.04 had a 4.10 kernel; I'm at a loss to
  explain the difference unless the zesty kernel was patched.)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-21-generic 4.13.0-21.24
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D7p:   tim2079 F...m pulseaudio
   /dev/snd/controlC0:  tim2079 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Dec 21 23:15:07 2017
  HibernationDevice: RESUME=UUID=3f719428-d2ac-4d3b-aa21-db3cd21940a5
  InstallationDate: Installed on 2015-09-30 (812 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: ZOTAC ZBOX-CI527/CI547
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=bfa21ce0-9f16-44a7-9177-80e2a6ef6de8 ro quiet splash pci=noaer
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-20 (61 days ago)
  dmi.bios.date: 03/15/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B331P205
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-CI527/CI547
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 9
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB331P205:bd03/15/2017:svnZOTAC:pnZBOX-CI527/CI547:pvrXX:rvnZOTAC:rnZBOX-CI527/CI547:rvrXX:cvnDefaultstring:ct9:cvrDefaultstring:
  dmi.product.family: NA
  dmi.product.name: ZBOX-CI527/CI547
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739678/+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 1734744] Re: OOM killer with kernel 4.4.0-92

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

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

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

Title:
  OOM killer with kernel 4.4.0-92

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

Bug description:
  When putting pressure on a Linux Node in Azure we see OOM killers (similar 
to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842 but not this 
is a different kernel)
  Reverting the kernel to 4.4.0-57 fixes the problem.

  dmesg and kernel.log attached
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 11 15:21 seq
   crw-rw 1 root audio 116, 33 Dec 11 15:21 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic 
root=UUID=512611f4-b05a-4d8a-b743-438b71c5385d ro console=tty1 console=ttyS0 
earlyprintk=ttyS0 rootdelay=300
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-92-generic N/A
   linux-backports-modules-4.4.0-92-generic  N/A
   linux-firmware1.157.13
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images xenial uec-images
  Uname: Linux 4.4.0-92-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/02/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090007
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.uuid: D88904A9-DF88-454F-9F50-7A8DE8964445
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734744/+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 1739765] Re: xt_TCPMSS buffer overflow bug

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

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

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

Title:
  xt_TCPMSS buffer overflow bug

Status in linux package in Ubuntu:
  Expired

Bug description:
  Bug was reported in LKML here: https://lkml.org/lkml/2017/4/2/13
  In few words - corrupted packet might be used to modify memory at router who 
has xt_TCPMSS used as iptables action.
  This is really nasty bug, and can be triggered remotely by malicious person 
on anything that usually use this iptables action (PPPoE/PPTP-enabled ISP or 
VPN provider, for example).
  This bug existed for several years, i guess.
  I waited for a while since April, as it's already pushed to stable, and 
probably all distributions have it updated, so now it's time to do bugreport, 
to make sure it is really fixed everywhere.
  Maybe worth to assign CVE for it?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739765/+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 1746340] Re: Samsung SSD corruption (fsck needed)

2018-03-04 Thread Kai-Heng Feng
Generally I boot up a live system and run fsck on they block device. A
quick google shows there are several ways to achieve the same thing.

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

Title:
  Samsung SSD corruption (fsck needed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.13.0-21.24-generic 4.13.13

  
  I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 
17.04, which gave me this error after 2 weeks of usage. After that, I installed 
16.04 and used it for MONTHS without any problems, until it produced the same 
error this week. I think it has to do with the ubuntu updates, because I did 
one recently and one today, just before this problem. Could be a coincidence 
though.

  I notice the error when I try to save something on disk and it says me
  that the disk is in read-only mode:

  lz@lz:/var/log$ touch something
  touch: cannot touch 'something': Read-only file system

  
  lz@lz:/var/log$ cat syslog
  Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): 
ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming 
directory block 0

  
  lz@lz:/var/log$ dmesg
  [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.377374] Aborting journal on device nvme0n1p2-8.
  [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
  [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" 
capability=12  capname="net_admin"

  Rebooting the ubuntu will give me a black terminal where I can run
  fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of
  orphaned inodes. The majority of time it boots back to the Ubuntu
  working good, but some times it boots to a broken ubuntu (no images,
  lots of things broken). I have to reinstall ubuntu then.

  Every time I reinstall my Ubuntu, I have to try lots of times until it
  installs without an Input/Output error. When it installs, I can use it
  for some hours without having the problem, but if I run the software
  updates, it ALWAYS crashes and enters in read-only mode, specifically
  in the part that is installing kernel updates.

  I noticed that Ubuntu installs updates automatically when they're for
  security reasons. Could this be the reason my Ubuntu worked for months
  without the problem, but then an update was applied and it broke?

  I thought that this bug was happening:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried
  different nvme_core.default_ps_max_latency_us= combinations, all them
  gave errors. I just changed to 0 and I had no error while using ubuntu
  (however I didn't test for a long time) but I still had the error
  after trying to update my ubuntu.

  My Samsung 512gb SSD is:

  SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q

  on a Razer Blade Stealth.

  I also asked this on ask ubuntu, without success:
  https://askubuntu.com/questions/998471/razer-blade-stealth-disk-
  corruption-fsck-needed-probably-samsung-ssd-bug-afte

  Please help me, as I need this computer to work on lots of things :c
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lz 1088 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2018-01-30 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Razer Blade Stealth
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)

2018-03-04 Thread Lucas Zanella
The next time it happen I will post the full dmesg. But even my first
message (#1):

Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device
nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat:
checksumming directory block 0

cites EXT-4 errors. It's always been like that, nothing changed.

I need to fsck the rootfs now or when the error happens again? And how
should I do 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/1746340

Title:
  Samsung SSD corruption (fsck needed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.13.0-21.24-generic 4.13.13

  
  I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 
17.04, which gave me this error after 2 weeks of usage. After that, I installed 
16.04 and used it for MONTHS without any problems, until it produced the same 
error this week. I think it has to do with the ubuntu updates, because I did 
one recently and one today, just before this problem. Could be a coincidence 
though.

  I notice the error when I try to save something on disk and it says me
  that the disk is in read-only mode:

  lz@lz:/var/log$ touch something
  touch: cannot touch 'something': Read-only file system

  
  lz@lz:/var/log$ cat syslog
  Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): 
ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming 
directory block 0

  
  lz@lz:/var/log$ dmesg
  [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.377374] Aborting journal on device nvme0n1p2-8.
  [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
  [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" 
capability=12  capname="net_admin"

  Rebooting the ubuntu will give me a black terminal where I can run
  fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of
  orphaned inodes. The majority of time it boots back to the Ubuntu
  working good, but some times it boots to a broken ubuntu (no images,
  lots of things broken). I have to reinstall ubuntu then.

  Every time I reinstall my Ubuntu, I have to try lots of times until it
  installs without an Input/Output error. When it installs, I can use it
  for some hours without having the problem, but if I run the software
  updates, it ALWAYS crashes and enters in read-only mode, specifically
  in the part that is installing kernel updates.

  I noticed that Ubuntu installs updates automatically when they're for
  security reasons. Could this be the reason my Ubuntu worked for months
  without the problem, but then an update was applied and it broke?

  I thought that this bug was happening:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried
  different nvme_core.default_ps_max_latency_us= combinations, all them
  gave errors. I just changed to 0 and I had no error while using ubuntu
  (however I didn't test for a long time) but I still had the error
  after trying to update my ubuntu.

  My Samsung 512gb SSD is:

  SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q

  on a Razer Blade Stealth.

  I also asked this on ask ubuntu, without success:
  https://askubuntu.com/questions/998471/razer-blade-stealth-disk-
  corruption-fsck-needed-probably-samsung-ssd-bug-afte

  Please help me, as I need this computer to work on lots of things :c
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lz 1088 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelea

[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)

2018-03-04 Thread Kai-Heng Feng
Again, can you attach full dmesg?
Because the message is not about NVMe, but EXT4.

Please fsck the rootfs before any further testing.

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

Title:
  Samsung SSD corruption (fsck needed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.13.0-21.24-generic 4.13.13

  
  I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 
17.04, which gave me this error after 2 weeks of usage. After that, I installed 
16.04 and used it for MONTHS without any problems, until it produced the same 
error this week. I think it has to do with the ubuntu updates, because I did 
one recently and one today, just before this problem. Could be a coincidence 
though.

  I notice the error when I try to save something on disk and it says me
  that the disk is in read-only mode:

  lz@lz:/var/log$ touch something
  touch: cannot touch 'something': Read-only file system

  
  lz@lz:/var/log$ cat syslog
  Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): 
ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming 
directory block 0

  
  lz@lz:/var/log$ dmesg
  [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.377374] Aborting journal on device nvme0n1p2-8.
  [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
  [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" 
capability=12  capname="net_admin"

  Rebooting the ubuntu will give me a black terminal where I can run
  fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of
  orphaned inodes. The majority of time it boots back to the Ubuntu
  working good, but some times it boots to a broken ubuntu (no images,
  lots of things broken). I have to reinstall ubuntu then.

  Every time I reinstall my Ubuntu, I have to try lots of times until it
  installs without an Input/Output error. When it installs, I can use it
  for some hours without having the problem, but if I run the software
  updates, it ALWAYS crashes and enters in read-only mode, specifically
  in the part that is installing kernel updates.

  I noticed that Ubuntu installs updates automatically when they're for
  security reasons. Could this be the reason my Ubuntu worked for months
  without the problem, but then an update was applied and it broke?

  I thought that this bug was happening:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried
  different nvme_core.default_ps_max_latency_us= combinations, all them
  gave errors. I just changed to 0 and I had no error while using ubuntu
  (however I didn't test for a long time) but I still had the error
  after trying to update my ubuntu.

  My Samsung 512gb SSD is:

  SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q

  on a Razer Blade Stealth.

  I also asked this on ask ubuntu, without success:
  https://askubuntu.com/questions/998471/razer-blade-stealth-disk-
  corruption-fsck-needed-probably-samsung-ssd-bug-afte

  Please help me, as I need this computer to work on lots of things :c
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lz 1088 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2018-01-30 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Razer Blade Stealth
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_

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

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

apport-collect 1753298

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

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

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

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

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

Title:
  audio not working, apollo lake 4.16 kernel

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I tried a lot of 4.16 ubuntu kenerls and audio is not working.

  Jumper EZ book v4, Ubuntu 16.04.4.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  Uname: Linux 4.16.0-994-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mich   2171 F pulseaudio
  Date: Sun Mar  4 19:48:50 2018
  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.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: JUMPER2x.P8.WP313R.NHNAUHN05
  dmi.board.asset.tag: Default string
  dmi.board.name: P313R
  dmi.board.vendor: INET
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJUMPER2x.P8.WP313R.NHNAUHN05:bd09/30/2017:svnJumper:pnEZbook:pvrDefaultstring:rvnINET:rnP313R:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: EZbook
  dmi.product.version: Default string
  dmi.sys.vendor: Jumper
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 
2017-11-05T18:46:40.564172

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753298/+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 1753298] Re: audio not working, apollo lake 4.16 kernel

2018-03-04 Thread Kai-Heng Feng
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  audio not working, apollo lake 4.16 kernel

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I tried a lot of 4.16 ubuntu kenerls and audio is not working.

  Jumper EZ book v4, Ubuntu 16.04.4.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  Uname: Linux 4.16.0-994-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mich   2171 F pulseaudio
  Date: Sun Mar  4 19:48:50 2018
  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.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: JUMPER2x.P8.WP313R.NHNAUHN05
  dmi.board.asset.tag: Default string
  dmi.board.name: P313R
  dmi.board.vendor: INET
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJUMPER2x.P8.WP313R.NHNAUHN05:bd09/30/2017:svnJumper:pnEZbook:pvrDefaultstring:rvnINET:rnP313R:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: EZbook
  dmi.product.version: Default string
  dmi.sys.vendor: Jumper
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 
2017-11-05T18:46:40.564172

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753298/+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 1753346] Status changed to Confirmed

2018-03-04 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  AMD 7 1800X system (Dell Inspiron 5675) randomly freezes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is happening every day or so.  I cannot see anything in the
  kern.log or syslog that give me a clue on where/what the issue might.
  I was using Ubuntu 17.10 earlier and upgraded to Ubuntu 18.04 on
  3/3/2018, since I thought kernel 4.15 might have better support for
  the ryzen 7 and also maybe amdgpu for the radeon 580 might be newer.
  I have removed most external devices except for networking and HDMI
  and audio out.

  Attached a tarball of info, although I believe that since I used
  'ubuntu-bug linux' command, the information might be duplicated,
  apologize for any extra attachments.

  $ ls -l dell-5675-sysinfo/
  total 168
  -rw-r--r-- 1 pss pss 83139 Mar  4 19:47 dmesg
  -rw-r--r-- 1 pss pss 26154 Mar  4 19:44 dmidecode
  -rw-r--r-- 1 pss pss  1507 Mar  4 19:45 gpu-manager.log
  -rw-r--r-- 1 pss pss   110 Mar  4 19:44 lsb-release-a
  -rw-r--r-- 1 pss pss  1464 Mar  4 19:44 lscpu
  -rw-r--r-- 1 pss pss  4353 Mar  4 19:46 lspci
  -rw-r--r-- 1 pss pss  4105 Mar  4 20:05 lspci-vvv-radeon-580.txt
  -rw-r--r-- 1 pss pss 19318 Mar  4 19:48 
mprime-p95v294b8.linux64-results-2018-03-04.txt
  -rw-r--r-- 1 pss pss   104 Mar  4 19:44 uname-a
  -rw-r--r-- 1 pss pss35 Mar  4 20:27 version.log

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pss1801 F pulseaudio
   /dev/snd/controlC0:  pss1801 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  4 20:21:55 2018
  InstallationDate: Installed on 2018-02-16 (16 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Dell Inc. Inspiron 5675
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.utf8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=d6a2ae1e-5421-435f-8e4c-e377133cebc9 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-03-04 (1 days ago)
  dmi.bios.date: 12/04/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.6
  dmi.board.name: 07PR60
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.6
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.6:bd12/04/2017:svnDellInc.:pnInspiron5675:pvr1.3.6:rvnDellInc.:rn07PR60:rvrA00:cvnDellInc.:ct3:cvr1.3.6:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5675
  dmi.product.version: 1.3.6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753346/+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 1753346] Re: AMD 7 1800X system (Dell Inspiron 5675) randomly freezes

2018-03-04 Thread Pragnesh Sampat
Most of the times, I have had to powercycle to recover.  Sometimes pings
work, but not ssh.  When this happens, I could use a 'ALT-SysReq USB'
sequence to try and reboot, which appeared to work, but eventually had
to powercycle.

** Summary changed:

- AMD 7 1800X system (Dell Inspiron 5675) randomly freezes - have to powercycle
+ AMD 7 1800X system (Dell Inspiron 5675) randomly freezes

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

Title:
  AMD 7 1800X system (Dell Inspiron 5675) randomly freezes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is happening every day or so.  I cannot see anything in the
  kern.log or syslog that give me a clue on where/what the issue might.
  I was using Ubuntu 17.10 earlier and upgraded to Ubuntu 18.04 on
  3/3/2018, since I thought kernel 4.15 might have better support for
  the ryzen 7 and also maybe amdgpu for the radeon 580 might be newer.
  I have removed most external devices except for networking and HDMI
  and audio out.

  Attached a tarball of info, although I believe that since I used
  'ubuntu-bug linux' command, the information might be duplicated,
  apologize for any extra attachments.

  $ ls -l dell-5675-sysinfo/
  total 168
  -rw-r--r-- 1 pss pss 83139 Mar  4 19:47 dmesg
  -rw-r--r-- 1 pss pss 26154 Mar  4 19:44 dmidecode
  -rw-r--r-- 1 pss pss  1507 Mar  4 19:45 gpu-manager.log
  -rw-r--r-- 1 pss pss   110 Mar  4 19:44 lsb-release-a
  -rw-r--r-- 1 pss pss  1464 Mar  4 19:44 lscpu
  -rw-r--r-- 1 pss pss  4353 Mar  4 19:46 lspci
  -rw-r--r-- 1 pss pss  4105 Mar  4 20:05 lspci-vvv-radeon-580.txt
  -rw-r--r-- 1 pss pss 19318 Mar  4 19:48 
mprime-p95v294b8.linux64-results-2018-03-04.txt
  -rw-r--r-- 1 pss pss   104 Mar  4 19:44 uname-a
  -rw-r--r-- 1 pss pss35 Mar  4 20:27 version.log

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pss1801 F pulseaudio
   /dev/snd/controlC0:  pss1801 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  4 20:21:55 2018
  InstallationDate: Installed on 2018-02-16 (16 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Dell Inc. Inspiron 5675
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.utf8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=d6a2ae1e-5421-435f-8e4c-e377133cebc9 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-03-04 (1 days ago)
  dmi.bios.date: 12/04/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.6
  dmi.board.name: 07PR60
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.6
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.6:bd12/04/2017:svnDellInc.:pnInspiron5675:pvr1.3.6:rvnDellInc.:rn07PR60:rvrA00:cvnDellInc.:ct3:cvr1.3.6:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5675
  dmi.product.version: 1.3.6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753346/+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 1753346] [NEW] AMD 7 1800X system (Dell Inspiron 5675) randomly freezes - have to powercycle

2018-03-04 Thread Pragnesh Sampat
Public bug reported:

This is happening every day or so.  I cannot see anything in the
kern.log or syslog that give me a clue on where/what the issue might.  I
was using Ubuntu 17.10 earlier and upgraded to Ubuntu 18.04 on 3/3/2018,
since I thought kernel 4.15 might have better support for the ryzen 7
and also maybe amdgpu for the radeon 580 might be newer.  I have removed
most external devices except for networking and HDMI and audio out.

Attached a tarball of info, although I believe that since I used
'ubuntu-bug linux' command, the information might be duplicated,
apologize for any extra attachments.

$ ls -l dell-5675-sysinfo/
total 168
-rw-r--r-- 1 pss pss 83139 Mar  4 19:47 dmesg
-rw-r--r-- 1 pss pss 26154 Mar  4 19:44 dmidecode
-rw-r--r-- 1 pss pss  1507 Mar  4 19:45 gpu-manager.log
-rw-r--r-- 1 pss pss   110 Mar  4 19:44 lsb-release-a
-rw-r--r-- 1 pss pss  1464 Mar  4 19:44 lscpu
-rw-r--r-- 1 pss pss  4353 Mar  4 19:46 lspci
-rw-r--r-- 1 pss pss  4105 Mar  4 20:05 lspci-vvv-radeon-580.txt
-rw-r--r-- 1 pss pss 19318 Mar  4 19:48 
mprime-p95v294b8.linux64-results-2018-03-04.txt
-rw-r--r-- 1 pss pss   104 Mar  4 19:44 uname-a
-rw-r--r-- 1 pss pss35 Mar  4 20:27 version.log

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-10-generic 4.15.0-10.11
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  pss1801 F pulseaudio
 /dev/snd/controlC0:  pss1801 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar  4 20:21:55 2018
InstallationDate: Installed on 2018-02-16 (16 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
MachineType: Dell Inc. Inspiron 5675
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=d6a2ae1e-5421-435f-8e4c-e377133cebc9 ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-10-generic N/A
 linux-backports-modules-4.15.0-10-generic  N/A
 linux-firmware 1.172
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2018-03-04 (1 days ago)
dmi.bios.date: 12/04/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.6
dmi.board.name: 07PR60
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 1.3.6
dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.6:bd12/04/2017:svnDellInc.:pnInspiron5675:pvr1.3.6:rvnDellInc.:rn07PR60:rvrA00:cvnDellInc.:ct3:cvr1.3.6:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5675
dmi.product.version: 1.3.6
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug bionic

** Attachment added: "tar file containing details that might be useful"
   
https://bugs.launchpad.net/bugs/1753346/+attachment/5069412/+files/dell-5675-sysinfo.tgz

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

Title:
  AMD 7 1800X system (Dell Inspiron 5675) randomly freezes - have to
  powercycle

Status in linux package in Ubuntu:
  New

Bug description:
  This is happening every day or so.  I cannot see anything in the
  kern.log or syslog that give me a clue on where/what the issue might.
  I was using Ubuntu 17.10 earlier and upgraded to Ubuntu 18.04 on
  3/3/2018, since I thought kernel 4.15 might have better support for
  the ryzen 7 and also maybe amdgpu for the radeon 580 might be newer.
  I have removed most external devices except for networking and HDMI
  and audio out.

  Attached a tarball of info, although I believe that since I used
  'ubuntu-bug linux' command, the information might be duplicated,
  apologize for any extra attachments.

  $ ls -l dell-5675-sysinfo/
  total 168
  -rw-r--r-- 1 pss pss 83139 Mar  4 19:47 dmesg
  -rw-r--r-- 1 pss pss 26154 Mar  4 19:44 dmidecode
  -rw-r--r-- 1 pss pss  1507 Mar  4 19:45 gpu-manager.log
  -rw-r--r-- 1 pss pss   110 Mar  4 19:44 lsb-release-a
  -rw-r--r-- 1 pss pss  1464 Mar  4 19:44 lscpu
  -rw-r--r-- 1 pss pss  4353 Mar  4 19:46 lspci
  -rw-r--r-- 1 pss pss  4105 Mar  4 20:05 lspci-vvv-radeon-580.txt
  -rw-r--r-- 1 pss pss 19318 Mar  4 19:48 
mprime-p95v294b8.linux64-results-2018-03-04.txt
  -rw-r--r-- 1 pss pss   104 Mar  4 19:44 uname-a
  -rw-r--r-- 1 pss pss35 Mar  4 20:27 version.log

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/

[Kernel-packages] [Bug 1753288] Re: ZFS setgid broken on 0.7

2018-03-04 Thread Stéphane Graber
That looks like it, yes. As far as I know most of us only noticed this
when bionic switched from 0.6.x to 0.7.x so yes, 0.6.x seems fine and
current 0.7.x is affected.

I've commented on the github issue and will reach out to Wolfgang (Blub)
on IRC otherwise (he hangs out in the LXC/LXD dev channel) to see if he
made any progress on this since November.

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

Title:
  ZFS setgid broken on 0.7

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hey there,

  We've had one of our LXD users report that setting the setgid bit
  inside a container using ZFS on Ubuntu 18.04 (zfs 0.7) is silently
  failing. This is not a LXD bug as the exact same operation works on
  other filesystems.

  There are more details available here:
  https://github.com/lxc/lxd/issues/4294

  Reproducer looks something like:

  ```
  root@c1:~# touch a
  root@c1:~# chmod g+s a
  root@c1:~# touch b
  root@c1:~# chown 0:117 b
  root@c1:~# chmod g+s b
  root@c1:~# stat a
File: a
Size: 0 Blocks: 1  IO Block: 131072 regular empty file
  Device: 43h/67d   Inode: 33890   Links: 1
  Access: (2644/-rw-r-Sr--)  Uid: (0/root)   Gid: (0/root)
  Access: 2018-03-02 03:32:47.019430367 +
  Modify: 2018-03-02 03:32:47.019430367 +
  Change: 2018-03-02 03:32:49.459445015 +
   Birth: -
  root@c1:~# stat b
File: b
Size: 0 Blocks: 1  IO Block: 131072 regular empty file
  Device: 43h/67d   Inode: 34186   Links: 1
  Access: (0644/-rw-r--r--)  Uid: (0/root)   Gid: (  117/postdrop)
  Access: 2018-03-02 03:32:50.907453706 +
  Modify: 2018-03-02 03:32:50.907453706 +
  Change: 2018-03-02 03:33:01.299516054 +
   Birth: -
  root@c1:~# 
  ```

  And for confirmation, using a tmpfs in the same container:

  ```
  root@c1:~# mkdir tmpfs
  root@c1:~# mount -t tmpfs tmpfs tmpfs
  root@c1:~# cd tmpfs/
  root@c1:~/tmpfs# touch a
  root@c1:~/tmpfs# chmod g+s a
  root@c1:~/tmpfs# touch b
  root@c1:~/tmpfs# chown 0:117 b
  root@c1:~/tmpfs# chmod g+s b
  root@c1:~/tmpfs# stat a
File: a
Size: 0 Blocks: 0  IO Block: 4096   regular empty file
  Device: 65h/101d  Inode: 3   Links: 1
  Access: (2644/-rw-r-Sr--)  Uid: (0/root)   Gid: (0/root)
  Access: 2018-03-02 03:33:35.783722623 +
  Modify: 2018-03-02 03:33:35.783722623 +
  Change: 2018-03-02 03:33:40.507750883 +
   Birth: -
  root@c1:~/tmpfs# stat b
File: b
Size: 0 Blocks: 0  IO Block: 4096   regular empty file
  Device: 65h/101d  Inode: 4   Links: 1
  Access: (2644/-rw-r-Sr--)  Uid: (0/root)   Gid: (  117/postdrop)
  Access: 2018-03-02 03:33:42.131760597 +
  Modify: 2018-03-02 03:33:42.131760597 +
  Change: 2018-03-02 03:33:46.227785091 +
   Birth: -
  root@c1:~/tmpfs# 
  ```

  This is particularly troubling because there are no errors returned to
  the user, so we now have containers that will have broken binaries and
  permissions applied to them with no visible way to detect the problem
  short of scanning the entire filesystem against a list of known
  permissions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753288/+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 1753288] Re: ZFS setgid broken on 0.7

2018-03-04 Thread Colin Ian King
If I'm not mistaken, this seems the same issue, correct me if I'm wrong:
https://github.com/zfsonlinux/zfs/issues/6800

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

Title:
  ZFS setgid broken on 0.7

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hey there,

  We've had one of our LXD users report that setting the setgid bit
  inside a container using ZFS on Ubuntu 18.04 (zfs 0.7) is silently
  failing. This is not a LXD bug as the exact same operation works on
  other filesystems.

  There are more details available here:
  https://github.com/lxc/lxd/issues/4294

  Reproducer looks something like:

  ```
  root@c1:~# touch a
  root@c1:~# chmod g+s a
  root@c1:~# touch b
  root@c1:~# chown 0:117 b
  root@c1:~# chmod g+s b
  root@c1:~# stat a
File: a
Size: 0 Blocks: 1  IO Block: 131072 regular empty file
  Device: 43h/67d   Inode: 33890   Links: 1
  Access: (2644/-rw-r-Sr--)  Uid: (0/root)   Gid: (0/root)
  Access: 2018-03-02 03:32:47.019430367 +
  Modify: 2018-03-02 03:32:47.019430367 +
  Change: 2018-03-02 03:32:49.459445015 +
   Birth: -
  root@c1:~# stat b
File: b
Size: 0 Blocks: 1  IO Block: 131072 regular empty file
  Device: 43h/67d   Inode: 34186   Links: 1
  Access: (0644/-rw-r--r--)  Uid: (0/root)   Gid: (  117/postdrop)
  Access: 2018-03-02 03:32:50.907453706 +
  Modify: 2018-03-02 03:32:50.907453706 +
  Change: 2018-03-02 03:33:01.299516054 +
   Birth: -
  root@c1:~# 
  ```

  And for confirmation, using a tmpfs in the same container:

  ```
  root@c1:~# mkdir tmpfs
  root@c1:~# mount -t tmpfs tmpfs tmpfs
  root@c1:~# cd tmpfs/
  root@c1:~/tmpfs# touch a
  root@c1:~/tmpfs# chmod g+s a
  root@c1:~/tmpfs# touch b
  root@c1:~/tmpfs# chown 0:117 b
  root@c1:~/tmpfs# chmod g+s b
  root@c1:~/tmpfs# stat a
File: a
Size: 0 Blocks: 0  IO Block: 4096   regular empty file
  Device: 65h/101d  Inode: 3   Links: 1
  Access: (2644/-rw-r-Sr--)  Uid: (0/root)   Gid: (0/root)
  Access: 2018-03-02 03:33:35.783722623 +
  Modify: 2018-03-02 03:33:35.783722623 +
  Change: 2018-03-02 03:33:40.507750883 +
   Birth: -
  root@c1:~/tmpfs# stat b
File: b
Size: 0 Blocks: 0  IO Block: 4096   regular empty file
  Device: 65h/101d  Inode: 4   Links: 1
  Access: (2644/-rw-r-Sr--)  Uid: (0/root)   Gid: (  117/postdrop)
  Access: 2018-03-02 03:33:42.131760597 +
  Modify: 2018-03-02 03:33:42.131760597 +
  Change: 2018-03-02 03:33:46.227785091 +
   Birth: -
  root@c1:~/tmpfs# 
  ```

  This is particularly troubling because there are no errors returned to
  the user, so we now have containers that will have broken binaries and
  permissions applied to them with no visible way to detect the problem
  short of scanning the entire filesystem against a list of known
  permissions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753288/+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 1753288] Re: ZFS setgid broken on 0.7

2018-03-04 Thread Colin Ian King
Just checking, is this a regression in ZFS 0.7.x?

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Bug watch added: Github Issue Tracker for ZFS #6800
   https://github.com/zfsonlinux/zfs/issues/6800

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

Title:
  ZFS setgid broken on 0.7

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hey there,

  We've had one of our LXD users report that setting the setgid bit
  inside a container using ZFS on Ubuntu 18.04 (zfs 0.7) is silently
  failing. This is not a LXD bug as the exact same operation works on
  other filesystems.

  There are more details available here:
  https://github.com/lxc/lxd/issues/4294

  Reproducer looks something like:

  ```
  root@c1:~# touch a
  root@c1:~# chmod g+s a
  root@c1:~# touch b
  root@c1:~# chown 0:117 b
  root@c1:~# chmod g+s b
  root@c1:~# stat a
File: a
Size: 0 Blocks: 1  IO Block: 131072 regular empty file
  Device: 43h/67d   Inode: 33890   Links: 1
  Access: (2644/-rw-r-Sr--)  Uid: (0/root)   Gid: (0/root)
  Access: 2018-03-02 03:32:47.019430367 +
  Modify: 2018-03-02 03:32:47.019430367 +
  Change: 2018-03-02 03:32:49.459445015 +
   Birth: -
  root@c1:~# stat b
File: b
Size: 0 Blocks: 1  IO Block: 131072 regular empty file
  Device: 43h/67d   Inode: 34186   Links: 1
  Access: (0644/-rw-r--r--)  Uid: (0/root)   Gid: (  117/postdrop)
  Access: 2018-03-02 03:32:50.907453706 +
  Modify: 2018-03-02 03:32:50.907453706 +
  Change: 2018-03-02 03:33:01.299516054 +
   Birth: -
  root@c1:~# 
  ```

  And for confirmation, using a tmpfs in the same container:

  ```
  root@c1:~# mkdir tmpfs
  root@c1:~# mount -t tmpfs tmpfs tmpfs
  root@c1:~# cd tmpfs/
  root@c1:~/tmpfs# touch a
  root@c1:~/tmpfs# chmod g+s a
  root@c1:~/tmpfs# touch b
  root@c1:~/tmpfs# chown 0:117 b
  root@c1:~/tmpfs# chmod g+s b
  root@c1:~/tmpfs# stat a
File: a
Size: 0 Blocks: 0  IO Block: 4096   regular empty file
  Device: 65h/101d  Inode: 3   Links: 1
  Access: (2644/-rw-r-Sr--)  Uid: (0/root)   Gid: (0/root)
  Access: 2018-03-02 03:33:35.783722623 +
  Modify: 2018-03-02 03:33:35.783722623 +
  Change: 2018-03-02 03:33:40.507750883 +
   Birth: -
  root@c1:~/tmpfs# stat b
File: b
Size: 0 Blocks: 0  IO Block: 4096   regular empty file
  Device: 65h/101d  Inode: 4   Links: 1
  Access: (2644/-rw-r-Sr--)  Uid: (0/root)   Gid: (  117/postdrop)
  Access: 2018-03-02 03:33:42.131760597 +
  Modify: 2018-03-02 03:33:42.131760597 +
  Change: 2018-03-02 03:33:46.227785091 +
   Birth: -
  root@c1:~/tmpfs# 
  ```

  This is particularly troubling because there are no errors returned to
  the user, so we now have containers that will have broken binaries and
  permissions applied to them with no visible way to detect the problem
  short of scanning the entire filesystem against a list of known
  permissions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753288/+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-03-04 Thread Emiko Bellocq
> #583

>>My point was that I have difficulty in changing the order, changes are not 
>>permanent, and if it does boot from the CD it does not work in UEFI mode, and 
>>so I cannot use e.g. Boot Repair.
>>Would it be harmful to use fix referred to above, or is that specific to 
>>Lenovo?

To make this boot order change permanent, you have to repair the EFI.
If you can access to the any sort of OS on the internal disc, you can install a 
newer version of Ubuntu to the another partition.

This dualboot creation is universal, not just for a specific laptop model.
If you have any inportant data on your working OS, I suggest you to make a 
backup before re-partitiong the disc.

-- 
You 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
  Toshiba Satellite L70-A-13M
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC (fixed with official fix)
  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 h

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

2018-03-04 Thread Emiko Bellocq
>#582
Yes, it is a BIOS bug.
My comment #581 is not a reply for your posting but the one above :).

I just wanted to point out that it is possible to install a new version of 
Ubuntu from the internal disc to another partition of the sam disc then boot 
from that newly installed Ubuntu partition to fix the BIOS problem.
To do that, you need GRUB2 instead of EasyBCD.

But if your laptop is still under the watrranty, certainly RMA it is the
another solution.

-- 
You 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
  Toshiba Satellite L70-A-13M
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC (fixed with official fix)
  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 

[Kernel-packages] [Bug 1751676] Re: Synaptics' touchpad not detected in 'CyberpowerPC Tracer II' laptop after kernel, system and multiple packages upgrade (for instance: CUDA, libinput, etc.

2018-03-04 Thread Pedro
Thanks @Joseph for the comment. I'm pretty weary of installing RC
kernels but it'll give it a try this week.

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

Title:
  Synaptics' touchpad not detected in 'CyberpowerPC Tracer II' laptop
  after kernel, system and multiple packages upgrade (for instance:
  CUDA, libinput, etc.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installed ubuntu 16.04 a while ago and touchpad was working. It does work as 
well on LiveCDs.
  After upgrading kernel and some system packages (i've even removed 
xorg-input-synaptics), touchpad does not even show in `xinput list`. USB mouse 
works though.

  I've skimmed dozens of pages in askubuntu and stackexchange to no avail:
  
https://unix.stackexchange.com/questions/28736/what-does-the-i8042-nomux-1-kernel-option-do-during-booting-of-ubuntu
  
https://askubuntu.com/questions/763584/elantech-touchpad-not-working-on-ubuntu-16-04-and-arch-linux
  https://ubuntuforums.org/showthread.php?t=2323564
  https://ubuntuforums.org/showthread.php?t=2352021

  Most of these revolved around tampering with the 
`GRUB_CMDLINE_LINUX_DEFAULT=` argument in `/etc/default/grub` and removing 
`xserver-xorg-input-synaptics` package along with confs.
  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  t2063 F pulseaudio
   /dev/snd/pcmC0D0p:   t2063 F...m pulseaudio
   /dev/snd/controlC0:  t2063 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=e86768f6-cc8c-4bdc-91fb-a25e5184ee57
  InstallationDate: Installed on 2017-08-27 (182 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: CyberpowerPC Tracer II
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   0 EFI VGA
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=6814f425-7e3f-4911-8fa7-e4637ae009c4 ro atkbd.reset=1 i8042.nomux=1 
i8042.reset=1 i8042.nopnp=1 i8042.dumbkbd=1 i8042.kbdreset=1 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.157.16
  Tags:  xenial
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/23/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N.1.03
  dmi.board.asset.tag: Standard
  dmi.board.name: Tracer II
  dmi.board.vendor: CyberpowerPC
  dmi.board.version: Standard
  dmi.chassis.asset.tag: Standard
  dmi.chassis.type: 9
  dmi.chassis.vendor: Standard
  dmi.chassis.version: Standard
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN.1.03:bd02/23/2017:svnCyberpowerPC:pnTracerII:pvrStandard:rvnCyberpowerPC:rnTracerII:rvrStandard:cvnStandard:ct9:cvrStandard:
  dmi.product.family: KBL
  dmi.product.name: Tracer II
  dmi.product.version: Standard
  dmi.sys.vendor: CyberpowerPC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751676/+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 1753144] Re: Booting kernel 4.4.0-116.140 fails

2018-03-04 Thread Simon Pepping
No luck running apport-collect:

simon:~$ apport-collect 1753144
ERROR: Could not import module, is a package upgrade in progress?  Error: No 
module named PyQt5.QtCore

I cannot fix this.

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

Title:
  Booting kernel 4.4.0-116.140 fails

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Booting kernel 4.4.0-116.140 lands me in an ash shell with prompt
  'initramfs'. keyboard and mouse USB fails, so that I can do nothing.

  Error messages from module hid: 'unknown symbol __x86_indirect_thunk_XXX err 
-22' and
  'disagrees about version of __x86_indirect_thunk_XXX err -22, where XXX has 5 
or 6 different 3-letter values.

  I have gcc-5:i386 (5.4.0-6ubuntu1~16.04.6, 5.4.0-6ubuntu1~16.04.9),
  which would be correct according to bug report #1750937. Since there
  are no modules built by DKMS, there is no compilation involved in
  installation.

  I removed and reinstalled the kernel image and headers, but the problem did 
not disappear: 
  Install: linux-headers-generic:i386 (4.4.0.116.122, automatic), 
linux-image-generic:i386 (4.4.0.116.122, automatic), 
linux-headers-4.4.0-116:i386 (4.4.0-116.140, automatic), 
linux-image-extra-4.4.0-116-generic:i386 (4.4.0-116.140, automatic), 
linux-headers-4.4.0-116-generic:i386 (4.4.0-116.140, automatic), 
linux-generic:i386 (4.4.0.116.122), linux-image-4.4.0-116-generic:i386 
(4.4.0-116.140, automatic)

  Since I cannot boot into this kernel, I cannot generate a bug report,
  and there are no syslog entries.

  Description:Ubuntu 16.04.4 LTS
  Release:16.04

  linux-image-4.4.0-116-generic:
Geïnstalleerd: 4.4.0-116.140
  linux-image-extra-4.4.0-116-generic:
Geïnstalleerd: 4.4.0-116.140
  gcc-5:
Geïnstalleerd: 5.4.0-6ubuntu1~16.04.9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753144/+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 1728244] Re: Touchpad stops working after reboot on Apollo Lake

2018-03-04 Thread iBART
Reported.

https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1753298

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

Title:
  Touchpad stops working after reboot on Apollo Lake

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

Bug description:
  On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450
  processor, if you install Ubuntu 17.10 (or less) with isorespin and
  use rEFInd as bootloader (this is the only way to get linux booting on
  this laptop) everything works out of the box, but after a reboot or
  two the touchpad stops working. Both in Ubuntu and Windows 10. The
  only way to restore functionality is to boot from usb key ubuntu 17.10
  respined, or disassemble laptop and detach-reattach battery cable.
  This is mesg | grep i2c_hid:

  
  [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)
  [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device.
  [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns 
-61
  [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)

  
  uname -rvps
  Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 
x86_64

  There has to be a bug in the kernel. Any way to avoid this?

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1728244/+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 1728244] Re: Touchpad stops working after reboot on Apollo Lake

2018-03-04 Thread iBART
Still not working for me. I just tried a new 4.16 kernel and I noticied
that audio is not working. I tried a lot of 4.16 ubuntu kenerls and
audio is not working in them.

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

Title:
  Touchpad stops working after reboot on Apollo Lake

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

Bug description:
  On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450
  processor, if you install Ubuntu 17.10 (or less) with isorespin and
  use rEFInd as bootloader (this is the only way to get linux booting on
  this laptop) everything works out of the box, but after a reboot or
  two the touchpad stops working. Both in Ubuntu and Windows 10. The
  only way to restore functionality is to boot from usb key ubuntu 17.10
  respined, or disassemble laptop and detach-reattach battery cable.
  This is mesg | grep i2c_hid:

  
  [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)
  [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device.
  [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns 
-61
  [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)

  
  uname -rvps
  Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 
x86_64

  There has to be a bug in the kernel. Any way to avoid this?

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1728244/+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 1753292] Status changed to Confirmed

2018-03-04 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 74s! [ksoftirqd/0:7]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  on virtual machine

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 861 F pulseaudio
igor   1163 F pulseaudio
  Date: Sun Mar  4 10:05:58 2018
  Failure: oops
  InstallationDate: Installed on 2017-11-18 (105 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171117)
  IwConfig:
   lono wireless extensions.
   
   ens33 no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=1a09b2d1-1d4f-44fc-baa7-37b9cf13c503 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  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#0 stuck for 74s! [ksoftirqd/0:7]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/19/2017
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753292/+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 1753292] [NEW] watchdog: BUG: soft lockup - CPU#0 stuck for 74s! [ksoftirqd/0:7]

2018-03-04 Thread igi
Public bug reported:

on virtual machine

ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-10-generic 4.15.0-10.11
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm 861 F pulseaudio
  igor   1163 F pulseaudio
Date: Sun Mar  4 10:05:58 2018
Failure: oops
InstallationDate: Installed on 2017-11-18 (105 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171117)
IwConfig:
 lono wireless extensions.
 
 ens33 no wireless extensions.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
 Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware Virtual Platform
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=1a09b2d1-1d4f-44fc-baa7-37b9cf13c503 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
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#0 stuck for 74s! [ksoftirqd/0:7]
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/19/2017
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.

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


** Tags: amd64 apport-kerneloops bionic kernel-driver-e1000 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/1753292

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 74s! [ksoftirqd/0:7]

Status in linux package in Ubuntu:
  New

Bug description:
  on virtual machine

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 861 F pulseaudio
igor   1163 F pulseaudio
  Date: Sun Mar  4 10:05:58 2018
  Failure: oops
  InstallationDate: Installed on 2017-11-18 (105 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171117)
  IwConfig:
   lono wireless extensions.
   
   ens33 no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=1a09b2d1-1d4f-44fc-baa7-37b9cf13c503 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  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#0 stuck for 74s! [ksoftirqd/0:7]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/19/2017
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: V

[Kernel-packages] [Bug 1753288] [NEW] ZFS setgid broken on 0.7

2018-03-04 Thread Stéphane Graber
Public bug reported:

Hey there,

We've had one of our LXD users report that setting the setgid bit inside
a container using ZFS on Ubuntu 18.04 (zfs 0.7) is silently failing.
This is not a LXD bug as the exact same operation works on other
filesystems.

There are more details available here:
https://github.com/lxc/lxd/issues/4294

Reproducer looks something like:

```
root@c1:~# touch a
root@c1:~# chmod g+s a
root@c1:~# touch b
root@c1:~# chown 0:117 b
root@c1:~# chmod g+s b
root@c1:~# stat a
  File: a
  Size: 0   Blocks: 1  IO Block: 131072 regular empty file
Device: 43h/67d Inode: 33890   Links: 1
Access: (2644/-rw-r-Sr--)  Uid: (0/root)   Gid: (0/root)
Access: 2018-03-02 03:32:47.019430367 +
Modify: 2018-03-02 03:32:47.019430367 +
Change: 2018-03-02 03:32:49.459445015 +
 Birth: -
root@c1:~# stat b
  File: b
  Size: 0   Blocks: 1  IO Block: 131072 regular empty file
Device: 43h/67d Inode: 34186   Links: 1
Access: (0644/-rw-r--r--)  Uid: (0/root)   Gid: (  117/postdrop)
Access: 2018-03-02 03:32:50.907453706 +
Modify: 2018-03-02 03:32:50.907453706 +
Change: 2018-03-02 03:33:01.299516054 +
 Birth: -
root@c1:~# 
```

And for confirmation, using a tmpfs in the same container:

```
root@c1:~# mkdir tmpfs
root@c1:~# mount -t tmpfs tmpfs tmpfs
root@c1:~# cd tmpfs/
root@c1:~/tmpfs# touch a
root@c1:~/tmpfs# chmod g+s a
root@c1:~/tmpfs# touch b
root@c1:~/tmpfs# chown 0:117 b
root@c1:~/tmpfs# chmod g+s b
root@c1:~/tmpfs# stat a
  File: a
  Size: 0   Blocks: 0  IO Block: 4096   regular empty file
Device: 65h/101dInode: 3   Links: 1
Access: (2644/-rw-r-Sr--)  Uid: (0/root)   Gid: (0/root)
Access: 2018-03-02 03:33:35.783722623 +
Modify: 2018-03-02 03:33:35.783722623 +
Change: 2018-03-02 03:33:40.507750883 +
 Birth: -
root@c1:~/tmpfs# stat b
  File: b
  Size: 0   Blocks: 0  IO Block: 4096   regular empty file
Device: 65h/101dInode: 4   Links: 1
Access: (2644/-rw-r-Sr--)  Uid: (0/root)   Gid: (  117/postdrop)
Access: 2018-03-02 03:33:42.131760597 +
Modify: 2018-03-02 03:33:42.131760597 +
Change: 2018-03-02 03:33:46.227785091 +
 Birth: -
root@c1:~/tmpfs# 
```

This is particularly troubling because there are no errors returned to
the user, so we now have containers that will have broken binaries and
permissions applied to them with no visible way to detect the problem
short of scanning the entire filesystem against a list of known
permissions.

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

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

Title:
  ZFS setgid broken on 0.7

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hey there,

  We've had one of our LXD users report that setting the setgid bit
  inside a container using ZFS on Ubuntu 18.04 (zfs 0.7) is silently
  failing. This is not a LXD bug as the exact same operation works on
  other filesystems.

  There are more details available here:
  https://github.com/lxc/lxd/issues/4294

  Reproducer looks something like:

  ```
  root@c1:~# touch a
  root@c1:~# chmod g+s a
  root@c1:~# touch b
  root@c1:~# chown 0:117 b
  root@c1:~# chmod g+s b
  root@c1:~# stat a
File: a
Size: 0 Blocks: 1  IO Block: 131072 regular empty file
  Device: 43h/67d   Inode: 33890   Links: 1
  Access: (2644/-rw-r-Sr--)  Uid: (0/root)   Gid: (0/root)
  Access: 2018-03-02 03:32:47.019430367 +
  Modify: 2018-03-02 03:32:47.019430367 +
  Change: 2018-03-02 03:32:49.459445015 +
   Birth: -
  root@c1:~# stat b
File: b
Size: 0 Blocks: 1  IO Block: 131072 regular empty file
  Device: 43h/67d   Inode: 34186   Links: 1
  Access: (0644/-rw-r--r--)  Uid: (0/root)   Gid: (  117/postdrop)
  Access: 2018-03-02 03:32:50.907453706 +
  Modify: 2018-03-02 03:32:50.907453706 +
  Change: 2018-03-02 03:33:01.299516054 +
   Birth: -
  root@c1:~# 
  ```

  And for confirmation, using a tmpfs in the same container:

  ```
  root@c1:~# mkdir tmpfs
  root@c1:~# mount -t tmpfs tmpfs tmpfs
  root@c1:~# cd tmpfs/
  root@c1:~/tmpfs# touch a
  root@c1:~/tmpfs# chmod g+s a
  root@c1:~/tmpfs# touch b
  root@c1:~/tmpfs# chown 0:117 b
  root@c1:~/tmpfs# chmod g+s b
  root@c1:~/tmpfs# stat a
File: a
Size: 0 Blocks: 0  IO Block: 4096   regular empty file
  Device: 65h/101d  Inode: 3   Links: 1
  Access: (2644/-rw-r-Sr--)  Uid: (0/root)   Gid: (0/root)
  Access: 2018-03-02 03:33:35.783722623 +
  Modify: 2018-03-02 03:33:35.783722623 +
  Change: 2018-03-02 03:33:40.507750883 +
   Birth: -
  root@c1:~/tmpfs# stat b
File: b
Size: 0 Blocks: 0  IO Bl

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

2018-03-04 Thread Rkimber
I think your problem is nothing to do with this BIOS bug.
Youn are giving a boot priority to the internal drive before the optic drive.
You should override the boot order by pressing a certain key such as F2, F8 and 
F9 just after the booting.
Refer the manual of your machine to find out this boot order override key.


My point was that I have difficulty in changing the order, changes are not 
permanent, and if it does boot from the CD it does not work in UEFI mode, and 
so I cannot use e.g. Boot Repair.

Would it be harmful to use fix referred to above, or is that specific to
Lenovo?

-- 
You 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
  Toshiba Satellite L70-A-13M
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC (fixed with official fix)
  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.

  Th

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

2018-03-04 Thread Kamil
Here is a new bug report for a new bug caused by recent updates that
fixed #1742675:

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

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

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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


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

2018-03-04 Thread Aubrey Bourke
When I enter the BIOS (F2) and change the boot order and save it doesn't
remember the settings. Changing to legacy mode is also not possible.
Finally, directly booting via the quick boot menu (F8) is not able to
boot anything except the HDD.

It's definitely the BIOS bug discussed here. Because I was using Lubuntu
17.10 in December 2017. The affected iso was released in October 2017. I
have an Insyde H20 bios. So all symptoms point to this bug.

Thanks for offering some solutions. I would love one of them to work for
me. However, I did recently contact Lenovo to send my laptop in for
repair. They were very helpful. And have even offered to pay for the
postage.

So that is another solution if you cant boot 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/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
  Toshiba Satellite L70-A-13M
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC (fixed with official fix)
  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 ve

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

2018-03-04 Thread Emiko Bellocq
>> #578
BootOrder: 0001,,001A,001D,001F,0021,0022,0023,0024,0025,0027
Boot0001* ubuntu 
HD(1,GPT,f3f80d9f-7ffc-4b2d-a2a4-f18977ec7d96,0x800,0x32000)/File(\EFI\ubuntu\shimx64.efi)
Boot001A* UEFI: Samsung SSD 850 PRO 128GB 
PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0,65535,0)/HD(5,GPT,e25b2fb2-415c-47cb-a039-f6fc9f1edbae,0xd97e800,0x14fd7a5)AMBO
Boot001D* PIONEER BD-RW BDR-209D BBS(CDROM,,0x0)AMBO


I think your problem is nothing to do with this BIOS bug.
Youn are giving a boot priority to the internal drive before the optic drive.
You should override the boot order by pressing a certain key such as F2, F8 and 
F9 just after the booting.
Refer the manual of your machine to find out this boot order override key.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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
  Toshiba Satellite L70-A-13M
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC (fixed with official fix)
  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 serio

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

2018-03-04 Thread Emiko Bellocq
#579

As I have way less experience with EFI than legacy BIOS, I hesitated to add my 
comment.
But there seems to be no answer to your question so far, I'll add my 2 cents.

If you can still boot from your Windows installation, there is a hope.
You should be able to proceed as  in the legacy BIOS setting (see above 
postings) but use GRUB2 instead of EasyBCD.
The detail is explained at EasyBCD website:
https://neosmart.net/wiki/easybcd/uefi/
Option 3: Use GRUB2 EFI as your main boot manager

While I cannot guarantee the result, it is worth trying before resorting
to the hardware solution (replacing or reflashing ROM chip).

-- 
You 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
  Toshiba Satellite L70-A-13M
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC (fixed with official fix)
  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 fu

[Kernel-packages] [Bug 1753010] Re: after recent updates playing youtube videos in firefox causes sometimes freezing of the system

2018-03-04 Thread Kamil
Not sure whether this additional info can help but adding it: freezing
does not occur immediately for the whole system; initially only one app
freezes (any app); but within 1 minute the whole system freezes too.

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

Title:
  after recent updates playing youtube videos in firefox causes
  sometimes freezing of the system

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After recent updates that fixed the bug
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742675 on my
  computer the following different bug has appeared. Playing Youtube
  music videos (static picture + music, length 40-70 minutes) in Firefox
  (as background for other activities on computer) causes sometimes
  (rather often, up to several times per day) freezing of the system.
  And only restart through reset button can help.

  Initially I though that it is related to different Javascript-related
  tasks (manipulating with complex widgets in Chromium, running heavy
  gulp tasks through yarn) but it looks they are not the reason (or at
  least not the main reason). Because right now I have seen the problem
  when keyboard/mouse was not touched at all.

  That's why I think this information is rather enough; and I decided to post 
this bug.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kamil  2021 F pulseaudio
   /dev/snd/controlC1:  kamil  2021 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=5b5ffc28-8999-4ad7-9ff3-f3298c4f28c2
  InstallationDate: Installed on 2017-06-23 (252 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  MachineType: Packard Bell Easynote ENTE70BH
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=557e3c22-0c8c-44b3-a8f6-5446013327ad ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  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.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.157.17
  Tags:  xenial
  Uname: Linux 4.13.0-36-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/08/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.05
  dmi.board.name: Easynote ENTE70BH
  dmi.board.vendor: Packard Bell
  dmi.board.version: V1.05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Packard Bell
  dmi.chassis.version: V1.05
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.05:bd08/08/2016:svnPackardBell:pnEasynoteENTE70BH:pvrV1.05:rvnPackardBell:rnEasynoteENTE70BH:rvrV1.05:cvnPackardBell:ct10:cvrV1.05:
  dmi.product.family: BDW
  dmi.product.name: Easynote ENTE70BH
  dmi.product.version: V1.05
  dmi.sys.vendor: Packard Bell

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753010/+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 1752829] ProcInterrupts.txt

2018-03-04 Thread Yassine
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1752829/+attachment/5068803/+files/ProcInterrupts.txt

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

Title:
  AMD HAINAN (Radeon R5 M330) Clock frequency is 750MHz while it is
  supposed to be 1030MHz

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel source: /drivers/gpu/drm/radeon/si_dpm.c line 2985:

  max_sclk = 75000;

  instead of

  max_sclk = 103000;

  Why is that? I changed it and rebuilt the kernel, and I can say that
  there are absolutely no issues when using the 1030MHz clock, which is
  what it is supposed to be.

  Linux Version: 4.13.0-36-generic

  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yassine3068 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=e9860ff6-0207-40ae-b2dd-115d7c7956b8
  InstallationDate: Installed on 2016-12-19 (439 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57d6 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 25a7:0701  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: \\boot\vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=070ac60f-63d1-48e3-9322-44812d365c40 ro quiet splash radeon.runpm=1 
vt.handoff=7 initrd=boot\initrd.img-4.13.0-36-generic
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-20 (135 days ago)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 11/24/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8136
  dmi.board.vendor: HP
  dmi.board.version: 31.34
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1D:bd11/24/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8136:rvr31.34:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752829/+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 1752829] WifiSyslog.txt

2018-03-04 Thread Yassine
apport information

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

** No longer affects: kernel

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

Title:
  AMD HAINAN (Radeon R5 M330) Clock frequency is 750MHz while it is
  supposed to be 1030MHz

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel source: /drivers/gpu/drm/radeon/si_dpm.c line 2985:

  max_sclk = 75000;

  instead of

  max_sclk = 103000;

  Why is that? I changed it and rebuilt the kernel, and I can say that
  there are absolutely no issues when using the 1030MHz clock, which is
  what it is supposed to be.

  Linux Version: 4.13.0-36-generic

  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yassine3068 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=e9860ff6-0207-40ae-b2dd-115d7c7956b8
  InstallationDate: Installed on 2016-12-19 (439 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57d6 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 25a7:0701  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: \\boot\vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=070ac60f-63d1-48e3-9322-44812d365c40 ro quiet splash radeon.runpm=1 
vt.handoff=7 initrd=boot\initrd.img-4.13.0-36-generic
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-20 (135 days ago)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 11/24/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8136
  dmi.board.vendor: HP
  dmi.board.version: 31.34
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1D:bd11/24/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8136:rvr31.34:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752829/+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 1752829] RfKill.txt

2018-03-04 Thread Yassine
apport information

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

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

Title:
  AMD HAINAN (Radeon R5 M330) Clock frequency is 750MHz while it is
  supposed to be 1030MHz

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel source: /drivers/gpu/drm/radeon/si_dpm.c line 2985:

  max_sclk = 75000;

  instead of

  max_sclk = 103000;

  Why is that? I changed it and rebuilt the kernel, and I can say that
  there are absolutely no issues when using the 1030MHz clock, which is
  what it is supposed to be.

  Linux Version: 4.13.0-36-generic

  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yassine3068 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=e9860ff6-0207-40ae-b2dd-115d7c7956b8
  InstallationDate: Installed on 2016-12-19 (439 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57d6 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 25a7:0701  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: \\boot\vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=070ac60f-63d1-48e3-9322-44812d365c40 ro quiet splash radeon.runpm=1 
vt.handoff=7 initrd=boot\initrd.img-4.13.0-36-generic
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-20 (135 days ago)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 11/24/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8136
  dmi.board.vendor: HP
  dmi.board.version: 31.34
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1D:bd11/24/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8136:rvr31.34:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752829/+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 1752829] UdevDb.txt

2018-03-04 Thread Yassine
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1752829/+attachment/5068807/+files/UdevDb.txt

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

Title:
  AMD HAINAN (Radeon R5 M330) Clock frequency is 750MHz while it is
  supposed to be 1030MHz

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel source: /drivers/gpu/drm/radeon/si_dpm.c line 2985:

  max_sclk = 75000;

  instead of

  max_sclk = 103000;

  Why is that? I changed it and rebuilt the kernel, and I can say that
  there are absolutely no issues when using the 1030MHz clock, which is
  what it is supposed to be.

  Linux Version: 4.13.0-36-generic

  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yassine3068 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=e9860ff6-0207-40ae-b2dd-115d7c7956b8
  InstallationDate: Installed on 2016-12-19 (439 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57d6 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 25a7:0701  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: \\boot\vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=070ac60f-63d1-48e3-9322-44812d365c40 ro quiet splash radeon.runpm=1 
vt.handoff=7 initrd=boot\initrd.img-4.13.0-36-generic
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-20 (135 days ago)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 11/24/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8136
  dmi.board.vendor: HP
  dmi.board.version: 31.34
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1D:bd11/24/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8136:rvr31.34:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752829/+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 1752829] PulseList.txt

2018-03-04 Thread Yassine
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1752829/+attachment/5068805/+files/PulseList.txt

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

Title:
  AMD HAINAN (Radeon R5 M330) Clock frequency is 750MHz while it is
  supposed to be 1030MHz

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel source: /drivers/gpu/drm/radeon/si_dpm.c line 2985:

  max_sclk = 75000;

  instead of

  max_sclk = 103000;

  Why is that? I changed it and rebuilt the kernel, and I can say that
  there are absolutely no issues when using the 1030MHz clock, which is
  what it is supposed to be.

  Linux Version: 4.13.0-36-generic

  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yassine3068 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=e9860ff6-0207-40ae-b2dd-115d7c7956b8
  InstallationDate: Installed on 2016-12-19 (439 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57d6 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 25a7:0701  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: \\boot\vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=070ac60f-63d1-48e3-9322-44812d365c40 ro quiet splash radeon.runpm=1 
vt.handoff=7 initrd=boot\initrd.img-4.13.0-36-generic
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-20 (135 days ago)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 11/24/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8136
  dmi.board.vendor: HP
  dmi.board.version: 31.34
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1D:bd11/24/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8136:rvr31.34:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752829/+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 1752829] ProcModules.txt

2018-03-04 Thread Yassine
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1752829/+attachment/5068804/+files/ProcModules.txt

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

Title:
  AMD HAINAN (Radeon R5 M330) Clock frequency is 750MHz while it is
  supposed to be 1030MHz

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel source: /drivers/gpu/drm/radeon/si_dpm.c line 2985:

  max_sclk = 75000;

  instead of

  max_sclk = 103000;

  Why is that? I changed it and rebuilt the kernel, and I can say that
  there are absolutely no issues when using the 1030MHz clock, which is
  what it is supposed to be.

  Linux Version: 4.13.0-36-generic

  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yassine3068 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=e9860ff6-0207-40ae-b2dd-115d7c7956b8
  InstallationDate: Installed on 2016-12-19 (439 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57d6 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 25a7:0701  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: \\boot\vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=070ac60f-63d1-48e3-9322-44812d365c40 ro quiet splash radeon.runpm=1 
vt.handoff=7 initrd=boot\initrd.img-4.13.0-36-generic
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-20 (135 days ago)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 11/24/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8136
  dmi.board.vendor: HP
  dmi.board.version: 31.34
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1D:bd11/24/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8136:rvr31.34:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752829/+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 1752829] CurrentDmesg.txt

2018-03-04 Thread Yassine
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1752829/+attachment/5068796/+files/CurrentDmesg.txt

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

Title:
  AMD HAINAN (Radeon R5 M330) Clock frequency is 750MHz while it is
  supposed to be 1030MHz

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel source: /drivers/gpu/drm/radeon/si_dpm.c line 2985:

  max_sclk = 75000;

  instead of

  max_sclk = 103000;

  Why is that? I changed it and rebuilt the kernel, and I can say that
  there are absolutely no issues when using the 1030MHz clock, which is
  what it is supposed to be.

  Linux Version: 4.13.0-36-generic

  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yassine3068 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=e9860ff6-0207-40ae-b2dd-115d7c7956b8
  InstallationDate: Installed on 2016-12-19 (439 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57d6 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 25a7:0701  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: \\boot\vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=070ac60f-63d1-48e3-9322-44812d365c40 ro quiet splash radeon.runpm=1 
vt.handoff=7 initrd=boot\initrd.img-4.13.0-36-generic
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-20 (135 days ago)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 11/24/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8136
  dmi.board.vendor: HP
  dmi.board.version: 31.34
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1D:bd11/24/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8136:rvr31.34:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752829/+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 1752829] Re: AMD HAINAN (Radeon R5 M330) Clock frequency is 750MHz while it is supposed to be 1030MHz

2018-03-04 Thread Yassine
apport information

** Tags added: apport-collected artful wayland-session

** Description changed:

  Kernel source: /drivers/gpu/drm/radeon/si_dpm.c line 2985:
  
  max_sclk = 75000;
  
  instead of
  
  max_sclk = 103000;
  
  Why is that? I changed it and rebuilt the kernel, and I can say that
  there are absolutely no issues when using the 1030MHz clock, which is
  what it is supposed to be.
  
  Linux Version: 4.13.0-36-generic
+ 
+ --- 
+ ApportVersion: 2.20.7-0ubuntu3.7
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  yassine3068 F pulseaudio
+ CurrentDesktop: GNOME
+ DistroRelease: Ubuntu 17.10
+ HibernationDevice: RESUME=UUID=e9860ff6-0207-40ae-b2dd-115d7c7956b8
+ InstallationDate: Installed on 2016-12-19 (439 days ago)
+ InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 005: ID 0bda:57d6 Realtek Semiconductor Corp. 
+  Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. 
+  Bus 001 Device 002: ID 25a7:0701  
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: HP HP Notebook
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: \\boot\vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=070ac60f-63d1-48e3-9322-44812d365c40 ro quiet splash radeon.runpm=1 
vt.handoff=7 initrd=boot\initrd.img-4.13.0-36-generic
+ ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
+ RelatedPackageVersions:
+  linux-restricted-modules-4.13.0-36-generic N/A
+  linux-backports-modules-4.13.0-36-generic  N/A
+  linux-firmware 1.169.3
+ Tags:  artful wayland-session
+ Uname: Linux 4.13.0-36-generic x86_64
+ UpgradeStatus: Upgraded to artful on 2017-10-20 (135 days ago)
+ UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo video
+ _MarkForUpload: True
+ dmi.bios.date: 11/24/2015
+ dmi.bios.vendor: Insyde
+ dmi.bios.version: F.1D
+ dmi.board.asset.tag: Type2 - Board Asset Tag
+ dmi.board.name: 8136
+ dmi.board.vendor: HP
+ dmi.board.version: 31.34
+ dmi.chassis.asset.tag: Chassis Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: HP
+ dmi.chassis.version: Chassis Version
+ dmi.modalias: 
dmi:bvnInsyde:bvrF.1D:bd11/24/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8136:rvr31.34:cvnHP:ct10:cvrChassisVersion:
+ dmi.product.family: 103C_5335KV G=N L=CON B=HP
+ dmi.product.name: HP Notebook
+ dmi.product.version: Type1ProductConfigId
+ dmi.sys.vendor: HP

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1752829/+attachment/5068794/+files/AlsaInfo.txt

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

Title:
  AMD HAINAN (Radeon R5 M330) Clock frequency is 750MHz while it is
  supposed to be 1030MHz

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel source: /drivers/gpu/drm/radeon/si_dpm.c line 2985:

  max_sclk = 75000;

  instead of

  max_sclk = 103000;

  Why is that? I changed it and rebuilt the kernel, and I can say that
  there are absolutely no issues when using the 1030MHz clock, which is
  what it is supposed to be.

  Linux Version: 4.13.0-36-generic

  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yassine3068 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=e9860ff6-0207-40ae-b2dd-115d7c7956b8
  InstallationDate: Installed on 2016-12-19 (439 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57d6 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 25a7:0701  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: \\boot\vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=070ac60f-63d1-48e3-9322-44812d365c40 ro quiet splash radeon.runpm=1 
vt.handoff=7 initrd=boot\initrd.img-4.13.0-36-generic
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-20 (135 days ago)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 11/24/2015
  d

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

2018-03-04 Thread Yassine
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1752829/+attachment/5068800/+files/ProcCpuinfo.txt

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

Title:
  AMD HAINAN (Radeon R5 M330) Clock frequency is 750MHz while it is
  supposed to be 1030MHz

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel source: /drivers/gpu/drm/radeon/si_dpm.c line 2985:

  max_sclk = 75000;

  instead of

  max_sclk = 103000;

  Why is that? I changed it and rebuilt the kernel, and I can say that
  there are absolutely no issues when using the 1030MHz clock, which is
  what it is supposed to be.

  Linux Version: 4.13.0-36-generic

  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yassine3068 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=e9860ff6-0207-40ae-b2dd-115d7c7956b8
  InstallationDate: Installed on 2016-12-19 (439 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57d6 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 25a7:0701  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: \\boot\vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=070ac60f-63d1-48e3-9322-44812d365c40 ro quiet splash radeon.runpm=1 
vt.handoff=7 initrd=boot\initrd.img-4.13.0-36-generic
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-20 (135 days ago)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 11/24/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8136
  dmi.board.vendor: HP
  dmi.board.version: 31.34
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1D:bd11/24/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8136:rvr31.34:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752829/+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 1752829] Lspci.txt

2018-03-04 Thread Yassine
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1752829/+attachment/5068799/+files/Lspci.txt

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

Title:
  AMD HAINAN (Radeon R5 M330) Clock frequency is 750MHz while it is
  supposed to be 1030MHz

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel source: /drivers/gpu/drm/radeon/si_dpm.c line 2985:

  max_sclk = 75000;

  instead of

  max_sclk = 103000;

  Why is that? I changed it and rebuilt the kernel, and I can say that
  there are absolutely no issues when using the 1030MHz clock, which is
  what it is supposed to be.

  Linux Version: 4.13.0-36-generic

  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yassine3068 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=e9860ff6-0207-40ae-b2dd-115d7c7956b8
  InstallationDate: Installed on 2016-12-19 (439 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57d6 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 25a7:0701  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: \\boot\vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=070ac60f-63d1-48e3-9322-44812d365c40 ro quiet splash radeon.runpm=1 
vt.handoff=7 initrd=boot\initrd.img-4.13.0-36-generic
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-20 (135 days ago)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 11/24/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8136
  dmi.board.vendor: HP
  dmi.board.version: 31.34
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1D:bd11/24/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8136:rvr31.34:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752829/+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 1752829] IwConfig.txt

2018-03-04 Thread Yassine
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1752829/+attachment/5068797/+files/IwConfig.txt

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

Title:
  AMD HAINAN (Radeon R5 M330) Clock frequency is 750MHz while it is
  supposed to be 1030MHz

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel source: /drivers/gpu/drm/radeon/si_dpm.c line 2985:

  max_sclk = 75000;

  instead of

  max_sclk = 103000;

  Why is that? I changed it and rebuilt the kernel, and I can say that
  there are absolutely no issues when using the 1030MHz clock, which is
  what it is supposed to be.

  Linux Version: 4.13.0-36-generic

  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yassine3068 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=e9860ff6-0207-40ae-b2dd-115d7c7956b8
  InstallationDate: Installed on 2016-12-19 (439 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57d6 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 25a7:0701  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: \\boot\vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=070ac60f-63d1-48e3-9322-44812d365c40 ro quiet splash radeon.runpm=1 
vt.handoff=7 initrd=boot\initrd.img-4.13.0-36-generic
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-20 (135 days ago)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 11/24/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8136
  dmi.board.vendor: HP
  dmi.board.version: 31.34
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1D:bd11/24/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8136:rvr31.34:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752829/+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 1752829] ProcCpuinfoMinimal.txt

2018-03-04 Thread Yassine
apport information

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

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

Title:
  AMD HAINAN (Radeon R5 M330) Clock frequency is 750MHz while it is
  supposed to be 1030MHz

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel source: /drivers/gpu/drm/radeon/si_dpm.c line 2985:

  max_sclk = 75000;

  instead of

  max_sclk = 103000;

  Why is that? I changed it and rebuilt the kernel, and I can say that
  there are absolutely no issues when using the 1030MHz clock, which is
  what it is supposed to be.

  Linux Version: 4.13.0-36-generic

  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yassine3068 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=e9860ff6-0207-40ae-b2dd-115d7c7956b8
  InstallationDate: Installed on 2016-12-19 (439 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57d6 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 25a7:0701  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: \\boot\vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=070ac60f-63d1-48e3-9322-44812d365c40 ro quiet splash radeon.runpm=1 
vt.handoff=7 initrd=boot\initrd.img-4.13.0-36-generic
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-20 (135 days ago)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 11/24/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8136
  dmi.board.vendor: HP
  dmi.board.version: 31.34
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1D:bd11/24/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8136:rvr31.34:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752829/+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 1752829] ProcEnviron.txt

2018-03-04 Thread Yassine
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1752829/+attachment/5068802/+files/ProcEnviron.txt

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

Title:
  AMD HAINAN (Radeon R5 M330) Clock frequency is 750MHz while it is
  supposed to be 1030MHz

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel source: /drivers/gpu/drm/radeon/si_dpm.c line 2985:

  max_sclk = 75000;

  instead of

  max_sclk = 103000;

  Why is that? I changed it and rebuilt the kernel, and I can say that
  there are absolutely no issues when using the 1030MHz clock, which is
  what it is supposed to be.

  Linux Version: 4.13.0-36-generic

  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yassine3068 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=e9860ff6-0207-40ae-b2dd-115d7c7956b8
  InstallationDate: Installed on 2016-12-19 (439 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57d6 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 25a7:0701  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: \\boot\vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=070ac60f-63d1-48e3-9322-44812d365c40 ro quiet splash radeon.runpm=1 
vt.handoff=7 initrd=boot\initrd.img-4.13.0-36-generic
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-20 (135 days ago)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 11/24/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8136
  dmi.board.vendor: HP
  dmi.board.version: 31.34
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1D:bd11/24/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8136:rvr31.34:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752829/+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 1752829] CRDA.txt

2018-03-04 Thread Yassine
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1752829/+attachment/5068795/+files/CRDA.txt

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

Title:
  AMD HAINAN (Radeon R5 M330) Clock frequency is 750MHz while it is
  supposed to be 1030MHz

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel source: /drivers/gpu/drm/radeon/si_dpm.c line 2985:

  max_sclk = 75000;

  instead of

  max_sclk = 103000;

  Why is that? I changed it and rebuilt the kernel, and I can say that
  there are absolutely no issues when using the 1030MHz clock, which is
  what it is supposed to be.

  Linux Version: 4.13.0-36-generic

  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yassine3068 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=e9860ff6-0207-40ae-b2dd-115d7c7956b8
  InstallationDate: Installed on 2016-12-19 (439 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57d6 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 25a7:0701  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: \\boot\vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=070ac60f-63d1-48e3-9322-44812d365c40 ro quiet splash radeon.runpm=1 
vt.handoff=7 initrd=boot\initrd.img-4.13.0-36-generic
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-20 (135 days ago)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 11/24/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8136
  dmi.board.vendor: HP
  dmi.board.version: 31.34
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1D:bd11/24/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8136:rvr31.34:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752829/+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 1752829] JournalErrors.txt

2018-03-04 Thread Yassine
apport information

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

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

Title:
  AMD HAINAN (Radeon R5 M330) Clock frequency is 750MHz while it is
  supposed to be 1030MHz

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel source: /drivers/gpu/drm/radeon/si_dpm.c line 2985:

  max_sclk = 75000;

  instead of

  max_sclk = 103000;

  Why is that? I changed it and rebuilt the kernel, and I can say that
  there are absolutely no issues when using the 1030MHz clock, which is
  what it is supposed to be.

  Linux Version: 4.13.0-36-generic

  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yassine3068 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=e9860ff6-0207-40ae-b2dd-115d7c7956b8
  InstallationDate: Installed on 2016-12-19 (439 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57d6 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 25a7:0701  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: \\boot\vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=070ac60f-63d1-48e3-9322-44812d365c40 ro quiet splash radeon.runpm=1 
vt.handoff=7 initrd=boot\initrd.img-4.13.0-36-generic
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-20 (135 days ago)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 11/24/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8136
  dmi.board.vendor: HP
  dmi.board.version: 31.34
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1D:bd11/24/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8136:rvr31.34:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752829/+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 1752621] Re: BUG: unable to handle kernel paging request at ffffded5330000a0

2018-03-04 Thread A. Sidorov
error disappears after I removed the apparmor=0 from kernel parameters

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

Title:
  BUG: unable to handle kernel paging request at ded533a0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [  155.111268] BUG: unable to handle kernel paging request at ded533a0
  [  155.111335] IP: kfree+0x53/0x160
  [  155.111357] PGD 0 
  [  155.111358] P4D 0 

  [  155.111401] Oops:  [#1] SMP PTI
  [  155.111424] Modules linked in: gpio_ich intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm 
snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel irqbypass 
snd_hda_codec snd_hda_core crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
pcbc aesni_intel snd_hwdep aes_x86_64 crypto_simd snd_pcm snd_seq_midi 
snd_seq_midi_event snd_rawmidi joydev input_leds glue_helper snd_seq 
snd_seq_device cryptd snd_timer intel_cstate intel_rapl_perf mei_me shpchp snd 
mei soundcore lpc_ich mac_hid serio_raw parport_pc ppdev lp parport ip_tables 
x_tables autofs4 hid_generic usbhid hid i915 video i2c_algo_bit drm_kms_helper 
syscopyarea sysfillrect sysimgblt ahci fb_sys_fops r8169 libahci drm mii
  [  155.111809] CPU: 0 PID: 1587 Comm: postgres Not tainted 4.13.0-36-generic 
#40-Ubuntu
  [  155.111853] Hardware name: Gigabyte Technology Co., Ltd. 
H67A-USB3-B3/H67A-USB3-B3, BIOS F7 03/27/2012
  [  155.111906] task: 8e971b4845c0 task.stack: 9c1bc2e7c000
  [  155.111942] RIP: 0010:kfree+0x53/0x160
  [  155.111966] RSP: 0018:9c1bc2e7fce8 EFLAGS: 00010282
  [  155.111998] RAX:  RBX: 00102aa3 RCX: 
0003
  [  155.112039] RDX: 2d8460201cf0 RSI: 00010080 RDI: 
716c4000
  [  155.112080] RBP: 9c1bc2e7fd00 R08: 00025d80 R09: 
bafc6a19
  [  155.112121] R10: ded53380 R11:  R12: 
8e974abe7800
  [  155.112162] R13: baba74d4 R14:  R15: 
8e9714f4d3c0
  [  155.112204] FS:  () GS:8e975fa0() 
knlGS:
  [  155.112250] CS:  0010 DS:  ES:  CR0: 80050033
  [  155.112285] CR2: ded533a0 CR3: 00022c20a001 CR4: 
000606f0
  [  155.112326] Call Trace:
  [  155.112349]  security_sk_free+0x44/0x60
  [  155.112377]  __sk_destruct+0x10b/0x190
  [  155.112403]  sk_destruct+0x20/0x30
  [  155.112427]  __sk_free+0x82/0xa0
  [  155.112451]  sk_free+0x19/0x20
  [  155.112472]  tcp_close+0x238/0x3f0
  [  155.112498]  inet_release+0x42/0x70
  [  155.112522]  sock_release+0x25/0x80
  [  155.112546]  sock_close+0x12/0x20
  [  155.114960]  __fput+0xea/0x230
  [  155.117332]  fput+0xe/0x10
  [  155.119604]  task_work_run+0x7c/0xa0
  [  155.121861]  do_exit+0x2d2/0xae0
  [  155.124100]  ? entry_SYSCALL_64_after_hwframe+0xd4/0x139
  [  155.126330]  ? entry_SYSCALL_64_after_hwframe+0xc6/0x139
  [  155.128524]  ? entry_SYSCALL_64_after_hwframe+0xbf/0x139
  [  155.130674]  ? entry_SYSCALL_64_after_hwframe+0xb8/0x139
  [  155.132757]  ? entry_SYSCALL_64_after_hwframe+0xb1/0x139
  [  155.134769]  do_group_exit+0x43/0xb0
  [  155.136307]  SyS_exit_group+0x14/0x20
  [  155.138219]  entry_SYSCALL_64_fastpath+0x24/0xab
  [  155.140110] RIP: 0033:0x7fe7b4851fd8
  [  155.141984] RSP: 002b:7ffe7f1d1e88 EFLAGS: 0246 ORIG_RAX: 
00e7
  [  155.143882] RAX: ffda RBX: 563529f04030 RCX: 
7fe7b4851fd8
  [  155.145590] RDX:  RSI: 003c RDI: 

  [  155.147316] RBP: 7ffe7f1d1e80 R08: 00e7 R09: 
fef8
  [  155.148956] R10: 7fe7acf95148 R11: 0246 R12: 
7fe7acf94d90
  [  155.150230] R13: 0036 R14:  R15: 
7ffe7f1d1c10
  [  155.151492] Code: 00 80 49 01 da 0f 82 1f 01 00 00 48 c7 c7 00 00 00 80 48 
2b 3d 4f b2 01 01 49 01 fa 49 c1 ea 0c 49 c1 e2 06 4c 03 15 2d b2 01 01 <49> 8b 
42 20 48 8d 50 ff a8 01 4c 0f 45 d2 49 8b 52 20 48 8d 42 
  [  155.152892] RIP: kfree+0x53/0x160 RSP: 9c1bc2e7fce8
  [  155.154283] CR2: ded533a0
  [  155.167949] ---[ end trace 28ca6dd18121abd3 ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-36-generic 4.13.0-36.40
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   1058 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  1 20:51:56 2018
  HibernationDevice: RESUME=UUID=dcaa0aaf-ec9b-4eec-962b-498d547772f5
  InstallationDate: Installed on 2018-02-23 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wi

[Kernel-packages] [Bug 1753010] Re: after recent updates playing youtube videos in firefox causes sometimes freezing of the system

2018-03-04 Thread Kamil
Right now the system freezed on opening complex js widget in Chromium with 
opened debugger.
No Firefox and no Youtube were opened.

So, it looks freezing occurs mainly on any kind of operations requiring
relatively heavy processor work.

Editing text files, browsing texts/images online, checking mail in
Thunderbird may be done for hours without any 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/1753010

Title:
  after recent updates playing youtube videos in firefox causes
  sometimes freezing of the system

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After recent updates that fixed the bug
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742675 on my
  computer the following different bug has appeared. Playing Youtube
  music videos (static picture + music, length 40-70 minutes) in Firefox
  (as background for other activities on computer) causes sometimes
  (rather often, up to several times per day) freezing of the system.
  And only restart through reset button can help.

  Initially I though that it is related to different Javascript-related
  tasks (manipulating with complex widgets in Chromium, running heavy
  gulp tasks through yarn) but it looks they are not the reason (or at
  least not the main reason). Because right now I have seen the problem
  when keyboard/mouse was not touched at all.

  That's why I think this information is rather enough; and I decided to post 
this bug.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kamil  2021 F pulseaudio
   /dev/snd/controlC1:  kamil  2021 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=5b5ffc28-8999-4ad7-9ff3-f3298c4f28c2
  InstallationDate: Installed on 2017-06-23 (252 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  MachineType: Packard Bell Easynote ENTE70BH
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=557e3c22-0c8c-44b3-a8f6-5446013327ad ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  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.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.157.17
  Tags:  xenial
  Uname: Linux 4.13.0-36-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/08/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.05
  dmi.board.name: Easynote ENTE70BH
  dmi.board.vendor: Packard Bell
  dmi.board.version: V1.05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Packard Bell
  dmi.chassis.version: V1.05
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.05:bd08/08/2016:svnPackardBell:pnEasynoteENTE70BH:pvrV1.05:rvnPackardBell:rnEasynoteENTE70BH:rvrV1.05:cvnPackardBell:ct10:cvrV1.05:
  dmi.product.family: BDW
  dmi.product.name: Easynote ENTE70BH
  dmi.product.version: V1.05
  dmi.sys.vendor: Packard Bell

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753010/+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