You are not logged in.

#1 2018-01-18 11:58:08

rokidakota
Member
Registered: 2014-11-22
Posts: 40

Files getting corrupted on my SSD after a crash

Hi, I'm wondering if anyone has 1) tips about diagnosing the problem and 2) ideas about why files can get corrupted on a drive.

Facts

Several times now I have booted my laptop and it has asked me to do a manual fsck. I've done that, and after hitting Y about 100 times to fix things, I pressed A (all), which scrolled like a thousand pages of text indicating all the broken things that had been fixed.
Since I suspected a failing SSD, I cloned my drive and I'm using a new SSD. It happened yesterday on the new one too.

Context

I'm quite sure the issue is related to using QtCreator to compile C++ programs, or it's demanding use of RAM. One of the first times it happened I believe my computer ran out of RAM. It became very slow. I thought it was frozen, so I did a hard shut down. I should have pressed AltGr+SysRq+S, but I didn't know of that possibity (to sync the drive). My mistake. But in yesterday's case QtCreator just disappeared when compiling. The system kept running fine. I had many other programs open. No issues. Then, after a while I shut down the computer and started it back on, and I was greeted with the fsck message.

More facts

After using fsck, the computer boots fine. But my cpp programs no longer compile, because many header files found in /usr/include/ got corrupted. The way I fix the broken header files is by searching which ones are not ascii

find ./ -iname "*.h" | xargs file "$1" | grep -v text

Then I use pacman -Qo /some/header/file.h to find the owner of that file, and reinstall the package. I also search for *.cpp, *.hpp and *.inl. This gets my compilation back working. I do not know if other random files on my drive are corrupted. I haven't found corrupted images or songs...

My questions are:

  • Why do these header files get full of external binary or text content? Anything I can do to avoid this happen?

  • How would you diagnose this? I wonder if it's faulty RAM, the motherboard, QtCreator, clang, ...

Thank you! :)

Offline

#2 2018-01-18 15:36:33

R00KIE
Forum Fellow
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 4,734

Re: Files getting corrupted on my SSD after a crash

As a start you can post the full output of dmesg, output of 'lspci -nnk' and 'smartctl -a -q noserial /dev/sdX' where sdX is your ssd.

Check the manufacturer's page for firmware updates for you ssd and apply them. For good measure I would make sure your ram is ok with memtest, filesystem corruption could be related to bad ram although I suppose you would see other problems if that was the case, but it doesn't hurt to check.

Are you running any form of power saving daemon like tlp or similar? Did you do any manual power saving tweaks such as the ones recommended by powertop or others?

Edit:
When you say you shutdown your computer is it a forced shutdown as in unplug it from the wall socket or by keeping the power button pressed or is it a "clean" shutdown?

Last edited by R00KIE (2018-01-18 15:38:02)


R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#3 2018-01-18 17:08:24

rokidakota
Member
Registered: 2014-11-22
Posts: 40

Re: Files getting corrupted on my SSD after a crash

Can posting the output of these commands be unsafe? Is pastebin ok?

I will learn how to update the firmware and do the memtest.

I don't have tlp nor powertop installed. I do have laptop-mode-tools. I don't remember if that's the only power management tool I have. This laptop has been running apparently fine for 2 or 3 years with ArchLinux.

When I mentioned "hard shutdown" above I meant holding down the power button for a few seconds. Yesterday after the crash a did a regular shut down, which means I touched the power button shortly, which triggers the laptop going off properly (I assume). I see the list of services being switched off.

Thank you for the help!

Last edited by rokidakota (2018-01-18 17:09:13)

Offline

#4 2018-01-18 17:23:28

R00KIE
Forum Fellow
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 4,734

Re: Files getting corrupted on my SSD after a crash

Posting the output I have requested is perfectly safe, you can post it directly here but don't forget to post it inside code tags, see here how to do it https://bbs.archlinux.org/help.php#bbcode

You can still post it on pastebin but that information will be lost after some time and it will make this post less valuable to anyone having a similar problem later.

Regarding laptop-mode-tools, either disable it or uninstall it and try to reproduce the problem. If you can't reproduce the problem, run your machine without laptop-mode-tools for a while to confirm there are no problems.


R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#5 2018-01-18 17:41:21

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,543
Website

Re: Files getting corrupted on my SSD after a crash

Could posting that output be unsafe how?  Being concerned about security is always a good thing, but if someone on the internet asks you for a certain bit of information that you are unsure if it is ok to share, asking that same person on the internet if it is ok to share is really silly.


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#6 2018-01-18 18:09:39

rokidakota
Member
Registered: 2014-11-22
Posts: 40

Re: Files getting corrupted on my SSD after a crash

Good point @Trilby By posting the question here it's not only @R00KIE who can see it, and I was hoping that if someone thinks it's not a good idea would say so.
I know it's common to ask for this info. I just don't like the idea of revealing computer details that stay online forever making it easier to hack into it, in case someone ever wanted to do that. I think the dmesg output contains computer model, host name, keyboard model, graphics table model, maybe the mac address of the router and my network cards... lots of computer/network identifying info?

@R00KIE I really hope I never reproduce the problem smile I mean, I'm risking the whole system. I realized earlier that other files were indeed damaged, for instance Firefox would crash when trying to play videos, and it was because a plugin that ffmpeg needs was corrupted. Fixed by reinstalling ffmpeg.

I'll try disabling laptop-mode-tools if that can help.

Last edited by rokidakota (2018-01-18 18:10:04)

Offline

#7 2018-01-18 18:36:41

R00KIE
Forum Fellow
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 4,734

Re: Files getting corrupted on my SSD after a crash

It is a good idea not to post things without thinking, when in doubt check the content of what is being asked. That said how would knowing any of the things you mentioned make you a special target or any easier to hack?

Certainly you are not the only one using any of the parts you have in your computer and I don't think disclosing a mac address will make you any more of a target than the next random stranger. If it was a static public IP address then I would be more inclined to agree, but with the constant scanning and prodding every internet connected machine receives every day it probably wouldn't make much of a difference anyway.

Short version: you have a problem and want help, we need that information to be able to make educated guesses otherwise we'll be playing a 20 questions game and wasting everyone's time.


R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#8 2018-01-18 19:31:31

loqs
Member
Registered: 2014-03-06
Posts: 19,113

Re: Files getting corrupted on my SSD after a crash

Under normal circumstances i.e. not running debug device firmware or requesting debug info from the network device driver would not expect to see mac address in dmesg.
You can always parse the requested outputs first and replace anything you believe is uniquely identifying with the word REDACTED so it is clearly marked what has been changed.

Offline

#9 2018-01-19 10:49:51

rokidakota
Member
Registered: 2014-11-22
Posts: 40

Re: Files getting corrupted on my SSD after a crash

Thank you all smile

[    0.000000] microcode: microcode updated early to revision 0x23, date = 2017-11-20
[    0.000000] Linux version 4.14.13-1-ARCH (builduser@heftig-32336) (gcc version 7.2.1 20171224 (GCC)) #1 SMP PREEMPT Wed Jan 10 11:14:50 UTC 2018
[    0.000000] Command line: BOOT_IMAGE=../vmlinuz-linux root=UUID=778ef320-7dcc-41bc-bcfa-37535ea14c6b rw initrd=../intel-ucode.img,../initramfs-linux.img
[    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[    0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
[    0.000000] e820: BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009cfff] usable
[    0.000000] BIOS-e820: [mem 0x000000000009d000-0x000000000009ffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000c3b17fff] usable
[    0.000000] BIOS-e820: [mem 0x00000000c3b18000-0x00000000c3d19fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000c3d1a000-0x00000000da14efff] usable
[    0.000000] BIOS-e820: [mem 0x00000000da14f000-0x00000000dc93efff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000dc93f000-0x00000000dca9efff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x00000000dca9f000-0x00000000dcafefff] ACPI data
[    0.000000] BIOS-e820: [mem 0x00000000dcaff000-0x00000000dcafffff] usable
[    0.000000] BIOS-e820: [mem 0x00000000dcb00000-0x00000000df9fffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed08000-0x00000000fed08fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed10000-0x00000000fed19fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000ffc9b000-0x00000000ffffffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000041e5fffff] usable
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] random: fast init done
[    0.000000] SMBIOS 2.7 present.
[    0.000000] DMI: FUJITSU LIFEBOOK E754/FJNB26F, BIOS Version 1.20 02/03/2015
[    0.000000] tsc: Fast TSC calibration using PIT
[    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
[    0.000000] e820: last_pfn = 0x41e600 max_arch_pfn = 0x400000000
[    0.000000] MTRR default type: write-back
[    0.000000] MTRR fixed ranges enabled:
[    0.000000]   00000-9FFFF write-back
[    0.000000]   A0000-BFFFF uncachable
[    0.000000]   C0000-FFFFF write-protect
[    0.000000] MTRR variable ranges enabled:
[    0.000000]   0 base 00E0000000 mask 7FE0000000 uncachable
[    0.000000]   1 base 00DE000000 mask 7FFE000000 uncachable
[    0.000000]   2 base 00DD000000 mask 7FFF000000 uncachable
[    0.000000]   3 base 00DCC00000 mask 7FFFC00000 uncachable
[    0.000000]   4 base 00DCB00000 mask 7FFFF00000 uncachable
[    0.000000]   5 disabled
[    0.000000]   6 disabled
[    0.000000]   7 disabled
[    0.000000]   8 disabled
[    0.000000]   9 disabled
[    0.000000] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
[    0.000000] e820: last_pfn = 0xdcb00 max_arch_pfn = 0x400000000
[    0.000000] found SMP MP-table at [mem 0x000f0100-0x000f010f] mapped at [ffffffffff200100]
[    0.000000] Scanning 1 areas for low memory corruption
[    0.000000] Base memory trampoline at [ffff9c8bc0097000] 97000 size 24576
[    0.000000] Using GB pages for direct mapping
[    0.000000] BRK [0x31c62a000, 0x31c62afff] PGTABLE
[    0.000000] BRK [0x31c62b000, 0x31c62bfff] PGTABLE
[    0.000000] BRK [0x31c62c000, 0x31c62cfff] PGTABLE
[    0.000000] BRK [0x31c62d000, 0x31c62dfff] PGTABLE
[    0.000000] BRK [0x31c62e000, 0x31c62efff] PGTABLE
[    0.000000] BRK [0x31c62f000, 0x31c62ffff] PGTABLE
[    0.000000] BRK [0x31c630000, 0x31c630fff] PGTABLE
[    0.000000] BRK [0x31c631000, 0x31c631fff] PGTABLE
[    0.000000] BRK [0x31c632000, 0x31c632fff] PGTABLE
[    0.000000] BRK [0x31c633000, 0x31c633fff] PGTABLE
[    0.000000] RAMDISK: [mem 0x7f792000-0x7fffffff]
[    0.000000] ACPI: Early table checksum verification disabled
[    0.000000] ACPI: RSDP 0x00000000000F0120 000024 (v02 FUJ   )
[    0.000000] ACPI: XSDT 0x00000000DCAFE170 0000AC (v01 FUJ    PC       01140000 FUJ  00000001)
[    0.000000] ACPI: FACP 0x00000000DCAF8000 00010C (v05 FUJ    PC       01140000 FUJ  00000001)
[    0.000000] ACPI: DSDT 0x00000000DCAE8000 00CD76 (v02 FUJ    FJNB26F  01140000 INTL 20120711)
[    0.000000] ACPI: FACS 0x00000000DCA9C000 000040
[    0.000000] ACPI: SSDT 0x00000000DCAFD000 0008FF (v01 FUJ    SataAhci 00000001 INTL 20120711)
[    0.000000] ACPI: SSDT 0x00000000DCAFC000 0002DF (v01 FUJ    BayAhci2 00000001 INTL 20120711)
[    0.000000] ACPI: SSDT 0x00000000DCAFB000 000106 (v02 FUJ    DockSsdt 00000001 INTL 20120711)
[    0.000000] ACPI: HPET 0x00000000DCAF7000 000038 (v01 FUJ    PC       01140000 FUJ  00000001)
[    0.000000] ACPI: APIC 0x00000000DCAF6000 000098 (v01 FUJ    PC       01140000 FUJ  00000001)
[    0.000000] ACPI: MCFG 0x00000000DCAF5000 00003C (v01 FUJ    PC       01140000 FUJ  00000001)
[    0.000000] ACPI: SSDT 0x00000000DCAE7000 000539 (v01 FUJ    Cpu0Ist  01140000 INTL 20120711)
[    0.000000] ACPI: SSDT 0x00000000DCAE6000 000B37 (v01 FUJ    CpuPm    01140000 INTL 20120711)
[    0.000000] ACPI: UEFI 0x00000000DCAE5000 000042 (v01 FUJ    PC       01140000 FUJ  00000001)
[    0.000000] ACPI: TCPA 0x00000000DCAE4000 000032 (v02 PTL     CRESTLN 06040000      00005A52)
[    0.000000] ACPI: MSDM 0x00000000DC9E6000 000055 (v03 FUJ    PC       01140000 FUJ  00000001)
[    0.000000] ACPI: UEFI 0x00000000DCAE3000 00003E (v01 FUJ    PC       01140000 FUJ  00000001)
[    0.000000] ACPI: FPDT 0x00000000DCAE2000 000064 (v01 FUJ    PC       01140000 FUJ  00000001)
[    0.000000] ACPI: ASF! 0x00000000DCAFA000 0000A5 (v32 FUJ    PC       01140000 FUJ  00000001)
[    0.000000] ACPI: SLIC 0x00000000DCAE1000 000176 (v01 FUJ    PC       01140000 FUJ  00000001)
[    0.000000] ACPI: UEFI 0x00000000DCAE0000 0001B6 (v01 FUJ    PC       01140000 FUJ  00000001)
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] No NUMA configuration found
[    0.000000] Faking a node at [mem 0x0000000000000000-0x000000041e5fffff]
[    0.000000] NODE_DATA(0) allocated [mem 0x41e5fc000-0x41e5fffff]
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
[    0.000000]   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
[    0.000000]   Normal   [mem 0x0000000100000000-0x000000041e5fffff]
[    0.000000]   Device   empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000001000-0x000000000009cfff]
[    0.000000]   node   0: [mem 0x0000000000100000-0x00000000c3b17fff]
[    0.000000]   node   0: [mem 0x00000000c3d1a000-0x00000000da14efff]
[    0.000000]   node   0: [mem 0x00000000dcaff000-0x00000000dcafffff]
[    0.000000]   node   0: [mem 0x0000000100000000-0x000000041e5fffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000001000-0x000000041e5fffff]
[    0.000000] On node 0 totalpages: 4162794
[    0.000000]   DMA zone: 64 pages used for memmap
[    0.000000]   DMA zone: 21 pages reserved
[    0.000000]   DMA zone: 3996 pages, LIFO batch:0
[    0.000000]   DMA32 zone: 13886 pages used for memmap
[    0.000000]   DMA32 zone: 888654 pages, LIFO batch:31
[    0.000000]   Normal zone: 51096 pages used for memmap
[    0.000000]   Normal zone: 3270144 pages, LIFO batch:31
[    0.000000] Reserving Intel graphics memory at 0x00000000dda00000-0x00000000df9fffff
[    0.000000] ACPI: PM-Timer IO Port: 0x1808
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[    0.000000] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[    0.000000] ACPI: IRQ0 used by override.
[    0.000000] ACPI: IRQ9 used by override.
[    0.000000] Using ACPI (MADT) for SMP configuration information
[    0.000000] ACPI: HPET id: 0x8086a301 base: 0xfed00000
[    0.000000] smpboot: Allowing 8 CPUs, 0 hotplug CPUs
[    0.000000] PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
[    0.000000] PM: Registered nosave memory: [mem 0x0009d000-0x0009ffff]
[    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
[    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
[    0.000000] PM: Registered nosave memory: [mem 0xc3b18000-0xc3d19fff]
[    0.000000] PM: Registered nosave memory: [mem 0xda14f000-0xdc93efff]
[    0.000000] PM: Registered nosave memory: [mem 0xdc93f000-0xdca9efff]
[    0.000000] PM: Registered nosave memory: [mem 0xdca9f000-0xdcafefff]
[    0.000000] PM: Registered nosave memory: [mem 0xdcb00000-0xdf9fffff]
[    0.000000] PM: Registered nosave memory: [mem 0xdfa00000-0xf7ffffff]
[    0.000000] PM: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
[    0.000000] PM: Registered nosave memory: [mem 0xfc000000-0xfebfffff]
[    0.000000] PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
[    0.000000] PM: Registered nosave memory: [mem 0xfec01000-0xfed07fff]
[    0.000000] PM: Registered nosave memory: [mem 0xfed08000-0xfed08fff]
[    0.000000] PM: Registered nosave memory: [mem 0xfed09000-0xfed0ffff]
[    0.000000] PM: Registered nosave memory: [mem 0xfed10000-0xfed19fff]
[    0.000000] PM: Registered nosave memory: [mem 0xfed1a000-0xfed1bfff]
[    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
[    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfedfffff]
[    0.000000] PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
[    0.000000] PM: Registered nosave memory: [mem 0xfee01000-0xffc9afff]
[    0.000000] PM: Registered nosave memory: [mem 0xffc9b000-0xffffffff]
[    0.000000] e820: [mem 0xdfa00000-0xf7ffffff] available for PCI devices
[    0.000000] Booting paravirtualized kernel on bare hardware
[    0.000000] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6370452778343963 ns
[    0.000000] setup_percpu: NR_CPUS:128 nr_cpumask_bits:128 nr_cpu_ids:8 nr_node_ids:1
[    0.000000] percpu: Embedded 42 pages/cpu @ffff9c8fde200000 s134168 r8192 d29672 u262144
[    0.000000] pcpu-alloc: s134168 r8192 d29672 u262144 alloc=1*2097152
[    0.000000] pcpu-alloc: [0] 0 1 2 3 4 5 6 7 
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 4097727
[    0.000000] Policy zone: Normal
[    0.000000] Kernel command line: BOOT_IMAGE=../vmlinuz-linux root=UUID=778ef320-7dcc-41bc-bcfa-37535ea14c6b rw initrd=../intel-ucode.img,../initramfs-linux.img
[    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[    0.000000] Calgary: detecting Calgary via BIOS EBDA area
[    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
[    0.000000] Memory: 16290164K/16651176K available (10252K kernel code, 1157K rwdata, 2788K rodata, 1348K init, 992K bss, 361012K reserved, 0K cma-reserved)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
[    0.000000] Kernel/User page tables isolation: enabled
[    0.000000] ftrace: allocating 29110 entries in 114 pages
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] 	RCU restricting CPUs from NR_CPUS=128 to nr_cpu_ids=8.
[    0.000000] 	Tasks RCU enabled.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
[    0.000000] NR_IRQS: 8448, nr_irqs: 488, preallocated irqs: 16
[    0.000000] Console: colour VGA+ 80x25
[    0.000000] console [tty0] enabled
[    0.000000] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484882848 ns
[    0.000000] hpet clockevent registered
[    0.000000] tsc: Fast TSC calibration using PIT
[    0.003333] tsc: Detected 2294.826 MHz processor
[    0.003333] Calibrating delay loop (skipped), value calculated using timer frequency.. 4591.88 BogoMIPS (lpj=7649420)
[    0.003333] pid_max: default: 32768 minimum: 301
[    0.003333] ACPI: Core revision 20170728
[    0.020009] ACPI: 6 ACPI AML tables successfully acquired and loaded
[    0.020034] Security Framework initialized
[    0.020035] Yama: becoming mindful.
[    0.022361] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes)
[    0.023550] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes)
[    0.023596] Mount-cache hash table entries: 32768 (order: 6, 262144 bytes)
[    0.023633] Mountpoint-cache hash table entries: 32768 (order: 6, 262144 bytes)
[    0.023824] CPU: Physical Processor ID: 0
[    0.023824] CPU: Processor Core ID: 0
[    0.023829] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[    0.023830] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
[    0.023834] mce: CPU supports 9 MCE banks
[    0.023842] CPU0: Thermal monitoring enabled (TM1)
[    0.023857] process: using mwait in idle threads
[    0.023859] Last level iTLB entries: 4KB 1024, 2MB 1024, 4MB 1024
[    0.023860] Last level dTLB entries: 4KB 1024, 2MB 1024, 4MB 1024, 1GB 4
[    0.024302] Freeing SMP alternatives memory: 24K
[    0.026723] smpboot: Max logical packages: 2
[    0.027133] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[    0.061779] TSC deadline timer enabled
[    0.061782] smpboot: CPU0: Intel(R) Core(TM) i7-4712MQ CPU @ 2.30GHz (family: 0x6, model: 0x3c, stepping: 0x3)
[    0.073352] Performance Events: PEBS fmt2+, Haswell events, 16-deep LBR, full-width counters, Intel PMU driver.
[    0.073393] ... version:                3
[    0.073394] ... bit width:              48
[    0.073394] ... generic registers:      4
[    0.073395] ... value mask:             0000ffffffffffff
[    0.073396] ... max period:             00007fffffffffff
[    0.073396] ... fixed-purpose events:   3
[    0.073397] ... event mask:             000000070000000f
[    0.080016] Hierarchical SRCU implementation.
[    0.093566] NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.
[    0.100014] smp: Bringing up secondary CPUs ...
[    0.126688] x86: Booting SMP configuration:
[    0.126689] .... node  #0, CPUs:      #1 #2 #3 #4 #5 #6 #7
[    0.288476] smp: Brought up 1 node, 8 CPUs
[    0.288476] smpboot: Total of 8 processors activated (36731.10 BogoMIPS)
[    0.290418] devtmpfs: initialized
[    0.290418] x86/mm: Memory block size: 128MB
[    0.291067] PM: Registering ACPI NVS region [mem 0xdc93f000-0xdca9efff] (1441792 bytes)
[    0.291067] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6370867519511994 ns
[    0.291067] futex hash table entries: 2048 (order: 5, 131072 bytes)
[    0.291067] pinctrl core: initialized pinctrl subsystem
[    0.291067] RTC time:  7:06:40, date: 01/18/18
[    0.291067] NET: Registered protocol family 16
[    0.291067] cpuidle: using governor ladder
[    0.291067] cpuidle: using governor menu
[    0.291067] ACPI: bus type PCI registered
[    0.291067] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[    0.291067] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
[    0.291067] PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
[    0.291067] PCI: Using configuration type 1 for base access
[    0.291067] core: PMU erratum BJ122, BV98, HSD29 worked around, HT is on
[    0.291067] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[    0.291067] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[    0.291067] ACPI: Added _OSI(Module Device)
[    0.291067] ACPI: Added _OSI(Processor Device)
[    0.291067] ACPI: Added _OSI(3.0 _SCP Extensions)
[    0.291067] ACPI: Added _OSI(Processor Aggregator Device)
[    0.293443] ACPI: Executed 1 blocks of module-level executable AML code
[    0.295592] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[    0.295592] ACPI: Dynamic OEM Table Load:
[    0.295594] ACPI: SSDT 0xFFFF9C8FCB902000 0011E5 (v02 FUJ    Win8Ssdt 00000001 INTL 20120711)
[    0.404155] ACPI: Dynamic OEM Table Load:
[    0.404155] ACPI: SSDT 0xFFFF9C8FCBB6A800 000433 (v01 PmRef  Cpu0Cst  00003001 INTL 20120711)
[    0.404155] ACPI: Dynamic OEM Table Load:
[    0.404155] ACPI: SSDT 0xFFFF9C8FCB83F800 0005AA (v01 PmRef  ApIst    00003000 INTL 20120711)
[    0.404155] ACPI: Dynamic OEM Table Load:
[    0.404155] ACPI: SSDT 0xFFFF9C8FCBB8F200 000119 (v01 PmRef  ApCst    00003000 INTL 20120711)
[    0.404159] ACPI: EC: EC started
[    0.404159] ACPI: EC: interrupt blocked
[    0.404159] ACPI: \_SB_.PCI0.LPCB.EC__: Used as first EC
[    0.404159] ACPI: \_SB_.PCI0.LPCB.EC__: GPE=0x17, EC_CMD/EC_SC=0x66, EC_DATA=0x62
[    0.404159] ACPI: \_SB_.PCI0.LPCB.EC__: Used as boot DSDT EC to handle transactions
[    0.404159] ACPI: Interpreter enabled
[    0.404159] ACPI: (supports S0 S3 S4 S5)
[    0.404159] ACPI: Using IOAPIC for interrupt routing
[    0.404159] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    0.404159] ACPI: GPE 0x13 active on init
[    0.406668] ACPI: GPE 0x14 active on init
[    0.406668] ACPI: Enabled 11 GPEs in block 00 to 3F
[    0.409737] acpi LNXIOBAY:00: ACPI dock station (docks/bays count: 1)
[    0.411182] acpi PNP0C15:00: ACPI dock station (docks/bays count: 2)
[    0.411802] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
[    0.411806] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
[    0.411923] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
[    0.412317] PCI host bridge to bus 0000:00
[    0.412320] pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
[    0.412321] pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
[    0.412322] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
[    0.412323] pci_bus 0000:00: root bus resource [mem 0xdfa00000-0xfeafffff window]
[    0.412324] pci_bus 0000:00: root bus resource [bus 00-3e]
[    0.412331] pci 0000:00:00.0: [8086:0c04] type 00 class 0x060000
[    0.412414] pci 0000:00:02.0: [8086:0416] type 00 class 0x030000
[    0.412425] pci 0000:00:02.0: reg 0x10: [mem 0xf0000000-0xf03fffff 64bit]
[    0.412430] pci 0000:00:02.0: reg 0x18: [mem 0xe0000000-0xefffffff 64bit pref]
[    0.412434] pci 0000:00:02.0: reg 0x20: [io  0x3000-0x303f]
[    0.412507] pci 0000:00:03.0: [8086:0c0c] type 00 class 0x040300
[    0.412516] pci 0000:00:03.0: reg 0x10: [mem 0xf0630000-0xf0633fff 64bit]
[    0.412616] pci 0000:00:14.0: [8086:8c31] type 00 class 0x0c0330
[    0.412635] pci 0000:00:14.0: reg 0x10: [mem 0xf0620000-0xf062ffff 64bit]
[    0.412692] pci 0000:00:14.0: PME# supported from D3hot D3cold
[    0.412757] pci 0000:00:16.0: [8086:8c3a] type 00 class 0x078000
[    0.412778] pci 0000:00:16.0: reg 0x10: [mem 0xf0639000-0xf063900f 64bit]
[    0.412838] pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
[    0.412907] pci 0000:00:19.0: [8086:153a] type 00 class 0x020000
[    0.412925] pci 0000:00:19.0: reg 0x10: [mem 0xf0600000-0xf061ffff]
[    0.412932] pci 0000:00:19.0: reg 0x14: [mem 0xf063f000-0xf063ffff]
[    0.412940] pci 0000:00:19.0: reg 0x18: [io  0x3080-0x309f]
[    0.412995] pci 0000:00:19.0: PME# supported from D0 D3hot D3cold
[    0.413060] pci 0000:00:1b.0: [8086:8c20] type 00 class 0x040300
[    0.413079] pci 0000:00:1b.0: reg 0x10: [mem 0xf0634000-0xf0637fff 64bit]
[    0.413145] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[    0.413214] pci 0000:00:1c.0: [8086:8c10] type 01 class 0x060400
[    0.413281] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[    0.413353] pci 0000:00:1c.5: [8086:8c1a] type 01 class 0x060400
[    0.413419] pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
[    0.413490] pci 0000:00:1c.7: [8086:8c1e] type 01 class 0x060400
[    0.413557] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
[    0.413628] pci 0000:00:1f.0: [8086:8c4f] type 00 class 0x060100
[    0.413787] pci 0000:00:1f.2: [8086:8c03] type 00 class 0x010601
[    0.413804] pci 0000:00:1f.2: reg 0x10: [io  0x30a8-0x30af]
[    0.413811] pci 0000:00:1f.2: reg 0x14: [io  0x30bc-0x30bf]
[    0.413818] pci 0000:00:1f.2: reg 0x18: [io  0x30a0-0x30a7]
[    0.413825] pci 0000:00:1f.2: reg 0x1c: [io  0x30b8-0x30bb]
[    0.413831] pci 0000:00:1f.2: reg 0x20: [io  0x3060-0x307f]
[    0.413839] pci 0000:00:1f.2: reg 0x24: [mem 0xf063c000-0xf063c7ff]
[    0.413872] pci 0000:00:1f.2: PME# supported from D3hot
[    0.413932] pci 0000:00:1f.3: [8086:8c22] type 00 class 0x0c0500
[    0.413950] pci 0000:00:1f.3: reg 0x10: [mem 0xf0638000-0xf06380ff 64bit]
[    0.413968] pci 0000:00:1f.3: reg 0x20: [io  0xefa0-0xefbf]
[    0.414074] pci 0000:00:1c.0: PCI bridge to [bus 01]
[    0.414163] pci 0000:02:00.0: [8086:08b1] type 00 class 0x028000
[    0.414240] pci 0000:02:00.0: reg 0x10: [mem 0xf0500000-0xf0501fff 64bit]
[    0.414480] pci 0000:02:00.0: PME# supported from D0 D3hot D3cold
[    0.430041] pci 0000:00:1c.5: PCI bridge to [bus 02]
[    0.430046] pci 0000:00:1c.5:   bridge window [mem 0xf0500000-0xf05fffff]
[    0.430155] pci 0000:03:00.0: [10ec:5227] type 00 class 0xff0000
[    0.430218] pci 0000:03:00.0: reg 0x10: [mem 0xf0400000-0xf0400fff]
[    0.430697] pci 0000:03:00.0: supports D1 D2
[    0.430698] pci 0000:03:00.0: PME# supported from D1 D2 D3hot D3cold
[    0.443365] pci 0000:00:1c.7: PCI bridge to [bus 03]
[    0.443370] pci 0000:00:1c.7:   bridge window [mem 0xf0400000-0xf04fffff]
[    0.444122] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15)
[    0.444196] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *10 11 12 14 15)
[    0.444268] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 10 *11 12 14 15)
[    0.444340] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 11 12 14 15) *7
[    0.444411] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 10 11 12 14 15) *7
[    0.444481] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
[    0.444552] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 10 *11 12 14 15)
[    0.444623] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 *10 11 12 14 15)
[    0.444997] ACPI: EC: interrupt unblocked
[    0.445003] ACPI: EC: event unblocked
[    0.445009] ACPI: \_SB_.PCI0.LPCB.EC__: GPE=0x17, EC_CMD/EC_SC=0x66, EC_DATA=0x62
[    0.445010] ACPI: \_SB_.PCI0.LPCB.EC__: Used as boot DSDT EC to handle transactions and events
[    0.445060] pci 0000:00:02.0: vgaarb: setting as boot VGA device
[    0.445060] pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
[    0.445060] pci 0000:00:02.0: vgaarb: bridge control possible
[    0.445060] vgaarb: loaded
[    0.445060] EDAC MC: Ver: 3.0.0
[    0.445060] PCI: Using ACPI for IRQ routing
[    0.445060] PCI: pci_cache_line_size set to 64 bytes
[    0.446703] e820: reserve RAM buffer [mem 0x0009d000-0x0009ffff]
[    0.446705] e820: reserve RAM buffer [mem 0xc3b18000-0xc3ffffff]
[    0.446705] e820: reserve RAM buffer [mem 0xda14f000-0xdbffffff]
[    0.446706] e820: reserve RAM buffer [mem 0xdcb00000-0xdfffffff]
[    0.446707] e820: reserve RAM buffer [mem 0x41e600000-0x41fffffff]
[    0.446775] NetLabel: Initializing
[    0.446775] NetLabel:  domain hash size = 128
[    0.446776] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
[    0.446790] NetLabel:  unlabeled traffic allowed by default
[    0.446951] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
[    0.446955] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
[    0.448976] clocksource: Switched to clocksource hpet
[    0.455206] VFS: Disk quotas dquot_6.6.0
[    0.455223] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.455275] pnp: PnP ACPI init
[    0.455456] system 00:00: [mem 0xfed1c000-0xfed1ffff] has been reserved
[    0.455457] system 00:00: [mem 0xfed10000-0xfed17fff] has been reserved
[    0.455459] system 00:00: [mem 0xfed18000-0xfed18fff] has been reserved
[    0.455460] system 00:00: [mem 0xfed19000-0xfed19fff] has been reserved
[    0.455461] system 00:00: [mem 0xf8000000-0xfbffffff] has been reserved
[    0.455462] system 00:00: [mem 0xfed20000-0xfed3ffff] has been reserved
[    0.455463] system 00:00: [mem 0xfed90000-0xfed93fff] has been reserved
[    0.455465] system 00:00: [mem 0xfed45000-0xfed8ffff] has been reserved
[    0.455466] system 00:00: [mem 0xff000000-0xffffffff] could not be reserved
[    0.455467] system 00:00: [mem 0xfee00000-0xfeefffff] could not be reserved
[    0.455468] system 00:00: [mem 0xfef00000-0xfeffffff] has been reserved
[    0.455469] system 00:00: [mem 0xfed08000-0xfed08fff] has been reserved
[    0.455471] system 00:00: [mem 0xdfa10000-0xdfa1ffff] has been reserved
[    0.455475] system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.455807] system 00:01: [io  0x04d0-0x04d1] has been reserved
[    0.455809] system 00:01: [io  0x0800-0x087f] has been reserved
[    0.455810] system 00:01: [io  0x1640-0x164f] has been reserved
[    0.455811] system 00:01: [io  0x1800-0x187f] has been reserved
[    0.455812] system 00:01: [io  0x1880-0x18ff] has been reserved
[    0.455813] system 00:01: [io  0xf800-0xf87f] has been reserved
[    0.455814] system 00:01: [io  0xf880-0xf8ff] has been reserved
[    0.455815] system 00:01: [io  0xfc00-0xfc7f] has been reserved
[    0.455816] system 00:01: [io  0xfc80-0xfcff] has been reserved
[    0.455818] system 00:01: [io  0xfd00-0xfd7f] has been reserved
[    0.455819] system 00:01: [io  0x2000-0x2003] has been reserved
[    0.455820] system 00:01: [io  0x2100-0x217f] has been reserved
[    0.455821] system 00:01: [io  0x2180-0x21ff] has been reserved
[    0.455822] system 00:01: [io  0x0604-0x0607] has been reserved
[    0.455823] system 00:01: [io  0x0600-0x0603] has been reserved
[    0.455826] system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.455883] pnp 00:02: Plug and Play ACPI device, IDs FUJ0300 PNP0303 (active)
[    0.455909] pnp 00:03: Plug and Play ACPI device, IDs SYN1f08 PNP0f13 (active)
[    0.455963] pnp 00:04: Plug and Play ACPI device, IDs PNP0b00 (active)
[    0.456083] system 00:05: [mem 0xfed00000-0xfed003ff] has been reserved
[    0.456085] system 00:05: Plug and Play ACPI device, IDs PNP0103 PNP0c01 (active)
[    0.456254] pnp 00:06: Plug and Play ACPI device, IDs IFX0102 PNP0c31 (active)
[    0.456862] pnp: PnP ACPI: found 7 devices
[    0.462791] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
[    0.462816] pci 0000:00:1c.0: PCI bridge to [bus 01]
[    0.462828] pci 0000:00:1c.5: PCI bridge to [bus 02]
[    0.462833] pci 0000:00:1c.5:   bridge window [mem 0xf0500000-0xf05fffff]
[    0.462840] pci 0000:00:1c.7: PCI bridge to [bus 03]
[    0.462844] pci 0000:00:1c.7:   bridge window [mem 0xf0400000-0xf04fffff]
[    0.462852] pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
[    0.462853] pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
[    0.462854] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
[    0.462855] pci_bus 0000:00: resource 7 [mem 0xdfa00000-0xfeafffff window]
[    0.462856] pci_bus 0000:02: resource 1 [mem 0xf0500000-0xf05fffff]
[    0.462857] pci_bus 0000:03: resource 1 [mem 0xf0400000-0xf04fffff]
[    0.462945] NET: Registered protocol family 2
[    0.463083] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
[    0.463249] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
[    0.463363] TCP: Hash tables configured (established 131072 bind 65536)
[    0.463396] UDP hash table entries: 8192 (order: 6, 262144 bytes)
[    0.463434] UDP-Lite hash table entries: 8192 (order: 6, 262144 bytes)
[    0.463501] NET: Registered protocol family 1
[    0.463513] pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
[    0.463582] pci 0000:00:14.0: can't derive routing for PCI INT A
[    0.463583] pci 0000:00:14.0: PCI INT A: no GSI
[    0.463652] PCI: CLS 64 bytes, default 64
[    0.463681] Unpacking initramfs...
[    0.580599] Freeing initrd memory: 8632K
[    0.580602] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[    0.580604] software IO TLB [mem 0xd614f000-0xda14f000] (64MB) mapped at [ffff9c8c9614f000-ffff9c8c9a14efff]
[    0.580872] Scanning for low memory corruption every 60 seconds
[    0.581420] Initialise system trusted keyrings
[    0.581428] Key type blacklist registered
[    0.581476] workingset: timestamp_bits=41 max_order=22 bucket_order=0
[    0.582359] zbud: loaded
[    0.583628] Key type asymmetric registered
[    0.583655] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247)
[    0.583693] io scheduler noop registered
[    0.583694] io scheduler deadline registered
[    0.583729] io scheduler cfq registered (default)
[    0.583729] io scheduler mq-deadline registered
[    0.583730] io scheduler kyber registered
[    0.583748] io scheduler bfq registered
[    0.584213] intel_idle: MWAIT substates: 0x42120
[    0.584214] intel_idle: v0.4.1 model 0x3C
[    0.584472] intel_idle: lapic_timer_reliable_states 0xffffffff
[    0.584772] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    0.585659] rtc_cmos 00:04: RTC can wake from S4
[    0.585775] rtc_cmos 00:04: rtc core: registered rtc_cmos as rtc0
[    0.585800] rtc_cmos 00:04: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
[    0.585809] intel_pstate: Intel P-state driver initializing
[    0.586105] ledtrig-cpu: registered to indicate activity on CPUs
[    0.586164] vlv2_plat_clk vlv2_plat_clk: vlv2_plat_clk initialized
[    0.586646] NET: Registered protocol family 10
[    0.595646] Segment Routing with IPv6
[    0.595690] NET: Registered protocol family 17
[    0.596947] RAS: Correctable Errors collector initialized.
[    0.597050] microcode: sig=0x306c3, pf=0x10, revision=0x23
[    0.597343] microcode: Microcode Update Driver: v2.2.
[    0.597367] sched_clock: Marking stable (597325196, 0)->(604359909, -7034713)
[    0.597984] registered taskstats version 1
[    0.597998] Loading compiled-in X.509 certificates
[    0.598041] zswap: loaded using pool lzo/zbud
[    0.602750] Key type big_key registered
[    0.602997]   Magic number: 2:127:117
[    0.603126] rtc_cmos 00:04: setting system clock to 2018-01-18 07:06:41 UTC (1516259201)
[    0.605895] Freeing unused kernel memory: 1348K
[    0.605897] Write protecting the kernel read-only data: 16384k
[    0.606514] Freeing unused kernel memory: 2016K
[    0.610635] Freeing unused kernel memory: 1308K
[    0.656588] i8042: PNP: PS/2 Controller [PNP0303:KBC,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
[    0.664859] i8042: Detected active multiplexing controller, rev 1.1
[    0.668684] serio: i8042 KBD port at 0x60,0x64 irq 1
[    0.668732] serio: i8042 AUX0 port at 0x60,0x64 irq 12
[    0.668758] serio: i8042 AUX1 port at 0x60,0x64 irq 12
[    0.668783] serio: i8042 AUX2 port at 0x60,0x64 irq 12
[    0.668808] serio: i8042 AUX3 port at 0x60,0x64 irq 12
[    0.669062] SCSI subsystem initialized
[    0.671049] ACPI: bus type USB registered
[    0.671069] usbcore: registered new interface driver usbfs
[    0.671079] usbcore: registered new interface driver hub
[    0.671114] usbcore: registered new device driver usb
[    0.671629] libata version 3.00 loaded.
[    0.673384] xhci_hcd 0000:00:14.0: can't derive routing for PCI INT A
[    0.673385] xhci_hcd 0000:00:14.0: PCI INT A: no GSI
[    0.673413] xhci_hcd 0000:00:14.0: xHCI Host Controller
[    0.673419] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1
[    0.674516] xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x00009810
[    0.674521] xhci_hcd 0000:00:14.0: cache line size of 64 is not supported
[    0.674743] hub 1-0:1.0: USB hub found
[    0.674763] hub 1-0:1.0: 15 ports detected
[    0.678652] xhci_hcd 0000:00:14.0: xHCI Host Controller
[    0.678656] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2
[    0.678805] hub 2-0:1.0: USB hub found
[    0.678818] hub 2-0:1.0: 6 ports detected
[    0.679844] ahci 0000:00:1f.2: version 3.0
[    0.679989] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x14 impl SATA mode
[    0.679990] ahci 0000:00:1f.2: flags: 64bit ncq ilck pm led clo pio slum part ems apst 
[    0.690520] scsi host0: ahci
[    0.690704] scsi host1: ahci
[    0.690876] scsi host2: ahci
[    0.690986] scsi host3: ahci
[    0.691107] scsi host4: ahci
[    0.691193] scsi host5: ahci
[    0.691223] ata1: DUMMY
[    0.691223] ata2: DUMMY
[    0.691226] ata3: SATA max UDMA/133 abar m2048@0xf063c000 port 0xf063c200 irq 26
[    0.691227] ata4: DUMMY
[    0.691229] ata5: SATA max UDMA/133 abar m2048@0xf063c000 port 0xf063c300 irq 26
[    0.691229] ata6: DUMMY
[    0.692440] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
[    1.004680] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    1.004707] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    1.006397] ata3.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[    1.006403] ata3.00: ACPI cmd b1/c1:00:00:00:00:a0 (DEVICE CONFIGURATION OVERLAY) filtered out
[    1.006500] ata5.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[    1.006503] ata5.00: ACPI cmd b1/c1:00:00:00:00:a0 (DEVICE CONFIGURATION OVERLAY) filtered out
[    1.006553] ata5.00: supports DRM functions and may not be fully accessible
[    1.006679] usb 1-9: new low-speed USB device number 2 using xhci_hcd
[    1.007319] ata5.00: disabling queued TRIM support
[    1.007323] ata5.00: ATA-9: Samsung SSD 850 PRO 256GB, EXM04B6Q, max UDMA/133
[    1.007325] ata5.00: 500118192 sectors, multi 1: LBA48 NCQ (depth 31/32), AA
[    1.009546] ata5.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[    1.009550] ata5.00: ACPI cmd b1/c1:00:00:00:00:a0 (DEVICE CONFIGURATION OVERLAY) filtered out
[    1.009661] ata5.00: supports DRM functions and may not be fully accessible
[    1.010447] ata5.00: disabling queued TRIM support
[    1.012272] ata5.00: configured for UDMA/133
[    1.045445] ata3.00: ATA-8: WDC WD3200BEVS-16VAT0, 11.01A11, max UDMA/133
[    1.045448] ata3.00: 625142448 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[    1.048144] ata3.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[    1.048148] ata3.00: ACPI cmd b1/c1:00:00:00:00:a0 (DEVICE CONFIGURATION OVERLAY) filtered out
[    1.048542] ata3.00: configured for UDMA/133
[    1.048869] scsi 2:0:0:0: Direct-Access     ATA      WDC WD3200BEVS-1 1A11 PQ: 0 ANSI: 5
[    1.049475] scsi 4:0:0:0: Direct-Access     ATA      Samsung SSD 850  4B6Q PQ: 0 ANSI: 5
[    1.054363] sd 2:0:0:0: [sda] 625142448 512-byte logical blocks: (320 GB/298 GiB)
[    1.054385] sd 2:0:0:0: [sda] Write Protect is off
[    1.054390] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    1.054392] sd 4:0:0:0: [sdb] 500118192 512-byte logical blocks: (256 GB/238 GiB)
[    1.054401] sd 4:0:0:0: [sdb] Write Protect is off
[    1.054405] sd 4:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[    1.054420] sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    1.054421] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    1.056006]  sdb: sdb1
[    1.056528] sd 4:0:0:0: [sdb] supports TCG Opal
[    1.056529] sd 4:0:0:0: [sdb] Attached SCSI disk
[    1.063365]  sda: sda1
[    1.063688] sd 2:0:0:0: [sda] Attached SCSI disk
[    1.157373] hidraw: raw HID events driver (C) Jiri Kosina
[    1.168212] usbcore: registered new interface driver usbhid
[    1.168213] usbhid: USB HID core driver
[    1.169175] input: Logitech Logitech USB Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9:1.0/0003:046D:C309.0001/input/input5
[    1.223453] hid-generic 0003:046D:C309.0001: input,hidraw0: USB HID v1.10 Keyboard [Logitech Logitech USB Keyboard] on usb-0000:00:14.0-9/input0
[    1.223599] input: Logitech Logitech USB Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9:1.1/0003:046D:C309.0002/input/input6
[    1.276714] usb 1-12: new high-speed USB device number 3 using xhci_hcd
[    1.280177] hid-generic 0003:046D:C309.0002: input,hidraw1: USB HID v1.10 Mouse [Logitech Logitech USB Keyboard] on usb-0000:00:14.0-9/input1
[    1.596720] tsc: Refined TSC clocksource calibration: 2294.687 MHz
[    1.596737] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x21139a22526, max_idle_ns: 440795252169 ns
[    2.610236] clocksource: Switched to clocksource tsc
[    3.676806] floppy0: no floppy controllers found
[    3.754045] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
[    3.833959] ip_tables: (C) 2000-2006 Netfilter Core Team
[    3.837869] systemd[1]: systemd 236 running in system mode. (+PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN default-hierarchy=hybrid)
[    3.853448] systemd[1]: Detected architecture x86-64.
[    3.853967] systemd[1]: Set hostname to <myhost77>.
[    3.933932] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[    3.934587] systemd[1]: Created slice System Slice.
[    3.934897] systemd[1]: Listening on Journal Socket (/dev/log).
[    3.938171] systemd[1]: Mounting Kernel Debug File System...
[    3.938821] systemd[1]: Mounting POSIX Message Queue File System...
[    3.939075] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[    3.939388] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    3.958733] EXT4-fs (sdb1): re-mounted. Opts: data=ordered
[    3.974828] vboxdrv: loading out-of-tree module taints kernel.
[    3.977872] vboxdrv: Found 8 processor cores
[    3.986293] systemd-journald[252]: Received request to flush runtime journal from PID 1
[    3.996861] vboxdrv: TSC mode is Invariant, tentative frequency 2294687163 Hz
[    3.996862] vboxdrv: Successfully loaded version 5.2.4 (interface 0x00290000)
[    3.998971] VBoxPciLinuxInit
[    4.001649] vboxpci: IOMMU not found (not registered)
[    4.003163] VBoxNetAdp: Successfully started.
[    4.005089] VBoxNetFlt: Successfully started.
[    4.029143] Adding 2097148k swap on /swap.  Priority:-2 extents:755 across:241331364k SSFS
[    4.316071] ACPI: AC Adapter [AC] (off-line)
[    4.326688] input: Fujitsu FUJ02E3 as /devices/LNXSYSTM:00/LNXSYBUS:00/FUJ02E3:00/input/input7
[    4.326692] fujitsu_laptop: ACPI: Fujitsu FUJ02E3 [FEXT]
[    4.330872] ACPI: \_SB_.FEXT: BTNI: [0x1010001]
[    4.336007] fujitsu_laptop: driver 0.6.0 successfully loaded
[    4.373507] EDAC ie31200: No ECC support
[    4.374540] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[    4.376846] ACPI Warning: SystemIO range 0x0000000000001828-0x000000000000182F conflicts with OpRegion 0x0000000000001800-0x000000000000187F (\_SB.PCI0.LPCB.PMIO) (20170728/utaddress-247)
[    4.376854] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[    4.376867] ACPI Warning: SystemIO range 0x0000000000000840-0x000000000000084F conflicts with OpRegion 0x0000000000000800-0x000000000000084B (\_SB.PCI0.LPCB.OGIO) (20170728/utaddress-247)
[    4.376872] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[    4.376876] ACPI Warning: SystemIO range 0x0000000000000830-0x000000000000083F conflicts with OpRegion 0x0000000000000800-0x000000000000084B (\_SB.PCI0.LPCB.OGIO) (20170728/utaddress-247)
[    4.376880] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[    4.377339] ACPI Warning: SystemIO range 0x0000000000000800-0x000000000000082F conflicts with OpRegion 0x0000000000000810-0x0000000000000813 (\IO_D) (20170728/utaddress-247)
[    4.377345] ACPI Warning: SystemIO range 0x0000000000000800-0x000000000000082F conflicts with OpRegion 0x0000000000000800-0x000000000000080F (\IO_T) (20170728/utaddress-247)
[    4.377351] ACPI Warning: SystemIO range 0x0000000000000800-0x000000000000082F conflicts with OpRegion 0x0000000000000800-0x000000000000084B (\_SB.PCI0.LPCB.OGIO) (20170728/utaddress-247)
[    4.377357] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[    4.377359] lpc_ich: Resource conflict(s) found affecting gpio_ich
[    4.377736] i801_smbus 0000:00:1f.3: SPD Write Disable is set
[    4.377756] i801_smbus 0000:00:1f.3: SMBus using PCI interrupt
[    4.403443] pps_core: LinuxPPS API ver. 1 registered
[    4.403445] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    4.424002] PTP clock support registered
[    4.425265] media: Linux media interface: v0.10
[    4.427252] mousedev: PS/2 mouse device common for all mice
[    4.429299] Linux agpgart interface v0.103
[    4.433974] tpm_tis 00:06: 1.2 TPM (device-id 0xB, rev-id 16)
[    4.437006] input: PC Speaker as /devices/platform/pcspkr/input/input10
[    4.440727] Linux video capture interface: v2.00
[    4.444141] RAPL PMU: API unit is 2^-32 Joules, 4 fixed counters, 655360 ms ovfl timer
[    4.444143] RAPL PMU: hw unit of domain pp0-core 2^-14 Joules
[    4.444144] RAPL PMU: hw unit of domain package 2^-14 Joules
[    4.444145] RAPL PMU: hw unit of domain dram 2^-14 Joules
[    4.444145] RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
[    4.445940] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[    4.445941] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[    4.446146] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[    4.447254] ACPI: Battery Slot [CMB1] (battery present)
[    4.447377] ACPI: Battery Slot [CMB2] (battery absent)
[    4.447489] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input11
[    4.447660] ACPI: Lid Switch [LID]
[    4.447717] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input12
[    4.447764] ACPI: Power Button [PWRB]
[    4.447812] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input13
[    4.447850] ACPI: Sleep Button [SLPB]
[    4.465555] AVX2 version of gcm_enc/dec engaged.
[    4.465557] AES CTR mode by8 optimization enabled
[    4.474416] uvcvideo: Found UVC 1.00 device FJ Camera (04f2:b3b4)
[    4.479723] uvcvideo 1-12:1.0: Entity type for entity Extension 4 was not initialized!
[    4.479726] uvcvideo 1-12:1.0: Entity type for entity Processing 2 was not initialized!
[    4.479728] uvcvideo 1-12:1.0: Entity type for entity Camera 1 was not initialized!
[    4.479802] input: FJ Camera: FJ Camera as /devices/pci0000:00/0000:00:14.0/usb1/1-12/1-12:1.0/input/input14
[    4.479874] usbcore: registered new interface driver uvcvideo
[    4.479875] USB Video Class driver (1.1.1)
[    4.482334] snd_hda_intel: unknown parameter 'vid' ignored
[    4.482336] snd_hda_intel: unknown parameter 'pid' ignored
[    4.482338] snd_hda_intel: unknown parameter 'vid' ignored
[    4.482339] snd_hda_intel: unknown parameter 'pid' ignored
[    4.497413] Intel(R) Wireless WiFi driver for Linux
[    4.497415] Copyright(c) 2003- 2015 Intel Corporation
[    4.500690] iwlwifi 0000:02:00.0: loaded firmware version 17.608620.0 op_mode iwlmvm
[    4.524929] random: crng init done
[    4.563040] iTCO_vendor_support: vendor-support=0
[    4.566125] tpm tpm0: A TPM error (7) occurred attempting to read a pcr value
[    4.566246] tpm tpm0: TPM is disabled/deactivated (0x7)
[    4.568112] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): registered PHC clock
[    4.573828] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[    4.573878] iTCO_wdt: Found a Lynx Point TCO device (Version=2, TCOBASE=0x1860)
[    4.574544] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[    4.575981] ppdev: user-space parallel port driver
[    4.588149] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band Wireless N 7260, REV=0x144
[    4.588308] intel_rapl: Found RAPL domain package
[    4.588310] intel_rapl: Found RAPL domain core
[    4.588311] intel_rapl: Found RAPL domain uncore
[    4.588312] intel_rapl: Found RAPL domain dram
[    4.607635] iwlwifi 0000:02:00.0: base HW address: 80:19:34:81:f9:e3
[    4.652569] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 74:2b:62:83:5c:09
[    4.652575] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[    4.652604] e1000e 0000:00:19.0 eth0: MAC: 11, PHY: 12, PBA No: FFFFFF-0FF
[    4.653254] [drm] Memory usable by graphics device = 2048M
[    4.653256] [drm] Replacing VGA console driver
[    4.654366] Console: switching to colour dummy device 80x25
[    4.659993] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    4.659994] [drm] Driver supports precise vblank timestamp query.
[    4.662027] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
[    4.667861] e1000e 0000:00:19.0 enp0s25: renamed from eth0
[    4.670413] [drm] Initialized i915 1.6.0 20170818 for 0000:00:02.0 on minor 0
[    4.671171] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[    4.671395] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input15
[    4.671555] snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[    4.673044] snd_hda_codec_realtek hdaudioC0D0: ALC282: SKU not ready 0x909701f0
[    4.673468] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC282: line_outs=1 (0x21/0x0/0x0/0x0/0x0) type:line
[    4.673470] snd_hda_codec_realtek hdaudioC0D0:    speaker_outs=1 (0x14/0x0/0x0/0x0/0x0)
[    4.673472] snd_hda_codec_realtek hdaudioC0D0:    hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
[    4.673474] snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
[    4.673475] snd_hda_codec_realtek hdaudioC0D0:    inputs:
[    4.673476] snd_hda_codec_realtek hdaudioC0D0:      Mic=0x18
[    4.673478] snd_hda_codec_realtek hdaudioC0D0:      Dock Mic=0x1a
[    4.673479] snd_hda_codec_realtek hdaudioC0D0:      Internal Mic=0x12
[    4.684304] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/sound/card0/input16
[    4.685022] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input17
[    4.685070] input: HDA Intel PCH Dock Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input18
[    4.685142] input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input19
[    4.685210] input: HDA Intel PCH Dock Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input20
[    4.707396] fbcon: inteldrmfb (fb0) is primary device
[    4.750878] input: HDA Intel HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.0/sound/card1/input21
[    4.750935] input: HDA Intel HDMI HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.0/sound/card1/input22
[    4.750983] input: HDA Intel HDMI HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:03.0/sound/card1/input23
[    4.751031] input: HDA Intel HDMI HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:03.0/sound/card1/input24
[    4.751080] input: HDA Intel HDMI HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:03.0/sound/card1/input25
[    4.804850] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[    4.805869] iwlwifi 0000:02:00.0 wlp2s0: renamed from wlan0
[    4.944548] EXT4-fs (sdb1): re-mounted. Opts: data=ordered,commit=600
[    5.634897] psmouse serio2: synaptics: queried max coordinates: x [..5652], y [..4676]
[    5.726931] psmouse serio2: synaptics: queried min coordinates: x [1410..], y [1330..]
[    5.726937] psmouse serio2: synaptics: Your touchpad (PNP: SYN1f08 PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not used, you might want to try setting psmouse.synaptics_intertouch to 1 and report this to linux-input@vger.kernel.org.
[    5.915042] psmouse serio2: synaptics: Touchpad model: 1, fw: 8.1, id: 0x1e2b1, caps: 0xd001a3/0x940300/0x126800/0x0, board id: 2721, fw id: 1450880
[    5.915051] psmouse serio2: synaptics: serio: Synaptics pass-through port at isa0060/serio2/input0
[    6.041615] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio2/input/input9
[    6.123302] Console: switching to colour frame buffer device 240x67
[    6.147028] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[    6.393503] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready
[    7.053541] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[    7.520023] floppy0: no floppy controllers found
[  419.179024] usb 1-9: USB disconnect, device number 2
[ 2606.339533] usb 1-9: new full-speed USB device number 4 using xhci_hcd
[ 2606.547996] input: Wacom Intuos 4x5 Pen as /devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9:1.0/0003:056A:0020.0003/input/input29
[ 2606.548125] wacom 0003:056A:0020.0003: hidraw0: USB HID v1.00 Device [Tablet GD-0405-U] on usb-0000:00:14.0-9/input0
[ 2613.849494] usb 1-1: new low-speed USB device number 5 using xhci_hcd
[ 2614.003966] input: Logitech Logitech USB Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/0003:046D:C309.0004/input/input32
[ 2614.060246] hid-generic 0003:046D:C309.0004: input,hidraw1: USB HID v1.10 Keyboard [Logitech Logitech USB Keyboard] on usb-0000:00:14.0-1/input0
[ 2614.068500] input: Logitech Logitech USB Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:046D:C309.0005/input/input33
[ 2614.123584] hid-generic 0003:046D:C309.0005: input,hidraw2: USB HID v1.10 Mouse [Logitech Logitech USB Keyboard] on usb-0000:00:14.0-1/input1
[ 2620.742155] NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.
[ 2620.771441] EXT4-fs (sdb1): re-mounted. Opts: data=ordered,commit=0
[ 5105.450720] wlp2s0: authenticate with dc:53:7c:7b:f0:23
[ 5105.454252] wlp2s0: send auth to dc:53:7c:7b:f0:23 (try 1/3)
[ 5105.558918] wlp2s0: send auth to dc:53:7c:7b:f0:23 (try 2/3)
[ 5105.663194] wlp2s0: send auth to dc:53:7c:7b:f0:23 (try 3/3)
[ 5105.765623] wlp2s0: authentication with dc:53:7c:7b:f0:23 timed out
[ 5108.953425] wlp2s0: authenticate with dc:53:7c:7b:f0:23
[ 5108.956427] wlp2s0: send auth to dc:53:7c:7b:f0:23 (try 1/3)
[ 5108.960821] wlp2s0: authenticated
[ 5108.962293] wlp2s0: associate with dc:53:7c:7b:f0:23 (try 1/3)
[ 5108.966736] wlp2s0: RX AssocResp from dc:53:7c:7b:f0:23 (capab=0x1411 status=0 aid=1)
[ 5108.969732] wlp2s0: associated
[ 5109.009841] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
[ 5113.385912] wlp2s0: deauthenticated from dc:53:7c:7b:f0:23 (Reason: 7=CLASS3_FRAME_FROM_NONASSOC_STA)
[ 5113.452306] wlp2s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)
[ 5113.452994] wlp2s0: authenticate with dc:53:7c:7b:f0:23
[ 5113.455744] wlp2s0: send auth to dc:53:7c:7b:f0:23 (try 1/3)
[ 5113.462493] wlp2s0: authenticated
[ 5113.465635] wlp2s0: associate with dc:53:7c:7b:f0:23 (try 1/3)
[ 5113.568983] wlp2s0: associate with dc:53:7c:7b:f0:23 (try 2/3)
[ 5113.682317] wlp2s0: associate with dc:53:7c:7b:f0:23 (try 3/3)
[ 5113.785648] wlp2s0: association with dc:53:7c:7b:f0:23 timed out
[ 5117.376147] wlp2s0: authenticate with dc:53:7c:7b:f0:23
[ 5117.379042] wlp2s0: send auth to dc:53:7c:7b:f0:23 (try 1/3)
[ 5117.382015] wlp2s0: authenticated
[ 5117.385618] wlp2s0: associate with dc:53:7c:7b:f0:23 (try 1/3)
[ 5117.492316] wlp2s0: associate with dc:53:7c:7b:f0:23 (try 2/3)
[ 5117.598969] wlp2s0: associate with dc:53:7c:7b:f0:23 (try 3/3)
[ 5117.702302] wlp2s0: association with dc:53:7c:7b:f0:23 timed out
[ 5121.790513] wlp2s0: authenticate with dc:53:7c:7b:f0:23
[ 5121.793634] wlp2s0: send auth to dc:53:7c:7b:f0:23 (try 1/3)
[ 5121.857636] wlp2s0: authenticated
[ 5121.858938] wlp2s0: associate with dc:53:7c:7b:f0:23 (try 1/3)
[ 5121.962309] wlp2s0: associate with dc:53:7c:7b:f0:23 (try 2/3)
[ 5122.065640] wlp2s0: associate with dc:53:7c:7b:f0:23 (try 3/3)
[ 5122.168973] wlp2s0: association with dc:53:7c:7b:f0:23 timed out
[ 5133.336692] wlp2s0: authenticate with dc:53:7c:7b:f0:23
[ 5133.339456] wlp2s0: send auth to dc:53:7c:7b:f0:23 (try 1/3)
[ 5133.342221] wlp2s0: authenticated
[ 5133.345673] wlp2s0: associate with dc:53:7c:7b:f0:23 (try 1/3)
[ 5133.355684] wlp2s0: RX AssocResp from dc:53:7c:7b:f0:23 (capab=0x1411 status=0 aid=1)
[ 5133.360925] wlp2s0: associated
[ 5208.651227] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[ 5208.651276] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s25: link becomes ready
[ 5286.598883] wlp2s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)
[ 5289.658624] wlp2s0: authenticate with dc:53:7c:7b:f0:24
[ 5289.662016] wlp2s0: send auth to dc:53:7c:7b:f0:24 (try 1/3)
[ 5289.714038] wlp2s0: send auth to dc:53:7c:7b:f0:24 (try 2/3)
[ 5289.749565] wlp2s0: send auth to dc:53:7c:7b:f0:24 (try 3/3)
[ 5289.801010] wlp2s0: authentication with dc:53:7c:7b:f0:24 timed out
[ 5355.684388] MediaPl~back #3[28619]: segfault at ffffffffffffffdb ip 00007f3b03826d10 sp 00007f3b0be3ab18 error 7 in libavcodec.so.57.107.100[7f3b02f67000+c53000]
[ 5364.962490] MediaPl~back #2[28685]: segfault at ffffffffffffffdb ip 00007fc21affad10 sp 00007fc223b39b18 error 7 in libavcodec.so.57.107.100[7fc21a73b000+c53000]
[ 5365.025202] MediaPl~back #2[28685]: segfault at ffffffffffffffdb ip 00007fc21affad10 sp 00007fc223b39b18 error 7 in libavcodec.so.57.107.100[7fc21a73b000+c53000]
[ 5365.087660] MediaPl~back #2[28685]: segfault at ffffffffffffffdb ip 00007fc21affad10 sp 00007fc223b39b18 error 7 in libavcodec.so.57.107.100[7fc21a73b000+c53000]
[ 5365.148009] MediaPl~back #2[28685]: segfault at ffffffffffffffdb ip 00007fc21affad10 sp 00007fc223b39b18 error 7 in libavcodec.so.57.107.100[7fc21a73b000+c53000]
[ 5379.691183] MediaPl~back #2[28750]: segfault at ffffffffffffffdb ip 00007fe07baf4d10 sp 00007fe083a3ab18 error 7 in libavcodec.so.57.107.100[7fe07b235000+c53000]
[ 5379.749139] MediaPl~back #2[28751]: segfault at ffffffffffffffdb ip 00007fe07baf4d10 sp 00007fe06d3feb18 error 7 in libavcodec.so.57.107.100[7fe07b235000+c53000]
[10457.722425] systemd: 35 output lines suppressed due to ratelimiting
[11086.082692] traps: MediaPD~oder #1[4658] trap invalid opcode ip:7f5eeb66eb3a sp:7f5ef32de3d8 error:0 in libavcodec.so.57.107.100[7f5eeae67000+c53000]
[12705.790637] usb 1-6: new high-speed USB device number 6 using xhci_hcd
[12705.971019] cdc_acm 1-6:1.0: ttyACM0: USB ACM device
[12705.971249] usbcore: registered new interface driver cdc_acm
[12705.971250] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[14721.120373] fish[31512]: segfault at 7500000020 ip 0000007500000020 sp 00007ffc733e8628 error 14 in fish (deleted)[556083198000+16b000]
[20443.577447] mmc0: new SD card at address e624
[20443.583723] mmcblk0: mmc0:e624 SD01G 969 MiB 
[20443.584595]  mmcblk0: p1
[20444.249346] mmc0: card e624 removed
[20445.450658] mmc0: new SD card at address e624
[20445.451044] mmcblk0: mmc0:e624 SD01G 969 MiB 
[20445.452244]  mmcblk0: p1
[20464.603711] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[21486.275775] mmc0: card e624 removed
[23087.154203] traps: MediaPD~oder #2[21531] trap invalid opcode ip:7faa8ff3cb3a sp:7faaa72513d8 error:0 in libavcodec.so.57.107.100[7faa8f735000+c53000]
[23092.506896] traps: MediaPD~oder #2[21598] trap invalid opcode ip:7f1e4d66eb3a sp:7f1e458833d8 error:0 in libavcodec.so.57.107.100[7f1e4ce67000+c53000]
[23095.608154] traps: MediaPD~oder #2[21660] trap invalid opcode ip:7f2e6996eb3a sp:7f2e648453d8 error:0 in libavcodec.so.57.107.100[7f2e69167000+c53000]
[24488.006527] fuse init (API version 7.26)
[28040.662362] perf: interrupt took too long (2508 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
[28740.660718] wlp2s0: authenticate with dc:53:7c:7b:f0:23
[28740.663846] wlp2s0: send auth to dc:53:7c:7b:f0:23 (try 1/3)
[28740.668045] wlp2s0: authenticated
[28740.670627] wlp2s0: associate with dc:53:7c:7b:f0:23 (try 1/3)
[28740.674769] wlp2s0: RX AssocResp from dc:53:7c:7b:f0:23 (capab=0x1411 status=0 aid=1)
[28740.678934] wlp2s0: associated
[30311.512695] MediaPl~back #2[26684]: segfault at ffffffffffffffdb ip 00007f243374dd10 sp 00007f244558fb18 error 7 in libavcodec.so.57.107.100[7f2432e8e000+c53000]
[30311.569858] MediaPl~back #2[26685]: segfault at ffffffffffffffdb ip 00007f243374dd10 sp 00007f24449feb18 error 7 in libavcodec.so.57.107.100[7f2432e8e000+c53000]
[30311.625372] MediaPl~back #2[26684]: segfault at ffffffffffffffdb ip 00007f243374dd10 sp 00007f244558fb18 error 7 in libavcodec.so.57.107.100[7f2432e8e000+c53000]
[30371.813094] MediaPl~back #3[27043]: segfault at ffffffffffffffdb ip 00007f5427e31d10 sp 00007f5439290b18 error 7 in libavcodec.so.57.107.100[7f5427572000+c53000]
[30371.870972] MediaPl~back #3[27044]: segfault at ffffffffffffffdb ip 00007f5427e31d10 sp 00007f543a7feb18 error 7 in libavcodec.so.57.107.100[7f5427572000+c53000]
[30371.928984] MediaPl~back #3[27043]: segfault at ffffffffffffffdb ip 00007f5427e31d10 sp 00007f5439290b18 error 7 in libavcodec.so.57.107.100[7f5427572000+c53000]
[30371.987405] MediaPl~back #3[27044]: segfault at ffffffffffffffdb ip 00007f5427e31d10 sp 00007f543a7feb18 error 7 in libavcodec.so.57.107.100[7f5427572000+c53000]
[30372.058410] MediaPl~back #3[27043]: segfault at ffffffffffffffdb ip 00007f5427e31d10 sp 00007f5439290b18 error 7 in libavcodec.so.57.107.100[7f5427572000+c53000]

The segfaults were corrected by reinstalling ffmpeg.

00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller [8086:0c04] (rev 06)
	Subsystem: Fujitsu Limited. Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller [10cf:17a6]
	Kernel modules: ie31200_edac
00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06)
	Subsystem: Fujitsu Limited. 4th Gen Core Processor Integrated Graphics Controller [10cf:17aa]
	Kernel driver in use: i915
	Kernel modules: i915
00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [8086:0c0c] (rev 06)
	Subsystem: Fujitsu Limited. Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [10cf:17c6]
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
00:14.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI [8086:8c31] (rev 04)
	Subsystem: Fujitsu Limited. 8 Series/C220 Series Chipset Family USB xHCI [10cf:17e1]
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci
00:16.0 Communication controller [0780]: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 [8086:8c3a] (rev 04)
	Subsystem: Fujitsu Limited. 8 Series/C220 Series Chipset Family MEI Controller [10cf:17dd]
	Kernel driver in use: mei_me
	Kernel modules: mei_me
00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection I217-LM [8086:153a] (rev 04)
	Subsystem: Fujitsu Limited. Ethernet Connection I217-LM [10cf:17e7]
	Kernel driver in use: e1000e
	Kernel modules: e1000e
00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller [8086:8c20] (rev 04)
	Subsystem: Fujitsu Limited. 8 Series/C220 Series Chipset High Definition Audio Controller [10cf:17ff]
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 [8086:8c10] (rev d4)
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:1c.5 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #6 [8086:8c1a] (rev d4)
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:1c.7 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #8 [8086:8c1e] (rev d4)
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:1f.0 ISA bridge [0601]: Intel Corporation QM87 Express LPC Controller [8086:8c4f] (rev 04)
	Subsystem: Fujitsu Limited. QM87 Express LPC Controller [10cf:17c7]
	Kernel driver in use: lpc_ich
	Kernel modules: lpc_ich
00:1f.2 SATA controller [0106]: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] [8086:8c03] (rev 04)
	Subsystem: Fujitsu Limited. 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] [10cf:17c9]
	Kernel driver in use: ahci
	Kernel modules: ahci
00:1f.3 SMBus [0c05]: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller [8086:8c22] (rev 04)
	Subsystem: Fujitsu Limited. 8 Series/C220 Series Chipset Family SMBus Controller [10cf:17cf]
	Kernel driver in use: i801_smbus
	Kernel modules: i2c_i801
02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 73)
	Subsystem: Intel Corporation Dual Band Wireless-N 7260 [8086:4060]
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI Express Card Reader [10ec:5227] (rev 01)
	Subsystem: Fujitsu Limited. RTS5227 PCI Express Card Reader [10cf:187f]
	Kernel driver in use: rtsx_pci
	Kernel modules: rtsx_pci
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.14.13-1-ARCH] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Samsung based SSDs
Device Model:     Samsung SSD 850 PRO 256GB
Firmware Version: EXM04B6Q
User Capacity:    256,060,514,304 bytes [256 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ATA8-ACS T13/1699-D revision 4c
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Thu Jan 18 17:33:37 2018 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		(    0) seconds.
Offline data collection
capabilities: 			 (0x53) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					No Offline surface scan supported.
					Self-test supported.
					No Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 133) minutes.
SCT capabilities: 	       (0x003d)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  9 Power_On_Hours          0x0032   099   099   000    Old_age   Always       -       314
 12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       -       98
177 Wear_Leveling_Count     0x0013   099   099   000    Pre-fail  Always       -       3
179 Used_Rsvd_Blk_Cnt_Tot   0x0013   100   100   010    Pre-fail  Always       -       0
181 Program_Fail_Cnt_Total  0x0032   100   100   010    Old_age   Always       -       0
182 Erase_Fail_Count_Total  0x0032   100   100   010    Old_age   Always       -       0
183 Runtime_Bad_Block       0x0013   100   100   010    Pre-fail  Always       -       0
187 Uncorrectable_Error_Cnt 0x0032   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0032   069   061   000    Old_age   Always       -       31
195 ECC_Error_Rate          0x001a   200   200   000    Old_age   Always       -       0
199 CRC_Error_Count         0x003e   100   100   000    Old_age   Always       -       0
235 POR_Recovery_Count      0x0012   099   099   000    Old_age   Always       -       4
241 Total_LBAs_Written      0x0032   099   099   000    Old_age   Always       -       1545707622

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
  255        0    65535  Read_scanning was never started
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

How does that look like?

Offline

#10 2018-01-19 13:39:47

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 78,863

Re: Files getting corrupted on my SSD after a crash

There seem to be two disks, a WD blue being sda (what does not mean it's your root device, but suspicious enough) - also we don't know your mount options and if you're trimming and whether that's probably a bad idea.

lsblk -f --discard
mount

Offline

#11 2018-01-19 14:02:08

R00KIE
Forum Fellow
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 4,734

Re: Files getting corrupted on my SSD after a crash

That looks good smile

One of my guesses would be that the SSD could be advertising queued trim and linux making use of it but in fact the SSD not supporting it properly and leading to data loss, but the following line rules that out

[    1.010447] ata5.00: disabling queued TRIM support

Speaking of trim, are you using continuous trim or periodic trim? I suspect the later but do confirm that.

From dmesg it seems you are using a laptop and have another hard disk, this makes me wonder how/where are you connecting the SSD. Are you connecting it in the "proper" place for an hard disk or are you using some caddy in the CD/DVD rom slot?

I see you are loading the virtualbox modules, how are you using it? Specifically are the virtual disks images or might you be passing a whole disk for virtualbox to use?

The only other thing I can think about now is laptop-mode-tools setting the sata ALPM to minimum power and things not playing along well together and causing data loss.

My previous advice about checking for firmware updates for the SSD still stands. Samsung is a bit tricky, they have bootable isos with the firmware updates but you have to know where to find them, see this section of the wiki https://wiki.archlinux.org/index.php/So … es#Samsung


R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#12 2018-01-19 14:32:57

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,543
Website

Re: Files getting corrupted on my SSD after a crash

Sidenote - sorry if I delayed this thread.  I certainly didn't mean to imply there was anything unsafe about posting that information.  I only intended to comment on the odd notion of security-awareness that I see come up in many contexts.


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#13 2018-01-19 14:51:35

rokidakota
Member
Registered: 2014-11-22
Posts: 40

Re: Files getting corrupted on my SSD after a crash

NAME   FSTYPE      LABEL UUID                                 MOUNTPOINT DISC-ALN DISC-GRAN DISC-MAX DISC-ZERO
sda                                                                             0        0B       0B         0
└─sda1 crypto_LUKS       210e15ab-3676-4b31-bede-6045d26c2b72                   0        0B       0B         0
sdb                                                                             0      512B       2G         0
└─sdb1 ext4              378ef370-7dcc-42bc-bcfa-35571ee23c6b /                 0      512B       2G         0

sda is not mounted, it's encrypted and spinned down 99% of the time. I'm using a DVD caddy for it. Now that you mention it, I wonder if mounting that drive is somehow related. Are such caddies known to cause problems? It's a cheap device from an unknown company. I had no such corruption issues before having this second drive inside, and I believe it was mounted when I decided to ask for help here. Maybe coincidence maybe not.

I still think it's related to C++ compilation, but I wonder if things go wrong when accessing both drives simultaneously.

I think I used Virtualbox once or twice. Not lately. The disk is just a regular file in sdb.

I will check the firmware when I have a moment. Also I read an article about Intel CPU firmware upgrades. Before the upgrades there were random (very rare) crashes on a known hosting company (forgot the name).

Thank you again for looking into this.

Last edited by rokidakota (2018-01-19 14:52:11)

Offline

#14 2018-01-19 15:38:02

R00KIE
Forum Fellow
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 4,734

Re: Files getting corrupted on my SSD after a crash

If it is sda (the rotating rust hd) that is in the caddy then that would not be my first guess but who knows if the larger current (and hence power) requirement of an hard disk could have an influence on the ssd (I'm assuming a shared power rail).

I was also thinking that the caddy might be an issue but since it seems you don't have PATA ports the caddy is most probably a passive device and it's almost the same as having the HD connected with cables.

Regarding the intel microcode updates you should have everything setup properly, as long as your system is up-to-date there is nothing else for you to do.

[    0.000000] microcode: microcode updated early to revision 0x23, date = 2017-11-20

You see now why the full output of dmesg is very useful? wink


R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#15 2018-01-26 16:53:47

rokidakota
Member
Registered: 2014-11-22
Posts: 40

Re: Files getting corrupted on my SSD after a crash

After one more corruption case (mostly fixed), I have a theory.

I increased my swap size from 2Gb to 5Gb and I haven't had any issues after that. I started monitoring my ram status with `watch free -m` when working with QtCreator. The interesting fact is that a few times (very rarely) I've seen it use more than 2Gb swap. That means that my previous configuration of 2Gb was not enough, and I think that was causing the trouble.

I believe that the file corruption happens when I run out of swap. Would that be possible under some circumstances?

ps. trim is done weekly

Last edited by rokidakota (2018-01-26 16:55:02)

Offline

#16 2018-01-26 17:17:01

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 78,863

Re: Files getting corrupted on my SSD after a crash

That means that my previous configuration of 2Gb was not enough

Not necessarily, that's a common misconception. The system swapped out some more anon pages to keep more files cached. You *might* have gone OOM previously, but that would cause stalls - in worst case freezes, but should not corrupt data (unlike an unexpected power loss by a hard shutdown which might catch the SSD while it's doing some wear leveling maintenance)

Offline

#17 2018-01-26 17:26:10

R00KIE
Forum Fellow
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 4,734

Re: Files getting corrupted on my SSD after a crash

I have to agree that running out of swap should not cause generalised data corruption, at most only the files opened by the process killed by the OOM killer could get corrupted/damaged. Did you confirm your ram is ok with memtest?


R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#18 2018-01-27 15:24:14

rokidakota
Member
Registered: 2014-11-22
Posts: 40

Re: Files getting corrupted on my SSD after a crash

I did test the RAM and there were no errors.

I saw the corruption happen "almost in real time": I was compiling, ran out of memory, I closed QtCreator. The system was still running, I could change virtual desktops on i3, it was responsive. BUT dmenu was suddenly damaged. I could open dmenu, but as soon as I typed something it closed instead of searching for the program I want to launch. I reinstalled a few packages and dmenu started working fine.

My point is that I did not do a hard shut down this time, kill any processes, nor it became unresponsive. I continued using the computer, eventually restarted, then was greeted with the fsck message announcing broken files, went through reinstalling a bunch of packages to repair the damage, etc.

As long as it does not happen again with the increased swap, I'm ok. But it really feels mysterious.

Now that I remember: the disk has some kind of hardware encryption enabled configured in the bios. I wonder if that is what is failing with high cpu and out of ram situations. I will check if there are firmware updates for this laptop model.

ps. I forgot to point out that the files that get corrupted are owned by root.

Last edited by rokidakota (2018-01-27 15:49:14)

Offline

#19 2018-01-27 16:52:31

R00KIE
Forum Fellow
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 4,734

Re: Files getting corrupted on my SSD after a crash

I would check for firmware updates for the SSD _and_ disable that bios encryption thing. Then I would try to force the problem again, if there are no problem then enable the bios "encryption" and see if you can trigger the problem.


R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#20 2018-02-09 12:05:25

bxabi
Member
Registered: 2018-02-09
Posts: 4

Re: Files getting corrupted on my SSD after a crash

Hi, I have exactly the same problem. Occasionally at boot I get a corrupted file system error, and I have to run manually the fsck.
I found a corrupted file later, where the content of a file I had it a while ago (a jar file which I was probably running), was overwritten with some kind of data from the Eclipse.
Once my grub configuration was corrupted.
In the past I thought it may be because of a hard reset after a crash. But I didn't have that lately.
As the topic opener wrote, I am also suspecting using up my full ram and swap space, this happened 2-3 days ago, but the disk corruption I saw only this morning, and the computer was restarted in the meanwhile.
Hm, I am also using stand-by sometimes. Can that be a cause? (no hibernation).

I checked the drive with smartctl -t long, and has no errors. I will test the RAM too.

Last edited by bxabi (2018-02-09 12:16:56)

Offline

#21 2018-02-09 12:13:40

bxabi
Member
Registered: 2018-02-09
Posts: 4

Re: Files getting corrupted on my SSD after a crash

But this is happening for the 3rd time, so it is worrying. This issue only appears since I switched to Arch from Fedora 1 month ago.

The fsck errors are mostly this type: setting filetype for entry '..' in ??? (inode) to 2.

but there are a couple actual folders corrupted: /var/lib/pacman/local/libgit2-<version>/ (pacman data) became empty during the fsck, I reinstalled that package.

I will laso increase the swap size. (I have 8G Ram +2G swap but sometimes I reach close to this limit).

Offline

#22 2018-02-09 14:17:08

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 78,863

Re: Files getting corrupted on my SSD after a crash

only appears since I switched to Arch from Fedora

This is pretty meaninless w/o details on the kernels and the FS config (same FS?, lvm? crypto?, zswap?, etc...)

Offline

#23 2018-02-10 14:30:25

bxabi
Member
Registered: 2018-02-09
Posts: 4

Re: Files getting corrupted on my SSD after a crash

The system is on a Samsung PRO 850 SSD, on an LVM partition, in the LVM there is the luks encrypted root partition where the problems occured.
I have a second hard drive luks encrypted as well, but as a single partition and not LVM, I had no problems on that one.
The system: Linux 4.15.2-2-ARCH #1 SMP PREEMPT x86_64 GNU/Linux
The EFI partition is FAT16 on the SSD drive, and once I had corruption on this too (needed to reinstall grub). So it seems to effect the whole SSD.
Yesterday I saw that there is a new firmware for the SSD, so I updated it.
Maybe I have to wait and see if the problem occurs again.

Offline

#24 2018-02-10 15:01:10

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 78,863

Re: Files getting corrupted on my SSD after a crash

The most interesting part would be any contrast to the fedora setup, since that would hint to narrow the area of cause.

Offline

#25 2018-02-10 18:45:34

bxabi
Member
Registered: 2018-02-09
Posts: 4

Re: Files getting corrupted on my SSD after a crash

I noticed that the fstab is different (I have a backup of the old Fedora)

The fstab on the current Arch system:

# the mapped luks partition
UUID=5a1bd281-50cd-40c7-8190-6c6e22b0a248	/         	ext4      	rw,relatime,data=ordered	0 1

# /dev/sda2 LABEL=boot
UUID=2b9309ce-92cd-4aae-8e8c-4c40eaaa6b2d	/boot     	ext4      	rw,relatime,data=ordered	0 2

# /dev/sda1 LABEL=EFI
UUID=D529-3745      	/boot/efi 	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro	0 2

The fstab from the old Fedora system:

/dev/mapper/luks-5e9470cd-f0d2-46d4-a594-6a369632264c /                       ext4    defaults,x-systemd.device-timeout=0,noatime 1 1
UUID=2b9309ce-92cd-4aae-8e8c-4c40eaaa6b2d /boot                   ext4    defaults        1 2
UUID=D529-3745          /boot/efi               vfat    umask=0077,shortname=winnt 0 0

Can some of these options be problematic?

Offline

Board footer

Powered by FluxBB