/qubes-issues

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PTE Write access is not set #1710

Closed
TNTBOMBOM opened this Issue Feb 1, 2016 · 7 comments

Comments

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
3 participants
@TNTBOMBOM @marmarek @adrelanos
@TNTBOMBOM

TNTBOMBOM commented Feb 1, 2016

dom0 logs , Qubes 3.1

Xen 4.6.0-12.fc20
(XEN) Xen version 4.6.0 (user@) (gcc (GCC) 4.8.3 20140911 (Red Hat 4.8.3-7)) debug=n Thu Jan 7 06:33:20 UTC 2016
(XEN) Latest ChangeSet:
(XEN) Bootloader: GRUB 2.00
(XEN) Command line: placeholder console=none dom0_mem=min:1024M
(XEN) Video information:
(XEN) VGA is text mode 80x25, font 8x16
(XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds
(XEN) Disc information:
(XEN) Found 1 MBR signatures
(XEN) Found 1 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 000000000009c800 (usable)
(XEN) 000000000009c800 - 00000000000a0000 (reserved)
(XEN) 00000000000e0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 00000000b97fc000 (usable)
(XEN) 00000000b97fc000 - 00000000b9803000 (ACPI NVS)
(XEN) 00000000b9803000 - 00000000ba06e000 (usable)
(XEN) 00000000ba06e000 - 00000000ba2fa000 (reserved)
(XEN) 00000000ba2fa000 - 00000000c98e0000 (usable)
(XEN) 00000000c98e0000 - 00000000c9af7000 (reserved)
(XEN) 00000000c9af7000 - 00000000c9e1c000 (usable)
(XEN) 00000000c9e1c000 - 00000000cab1f000 (ACPI NVS)
(XEN) 00000000cab1f000 - 00000000cafff000 (reserved)
(XEN) 00000000cafff000 - 00000000cb000000 (usable)
(XEN) 00000000cbc00000 - 00000000cfe00000 (reserved)
(XEN) 00000000f8000000 - 00000000fc000000 (reserved)
(XEN) 00000000fec00000 - 00000000fec01000 (reserved)
(XEN) 00000000fed00000 - 00000000fed04000 (reserved)
(XEN) 00000000fed1c000 - 00000000fed20000 (reserved)
(XEN) 00000000fee00000 - 00000000fee01000 (reserved)
(XEN) 00000000ff000000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 000000022f200000 (usable)
(XEN) ACPI: RSDP 000F0490, 0024 (r2 ASUS)
(XEN) ACPI: XSDT C9EA4088, 009C (r1 ASUS Notebook 1072009 AMI 10013)
(XEN) ACPI: FACP C9EB7E58, 010C (r5 ASUS Notebook 1072009 AMI 10013)
(XEN) ACPI: DSDT C9EA4240, 13C16 (r2 ASUS Notebook 12 INTL 20120711)
(XEN) ACPI: FACS CAB1DF80, 0040
(XEN) ACPI: APIC C9EB7F68, 0092 (r3 ASUS Notebook 1072009 AMI 10013)
(XEN) ACPI: FPDT C9EB8000, 0044 (r1 ASUS Notebook 1072009 AMI 10013)
(XEN) ACPI: ECDT C9EB8048, 00C1 (r1 ASUS Notebook 1072009 AMI. 5)
(XEN) ACPI: SSDT C9EB8110, 019D (r1 Intel zpodd 1000 INTL 20120711)
(XEN) ACPI: SSDT C9EB82B0, 0539 (r1 PmRef Cpu0Ist 3000 INTL 20120711)
(XEN) ACPI: SSDT C9EB87F0, 0AD8 (r1 PmRef CpuPm 3000 INTL 20120711)
(XEN) ACPI: MCFG C9EB92C8, 003C (r1 ASUS Notebook 1072009 MSFT 97)
(XEN) ACPI: HPET C9EB9308, 0038 (r1 ASUS Notebook 1072009 AMI. 5)
(XEN) ACPI: SSDT C9EB9340, 0298 (r1 SataRe SataTabl 1000 INTL 20120711)
(XEN) ACPI: SSDT C9EB95D8, 44FA (r1 SaSsdt SaSsdt 3000 INTL 20091112)
(XEN) ACPI: SSDT C9EBDAD8, 17D1 (r1 SgRef SgPeg 1000 INTL 20120711)
(XEN) ACPI: DMAR C9EBF2B0, 00B0 (r1 INTEL HSW 1 INTL 1)
(XEN) ACPI: SSDT C9EBF360, 13ED (r1 OptRef OptTabl 1000 INTL 20120711)
(XEN) ACPI: MSDM C9AF4E18, 0055 (r3 ASUS Notebook 0 ASUS 1)
(XEN) System RAM: 8075MB (8268860kB)
(XEN) Domain heap initialised
(XEN) ACPI: 32/64X FACS address mismatch in FADT - cab1df80/0000000000000000, using 32
(XEN) Processor #0 7:12 APIC version 21
(XEN) Processor #2 7:12 APIC version 21
(XEN) Processor #4 7:12 APIC version 21
(XEN) Processor #6 7:12 APIC version 21
(XEN) Processor #1 7:12 APIC version 21
(XEN) Processor #3 7:12 APIC version 21
(XEN) Processor #5 7:12 APIC version 21
(XEN) Processor #7 7:12 APIC version 21
(XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) Switched to APIC driver x2apic_cluster.
(XEN) xstate_init: using cntxt_size: 0x340 and states: 0x7
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2494.272 MHz processor.
(XEN) Initing memory sharing.
(XEN) spurious 8259A interrupt: IRQ7.
(XEN) Intel VT-d iommu 0 supported page sizes: 4kB.
(XEN) Intel VT-d iommu 1 supported page sizes: 4kB.
(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 not enabled.
(XEN) I/O virtualisation enabled
(XEN) - Dom0 mode: Relaxed
(XEN) Interrupt remapping enabled
(XEN) Enabled directed EOI with ioapic_ack_old on!
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using old ACK method
(XEN) Platform timer is 14.318MHz HPET
(XEN) Allocated console ring of 16 KiB.
(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) - VM Functions
(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 8 CPUs
(XEN) Dom0 has maximum 792 PIRQs
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen kernel: 64-bit, lsb, compat32
(XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x2269000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 0000000220000000->0000000224000000 (1977129 pages to be allocated)
(XEN) Init. ramdisk: 000000022c572000->000000022f200000
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff81000000->ffffffff82269000
(XEN) Init. ramdisk: 0000000000000000->0000000000000000
(XEN) Phys-Mach map: ffffffff82269000->ffffffff831b4db8
(XEN) Start info: ffffffff831b5000->ffffffff831b54b4
(XEN) Page tables: ffffffff831b6000->ffffffff831d3000
(XEN) Boot stack: ffffffff831d3000->ffffffff831d4000
(XEN) TOTAL: ffffffff80000000->ffffffff83400000
(XEN) ENTRY ADDRESS: ffffffff81d341f0
(XEN) Dom0 has maximum 8 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: Errors and warnings
(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 304kB init memory.
(XEN) Bogus DMIBAR 0xfed18001 on 0000:00:00.0
(XEN) [VT-D]DMAR:[DMA Write] Request device [0000:01:00.0] fault addr 8c000, iommu reg = ffff82c000203000
(XEN) [VT-D]DMAR: reason 05 - PTE Write access is not set
(XEN) [VT-D]DMAR:[DMA Write] Request device [0000:01:00.0] fault addr 8c000, iommu reg = ffff82c000203000
(XEN) [VT-D]DMAR: reason 05 - PTE Write access is not set
(XEN) [VT-D]DMAR:[DMA Write] Request device [0000:01:00.0] fault addr 8c000, iommu reg = ffff82c000203000
(XEN) [VT-D]DMAR: reason 05 - PTE Write access is not set
(XEN) [VT-D]DMAR:[DMA Write] Request device [0000:01:00.0] fault addr 8c000, iommu reg = ffff82c000203000
(XEN) [VT-D]DMAR: reason 05 - PTE Write access is not set
(XEN) [VT-D]DMAR:[DMA Write] Request device [0000:01:00.0] fault addr 8c000, iommu reg = ffff82c000203000
(XEN) [VT-D]DMAR: reason 05 - PTE Write access is not set
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 1, 2016

Member

Please send this to qubes-devel mailing list, or even better xen-devel...
Member

marmarek commented Feb 1, 2016

Please send this to qubes-devel mailing list, or even better xen-devel...

@marmarek marmarek closed this Feb 1, 2016

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 1, 2016

Member

Generally it looks like misbehaving device.
Member

marmarek commented Feb 1, 2016

Generally it looks like misbehaving device.
@TNTBOMBOM

This comment has been minimized.

Show comment
Hide comment
@TNTBOMBOM

TNTBOMBOM Feb 1, 2016

i have already reported my whonix design to them as u have suggested , but i just got one answer which is in conclusion " i didnt understand the design" ? so it is dead mailing list but tho i dont know any alternatives so i will report this issue to them

TNTBOMBOM commented Feb 1, 2016

i have already reported my whonix design to them as u have suggested , but i just got one answer which is in conclusion " i didnt understand the design" ? so it is dead mailing list but tho i dont know any alternatives so i will report this issue to them
@adrelanos

This comment has been minimized.

Show comment
Hide comment
@adrelanos

adrelanos Feb 1, 2016

Member

TNT BOM BOM:

i have already reported my whonix design to them as u have suggested , but i just got one answer which is in conclusion " i didnt understand the design" ? so it is dead mailing list but tho i dont know any alternatives so i will report this issue to them

Wrong ticket. (Here was no Whonix design involved.)
Member

adrelanos commented Feb 1, 2016

TNT BOM BOM:

i have already reported my whonix design to them as u have suggested , but i just got one answer which is in conclusion " i didnt understand the design" ? so it is dead mailing list but tho i dont know any alternatives so i will report this issue to them

Wrong ticket. (Here was no Whonix design involved.)
@TNTBOMBOM

This comment has been minimized.

Show comment
Hide comment
@TNTBOMBOM

TNTBOMBOM Feb 1, 2016

Wrong ticket. (Here was no Whonix design involved.)

correct , but i didnt meant whonix specifically , i meant they dont respond to my messages. which is whonix design was the first message to them.

TNTBOMBOM commented Feb 1, 2016

Wrong ticket. (Here was no Whonix design involved.)

correct , but i didnt meant whonix specifically , i meant they dont respond to my messages. which is whonix design was the first message to them.
@adrelanos

This comment has been minimized.

Show comment
Hide comment
@adrelanos

adrelanos Feb 1, 2016

Member

TNT BOM BOM:

Wrong ticket. (Here was no Whonix design involved.)

correct , but i didnt meant whonix specifically , i meant they dont respond to my messages. which is whonix design was the first message to them.

The qubes mailing lists are active enough. See the archives.

The new Whonix design you posted however is difficult to understand. And
if multiple people have issues understanding it, I conclude that it's
more likely not very well understandable by other mortals.

However, the issue in this ticket is simpler. It's not suggesting
something new. It's posting an existing issue. Much easier to grasp.
Existing log files. Existing messages (they have to exist in the source
codes).

Still, there is no insurance. Could still be that no one has a clue and
that posting will be futile. Also happens to me some times...
Member

adrelanos commented Feb 1, 2016

TNT BOM BOM:

Wrong ticket. (Here was no Whonix design involved.)

correct , but i didnt meant whonix specifically , i meant they dont respond to my messages. which is whonix design was the first message to them.

The qubes mailing lists are active enough. See the archives.

The new Whonix design you posted however is difficult to understand. And
if multiple people have issues understanding it, I conclude that it's
more likely not very well understandable by other mortals.

However, the issue in this ticket is simpler. It's not suggesting
something new. It's posting an existing issue. Much easier to grasp.
Existing log files. Existing messages (they have to exist in the source
codes).

Still, there is no insurance. Could still be that no one has a clue and
that posting will be futile. Also happens to me some times...
@TNTBOMBOM

This comment has been minimized.

Show comment
Hide comment
@TNTBOMBOM

TNTBOMBOM Feb 1, 2016

yeah i c , then i need to increase the info and pictures to make it as simple as possible.

thnx for the help.

TNTBOMBOM commented Feb 1, 2016

yeah i c , then i need to increase the info and pictures to make it as simple as possible.

thnx for the help.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment