date:20180415

[Kernel-packages] [Bug 1758496] Re: Backlight does not work on a MacBookAir3, 2

2018-04-15 Thread Kai-Heng Feng

When you use "acpi_backlight=vendor", is /sys/class/backlight still
empty?

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

Title:
  Backlight does not work on a MacBookAir3,2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Backlight control does not work and there are no entries in
  /sys/class/backlight. When I boot my system with the option
  GRUB_CMDLINE_LINUX_DEFAULT="acpi_backlight=vendor" I can change the
  brightness with the command xrandr on a terminal.

  I attach all the system information about this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-37-generic 4.13.0-37.42
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  victor 2932 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 24 07:22:05 2018
  InstallationDate: Installed on 2018-03-04 (19 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Apple Inc. MacBookAir3,2
  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-37-generic.efi.signed 
root=UUID=dd2bcce2-7d14-4df7-b7c8-6aea4fbb9c13 ro acpi_backlight=vendor
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-37-generic N/A
   linux-backports-modules-4.13.0-37-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/10
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA31.88Z.0061.B01.1011181342
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-942C5DF58193131B
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir3,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-942C5DF58193131B
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA31.88Z.0061.B01.1011181342:bd11/18/10:svnAppleInc.:pnMacBookAir3,2:pvr1.0:rvnAppleInc.:rnMac-942C5DF58193131B:rvrMacBookAir3,2:cvnAppleInc.:ct10:cvrMac-942C5DF58193131B:
  dmi.product.family: MacBook
  dmi.product.name: MacBookAir3,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758496/+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 1762844] Comment bridged from LTC Bugzilla

2018-04-15 Thread bugproxy

--- Comment From indira.pr...@in.ibm.com 2018-04-16 01:24 EDT---
(In reply to comment #54)
> Please collect the dmesg log and a crashdump.

Collected dl logs from xmon prompt & unable to take crashdump from xmon
prompt  ,we have bug#10 opened.

Regards,
Indira

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

  root@boslcp3:~# [   66.295233] Unable to handle kernel paging request for 
data at address 0x8882f6ed90e9151a
  [   66.295297] Faulting instruction address: 0xc038a110
  cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650]
  pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350
  lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350
  sp: c692f8d0
 msr: 90009033
 dar: 8882f6ed90e9151a
current = 0xc698fd00
paca= 0xcfab7000   softe: 0irq_happened: 0x01
  pid   = 1762, comm = systemd-journal
  Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 
(Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 
4.15.0-15.16-generic 4.15.15)
  enter ? for help
  [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
  [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0
  [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90
  [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390
  [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0
  [c692fe30] c000b184 system_call+0x58/0x6c
  --- Exception: c00 (System Call) at 74826f6fa9c4
  SP (75dc5510) is in userspace
  50:mon>
  50:mon>

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c000200e0b20f9a0]

[Kernel-packages] [Bug 1762844] dmesg logs from xmon prompt_boslcp3

2018-04-15 Thread bugproxy

--- Comment on attachment From indira.pr...@in.ibm.com 2018-04-16 01:31 
EDT---


Attached dl logs from xmon pormpt _boslcp3

** Attachment added: "dmesg logs from xmon prompt_boslcp3"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5117547/+files/dmesg_xmon_boslcp3.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/1762844

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

  root@boslcp3:~# [   66.295233] Unable to handle kernel paging request for 
data at address 0x8882f6ed90e9151a
  [   66.295297] Faulting instruction address: 0xc038a110
  cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650]
  pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350
  lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350
  sp: c692f8d0
 msr: 90009033
 dar: 8882f6ed90e9151a
current = 0xc698fd00
paca= 0xcfab7000   softe: 0irq_happened: 0x01
  pid   = 1762, comm = systemd-journal
  Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 
(Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 
4.15.0-15.16-generic 4.15.15)
  enter ? for help
  [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
  [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0
  [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90
  [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390
  [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0
  [c692fe30] c000b184 system_call+0x58/0x6c
  --- Exception: c00 (System Call) at 74826f6fa9c4
  SP (75dc5510) is in userspace
  50:mon>
  50:mon>

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220

[Kernel-packages] [Bug 1751887] Re: The brightness of the screen cannot be adjusted with either the buttons or the slider.

2018-04-15 Thread Kai-Heng Feng

Can you attach acpidump? Thanks!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 1751887] Re: The brightness of the screen cannot be adjusted with either the buttons or the slider.

2018-04-15 Thread Kai-Heng Feng

Also, do you add "acpi_osi=Linux" for any reason?

-- 
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 1764246] Status changed to Confirmed

2018-04-15 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/1764246

Title:
  kdump kernel panics on Bionic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The kdump/crashdump kernel is panicing during boot on Bionic.

  1) Install the daily Bionic server or desktop ISO
  2) apt install linux-crashdump, say yes to kdump being enabled
  3) Reboot so as to boot with the correct kernel parameter
  4) Run:
  root@bionic-server:~# echo 1 > /proc/sys/kernel/sysrq 
  root@bionic-server:~# echo c > /proc/sysrq-trigger 
  5) Observe that the crashdump kernel panics before booting with an 
out-of-memory error. Log below.

  If I replace the bionic image with the artful cloud image, and repeat
  steps 2-4, the crashdump kernel boots and successfully stores the
  vmcore.

  The full log:

  [   54.424512] sysrq: SysRq : Trigger a crash
  [   54.427899] BUG: unable to handle kernel NULL pointer dereference at 

  [   54.433915] IP: sysrq_handle_crash+0x16/0x20
  [   54.437157] PGD 0 P4D 0 
  [   54.439292] Oops: 0002 [#1] SMP PTI
  [   54.444571] Modules linked in: snd_hda_codec_generic crct10dif_pclmul 
crc32_pclmul snd_hda_intel ghash_clmulni_intel snd_hda_codec snd_hda_core 
snd_hwdep input_leds joydev snd_pcm serio_raw snd_timer snd soundcore 
qemu_fw_cfg mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp 
libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid 
hid qxl aesni_intel ttm drm_kms_helper aes_x86_64 crypto_simd cryptd 
glue_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse virtio_blk 
virtio_net drm i2c_piix4 pata_acpi floppy
  [   54.468925] CPU: 0 PID: 1075 Comm: bash Not tainted 4.15.0-15-generic 
#16-Ubuntu
  [   54.470377] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [   54.472016] RIP: 0010:sysrq_handle_crash+0x16/0x20
  [   54.472891] RSP: 0018:a3a000643e30 EFLAGS: 00010286
  [   54.473826] RAX: 917e0950 RBX: 92787200 RCX: 

  [   54.475092] RDX:  RSI: 90dfbfc16498 RDI: 
0063
  [   54.476182] RBP: a3a000643e30 R08:  R09: 
022b
  [   54.477272] R10: 0001 R11: 92b5280d R12: 
0004
  [   54.478361] R13: 0063 R14: 0002 R15: 
90dfbab0ef00
  [   54.479456] FS:  7ff6248af740() GS:90dfbfc0() 
knlGS:
  [   54.480602] CS:  0010 DS:  ES:  CR0: 80050033
  [   54.481379] CR2:  CR3: 7bcb2006 CR4: 
003606f0
  [   54.482341] Call Trace:
  [   54.482690]  __handle_sysrq+0x9f/0x170
  [   54.483207]  write_sysrq_trigger+0x34/0x40
  [   54.483775]  proc_reg_write+0x45/0x70
  [   54.484281]  __vfs_write+0x1b/0x40
  [   54.484751]  vfs_write+0xb1/0x1a0
  [   54.485208]  SyS_write+0x55/0xc0
  [   54.485669]  do_syscall_64+0x73/0x130
  [   54.486156]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [   54.486784] RIP: 0033:0x7ff623f84154
  [   54.487328] RSP: 002b:7ffe5f399678 EFLAGS: 0246 ORIG_RAX: 
0001
  [   54.488272] RAX: ffda RBX: 0002 RCX: 
7ff623f84154
  [   54.489179] RDX: 0002 RSI: 55a5a49151c0 RDI: 
0001
  [   54.490313] RBP: 55a5a49151c0 R08: 000a R09: 
0001
  [   54.491179] R10: 000a R11: 0246 R12: 
7ff624260760
  [   54.492311] R13: 0002 R14: 7ff62425c2a0 R15: 
7ff62425b760
  [   54.493124] Code: e7 e8 9f fb ff ff e9 c0 fe ff ff 90 90 90 90 90 90 90 90 
90 90 0f 1f 44 00 00 55 c7 05 a8 a7 36 01 01 00 00 00 48 89 e5 0f ae f8  04 
25 00 00 00 00 01 5d c3 0f 1f 44 00 00 55 c7 05 40 1f e8 
  [   54.496461] RIP: sysrq_handle_crash+0x16/0x20 RSP: a3a000643e30
  [   54.497393] CR2: 
  [0.00] Linux version 4.15.0-15-generic (buildd@lgw01-amd64-050) (gcc 
version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:58:14 UTC 
2018 (Ubuntu 4.15.0-15.16-generic 4.15.15)
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=3e45b7ec-412a-11e8-a844-5254003896a5 ro maybe-ubiquity console=ttyS0 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll nousb 
ata_piix.prefer_ms_hyperv=0 elfcorehdr=802164K
  [0.00] KERNEL supported cpus:
  [0.00]   Intel GenuineIntel
  [0.00]   AMD AuthenticAMD
  [0.00]   Centaur CentaurHauls
  [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
  [0.00] x86/fpu: Supporting XSAVE feature 0x002:

[Kernel-packages] [Bug 1764246] [NEW] kdump kernel panics on Bionic

2018-04-15 Thread Daniel Axtens

Public bug reported:

The kdump/crashdump kernel is panicing during boot on Bionic.

1) Install the daily Bionic server or desktop ISO
2) apt install linux-crashdump, say yes to kdump being enabled
3) Reboot so as to boot with the correct kernel parameter
4) Run:
root@bionic-server:~# echo 1 > /proc/sys/kernel/sysrq 
root@bionic-server:~# echo c > /proc/sysrq-trigger 
5) Observe that the crashdump kernel panics before booting with an 
out-of-memory error. Log below.

If I replace the bionic image with the artful cloud image, and repeat
steps 2-4, the crashdump kernel boots and successfully stores the
vmcore.

The full log:

[   54.424512] sysrq: SysRq : Trigger a crash
[   54.427899] BUG: unable to handle kernel NULL pointer dereference at 

[   54.433915] IP: sysrq_handle_crash+0x16/0x20
[   54.437157] PGD 0 P4D 0 
[   54.439292] Oops: 0002 [#1] SMP PTI
[   54.444571] Modules linked in: snd_hda_codec_generic crct10dif_pclmul 
crc32_pclmul snd_hda_intel ghash_clmulni_intel snd_hda_codec snd_hda_core 
snd_hwdep input_leds joydev snd_pcm serio_raw snd_timer snd soundcore 
qemu_fw_cfg mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp 
libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid 
hid qxl aesni_intel ttm drm_kms_helper aes_x86_64 crypto_simd cryptd 
glue_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse virtio_blk 
virtio_net drm i2c_piix4 pata_acpi floppy
[   54.468925] CPU: 0 PID: 1075 Comm: bash Not tainted 4.15.0-15-generic 
#16-Ubuntu
[   54.470377] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
[   54.472016] RIP: 0010:sysrq_handle_crash+0x16/0x20
[   54.472891] RSP: 0018:a3a000643e30 EFLAGS: 00010286
[   54.473826] RAX: 917e0950 RBX: 92787200 RCX: 
[   54.475092] RDX:  RSI: 90dfbfc16498 RDI: 0063
[   54.476182] RBP: a3a000643e30 R08:  R09: 022b
[   54.477272] R10: 0001 R11: 92b5280d R12: 0004
[   54.478361] R13: 0063 R14: 0002 R15: 90dfbab0ef00
[   54.479456] FS:  7ff6248af740() GS:90dfbfc0() 
knlGS:
[   54.480602] CS:  0010 DS:  ES:  CR0: 80050033
[   54.481379] CR2:  CR3: 7bcb2006 CR4: 003606f0
[   54.482341] Call Trace:
[   54.482690]  __handle_sysrq+0x9f/0x170
[   54.483207]  write_sysrq_trigger+0x34/0x40
[   54.483775]  proc_reg_write+0x45/0x70
[   54.484281]  __vfs_write+0x1b/0x40
[   54.484751]  vfs_write+0xb1/0x1a0
[   54.485208]  SyS_write+0x55/0xc0
[   54.485669]  do_syscall_64+0x73/0x130
[   54.486156]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[   54.486784] RIP: 0033:0x7ff623f84154
[   54.487328] RSP: 002b:7ffe5f399678 EFLAGS: 0246 ORIG_RAX: 
0001
[   54.488272] RAX: ffda RBX: 0002 RCX: 7ff623f84154
[   54.489179] RDX: 0002 RSI: 55a5a49151c0 RDI: 0001
[   54.490313] RBP: 55a5a49151c0 R08: 000a R09: 0001
[   54.491179] R10: 000a R11: 0246 R12: 7ff624260760
[   54.492311] R13: 0002 R14: 7ff62425c2a0 R15: 7ff62425b760
[   54.493124] Code: e7 e8 9f fb ff ff e9 c0 fe ff ff 90 90 90 90 90 90 90 90 
90 90 0f 1f 44 00 00 55 c7 05 a8 a7 36 01 01 00 00 00 48 89 e5 0f ae f8  04 
25 00 00 00 00 01 5d c3 0f 1f 44 00 00 55 c7 05 40 1f e8 
[   54.496461] RIP: sysrq_handle_crash+0x16/0x20 RSP: a3a000643e30
[   54.497393] CR2: 
[0.00] Linux version 4.15.0-15-generic (buildd@lgw01-amd64-050) (gcc 
version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:58:14 UTC 
2018 (Ubuntu 4.15.0-15.16-generic 4.15.15)
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=3e45b7ec-412a-11e8-a844-5254003896a5 ro maybe-ubiquity console=ttyS0 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll nousb 
ata_piix.prefer_ms_hyperv=0 elfcorehdr=802164K
[0.00] KERNEL supported cpus:
[0.00]   Intel GenuineIntel
[0.00]   AMD AuthenticAMD
[0.00]   Centaur CentaurHauls
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, 
using 'standard' format.
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x1000-0x0009fbff] usable
[0.00] BIOS-e820: [mem 0x2900-0x30f5cfff]

[Kernel-packages] [Bug 1749214] Re: default vers value when mounting cifs shares with mount.cifs not working

2018-04-15 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/1749214

Title:
  default vers value when mounting cifs shares with mount.cifs not
  working

Status in linux package in Ubuntu:
  Expired

Bug description:
  Firstly, apologies if this isn't a bug in cifs.mount - I know it's
  intimitly connected to a recent kernel updates which changed the
  default SMB version cifs connects with, but I'm having trouble
  distinguishing whether this behaviour is caused by the kernel change
  or a problem with cifs.

  On a recently built 16.04.3 LTS box with kernel 4.4.0-109, I was able
  to mount to a network DFS share with the following

  mount.cifs -o user=username //pathto/share /mountpoint

  and after doing so, I was able to navigate through the mounted share,
  and through the underlying DFS structure with no problems.  The mount
  command notably contained 'vers=1.0' - which was expected.

  After updating the kernel to 4.13.0.32, if I run the same command, the
  share appears to mount, but I get a 'cannot access ...: Input/Output
  error' when trying to move through a DFS mount within the mounted
  filesystem.

  Notably, the output from the mount command has 'vers=default'.

  I understand from various sources, that the default SMB vers is now
  3.0 - and if I mount this share explicitly with

  mount.cifs -o user=username,vers=3.0 //pathto/share /mountpoint

  Then I see 'vers=3' on the output from mount, and am able to use the
  share as expected.

  The man page for the cifs.mount cmd still says the default is SMB1.0
  (this appeared to be the case with a kernel previous to 4.13).  The
  kernel sources now say the default is SMB 3.0 - which would also be
  find, if the share is mounted with vers=3.0.

  But instead I'm seeing 'vers=default' - and I'm unsure as to what
  version of SMB it's actually trying to use (if any) - whatever it is,
  it doesn't work unless I explicitly set vers=3.0.

  Thanks
  Dave
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 13 12:02 seq
   crw-rw 1 root audio 116, 33 Feb 13 12:02 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  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: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=4d912473-ae08-4591-886b-eff2cb5edfd9
  InstallationDate: Installed on 2017-07-11 (217 days ago)
  InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.8)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=d702a195-430c-4bf2-9753-6618837863dc ro
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.157.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: oracle
  _MarkForUpload: True
  dmi.bios.date: 04/05/2016
  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:bd04/05/2016: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/1749214/+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 1749329] Re: BUG: Bad rss-counter state mm:ffff9ac8374f39c0 idx:1 val:1

2018-04-15 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/1749329

Title:
  BUG: Bad rss-counter state mm:9ac8374f39c0 idx:1 val:1

Status in linux package in Ubuntu:
  Expired

Bug description:
  No additional information.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-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:  gdm1204 F pulseaudio
bertadmin   1928 F pulseaudio
  Date: Tue Feb 13 20:59:15 2018
  Failure: oops
  InstallationDate: Installed on 2017-12-22 (53 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=f3311827-9a0c-490d-a707-d4d037152c4d ro quiet splash
  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: BUG: Bad rss-counter state mm:9ac8374f39c0 idx:1 val:1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749329/+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 1763273] Re: kernel panic in Radeon driver while screen blank

2018-04-15 Thread RBL Admin

While logged in via ssh to the machine with the "hung" Xorg (screen
blank, no way to recover except Alt-SysRq-k), I dumped the output of
Alt-SysRq-t into the syslog -- see attached file. Not sure this is much
use, however. Just trying to be complete while I'm on-site with a hung
machine.

** Attachment added: "syslog with output from Alt-SysRq-t in ssh session"

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117347/+files/syslog

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

Title:
kernel panic in Radeon driver while screen blank

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

Bug description:
I maintain a set of older kiosks running a mix of stock Ubuntu 14.04
LTS and 16.04. As we have gradually transitioned them to 16.04, we
have noticed that the machines running 16.04.1 now regularly exhibit
problems restoring from the blank screen which appears after a period
of inactivity.

This only occurs on the machines where we've installed 16.04. All of
the 16.04.1 installations are "fresh", that is, complete re-installs
from scratch, and we install all security and other updates on a
regular basis. This problem has persisted right from the beginning
when we started using 16.04.

Following a period of user inactivity, the screen goes blank; this is,
of course, expected. When the user tries to restore the session by
typing a key or moving the mouse, one of three outcomes occurs.

Sometimes, the session restores normally. Other times, the screen
remains blank regardless of all normal keyboard input, until a magic
SysRq sequence is performed. After Alt-SysRq-k, either the virtual
console resets to a login screen (as expected after this SysRq
sequence), or we get a kernel panic text screen (see attached screen
photo) and can only restore via a hard power-cycle reboot.

I will continue to try to capture a better trace output from one of
these conditions, perhaps from /var/log/kern.log or by installing
linux-crashdump (although these old machines may not have enough
memory for the stock package). But in the meantime, I'm attaching a
photo of the kernel panic we see, which suggests a problem may reside
in the Radeon driver ... which would seem possible, given the general
blank-screen no-resume problem on these systems.

Any advice on how to further capture any other needed details would be
appreciated. Thanks very much!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763273/+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 1763273] Re: kernel panic in Radeon driver while screen blank

2018-04-15 Thread RBL Admin

** Attachment added: "rom.vga.bin"

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117323/+files/rom.vga.bin

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

Title:
kernel panic in Radeon driver while screen blank

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

Any advice on how to further capture any other needed details would be
appreciated. Thanks very much!

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

[Kernel-packages] [Bug 1763273] Re: kernel panic in Radeon driver while screen blank

2018-04-15 Thread RBL Admin

** Attachment added: "Xorg.0.log"

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117322/+files/Xorg.0.log

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

Title:
kernel panic in Radeon driver while screen blank

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

Any advice on how to further capture any other needed details would be
appreciated. Thanks very much!

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

[Kernel-packages] [Bug 1763273] Re: kernel panic in Radeon driver while screen blank

2018-04-15 Thread RBL Admin

** Attachment added: "gdb-Xorg.txt"

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117324/+files/gdb-Xorg.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/1763273

Title:
kernel panic in Radeon driver while screen blank

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

Any advice on how to further capture any other needed details would be
appreciated. Thanks very much!

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

[Kernel-packages] [Bug 1763273] Re: kernel panic in Radeon driver while screen blank

2018-04-15 Thread RBL Admin

Further debugging today while I'm on-site with the kiosks.  The system
froze, as usual, after normal idle screen blanking.  I was able to login
via ssh and retrieve some details.

First, it appears that the basic screen blanking problem is somehow
related to the Radeon driver.  I will attach the Xorg.0.log file and a
gdb backtrace on the running but non-responsive Xorg process.  No
keyboard or mouse activity will un-blank the screen.

Here's the output from lspci | grep VGA:

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV516 
[Radeon X1300/X1550 Series]

I'll also attach the PCI ROM dump from the /sys/devices rom file for
this device.

This suggests that when we use Alt-SysRq-k to restore the system,
sometimes we trigger *another* bug in the driver which results in the
overall system crash.  See the attached apr1.full.kern.log file for what
details I could recover from the crash on April 1st; that corresponds to
the screen photo I took that day (the radeon_kernel_panic1.jpg
attachment).

The Xorg "hang" bug which precedes this appears similar, but not
identical, to what is documented in #1664979:

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1664979

I will continue to try to study the live Xorg process to see if I can
determine where its hung, but I may not have time this evening.  Let me
know if there are specific further debugging steps I can take to examine
either the Xorg hang or the subsequent crash which (sometimes) follows
on attempting to recover with Alt-SysRq-k.  (And note that I'll copy in
the files apport-bug generated from #1764211 later tonight, using my
"cdarroch" personal account, and then I'll try to close that extra bug
report.)

Thanks very much,
Chris.

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

Title:
  kernel panic in Radeon driver while screen blank

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

Bug description:
  I maintain a set of older kiosks running a mix of stock Ubuntu 14.04
  LTS and 16.04.  As we have gradually transitioned them to 16.04, we
  have noticed that the machines running 16.04.1 now regularly exhibit
  problems restoring from the blank screen which appears after a period
  of inactivity.

  This only occurs on the machines where we've installed 16.04.  All of
  the 16.04.1 installations are "fresh", that is, complete re-installs
  from scratch, and we install all security and other updates on a
  regular basis.  This problem has persisted right from the beginning
  when we started using 16.04.

  Following a period of user inactivity, the screen goes blank; this is,
  of course, expected.  When the user tries to restore the session by
  typing a key or moving the mouse, one of three outcomes occurs.

  Sometimes, the session restores normally.  Other times, the screen
  remains blank regardless of all normal keyboard input, until a magic
  SysRq  sequence is performed.  After Alt-SysRq-k, either the virtual
  console resets to a login screen (as expected after this SysRq
  sequence), or we get a kernel panic text screen (see attached screen
  photo) and can only restore via a hard power-cycle reboot.

  I will continue to try to capture a better trace output from one of
  these conditions, perhaps from /var/log/kern.log or by installing
  linux-crashdump (although these old machines may not have enough
  memory for the stock package).  But in the meantime, I'm attaching a
  photo of the kernel panic we see, which suggests a problem may reside
  in the Radeon driver ... which would seem possible, given the general
  blank-screen no-resume problem on these systems.

  Any advice on how to further capture any other needed details would be
  appreciated.  Thanks very much!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763273/+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 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

2018-04-15 Thread Daniel van Vugt

"Mature" means it hasn't changed in a while and we know what bugs it
contains. "Mature" does not mean zero bugs, but at least by not changing
it at the last minute we don't risk introducing bigger bugs. And this
bug is not big at all.

As an example, just today the "gjs" package has blown up with lots of
new crashes that didn't exist last week. This was caused by an
unnecessary upgrade of a previously mature package, and it looks like it
may risk the whole 18.04 release. That is why you shouldn't change
things late in the release cycle.

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

Title:
   bluez regression: Bluetooth audio fails to reconnect after resume

Status in bluez package in Ubuntu:
  Triaged
Status in bluez package in Fedora:
  Fix Released
Status in Suse:
  Fix Released

Bug description:
  STEPS TO REPRODUCE:
  1. Connect to Bluetooth audio device
  2. Suspend & Resume
  3. Reconnect to Bluetooth device.

  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.

  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments

  Workaround is to run sudo systemctl restart bluetooth after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 28 12:37:11 2018
  InstallationDate: Installed on 2018-03-23 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:5025 acl:32 sco:0 events:202 errors:0
TX bytes:5785 acl:32 sco:0 commands:103 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759628/+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 1763273] Re: kernel panic in Radeon driver while screen blank

2018-04-15 Thread RBL Admin

Further details from apport-bug are in #1764211; I'll copy them into
this account using my "cdarroch" personal Launchpad account in a few
hours, when I get home.

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

Title:
  kernel panic in Radeon driver while screen blank

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

Bug description:
  I maintain a set of older kiosks running a mix of stock Ubuntu 14.04
  LTS and 16.04.  As we have gradually transitioned them to 16.04, we
  have noticed that the machines running 16.04.1 now regularly exhibit
  problems restoring from the blank screen which appears after a period
  of inactivity.

  This only occurs on the machines where we've installed 16.04.  All of
  the 16.04.1 installations are "fresh", that is, complete re-installs
  from scratch, and we install all security and other updates on a
  regular basis.  This problem has persisted right from the beginning
  when we started using 16.04.

  Following a period of user inactivity, the screen goes blank; this is,
  of course, expected.  When the user tries to restore the session by
  typing a key or moving the mouse, one of three outcomes occurs.

  Sometimes, the session restores normally.  Other times, the screen
  remains blank regardless of all normal keyboard input, until a magic
  SysRq  sequence is performed.  After Alt-SysRq-k, either the virtual
  console resets to a login screen (as expected after this SysRq
  sequence), or we get a kernel panic text screen (see attached screen
  photo) and can only restore via a hard power-cycle reboot.

  I will continue to try to capture a better trace output from one of
  these conditions, perhaps from /var/log/kern.log or by installing
  linux-crashdump (although these old machines may not have enough
  memory for the stock package).  But in the meantime, I'm attaching a
  photo of the kernel panic we see, which suggests a problem may reside
  in the Radeon driver ... which would seem possible, given the general
  blank-screen no-resume problem on these systems.

  Any advice on how to further capture any other needed details would be
  appreciated.  Thanks very much!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763273/+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 1763273] Re: kernel panic in Radeon driver while screen blank

2018-04-15 Thread RBL Admin

** Attachment added: "Full kern.log from April 1 crash"

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117229/+files/apr1.full.kern.log

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

Title:
kernel panic in Radeon driver while screen blank

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

Any advice on how to further capture any other needed details would be
appreciated. Thanks very much!

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

Re: [Kernel-packages] [Bug 1763865] Re: Random system freezes

2018-04-15 Thread Don

Bios upgraded from v 2.19 to 2.30 today. I will test and let you know if
the issue remains.
I downloaded Lubuntu and burned the .iso to a DVD for possible installation.

On Sat, Apr 14, 2018 at 12:41 PM, axt <1763...@bugs.launchpad.net>
wrote:

> > dmi.bios.date: 06/06/2008
> > dmi.bios.vendor: LENOVO
> > dmi.bios.version: 7LETB9WW (2.19 )
> > (...)
> > dmi.product.version: ThinkPad T61
>
> At the first you should flash the current BIOS version 2.30-1.08 (!).
>
> The Core 2 Duo has implemented the Intel64 extension. You should install
> Bionic 64 bit (usefully Lubuntu) w/o Flash.
>
> It exists a serious hardware issue with T61 and Nvdia GPU. This may
> affect your device. Plz use a search engine!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1763865
>
> Title:
>   Random system freezes
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I have a lenovo T-61 with 4 GB of RAM. and a Intel® Core™2 Duo CPU
>   T7300 @ 2.00GHz × 2 GNOME is v 3.26.2. I have a 70 GB IDE HDD. Running
>   v 17.10
>
>   don@jarvis-t61:~$ ubuntu-bug linux
>   Using PPAPI flash.
>   don@jarvis-t61:~$  
> --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so
> --ppapi-flash-version=
>   Created new window in existing browser session.
>   
> [3490:3534:0413/201145.420218:ERROR:browser_gpu_channel_host_factory.cc(120)]
> Failed to launch GPU process.
>
>   ~$ apt-cache policy pkgname
>   N: Unable to locate package pkgname
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.10
>   Package: linux-image-4.13.0-38-generic 4.13.0-38.43
>   ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
>   Uname: Linux 4.13.0-38-generic i686
>   ApportVersion: 2.20.7-0ubuntu3.8
>   Architecture: i386
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  don1376 F pulseaudio
>   CurrentDesktop: ubuntu:GNOME
>   Date: Fri Apr 13 20:11:01 2018
>   HibernationDevice: RESUME=UUID=2768c12e-4582-4315-bc38-efd7c63d085d
>   InstallationDate: Installed on 2016-05-12 (701 days ago)
>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386
> (20160420.1)
>   MachineType: LENOVO 765912U
>   PccardctlIdent:
>Socket 0:
>  no product info available
>   PccardctlStatus:
>Socket 0:
>  no card
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic
> root=UUID=0d02ed0f-0377-4bab-b21b-eaaeb8fd8c64 ro quiet splash
> vt.handoff=7
>   RelatedPackageVersions:
>linux-restricted-modules-4.13.0-38-generic N/A
>linux-backports-modules-4.13.0-38-generic  N/A
>linux-firmware 1.169.3
>   SourcePackage: linux
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 06/06/2008
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: 7LETB9WW (2.19 )
>   dmi.board.name: 765912U
>   dmi.board.vendor: LENOVO
>   dmi.board.version: Not Available
>   dmi.chassis.asset.tag: No Asset Information
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: Not Available
>   dmi.modalias: dmi:bvnLENOVO:bvr7LETB9WW(2.19):bd06/06/2008:svnLENOVO:
> pn765912U:pvrThinkPadT61:rvnLENOVO:rn765912U:rvrNotAvailable:cvnLENOVO:
> ct10:cvrNotAvailable:
>   dmi.product.family: ThinkPad T61
>   dmi.product.name: 765912U
>   dmi.product.version: ThinkPad T61
>   dmi.sys.vendor: LENOVO
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1763865/+subscriptions
>

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

Title:
  Random system freezes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a lenovo T-61 with 4 GB of RAM. and a Intel® Core™2 Duo CPU
  T7300 @ 2.00GHz × 2 GNOME is v 3.26.2. I have a 70 GB IDE HDD. Running
  v 17.10

  don@jarvis-t61:~$ ubuntu-bug linux
  Using PPAPI flash.
  don@jarvis-t61:~$  
--ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
  Created new window in existing browser session.
  [3490:3534:0413/201145.420218:ERROR:browser_gpu_channel_host_factory.cc(120)] 
Failed to launch GPU process.

  ~$ apt-cache policy pkgname
  N: Unable to locate package pkgname

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-38-generic 4.13.0-38.43
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic i686
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  don1376 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 13 20:11:01 2018
  HibernationDevice:

[Kernel-packages] [Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

2018-04-15 Thread Anmar Oueja

As much as I love to have this fixed in the final release, I understand
Daniel's hesitation.   The point is to try and keep things as stable as
possible prior to releasing. Good news it is fixed and it is just a
matter of time before it is released.

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

Title:
   bluez regression: Bluetooth audio fails to reconnect after resume

Status in bluez package in Ubuntu:
  Triaged
Status in bluez package in Fedora:
  Fix Released
Status in Suse:
  Fix Released

Bug description:
  STEPS TO REPRODUCE:
  1. Connect to Bluetooth audio device
  2. Suspend & Resume
  3. Reconnect to Bluetooth device.

  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.

  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments

  Workaround is to run sudo systemctl restart bluetooth after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 28 12:37:11 2018
  InstallationDate: Installed on 2018-03-23 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:5025 acl:32 sco:0 events:202 errors:0
TX bytes:5785 acl:32 sco:0 commands:103 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759628/+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 1762844] Comment bridged from LTC Bugzilla

2018-04-15 Thread bugproxy

--- Comment From dougm...@us.ibm.com 2018-04-15 16:36 EDT---
Please collect the dmesg log and a crashdump.

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

  root@boslcp3:~# [   66.295233] Unable to handle kernel paging request for 
data at address 0x8882f6ed90e9151a
  [   66.295297] Faulting instruction address: 0xc038a110
  cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650]
  pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350
  lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350
  sp: c692f8d0
 msr: 90009033
 dar: 8882f6ed90e9151a
current = 0xc698fd00
paca= 0xcfab7000   softe: 0irq_happened: 0x01
  pid   = 1762, comm = systemd-journal
  Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 
(Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 
4.15.0-15.16-generic 4.15.15)
  enter ? for help
  [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
  [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0
  [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90
  [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390
  [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0
  [c692fe30] c000b184 system_call+0x58/0x6c
  --- Exception: c00 (System Call) at 74826f6fa9c4
  SP (75dc5510) is in userspace
  50:mon>
  50:mon>

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  [c000200e0b20fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
  [c000200e0b20fae0] c0c56ae4

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

2018-04-15 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/1764118

Title:
  BUG: unable to handle kernel NULL pointer dereference at
  0008

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  -

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-lowlatency 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
  Uname: Linux 4.15.0-15-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Sun Apr 15 15:26:46 2018
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location RIP: free_pcppages_bulk+0x15d/0x510 RSP: b37e8a45fa50
  Failure: oops
  HibernationDevice: RESUME=UUID=888376db-2e15-45cd-b40f-c9ccf9218dfb
  InstallationDate: Installed on 2018-03-02 (43 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  MachineType: Micro-Star International Co., Ltd MS-7A32
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-lowlatency 
root=/dev/mapper/ubuntu--gnome--vg-root ro rootflags=subvol=@ quiet splash 
vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: BUG: unable to handle kernel NULL pointer dereference at 
0008
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.80
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X370 GAMING PRO CARBON AC (MS-7A32)
  dmi.board.vendor: Micro-Star International Co., Ltd
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd01/26/2018:svnMicro-StarInternationalCo.,Ltd:pnMS-7A32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnX370GAMINGPROCARBONAC(MS-7A32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A32
  dmi.product.version: 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/1764118/+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 1753662] Re: [i40e] LACP bonding start up race conditions

2018-04-15 Thread Nobuto Murata

Ok, we have some numbers with the new host.

Failure rate: 45/112 (40.2%),   4.4.0-119-generic #143-Ubuntu SMP Mon Apr 2 
16:08:24 UTC 2018
Failure rate: 87/222 (39.2%),   4.4.0-120-generic #144-Ubuntu SMP Thu Apr 5 
14:11:49 UTC 2018
Failure rate: 117/726 (16.1%),  4.4.0-040400-generic #201803261439 SMP Mon Mar 
26 14:43:35 UTC 2018
Failure rate: 4/277 (1.4%), 4.12.0-041200rc3-generic #201804132111 SMP Fri 
Apr 13 21:13:47 UTC 2018
Failure rate: 0/407 (0.0%), 4.13.0-38-generic #43~16.04.1-Ubuntu SMP Wed 
Mar 14 17:48:43 UTC 2018


The xenial stock kernel and -120 from -proposed (just to see if LP: #1723127 is 
related or not) have around 40% failure rate.

However, xenial kernel with artful config (4.4.0-040400-generic
#201803261439) cuts down the failure rate on some level while we didn't
expect any difference from failure rate point of view.

4.12.0-041200rc3 cuts down more, then HWE eliminates the occurrence.

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

Title:
  [i40e] LACP bonding start up race conditions

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

Bug description:
  When provisioning Ubuntu servers with MAAS at once, some bonding pairs
  will have unexpected LACP status such as "Expired". It randomly
  happens at each provisioning with the default xenial kernel(4.4), but
  not reproducible with HWE kernel(4.13). I'm using Intel X710 cards
  (Dell-branded).

  Using the HWE kernel works as a workaround for short term, but it's
  not ideal since 4.13 is not covered by Canonical Livepatch service.

  How to reproduce:
  1. configure LACP bonding with MAAS
  2. provision machines
  3. check the bonding status in /proc/net/bonding/bond*

  frequency of occurrence:
  About 5 bond pairs in 22 pairs at each provisioning.

  [reproducible combination]
  $ uname -a
  Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 1.4.25-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  [non-reproducible combination]
  $ uname -a
  Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 2.1.14-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-116-generic 4.4.0-116.140
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  6 06:37 seq
   crw-rw 1 root audio 116, 33 Mar  6 06:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Mar  6 06:46:32 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R730
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 
console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-116-generic N/A
   linux-backports-modules-4.4.0-116-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.5
  dmi.board.name: 072T6D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.asset.tag: 0018880
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R730
  dmi.sys.vendor: Dell Inc.

To

[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions

2018-04-15 Thread Nobuto Murata

Just for the record, I'm using the attached rc.local for testing.

** Attachment added: "rc.local"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5116629/+files/rc.local

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

Title:
  [i40e] LACP bonding start up race conditions

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

Bug description:
  When provisioning Ubuntu servers with MAAS at once, some bonding pairs
  will have unexpected LACP status such as "Expired". It randomly
  happens at each provisioning with the default xenial kernel(4.4), but
  not reproducible with HWE kernel(4.13). I'm using Intel X710 cards
  (Dell-branded).

  Using the HWE kernel works as a workaround for short term, but it's
  not ideal since 4.13 is not covered by Canonical Livepatch service.

  How to reproduce:
  1. configure LACP bonding with MAAS
  2. provision machines
  3. check the bonding status in /proc/net/bonding/bond*

  frequency of occurrence:
  About 5 bond pairs in 22 pairs at each provisioning.

  [reproducible combination]
  $ uname -a
  Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 1.4.25-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  [non-reproducible combination]
  $ uname -a
  Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 2.1.14-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-116-generic 4.4.0-116.140
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  6 06:37 seq
   crw-rw 1 root audio 116, 33 Mar  6 06:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Mar  6 06:46:32 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R730
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 
console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-116-generic N/A
   linux-backports-modules-4.4.0-116-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.5
  dmi.board.name: 072T6D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.asset.tag: 0018880
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R730
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1764118] Re: BUG: unable to handle kernel NULL pointer dereference at 0000000000000008

2018-04-15 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  BUG: unable to handle kernel NULL pointer dereference at
  0008

Status in linux package in Ubuntu:
  New

Bug description:
  -

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-lowlatency 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
  Uname: Linux 4.15.0-15-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Sun Apr 15 15:26:46 2018
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location RIP: free_pcppages_bulk+0x15d/0x510 RSP: b37e8a45fa50
  Failure: oops
  HibernationDevice: RESUME=UUID=888376db-2e15-45cd-b40f-c9ccf9218dfb
  InstallationDate: Installed on 2018-03-02 (43 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  MachineType: Micro-Star International Co., Ltd MS-7A32
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-lowlatency 
root=/dev/mapper/ubuntu--gnome--vg-root ro rootflags=subvol=@ quiet splash 
vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: BUG: unable to handle kernel NULL pointer dereference at 
0008
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.80
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X370 GAMING PRO CARBON AC (MS-7A32)
  dmi.board.vendor: Micro-Star International Co., Ltd
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd01/26/2018:svnMicro-StarInternationalCo.,Ltd:pnMS-7A32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnX370GAMINGPROCARBONAC(MS-7A32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A32
  dmi.product.version: 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/1764118/+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 1764118] [NEW] BUG: unable to handle kernel NULL pointer dereference at 0000000000000008

2018-04-15 Thread SiggiTron

Public bug reported:

-

ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-15-lowlatency 4.15.0-15.16
ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
Uname: Linux 4.15.0-15-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
Date: Sun Apr 15 15:26:46 2018
DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location RIP: free_pcppages_bulk+0x15d/0x510 RSP: b37e8a45fa50
Failure: oops
HibernationDevice: RESUME=UUID=888376db-2e15-45cd-b40f-c9ccf9218dfb
InstallationDate: Installed on 2018-03-02 (43 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
MachineType: Micro-Star International Co., Ltd MS-7A32
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-lowlatency 
root=/dev/mapper/ubuntu--gnome--vg-root ro rootflags=subvol=@ quiet splash 
vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
SourcePackage: linux
Title: BUG: unable to handle kernel NULL pointer dereference at 0008
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/26/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.80
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X370 GAMING PRO CARBON AC (MS-7A32)
dmi.board.vendor: Micro-Star International Co., Ltd
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd01/26/2018:svnMicro-StarInternationalCo.,Ltd:pnMS-7A32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnX370GAMINGPROCARBONAC(MS-7A32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7A32
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd

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


** Tags: amd64 apport-kerneloops bionic 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/1764118

Title:
  BUG: unable to handle kernel NULL pointer dereference at
  0008

Status in linux package in Ubuntu:
  New

Bug description:
  -

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-lowlatency 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
  Uname: Linux 4.15.0-15-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Sun Apr 15 15:26:46 2018
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location RIP: free_pcppages_bulk+0x15d/0x510 RSP: b37e8a45fa50
  Failure: oops
  HibernationDevice: RESUME=UUID=888376db-2e15-45cd-b40f-c9ccf9218dfb
  InstallationDate: Installed on 2018-03-02 (43 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  MachineType: Micro-Star International Co., Ltd MS-7A32
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-lowlatency 
root=/dev/mapper/ubuntu--gnome--vg-root ro rootflags=subvol=@ quiet splash 
vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: BUG: unable to handle kernel NULL pointer dereference at 
0008
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.80
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X370 GAMING PRO CARBON AC (MS-7A32)
  dmi.board.vendor: Micro-Star International Co., Ltd
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd01/26/2018:svnMicro-StarInternationalCo.,Ltd:pnMS-7A32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnX370GAMINGPROCARBONAC(MS-7A32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A32
  dmi.product.version: 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/1764118/+subscriptions

-- 
Mailing list:

Re: [Kernel-packages] [Bug 1746740] Re: XPS13 L322X Bionic (daily dev) touchpad laggy

2018-04-15 Thread Bib

It does.
You see, I believe bvr in the string surely stands for BIOS Vendor
Release. You are @A08, and I @A10. This may be the reason for a
different "pn" returned string for the exactly same computer.
Silly Vendor
Thank you Sean

Le 15/04/2018 à 12:24, seanlano a écrit :
> On my machine, the complete string is
> dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0WW7PG:rvrA00:cvnDellInc.:ct8:cvr0.1
> - so the *XPSL322X* seems to still match. I'm not sure on the syntax
> either really, but it seemed to work for me at least - did it work for
> you?
>

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

Title:
  XPS13 L322X Bionic (daily dev) touchpad laggy

Status in libinput:
  Fix Released
Status in libinput package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Also, all function keys work as expected, even F6 (keyboard 3-states
  backlight), but OSD picture for this last feature randomly auto-
  triggers.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1876 F pulseaudio
  CasperVersion: 1.388
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  1 14:05:22 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180201)
  MachineType: Dell Inc. XPS L322X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- debian-installer/language=fr 
keyboard-configuration/layoutcode?=fr keyboard-configuration/variantcode?=oss
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.sys.vendor: Dell Inc.

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

2018-04-15 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/1764112

Title:
  BUG: scheduling while atomic: displaycal-appl/2687/0x0002

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  -

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-lowlatency 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
  Uname: Linux 4.15.0-15-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Sun Apr 15 14:42:08 2018
  Failure: oops
  HibernationDevice: RESUME=UUID=888376db-2e15-45cd-b40f-c9ccf9218dfb
  InstallationDate: Installed on 2018-03-02 (43 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  MachineType: Micro-Star International Co., Ltd MS-7A32
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-lowlatency 
root=/dev/mapper/ubuntu--gnome--vg-root ro rootflags=subvol=@ quiet splash 
vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: BUG: scheduling while atomic: displaycal-appl/2687/0x0002
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.80
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X370 GAMING PRO CARBON AC (MS-7A32)
  dmi.board.vendor: Micro-Star International Co., Ltd
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd01/26/2018:svnMicro-StarInternationalCo.,Ltd:pnMS-7A32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnX370GAMINGPROCARBONAC(MS-7A32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A32
  dmi.product.version: 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/1764112/+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 1764112] [NEW] BUG: scheduling while atomic: displaycal-appl/2687/0x00000002

2018-04-15 Thread SiggiTron

Public bug reported:

-

ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-15-lowlatency 4.15.0-15.16
ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
Uname: Linux 4.15.0-15-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
Date: Sun Apr 15 14:42:08 2018
Failure: oops
HibernationDevice: RESUME=UUID=888376db-2e15-45cd-b40f-c9ccf9218dfb
InstallationDate: Installed on 2018-03-02 (43 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
MachineType: Micro-Star International Co., Ltd MS-7A32
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-lowlatency 
root=/dev/mapper/ubuntu--gnome--vg-root ro rootflags=subvol=@ quiet splash 
vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
SourcePackage: linux
Title: BUG: scheduling while atomic: displaycal-appl/2687/0x0002
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/26/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.80
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X370 GAMING PRO CARBON AC (MS-7A32)
dmi.board.vendor: Micro-Star International Co., Ltd
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd01/26/2018:svnMicro-StarInternationalCo.,Ltd:pnMS-7A32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnX370GAMINGPROCARBONAC(MS-7A32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7A32
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd

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


** Tags: amd64 apport-kerneloops bionic 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/1764112

Title:
  BUG: scheduling while atomic: displaycal-appl/2687/0x0002

Status in linux package in Ubuntu:
  New

Bug description:
  -

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-lowlatency 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
  Uname: Linux 4.15.0-15-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Sun Apr 15 14:42:08 2018
  Failure: oops
  HibernationDevice: RESUME=UUID=888376db-2e15-45cd-b40f-c9ccf9218dfb
  InstallationDate: Installed on 2018-03-02 (43 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  MachineType: Micro-Star International Co., Ltd MS-7A32
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-lowlatency 
root=/dev/mapper/ubuntu--gnome--vg-root ro rootflags=subvol=@ quiet splash 
vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: BUG: scheduling while atomic: displaycal-appl/2687/0x0002
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.80
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X370 GAMING PRO CARBON AC (MS-7A32)
  dmi.board.vendor: Micro-Star International Co., Ltd
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd01/26/2018:svnMicro-StarInternationalCo.,Ltd:pnMS-7A32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnX370GAMINGPROCARBONAC(MS-7A32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A32
  dmi.product.version: 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/1764112/+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 1746740] Re: XPS13 L322X Bionic (daily dev) touchpad laggy

2018-04-15 Thread seanlano

On my machine, the complete string is
dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0WW7PG:rvrA00:cvnDellInc.:ct8:cvr0.1
- so the *XPSL322X* seems to still match. I'm not sure on the syntax
either really, but it seemed to work for me at least - did it work for
you?

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

Title:
  XPS13 L322X Bionic (daily dev) touchpad laggy

Status in libinput:
  Fix Released
Status in libinput package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Also, all function keys work as expected, even F6 (keyboard 3-states
  backlight), but OSD picture for this last feature randomly auto-
  triggers.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1876 F pulseaudio
  CasperVersion: 1.388
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  1 14:05:22 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180201)
  MachineType: Dell Inc. XPS L322X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- debian-installer/language=fr 
keyboard-configuration/layoutcode?=fr keyboard-configuration/variantcode?=oss
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.sys.vendor: Dell Inc.

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

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

Re: [Kernel-packages] [Bug 1746740] Re: XPS13 L322X Bionic (daily dev) touchpad laggy

2018-04-15 Thread Bib

I'm not skilled at all with hwdb & libinput syntax : didn't you forget
the "pn" substring before *XPSL322X* ?

Le 15/04/2018 à 05:02, seanlano a écrit :
> I've updated my patch to libinput, in
> https://bugs.freedesktop.org/show_bug.cgi?id=104990#c25
>
> Hopefully the devs there will shortly be able to revert the older patch,
> apply the new one, and then it will make it's way into 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/1746740

Title:
  XPS13 L322X Bionic (daily dev) touchpad laggy

Status in libinput:
  Fix Released
Status in libinput package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Also, all function keys work as expected, even F6 (keyboard 3-states
  backlight), but OSD picture for this last feature randomly auto-
  triggers.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1876 F pulseaudio
  CasperVersion: 1.388
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  1 14:05:22 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180201)
  MachineType: Dell Inc. XPS L322X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- debian-installer/language=fr 
keyboard-configuration/layoutcode?=fr keyboard-configuration/variantcode?=oss
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libinput/+bug/1746740/+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 1713884] Re: [CIFS] Fix maximum SMB2 header size

2018-04-15 Thread Michael Yap

** Changed in: linux (Ubuntu Xenial)
 Assignee: Joseph Salisbury (jsalisbury) => Michael Yap (imbainsik)

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

Title:
  [CIFS] Fix maximum SMB2 header size

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

Bug description:
  Currently the maximum size of SMB2/3 header is set incorrectly which
  leads to hanging of directory listing operations on encrypted SMB3
  connections. Fix this by setting the maximum size to 170 bytes that
  is calculated as RFC1002 length field size (4) + transform header
  size (52) + SMB2 header size (64) + create response size (56).

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/?id=47690ab81f4f29b12bbb0676d3579e61ab4d84de

  This applies across the board 3.16, 4.4, 4.10, artful, and azure.
  Microsoft would be happy to help test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713884/+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 1758496] Re: Backlight does not work on a MacBookAir3, 2

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

[Kernel-packages] [Bug 1762844] dmesg logs from xmon prompt_boslcp3

[Kernel-packages] [Bug 1751887] Re: The brightness of the screen cannot be adjusted with either the buttons or the slider.

[Kernel-packages] [Bug 1751887] Re: The brightness of the screen cannot be adjusted with either the buttons or the slider.

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

[Kernel-packages] [Bug 1764246] [NEW] kdump kernel panics on Bionic

[Kernel-packages] [Bug 1749214] Re: default vers value when mounting cifs shares with mount.cifs not working

[Kernel-packages] [Bug 1749329] Re: BUG: Bad rss-counter state mm:ffff9ac8374f39c0 idx:1 val:1

[Kernel-packages] [Bug 1763273] Re: kernel panic in Radeon driver while screen blank

[Kernel-packages] [Bug 1763273] Re: kernel panic in Radeon driver while screen blank

[Kernel-packages] [Bug 1763273] Re: kernel panic in Radeon driver while screen blank

[Kernel-packages] [Bug 1763273] Re: kernel panic in Radeon driver while screen blank

[Kernel-packages] [Bug 1763273] Re: kernel panic in Radeon driver while screen blank

[Kernel-packages] [Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

[Kernel-packages] [Bug 1763273] Re: kernel panic in Radeon driver while screen blank

[Kernel-packages] [Bug 1763273] Re: kernel panic in Radeon driver while screen blank

Re: [Kernel-packages] [Bug 1763865] Re: Random system freezes

[Kernel-packages] [Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

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

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

[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions

[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions

[Kernel-packages] [Bug 1764118] Re: BUG: unable to handle kernel NULL pointer dereference at 0000000000000008

[Kernel-packages] [Bug 1764118] [NEW] BUG: unable to handle kernel NULL pointer dereference at 0000000000000008

Re: [Kernel-packages] [Bug 1746740] Re: XPS13 L322X Bionic (daily dev) touchpad laggy

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

[Kernel-packages] [Bug 1764112] [NEW] BUG: scheduling while atomic: displaycal-appl/2687/0x00000002

[Kernel-packages] [Bug 1746740] Re: XPS13 L322X Bionic (daily dev) touchpad laggy

Re: [Kernel-packages] [Bug 1746740] Re: XPS13 L322X Bionic (daily dev) touchpad laggy

[Kernel-packages] [Bug 1713884] Re: [CIFS] Fix maximum SMB2 header size

31 matches

Site Navigation

Mail list logo

Footer information