fox2k12
Anmeldungsdatum: 22. September 2012
Beiträge: 158
Wohnort: Bei Stuttgart
|
Hallo, ich habe auf meinem HP ProBook 450 G4 Notebook KUbuntu 17.04 x64 installiert.
Das UEFI ist aktuell, KUbuntu auf aktuellem stand. Es läuft alles soweit stabil und alles funktioniert auch. Nur eine Sache stört mich sehr:
Beim Booten bleibt er ca. 1,5Min. hängen, bevor es weitergeht. Ausgabe von DMESG :
....
[ 7.648421] snd_hda_codec_conexant hdaudioC0D0: CX8200: BIOS auto-probing.
[ 7.648937] snd_hda_codec_conexant hdaudioC0D0: autoconfig for CX8200: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
[ 7.648939] snd_hda_codec_conexant hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 7.648940] snd_hda_codec_conexant hdaudioC0D0: hp_outs=1 (0x16/0x0/0x0/0x0/0x0)
[ 7.648941] snd_hda_codec_conexant hdaudioC0D0: mono: mono_out=0x0
[ 7.648942] snd_hda_codec_conexant hdaudioC0D0: inputs:
[ 7.648943] snd_hda_codec_conexant hdaudioC0D0: Internal Mic=0x1a
[ 7.648944] snd_hda_codec_conexant hdaudioC0D0: Mic=0x19
[ 7.649893] snd_hda_codec_conexant hdaudioC0D0: Enable sync_write for stable communication
[ 7.675266] intel_rapl: Found RAPL domain package
[ 7.675267] intel_rapl: Found RAPL domain core
[ 7.675268] intel_rapl: Found RAPL domain uncore
[ 7.675269] intel_rapl: Found RAPL domain dram
[ 7.686017] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input17
[ 7.686071] input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1f.3/sound/card0/input18
[ 7.686121] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input19
[ 7.686170] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input20
[ 7.686215] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input21
[ 7.713842] ACPI Error: Needed [Buffer/String/Package], found [Integer] ffff8b7b1e5a31b0 (20160930/exresop-594)
[ 7.713848] ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20160930/dswexec-461)
[ 7.713852] ACPI Error: Method parse/execution failed [\_SB.WMIV.WVPO] (Node ffff8b7b280ae3e8), AE_AML_OPERAND_TYPE (20160930/psparse-543)
[ 7.713858] ACPI Error: Method parse/execution failed [\_SB.WMIV.WMPV] (Node ffff8b7b280aef50), AE_AML_OPERAND_TYPE (20160930/psparse-543)
[ 7.714220] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
[ 7.715288] ACPI Error: Needed [Buffer/String/Package], found [Integer] ffff8b7b1e5a3240 (20160930/exresop-594)
[ 7.715293] ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20160930/dswexec-461)
[ 7.715297] ACPI Error: Method parse/execution failed [\_SB.WMIV.WVPO] (Node ffff8b7b280ae3e8), AE_AML_OPERAND_TYPE (20160930/psparse-543)
[ 7.715303] ACPI Error: Method parse/execution failed [\_SB.WMIV.WMPV] (Node ffff8b7b280aef50), AE_AML_OPERAND_TYPE (20160930/psparse-543)
[ 7.716578] ACPI Error: Needed [Buffer/String/Package], found [Integer] ffff8b7b1e5a30d8 (20160930/exresop-594)
[ 7.716583] ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20160930/dswexec-461)
[ 7.716587] ACPI Error: Method parse/execution failed [\_SB.WMIV.WVPO] (Node ffff8b7b280ae3e8), AE_AML_OPERAND_TYPE (20160930/psparse-543)
[ 7.716593] ACPI Error: Method parse/execution failed [\_SB.WMIV.WMPV] (Node ffff8b7b280aef50), AE_AML_OPERAND_TYPE (20160930/psparse-543)
[ 7.716652] input: HP WMI hotkeys as /devices/virtual/input/input22
[ 7.720108] ACPI Error: Attempt to CreateField of length zero (20160930/dsopcode-168)
[ 7.720115] ACPI Error: Method parse/execution failed [\_SB.WMIV.WVPI] (Node ffff8b7b280aef00), AE_AML_OPERAND_VALUE (20160930/psparse-543)
[ 7.720124] ACPI Error: Method parse/execution failed [\_SB.WMIV.WMPV] (Node ffff8b7b280aef50), AE_AML_OPERAND_VALUE (20160930/psparse-543)
[ 7.752643] iwlwifi 0000:02:00.0 wlp2s0: renamed from wlan0
[ 7.754774] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
[ 7.901852] audit: type=1400 audit(1504346524.835:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/snapd/snap-confine" pid=801 comm="apparmor_parser"
[ 7.901854] audit: type=1400 audit(1504346524.835:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=801 comm="apparmor_parser"
[ 7.902149] audit: type=1400 audit(1504346524.835:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=799 comm="apparmor_parser"
[ 7.902150] audit: type=1400 audit(1504346524.835:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=799 comm="apparmor_parser"
[ 7.902151] audit: type=1400 audit(1504346524.835:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=799 comm="apparmor_parser"
[ 7.902152] audit: type=1400 audit(1504346524.835:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=799 comm="apparmor_parser"
[ 7.902983] audit: type=1400 audit(1504346524.839:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/ippusbxd" pid=805 comm="apparmor_parser"
[ 7.904091] audit: type=1400 audit(1504346524.839:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/mysqld-akonadi" pid=806 comm="apparmor_parser"
[ 7.904092] audit: type=1400 audit(1504346524.839:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/mysqld-akonadi///usr/sbin/mysqld" pid=806 comm="apparmor_parser"
[ 8.798977] input: ST LIS3LV02DL Accelerometer as /devices/platform/lis3lv02d/input/input23
-- Warum diese Verzögerung ab hier ? --
[ 97.465099] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 97.465100] Bluetooth: BNEP filters: protocol multicast
[ 97.465103] Bluetooth: BNEP socket layer initialized
[ 97.655252] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
[ 97.677563] r8169 0000:01:00.0 enp1s0: link down
[ 97.677643] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
[ 97.681181] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 97.682949] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[ 97.683394] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[ 97.690437] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[ 97.690442] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
[ 97.690443] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
[ 97.690445] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
[ 97.749140] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[ 97.749581] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[ 97.776335] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 97.783987] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[ 97.784427] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[ 97.791454] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[ 97.791460] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
[ 97.791464] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
[ 97.791466] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
[ 97.849302] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[ 97.849743] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[ 97.856983] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[ 97.856991] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
[ 97.856994] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
[ 97.856996] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
[ 97.865461] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 97.922085] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 101.667097] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 101.672431] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 101.676311] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 108.761434] Bluetooth: RFCOMM TTY layer initialized
[ 108.761439] Bluetooth: RFCOMM socket layer initialized
[ 108.761442] Bluetooth: RFCOMM ver 1.11
....
Liegt es an diesem "ST LIS3LV02DL Accelerometer" Ding, was immer das auch sein soll ?
Denn ab dort beginnt diese Verzögerung. Wegen der "link is not ready" Meldung vom enp1s0 und wlp2s0 device :
Es spielt keine Rolle ob ein LAN Kabel angeschlossen ist und/oder eine Verbindung zum WLAN
besteht, diese Verzögerung von 8 auf 97Sek. ist immer an der selben Stelle und unverändert. Da dieses Notebook "Designd for Windows"-Hardware ist, nehme ich an, da kann man nichts machen
ausser hoffen und warten das irgendwann eine passende Firmware von der entwickler community erscheint ? Ansonsten, hat Jemand eine Idee ?
|
hakel
Anmeldungsdatum: 13. August 2009
Beiträge: 23336
|
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685794 Das kannte ich auch noch nicht. Wenn man den Laptop an die Wand schmeißt, zieht die Festplatte die Füße ein. Aha ... Warte auf den nächsten Kernel.
|
Taomon
Supporter
Anmeldungsdatum: 30. Januar 2011
Beiträge: 8432
Wohnort: Digiworld
|
Zeige mal ls -al /dev/input/ und auf Verdacht udevadm info --name=/dev/input/js0 --attribute-walk Gruß Taomon
|
fox2k12
(Themenstarter)
Anmeldungsdatum: 22. September 2012
Beiträge: 158
Wohnort: Bei Stuttgart
|
Taomon schrieb: Zeige mal ls -al /dev/input/ und auf Verdacht udevadm info --name=/dev/input/js0 --attribute-walk Gruß Taomon
Hier die Ausgaben :
office-user@office:~$ ls -al /dev/input/
insgesamt 0
drwxr-xr-x 4 root root 500 Sep 21 17:36 .
drwxr-xr-x 21 root root 4260 Sep 21 17:36 ..
drwxr-xr-x 2 root root 120 Sep 21 17:36 by-id
drwxr-xr-x 2 root root 140 Sep 21 17:36 by-path
crw-rw---- 1 root input 13, 64 Sep 21 17:36 event0
crw-rw---- 1 root input 13, 65 Sep 21 17:36 event1
crw-rw---- 1 root input 13, 74 Sep 21 17:36 event10
crw-rw---- 1 root input 13, 75 Sep 21 17:36 event11
crw-rw---- 1 root input 13, 76 Sep 21 17:36 event12
crw-rw---- 1 root input 13, 77 Sep 21 17:36 event13
crw-rw---- 1 root input 13, 78 Sep 21 17:36 event14
crw-rw---- 1 root input 13, 79 Sep 21 17:36 event15
crw-rw---- 1 root input 13, 80 Sep 21 17:36 event16
crw-rw---- 1 root input 13, 66 Sep 21 17:36 event2
crw-rw---- 1 root input 13, 67 Sep 21 17:36 event3
crw-rw---- 1 root input 13, 68 Sep 21 17:36 event4
crw-rw---- 1 root input 13, 69 Sep 21 17:36 event5
crw-rw---- 1 root input 13, 70 Sep 21 17:36 event6
crw-rw---- 1 root input 13, 71 Sep 21 17:36 event7
crw-rw---- 1 root input 13, 72 Sep 21 17:36 event8
crw-rw---- 1 root input 13, 73 Sep 21 17:36 event9
crw-rw-r-- 1 root input 13, 0 Sep 21 17:36 js0
crw-rw---- 1 root input 13, 63 Sep 21 17:36 mice
crw-rw---- 1 root input 13, 32 Sep 21 17:36 mouse0
crw-rw---- 1 root input 13, 33 Sep 21 17:36 mouse1
office-user@office:~$ udevadm info --name=/dev/input/js0 --attribute-walk
Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/devices/platform/lis3lv02d/input/input23/js0':
KERNEL=="js0"
SUBSYSTEM=="input"
DRIVER==""
looking at parent device '/devices/platform/lis3lv02d/input/input23':
KERNELS=="input23"
SUBSYSTEMS=="input"
DRIVERS==""
ATTRS{max}=="2000"
ATTRS{min}=="0"
ATTRS{name}=="ST LIS3LV02DL Accelerometer"
ATTRS{phys}=="lis3lv02d/input0"
ATTRS{poll}=="50"
ATTRS{properties}=="0"
ATTRS{uniq}==""
looking at parent device '/devices/platform/lis3lv02d':
KERNELS=="lis3lv02d"
SUBSYSTEMS=="platform"
DRIVERS==""
ATTRS{driver_override}=="(null)"
ATTRS{position}=="(36,0,1134)"
ATTRS{rate}=="100"
looking at parent device '/devices/platform':
KERNELS=="platform"
SUBSYSTEMS==""
DRIVERS==""
office-user@office:~$
Ich rate jetzt mal :
der Kernel kann mit diesem Accelerometer Device (noch)nichts anfangen, da fehlt das passende Kernelmodul/Treiber ?
Dann heist es wohl doch warten. 17.10 steht ja vor der Tür.
Um dem Kernel jetzt zu sagen das er dieses Device einfach ignorieren und durchbooten soll, müsste ich
mir einen Kernel selbst compilieren, richtig ? hakel schrieb: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685794 Das kannte ich auch noch nicht. Wenn man den Laptop an die Wand schmeißt, zieht die Festplatte die Füße ein. Aha ... Warte auf den nächsten Kernel.
Kam mir auch schon in den Sinn, lass ich lieber, wird zu teuer. 😛
|
Taomon
Supporter
Anmeldungsdatum: 30. Januar 2011
Beiträge: 8432
Wohnort: Digiworld
|
Mann kann probieren über eine udev-regel was zu drehen. Ob Dein Rechner dann schneller durchbootet weiß ich aber nicht. Bei mir war das Problem ein anderes. klick Oder das entsprechende Modul blacklisten. lsmod zeigt was? Gruß Taomon
|
fox2k12
(Themenstarter)
Anmeldungsdatum: 22. September 2012
Beiträge: 158
Wohnort: Bei Stuttgart
|
Taomon schrieb: Mann kann probieren über eine udev-regel was zu drehen. Ob Dein Rechner dann schneller durchbootet weiß ich aber nicht. Bei mir war das Problem ein anderes. klick Oder das entsprechende Modul blacklisten. lsmod zeigt was? Gruß Taomon
office-user@office:~$ lsmod
Module Size Used by
mmc_block 36864 0
ccm 20480 3
rfcomm 77824 14
cmac 16384 1
bnep 20480 2
nls_iso8859_1 16384 1
hp_wmi 16384 0
snd_soc_skl 65536 0
snd_soc_skl_ipc 49152 1 snd_soc_skl
sparse_keymap 16384 1 hp_wmi
snd_soc_sst_ipc 16384 1 snd_soc_skl_ipc
snd_hda_codec_hdmi 49152 1
snd_soc_sst_dsp 28672 1 snd_soc_skl_ipc
snd_hda_ext_core 24576 1 snd_soc_skl
intel_rapl 20480 0
snd_soc_sst_match 16384 1 snd_soc_skl
x86_pkg_temp_thermal 16384 0
intel_powerclamp 16384 0
snd_hda_codec_conexant 24576 1
coretemp 16384 0
snd_hda_codec_generic 73728 1 snd_hda_codec_conexant
snd_soc_core 233472 1 snd_soc_skl
snd_compress 20480 1 snd_soc_core
arc4 16384 2
ac97_bus 16384 1 snd_soc_core
snd_pcm_dmaengine 16384 1 snd_soc_core
snd_hda_intel 36864 3
kvm 593920 0
snd_hda_codec 126976 4 snd_hda_intel,snd_hda_codec_conexant,snd_hda_codec_hdmi,snd_hda_codec_generic
snd_hda_core 81920 7 snd_hda_intel,snd_hda_codec_conexant,snd_hda_codec,snd_hda_ext_core,snd_soc_skl,snd_hda_codec_hdmi,snd_hda_codec_generic
snd_hwdep 16384 1 snd_hda_codec
irqbypass 16384 1 kvm
snd_pcm 102400 8 snd_hda_intel,snd_hda_codec,snd_pcm_dmaengine,snd_hda_ext_core,snd_hda_core,snd_soc_skl,snd_hda_codec_hdmi,snd_soc_core
crct10dif_pclmul 16384 0
crc32_pclmul 16384 0
ghash_clmulni_intel 16384 0
pcbc 16384 0
snd_seq_midi 16384 0
snd_seq_midi_event 16384 1 snd_seq_midi
iwlmvm 368640 0
snd_rawmidi 32768 1 snd_seq_midi
mac80211 782336 1 iwlmvm
aesni_intel 167936 941
aes_x86_64 20480 1 aesni_intel
iwlwifi 229376 1 iwlmvm
snd_seq 65536 2 snd_seq_midi_event,snd_seq_midi
crypto_simd 16384 1 aesni_intel
glue_helper 16384 1 aesni_intel
cryptd 24576 469 crypto_simd,ghash_clmulni_intel,aesni_intel
snd_seq_device 16384 3 snd_seq,snd_rawmidi,snd_seq_midi
uvcvideo 90112 0
snd_timer 32768 2 snd_seq,snd_pcm
cfg80211 602112 3 iwlmvm,iwlwifi,mac80211
videobuf2_vmalloc 16384 1 uvcvideo
joydev 20480 0
videobuf2_memops 16384 1 videobuf2_vmalloc
videobuf2_v4l2 24576 1 uvcvideo
rtsx_pci_ms 20480 0
videobuf2_core 40960 2 uvcvideo,videobuf2_v4l2
serio_raw 16384 0
videodev 172032 3 uvcvideo,videobuf2_core,videobuf2_v4l2
snd 77824 19 snd_compress,snd_hda_intel,snd_hwdep,snd_hda_codec_conexant,snd_seq,snd_hda_codec,snd_timer,snd_rawmidi,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_seq_device,snd_soc_core,snd_pcm
media 40960 2 uvcvideo,videodev
soundcore 16384 1 snd
memstick 16384 1 rtsx_pci_ms
input_leds 16384 0
btusb 45056 0
shpchp 36864 0
btrtl 16384 1 btusb
mei_me 40960 0
mei 102400 1 mei_me
intel_pch_thermal 16384 0
hci_uart 98304 0
btbcm 16384 2 hci_uart,btusb
btqca 16384 1 hci_uart
hp_accel 28672 0
btintel 16384 2 hci_uart,btusb
lis3lv02d 20480 1 hp_accel
bluetooth 557056 43 btrtl,hci_uart,btintel,btqca,bnep,btbcm,rfcomm,btusb
input_polldev 16384 1 lis3lv02d
intel_lpss_acpi 16384 0
mac_hid 16384 0
intel_lpss 16384 1 intel_lpss_acpi
tpm_crb 16384 0
hp_wireless 16384 0
acpi_pad 180224 0
parport_pc 32768 0
ppdev 20480 0
lp 20480 0
parport 49152 3 lp,parport_pc,ppdev
ip_tables 24576 0
x_tables 36864 1 ip_tables
autofs4 40960 2
hid_logitech_hidpp 28672 0
hid_logitech_dj 20480 0
usbhid 53248 0
rtsx_pci_sdmmc 24576 0
i915 1449984 20
i2c_algo_bit 16384 1 i915
drm_kms_helper 151552 1 i915
syscopyarea 16384 1 drm_kms_helper
psmouse 139264 0
sysfillrect 16384 1 drm_kms_helper
sysimgblt 16384 1 drm_kms_helper
fb_sys_fops 16384 1 drm_kms_helper
rtsx_pci 57344 2 rtsx_pci_sdmmc,rtsx_pci_ms
drm 352256 9 i915,drm_kms_helper
ahci 36864 3
r8169 81920 0
libahci 32768 1 ahci
mii 16384 1 r8169
wmi 16384 1 hp_wmi
video 40960 1 i915
pinctrl_sunrisepoint 28672 0
i2c_hid 20480 0
pinctrl_intel 20480 1 pinctrl_sunrisepoint
hid 114688 6 i2c_hid,usbhid,hid_logitech_dj,hid_logitech_hidpp
fjes 73728 0
office-user@office:~$
|
Taomon
Supporter
Anmeldungsdatum: 30. Januar 2011
Beiträge: 8432
Wohnort: Digiworld
|
Probier dies. Erstelle die Datei /etc/modprobe.d/hp_accel.conf mit folgendem Imhalt. blacklist hp_accel und danach Reboot. Sollte es zu seltsamen Effekten kommen, lösche die Datei einfach. Gruß Taomon P.S mich zu zitieren ist nicht nötig.
|
fox2k12
(Themenstarter)
Anmeldungsdatum: 22. September 2012
Beiträge: 158
Wohnort: Bei Stuttgart
|
Ok, habe ich gemacht. Das hp_accel Modul ist raus.
office-user@office:~$ lsmod | grep "hp_accel"
office-user@office:~$ Seltsam, jetzt ist der "Zeitsprung" bei AppArmor :
...
[ 6.924053] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input18
[ 6.924093] input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1f.3/sound/card0/input19
[ 6.924126] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input20
[ 6.924158] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input21
[ 6.924189] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input22
[ 6.972401] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
[ 7.016101] audit: type=1400 audit(1506018077.979:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/snapd/snap-confine" pid=807 comm="apparmor_parser"
[ 7.016103] audit: type=1400 audit(1506018077.979:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=807 comm="apparmor_parser"
[ 7.016650] audit: type=1400 audit(1506018077.979:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=805 comm="apparmor_parser"
[ 7.016651] audit: type=1400 audit(1506018077.979:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=805 comm="apparmor_parser"
[ 7.016652] audit: type=1400 audit(1506018077.979:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=805 comm="apparmor_parser"
[ 7.016653] audit: type=1400 audit(1506018077.979:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=805 comm="apparmor_parser"
[ 7.017534] audit: type=1400 audit(1506018077.979:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/ippusbxd" pid=811 comm="apparmor_parser"
[ 7.017911] audit: type=1400 audit(1506018077.979:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/cups-browsed" pid=809 comm="apparmor_parser"
[ 7.018782] audit: type=1400 audit(1506018077.983:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/telepathy/mission-control-5" pid=808 comm="apparmor_parser"
[ 95.940080] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 95.940082] Bluetooth: BNEP filters: protocol multicast
[ 95.940085] Bluetooth: BNEP socket layer initialized
...
Bluetooth funktioniert aber normal.
Ich werde nicht schlau daraus.
|
Hans9876543210
Anmeldungsdatum: 2. Januar 2011
Beiträge: 3741
|
Dann mach doch mal:
| systemd-analyze blame
systemctl list-units --state failed
journalctl -k | egrep -i 'err|war|fail|disabl'
|
|
fox2k12
(Themenstarter)
Anmeldungsdatum: 22. September 2012
Beiträge: 158
Wohnort: Bei Stuttgart
|
systemd-analyze blame
5.036s NetworkManager-wait-online.service
1.049s keyboard-setup.service
793ms systemd-backlight@backlight:intel_backlight.service
481ms dev-sda5.device
383ms systemd-resolved.service
135ms upower.service
124ms systemd-timesyncd.service
122ms plymouth-quit.service
103ms ModemManager.service
98ms accounts-daemon.service
87ms networking.service
77ms systemd-rfkill.service
64ms apport.service
60ms thermald.service
60ms systemd-udev-trigger.service
59ms irqbalance.service
59ms systemd-logind.service
56ms grub-common.service
46ms systemd-udevd.service
46ms NetworkManager.service
44ms alsa-restore.service
43ms snapd.service
41ms rsyslog.service
40ms pppd-dns.service
39ms udisks2.service
36ms apparmor.service
34ms packagekit.service
31ms systemd-fsck@dev-disk-by\x2duuid-AADA\x2dDD99.service
29ms systemd-journald.service
29ms avahi-daemon.service
28ms bluetooth.service
25ms polkit.service
24ms colord.service
23ms systemd-modules-load.service
21ms snapd.autoimport.service
21ms systemd-fsck@dev-disk-by\x2duuid-25a941b6\x2d7c86\x2d475d\x2d96e3\x2dcfd629db041e.service
19ms user@1000.service
18ms systemd-tmpfiles-setup-dev.service
16ms systemd-tmpfiles-clean.service
16ms ureadahead-stop.service
14ms systemd-update-utmp-runlevel.service
14ms plymouth-start.service
13ms sddm.service
13ms user@119.service
12ms plymouth-read-write.service
12ms snap-repair.service
11ms systemd-journal-flush.service
11ms resolvconf.service
10ms setvtrgb.service
9ms dev-hugepages.mount
8ms systemd-sysctl.service
8ms systemd-random-seed.service
7ms ufw.service
7ms kmod-static-nodes.service
7ms systemd-tmpfiles-setup.service
7ms systemd-user-sessions.service
6ms sys-kernel-debug.mount
6ms boot-efi.mount
6ms systemd-remount-fs.service
5ms home.mount
5ms dev-mqueue.mount
4ms wpa_supplicant.service
3ms systemd-update-utmp.service
3ms snapd.socket
3ms rtkit-daemon.service
2ms console-setup.service
2ms sys-fs-fuse-connections.mount
1ms swapfile.swap
systemctl list-units --state failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● swapfile.swap loaded failed failed /swapfile
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
1 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'. journalctl -k | egrep -i 'err|war|fail|disabl'
Sep 21 20:21:16 office kernel: NX (Execute Disable) protection: active
Sep 21 20:21:16 office kernel: 4 disabled
Sep 21 20:21:16 office kernel: 5 disabled
Sep 21 20:21:16 office kernel: 6 disabled
Sep 21 20:21:16 office kernel: 7 disabled
Sep 21 20:21:16 office kernel: 8 disabled
Sep 21 20:21:16 office kernel: 9 disabled
Sep 21 20:21:16 office kernel: ACPI: Early table checksum verification disabled
Sep 21 20:21:16 office kernel: ACPI: IRQ0 used by override.
Sep 21 20:21:16 office kernel: ACPI: IRQ9 used by override.
Sep 21 20:21:16 office kernel: Booting paravirtualized kernel on bare hardware
Sep 21 20:21:16 office kernel: ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0xC655 (20160930/psloop-222)
Sep 21 20:21:16 office kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
Sep 21 20:21:16 office kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
Sep 21 20:21:16 office kernel: ACPI Error: Field [CAP1] at 96 exceeds Buffer [NULL] size 64 (bits) (20160930/dsopcode-236)
Sep 21 20:21:16 office kernel: ACPI Error: Method parse/execution failed [\_SB._OSC] (Node ffff9bf3e80f2410), AE_AML_BUFFER_LIMIT (20160930/psparse-543)
Sep 21 20:21:16 office kernel: ACPI : EC: interrupt blocked
Sep 21 20:21:16 office kernel: ACPI: Using IOAPIC for interrupt routing
Sep 21 20:21:16 office kernel: pci 0000:00:14.0: System wakeup disabled by ACPI
Sep 21 20:21:16 office kernel: pci 0000:00:1c.0: System wakeup disabled by ACPI
Sep 21 20:21:16 office kernel: pci 0000:00:1c.5: System wakeup disabled by ACPI
Sep 21 20:21:16 office kernel: pci 0000:00:1d.0: System wakeup disabled by ACPI
Sep 21 20:21:16 office kernel: pci 0000:00:1f.3: System wakeup disabled by ACPI
Sep 21 20:21:16 office kernel: pci 0000:01:00.0: System wakeup disabled by ACPI
Sep 21 20:21:16 office kernel: pci 0000:02:00.0: System wakeup disabled by ACPI
Sep 21 20:21:16 office kernel: pci 0000:03:00.0: System wakeup disabled by ACPI
Sep 21 20:21:16 office kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep 21 20:21:16 office kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *10 11 12 14 15)
Sep 21 20:21:16 office kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep 21 20:21:16 office kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep 21 20:21:16 office kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep 21 20:21:16 office kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep 21 20:21:16 office kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep 21 20:21:16 office kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep 21 20:21:16 office kernel: ACPI : EC: interrupt unblocked
Sep 21 20:21:16 office kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Sep 21 20:21:16 office kernel: software IO TLB [mem 0xa37b3000-0xa77b3000] (64MB) mapped at [ffff9bf2637b3000-ffff9bf2677b2fff]
Sep 21 20:21:16 office kernel: audit: initializing netlink subsys (disabled)
Sep 21 20:21:16 office kernel: r8169 0000:01:00.0: can't disable ASPM; OS doesn't have ASPM control
Sep 21 20:21:16 office kernel: [drm] GuC firmware load skipped
Sep 21 20:21:16 office kernel: ata1.00: disabling queued TRIM support
Sep 21 20:21:16 office kernel: ata1.00: disabling queued TRIM support
Sep 21 20:21:16 office kernel: EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro
Sep 21 20:21:17 office kernel: Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.8.10-fw-22.50.19.14.f.bseq
Sep 21 20:21:17 office kernel: iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-26.ucode failed with error -2
Sep 21 20:21:17 office kernel: iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-25.ucode failed with error -2
Sep 21 20:21:17 office kernel: iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-24.ucode failed with error -2
Sep 21 20:21:17 office kernel: iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-23.ucode failed with error -2
Sep 21 20:21:17 office kernel: iwlwifi 0000:02:00.0: loaded firmware version 22.391740.0 op_mode iwlmvm
Sep 21 20:21:17 office kernel: kvm: disabled by bios
Sep 21 20:21:17 office kernel: ACPI Error: Needed [Buffer/String/Package], found [Integer] ffff9bf3dd9b4b40 (20160930/exresop-594)
Sep 21 20:21:17 office kernel: ACPI Error: Method parse/execution failed [\_SB.WMIV.WVPO] (Node ffff9bf3e80ae118), AE_AML_OPERAND_TYPE (20160930/psparse-543)
Sep 21 20:21:17 office kernel: ACPI Error: Method parse/execution failed [\_SB.WMIV.WMPV] (Node ffff9bf3e80ae410), AE_AML_OPERAND_TYPE (20160930/psparse-543)
Sep 21 20:21:17 office kernel: ACPI Error: Needed [Buffer/String/Package], found [Integer] ffff9bf3de707bd0 (20160930/exresop-594)
Sep 21 20:21:17 office kernel: ACPI Error: Method parse/execution failed [\_SB.WMIV.WVPO] (Node ffff9bf3e80ae118), AE_AML_OPERAND_TYPE (20160930/psparse-543)
Sep 21 20:21:17 office kernel: ACPI Error: Method parse/execution failed [\_SB.WMIV.WMPV] (Node ffff9bf3e80ae410), AE_AML_OPERAND_TYPE (20160930/psparse-543)
Sep 21 20:21:17 office kernel: ACPI Error: Needed [Buffer/String/Package], found [Integer] ffff9bf3de707b88 (20160930/exresop-594)
Sep 21 20:21:17 office kernel: ACPI Error: Method parse/execution failed [\_SB.WMIV.WVPO] (Node ffff9bf3e80ae118), AE_AML_OPERAND_TYPE (20160930/psparse-543)
Sep 21 20:21:17 office kernel: ACPI Error: Method parse/execution failed [\_SB.WMIV.WMPV] (Node ffff9bf3e80ae410), AE_AML_OPERAND_TYPE (20160930/psparse-543)
Sep 21 20:21:17 office kernel: ACPI Error: Attempt to CreateField of length zero (20160930/dsopcode-168)
Sep 21 20:21:17 office kernel: ACPI Error: Method parse/execution failed [\_SB.WMIV.WVPI] (Node ffff9bf3e80ae438), AE_AML_OPERAND_VALUE (20160930/psparse-543)
Sep 21 20:21:17 office kernel: ACPI Error: Method parse/execution failed [\_SB.WMIV.WMPV] (Node ffff9bf3e80ae410), AE_AML_OPERAND_VALUE (20160930/psparse-543)
Sep 21 20:21:17 office kernel: Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
Sep 21 20:22:47 office kernel: pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Sep 21 20:22:47 office kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Sep 21 20:22:47 office kernel: pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Sep 21 20:22:47 office kernel: pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Sep 21 20:22:47 office kernel: pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Sep 21 20:22:47 office kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Sep 21 20:22:47 office kernel: pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Sep 21 20:22:47 office kernel: pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
|
Hans9876543210
Anmeldungsdatum: 2. Januar 2011
Beiträge: 3741
|
Scheinbar gibt es bei dir keinen Swap? free -m
cat /etc/fstab
sudo blkid
|
fox2k12
(Themenstarter)
Anmeldungsdatum: 22. September 2012
Beiträge: 158
Wohnort: Bei Stuttgart
|
SWAP wurde bei der Installation nicht angelegt. Wozu auch bei 8GB RAM.
Ist eine Win10/KUbuntu dualboot Installation.
(EFI/Secureboot, Win10 Partition und mein Benutzer Verzeichnis unter KUbuntu auf der SSD verschlüsselt) Ich wüsste jetzt auch nicht, was das damit zutun haben sollte.
|
Hans9876543210
Anmeldungsdatum: 2. Januar 2011
Beiträge: 3741
|
Das Laden der Swap Unit schlägt fehl. Vielleicht kommt daher die Verzögerung. systemctl status swapfile.swap
|
hakel
Anmeldungsdatum: 13. August 2009
Beiträge: 23336
|
Ich wüsste jetzt auch nicht, was das damit zutun haben sollte.
Die meisten Verzögerungen beim Boot entstehen dadurch, daß nicht vorhandene/bereite Laufwerke gesucht werden. Seien es nun Netzdevices oder Fehler in der fstab, die z.B. während der Installation entstanden sind. Swap kommt dabei auch recht oft vor, ein Erfahrungswert. Ich habe immer eine kleine Swap mit 2GB, um möglichen Seltsamkeiten aus dem Weg zu gehen. Wurde hier schon öfter diskutiert.
|
fox2k12
(Themenstarter)
Anmeldungsdatum: 22. September 2012
Beiträge: 158
Wohnort: Bei Stuttgart
|
Also, es ist WEDER das hp_accel modul bzw. das ST LIS3LV02DL Accelerometer device NOCH die swap. Bei der KUbuntu Installation hatte ich die Option "Meine Dateien verschlüsseln" ausgewählt, also das nur
dass Benutzer Verzeichnis verschlüsselt wird. Erneute Installation ohne diese Option und es bootet durch ohne Verzögerung. Ich habe das auf meinem alten Notebook gegen getestet, einmal mit, einmal ohne diese Option.
Genau das selbe. An der System Performance kann es sicher NICHT liegen da in dem HP 450 G4 eine Samsung 850 Pro mit 256GB die System SSD ist, und diese läuft im AHCI Modus.
CPU ist ein i5-7200U. Da ist irgendwas verbuggt in der Verschlüsselungs/Entschlüsselungs Funktion für das Benutzer Verzeichnis !
Ich warte jetzt auf 17.10 und berichte dann.
|