date:20181015

Public bug reported:

tag=getxattr05 stime=1539663573
cmdline="getxattr05"
contacts=""
analysis=exit
<<>>
incrementing stop
tst_test.c:1072: INFO: Timeout per run is 0h 05m 00s
getxattr05.c:85: PASS: Got same data when acquiring the value of 
system.posix_acl_access twice
getxattr05.c:80: FAIL: Got different data(00 != ) at 16
getxattr05.c:85: PASS: Got same data when acquiring the value of 
system.posix_acl_access twice

Summary:
passed   2
failed   1
skipped  0
warnings 0

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-160-generic 3.13.0-160.210
ProcVersionSignature: User Name 3.13.0-160.210-generic 3.13.11-ckt39
Uname: Linux 3.13.0-160-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Oct 16 03:39 seq
 crw-rw 1 root audio 116, 33 Oct 16 03:39 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.14.1-0ubuntu3.29
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 Oct 16 04:19:43 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Intel Corporation S1200RP
PciMultimedia:
 
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-160-generic 
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro console=ttyS0,115200n8
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-160-generic N/A
 linux-backports-modules-3.13.0-160-generic  N/A
 linux-firmware  1.127.24
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/01/2015
dmi.bios.vendor: Intel Corp.
dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
dmi.board.asset.tag: 
dmi.board.name: S1200RP
dmi.board.vendor: Intel Corporation
dmi.board.version: G62254-407
dmi.chassis.asset.tag: 
dmi.chassis.type: 17
dmi.chassis.vendor: ..
dmi.chassis.version: ..
dmi.modalias: 
dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..:
dmi.product.name: S1200RP
dmi.product.version: 
dmi.sys.vendor: Intel Corporation

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug trusty uec-images

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

Title:
  getxattr05 in ubuntu_ltp_syscalls failed with T

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  tag=getxattr05 stime=1539663573
  cmdline="getxattr05"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1072: INFO: Timeout per run is 0h 05m 00s
  getxattr05.c:85: PASS: Got same data when acquiring the value of 
system.posix_acl_access twice
  getxattr05.c:80: FAIL: Got different data(00 != ) at 16
  getxattr05.c:85: PASS: Got same data when acquiring the value of 
system.posix_acl_access twice

  Summary:
  passed   2
  failed   1
  skipped  0
  warnings 0

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-160-generic 3.13.0-160.210
  ProcVersionSignature: User Name 3.13.0-160.210-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-160-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 16 03:39 seq
   crw-rw 1 root audio 116, 33 Oct 16 03:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.29
  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 Oct 16 04:19:43 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Intel Corporation S1200RP
  PciMultimedia:
   
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-160-generic 
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-160-generic N/A
   linux-backports-modules-3.13.0-160-generic  N/A
   linux-firmware  1.127.24
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
  dmi.board.asset.tag:

[Kernel-packages] [Bug 1798013] Re: getxattr05 in ubuntu_ltp_syscalls failed with T

>From the test case:

 * This issue included by getxattr05 has been fixed in kernel:
 * '82c9a927bc5d ("getxattr: use correct xattr length")'
 */

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

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

Title:
  getxattr05 in ubuntu_ltp_syscalls failed with T

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  tag=getxattr05 stime=1539663573
  cmdline="getxattr05"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1072: INFO: Timeout per run is 0h 05m 00s
  getxattr05.c:85: PASS: Got same data when acquiring the value of 
system.posix_acl_access twice
  getxattr05.c:80: FAIL: Got different data(00 != ) at 16
  getxattr05.c:85: PASS: Got same data when acquiring the value of 
system.posix_acl_access twice

  Summary:
  passed   2
  failed   1
  skipped  0
  warnings 0

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-160-generic 3.13.0-160.210
  ProcVersionSignature: User Name 3.13.0-160.210-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-160-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 16 03:39 seq
   crw-rw 1 root audio 116, 33 Oct 16 03:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.29
  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 Oct 16 04:19:43 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Intel Corporation S1200RP
  PciMultimedia:
   
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-160-generic 
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-160-generic N/A
   linux-backports-modules-3.13.0-160-generic  N/A
   linux-firmware  1.127.24
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
  dmi.board.asset.tag: 
  dmi.board.name: S1200RP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G62254-407
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 17
  dmi.chassis.vendor: ..
  dmi.chassis.version: ..
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..:
  dmi.product.name: S1200RP
  dmi.product.version: 
  dmi.sys.vendor: Intel Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1798013/+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 1790586] Re: The proposed grub package in Trusty / Bionic overrides the boot order on a MaaS deployed system

Node lodygin is out-of-order now, need to check this later.

** Changed in: ubuntu-kernel-tests
   Status: Confirmed => Incomplete

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

Title:
  The proposed grub package in Trusty / Bionic overrides the boot order
  on a MaaS deployed system

Status in ubuntu-kernel-tests:
  Incomplete
Status in grub2 package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Similar to bug 1642298, bug 1750732 and bug 1788539

  This issue was only spotted on ThunderX Cavium ARM64 system and an AMD
  Naples amd64 server in this SRU cycle.

  Steps:
  1. Deploy the ThunderX system with Trusty + T-LTS 4.4 kernel (It works fine 
with just Trusty, however this was tested on the AMD Naples, not ThunderX since 
it does not support 3.13 kernel)
  2. Check the efibootmgr output
  3. Enable proposed, install grub-common
  4. Check efibootmgr again

  Result:
  In step 2, the boot order is correct:
  ubuntu@wright-kernel:~$ sudo efibootmgr
  BootCurrent: 0002
  Timeout: 10 seconds
  BootOrder: 0002,,0003,0004,0001
  Boot* ubuntu
  Boot0001  UEFI: Built-in EFI Shell
  Boot0002* UEFI: IP4 Ethernet vNIC Controller 62:54:CA
  Boot0003* UEFI: IP4 Ethernet vNIC Controller 62:54:CB
  Boot0004* UEFI: IP4 Ethernet vNIC Controller 62:54:CC

  But in step 4, the boot order will be overridden:
  ubuntu@wright-kernel:~$ sudo efibootmgr
  BootCurrent: 0002
  Timeout: 10 seconds
  BootOrder: ,0002,0003,0004,0001
  Boot* ubuntu
  Boot0001  UEFI: Built-in EFI Shell
  Boot0002* UEFI: IP4 Ethernet vNIC Controller 62:54:CA
  Boot0003* UEFI: IP4 Ethernet vNIC Controller 62:54:CB
  Boot0004* UEFI: IP4 Ethernet vNIC Controller 62:54:CC

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: grub-common 2.02~beta2-9ubuntu1.15
  ProcVersionSignature: User Name 4.4.0-134.160~14.04.1-generic 4.4.140
  Uname: Linux 4.4.0-134-generic aarch64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: arm64
  Date: Tue Sep  4 07:45:19 2018
  SourcePackage: grub2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1790586/+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 1796385] Re: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112]

2018-10-15 Thread Bounty

Hello,

I won't be able to quickly test another video card. sorry about that.

Greg

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

Title:
  watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112]

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

Bug description:
  I can use the system for a while, then at random, the screen blinks and 
freezes. Must reboot.
  Seems to happen both with Wayland and Xorg.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-8-generic 4.18.0-8.9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  greg   2039 F pulseaudio
   /dev/snd/controlC1:  greg   2039 F pulseaudio
  Date: Tue Oct  2 15:56:23 2018
  Failure: oops
  InstallationDate: Installed on 2018-09-28 (7 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Default string
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=ce06b10d-2a7f-49db-a15b-85554d9a7e4d ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: X99-UD4-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd06/07/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99-UD4-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1796385/+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 1787299] Re: Frequent PCIe bus error on device 8086:a292

[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/1787299

Title:
  Frequent PCIe bus error on device 8086:a292

Status in linux package in Ubuntu:
  Expired

Bug description:
  This is on a fresh Dell 8930 with an i7-8700 (and a gtx1050) running ubuntu 
18.04.
  Linux rbb-ubu1804-1 4.15.0-32-generic #35-Ubuntu SMP Fri Aug 10 17:58:07 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  Oddly this only happens on one of the two such boxes I have.

  Here's the main warning I'm seeing:

  Aug 15 00:08:18 rbb-ubu1804-1 kernel: [24014.113915] pcieport :00:1c.2: 
AER: Corrected error received: id=00e2
  Aug 15 00:08:18 rbb-ubu1804-1 kernel: [24014.113931] pcieport :00:1c.2: 
PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e2(Transmitter 
ID)
  Aug 15 00:08:18 rbb-ubu1804-1 kernel: [24014.113942] pcieport :00:1c.2:   
device [8086:a292] error status/mask=1000/2000
  Aug 15 00:08:18 rbb-ubu1804-1 kernel: [24014.113950] pcieport :00:1c.2:   
 [12] Replay Timer Timeout

  
  Happens kind of randomly; dmesg shows it happened 13 times in first 9 minutes;
  syslog shows it happened 841 times in about 12 hours.

  Also see a bit of this:

  Aug 15 15:59:40 rbb-ubu1804-1 kernel: [  385.278631] pcieport :00:1c.2: 
AER: Multiple Corrected error received: id=00e2
  Aug 15 15:59:40 rbb-ubu1804-1 kernel: [  385.278635] pcieport :00:1c.2: 
can't find device of ID00e2

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-32-generic 4.15.0-32.35
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  buildbot   1881 F pulseaudio
   /dev/snd/controlC0:  buildbot   1881 F pulseaudio
  Date: Wed Aug 15 15:55:59 2018
  HibernationDevice: RESUME=UUID=d0b594a3-6d1f-41af-bde1-89c3ec729d02
  InstallationDate: Installed on 2018-08-14 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. XPS 8930
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/17/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.10
  dmi.board.name: 0DF42J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.10:bd05/17/2018:svnDellInc.:pnXPS8930:pvr1.0.10:rvnDellInc.:rn0DF42J:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.family: XPS
  dmi.product.name: XPS 8930
  dmi.product.version: 1.0.10
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787299/+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 1787283] Re: watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [gsd-power:1338]

[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/1787283

Title:
  watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [gsd-power:1338]

Status in linux package in Ubuntu:
  Expired

Bug description:
  sometimes "freezes" cp1

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1370 F pulseaudio
john   1723 F pulseaudio
  Date: Wed Aug 15 14:48:08 2018
  Failure: oops
  InstallationDate: Installed on 2018-08-15 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: HP-Pavilion FQ602AAR-ABA m9525f
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=67c65cef-894d-4ced-8f26-2f69f6ec9334 ro recovery nomodeset
  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:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [gsd-power:1338]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.39
  dmi.board.name: Benicia
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.39:bd05/06/2009:svnHP-Pavilion:pnFQ602AAR-ABAm9525f:pvr:rvnPEGATRONCORPORATION:rnBenicia:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion:
  dmi.product.family: 103C_53316J
  dmi.product.name: FQ602AAR-ABA m9525f
  dmi.sys.vendor: HP-Pavilion

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787283/+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 1787391] Re: Upgrade from 16.04 LTS to 18.04 LTS breaks sound due to missing package dependencies

[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/1787391

Title:
  Upgrade from 16.04 LTS to 18.04 LTS breaks sound due to missing
  package dependencies

Status in linux package in Ubuntu:
  Expired

Bug description:
  I upgraded one of my desktops from Xubuntu 16.04 LTS to 18.04 LTS.
  This broke alsa/pulseaudio, because the upgrade failed to install the
  linux-modules-extra-* package.

  Before the upgrade, sound worked fine, after the upgrade pulseaudio
  only showed the infamous "Dummy device".

  Installing, in my case, linux-modules-extra-4.15.0-30-generic and
  rebooting fixed the problem.

  While i, generally, understand that you might want to minimize the
  amount of kernel modules (which is why this is an extra package, i
  presume), when the system has alsa and pulseaudio installed, it makes
  sense to also install the relevant kernel drivers.

  If you don't want to install the "extra" modules in all cases, please
  make alsa and/or pulseaudio depend on them. Not doing so breaks sound
  on a lot of devices, because the "extra" module also includes the
  driver for many Intel onboard sound devices.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-modules-extra-4.15.0-30-generic 4.15.0-30.32
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Aug 16 14:04:25 2018
  HibernationDevice: RESUME=UUID=cb011f5b-7340-4abf-a775-b304ed1323fe
  InstallationDate: Installed on 2018-01-10 (218 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=a75fcaaa-d710-499a-b778-8bc7ec1223ea ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-30-generic N/A
   linux-backports-modules-4.15.0-30-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (2 days ago)
  dmi.bios.date: 08/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4210
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH X79
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787391/+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 1785198] Re: mkfs.vfat is causing failure on fallocate05, fsetxattr01, fgetxattr01, fsync01, msync04, preadv03, preadv03, pwritev03, pwritev03_64, setxattr01 tests in ubuntu_ltp

** Summary changed:

- mkfs.vfat is causing failure on fallocate05 / fsync01 / msync04 / preadv03 / 
pwritev03 / setxattr01 tests in ubuntu_ltp_syscall on Trusty
+ mkfs.vfat is causing failure on  fallocate05, fsetxattr01, fgetxattr01, 
fsync01, msync04, preadv03, preadv03, pwritev03, pwritev03_64, setxattr01 tests 
in ubuntu_ltp_syscall on Trusty

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

Title:
  mkfs.vfat is causing failure on  fallocate05, fsetxattr01,
  fgetxattr01, fsync01, msync04, preadv03, preadv03, pwritev03,
  pwritev03_64, setxattr01 tests in ubuntu_ltp_syscall on Trusty

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Triaged

Bug description:
  This test failed due to:
  mkfs.vfat: /dev/loop0 contains a mounted filesystem.
  tst_mkfs.c:94: BROK: mkfs.vfat:1: tst_test.c failed with 732

  fallocate05 / fsync01 / msync04 / preadv03 / preadv03_64 / pwritev03 /
  pwrite03_64 / setxattr01 are failing with the same issue.

  The mkfs.vfat command only works once for the first test.

  So if you run the same test case (e.g. msync04) on a recently rebooted
  system, it will pass for the first run.

  <<>>
  tag=fallocate05 stime=1533288629
  cmdline="fallocate05"
  contacts=""
  analysis=exit
  <<>>
  tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop0'
  incrementing stop
  tst_supported_fs_types.c:72: INFO: Kernel supports ext2
  tst_supported_fs_types.c:56: INFO: mkfs.ext2 does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports ext3
  tst_supported_fs_types.c:56: INFO: mkfs.ext3 does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports ext4
  tst_supported_fs_types.c:56: INFO: mkfs.ext4 does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports xfs
  tst_supported_fs_types.c:56: INFO: mkfs.xfs does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports btrfs
  tst_supported_fs_types.c:52: INFO: mkfs.btrfs does not exist
  tst_supported_fs_types.c:72: INFO: Kernel supports vfat
  tst_supported_fs_types.c:56: INFO: mkfs.vfat does exist
  tst_supported_fs_types.c:95: INFO: Filesystem exfat is not supported
  tst_supported_fs_types.c:72: INFO: Kernel supports ntfs
  tst_supported_fs_types.c:56: INFO: mkfs.ntfs does exist
  tst_test.c:1079: INFO: Testing on ext2
  tst_mkfs.c:83: INFO: Formatting /dev/loop0 with ext2 opts='' extra opts=''
  mke2fs 1.42.9 (4-Feb-2014)
  tst_test.c:1018: INFO: Timeout per run is 0h 05m 00s
  fallocate05.c:46: CONF: fallocate() not supported: EOPNOTSUPP
  tst_test.c:1079: INFO: Testing on ext3
  tst_mkfs.c:83: INFO: Formatting /dev/loop0 with ext3 opts='' extra opts=''
  mke2fs 1.42.9 (4-Feb-2014)
  tst_test.c:1018: INFO: Timeout per run is 0h 05m 00s
  fallocate05.c:46: CONF: fallocate() not supported: EOPNOTSUPP
  tst_test.c:1079: INFO: Testing on ext4
  tst_mkfs.c:83: INFO: Formatting /dev/loop0 with ext4 opts='' extra opts=''
  mke2fs 1.42.9 (4-Feb-2014)
  tst_test.c:1018: INFO: Timeout per run is 0h 05m 00s
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file0 size 21710183
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file1 size 8070086
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file2 size 3971177
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file3 size 36915315
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file4 size 70310993
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file5 size 4807935
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file6 size 90739786
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file7 size 76896492
  tst_fill_fs.c:61: INFO: write(): ENOSPC
  fallocate05.c:62: PASS: write() wrote 8192 bytes
  fallocate05.c:71: PASS: fallocate() on full FS: ENOSPC
  fallocate05.c:80: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE)
  fallocate05.c:86: PASS: write()
  tst_test.c:1079: INFO: Testing on xfs
  tst_mkfs.c:83: INFO: Formatting /dev/loop0 with xfs opts='' extra opts=''
  tst_test.c:1018: INFO: Timeout per run is 0h 05m 00s
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file0 size 21710183
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file1 size 8070086
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file2 size 3971177
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file3 size 36915315
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file4 size 70310993
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file5 size 4807935
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file6 size 90739786
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file7 size 76896492
  tst_fill_fs.c:61: INFO: write(): ENOSPC
  fallocate05.c:62: PASS: write() wrote 8192 bytes
  fallocate05.c:71: PASS: fallocate() on full FS: ENOSPC
  fallocate05.c:80: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE)
  fallocate05.c:86: PASS: write()
  tst_test.c:1079: INFO: Testing on vfat
  tst_mkfs.c:83: INFO: Formatting /dev/loop0 with vfat opts='' extra

[Kernel-packages] [Bug 1785198] Re: mkfs.vfat is causing failure on fallocate05 / fsync01 / msync04 / preadv03 / pwritev03 / setxattr01 tests in ubuntu_ltp_syscall on Trusty

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

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

Title:
  mkfs.vfat is causing failure on fallocate05 / fsync01 / msync04 /
  preadv03 / pwritev03 / setxattr01 tests in ubuntu_ltp_syscall on
  Trusty

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Triaged

Bug description:
  This test failed due to:
  mkfs.vfat: /dev/loop0 contains a mounted filesystem.
  tst_mkfs.c:94: BROK: mkfs.vfat:1: tst_test.c failed with 732

  fallocate05 / fsync01 / msync04 / preadv03 / preadv03_64 / pwritev03 /
  pwrite03_64 / setxattr01 are failing with the same issue.

  The mkfs.vfat command only works once for the first test.

  So if you run the same test case (e.g. msync04) on a recently rebooted
  system, it will pass for the first run.

  <<>>
  tag=fallocate05 stime=1533288629
  cmdline="fallocate05"
  contacts=""
  analysis=exit
  <<>>
  tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop0'
  incrementing stop
  tst_supported_fs_types.c:72: INFO: Kernel supports ext2
  tst_supported_fs_types.c:56: INFO: mkfs.ext2 does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports ext3
  tst_supported_fs_types.c:56: INFO: mkfs.ext3 does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports ext4
  tst_supported_fs_types.c:56: INFO: mkfs.ext4 does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports xfs
  tst_supported_fs_types.c:56: INFO: mkfs.xfs does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports btrfs
  tst_supported_fs_types.c:52: INFO: mkfs.btrfs does not exist
  tst_supported_fs_types.c:72: INFO: Kernel supports vfat
  tst_supported_fs_types.c:56: INFO: mkfs.vfat does exist
  tst_supported_fs_types.c:95: INFO: Filesystem exfat is not supported
  tst_supported_fs_types.c:72: INFO: Kernel supports ntfs
  tst_supported_fs_types.c:56: INFO: mkfs.ntfs does exist
  tst_test.c:1079: INFO: Testing on ext2
  tst_mkfs.c:83: INFO: Formatting /dev/loop0 with ext2 opts='' extra opts=''
  mke2fs 1.42.9 (4-Feb-2014)
  tst_test.c:1018: INFO: Timeout per run is 0h 05m 00s
  fallocate05.c:46: CONF: fallocate() not supported: EOPNOTSUPP
  tst_test.c:1079: INFO: Testing on ext3
  tst_mkfs.c:83: INFO: Formatting /dev/loop0 with ext3 opts='' extra opts=''
  mke2fs 1.42.9 (4-Feb-2014)
  tst_test.c:1018: INFO: Timeout per run is 0h 05m 00s
  fallocate05.c:46: CONF: fallocate() not supported: EOPNOTSUPP
  tst_test.c:1079: INFO: Testing on ext4
  tst_mkfs.c:83: INFO: Formatting /dev/loop0 with ext4 opts='' extra opts=''
  mke2fs 1.42.9 (4-Feb-2014)
  tst_test.c:1018: INFO: Timeout per run is 0h 05m 00s
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file0 size 21710183
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file1 size 8070086
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file2 size 3971177
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file3 size 36915315
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file4 size 70310993
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file5 size 4807935
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file6 size 90739786
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file7 size 76896492
  tst_fill_fs.c:61: INFO: write(): ENOSPC
  fallocate05.c:62: PASS: write() wrote 8192 bytes
  fallocate05.c:71: PASS: fallocate() on full FS: ENOSPC
  fallocate05.c:80: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE)
  fallocate05.c:86: PASS: write()
  tst_test.c:1079: INFO: Testing on xfs
  tst_mkfs.c:83: INFO: Formatting /dev/loop0 with xfs opts='' extra opts=''
  tst_test.c:1018: INFO: Timeout per run is 0h 05m 00s
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file0 size 21710183
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file1 size 8070086
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file2 size 3971177
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file3 size 36915315
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file4 size 70310993
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file5 size 4807935
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file6 size 90739786
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file7 size 76896492
  tst_fill_fs.c:61: INFO: write(): ENOSPC
  fallocate05.c:62: PASS: write() wrote 8192 bytes
  fallocate05.c:71: PASS: fallocate() on full FS: ENOSPC
  fallocate05.c:80: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE)
  fallocate05.c:86: PASS: write()
  tst_test.c:1079: INFO: Testing on vfat
  tst_mkfs.c:83: INFO: Formatting /dev/loop0 with vfat opts='' extra opts=''
  mkfs.vfat: /dev/loop0 contains a mounted filesystem.
  tst_mkfs.c:94: BROK: mkfs.vfat:1: tst_test.c failed with 732

  Summary:
  passed   8
  failed   0
  skipped  2
  warnings 0
  <<>>
  initiation_status="ok"
  duration=8 termination_type=exited termination_id=2 corefile=no
  cutime=6 cstime=105
  <<>>

[Kernel-packages] [Bug 1797069] Re: linux-oem: 4.15.0-1024.28 -proposed tracker

2018-10-15 Thread Brad Figg

** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: In Progress => Fix Released

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

Title:
  linux-oem: 4.15.0-1024.28 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1797061
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797069/+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 1795453] Re: IO's are issued with incorrect Scatter Gather Buffer

2018-10-15 Thread Sujith Pandel

@sasikumarpc - Ok. So when you say below v4.18 kernel fixes it, does it
mean with increased memory or is it with the same setup where the issue
was originally seen?

Issue resolved Kernel Version
-
4.18.0-8-generic

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

Title:
  IO's are issued with incorrect Scatter Gather Buffer

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect 
Scatter Gather Buffer address .

  i.e

   OS is sending the IO with 64 bit Scatter Gather Buffer address , such
  that if we add the length with buffer address then it causes the roll
  over .

  
  Here is the data we captured in our driver (Printed the SGE details which was 
sent by OS)

  sgl_ptr->Address = f000 
  [14547.313240] 
  sgl_ptr->Length = 1000 
  [14547.313241] 
  sge_count = 18 
  [14547.313242] 
  cmd->index = 9d9

  
  Note : This issue is observed only when virtualization is enabled 

  Product : Broadcom (LSI) Megaraid H840 controller
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R7415
  dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R7415
  dmi.product.sku:

[Kernel-packages] [Bug 1797069] Re: linux-oem: 4.15.0-1024.28 -proposed tracker

2018-10-15 Thread Brad Figg

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

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

Title:
  linux-oem: 4.15.0-1024.28 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1797061
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797069/+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 1795292] Re: ELAN469D touch pad not working

2018-10-15 Thread Patrick Van Oosterwijck

Here's the full output of acpidump.

** Attachment added: "acpidump.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795292/+attachment/5201434/+files/acpidump.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/1795292

Title:
  ELAN469D touch pad not working

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

Bug description:
  I installed Bionic Beaver and now upgraded to Cosmic Cuttlefish on
  this Lenovo Ideapad 330S-15ARR laptop.  The touch pad doesn't work in
  either.

  Some possibly relevant info from dmesg:
  i2c_hid i2c-ELAN469D:00: i2c-ELAN469D:00 supply vdd not found, using dummy 
regulator
  i2c_designware AMDI0010:01: controller timed out

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-7-generic 4.18.0-7.8
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  xorbit 2086 F pulseaudio
   /dev/snd/pcmC1D0p:   xorbit 2086 F...m pulseaudio
   /dev/snd/controlC0:  xorbit 2086 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Sep 30 23:14:26 2018
  InstallationDate: Installed on 2018-09-20 (10 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 81FB
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic 
root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic processor.max_cstate=1 
rcu_nocbs=0-7 pcie_aspm=off pci=noaer quiet splash vt.handoff=1 
elan_i2c.dyndbg=+p
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-7-generic N/A
   linux-backports-modules-4.18.0-7-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (0 days ago)
  dmi.bios.date: 06/08/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7WCN22WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330S-15ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr7WCN22WW:bd06/08/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR:
  dmi.product.family: ideapad 330S-15ARR
  dmi.product.name: 81FB
  dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR
  dmi.product.version: Lenovo ideapad 330S-15ARR
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-09-20 (13 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  cosmic
  Uname: Linux 4.19.0-041900rc6-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (2 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1795292/+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 1797069] Re: linux-oem: 4.15.0-1024.28 -proposed tracker

2018-10-15 Thread AceLan Kao

** Summary changed:

- linux-oem:  -proposed tracker
+ linux-oem: 4.15.0-1024.28 -proposed tracker

** Summary changed:

- linux-oem: 4.15.0-1024.28 -proposed tracker
+ linux-oem:  -proposed tracker

** Summary changed:

- linux-oem:  -proposed tracker
+ linux-oem: 4.15.0-1024.28 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Fix Released => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: Fix Released => In Progress

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: Fix Released => In Progress

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

Title:
  linux-oem: 4.15.0-1024.28 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1797061
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797069/+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 1797069] Re: linux-oem: -proposed tracker

2018-10-15 Thread AceLan Kao

** Summary changed:

- linux-oem: 4.15.0-1024.27 -proposed tracker
+ linux-oem:  -proposed tracker

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

Title:
  linux-oem:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1797061
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797069/+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 1774484] Re: package linux-firmware 1.173.1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 127

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package linux-firmware 1.173.1 failed to install/upgrade: installed
  linux-firmware package post-installation script subprocess returned
  error exit status 127

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  The failure has something to do with live patch

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.173.1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Tue May 29 09:03:40 2018
  Dependencies:
   
  DuplicateSignature:
   package:linux-firmware:1.173.1
   Setting up linux-firmware (1.173.1) ...
   awk: symbol lookup error: /usr/local/lib/libreadline.so.7: undefined symbol: 
UP
   dpkg: error processing package linux-firmware (--configure):
installed linux-firmware package post-installation script subprocess 
returned error exit status 127
  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 127
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: linux-firmware
  Title: package linux-firmware 1.173.1 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1774484/+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 1797669] Re: tc filter add after delete get error "No space left on device"

2018-10-15 Thread Neil

yes, I upgrade from ubuntu 4.4.0-116-generic, and it works fine.
I tested upstream latest v4.19 kernel first and it is fine, then find out that 
upstream has this issue between 4.15.x-4.16.2.

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

** Tags added: kernel-fixed-upstream

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

Title:
  tc filter add after delete get error "No space left on device"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  tc filter seems still leak with ubuntu kernel 4.15.0-36-generic,
  it can be reproduced with the following steps.

  ```
  tc qdisc add dev eth0 ingress
  tc filter add dev eth0 ingress protocol ip prio 1 handle 800::1 u32 match ip 
dst 192.168.5.113/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1
  tc filter add dev eth0 ingress protocol ip prio 1 handle 800::2 u32 match ip 
dst 192.168.5.46/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1
  tc filter del dev eth0 ingress protocol ip prio 1 handle 800::1 u32 match ip 
dst 192.168.5.113/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1
  tc filter add dev eth0 ingress protocol ip prio 1 handle 800::1 u32 match ip 
dst 192.168.5.113/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1
  ```

  the last command will get this error
  ```
  RTNETLINK answers: No space left on device
  We have an error talking to the kernel
  ```

  upstream 4.15(eol) also have this issue, but 4.16.2 fixed, and ubuntu 
4.15.0-36 already patched upstream 4.16.2 fix patch.
  however this issue still exist, I think the difference between 4.15 and 4.16 
caused this issue.
  please kindly help check it.
  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797669/+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 1778011] Re: SRU: PRIME Power Saving mode draws too much power

2018-10-15 Thread Josh Holland

Is there another bug I can follow to find out when LightDM will receive
support for this update?

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

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in HWE Next:
  New
Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released
Status in nvidia-prime source package in Bionic:
  Fix Released
Status in nvidia-settings source package in Bionic:
  Fix Released
Status in ubuntu-drivers-common source package in Bionic:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 *

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

  2) Create /etc/apt/preferences.d/proposed-updates with the following
  content:

  Package: *
  Pin: release a=bionic-proposed
  Pin-Priority: 400

  3) Update the list of packages:

  sudo apt-get update

  4) Install the packages from -proposed using the following command:

  sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-
  proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-
  proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic-
  proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390
  /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia-
  ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1778011/+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 1797990] [NEW] kdump fail due to an IRQ storm

2018-10-15 Thread Guilherme G. Piccoli

Public bug reported:

We have reports of a kdump failure in Ubuntu (in x86 machine) that was
narrowed down to a MSI irq storm coming from a PCI network device.

The bug manifests as a lack of progress in the boot process of the kdump
kernel, and a storm of kernel messages like:

[...]
[  342.265294] do_IRQ: 0.155 No irq handler for vector
[  342.266916] do_IRQ: 0.155 No irq handler for vector
[  347.258422] do_IRQ: 14053260 callbacks suppressed
[...]

The root cause of the the issue is that the kdump kernel kexec process
does not ensure PCI devices are reset and/or MSI capabilities are
disabled, so a PCI device could produce a huge amount of PCI irqs which
would take all the processing time for the CPU (specially since we
restrict the kdump kernel to use one single CPU only).

This was tested using upstream kernel version 4.18, and the problem reproduces.
In the specific test scenario, the PCI NIC was an "Intel 82599ES 10-Gigabit 
[8086:10fb]" that was used in SR-IOV PCI passthrough mode (vfio_pci), under 
high load on the guest.

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Guilherme G. Piccoli (gpiccoli)
 Status: Confirmed


** Tags: sts

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

Title:
  kdump fail due to an IRQ storm

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We have reports of a kdump failure in Ubuntu (in x86 machine) that was
  narrowed down to a MSI irq storm coming from a PCI network device.

  The bug manifests as a lack of progress in the boot process of the
  kdump kernel, and a storm of kernel messages like:

  [...]
  [  342.265294] do_IRQ: 0.155 No irq handler for vector
  [  342.266916] do_IRQ: 0.155 No irq handler for vector
  [  347.258422] do_IRQ: 14053260 callbacks suppressed
  [...]

  The root cause of the the issue is that the kdump kernel kexec process
  does not ensure PCI devices are reset and/or MSI capabilities are
  disabled, so a PCI device could produce a huge amount of PCI irqs
  which would take all the processing time for the CPU (specially since
  we restrict the kdump kernel to use one single CPU only).

  This was tested using upstream kernel version 4.18, and the problem 
reproduces.
  In the specific test scenario, the PCI NIC was an "Intel 82599ES 10-Gigabit 
[8086:10fb]" that was used in SR-IOV PCI passthrough mode (vfio_pci), under 
high load on the guest.

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

--- Comment From mranw...@us.ibm.com 2018-10-15 18:04 EDT---
Test kernel looks good:
user@deb3qwsp2:/usr/local/cuda-10.0/samples/0_Simple/matrixMul$ cat 
/proc/version
Linux version 4.15.0-36-generic (jsalisbury@kathleen) (gcc version 7.3.0 
(Ubuntu 7.3.0-16ubuntu3)) #40~lp1797963 SMP Mon Oct 15 19:50:41 UTC 2018
user@deb3qwsp2:/usr/local/cuda-10.0/samples/0_Simple/matrixMul$ gdb ./matrixMul
GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "powerpc64le-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./matrixMul...(no debugging symbols found)...done.
(gdb) break main
Breakpoint 1 at 0x8284
(gdb) run
Starting program: /usr/local/cuda-10.0/samples/0_Simple/matrixMul/matrixMul
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/powerpc64le-linux-gnu/libthread_db.so.1".

Breakpoint 1, 0x00018284 in main ()
(gdb) break *(__kernel_clock_gettime+144)
Breakpoint 2 at 0x77f805e4: file 
/home/jsalisbury/bugs/lp1797963/ubuntu-bionic/arch/powerpc/kernel/vdso64/gettimeofday.S,
 line 128.
(gdb) continue
Continuing.
[Matrix Multiply Using CUDA] - Starting...

Breakpoint 2, __kernel_clock_gettime ()
at 
/home/jsalisbury/bugs/lp1797963/ubuntu-bionic/arch/powerpc/kernel/vdso64/gettimeofday.S:128
128 
/home/jsalisbury/bugs/lp1797963/ubuntu-bionic/arch/powerpc/kernel/vdso64/gettimeofday.S:
 No such file or directory.
(gdb) bt
#0  __kernel_clock_gettime () at 
/home/jsalisbury/bugs/lp1797963/ubuntu-bionic/arch/powerpc/kernel/vdso64/gettimeofday.S:128
#1  0x77b8f574 in __GI___clock_gettime (clock_id=, 
tp=)
at ../sysdeps/unix/clock_gettime.c:115
#2  0x76bcab24 in ?? () from /usr/lib/powerpc64le-linux-gnu/libcuda.so.1
#3  0x76b81118 in ?? () from /usr/lib/powerpc64le-linux-gnu/libcuda.so.1
#4  0x76a69c70 in ?? () from /usr/lib/powerpc64le-linux-gnu/libcuda.so.1
#5  0x76bf0ba0 in cuInit () from 
/usr/lib/powerpc64le-linux-gnu/libcuda.so.1
#6  0x00010003ca50 in cudart::__loadDriverInternalUtil() ()
#7  0x77f05274 in __pthread_once_slow (
once_control=0x1000c00f0 ,
init_routine=0x10003c950 ) at 
pthread_once.c:116
#8  0x00010008ea88 in cudart::cuosOnce(int*, void (*)()) ()
#9  0x0001000410a8 in cudart::globalState::initializeDriver() ()
#10 0x00010005ec90 in cudaGetDeviceCount ()
#11 0x00019930 in gpuGetMaxGflopsDeviceId() ()
#12 0x00019bf4 in findCudaDevice(int, char const**) ()
#13 0x0001836c in main ()
(gdb) step
129 in 
/home/jsalisbury/bugs/lp1797963/ubuntu-bionic/arch/powerpc/kernel/vdso64/gettimeofday.S
(gdb) bt
#0  __kernel_clock_gettime () at 
/home/jsalisbury/bugs/lp1797963/ubuntu-bionic/arch/powerpc/kernel/vdso64/gettimeofday.S:129
#1  0x77b8f574 in __GI___clock_gettime (clock_id=, 
tp=)
at ../sysdeps/unix/clock_gettime.c:115
#2  0x76bcab24 in ?? () from /usr/lib/powerpc64le-linux-gnu/libcuda.so.1
#3  0x76b81118 in ?? () from /usr/lib/powerpc64le-linux-gnu/libcuda.so.1
#4  0x76a69c70 in ?? () from /usr/lib/powerpc64le-linux-gnu/libcuda.so.1
#5  0x76bf0ba0 in cuInit () from 
/usr/lib/powerpc64le-linux-gnu/libcuda.so.1
#6  0x00010003ca50 in cudart::__loadDriverInternalUtil() ()
#7  0x77f05274 in __pthread_once_slow (
once_control=0x1000c00f0 ,
init_routine=0x10003c950 ) at 
pthread_once.c:116
#8  0x00010008ea88 in cudart::cuosOnce(int*, void (*)()) ()
#9  0x0001000410a8 in cudart::globalState::initializeDriver() ()
#10 0x00010005ec90 in cudaGetDeviceCount ()
#11 0x00019930 in gpuGetMaxGflopsDeviceId() ()
#12 0x00019bf4 in findCudaDevice(int, char const**) ()
#13 0x0001836c in main ()
(gdb)

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

Title:
  not able to unwind the stack from within __kernel_clock_gettime in the
  Linux vDSO

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  Description

  We're not able to unwind the stack from within __kernel_clock_gettime
  in the Linux vDSO on Summit. This affects both DDT and MAP (via GDB
  and libunwind). The

[Kernel-packages] [Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic

2018-10-15 Thread royden

"The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1788997;

linux-
headers-4.17.0-041700rc2-generic_4.17.0-041700rc2.201810151529_amd64

This kernel has wifi working just fine, ant_sel=1.

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

Title:
  rtl8723be wifi does not work under linux-modules-
  extra-4.15.0-33-generic

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with
  kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK.

  Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any
  wifi networks and thus there is no connection. Changing the antenna
  setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either;
  as a workaround an external wifi device (Gigaset USB Adapter 108)
  works.

  The expectation is that wifi through rtl8723be will still work under 
4.15.0-33.36 as it did previously.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  al 1234 F pulseaudio
   /dev/snd/controlC0:  al 1234 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-05-27 (89 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Hewlett-Packard HP Notebook
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.02
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8137
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 99.02
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard

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

--- Comment From mranw...@us.ibm.com 2018-10-15 17:55 EDT---
This kernel also looks good - I did a couple 10+ minutes runs against it 
without any problems, which shows the problem being fixed.

I think that leaving out DD1 is ok - but at some point if it's still
there it may make some other backport much harder - but we can also just
deal with that when needed.

The backport removing DD1 also included the fix for powerpc/64s:
dt_cpu_ftrs fix POWER9 DD2.2 and above (9e9626e) - but maybe I should
open a bug to get that into the next SRU?

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

Title:
  Signal 7 error when running GPFS tracing in cluster

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  
  == SRU Justification ==
  IBM is requesting these commits in bionic and cosmic.  These commits
  also rely on commit 7acf50e4efa6, which was SRU'd in bug 1792102.  The
  first patch, commit 2bf1071a8d50, was backported by IBM themself.

  Description of bug:
  GPFS mmfsd daemon is mapping shared tracing buffer(allocated from kernel
  driver using vmalloc) and then writing trace records from user space threads
  in parallel. While the SIGBUS happened, the access virtual memory address
  is in the mapped range, no overflow on access.

  The root cause is that for PTEs created by a driver at mmap time (ie, that
  aren't created dynamically at fault time), it's not legit for 
ptep_set_access_flags()
  to make them invalid even temporarily. A concurrent access while they are
  invalid will be unable to service the page fault and will cause as SIGBUS.

  
  == Fixes ==
  2bf1071a8d50 ("powerpc/64s: Remove POWER9 DD1 support")
  bd0dbb73e013 ("powerpc/mm/books3s: Add new pte bit to mark pte temporarily 
invalid.")
  f08d08f3db55 ("powerpc/mm/radix: Only need the Nest MMU workaround for R -> 
RW transition")

  
  == Regression Potential ==
  Low.  Limited to powerpc.

  == Test Case ==
  A test kernel was built with these patches and tested by IBM.
  IBM states the test kernel resolved the bug.


  -- Problem Description --
  GPFS mmfsd daemon is mapping shared tracing buffer(allocated from kernel 
driver using vmalloc) and then writing trace records from user space threads in 
parallel.  While the SIGBUS happened, the access virtual memory address is in 
the mapped range, no overflow on access.

  Worked with Benjamin Herrenschmidt on GPFS tracing kernel driver code
  and he made a suggestion as workaround on the driver code to bypass
  the problem, and it works

  the workaround code change as below:

   - rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, PAGE_SHARED);
  + rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, 
__pgprot(pgprot_val(PAGE_SHARED)|_PAGE_DIRTY);

  As Benjamin mentioned, this is a Linux kernel bug and this is just a
  workaround. He will give the details about the kernel bug and why this
  workaround works

  The root cause is that for PTEs created by a driver at mmap time (ie,
  that aren't created dynamically at fault time), it's not legit for
  ptep_set_access_flags() to make them invalid even temporarily. A
  concurrent access while they are invalid will be unable to service the
  page fault and will cause as SIGBUS.

  Thankfully such PTEs shouldn't normally be the subject of a RO->RW
  privilege escalation.

  What happens is that the GPFS driver creates the PTEs using
  remap_pfn_range(...,PAGE_SHARED).

  PAGE_SHARED has _PAGE_ACCESSED (R) but not _PAGE_DIRTY (C) set.

  Thus on the first write, we try set C and while doing so, hit the
  above workaround, which causes the problem described earlier.

  The proposed patch will ensure we only do the Nest MMU hack when
  changing _PAGE_RW and not for normal R/C updates.

  The workaround tested by the GPFS team consists of adding _PAGE_DIRTY
  to the mapping created by remap_pfn_range() to avoid the RC update
  fault completely.

  This is fixed by these:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd0dbb73e01306a1060e56f81e5fe287be936477

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f08d08f3db55452d31ba4a37c702da6245876b96

  Since DD1 support is still in (ie,
  2bf1071a8d50928a4ae366bb3108833166c2b70c is not applied) the second
  doesn't apply cleanly.  Did you want that attached?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1792195/+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 1761379] Comment bridged from LTC Bugzilla

--- Comment From grom...@br.ibm.com 2018-10-15 17:33 EDT---
Hi Joseph,

(In reply to comment #20)
> It's possible this is happening because I'm cross compiling.  I'll build the
> packages in a PPA, so it is a native compile.
>
> The PPA will be located at:
> https://launchpad.net/~jsalisbury/+archive/ubuntu/1761379
>
> It is currently building and should be done in an hour or two.

I'm now able to find the 'perf' binary and it works correctly.

However I'm still unable to find the ' libperf-jvmti.so`.

Could you please check it again and confirm in which package exactly
Canonical will provide such a file?

Thanks and best regards,
Gustavo

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

Title:
  [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common
  deb on Ubuntu

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  ---Problem Description---
  File libperf-jvmti.so is missing in linux-tools-common deb making it 
impossible to use perf for the JVM JITed methods
   
  ---uname output---
  inux-image-4.13.0-36-generic
   
  Machine Type = not relevant 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   File libperf-jvmti.so is missing in linux-tools-common deb provided for 
Ubuntu 17.10 making it impossible to use perf for the JVM JITed methods. I also 
checked if the file is available on launchpad 
(https://launchpad.net/ubuntu/+source/linux) for Bionic Beaver proposed (main) 
at it's also absent there:

  gromero@ltc-wspoon3:~/download$ dpkg -c 
linux-tools-common_4.15.0-13.14_all.deb | fgrep jvm
  gromero@ltc-wspoon3:~/download$ dpkg -c 
linux-tools-4.15.0-13-generic_4.15.0-13.14_ppc64el.deb | fgrep jvm

  I do see the file in tools/perf/jvmti dir in the source .tar.gz, but
  apparently it's no being packaged in any .deb file?

  Thanks. 
   

   
  Userspace tool common name: perf 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace tool obtained from project website:  na

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1761379/+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 1797975] Missing required logs.

2018-10-15 Thread Ubuntu Kernel Bot

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

apport-collect 1797975

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

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

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

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

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

Title:
  [armhf+raspi2] Error: Driver 'sdhost-bcm2835' is already registered,
  aborting

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The follow error is shown in dmesg on my Raspberry Pi 2:

  [4.380151] device-mapper: uevent: version 1.0.3
  [4.388525] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: 
dm-de...@redhat.com
  [4.396718] bcm2835-cpufreq: min=60 max=90
  [4.407362] sdhci: Secure Digital Host Controller Interface driver
  [4.412699] sdhci: Copyright(c) Pierre Ossman
  [4.418378] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe
  [4.423879] Error: Driver 'sdhost-bcm2835' is already registered, 
aborting...

  This may not be an issue at all, I don't know.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 22 11:11 seq
   crw-rw 1 root audio 116, 33 Jun 22 11:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: armhf
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 18.10
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
   Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 BCM2708 FB
  ProcKernelCmdLine: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1824 
bcm2708_fb.fbheight=984 bcm2709.boardrev=0xa01041 bcm2709.serial=0x17b63586 
smsc95xx.macaddr=B8:27:EB:B6:35:86 bcm2708_fb.fbswap=1 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=47 
bcm2709.disk_led_active_low=0 vc_mem.mem_base=0x3dc0 
vc_mem.mem_size=0x3f00  net.ifnames=0 dwc_otg.lpm_enable=0 
console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 
elevator=deadline rootwait
  ProcVersionSignature: User Name 4.18.0-1004.6-raspi2 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-1004-raspi2 N/A
   linux-backports-modules-4.18.0-1004-raspi2  N/A
   linux-firmware  1.175
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  cosmic uec-images
  Uname: Linux 4.18.0-1004-raspi2 armv7l
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797975/+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 1794641] Re: Slow boot caused by unresponsive internal sd card reader

2018-10-15 Thread recovered buzzy

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

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

Title:
  Slow boot caused by unresponsive internal sd card reader

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running Ubuntu 18.04 / Mac OS High Sierra Dual Boot on Macbook Pro
  11,1. I've had a long standing kernel problem, that is still present
  for Ubuntu's linux-generic 4.15.0-34 kernel.

  Since roughly December the system has two kinds of boots: good and
  bad. I had been running 16.04 until a few days ago. I was hoping an
  18.04 update would get rid of this problem. The problem remains, both
  with the canonical's 4.15 generic kernel and the 4.19 rc4 kernel. I
  even updated Mac OS to High Sierra in hopes that would update any
  potential firmware updates might resolve the issue.

  No dice. Hope this bug report can get the ball rolling.

  The Boots--
  Good Boot:
  5 seconds from power on chime to refind bootmanager, 5 seconds to kernel 
space, 10-15 userspace.
  Bad Boot:
  it takes about 20-30 to get to my boot manager after I select the kernel to 
use, it takes roughly 50 seconds, most of that time is spent with the kernel 
trying to assign an address to usb 2-3: my computer's SD Card Reader. Something 
prevents it from doing so and it gives up after trying all 4 usb ports twice. 
(Eats 40 seconds).

  On a Good Boot the SD Card Reader works just fine. On a Bad Boot it is
  completely nonfunctional.

  When are Good Boot and Bad Boots?-
  Cold Reboots are always Bad.
  After a Bad Boot, a warm reboot is always Good.
  A warm reboot after a Good boot is always Bad.

  I've compared the dmesg logs between the different boots and they are
  quite different. Something in the shutdown/reboot process is really
  altering how the kernel behaves. Since the slowdown starts before the
  boot manager I've been suspicious of the EFI. Checking EFI variables
  between these two boots shows an EFI variable is present after a good
  boot that is not present after a bad boot: usb-cr-rec-7c436110-ab2a-
  4bbb-a880-fe41995c9f82. This appears to be a Mac specific setting. I
  don't know what it does, but I can confirm that speeds up the boot
  process when present, regardless of which operating system I boot.

  I'm aware this might be an EFI issue that I might have to talk to
  Apple about. However, Apple's kernel seems to handle the SD card
  reader gracefully, rather than leave a 40 unresponsive blank screen
  whilst booting.

  I have attached the slow boot dmesg logs for Canonical's 4.15.0-34
  kernel. The big gaps of kernel time are generally accompanied by lines
  like

  usb 2-3: device not accepting address 4, error -62.

  I'd like to attach files for for current 4.15 Ubuntu and 4.19 Mainline fast 
and slow boots, but there
  only seems to be one attachment allowed. 

  General info
  ==
  uname -all
  ==

  Linux james-MacBookPro 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27
  15:21:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  ==
  lspci -vvnn
  ==

  00:00.0 Host bridge [0600]: Intel Corporation Haswell-ULT DRAM Controller 
[8086:0a04] (rev 09)
Subsystem: Apple Inc. Haswell-ULT DRAM Controller [106b:011a]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: hsw_uncore

  00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT 
Integrated Graphics Controller [8086:0a2e] (rev 09) (prog-if 00 [VGA 
controller])
Subsystem: Apple Inc. Haswell-ULT Integrated Graphics Controller 
[106b:011a]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

  00:03.0 Audio device [0403]: Intel Corporation Haswell-ULT HD Audio 
Controller [8086:0a0c] (rev 09)
Subsystem: Apple Inc. Haswell-ULT HD Audio Controller [106b:011a]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

  00:14.0 USB controller [0c03]: Intel Corporation 8 Series USB xHCI HC 
[8086:9c31] (rev 04) (prog-if 30 [XHCI])
Subsystem: Intel Corporation Apple MacBookAir6,2 / MacBookPro11,1 
[8086:7270]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use:

[Kernel-packages] [Bug 1797975] WifiSyslog.txt

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1797975/+attachment/5201404/+files/WifiSyslog.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/1797975

Title:
  [armhf+raspi2] Error: Driver 'sdhost-bcm2835' is already registered,
  aborting

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The follow error is shown in dmesg on my Raspberry Pi 2:

  [4.380151] device-mapper: uevent: version 1.0.3
  [4.388525] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: 
dm-de...@redhat.com
  [4.396718] bcm2835-cpufreq: min=60 max=90
  [4.407362] sdhci: Secure Digital Host Controller Interface driver
  [4.412699] sdhci: Copyright(c) Pierre Ossman
  [4.418378] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe
  [4.423879] Error: Driver 'sdhost-bcm2835' is already registered, 
aborting...

  This may not be an issue at all, I don't know.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 22 11:11 seq
   crw-rw 1 root audio 116, 33 Jun 22 11:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: armhf
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 18.10
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
   Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 BCM2708 FB
  ProcKernelCmdLine: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1824 
bcm2708_fb.fbheight=984 bcm2709.boardrev=0xa01041 bcm2709.serial=0x17b63586 
smsc95xx.macaddr=B8:27:EB:B6:35:86 bcm2708_fb.fbswap=1 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=47 
bcm2709.disk_led_active_low=0 vc_mem.mem_base=0x3dc0 
vc_mem.mem_size=0x3f00  net.ifnames=0 dwc_otg.lpm_enable=0 
console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 
elevator=deadline rootwait
  ProcVersionSignature: User Name 4.18.0-1004.6-raspi2 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-1004-raspi2 N/A
   linux-backports-modules-4.18.0-1004-raspi2  N/A
   linux-firmware  1.175
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  cosmic uec-images
  Uname: Linux 4.18.0-1004-raspi2 armv7l
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

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

apport information

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

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

Title:
  [armhf+raspi2] Error: Driver 'sdhost-bcm2835' is already registered,
  aborting

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The follow error is shown in dmesg on my Raspberry Pi 2:

  [4.380151] device-mapper: uevent: version 1.0.3
  [4.388525] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: 
dm-de...@redhat.com
  [4.396718] bcm2835-cpufreq: min=60 max=90
  [4.407362] sdhci: Secure Digital Host Controller Interface driver
  [4.412699] sdhci: Copyright(c) Pierre Ossman
  [4.418378] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe
  [4.423879] Error: Driver 'sdhost-bcm2835' is already registered, 
aborting...

  This may not be an issue at all, I don't know.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 22 11:11 seq
   crw-rw 1 root audio 116, 33 Jun 22 11:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: armhf
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 18.10
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
   Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 BCM2708 FB
  ProcKernelCmdLine: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1824 
bcm2708_fb.fbheight=984 bcm2709.boardrev=0xa01041 bcm2709.serial=0x17b63586 
smsc95xx.macaddr=B8:27:EB:B6:35:86 bcm2708_fb.fbswap=1 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=47 
bcm2709.disk_led_active_low=0 vc_mem.mem_base=0x3dc0 
vc_mem.mem_size=0x3f00  net.ifnames=0 dwc_otg.lpm_enable=0 
console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 
elevator=deadline rootwait
  ProcVersionSignature: User Name 4.18.0-1004.6-raspi2 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-1004-raspi2 N/A
   linux-backports-modules-4.18.0-1004-raspi2  N/A
   linux-firmware  1.175
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  cosmic uec-images
  Uname: Linux 4.18.0-1004-raspi2 armv7l
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

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

apport information

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

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

Title:
  [armhf+raspi2] Error: Driver 'sdhost-bcm2835' is already registered,
  aborting

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The follow error is shown in dmesg on my Raspberry Pi 2:

  [4.380151] device-mapper: uevent: version 1.0.3
  [4.388525] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: 
dm-de...@redhat.com
  [4.396718] bcm2835-cpufreq: min=60 max=90
  [4.407362] sdhci: Secure Digital Host Controller Interface driver
  [4.412699] sdhci: Copyright(c) Pierre Ossman
  [4.418378] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe
  [4.423879] Error: Driver 'sdhost-bcm2835' is already registered, 
aborting...

  This may not be an issue at all, I don't know.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 22 11:11 seq
   crw-rw 1 root audio 116, 33 Jun 22 11:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: armhf
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 18.10
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
   Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 BCM2708 FB
  ProcKernelCmdLine: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1824 
bcm2708_fb.fbheight=984 bcm2709.boardrev=0xa01041 bcm2709.serial=0x17b63586 
smsc95xx.macaddr=B8:27:EB:B6:35:86 bcm2708_fb.fbswap=1 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=47 
bcm2709.disk_led_active_low=0 vc_mem.mem_base=0x3dc0 
vc_mem.mem_size=0x3f00  net.ifnames=0 dwc_otg.lpm_enable=0 
console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 
elevator=deadline rootwait
  ProcVersionSignature: User Name 4.18.0-1004.6-raspi2 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-1004-raspi2 N/A
   linux-backports-modules-4.18.0-1004-raspi2  N/A
   linux-firmware  1.175
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  cosmic uec-images
  Uname: Linux 4.18.0-1004-raspi2 armv7l
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

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

apport information

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

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

Title:
  [armhf+raspi2] Error: Driver 'sdhost-bcm2835' is already registered,
  aborting

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The follow error is shown in dmesg on my Raspberry Pi 2:

  [4.380151] device-mapper: uevent: version 1.0.3
  [4.388525] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: 
dm-de...@redhat.com
  [4.396718] bcm2835-cpufreq: min=60 max=90
  [4.407362] sdhci: Secure Digital Host Controller Interface driver
  [4.412699] sdhci: Copyright(c) Pierre Ossman
  [4.418378] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe
  [4.423879] Error: Driver 'sdhost-bcm2835' is already registered, 
aborting...

  This may not be an issue at all, I don't know.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 22 11:11 seq
   crw-rw 1 root audio 116, 33 Jun 22 11:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: armhf
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 18.10
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
   Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 BCM2708 FB
  ProcKernelCmdLine: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1824 
bcm2708_fb.fbheight=984 bcm2709.boardrev=0xa01041 bcm2709.serial=0x17b63586 
smsc95xx.macaddr=B8:27:EB:B6:35:86 bcm2708_fb.fbswap=1 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=47 
bcm2709.disk_led_active_low=0 vc_mem.mem_base=0x3dc0 
vc_mem.mem_size=0x3f00  net.ifnames=0 dwc_otg.lpm_enable=0 
console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 
elevator=deadline rootwait
  ProcVersionSignature: User Name 4.18.0-1004.6-raspi2 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-1004-raspi2 N/A
   linux-backports-modules-4.18.0-1004-raspi2  N/A
   linux-firmware  1.175
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  cosmic uec-images
  Uname: Linux 4.18.0-1004-raspi2 armv7l
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797975/+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 1797975] [NEW] [armhf+raspi2] Error: Driver 'sdhost-bcm2835' is already registered, aborting

Public bug reported:

The follow error is shown in dmesg on my Raspberry Pi 2:

[4.380151] device-mapper: uevent: version 1.0.3
[4.388525] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: 
dm-de...@redhat.com
[4.396718] bcm2835-cpufreq: min=60 max=90
[4.407362] sdhci: Secure Digital Host Controller Interface driver
[4.412699] sdhci: Copyright(c) Pierre Ossman
[4.418378] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe
[4.423879] Error: Driver 'sdhost-bcm2835' is already registered, aborting...

This may not be an issue at all, I don't know.
--- 
ProblemType: Bug
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Jun 22 11:11 seq
 crw-rw 1 root audio 116, 33 Jun 22 11:11 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu13
Architecture: armhf
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 18.10
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
 Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
 Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Package: linux (not installed)
PciMultimedia:
 
ProcFB: 0 BCM2708 FB
ProcKernelCmdLine: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1824 
bcm2708_fb.fbheight=984 bcm2709.boardrev=0xa01041 bcm2709.serial=0x17b63586 
smsc95xx.macaddr=B8:27:EB:B6:35:86 bcm2708_fb.fbswap=1 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=47 
bcm2709.disk_led_active_low=0 vc_mem.mem_base=0x3dc0 
vc_mem.mem_size=0x3f00  net.ifnames=0 dwc_otg.lpm_enable=0 
console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 
elevator=deadline rootwait
ProcVersionSignature: User Name 4.18.0-1004.6-raspi2 4.18.7
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-1004-raspi2 N/A
 linux-backports-modules-4.18.0-1004-raspi2  N/A
 linux-firmware  1.175
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags:  cosmic uec-images
Uname: Linux 4.18.0-1004-raspi2 armv7l
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
_MarkForUpload: True

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


** Tags: apport-collected bot-stop-nagging cosmic uec-images

** Tags added: bot-stop-nagging

** Tags added: apport-collected cosmic uec-images

** Description changed:

  The follow error is shown in dmesg on my Raspberry Pi 2:
  
  [4.380151] device-mapper: uevent: version 1.0.3
  [4.388525] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: 
dm-de...@redhat.com
  [4.396718] bcm2835-cpufreq: min=60 max=90
  [4.407362] sdhci: Secure Digital Host Controller Interface driver
  [4.412699] sdhci: Copyright(c) Pierre Ossman
  [4.418378] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe
  [4.423879] Error: Driver 'sdhost-bcm2835' is already registered, 
aborting...
  
  This may not be an issue at all, I don't know.
+ --- 
+ ProblemType: Bug
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116,  1 Jun 22 11:11 seq
+  crw-rw 1 root audio 116, 33 Jun 22 11:11 timer
+ AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
+ ApportVersion: 2.20.10-0ubuntu13
+ Architecture: armhf
+ ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ CRDA: N/A
+ DistroRelease: Ubuntu 18.10
+ IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
+ Lsusb:
+  Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
+  Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcFB: 0 BCM2708 FB
+ ProcKernelCmdLine: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1824 
bcm2708_fb.fbheight=984 bcm2709.boardrev=0xa01041 bcm2709.serial=0x17b63586 
smsc95xx.macaddr=B8:27:EB:B6:35:86 bcm2708_fb.fbswap=1 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=47 
bcm2709.disk_led_active_low=0 vc_mem.mem_base=0x3dc0 
vc_mem.mem_size=0x3f00  net.ifnames=0 dwc_otg.lpm_enable=0 
console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 
elevator=deadline rootwait
+ ProcVersionSignature: User Name 4.18.0-1004.6-raspi2 4.18.7
+ RelatedPackageVersions:
+  linux-restricted-modules-4.18.0-1004-raspi2 N/A
+  linux-backports-modules-4.18.0-1004-raspi2  N/A
+  linux-firmware

[Kernel-packages] [Bug 1797975] ProcCpuinfoMinimal.txt

apport information

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

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

Title:
  [armhf+raspi2] Error: Driver 'sdhost-bcm2835' is already registered,
  aborting

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The follow error is shown in dmesg on my Raspberry Pi 2:

  [4.380151] device-mapper: uevent: version 1.0.3
  [4.388525] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: 
dm-de...@redhat.com
  [4.396718] bcm2835-cpufreq: min=60 max=90
  [4.407362] sdhci: Secure Digital Host Controller Interface driver
  [4.412699] sdhci: Copyright(c) Pierre Ossman
  [4.418378] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe
  [4.423879] Error: Driver 'sdhost-bcm2835' is already registered, 
aborting...

  This may not be an issue at all, I don't know.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 22 11:11 seq
   crw-rw 1 root audio 116, 33 Jun 22 11:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: armhf
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 18.10
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
   Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 BCM2708 FB
  ProcKernelCmdLine: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1824 
bcm2708_fb.fbheight=984 bcm2709.boardrev=0xa01041 bcm2709.serial=0x17b63586 
smsc95xx.macaddr=B8:27:EB:B6:35:86 bcm2708_fb.fbswap=1 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=47 
bcm2709.disk_led_active_low=0 vc_mem.mem_base=0x3dc0 
vc_mem.mem_size=0x3f00  net.ifnames=0 dwc_otg.lpm_enable=0 
console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 
elevator=deadline rootwait
  ProcVersionSignature: User Name 4.18.0-1004.6-raspi2 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-1004-raspi2 N/A
   linux-backports-modules-4.18.0-1004-raspi2  N/A
   linux-firmware  1.175
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  cosmic uec-images
  Uname: Linux 4.18.0-1004-raspi2 armv7l
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

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

apport information

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

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

Title:
  [armhf+raspi2] Error: Driver 'sdhost-bcm2835' is already registered,
  aborting

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The follow error is shown in dmesg on my Raspberry Pi 2:

  [4.380151] device-mapper: uevent: version 1.0.3
  [4.388525] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: 
dm-de...@redhat.com
  [4.396718] bcm2835-cpufreq: min=60 max=90
  [4.407362] sdhci: Secure Digital Host Controller Interface driver
  [4.412699] sdhci: Copyright(c) Pierre Ossman
  [4.418378] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe
  [4.423879] Error: Driver 'sdhost-bcm2835' is already registered, 
aborting...

  This may not be an issue at all, I don't know.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 22 11:11 seq
   crw-rw 1 root audio 116, 33 Jun 22 11:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: armhf
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 18.10
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
   Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 BCM2708 FB
  ProcKernelCmdLine: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1824 
bcm2708_fb.fbheight=984 bcm2709.boardrev=0xa01041 bcm2709.serial=0x17b63586 
smsc95xx.macaddr=B8:27:EB:B6:35:86 bcm2708_fb.fbswap=1 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=47 
bcm2709.disk_led_active_low=0 vc_mem.mem_base=0x3dc0 
vc_mem.mem_size=0x3f00  net.ifnames=0 dwc_otg.lpm_enable=0 
console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 
elevator=deadline rootwait
  ProcVersionSignature: User Name 4.18.0-1004.6-raspi2 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-1004-raspi2 N/A
   linux-backports-modules-4.18.0-1004-raspi2  N/A
   linux-firmware  1.175
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  cosmic uec-images
  Uname: Linux 4.18.0-1004-raspi2 armv7l
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

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

apport information

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

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

Title:
  [armhf+raspi2] Error: Driver 'sdhost-bcm2835' is already registered,
  aborting

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The follow error is shown in dmesg on my Raspberry Pi 2:

  [4.380151] device-mapper: uevent: version 1.0.3
  [4.388525] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: 
dm-de...@redhat.com
  [4.396718] bcm2835-cpufreq: min=60 max=90
  [4.407362] sdhci: Secure Digital Host Controller Interface driver
  [4.412699] sdhci: Copyright(c) Pierre Ossman
  [4.418378] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe
  [4.423879] Error: Driver 'sdhost-bcm2835' is already registered, 
aborting...

  This may not be an issue at all, I don't know.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 22 11:11 seq
   crw-rw 1 root audio 116, 33 Jun 22 11:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: armhf
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 18.10
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
   Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 BCM2708 FB
  ProcKernelCmdLine: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1824 
bcm2708_fb.fbheight=984 bcm2709.boardrev=0xa01041 bcm2709.serial=0x17b63586 
smsc95xx.macaddr=B8:27:EB:B6:35:86 bcm2708_fb.fbswap=1 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=47 
bcm2709.disk_led_active_low=0 vc_mem.mem_base=0x3dc0 
vc_mem.mem_size=0x3f00  net.ifnames=0 dwc_otg.lpm_enable=0 
console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 
elevator=deadline rootwait
  ProcVersionSignature: User Name 4.18.0-1004.6-raspi2 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-1004-raspi2 N/A
   linux-backports-modules-4.18.0-1004-raspi2  N/A
   linux-firmware  1.175
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  cosmic uec-images
  Uname: Linux 4.18.0-1004-raspi2 armv7l
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

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

apport information

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

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

Title:
  [armhf+raspi2] Error: Driver 'sdhost-bcm2835' is already registered,
  aborting

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The follow error is shown in dmesg on my Raspberry Pi 2:

  [4.380151] device-mapper: uevent: version 1.0.3
  [4.388525] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: 
dm-de...@redhat.com
  [4.396718] bcm2835-cpufreq: min=60 max=90
  [4.407362] sdhci: Secure Digital Host Controller Interface driver
  [4.412699] sdhci: Copyright(c) Pierre Ossman
  [4.418378] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe
  [4.423879] Error: Driver 'sdhost-bcm2835' is already registered, 
aborting...

  This may not be an issue at all, I don't know.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 22 11:11 seq
   crw-rw 1 root audio 116, 33 Jun 22 11:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: armhf
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 18.10
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
   Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 BCM2708 FB
  ProcKernelCmdLine: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1824 
bcm2708_fb.fbheight=984 bcm2709.boardrev=0xa01041 bcm2709.serial=0x17b63586 
smsc95xx.macaddr=B8:27:EB:B6:35:86 bcm2708_fb.fbswap=1 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=47 
bcm2709.disk_led_active_low=0 vc_mem.mem_base=0x3dc0 
vc_mem.mem_size=0x3f00  net.ifnames=0 dwc_otg.lpm_enable=0 
console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 
elevator=deadline rootwait
  ProcVersionSignature: User Name 4.18.0-1004.6-raspi2 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-1004-raspi2 N/A
   linux-backports-modules-4.18.0-1004-raspi2  N/A
   linux-firmware  1.175
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  cosmic uec-images
  Uname: Linux 4.18.0-1004-raspi2 armv7l
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797975/+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 1797963] Re: not able to unwind the stack from within __kernel_clock_gettime in the Linux vDSO

2018-10-15 Thread Joseph Salisbury

I built a test kernel with linux-next commit 56d20861c027.  The test kernel can 
be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1797963

Can you test this kernel and see if it resolves this bug?

Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the 
linux-image and linux-image-extra .deb packages.
• If the test kernel is 4.15(Bionic) or newer, you need to install the 
linux-modules, linux-modules-extra and linux-image-unsigned .deb packages.

Thanks in advance!

** Also affects: linux (Ubuntu Cosmic)
   Importance: High
 Assignee: Canonical Kernel Team (canonical-kernel-team)
   Status: New

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

** Changed in: linux (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: linux (Ubuntu Cosmic)
   Status: New => In Progress

** Changed in: linux (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Cosmic)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph 
Salisbury (jsalisbury)

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

Title:
  not able to unwind the stack from within __kernel_clock_gettime in the
  Linux vDSO

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  Description

  We're not able to unwind the stack from within __kernel_clock_gettime
  in the Linux vDSO on Summit. This affects both DDT and MAP (via GDB
  and libunwind). The issue is more serious than may first appear as the
  function appears to be called somewhat often by the CUDA runtime, and
  can defer to a syscall making it relatively time consuming (making it
  more likely to be encountered).

  To reproduce:

  Compile $CUDA_DIR/samples/0_Simple/matrixMul (attached is a small
  patch to modify the Makefile to compile outside of the samples
  directory)

  Run the following GDB commands:
  user@deb3qwsp1:/usr/local/cuda-10.0/samples/0_Simple/matrixMul$ gdb 
./matrixMul 
  GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git
  Copyright (C) 2018 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from ./matrixMul...(no debugging symbols found)...done.
  (gdb) break main
  Breakpoint 1 at 0x8284
  (gdb) run
  Starting program: /usr/local/cuda-10.0/samples/0_Simple/matrixMul/matrixMul 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library 
"/lib/powerpc64le-linux-gnu/libthread_db.so.1".

  Breakpoint 1, 0x00018284 in main ()
  (gdb) break *(__kernel_clock_gettime+144)
  Breakpoint 2 at 0x77f805e4: file 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S, 
line 127.
  (gdb) continue
  Continuing.
  [Matrix Multiply Using CUDA] - Starting...

  Breakpoint 2, __kernel_clock_gettime () at 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S:127
  127   
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S: No 
such file or directory.
  (gdb) bt
  #0  __kernel_clock_gettime () at 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S:127
  #1  0x77b8f530 in ?? () from /lib/powerpc64le-linux-gnu/libc.so.6
  #2  0x76b81118 in ?? () from 
/usr/lib/powerpc64le-linux-gnu/libcuda.so.1
  #3  0x76a69c70 in ?? () from 
/usr/lib/powerpc64le-linux-gnu/libcuda.so.1
  #4  0x76bf0ba0 in cuInit () from 
/usr/lib/powerpc64le-linux-gnu/libcuda.so.1
  #5  0x00010003ca50 in cudart::__loadDriverInternalUtil() ()
  #6  0x77f05274 in __pthread_once_slow (
  once_control=0x1000c00f0 
, 
  init_routine=0x10003c950 ) at 
pthread_once.c:116
  #7  0x00010008ea88 in cudart::cuosOnce(int*, void (*)()) ()
  #8  0x0001000410a8 in cudart::globalState::initializeDriver() ()
  #9  0x00010005ec90 in cudaGetDeviceCount ()
  #10 0x00019930 in gpuGetMaxGflopsDeviceId() ()
  #11 0x00019bf4 in findCudaDevice(int, char const**)

[Kernel-packages] [Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode

2018-10-15 Thread Eric Desrochers

Might be a good idea to enable some systemd parameter for debugging
purposes : https://freedesktop.org/wiki/Software/systemd/Debugging/

Enabling tty9 w/ systemd.debug-shell=1

and possibly the following :

Diagnosing Shutdown Problems
Just like with boot problems, when you encounter a hang during shutting down, 
make sure you wait at least 5 minutes to distinguish a permanent hang from a 
broken service that's just timing out. Then it's worth testing whether the 
system reacts to CTRL+ALT+DEL in any way.

If shutdown (whether it be to reboot or power-off) of your system gets
stuck, first test if the kernel itself is able to reboot or power-off
the machine forcedly using one of these commands:

reboot -f
poweroff -f
If either one of the commands does not work, it's more likely to be a kernel, 
not systemd bug.

Shutdown Completes Eventually
If normal reboot or poweroff work, but take a suspiciously long time, then

boot with the debug options:

systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M 
printk.devkmsg=on enforcing=0
save the following script as /usr/lib/systemd/system-shutdown/debug.sh and make 
it executable:

#!/bin/sh
mount -o remount,rw /
dmesg > /shutdown-log.txt
mount -o remount,ro /
reboot

Look for timeouts logged in the resulting file shutdown-log.txt and/or
attach it to a bugreport.

Shutdown Never Finishes
If normal reboot or poweroff never finish even after waiting a few minutes, the 
above method to create the shutdown log will not help and the log must be 
obtained using other methods. Two options that are useful for debugging boot 
problems can be used also for shutdown problems:

use a serial console
use a debug shell - not only is it available from early boot, it also stays 
active until late shutdown.

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

Title:
  Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable
  with unattended-upgrades on shutdown mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since the following linux-cloud-tools-common package versions :

  Xenial : 4.4.0-135.161
  Bionic : 4.15.0-34.37

  the Systemd service unit file for hv-kvp-daemon has been modified with new 
dependencies that make the package unable to be upgraded with 
unattended-upgrades on shutdown mode.
  Unattended-upgrades hangs with the linux-cloud-tools-common package during 
"Preparing to unpack". The server restarts after the unattended-upgrades 
service timeout expires.

  - Package state after reboot :

  iFR linux-cloud-tools-common  4.15.0-34.37
  all  Linux kernel version specific cloud tools for version
  4.15.0

  - Unattended-upgrades dpkg logs :

  Log started: 2018-10-05  17:59:04
  (Reading database ... 52043 files and directories currently installed.)
  Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ...
  Log ended: 2018-10-05  18:00:54

  - Impact :

  The current impact is very important as all security updates are
  blocked until you manually fix each server with :

  dpkg --configure -a
  apt install --only-upgrade linux-cloud-tools-common

  - Workaround/Fix :

  As a simple straightforward fix, replacing :

  Before=shutdown.target cloud-init-local.service walinuxagent.service

  with :

  Before=shutdown.target walinuxagent.service

  makes the package upgradable during shutdown.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+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 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode

2018-10-15 Thread Eric Desrochers

It may help to better understand what's going on.

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

Title:
  Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable
  with unattended-upgrades on shutdown mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since the following linux-cloud-tools-common package versions :

  Xenial : 4.4.0-135.161
  Bionic : 4.15.0-34.37

  the Systemd service unit file for hv-kvp-daemon has been modified with new 
dependencies that make the package unable to be upgraded with 
unattended-upgrades on shutdown mode.
  Unattended-upgrades hangs with the linux-cloud-tools-common package during 
"Preparing to unpack". The server restarts after the unattended-upgrades 
service timeout expires.

  - Package state after reboot :

  iFR linux-cloud-tools-common  4.15.0-34.37
  all  Linux kernel version specific cloud tools for version
  4.15.0

  - Unattended-upgrades dpkg logs :

  Log started: 2018-10-05  17:59:04
  (Reading database ... 52043 files and directories currently installed.)
  Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ...
  Log ended: 2018-10-05  18:00:54

  - Impact :

  The current impact is very important as all security updates are
  blocked until you manually fix each server with :

  dpkg --configure -a
  apt install --only-upgrade linux-cloud-tools-common

  - Workaround/Fix :

  As a simple straightforward fix, replacing :

  Before=shutdown.target cloud-init-local.service walinuxagent.service

  with :

  Before=shutdown.target walinuxagent.service

  makes the package upgradable during shutdown.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+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 1797628] Re: System hangs during boot at "Started configure plugged in printer"

2018-10-15 Thread Michael Ehling

This started happening after the distribution upgrade from Bionic 18.04
which I did in the first few days of October 2018. (Sorry for lack of
specificity here.)

Tested the latest upstream kernel: 4.19rc8. Problem still exists. I set
the take 'kernel-bug-exists-upstream.'

Set status to 'confirmed.'

Thanks!

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

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

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

Title:
  System hangs during boot at "Started configure plugged in printer"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System: Lenovo T430s with HP OfficeJet Pro 8600 attached via usb hub

  Followed general bug reporting instructions (including
  https://wiki.ubuntu.com/Bugs/FindRightPackage). This may be kernel
  related, not xorg.

  What I tried: rebooting
  What I expected: to see the login screen
  What happened: booting hangs

  Rebooted using 'E' option in grub to remove splash and quiet. Saw
  system hang at "Started configure plugged in printer"

  When I unplug the USB hub (to which the printer is connected), I can
  reboot and login fine then reinsert USB hub.

  After this "fix," I can reboot fine without unplugging anything. This
  bug appears to happen right after a system update (running Software
  Updater and there are kernel bits to update).

  This is new behaviour; I had the same system setup running and booting
  fine under 18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12
  Uname: Linux 4.18.0-9-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 12 15:48:22 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fb]
  InstallationDate: Installed on 2018-10-02 (10 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  MachineType: LENOVO 2356CU8
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-9-generic 
root=UUID=e307efee-e562-4d24-9632-4a97a84073ee ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/22/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G7ET91WW (2.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2356CU8
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: 529944
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG7ET91WW(2.51):bd01/22/2013:svnLENOVO:pn2356CU8:pvrThinkPadT430s:rvnLENOVO:rn2356CU8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430s
  dmi.product.name: 2356CU8
  dmi.product.sku: LENOVO_MT_2356
  dmi.product.version: ThinkPad T430s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797628/+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 1797963] Re: not able to unwind the stack from within __kernel_clock_gettime in the Linux vDSO

2018-10-15 Thread Manoj Iyer

** Changed in: linux (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Canonical Kernel Team (canonical-kernel-team)

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

Title:
  not able to unwind the stack from within __kernel_clock_gettime in the
  Linux vDSO

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  Description

  We're not able to unwind the stack from within __kernel_clock_gettime
  in the Linux vDSO on Summit. This affects both DDT and MAP (via GDB
  and libunwind). The issue is more serious than may first appear as the
  function appears to be called somewhat often by the CUDA runtime, and
  can defer to a syscall making it relatively time consuming (making it
  more likely to be encountered).

  To reproduce:

  Compile $CUDA_DIR/samples/0_Simple/matrixMul (attached is a small
  patch to modify the Makefile to compile outside of the samples
  directory)

  Run the following GDB commands:
  user@deb3qwsp1:/usr/local/cuda-10.0/samples/0_Simple/matrixMul$ gdb 
./matrixMul 
  GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git
  Copyright (C) 2018 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from ./matrixMul...(no debugging symbols found)...done.
  (gdb) break main
  Breakpoint 1 at 0x8284
  (gdb) run
  Starting program: /usr/local/cuda-10.0/samples/0_Simple/matrixMul/matrixMul 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library 
"/lib/powerpc64le-linux-gnu/libthread_db.so.1".

  Breakpoint 1, 0x00018284 in main ()
  (gdb) break *(__kernel_clock_gettime+144)
  Breakpoint 2 at 0x77f805e4: file 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S, 
line 127.
  (gdb) continue
  Continuing.
  [Matrix Multiply Using CUDA] - Starting...

  Breakpoint 2, __kernel_clock_gettime () at 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S:127
  127   
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S: No 
such file or directory.
  (gdb) bt
  #0  __kernel_clock_gettime () at 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S:127
  #1  0x77b8f530 in ?? () from /lib/powerpc64le-linux-gnu/libc.so.6
  #2  0x76b81118 in ?? () from 
/usr/lib/powerpc64le-linux-gnu/libcuda.so.1
  #3  0x76a69c70 in ?? () from 
/usr/lib/powerpc64le-linux-gnu/libcuda.so.1
  #4  0x76bf0ba0 in cuInit () from 
/usr/lib/powerpc64le-linux-gnu/libcuda.so.1
  #5  0x00010003ca50 in cudart::__loadDriverInternalUtil() ()
  #6  0x77f05274 in __pthread_once_slow (
  once_control=0x1000c00f0 
, 
  init_routine=0x10003c950 ) at 
pthread_once.c:116
  #7  0x00010008ea88 in cudart::cuosOnce(int*, void (*)()) ()
  #8  0x0001000410a8 in cudart::globalState::initializeDriver() ()
  #9  0x00010005ec90 in cudaGetDeviceCount ()
  #10 0x00019930 in gpuGetMaxGflopsDeviceId() ()
  #11 0x00019bf4 in findCudaDevice(int, char const**) ()
  #12 0x0001836c in main ()
  (gdb) step
  128   in 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S
  (gdb) bt
  #0  __kernel_clock_gettime () at 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S:128
  #1  0x in ?? ()
  (gdb) 

  
  Note: __kernel_clock_gettime+144 is currently the point in the function at 
which the syscall made, and is liable to change if updated. It corresponds to 
the "sc" instruction here: 
https://gitlab.com/TeeFirefly/linux-kernel/blob/7408b38cfdf9b0c6c3bda97402c75bd27ef69a85/arch/powerpc/kernel/vdso64/gettimeofday.S#L127
 and can be rediscovered if needed by disassembling the function.

  Note that a backtrace can be collected before entering the syscall,
  but not during. The inability to unwind also prevents GDB from being
  able to "finish" (step out of) the function:

  (gdb) finish
  Run till exit from #0  __kernel_clock_gettime ()
  at 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S:128

[Kernel-packages] [Bug 1797967] [NEW] zfs-dkms 0.7.5-1ubuntu16.4: zfs kernel module failed to build

2018-10-15 Thread Piotrek

Public bug reported:

I was doing an ordinary system update.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: zfs-dkms 0.7.5-1ubuntu16.4
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
DKMSBuildLog:
 DKMS make.log for zfs-0.7.5 for kernel 4.15.0-36-generic (x86_64)
 pon, 15 paź 2018, 21:35:50 CEST
 make: *** Nie podano obiektów i nie znaleziono makefile. Stop.
DKMSKernelVersion: 4.15.0-36-generic
Date: Mon Oct 15 21:35:50 2018
InstallationDate: Installed on 2018-07-22 (85 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
PackageVersion: 0.7.5-1ubuntu16.4
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3ubuntu0.1
SourcePackage: zfs-linux
Title: zfs-dkms 0.7.5-1ubuntu16.4: zfs kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  zfs-dkms 0.7.5-1ubuntu16.4: zfs kernel module failed to build

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  I was doing an ordinary system update.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: zfs-dkms 0.7.5-1ubuntu16.4
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  DKMSBuildLog:
   DKMS make.log for zfs-0.7.5 for kernel 4.15.0-36-generic (x86_64)
   pon, 15 paź 2018, 21:35:50 CEST
   make: *** Nie podano obiektów i nie znaleziono makefile. Stop.
  DKMSKernelVersion: 4.15.0-36-generic
  Date: Mon Oct 15 21:35:50 2018
  InstallationDate: Installed on 2018-07-22 (85 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  PackageVersion: 0.7.5-1ubuntu16.4
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: zfs-linux
  Title: zfs-dkms 0.7.5-1ubuntu16.4: zfs kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1797967/+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 1797963] Re: not able to unwind the stack from within __kernel_clock_gettime in the Linux vDSO

2018-10-15 Thread Frank Heimes

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-power-systems
   Importance: Undecided => High

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

Title:
  not able to unwind the stack from within __kernel_clock_gettime in the
  Linux vDSO

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Description

  We're not able to unwind the stack from within __kernel_clock_gettime
  in the Linux vDSO on Summit. This affects both DDT and MAP (via GDB
  and libunwind). The issue is more serious than may first appear as the
  function appears to be called somewhat often by the CUDA runtime, and
  can defer to a syscall making it relatively time consuming (making it
  more likely to be encountered).

  To reproduce:

  Compile $CUDA_DIR/samples/0_Simple/matrixMul (attached is a small
  patch to modify the Makefile to compile outside of the samples
  directory)

  Run the following GDB commands:
  user@deb3qwsp1:/usr/local/cuda-10.0/samples/0_Simple/matrixMul$ gdb 
./matrixMul 
  GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git
  Copyright (C) 2018 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from ./matrixMul...(no debugging symbols found)...done.
  (gdb) break main
  Breakpoint 1 at 0x8284
  (gdb) run
  Starting program: /usr/local/cuda-10.0/samples/0_Simple/matrixMul/matrixMul 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library 
"/lib/powerpc64le-linux-gnu/libthread_db.so.1".

  Breakpoint 1, 0x00018284 in main ()
  (gdb) break *(__kernel_clock_gettime+144)
  Breakpoint 2 at 0x77f805e4: file 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S, 
line 127.
  (gdb) continue
  Continuing.
  [Matrix Multiply Using CUDA] - Starting...

  Breakpoint 2, __kernel_clock_gettime () at 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S:127
  127   
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S: No 
such file or directory.
  (gdb) bt
  #0  __kernel_clock_gettime () at 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S:127
  #1  0x77b8f530 in ?? () from /lib/powerpc64le-linux-gnu/libc.so.6
  #2  0x76b81118 in ?? () from 
/usr/lib/powerpc64le-linux-gnu/libcuda.so.1
  #3  0x76a69c70 in ?? () from 
/usr/lib/powerpc64le-linux-gnu/libcuda.so.1
  #4  0x76bf0ba0 in cuInit () from 
/usr/lib/powerpc64le-linux-gnu/libcuda.so.1
  #5  0x00010003ca50 in cudart::__loadDriverInternalUtil() ()
  #6  0x77f05274 in __pthread_once_slow (
  once_control=0x1000c00f0 
, 
  init_routine=0x10003c950 ) at 
pthread_once.c:116
  #7  0x00010008ea88 in cudart::cuosOnce(int*, void (*)()) ()
  #8  0x0001000410a8 in cudart::globalState::initializeDriver() ()
  #9  0x00010005ec90 in cudaGetDeviceCount ()
  #10 0x00019930 in gpuGetMaxGflopsDeviceId() ()
  #11 0x00019bf4 in findCudaDevice(int, char const**) ()
  #12 0x0001836c in main ()
  (gdb) step
  128   in 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S
  (gdb) bt
  #0  __kernel_clock_gettime () at 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S:128
  #1  0x in ?? ()
  (gdb) 

  
  Note: __kernel_clock_gettime+144 is currently the point in the function at 
which the syscall made, and is liable to change if updated. It corresponds to 
the "sc" instruction here: 
https://gitlab.com/TeeFirefly/linux-kernel/blob/7408b38cfdf9b0c6c3bda97402c75bd27ef69a85/arch/powerpc/kernel/vdso64/gettimeofday.S#L127
 and can be rediscovered if needed by disassembling the function.

  Note that a backtrace can be collected before entering the syscall,
  but not during. The inability to unwind also prevents GDB from being
  able to "finish" (step out of) the function:

  (gdb) finish
  Run till exit from #0  __kernel_clock_gettime ()
  at 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S:128
  Warning:

[Kernel-packages] [Bug 1797963] Re: not able to unwind the stack from within __kernel_clock_gettime in the Linux vDSO

2018-10-15 Thread Joseph Salisbury

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

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

Title:
  not able to unwind the stack from within __kernel_clock_gettime in the
  Linux vDSO

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Description

  We're not able to unwind the stack from within __kernel_clock_gettime
  in the Linux vDSO on Summit. This affects both DDT and MAP (via GDB
  and libunwind). The issue is more serious than may first appear as the
  function appears to be called somewhat often by the CUDA runtime, and
  can defer to a syscall making it relatively time consuming (making it
  more likely to be encountered).

  To reproduce:

  Compile $CUDA_DIR/samples/0_Simple/matrixMul (attached is a small
  patch to modify the Makefile to compile outside of the samples
  directory)

  Run the following GDB commands:
  user@deb3qwsp1:/usr/local/cuda-10.0/samples/0_Simple/matrixMul$ gdb 
./matrixMul 
  GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git
  Copyright (C) 2018 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from ./matrixMul...(no debugging symbols found)...done.
  (gdb) break main
  Breakpoint 1 at 0x8284
  (gdb) run
  Starting program: /usr/local/cuda-10.0/samples/0_Simple/matrixMul/matrixMul 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library 
"/lib/powerpc64le-linux-gnu/libthread_db.so.1".

  Breakpoint 1, 0x00018284 in main ()
  (gdb) break *(__kernel_clock_gettime+144)
  Breakpoint 2 at 0x77f805e4: file 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S, 
line 127.
  (gdb) continue
  Continuing.
  [Matrix Multiply Using CUDA] - Starting...

  Breakpoint 2, __kernel_clock_gettime () at 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S:127
  127   
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S: No 
such file or directory.
  (gdb) bt
  #0  __kernel_clock_gettime () at 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S:127
  #1  0x77b8f530 in ?? () from /lib/powerpc64le-linux-gnu/libc.so.6
  #2  0x76b81118 in ?? () from 
/usr/lib/powerpc64le-linux-gnu/libcuda.so.1
  #3  0x76a69c70 in ?? () from 
/usr/lib/powerpc64le-linux-gnu/libcuda.so.1
  #4  0x76bf0ba0 in cuInit () from 
/usr/lib/powerpc64le-linux-gnu/libcuda.so.1
  #5  0x00010003ca50 in cudart::__loadDriverInternalUtil() ()
  #6  0x77f05274 in __pthread_once_slow (
  once_control=0x1000c00f0 
, 
  init_routine=0x10003c950 ) at 
pthread_once.c:116
  #7  0x00010008ea88 in cudart::cuosOnce(int*, void (*)()) ()
  #8  0x0001000410a8 in cudart::globalState::initializeDriver() ()
  #9  0x00010005ec90 in cudaGetDeviceCount ()
  #10 0x00019930 in gpuGetMaxGflopsDeviceId() ()
  #11 0x00019bf4 in findCudaDevice(int, char const**) ()
  #12 0x0001836c in main ()
  (gdb) step
  128   in 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S
  (gdb) bt
  #0  __kernel_clock_gettime () at 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S:128
  #1  0x in ?? ()
  (gdb) 

  
  Note: __kernel_clock_gettime+144 is currently the point in the function at 
which the syscall made, and is liable to change if updated. It corresponds to 
the "sc" instruction here: 
https://gitlab.com/TeeFirefly/linux-kernel/blob/7408b38cfdf9b0c6c3bda97402c75bd27ef69a85/arch/powerpc/kernel/vdso64/gettimeofday.S#L127
 and can be rediscovered if needed by disassembling the function.

  Note that a backtrace can be collected before entering the syscall,
  but not during. The inability to unwind also prevents GDB from being
  able to "finish" (step out of) the function:

  (gdb) finish
  Run till exit from #0  __kernel_clock_gettime ()
  at 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S:128
  Warning:
  Cannot insert breakpoint 0.
  Cannot access memory at address 0x0

  Command aborted.
  (gdb)

  
  The cause of the issue is a lack of Call Frame Information (CFI) in the 
syscall code path, and so a

[Kernel-packages] [Bug 1797963] [NEW] not able to unwind the stack from within __kernel_clock_gettime in the Linux vDSO

Public bug reported:

Description

We're not able to unwind the stack from within __kernel_clock_gettime in
the Linux vDSO on Summit. This affects both DDT and MAP (via GDB and
libunwind). The issue is more serious than may first appear as the
function appears to be called somewhat often by the CUDA runtime, and
can defer to a syscall making it relatively time consuming (making it
more likely to be encountered).

To reproduce:

Compile $CUDA_DIR/samples/0_Simple/matrixMul (attached is a small patch
to modify the Makefile to compile outside of the samples directory)

Run the following GDB commands:
user@deb3qwsp1:/usr/local/cuda-10.0/samples/0_Simple/matrixMul$ gdb ./matrixMul 
GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "powerpc64le-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./matrixMul...(no debugging symbols found)...done.
(gdb) break main
Breakpoint 1 at 0x8284
(gdb) run
Starting program: /usr/local/cuda-10.0/samples/0_Simple/matrixMul/matrixMul 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/powerpc64le-linux-gnu/libthread_db.so.1".

Breakpoint 1, 0x00018284 in main ()
(gdb) break *(__kernel_clock_gettime+144)
Breakpoint 2 at 0x77f805e4: file 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S, 
line 127.
(gdb) continue
Continuing.
[Matrix Multiply Using CUDA] - Starting...

Breakpoint 2, __kernel_clock_gettime () at 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S:127
127 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S: No 
such file or directory.
(gdb) bt
#0  __kernel_clock_gettime () at 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S:127
#1  0x77b8f530 in ?? () from /lib/powerpc64le-linux-gnu/libc.so.6
#2  0x76b81118 in ?? () from /usr/lib/powerpc64le-linux-gnu/libcuda.so.1
#3  0x76a69c70 in ?? () from /usr/lib/powerpc64le-linux-gnu/libcuda.so.1
#4  0x76bf0ba0 in cuInit () from 
/usr/lib/powerpc64le-linux-gnu/libcuda.so.1
#5  0x00010003ca50 in cudart::__loadDriverInternalUtil() ()
#6  0x77f05274 in __pthread_once_slow (
once_control=0x1000c00f0 
, 
init_routine=0x10003c950 ) at 
pthread_once.c:116
#7  0x00010008ea88 in cudart::cuosOnce(int*, void (*)()) ()
#8  0x0001000410a8 in cudart::globalState::initializeDriver() ()
#9  0x00010005ec90 in cudaGetDeviceCount ()
#10 0x00019930 in gpuGetMaxGflopsDeviceId() ()
#11 0x00019bf4 in findCudaDevice(int, char const**) ()
#12 0x0001836c in main ()
(gdb) step
128 in 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S
(gdb) bt
#0  __kernel_clock_gettime () at 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S:128
#1  0x in ?? ()
(gdb) 


Note: __kernel_clock_gettime+144 is currently the point in the function at 
which the syscall made, and is liable to change if updated. It corresponds to 
the "sc" instruction here: 
https://gitlab.com/TeeFirefly/linux-kernel/blob/7408b38cfdf9b0c6c3bda97402c75bd27ef69a85/arch/powerpc/kernel/vdso64/gettimeofday.S#L127
 and can be rediscovered if needed by disassembling the function.

Note that a backtrace can be collected before entering the syscall, but
not during. The inability to unwind also prevents GDB from being able to
"finish" (step out of) the function:

(gdb) finish
Run till exit from #0  __kernel_clock_gettime ()
at 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S:128
Warning:
Cannot insert breakpoint 0.
Cannot access memory at address 0x0

Command aborted.
(gdb)


The cause of the issue is a lack of Call Frame Information (CFI) in the syscall 
code path, and so a potential fix here could be to save the link register and 
add the corresponding CFI directive for the syscall code path (as is done for 
the alternative code path).[Less]

This is now upstream accepted in the powerpc tree as git commit
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=56d20861c027498b5a1112b4f9f05b56d906fdda
("powerpc/vdso: Correct call frame information")

** Affects: ubuntu-power-systems
 Importance: High
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux

[Kernel-packages] [Bug 1792195] Re: Signal 7 error when running GPFS tracing in cluster

2018-10-15 Thread Joseph Salisbury

I built another test kernel, without commit 2bf1071a8d5. This test
kernel has the three commit:

7acf50e4efa6 ("Revert "powerpc/powernv: Increase memory block size to 1GB on
radix"")
f08d08f3db55 ("powerpc/mm/radix: Only need the Nest MMU workaround for R -> RW
transition")
bd0dbb73e013 ("powerpc/mm/books3s: Add new pte bit to mark pte temporarily
invalid.")

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1792195

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

Title:
Signal 7 error when running GPFS tracing in cluster

Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress

Bug description:

== SRU Justification ==
IBM is requesting these commits in bionic and cosmic. These commits
also rely on commit 7acf50e4efa6, which was SRU'd in bug 1792102. The
first patch, commit 2bf1071a8d50, was backported by IBM themself.

Description of bug:
GPFS mmfsd daemon is mapping shared tracing buffer(allocated from kernel
driver using vmalloc) and then writing trace records from user space threads
in parallel. While the SIGBUS happened, the access virtual memory address
is in the mapped range, no overflow on access.

The root cause is that for PTEs created by a driver at mmap time (ie, that
aren't created dynamically at fault time), it's not legit for
ptep_set_access_flags()
to make them invalid even temporarily. A concurrent access while they are
invalid will be unable to service the page fault and will cause as SIGBUS.

== Fixes ==
2bf1071a8d50 ("powerpc/64s: Remove POWER9 DD1 support")
bd0dbb73e013 ("powerpc/mm/books3s: Add new pte bit to mark pte temporarily
invalid.")
f08d08f3db55 ("powerpc/mm/radix: Only need the Nest MMU workaround for R ->
RW transition")

== Regression Potential ==
Low. Limited to powerpc.

== Test Case ==
A test kernel was built with these patches and tested by IBM.
IBM states the test kernel resolved the bug.

-- Problem Description --
GPFS mmfsd daemon is mapping shared tracing buffer(allocated from kernel
driver using vmalloc) and then writing trace records from user space threads in
parallel. While the SIGBUS happened, the access virtual memory address is in
the mapped range, no overflow on access.

Worked with Benjamin Herrenschmidt on GPFS tracing kernel driver code
and he made a suggestion as workaround on the driver code to bypass
the problem, and it works

the workaround code change as below:

- rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, PAGE_SHARED);
+ rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE,
__pgprot(pgprot_val(PAGE_SHARED)|_PAGE_DIRTY);

As Benjamin mentioned, this is a Linux kernel bug and this is just a
workaround. He will give the details about the kernel bug and why this
workaround works

The root cause is that for PTEs created by a driver at mmap time (ie,
that aren't created dynamically at fault time), it's not legit for
ptep_set_access_flags() to make them invalid even temporarily. A
concurrent access while they are invalid will be unable to service the
page fault and will cause as SIGBUS.

Thankfully such PTEs shouldn't normally be the subject of a RO->RW
privilege escalation.

What happens is that the GPFS driver creates the PTEs using
remap_pfn_range(...,PAGE_SHARED).

PAGE_SHARED has _PAGE_ACCESSED (R) but not _PAGE_DIRTY (C) set.

Thus on the first write, we try set C and while doing so, hit the
above workaround, which causes the problem described earlier.

The proposed patch will ensure we only do the Nest MMU hack when
changing _PAGE_RW and not for normal R/C updates.

The workaround tested by the GPFS team consists of adding _PAGE_DIRTY
to the mapping created by remap_pfn_range() to avoid the RC update
fault completely.

This is fixed by these:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd0dbb73e01306a1060e56f81e5fe287be936477

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f08d08f3db55452d31ba4a37c702da6245876b96

Since DD1 support is still in (ie,
2bf1071a8d50928a4ae366bb3108833166c2b70c is not applied) the second
doesn't apply cleanly. Did you want that attached?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1792195/+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 1797963] [NEW] not able to unwind the stack from within __kernel_clock_gettime in the Linux vDSO