linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: "David H. Gutteridge" <dhgutteridge@sympatico.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/31 v2] PTI support for x86_32
Date: Tue, 20 Feb 2018 09:40:55 +0100	[thread overview]
Message-ID: <20180220084055.GL16484@8bytes.org> (raw)
In-Reply-To: <1519098356.2973.7.camel@sympatico.ca>

Hi David,

thanks a lot for your testing, much appreciated!

On Mon, Feb 19, 2018 at 10:45:56PM -0500, David H. Gutteridge wrote:
> (1) There is a regression when the QXL display driver is enabled; the
> VM hangs during boot. (QXL has been a source of similar trouble in the
> past.) I don't have an example trace for it at present.
> 
> (2) There is a regression when the VGA display driver is enabled; it
> intermittently (but reproducibly) faults, which makes it impossible
> to boot to the graphical login manager.

Can you please send me the kernel-config used and the qemu command-line
of the VM? I'll try to reproduce this here.

> [   25.439213] kernel BUG at arch/x86/mm/fault.c:268!
> [   25.439218] invalid opcode: 0000 [#1] SMP PTI
> [   25.439218] Modules linked in: bochs_drm(+) ttm snd_hda_core
> drm_kms_helper snd_hwdep drm snd_seq snd_seq_device snd_pcm snd_timer
> snd pcspkr virtio_balloon i2c_piix4 soundcore virtio_console 8139too
> crc32c_intel virtio_pci virtio_ring serio_raw virtio 8139cp ata_generic
> mii pata_acpi floppy qemu_fw_cfg
> [   25.439236] CPU: 1 PID: 545 Comm: systemd-udevd Tainted:
> G        W        4.15.0+ #1
> [   25.439237] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),
> BIOS 1.10.2-1 04/01/2014
> [   25.439241] EIP: vmalloc_fault+0x1e7/0x210
> [   25.439242] EFLAGS: 00010083 CPU: 1
> [   25.439243] EAX: 02788000 EBX: d78ecdf8 ECX: 00000080 EDX: 00000000
> [   25.439244] ESI: 000fd000 EDI: fd0000f3 EBP: f3f639a0 ESP: f3f63988
> [   25.439245]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
> [   25.439246] CR0: 80050033 CR2: f7e00000 CR3: 33e3a000 CR4: 000006f0

This is a kernel-cr3, so that is at least not the issue.


Thanks,

	Joerg

  reply	other threads:[~2018-02-20  8:40 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-20  3:45 [PATCH 00/31 v2] PTI support for x86_32 David H. Gutteridge
2018-02-20  8:40 ` Joerg Roedel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-02-09  9:25 Joerg Roedel
2018-02-09 12:11 ` Juergen Gross
2018-02-09 13:35   ` Joerg Roedel
2018-02-09 13:54     ` Andrew Cooper
2018-02-09 17:47 ` Andy Lutomirski
2018-02-09 19:11   ` Joerg Roedel
2018-02-10  9:15     ` Adam Borowski
2018-02-10 20:22       ` Linus Torvalds
2018-02-11 10:59         ` Adam Borowski
2018-02-11 17:40           ` Mark D Rustad
2018-02-11 19:42             ` Andy Lutomirski
2018-02-11 20:14               ` Linus Torvalds
2018-02-11 22:12               ` James Bottomley
2018-02-11 22:30                 ` Andy Lutomirski
2018-02-11 23:47                   ` James Bottomley
2018-02-11 22:34               ` Pavel Machek
2018-02-11 23:25               ` Alan Cox
2018-02-12 10:16                 ` Anders Larsen
2018-02-14 10:43               ` Pavel Machek
2018-02-13  8:54             ` Greg KH
2018-02-13 17:25               ` Linus Torvalds
2018-02-14  8:54                 ` Greg KH
2018-02-21 10:26                   ` Lorenzo Colitti
2018-02-21 16:59                     ` Arnd Bergmann
2018-02-22 11:10                       ` Greg KH
2018-02-22 11:18                         ` Arnd Bergmann
2018-03-06 15:39                 ` Jason A. Donenfeld
2018-02-11 19:13     ` Ingo Molnar
2018-02-12 14:51       ` Joerg Roedel
2018-02-09 21:09   ` Pavel Machek
2018-02-09 21:11     ` Linus Torvalds
2018-02-09 21:28     ` Andrew Cooper

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180220084055.GL16484@8bytes.org \
    --to=joro@8bytes.org \
    --cc=dhgutteridge@sympatico.ca \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).