Frequent 3.2 crashes , How to troubleshoot?

[yre...@riseup.net]

Hello, I've had a stable system for >6 months, but in the last month,
I'd say I've had 4-6 total crashes, where the machine reboots itself ,
then maybe 2-4 crashes where the system doesn't reboot, but closes all
VMs and asks me to re-login .....

The last machine reboot was after initiating a Fedora-25 update ; I have
16GB of RAM, but am always up against the max RAM allowed , and have to
close VMs to open others etc
Is there a particular log item I can post or look for to explain or
maybe fix this? Or maybe it will just fix itself eventually ? Kind
of annoying to have to re-open and set up my VMs over and over more
than I already do .....

[awokd]

On Fri, January 5, 2018 6:54 pm, yre...@riseup.net wrote:
> Hello, I've had a stable system for >6 months, but in the last month,
> I'd say I've had 4-6 total crashes, where the machine reboots itself ,
> then maybe 2-4 crashes where the system doesn't reboot, but closes all
> VMs and asks me to re-login .....

Look in "xl dmesg" for memory balancing errors. You might need to add
loglvl=all to your Xen command line.

[yre...@riseup.net]

On 01/05/2018 01:35 PM, 'awokd' via qubes-users wrote:

> On Fri, January 5, 2018 6:54 pm, yrebstv-sGOZH3h...@public.gmane.org wrote:
>> Hello, I've had a stable system for >6 months, but in the last month,
>> I'd say I've had 4-6 total crashes, where the machine reboots itself ,
>> then maybe 2-4 crashes where the system doesn't reboot, but closes all
>> VMs and asks me to re-login .....
>
> Look in "xl dmesg" for memory balancing errors. You might need to add
> loglvl=all to your Xen command line.
>

1)
Thanks for responding. I have always have these ACPI complaints when I
boot, it may have grown to about 5-6 lines, but flashes by and continues
to boot, FWIW.

2) Below, is what a "memory balancing error" might look like? If so ,
what , if anything in the BIOS or elsewhere would you advise ??

3)
Meanwhile. Please excuse the long post below of

$xl dmesg (actually I used the copy from dom0 log feature)

--
(XEN) [VT-D]DMAR:[DMA Write] Request device [0000:04:00.0] fault addr
fff00000, iommu reg = ffff82c0009f4000
(XEN) [VT-D]DMAR: reason 05 - PTE Write access is not set
(XEN) [VT-D]DMAR:[DMA Write] Request device [0000:04:00.0] fault addr
fff00000, iommu reg = ffff82c0009f4000
(XEN) [VT-D]DMAR: reason 05 - PTE Write access is not set
(XEN) [VT-D]DMAR:[DMA Write] Request device [0000:04:00.0] fault addr
fff00000, iommu reg = ffff82c0009f4000
(XEN) [VT-D]DMAR: reason 05 - PTE Write access is not set
(XEN) [VT-D]DMAR:[DMA Write] Request device [0000:04:00.0] fault addr
fff00000, iommu reg = ffff82c0009f4000

(XEN) [VT-D]DMAR: reason 05 - PTE Write access is not set
(XEN) [VT-D]DMAR:[DMA Write] Request device [0000:04:00.0] fault addr
fff00000, iommu reg = ffff82c0009f4000
(XEN) [VT-D]DMAR: reason 05 - PTE Write access is not set
(XEN) [VT-D]DMAR:[DMA Write] Request device [0000:04:00.0] fault addr
fff00000, iommu reg = ffff82c0009f4000
(XEN) [VT-D]DMAR: reason 05 - PTE Write access is not set
(XEN) [VT-D]DMAR:[DMA Write] Request device [0000:04:00.0] fault addr
fff00000, iommu reg = ffff82c0009f4000
(XEN) [VT-D]DMAR: reason 05 - PTE Write access is not set
(XEN) [VT-D]DMAR:[DMA Write] Request device [0000:04:00.0] fault addr
fff00000, iommu reg = ffff82c0009f4000
(XEN) [VT-D]DMAR: reason 05 - PTE Write access is not set
Xen 4.6.6-35.fc23
(XEN) Xen version 4.6.6 (user@[unknown]) (gcc (GCC) 5.3.1 20160406 (Red
Hat 5.3.1-6)) debug=n Tue Nov 28 12:59:56 UTC 2017
(XEN) Latest ChangeSet:
(XEN) Bootloader: EFI
(XEN) Command line: loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M
(XEN) Video information:
(XEN) VGA is graphics mode 1920x1080, 32 bpp
(XEN) Disc information:
(XEN) Found 0 MBR signatures
(XEN) Found 2 EDD information structures
(XEN) EFI RAM map:
(XEN) 0000000000000000 - 0000000000058000 (usable)
(XEN) 0000000000058000 - 0000000000059000 (reserved)
(XEN) 0000000000059000 - 000000000009f000 (usable)
(XEN) 000000000009f000 - 00000000000a0000 (reserved)
(XEN) 0000000000100000 - 000000005cec8000 (usable)
(XEN) 000000005cec8000 - 000000005cec9000 (ACPI NVS)
(XEN) 000000005cec9000 - 000000005cef3000 (reserved)
(XEN) 000000005cef3000 - 000000005cf43000 (usable)
(XEN) 000000005cf43000 - 000000005dc64000 (reserved)
(XEN) 000000005dc64000 - 0000000076e59000 (usable)
(XEN) 0000000076e59000 - 00000000777b2000 (reserved)
(XEN) 00000000777b2000 - 0000000077f99000 (ACPI NVS)
(XEN) 0000000077f99000 - 0000000077ffe000 (ACPI data)
(XEN) 0000000077ffe000 - 0000000077fff000 (usable)
(XEN) 0000000078000000 - 0000000078100000 (reserved)
(XEN) 00000000e0000000 - 00000000f0000000 (reserved)
(XEN) 00000000fe000000 - 00000000fe011000 (reserved)
(XEN) 00000000fec00000 - 00000000fec01000 (reserved)
(XEN) 00000000fee00000 - 00000000fee01000 (reserved)
(XEN) 00000000ff000000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 0000000476000000 (usable)
(XEN) ACPI: RSDP 77F30000, 0024 (r2 ALASKA)
(XEN) ACPI: XSDT 77F300A0, 00C4 (r1 ALASKA A M I 1072009 AMI
10013)
(XEN) ACPI: FACP 77F51188, 010C (r5 ALASKA A M I 1072009 AMI
10013)
(XEN) ACPI: DSDT 77F30200, 20F88 (r2 ALASKA A M I 1072009 INTL
20120913)
(XEN) ACPI: FACS 77F98F80, 0040
(XEN) ACPI: APIC 77F51298, 0084 (r3 ALASKA A M I 1072009 AMI
10013)
(XEN) ACPI: FPDT 77F51320, 0044 (r1 ALASKA A M I 1072009 AMI
10013)
(XEN) ACPI: FIDT 77F51368, 009C (r1 ALASKA A M I 1072009 AMI
10013)
(XEN) ACPI: MCFG 77F51408, 003C (r1 ALASKA A M I 1072009 MSFT
97)
(XEN) ACPI: HPET 77F51448, 0038 (r1 ALASKA A M I 1072009 AMI.
5000B)
(XEN) ACPI: SSDT 77F51480, 036D (r1 SataRe SataTabl 1000 INTL
20120913)
(XEN) ACPI: LPIT 77F517F0, 0094 (r1 INTEL SKL 0 MSFT
5F)
(XEN) ACPI: SSDT 77F51888, 002B (r2 INTEL UsbCTabl 1000 INTL
20120913)
(XEN) ACPI: DBGP 77F518B8, 0034 (r1 INTEL 0 MSFT
5F)
(XEN) ACPI: DBG2 77F518F0, 0054 (r0 INTEL 0 MSFT
5F)
(XEN) ACPI: SSDT 77F51948, 0616 (r2 INTEL xh_rvp08 0 INTL
20120913)
(XEN) ACPI: AAFT 77F51F60, 029F (r1 ALASKA OEMAAFT 1072009 MSFT
97)
(XEN) ACPI: SSDT 77F52200, 5212 (r2 SaSsdt SaSsdt 3000 INTL
20120913)
(XEN) ACPI: UEFI 77F57418, 0042 (r1 0
0)
(XEN) ACPI: SSDT 77F57460, 0E58 (r2 CpuRef CpuSsdt 3000 INTL
20120913)
(XEN) ACPI: BGRT 77F582B8, 0038 (r1 ALASKA A M I 1072009 AMI
10013)
(XEN) ACPI: DMAR 77F582F0, 00A8 (r1 INTEL SKL 1 INTL
1)
(XEN) ACPI: TPM2 77F58398, 0034 (r3 Tpm2Tabl 1 AMI
0)
(XEN) ACPI: ASF! 77F583D0, 00A5 (r32 INTEL HCG 1 TFSM
F4240)
(XEN) System RAM: 16064MB (16450224kB)
(XEN) No NUMA configuration found
(XEN) Faking a node at 0000000000000000-0000000476000000
(XEN) Domain heap initialised
(XEN) vesafb: framebuffer at 0xc0000000, mapped to 0xffff82c000201000,
using 8128k, total 8128k
(XEN) vesafb: mode is 1920x1080x32, linelength=7680, font 8x16
(XEN) vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
(XEN) Couldn't initialize a 1920x1080 framebuffer early.
(XEN) SMBIOS 2.8 present.
(XEN) DMI 2.8 present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x1808
(XEN) ACPI: v5 SLEEP INFO: control[1:1804], status[1:1800]
(XEN) ACPI: Invalid sleep control/status register data: 0:0x8:0x3
0:0x8:0x3
(XEN) ACPI: SLEEP INFO: pm1x_cnt[1:1804,1:0], pm1x_evt[1:1800,1:0]
(XEN) ACPI: 32/64X FACS address mismatch in FADT -
77f98f80/0000000000000000, using 32
(XEN) ACPI: wakeup_vec[77f98f8c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
(XEN) Processor #2 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
(XEN) Processor #4 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)
(XEN) Processor #6 7:14 APIC version 21
(XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
(XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-119
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) ACPI: HPET id: 0x8086a701 base: 0xfed00000
(XEN) [VT-D] RMRR address range 78800000..88ffffff not in reserved
memory; need "iommu_inclusive_mapping=1"?
(XEN) ERST table was not found
(XEN) ACPI: BGRT: invalidating v1 image at 0x74f46018
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) SMP: Allowing 4 CPUs (0 hotplug CPUs)
(XEN) IRQ limits: 120 GSI, 840 MSI/MSI-X
(XEN) Not enabling x2APIC (upon firmware request)
(XEN) xstate_init: using cntxt_size: 0x440 and states: 0x1f
(XEN) Intel machine check reporting enabled
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 3192.042 MHz processor.
(XEN) EFI memory map:
(XEN) 0000000000000-0000000007fff type=3 attr=000000000000000f
(XEN) 0000000008000-0000000057fff type=7 attr=000000000000000f
(XEN) 0000000058000-0000000058fff type=0 attr=000000000000000f
(XEN) 0000000059000-000000005bfff type=7 attr=000000000000000f
(XEN) 000000005c000-000000005efff type=2 attr=000000000000000f
(XEN) 000000005f000-000000005ffff type=4 attr=000000000000000f
(XEN) 0000000060000-000000009efff type=3 attr=000000000000000f
(XEN) 000000009f000-000000009ffff type=0 attr=000000000000000f
(XEN) 0000000100000-000003dc7bfff type=7 attr=000000000000000f
(XEN) 000003dc7c000-000003dcbbfff type=4 attr=000000000000000f
(XEN) 000003dcbc000-00000594d3fff type=7 attr=000000000000000f
(XEN) 00000594d4000-000005ad97fff type=2 attr=000000000000000f
(XEN) 000005ad98000-000005bf97fff type=1 attr=000000000000000f
(XEN) 000005bf98000-000005cec7fff type=4 attr=000000000000000f
(XEN) 000005cec8000-000005cec8fff type=10 attr=000000000000000f
(XEN) 000005cec9000-000005cef2fff type=6 attr=800000000000000f
(XEN) 000005cef3000-000005cf42fff type=4 attr=000000000000000f
(XEN) 000005cf43000-000005dc63fff type=6 attr=800000000000000f
(XEN) 000005dc64000-000005dc6bfff type=4 attr=000000000000000f
(XEN) 000005dc6c000-0000074325fff type=7 attr=000000000000000f
(XEN) 0000074326000-0000076858fff type=4 attr=000000000000000f
(XEN) 0000076859000-00000769c9fff type=7 attr=000000000000000f
(XEN) 00000769ca000-0000076e58fff type=3 attr=000000000000000f
(XEN) 0000076e59000-0000076eaffff type=5 attr=800000000000000f
(XEN) 0000076eb0000-00000773affff type=6 attr=800000000000000f
(XEN) 00000773b0000-00000777b1fff type=0 attr=000000000000000f
(XEN) 00000777b2000-0000077f98fff type=10 attr=000000000000000f
(XEN) 0000077f99000-0000077ffdfff type=9 attr=000000000000000f
(XEN) 0000077ffe000-0000077ffefff type=4 attr=000000000000000f
(XEN) 0000100000000-0000475ffffff type=7 attr=000000000000000f
(XEN) 0000078000000-00000780fffff type=0 attr=0000000000000000
(XEN) Unknown cachability for MFNs 0x78000-0x780ff
(XEN) 00000e0000000-00000efffffff type=11 attr=8000000000000001
(XEN) 00000fe000000-00000fe010fff type=11 attr=8000000000000001
(XEN) 00000fec00000-00000fec00fff type=11 attr=8000000000000001
(XEN) 00000fee00000-00000fee00fff type=11 attr=8000000000000001
(XEN) 00000ff000000-00000ffffffff type=11 attr=8000000000000001
(XEN) Initing memory sharing.
(XEN) alt table ffff82d0802c9cd0 -> ffff82d0802cb188
(XEN) spurious 8259A interrupt: IRQ7.
(XEN) PCI: MCFG configuration 0: base e0000000 segment 0000 buses 00 -
ff
(XEN) PCI: MCFG area at e0000000 reserved in E820
(XEN) PCI: Using MCFG for segment 0000 bus 00-ff
(XEN) Intel VT-d iommu 0 supported page sizes: 4kB, 2MB, 1GB.
(XEN) Intel VT-d iommu 1 supported page sizes: 4kB, 2MB, 1GB.
(XEN) Intel VT-d Snoop Control not enabled.
(XEN) Intel VT-d Dom0 DMA Passthrough not enabled.
(XEN) Intel VT-d Queued Invalidation enabled.
(XEN) Intel VT-d Interrupt Remapping enabled.
(XEN) Intel VT-d Shared EPT tables enabled.
(XEN) I/O virtualisation enabled
(XEN) - Dom0 mode: Relaxed
(XEN) Interrupt remapping enabled
(XEN) nr_sockets: 2
(XEN) Enabled directed EOI with ioapic_ack_old on!
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using old ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=0 pin2=0
(XEN) TSC deadline timer enabled
(XEN) Platform timer appears to have unexpectedly wrapped 10 or more
times.
(XEN) Platform timer is 23.999MHz HPET
(XEN) Allocated console ring of 32 KiB.
(XEN) mwait-idle: does not run on family 6 model 94
(XEN) VMX: Supported advanced features:
(XEN) - APIC MMIO access virtualisation
(XEN) - APIC TPR shadow
(XEN) - Extended Page Tables (EPT)
(XEN) - Virtual-Processor Identifiers (VPID)
(XEN) - Virtual NMI
(XEN) - MSR direct-access bitmap
(XEN) - Unrestricted Guest
(XEN) - VMCS shadowing
(XEN) - VM Functions
(XEN) - Virtualisation Exceptions
(XEN) HVM: ASIDs enabled.
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assisted Paging (HAP) detected
(XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB
(XEN) Brought up 4 CPUs
(XEN) ACPI sleep modes: S3
(XEN) VPMU: disabled
(XEN) mcheck_poll: Machine check polling timer started.
(XEN) Dom0 has maximum 696 PIRQs
(XEN) NX (Execute Disable) protection active
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen kernel: 64-bit, lsb, compat32
(XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x20d2000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 0000000460000000->0000000464000000 (1027148 pages
to be allocated)
(XEN) Init. ramdisk: 0000000474c4c000->0000000475fffeb1
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff81000000->ffffffff820d2000
(XEN) Init. ramdisk: 0000000000000000->0000000000000000
(XEN) Phys-Mach map: 0000008000000000->0000008000800000
(XEN) Start info: ffffffff820d2000->ffffffff820d24b4
(XEN) Page tables: ffffffff820d3000->ffffffff820e8000
(XEN) Boot stack: ffffffff820e8000->ffffffff820e9000
(XEN) TOTAL: ffffffff80000000->ffffffff82400000
(XEN) ENTRY ADDRESS: ffffffff81d7b180
(XEN) Dom0 has maximum 4 VCPUs
(XEN) Bogus DMIBAR 0xfed18001 on 0000:00:00.0
(XEN) Scrubbing Free RAM on 1 nodes using 4 CPUs
(XEN) ....................................done.
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
input to Xen)
(XEN) Freed 324kB init memory.
(XEN) Bogus DMIBAR 0xfed18001 on 0000:00:00.0
(XEN) PCI add device 0000:00:00.0
(XEN) PCI add device 0000:00:02.0
(XEN) PCI add device 0000:00:14.0
(XEN) PCI add device 0000:00:14.2
(XEN) PCI add device 0000:00:16.0
(XEN) PCI add device 0000:00:17.0
(XEN) PCI add device 0000:00:1c.0
(XEN) PCI add device 0000:00:1d.0
(XEN) PCI add device 0000:00:1d.3
(XEN) PCI add device 0000:00:1d.7
(XEN) PCI add device 0000:00:1f.0
(XEN) PCI add device 0000:00:1f.2
(XEN) PCI add device 0000:00:1f.3
(XEN) PCI add device 0000:00:1f.4
(XEN) PCI add device 0000:00:1f.6
(XEN) PCI add device 0000:03:00.0
(XEN) PCI add device 0000:04:00.0
(XEN) Monitor-Mwait will be used to enter C1 state
(XEN) Monitor-Mwait will be used to enter C2 state
(XEN) Monitor-Mwait will be used to enter C3 state
(XEN) No CPU ID for APIC ID 0x5
(XEN) Preparing system for ACPI S3 state.
(XEN) Disabling non-boot CPUs ...
(XEN) Broke affinity for irq 1
(XEN) Broke affinity for irq 8
(XEN) Broke affinity for irq 9
(XEN) Broke affinity for irq 19
(XEN) Broke affinity for irq 126
(XEN) Broke affinity for irq 127
(XEN) Broke affinity for irq 128
(XEN) Broke affinity for irq 132
(XEN) Entering ACPI S3 state.
(XEN) CPU0 CMCI LVT vector (0xf1) already installed
(XEN) Finishing wakeup from ACPI S3 state.
(XEN) Enabling non-boot CPUs ...
(XEN) [VT-D]DMAR:[DMA Write] Request device [0000:04:00.0] fault addr
fff00000, iommu reg = ffff82c0009f4000
(XEN) [VT-D]DMAR: reason 05 - PTE Write access is not set
(XEN) [VT-D]DMAR:[DMA Write] Request device [0000:04:00.0] fault addr
fff00000, iommu reg = ffff82c0009f4000
(XEN) [VT-D]DMAR: reason 05 - PTE Write access is not set
(XEN) [VT-D]DMAR:[DMA Write] Request device [0000:04:00.0] fault addr
fff00000, iommu reg = ffff82c0009f4000
(XEN) [VT-D]DMAR: reason 05 - PTE Write access is not set
(XEN) [VT-D]DMAR:[DMA Write] Request device [0000:04:00.0] fault addr
fff00000, iommu reg = ffff82c0009f4000
(XEN) [VT-D]DMAR: reason 05 - PTE Write access is not set
(XEN) [VT-D]DMAR:[DMA Write] Request device [0000:04:00.0] fault addr
fff00000, iommu reg = ffff82c0009f4000
(XEN) [VT-D]DMAR: reason 05 - PTE Write access is not set
(XEN) [VT-D]DMAR:[DMA Write] Request device [0000:04:00.0] fault addr
fff00000, iommu reg = ffff82c0009f4000
(XEN) [VT-D]DMAR: reason 05 - PTE Write access is not set
(XEN) [VT-D]DMAR:[DMA Write] Request device [0000:04:00.0] fault addr
fff00000, iommu reg = ffff82c0009f4000
(XEN) [VT-D]DMAR: reason 05 - PTE Write access is not set
(XEN) [VT-D]DMAR:[DMA Write] Request device [0000:04:00.0] fault addr
fff00000, iommu reg = ffff82c0009f4000
(XEN) [VT-D]DMAR: reason 05 - PTE Write access is not set
(XEN) [VT-D]DMAR:[DMA Write] Request device [0000:04:00.0] fault addr
fff00000, iommu reg = ffff82c0009f4000
(XEN) [VT-D]DMAR: reason 05 - PTE Write access is not set
(XEN) [VT-D]DMAR:[DMA Write] Request device [0000:04:00.0] fault addr
fff00000, iommu reg = ffff82c0009f4000
(XEN) [VT-D]DMAR: reason 05 - PTE Write access is not set
(XEN) [VT-D]DMAR:[DMA Write] Request device [0000:04:00.0] fault addr
fff00000, iommu reg = ffff82c0009f4000
(XEN) [VT-D]DMAR: reason 05 - PTE Write access is not set


......repeat another 300 times :)

[awokd]

On Sat, January 6, 2018 12:14 am, yre...@riseup.net wrote:
> (XEN) [VT-D]DMAR:[DMA Write] Request device [0000:04:00.0] fault addr
> fff00000, iommu reg = ffff82c0009f4000 (XEN) [VT-D]DMAR: reason 05 - PTE
> Write access is not set
>
>
>
> ......repeat another 300 times :)

I'm not seeing any of the memory balancing log messages I was expecting,
maybe they aren't listed there in 3.2? I'll check on my system later.

Is it possible to remove or disable device 04:00.0 for a while to see if
that's causing your issue? I'm guessing it's an Ethernet card. You can
check with "lspci".

"sudo journalctl -b" might also give you some clues.

[yre...@riseup.net]

Hi *yes, 04:00.0 is :

00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2)
I219-V (rev 31)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)

04:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821AE
802.11ac PCIe Wireless Network Adapter

Despite not using the Wireless, once in a while it pops up asking me if
I want to connect , and I just close the window. I'm really not sure, if
there is a better way to "disable" it, or if that explains the entry
above ?

ok, I'll wait to hear back on which log.....

[awokd]

On Sat, January 6, 2018 4:06 am, yre...@riseup.net wrote:

> Despite not using the Wireless, once in a while it pops up asking me if
> I want to connect , and I just close the window. I'm really not sure, if
> there is a better way to "disable" it, or if that explains the entry
> above ?

Unless that helped with the crashes, go ahead and keep using wireless. I
think this is actually what you are hitting:
https://github.com/QubesOS/qubes-issues/issues/3079. You can see if it's
the same issue by doing a "sudo journalctl" after a crash and looking for
those messages about oom-killer.

[yre...@riseup.net]

I browsed through that URL and did this on my system:

[quser4@dom0 Desktop]$ journalctl|grep oom
Dec 27 21:11:28 dom0 kernel: Xorg invoked oom-killer:
gfp_mask=0x240c0d0(GFP_TEMPORARY|__GFP_COMP|__GFP_ZERO), nodemask=0,
order=3, oom_score_adj=0
Dec 27 21:11:28 dom0 kernel: [<ffffffff811b8939>]
oom_kill_process+0x219/0x3e0
Dec 27 21:11:28 dom0 kernel: [ pid ] uid tgid total_vm rss
nr_ptes nr_pmds swapents oom_score_adj name
Dec 27 21:11:28 dom0 kernel: oom_reaper: reaped process 5560 (Xorg), now
anon-rss:0kB, file-rss:0kB, shmem-rss:270816kB
Jan 03 12:25:17 dom0 kernel: Xorg invoked oom-killer:
gfp_mask=0x240c0d0(GFP_TEMPORARY|__GFP_COMP|__GFP_ZERO), nodemask=0,
order=3, oom_score_adj=0
Jan 03 12:25:17 dom0 kernel: [<ffffffff811b8939>]
oom_kill_process+0x219/0x3e0
Jan 03 12:25:17 dom0 kernel: [ pid ] uid tgid total_vm rss
nr_ptes nr_pmds swapents oom_score_adj name
Jan 03 12:25:17 dom0 kernel: oom_reaper: reaped process 5545 (Xorg), now
anon-rss:0kB, file-rss:0kB, shmem-rss:422640kB

The "OOM" bug, as I read it on the URL, seems to indicate only that "X"
crashes, in my case more often the whole system has rebooted, but
perhaps the OOM could also cause that?

Plus "grep" seems to find only 2 entries , and I've had many such
crashes :)

[awokd]

On Sat, January 6, 2018 5:32 pm, yre...@riseup.net wrote:

>
> The "OOM" bug, as I read it on the URL, seems to indicate only that "X"
> crashes, in my case more often the whole system has rebooted, but perhaps
> the OOM could also cause that?
>
> Plus "grep" seems to find only 2 entries , and I've had many such
> crashes :)

Look through that journalctl log manually and try to find more crashes.
Might be something else besides OOM causing them too. Also, look through
/var/log/xen/console/hypervisor.log for crash messages.

[yre...@riseup.net]

sadly, it being in dom0 complicates that, as journalctl is so huge ;
besides |more and |less any other suggestions on examining logs in
dom0?

or particular terms to grep ? "crash" didn't seem to do much :)

[tezeb]

Judging by the end result(crash) and the fact that my Qubes has worked
well until recently I believe that I am hitting the same issue as you
do. I don't have any "oom" logs in journalctl, but I had seen few
crashes recently.


The last lines before "-- Reboot --" in journalctl is, but that does not
repeat earlier so I doubt it's the issue:

Jan 06 20:15:03 dom0 block-cleaner-daemon.py[2759]: libxl: error:
libxl_device.c:369:libxl__device_disk_set_backend: no suitable backend
for disk xvdd
Jan 06 20:15:03 dom0 block-cleaner-daemon.py[2759]:
libxl_device_disk_remove failed.
Jan 06 20:15:04 dom0 block-cleaner-daemon.py[2759]: libxl: error:
libxl_device.c:369:libxl__device_disk_set_backend: no suitable backend
for disk xvdc
Jan 06 20:15:04 dom0 block-cleaner-daemon.py[2759]:
libxl_device_disk_remove failed.