You are not logged in.

Pages: 1 … 36 37 38 39 40 … 54

Topic closed

#926 2016-09-05 22:44:12

damige
Member
Registered: 2016-09-02
Posts: 40

Re: Dell XPS 13 9350 Late 2015

computoruzer wrote:

Hey guys. Long time lurker, first time poster. I tried to build and install the AUR linux-nvme kernel, but it's having issues building the dependencies.

$ makepkg -sir
==> WARNING: The package group has already been built, installing existing packages...
==> Installing linux-nvme package group with pacman -U...
loading packages...
warning: linux-nvme-4.8rc5-1 is up to date -- reinstalling
warning: linux-nvme-headers-4.8rc5-1 is up to date -- reinstalling
warning: linux-nvme-docs-4.8rc5-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (3) linux-nvme-4.8rc5-1  linux-nvme-docs-4.8rc5-1  linux-nvme-headers-4.8rc5-1

Total Installed Size:  153.95 MiB
Net Upgrade Size:        0.00 MiB

:: Proceed with installation? [Y/n] 
(3/3) checking keys in keyring                                                                                         [########################################################################] 100%
(3/3) checking package integrity                                                                                       [########################################################################] 100%
(3/3) loading package files                                                                                            [########################################################################] 100%
(3/3) checking for file conflicts                                                                                      [########################################################################] 100%
(3/3) checking available disk space                                                                                    [########################################################################] 100%
:: Running pre-transaction hooks...
(1/1) Remove DKMS modules
==> dkms remove -m * -v * -k 4.8.0-rc5-nvme
Error! There are no instances of module: *
* located in the DKMS tree.
:: Processing package changes...
(1/3) reinstalling linux-nvme                                                                                          [########################################################################] 100%
>>> Updating module dependencies. Please wait ...
>>> Generating initial ramdisk, using mkinitcpio. Please wait...
==> Building image from preset: /etc/mkinitcpio.d/linux-nvme.preset: 'default'
  -> -k /boot/vmlinuz-linux-nvme -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-nvme.img
==> Starting build: 4.8.0-rc5-nvme
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [encrypt]
  -> Running build hook: [keyboard]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-nvme.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-nvme.preset: 'fallback'
  -> -k /boot/vmlinuz-linux-nvme -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-nvme-fallback.img -S autodetect
==> Starting build: 4.8.0-rc5-nvme
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: aic94xx
  -> Running build hook: [encrypt]
  -> Running build hook: [keyboard]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-nvme-fallback.img
==> Image generation successful
(2/3) reinstalling linux-nvme-headers                                                                                  [########################################################################] 100%
(3/3) reinstalling linux-nvme-docs                                                                                     [########################################################################] 100%
:: Running post-transaction hooks...
(1/1) Install DKMS modules
==> dkms install -m * -v * -k 4.8.0-rc5-nvme
Error! Could not find module source directory.
Directory: /usr/src/*-* does not exist.

Hi i also responded to this on the aur comment:

"I tried installing virtualbox-host-dkms and its immediately placed into the /usr/src before doing dkms install.
This dkms went through without errors. Could it be that your /usr/src is empty by accident? have you tried reinstalling from pacman the dkms you require. And afterwards do "mkinitcpio -p linux-nvme""

maybe also try "dkms status" and see if there are modules listed that are somehow not in /usr/src.
In my case if there are no DKMS installed it does not run the "dkms install" section

edit: Regarding the wifi issues, i have had troubles with BCM but they were Networkmanager related. but as you are on intel my problems might not apply.
Also: great to hear you have the razer core working. I'd be very interested in your findings when you have it all sorted. (might get one myself!)

edit2: So i installed and deinstalled some DKMS packages and ended up with the same problem... call me crazy but the "fix" was: removing the DKMS package (as there were no packages requiring it anymore and /usr/src was empty)
I confirmed this error on 4.8RC4 and 4.8RC5 with or without NVME patches.

Last edited by damige (2016-09-05 23:01:14)

XPS 15 7590 | i9-9980HK | 32GB RAM | 512G NVME | Intel AX200 | NVIDIA 1650 | OLED 4K

Offline

#927 2016-09-05 23:06:46

computoruzer
Member
Registered: 2016-09-05
Posts: 6

Re: Dell XPS 13 9350 Late 2015

@damige

Thanks! I originally removed the virtualbox-host-dkms and virtualbox-guest-dkms, because the guest dkms module would not build. After reinstalling just the host dkms the PKGBUILD seems to complete.

Have you been able to get the guest dkms module to build?

$ sudo pacman -S virtualbox-guest-dkms

resolving dependencies...
looking for conflicting packages...

Packages (1) virtualbox-guest-dkms-5.1.4-1

Total Installed Size:  7.48 MiB

:: Proceed with installation? [Y/n] Y
(1/1) checking keys in keyring                             [################################] 100%
(1/1) checking package integrity                           [################################] 100%
(1/1) loading package files                                [################################] 100%
(1/1) checking for file conflicts                          [################################] 100%
(1/1) checking available disk space                        [################################] 100%
:: Processing package changes...
(1/1) installing virtualbox-guest-dkms                     [################################] 100%
Optional dependencies for virtualbox-guest-dkms
    linux-headers: build modules against Arch kernel [installed]
    linux-lts-headers: build modules against LTS kernel
    linux-zen-headers: build modules against ZEN kernel
:: Running post-transaction hooks...
(1/1) Install DKMS modules
==> dkms install -m vboxguest -v 5.1.4_OSE -k 4.7.2-1-ARCH
==> dkms install -m vboxguest -v 5.1.4_OSE -k 4.8.0-rc5-nvme
Error! Bad return status for module build on kernel: 4.8.0-rc5-nvme (x86_64)
Consult /var/lib/dkms/vboxguest/5.1.4_OSE/build/make.log for more information.

/var/lib/dkms/vboxguest/5.1.4_OSE/build/make.log

DKMS make.log for vboxguest-5.1.4_OSE for kernel 4.8.0-rc5-nvme (x86_64)
Mon Sep  5 16:01:02 PDT 2016
make: Entering directory '/usr/lib/modules/4.8.0-rc5-nvme/build'
  LD      /var/lib/dkms/vboxguest/5.1.4_OSE/build/built-in.o
  LD      /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/built-in.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/VBoxGuest-linux.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/VBoxGuest.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/GenericRequest.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/HGCMInternal.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/Init.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/PhysHeap.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/SysHlp.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/VMMDev.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/r0drv/alloc-r0drv.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/r0drv/initterm-r0drv.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/r0drv/memobj-r0drv.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/r0drv/mpnotification-r0drv.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/r0drv/powernotification-r0drv.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/r0drv/linux/alloc-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/r0drv/linux/assert-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/r0drv/linux/initterm-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/r0drv/linux/memobj-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/r0drv/linux/memuserkernel-r0drv-linux.o
/var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/r0drv/linux/memuserkernel-r0drv-linux.o: warning: objtool: .fixup: unexpected end of section
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/r0drv/linux/mp-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/r0drv/linux/mpnotification-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/r0drv/linux/process-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/r0drv/linux/semevent-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/r0drv/linux/semeventmulti-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/r0drv/linux/semfastmutex-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/r0drv/linux/semmutex-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/r0drv/linux/spinlock-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/r0drv/linux/thread-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/r0drv/linux/thread2-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/r0drv/linux/time-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/r0drv/linux/timer-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/r0drv/linux/RTLogWriteDebugger-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/r0drv/generic/semspinmutex-r0drv-generic.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/common/alloc/alloc.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/common/err/RTErrConvertFromErrno.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/common/err/RTErrConvertToErrno.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/common/log/log.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/common/log/logellipsis.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/common/log/logrel.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/common/log/logrelellipsis.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/common/log/logcom.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/common/log/logformat.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/common/misc/RTAssertMsg1Weak.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/common/misc/RTAssertMsg2.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/common/misc/RTAssertMsg2Add.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/common/misc/RTAssertMsg2AddWeak.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/common/misc/RTAssertMsg2AddWeakV.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/common/misc/RTAssertMsg2Weak.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/common/misc/RTAssertMsg2WeakV.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/common/misc/assert.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/common/misc/thread.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/common/string/RTStrCopy.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/common/string/RTStrCopyEx.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/common/string/RTStrCopyP.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/common/string/strformat.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/common/string/strformatrt.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/common/string/strformattype.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/common/string/strprintf.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/common/string/strtonum.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/common/table/avlpv.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/common/time/time.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/generic/RTAssertShouldPanic-generic.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/generic/RTLogWriteStdErr-stub-generic.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/generic/RTLogWriteStdOut-stub-generic.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/generic/RTMpGetCoreCount-generic.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/generic/RTSemEventWait-2-ex-generic.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/generic/RTSemEventWaitNoResume-2-ex-generic.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/generic/RTSemEventMultiWait-2-ex-generic.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/generic/RTSemEventMultiWaitNoResume-2-ex-generic.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/generic/errvars-generic.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/generic/mppresent-generic.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/VBox/log-vbox.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/VBox/logbackdoor.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/common/alloc/heapsimple.o
  LD [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxguest/vboxguest.o
  LD      /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxsf/built-in.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxsf/vfsmod.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxsf/dirops.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxsf/lnkops.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxsf/regops.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxsf/utils.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxsf/GenericRequest.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxsf/SysHlp.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxsf/PhysHeap.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxsf/Init.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxsf/VMMDev.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxsf/HGCM.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxsf/VBoxGuestR0LibSharedFolders.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxsf/VbglR0CanUsePhysPageList.o
  LD [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxsf/vboxsf.o
  LD      /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/built-in.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/HGSMIBase.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/HGSMICommon.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/HGSMIMemAlloc.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/heapoffset.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/Modesetting.o
  CC [M]  /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.o
/var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.c:68:8: error: type defaults to 'int' in declaration of 'DEFINE_PCI_DEVICE_TABLE' [-Werror=implicit-int]
 static DEFINE_PCI_DEVICE_TABLE(pciidlist) =
        ^~~~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.c:68:1: warning: parameter names (without types) in function declaration
 static DEFINE_PCI_DEVICE_TABLE(pciidlist) =
 ^~~~~~
/var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.c:68:1: error: function 'DEFINE_PCI_DEVICE_TABLE' is initialized like a variable
/var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.c:70:5: warning: braces around scalar initializer
     {0x80ee, 0xbeef, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0},
     ^
/var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.c:70:5: note: (near initialization for 'DEFINE_PCI_DEVICE_TABLE')
/var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.c:70:6: error: invalid initializer
     {0x80ee, 0xbeef, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0},
      ^~~~~~
/var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.c:70:6: note: (near initialization for 'DEFINE_PCI_DEVICE_TABLE')
/var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.c:70:14: warning: excess elements in scalar initializer
     {0x80ee, 0xbeef, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0},
              ^~~~~~
/var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.c:70:14: note: (near initialization for 'DEFINE_PCI_DEVICE_TABLE')
In file included from ./include/linux/pci.h:20:0,
                 from /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/include/the-linux-kernel.h:119,
                 from /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.h:53,
                 from /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.c:48:
./include/linux/mod_devicetable.h:16:20: warning: excess elements in scalar initializer
 #define PCI_ANY_ID (~0)
                    ^
/var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.c:70:22: note: in expansion of macro 'PCI_ANY_ID'
     {0x80ee, 0xbeef, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0},
                      ^~~~~~~~~~
./include/linux/mod_devicetable.h:16:20: note: (near initialization for 'DEFINE_PCI_DEVICE_TABLE')
 #define PCI_ANY_ID (~0)
                    ^
/var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.c:70:22: note: in expansion of macro 'PCI_ANY_ID'
     {0x80ee, 0xbeef, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0},
                      ^~~~~~~~~~
./include/linux/mod_devicetable.h:16:20: warning: excess elements in scalar initializer
 #define PCI_ANY_ID (~0)
                    ^
/var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.c:70:34: note: in expansion of macro 'PCI_ANY_ID'
     {0x80ee, 0xbeef, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0},
                                  ^~~~~~~~~~
./include/linux/mod_devicetable.h:16:20: note: (near initialization for 'DEFINE_PCI_DEVICE_TABLE')
 #define PCI_ANY_ID (~0)
                    ^
/var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.c:70:34: note: in expansion of macro 'PCI_ANY_ID'
     {0x80ee, 0xbeef, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0},
                                  ^~~~~~~~~~
/var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.c:70:46: warning: excess elements in scalar initializer
     {0x80ee, 0xbeef, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0},
                                              ^
/var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.c:70:46: note: (near initialization for 'DEFINE_PCI_DEVICE_TABLE')
/var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.c:70:49: warning: excess elements in scalar initializer
     {0x80ee, 0xbeef, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0},
                                                 ^
/var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.c:70:49: note: (near initialization for 'DEFINE_PCI_DEVICE_TABLE')
/var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.c:70:52: warning: excess elements in scalar initializer
     {0x80ee, 0xbeef, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0},
                                                    ^
/var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.c:70:52: note: (near initialization for 'DEFINE_PCI_DEVICE_TABLE')
/var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.c:71:5: warning: braces around scalar initializer
     {0, 0, 0},
     ^
/var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.c:71:5: note: (near initialization for 'DEFINE_PCI_DEVICE_TABLE')
/var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.c:71:6: error: invalid initializer
     {0, 0, 0},
      ^
/var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.c:71:6: note: (near initialization for 'DEFINE_PCI_DEVICE_TABLE')
/var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.c:71:9: warning: excess elements in scalar initializer
     {0, 0, 0},
         ^
/var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.c:71:9: note: (near initialization for 'DEFINE_PCI_DEVICE_TABLE')
/var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.c:71:12: warning: excess elements in scalar initializer
     {0, 0, 0},
            ^
/var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.c:71:12: note: (near initialization for 'DEFINE_PCI_DEVICE_TABLE')
/var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.c:71:5: warning: excess elements in scalar initializer
     {0, 0, 0},
     ^
/var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.c:71:5: note: (near initialization for 'DEFINE_PCI_DEVICE_TABLE')
In file included from /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/include/the-linux-kernel.h:88:0,
                 from /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.h:53,
                 from /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.c:48:
/var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.c:74:26: error: 'pciidlist' undeclared here (not in a function)
 MODULE_DEVICE_TABLE(pci, pciidlist);
                          ^
./include/linux/module.h:213:21: note: in definition of macro 'MODULE_DEVICE_TABLE'
 extern const typeof(name) __mod_##type##__##name##_device_table  \
                     ^~~~
/var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.c:270:20: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
     .master_drop = vbox_master_drop,
                    ^~~~~~~~~~~~~~~~
/var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.c:270:20: note: (near initialization for 'driver.master_drop')
In file included from /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/include/the-linux-kernel.h:88:0,
                 from /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.h:53,
                 from /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.c:48:
./include/linux/module.h:213:27: error: '__mod_pci__pciidlist_device_table' aliased to undefined symbol 'pciidlist'
 extern const typeof(name) __mod_##type##__##name##_device_table  \
                           ^
/var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.c:74:1: note: in expansion of macro 'MODULE_DEVICE_TABLE'
 MODULE_DEVICE_TABLE(pci, pciidlist);
 ^~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:290: /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo/vbox_drv.o] Error 1
make[1]: *** [scripts/Makefile.build:440: /var/lib/dkms/vboxguest/5.1.4_OSE/build/vboxvideo] Error 2
make: *** [Makefile:1471: _module_/var/lib/dkms/vboxguest/5.1.4_OSE/build] Error 2
make: Leaving directory '/usr/lib/modules/4.8.0-rc5-nvme/build'

Offline

#928 2016-09-05 23:11:10

damige
Member
Registered: 2016-09-02
Posts: 40

Re: Dell XPS 13 9350 Late 2015

Unfortionatly not, though i dont think its due to the nvme part because the vanilla mainline fails also! sry sad

(1/1) Install DKMS modules
==> dkms install -m vboxguest -v 5.1.4_OSE -k 4.7.2-1-ARCH
==> dkms install -m vboxguest -v 5.1.4_OSE -k 4.8.0-rc4-nvme
Error! Bad return status for module build on kernel: 4.8.0-rc4-nvme (x86_64)
Consult /var/lib/dkms/vboxguest/5.1.4_OSE/build/make.log for more information.
==> dkms install -m vboxguest -v 5.1.4_OSE -k 4.8.0-rc5-mainline
Error! Bad return status for module build on kernel: 4.8.0-rc5-mainline (x86_64)
Consult /var/lib/dkms/vboxguest/5.1.4_OSE/build/make.log for more information.
error: missing 'lib32-ldb' dependency for 'lib32-smbclient'

edit: I use KVM for virtualization with which i am very pleased. Might be worth checking out if you have not already. There is a graphical fontend called virt-manager if im not mistaken.
Also isnt the guest-dkms only for hosts running inside a virtual machine? please correct me if wrong

Last edited by damige (2016-09-05 23:24:54)

XPS 15 7590 | i9-9980HK | 32GB RAM | 512G NVME | Intel AX200 | NVIDIA 1650 | OLED 4K

Offline

#929 2016-09-06 05:47:04

bakteria
Member
Registered: 2015-12-15
Posts: 35

Re: Dell XPS 13 9350 Late 2015

Mine crashes on wake after suspend on 4.7.2-1. Same issue on mainline as well. Very strange.

Offline

#930 2016-09-06 06:02:26

frank604
Member
From: BC, Canada
Registered: 2011-04-20
Posts: 1,212

Re: Dell XPS 13 9350 Late 2015

bakteria wrote:

Mine crashes on wake after suspend on 4.7.2-1. Same issue on mainline as well. Very strange.

Logs? Are you mentioning the stock arch kernel?  Does it happen when you manually suspend and resume?  Does this happen on a fresh boot?  All the time?  Downgrading kernel version resolves issue?  This is on archlinux?

Offline

#931 2016-09-06 07:06:25

bakteria
Member
Registered: 2015-12-15
Posts: 35

Re: Dell XPS 13 9350 Late 2015

frank604 wrote:
bakteria wrote:

Mine crashes on wake after suspend on 4.7.2-1. Same issue on mainline as well. Very strange.

Logs? Are you mentioning the stock arch kernel?  Does it happen when you manually suspend and resume?  Does this happen on a fresh boot?  All the time?  Downgrading kernel version resolves issue?  This is on archlinux?

Had this issue yesterday at work. Didnt save logs. Tried to recreate it today but now it seems to work as intended.
It happened on manual and timed suspend. Fresh boot and every time I tried to wake from suspend. Didn't try to downgrade the kernel. It is on arch.

Offline

#932 2016-09-06 15:45:21

davidgf
Member
Registered: 2015-11-28
Posts: 58

Re: Dell XPS 13 9350 Late 2015

With 4.8 I get this as soon as I go into suspend:

[   70.953033] ACPI Error: Cannot release Mutex [PATM], not acquired (20160422/exmutex-393)
[   70.953037] ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.ECDV._Q66] (Node ffff9002b60e3fa0), AE_AML_MUTEX_NOT_ACQUIRED (20160422/psparse-542)
[   83.006060] ACPI Error: Thread 2967568384 cannot release Mutex [PATM] acquired by thread 3029515776 (20160422/exmutex-416)
[   83.006070] ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.ECDV._Q66] (Node ffff9002b60e3fa0), AE_AML_NOT_OWNER (20160422/psparse-542)
[   91.862512] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30)

And it doesn't go into suspend. Therefore I cannot properly shut it down, cause suspension entering process is still working. This is with 4.8 vanilla + 1 fedora patch (cpu mask) + 3 nvme low power patches.

If anybody find that in their dmesg, do say please!

Offline

#933 2016-09-06 18:16:37

frank604
Member
From: BC, Canada
Registered: 2011-04-20
Posts: 1,212

Re: Dell XPS 13 9350 Late 2015

Those look familiar when I used mainline.  I do not have those errors on intel-drm.  I haven't had suspend issues in a long time.

Offline

#934 2016-09-08 03:59:42

Jiaan
Member
From: China
Registered: 2016-08-07
Posts: 16
Website

Re: Dell XPS 13 9350 Late 2015

Having tried the patched kernel for days, I couldn't perceive any improvement. sad Though I don't have suspend issues, the patched kernel doesn't provide battery saving or cooling effect either. What is odd is that the idle discharge rate(~6.54W on plasma5) is even slightly higher than that of vanilla kernel(~6.29W).  And the boot time is slightly longer (0.4s more kernel time). I'm on a FHD i7-6560U model, maybe the effect is more apparent on non-Iris model? But it doesn't make sense since the patch is towards nvme devices, which should be same. I am bewildered now.

Offline

#935 2016-09-08 06:15:17

maurice
Member
Registered: 2016-09-08
Posts: 1

Re: Dell XPS 13 9350 Late 2015

Jiaan wrote:

Having tried the patched kernel for days, I couldn't perceive any improvement. sad Though I don't have suspend issues, the patched kernel doesn't provide battery saving or cooling effect either. What is odd is that the idle discharge rate(~6.54W on plasma5) is even slightly higher than that of vanilla kernel(~6.29W).  And the boot time is slightly longer (0.4s more kernel time). I'm on a FHD i7-6560U model, maybe the effect is more apparent on non-Iris model? But it doesn't make sense since the patch is towards nvme devices, which should be same. I am bewildered now.


I can confirm that with a QHD+ i7 6500U ( Gnome ).

Offline

#936 2016-09-08 07:24:39

frank604
Member
From: BC, Canada
Registered: 2011-04-20
Posts: 1,212

Re: Dell XPS 13 9350 Late 2015

I tried to see if there was other feedback from the nvme power saving patch by Andy.  Unfortunately it seems this forum has the only test results.  Have you guys tested battery life without X/Wayland?  Wondering if your autostart programs and/or DEs have some influence preventing nvme from going to lower power state?  Just a thought...  Or if there are any run away processes?  Have you looked at iotop and htop during your tests?

Anyways, reading the mailing list I came across the next batch of patches.  https://lkml.org/lkml/2016/8/28/223
However, I don't see these patches in the diff for 4.8 RC5.  So when do they land?  Looks like some DRM/Intel patches flew in.  I wonder how often Intel DRM nightly gets synced with Mainline?

Last edited by frank604 (2016-09-08 07:25:12)

Offline

#937 2016-09-08 10:43:01

damige
Member
Registered: 2016-09-02
Posts: 40

Re: Dell XPS 13 9350 Late 2015

Jiaan wrote:

Having tried the patched kernel for days, I couldn't perceive any improvement. sad Though I don't have suspend issues, the patched kernel doesn't provide battery saving or cooling effect either. What is odd is that the idle discharge rate(~6.54W on plasma5) is even slightly higher than that of vanilla kernel(~6.29W).  And the boot time is slightly longer (0.4s more kernel time). I'm on a FHD i7-6560U model, maybe the effect is more apparent on non-Iris model? But it doesn't make sense since the patch is towards nvme devices, which should be same. I am bewildered now.

The added boot time is most likely due to the added kernel logging, nothing else should be effected. I could look into disabling this, but it comes by default in mainline on which the linux-nvme is based.

Its strange that you do not see an improvement i have the same (FHD, 6560U). maybe something is causing constant io to disk?
On my laptop with 50% brightness i hover around ~5.6watt idle (wifi on, bt enabled but not paired, a few terminals open+powertop and this chrometab, keyboard backlight off)
with 1% brighteness im around ~4.4w with dips to 3.8w and peaks 6w. (same things running as above)

Just for reference: Are you using TLP? i do use it. Also, By default it seems arch runs on the performance governor, i have set this to powersave as scaling seems to work pretty good and i like the better battery time.

edit: current measurements also plasma5

edit2: I have updated the package to enable normal kernel logging. I have made it on purpose that AUR does not force an update to everyone just to disable logging. A reinstall or a new install will enable this feature by default.
Look for file "change-default-console-loglevel.patch" in PKGBUILD if you want to be certain.

for binary: https://github.com/damige/linux-nvme/tr … pkg/4.8rc5
for compile: https://github.com/damige/linux-nvme/tr … src/4.8rc5 or AUR

This should get your 0.4 seconds back wink please let me know if this also has an positive effect on your idle +0.25w usage compared to stock. If this works i will make this a new release on AUR.

Last edited by damige (2016-09-08 11:42:16)

XPS 15 7590 | i9-9980HK | 32GB RAM | 512G NVME | Intel AX200 | NVIDIA 1650 | OLED 4K

Offline

#938 2016-09-08 18:56:31

vtrac
Member
Registered: 2016-01-28
Posts: 42

Re: Dell XPS 13 9350 Late 2015

davidgf wrote:

With 4.8 I get this as soon as I go into suspend:

[   70.953033] ACPI Error: Cannot release Mutex [PATM], not acquired (20160422/exmutex-393)
[   70.953037] ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.ECDV._Q66] (Node ffff9002b60e3fa0), AE_AML_MUTEX_NOT_ACQUIRED (20160422/psparse-542)
[   83.006060] ACPI Error: Thread 2967568384 cannot release Mutex [PATM] acquired by thread 3029515776 (20160422/exmutex-416)
[   83.006070] ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.ECDV._Q66] (Node ffff9002b60e3fa0), AE_AML_NOT_OWNER (20160422/psparse-542)
[   91.862512] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30)

And it doesn't go into suspend. Therefore I cannot properly shut it down, cause suspension entering process is still working. This is with 4.8 vanilla + 1 fedora patch (cpu mask) + 3 nvme low power patches.

If anybody find that in their dmesg, do say please!

I'm having suspend troubles, and this is happening to me.  I filed a bug for it: 

https://bugzilla.kernel.org/show_bug.cgi?id=156361

Feel free to pile on your dmesg.

Offline

#939 2016-09-08 23:33:13

kang
Member
Registered: 2010-08-07
Posts: 83

Re: Dell XPS 13 9350 Late 2015

It seems that nvme patch regained a couple of watts here after a few days of testing.
QHD + i7 iris though, so im at 7w lowest running plasma5  (3-4w would be so amazing ;P), used to be more around 8-9w minimum which is nice.
Could also be other changes though since ive also upgraded from 4.7, and my kernels only enable what i use (ie they're not compiling all modules). Still it seems to be the nvme patch.

Offline

#940 2016-09-09 09:54:20

frank604
Member
From: BC, Canada
Registered: 2011-04-20
Posts: 1,212

Re: Dell XPS 13 9350 Late 2015

Compiling modules you only use just decreases compiling time and build size. The other modules were never loaded as is your stripped kernel so there is no difference in performance.  Once again, check power drain without x. Then you know how much plasma draws. Then you can investigate and see if that is the lowest you can get the drain.

For those with suspend issues, here is my dmesg of suspend working fine on my end in case it helps http://ix.io/1loD
Looks like I do have 

[Thu Sep  8 00:28:16 2016] ACPI Error: Cannot release Mutex [PATM], not acquired (20160422/exmutex-393)
[Thu Sep  8 00:28:16 2016] ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.ECDV._Q66] (Node ffff8802760def00), AE_AML_MUTEX_NOT_ACQUIRED (20160422/psparse-542)

but it seems harmless.

Last edited by frank604 (2016-09-09 16:22:32)

Offline

#941 2016-09-10 05:15:59

vtrac
Member
Registered: 2016-01-28
Posts: 42

Re: Dell XPS 13 9350 Late 2015

For those that are running 4.8.x and have no suspend issues, would you mind posting your mkinitcpio.conf's MODULES & HOOKS, anything in /etc/modprobe.d/, /etc/modules-load.d/, and your kernel boot options?

Thanks.

Offline

#942 2016-09-10 05:20:52

frank604
Member
From: BC, Canada
Registered: 2011-04-20
Posts: 1,212

Re: Dell XPS 13 9350 Late 2015

/etc/modprobe.d
❯ cat blacklist.conf
install btusb /bin/false
install bluetooth /bin/false

/etc/modprobe.d
❯ cat iwldvm.conf
options iwldvm force_cam=0

/etc/modprobe.d
❯ cat iwlwifi.conf
options iwlwifi power_save=1 d0i3_disable=0 uapsd_disable=0

/etc/modprobe.d
❯ cat k70corsair.conf
options usbhid quirks=0x1B1C:0x1B13:0x20000000

/etc/modprobe.d
❯ cat usb-autosuspend.conf
options usbcore autosuspend=5

/etc/modules-load.d is empty

/etc/mkinitcpio.conf
http://ix.io/1lz8

bootloader = systemd-boot

/boot/loader/entries
❯ cat intel.conf
title   Arch Linux - Intel DRM Next
linux   /vmlinuz-linux-drm-intel-nightly
initrd  /intel-ucode.img
initrd  /initramfs-linux-drm-intel-nightly.img
options root=/dev/nvme0n1p2 rw  pcie_aspm=force i915.enable_rc6=7 net.ifnames=0
#options root=/dev/nvme0n1p2 rw  pcie_aspm=force  i915.enable_psr=1 i915.enable_fbc=1 i915.enable_rc6=7 net.ifnames=0
#options root=/dev/nvme0n1p2 rw  pcie_aspm=force  i915.enable_psr=1 i915.enable_rc6=7 net.ifnames=0

Offline

#943 2016-09-10 13:55:08

robsmith11
Member
Registered: 2016-09-10
Posts: 23

Re: Dell XPS 13 9350 Late 2015

vtrac wrote:

For those that are running 4.8.x and have no suspend issues, would you mind posting your mkinitcpio.conf's MODULES & HOOKS, anything in /etc/modprobe.d/, /etc/modules-load.d/, and your kernel boot options?

Thanks.

I just upgraded to the nvme 4.8 patchset in AUR from the 4.7.2 mainline on my 9350 FHD with 256GB SSD.  It made a big difference at idle (just running dwm, st, and wifi): was 3.50W, now 2.75W!  (EDIT: got it down to 2.49W if i turn down the backlight)

No crashes or problems with suspend so far.

mkinitcpio.conf:
MODULES="nvme"
HOOKS="base udev autodetect modconf block filesystems keyboard fsck"

I have no entries in /etc/modprobe.d or /etc/modules-load.d.

boot options:
options root=PARTUUID=9ec5f593-475f-4bc4-b025-613baf1bd485 rw

A pretty vanilla setup.  I am using xf86-video-modesetting rather than xf86-video-intel though.

Last edited by robsmith11 (2016-09-10 22:02:54)

Offline

#944 2016-09-10 21:02:19

computoruzer
Member
Registered: 2016-09-05
Posts: 6

Re: Dell XPS 13 9350 Late 2015

computoruzer wrote:

Also, since performing a full system upgrade from 4.6.x, my Intel 8260 has been misbehaving. It will work initially on boot, but after a couple of minutes it throws:

[  152.396975] iwlwifi 0000:3a:00.0: Error sending STATISTICS_CMD: time out after 2000ms.
[  152.903552] iwlwifi 0000:3a:00.0: Queue 9 stuck for 2500 ms.

[  158.397282] iwlwifi 0000:3a:00.0: Failed to load firmware chunk!
[  158.397299] iwlwifi 0000:3a:00.0: Could not load the [6] uCode section
[  158.397343] iwlwifi 0000:3a:00.0: Failed to start INIT ucode: -110
[  158.397349] iwlwifi 0000:3a:00.0: Failed to run INIT ucode: -110
[  158.401714] iwlwifi 0000:3a:00.0: Failed to disable queue 16 (ret=-5)

The NIC will disconnect and refuse to scan or go up. Trying to set the device up using ip yields, "RTNETLINK answers: Connection timed out.". Unloading and reloading iwlmvm, iwlwifi will force the device back on, but then the laptop will lockup shortly afterwards. I chose to install the AUR linux-firmware-git, and it seems to be working so far. Has anyone else encountered the same behavior?

Issue began with:
[****************] [ALPM] upgraded linux-firmware (20160516.80d463b-1 -> 20160730.6bc2c60-1)

Currently stable after:
[****************] [PACMAN] Running '/usr/bin/pacman -U /tmp/linux-firmware-git/linux-firmware-git-20160831.c883a6b-1-any.pkg.tar.xz'
[****************] [ALPM] removed linux-firmware (20160730.6bc2c60-1)
[****************] [ALPM] installed linux-firmware-git (20160831.c883a6b-1)

Also, also, I was able to get the new Thunderbolt 3 Razer Core working on my 9350. It works really well. Still working on writing hot-plugging services and PCI passthrough with qemu. If anyone's interested I can post some links.

Looks like I was wrong. Installing linux-firmware from AUR didn't solve anything. I'm still forced to unload and reload iwlmvm and iwlwifi at times. Has no one else ran into this issue?

Offline

#945 2016-09-10 22:32:35

kang
Member
Registered: 2010-08-07
Posts: 83

Re: Dell XPS 13 9350 Late 2015

frank604 wrote:

Compiling modules you only use just decreases compiling time and build size. The other modules were never loaded as is your stripped kernel so there is no difference in performance.  Once again, check power drain without x. Then you know how much plasma draws. Then you can investigate and see if that is the lowest you can get the drain.

For those with suspend issues, here is my dmesg of suspend working fine on my end in case it helps http://ix.io/1loD
Looks like I do have 

[Thu Sep  8 00:28:16 2016] ACPI Error: Cannot release Mutex [PATM], not acquired (20160422/exmutex-393)
[Thu Sep  8 00:28:16 2016] ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.ECDV._Q66] (Node ffff8802760def00), AE_AML_MUTEX_NOT_ACQUIRED (20160422/psparse-542)

but it seems harmless.

blablabla
the point is im not loading some of the modules that would otherwise be loaded (ye ye u can blacklist them smart guy) and have different things turned on and off that you cannot set at the module level (yeh u cant do that..).

Last edited by kang (2016-09-10 22:33:19)

Offline

#946 2016-09-11 06:20:28

Jiaan
Member
From: China
Registered: 2016-08-07
Posts: 16
Website

Re: Dell XPS 13 9350 Late 2015

@frank604  @damige 
Ok so I sort out the possibility that other programs are making constant disk IO by a minimal boot (with only just few systemd stuff in pstree), still get around 6W discharge rate at 20% brightness.

I tried your precompiled kernel. It seems that kernel boot time decreases by 0.1s. Not really useful though. But anyway I mainly care about battery life, the increased boot time is too trivial.
Yes, I am using TLP (with default configuration). But with 50% brightness and 1 chrome tab and powertop open while doing nothing, I get 7W discharge rate. In powertop the power comsumption estimation for "Display Backlight" is 4.7W already! But I don't think that's a faithful evaluation.

Offline

#947 2016-09-11 18:42:46

zetxx
Member
From: Sofia :: Bulgaria
Registered: 2013-12-13
Posts: 97

Re: Dell XPS 13 9350 Late 2015

humm, im seeing this numbers for the firs time:

The battery reports a discharge rate of 4.77 W
The estimated remaining time is 11 hours, 23 minutes

xps13@late2015x16gbx512g

Offline

#948 2016-09-11 19:27:39

frank604
Member
From: BC, Canada
Registered: 2011-04-20
Posts: 1,212

Re: Dell XPS 13 9350 Late 2015

@jiaan I agree the 4.7W for backlight seems a bit off. 

Here is my powerstat(AUR) output.

❯ sudo powerstat -d 0
Running for 480.0 seconds (48 samples at 10.0 second intervals).
Power measurements will start in 0 seconds time.

  Time    User  Nice   Sys  Idle    IO  Run Ctxt/s  IRQ/s Fork Exec Exit  Watts
12:16:22   4.0   0.0   3.0  92.7   0.4    1   4208   1242   20    0   20   5.78
12:16:32   3.9   0.0   3.1  92.6   0.4    1   4334   1589   20    0   20   4.72
12:16:42   7.7   0.0   3.8  87.9   0.6    3   7180   2867   38    0  120   9.79
12:16:52   5.0   0.0   3.3  91.2   0.5    2   4530   1993   30    7   30   5.62
12:17:02   4.2   0.0   2.9  89.5   3.4    3   4027   1327   20    0   19   5.99
12:17:12   3.7   0.0   2.9  93.0   0.4    1   3986   1209   20    0   21   4.69
12:17:22   3.8   0.0   2.9  93.1   0.2    1   4041   1246   20    0   21   4.63
12:17:32   3.8   0.0   3.0  92.9   0.4    1   4144   1285   20    0   20   4.57
12:17:42   4.4   0.0   2.9  92.1   0.7    1   3979   1243   25    0   27   4.50
12:17:52   3.7   0.0   2.9  93.0   0.4    1   4219   1285   20    0   20   4.67
12:18:02   4.1   0.0   3.9  89.8   2.2    1   5022   1608   20    0   20   4.81
12:18:12   3.9   0.0   3.8  90.2   2.2    2   5227   1770   20    0   20   5.70
12:18:22   5.8   0.0   4.0  89.9   0.3    2   5628   3498   21    0   20   6.66
12:18:32   5.5   0.0   3.1  91.1   0.4    1   5544  10005   18    0   18   5.18
12:18:42   4.1   0.0   3.3  92.4   0.3    4   5469   9938   24    0   24   5.25
12:18:52  11.5   0.0   3.4  84.7   0.3    1   5427   9770   20    0   20   9.17
12:19:02   6.9   0.0   1.2  91.7   0.3    1   2661   2703   23    0   20   5.22
12:19:12   9.3   0.0   1.9  84.2   4.5    2   3309   6655   27    0   20   5.02
12:19:22   5.5   0.0   1.4  92.6   0.4    1   2832   9112   19    0   20   5.78
12:19:32   4.7   0.0   1.1  94.1   0.2    1   2402   4543   20    0   20   4.03
12:19:42   4.5   0.0   0.9  94.5   0.1    1   2430   5165   23    0   29   4.86
12:19:52   5.7   0.0   1.3  92.9   0.1    2   2623   3905   20    0   20   5.77
12:20:02   4.4   0.0   1.1  94.3   0.2    1   2246   2486   19    0   19   4.04
12:20:12   5.1   0.0   1.4  93.2   0.3    1   2481   4628   20    0   20   3.95
12:20:22   7.6   0.0   1.2  90.9   0.2    1   3161   6391   20    0   20   6.71
12:20:32  10.6   0.0   1.9  87.4   0.1    3   3978   8883   20    0   20   5.60
12:20:42  10.6   0.0   1.9  87.4   0.1    1   4925   6298   24    0   24   6.16
12:20:52   5.4   0.0   1.3  93.0   0.3    3   2440   3280   19    0   18   4.45
12:21:02   4.8   0.0   1.4  93.3   0.4    1   2531    725   21    0   20   4.28
12:21:12   4.2   0.0   1.5  94.0   0.4    2   2443   1167   23    0   22   4.15
12:21:22   3.5   0.0   1.1  94.9   0.4    1   2445   3990   20    0   23   5.04
12:21:32   3.9   0.0   1.1  94.9   0.2    2   2424   3975   19    0   19   4.20
12:21:42   4.1   0.0   1.1  94.7   0.2    1   2130    720   25    0   24   4.27
12:21:52   4.1   0.0   1.1  94.2   0.6    1   2272    852   20    0   20   4.19
12:22:02   6.3   0.0   1.9  91.1   0.6    1   2704    691   19    0   19   4.17
12:22:12   3.2   0.0   1.3  95.2   0.3    1   1981    512   20    0   20   4.88
12:22:22   3.6   0.0   1.0  95.1   0.3    1   2116    575   20    0   21   4.29
12:22:32   4.0   0.0   1.2  94.6   0.3    1   2278    946   20    0   20   4.07
12:22:42   4.2   0.0   1.0  94.2   0.6    1   2141   1833   23    0   23   6.31
12:22:52   4.7   0.0   0.9  94.1   0.3    1   1986    505   21    0   21   4.02
12:23:02   3.7   0.0   1.1  94.9   0.3    2   2325   2227   23    1   20   4.92
12:23:12   4.7   0.0   2.2  92.7   0.4    1   2692   3592  140   66  135   4.56
12:23:22   4.0   0.0   1.3  94.4   0.3    1   2346   2896   71   30   72   4.06

12:23:32   4.0   0.0   1.3  94.3   0.4    1   2135   1257   35   10   37   4.40
12:23:42   5.8   0.0   1.5  92.5   0.2    1   1995    553   24    0   24   6.70
12:23:52   3.4   0.0   1.2  95.2   0.3    1   2226   2823   20    0   20   4.25
12:24:02   3.6   0.0   1.1  95.2   0.1    1   2442   4419   20    0   21   4.09
12:24:12   4.9   0.0   1.3  93.6   0.2    1   2658   5437   23    2   23   4.14
-------- ----- ----- ----- ----- ----- ---- ------ ------ ---- ---- ---- ------
 Average   5.1   0.0   2.0  92.4   0.5  1.4 3306.8 3242.0 25.4  2.4 27.0   5.09
  StdDev   1.9   0.0   1.0   2.6   0.8  0.7 1267.6 2716.6 18.5 10.3 22.5   1.20
-------- ----- ----- ----- ----- ----- ---- ------ ------ ---- ---- ---- ------
 Minimum   3.2   0.0   0.9  84.2   0.1  1.0 1981.0  505.3 18.0  0.0 18.0   3.95
 Maximum  11.5   0.0   4.0  95.2   4.5  4.0 7180.3 10004.6 140.0 66.0 135.0   9.79
-------- ----- ----- ----- ----- ----- ---- ------ ------ ---- ---- ---- ------
Summary:
System:   5.09 Watts on average with standard deviation 1.20

Read this to understand above output.
I'm not seeing the 3.x I saw when using powertop.  But this is not bad with some work app/email and qutebrowser and 1 local termite + tmux and 2 remote mosh +tmux.

Offline

#949 2016-09-11 21:11:09

kgizdov
Package Maintainer (PM)
From: Edinburgh, UK
Registered: 2015-12-08
Posts: 113

Re: Dell XPS 13 9350 Late 2015

Has anyone even seen this before:

[ 8050.725362] ------------[ cut here ]------------
[ 8050.725394] WARNING: CPU: 0 PID: 5127 at net/sched/sch_generic.c:272 dev_watchdog+0x22a/0x230
[ 8050.725405] NETDEV WATCHDOG: enp57s0u1 (rndis_host): transmit queue 0 timed out
[ 8050.725411] Modules linked in: rndis_host cdc_ether usbnet mii rfcomm ctr ccm cmac fuse overlay uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media btusb btrtl bnep joydev mousedev arc4 nls_iso8859_1 snd_hda_codec_hdmi snd_soc_skl nls_cp437 dell_led i2c_designware_platform iTCO_wdt vfat snd_soc_skl_ipc fat iTCO_vendor_support i2c_designware_core snd_soc_sst_ipc snd_soc_sst_dsp dell_wmi snd_hda_ext_core snd_soc_sst_match iwlmvm snd_hda_codec_realtek mac80211 snd_hda_codec_generic snd_soc_core intel_rapl dell_laptop snd_compress dell_smbios x86_pkg_temp_thermal intel_powerclamp dcdbas snd_pcm_dmaengine ac97_bus iwlwifi kvm_intel snd_hda_intel snd_hda_codec snd_hda_core rtsx_pci_ms snd_hwdep kvm memstick irqbypass cfg80211 snd_pcm intel_cstate intel_rapl_perf snd_timer
[ 8050.725596]  snd input_leds pcspkr led_class i2c_i801 soundcore mei_me mei shpchp idma64 intel_pch_thermal intel_lpss_pci ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 processor_thermal_device intel_soc_dts_iosf xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG fan thermal wmi xt_limit battery i2c_hid xt_tcpudp xt_addrtype hci_uart btbcm btqca btintel nf_conntrack_ipv4 nf_defrag_ipv4 bluetooth xt_conntrack rfkill pinctrl_sunrisepoint pinctrl_intel intel_lpss_acpi intel_lpss ip6table_filter int3400_thermal acpi_als evdev int3403_thermal acpi_thermal_rel mac_hid int340x_thermal_zone ip6_tables kfifo_buf ac acpi_pad intel_hid industrialio sparse_keymap nf_conntrack_netbios_ns tpm_tis nf_conntrack_broadcast tpm fjes nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack
[ 8050.725774]  iptable_filter sch_fq_codel vboxnetflt(O) vboxnetadp(O) vboxdrv(O) coretemp msr ip_tables x_tables ext4 crc16 jbd2 mbcache algif_skcipher af_alg hid_multitouch usbhid hid dm_crypt dm_mod rtsx_pci_sdmmc mmc_core serio_raw atkbd libps2 crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd ahci libahci xhci_pci xhci_hcd libata rtsx_pci scsi_mod usbcore usb_common i8042 serio i915 video button i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm intel_agp intel_gtt nvme nvme_core jitterentropy_rng sha256_ssse3 sha256_generic hmac drbg ansi_cprng
[ 8050.725952] CPU: 0 PID: 5127 Comm: chromium Tainted: G     U  W  O    4.7.2-1-ARCH #1
[ 8050.725960] Hardware name: Dell Inc. XPS 13 9350/0VM5NC, BIOS 1.4.4 06/14/2016
[ 8050.725969]  0000000000000286 000000004c6af300 ffff88047ec03d90 ffffffff812eb132
[ 8050.725986]  ffff88047ec03de0 0000000000000000 ffff88047ec03dd0 ffffffff8107a3ab
[ 8050.726000]  000001100000022f 0000000000000000 ffff8803a7a5c880 0000000000000000
[ 8050.726015] Call Trace:
[ 8050.726023]  <IRQ>  [<ffffffff812eb132>] dump_stack+0x63/0x81
[ 8050.726052]  [<ffffffff8107a3ab>] __warn+0xcb/0xf0
[ 8050.726066]  [<ffffffff8107a42f>] warn_slowpath_fmt+0x5f/0x80
[ 8050.726088]  [<ffffffff814fc37a>] dev_watchdog+0x22a/0x230
[ 8050.726103]  [<ffffffff814fc150>] ? qdisc_rcu_free+0x40/0x40
[ 8050.726120]  [<ffffffff810e71c5>] call_timer_fn+0x35/0x150
[ 8050.726134]  [<ffffffff814fc150>] ? qdisc_rcu_free+0x40/0x40
[ 8050.726149]  [<ffffffff810e7516>] run_timer_softirq+0x236/0x2e0
[ 8050.726165]  [<ffffffff815e12c6>] __do_softirq+0xe6/0x2ec
[ 8050.726180]  [<ffffffff8107f983>] irq_exit+0xa3/0xb0
[ 8050.726195]  [<ffffffff815e10b2>] smp_apic_timer_interrupt+0x42/0x50
[ 8050.726209]  [<ffffffff815df3b2>] apic_timer_interrupt+0x82/0x90
[ 8050.726215]  <EOI> 
[ 8050.726226] ---[ end trace 43ed79263da41d5d ]---

Any ideas what may have caused it. The trace seems not very helpful. Also, do people know how/where to report these?

Offline

#950 2016-09-11 21:25:17

frank604
Member
From: BC, Canada
Registered: 2011-04-20
Posts: 1,212

Re: Dell XPS 13 9350 Late 2015

Did it cause you any issues?  If yes, you can write a bug report upstream at bugzilla for the kernel.  Search before writing a report though.

Offline

Pages: 1 … 36 37 38 39 40 … 54

Topic closed

Board footer

Powered by FluxBB