From: Bastian Blank <waldi@debian.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>, xen-devel@lists.xensource.com
Subject: pvops: i915 kms crashs with corrupt page table
Date: Wed, 24 Feb 2010 18:55:56 +0100 [thread overview]
Message-ID: <20100224175555.GA6353@wavehammer.waldi.eu.org> (raw)
Hi
I run a 2.6.32 dom0 kernel (the Debian distribution config). If I enable
KMS in the intel driver, Xorg crashs with corrupt page table.
| Xorg: Corrupted page table at address 7fd9e2f86000
| PGD 745d0067 PUD 74d1f067 PMD 72cae067 PTE fffffffffffff22f
| Bad pagetable: 000f [#1] SMP
| last sysfs file: /sys/devices/virtual/backlight/acpi_video0/brightness
| CPU 0
| Modules linked in: i915 drm_kms_helper xen_evtchn xenfs bridge stp firewire_sbp2 loop dm_snapshot snd_hda_codec_analog ide_cs arc4 snd_hda_intel snd_hda_codec snd_hwdep ecb snd_pcm snd_timer joydev snd hp_accel lis3lv02d parport_pc pcmcia irda soundcore parport tpm_infineon iwlagn yenta_socket tpm rsrc_nonstatic container evdev input_polldev crc_ccitt iwlcore ac snd_page_alloc pcspkr tpm_bios pcmcia_core wmi battery mac80211 processor cfg80211 rfkill serio_raw psmouse ext3 jbd mbcache dm_mod sd_mod crc_t10dif ide_cd_mod cdrom ata_generic uhci_hcd ide_pci_generic ahci sdhci_pci sdhci ricoh_mmc firewire_ohci firewire_core crc_itu_t mmc_core led_class intel_agp drm i2c_algo_bit button i2c_core video output e1000e libata scsi_mod ehci_hcd piix ide_core usbcore nls_base thermal fan thermal_sys [last unloaded: drm_kms_helper]
| Pid: 1955, comm: Xorg Not tainted 2.6.32-3-xen-amd64 #1 HP Compaq 6910p
| RIP: e033:[<00007fd9e34dc0a0>] [<00007fd9e34dc0a0>] 0x7fd9e34dc0a0
| RSP: e02b:00007fff0525abf8 EFLAGS: 00010246
| RAX: 0000000000000010 RBX: 00007fd9e2f86000 RCX: 0000000000000000
| RDX: 00000000ffff0000 RSI: 00000000ffffffff RDI: 000000000000ffff
| RBP: 0000000000000000 R08: 00007fd9e2f86000 R09: 0000000000000000
| R10: 0000000000000000 R11: 0000000000000002 R12: 0000000000000000
| R13: 0000000000000040 R14: 0000000400000000 R15: 0000000400000000
| FS: 00007fd9e786a790(0000) GS:ffff88000342f000(0000) knlGS:0000000000000000
| CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b
| CR2: 00007fd9e2f86000 CR3: 0000000002b52000 CR4: 0000000000002660
| DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
| DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
| Process Xorg (pid: 1955, threadinfo ffff880001f2a000, task ffff880001e28e20)
|
| RIP [<00007fd9e34dc0a0>] 0x7fd9e34dc0a0
| RSP <00007fff0525abf8>
| ---[ end trace 8b2c5cb2c5b589cc ]---
Bastian
--
There are always alternatives.
-- Spock, "The Galileo Seven", stardate 2822.3
next reply other threads:[~2010-02-24 17:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 17:55 Bastian Blank [this message]
2010-02-24 19:23 ` pvops: i915 kms crashs with corrupt page table Jeremy Fitzhardinge
2010-02-25 10:06 ` Bastian Blank
2010-02-25 10:32 ` Bastian Blank
2010-02-26 0:37 ` Jeremy Fitzhardinge
2010-02-26 12:44 ` Bastian Blank
2010-02-26 17:29 ` Jeremy Fitzhardinge
[not found] ` <20100226180545.GC21871@wavehammer.waldi.eu.org>
[not found] ` <4B880EC0.8000803@goop.org>
2010-02-27 0:45 ` Bastian Blank
2010-02-27 1:17 ` Jeremy Fitzhardinge
2010-02-28 12:27 ` Bastian Blank
2010-03-01 8:43 ` Ian Campbell
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=20100224175555.GA6353@wavehammer.waldi.eu.org \
--to=waldi@debian.org \
--cc=jeremy@goop.org \
--cc=xen-devel@lists.xensource.com \
/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).