From: Jon Smirl <jonsmirl@gmail.com>
To: Rik van Riel <riel@redhat.com>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: vm86 - DCC probes don't work
Date: Tue, 22 Feb 2005 15:18:32 -0500 [thread overview]
Message-ID: <9e4733910502221218c104ebe@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0502221343350.30519@chimarrao.boston.redhat.com>
ddcprobe is trying to read hardware I2C buses. On a radeon card these
are part of the mmio address space. Not sure where they appear on the
i915 but it should be easy to find in the source.
On Tue, 22 Feb 2005 13:45:31 -0500 (EST), Rik van Riel <riel@redhat.com> wrote:
> After digging around a bit on a system that hangs when trying to
> start X, I tried another system and was luckier, when running
> system-config-display:
>
> do_wp_page: bogus page at address 00000449
> VM: killing process ddcprobe
> PCI: Obtained IRQ 16 for device 0000:00:02.0
> [drm] Initialized i915 1.1.0 20040405 on minor 0:
> do_wp_page: bogus page at address 00000449
> VM: killing process ddcprobe
>
> I guess some of our low physical memory mappings in domain 0
> aren't complete ?
>
> X did start, btw ...
>
> --
> "Debugging is twice as hard as writing the code in the first place.
> Therefore, if you write the code as cleverly as possible, you are,
> by definition, not smart enough to debug it." - Brian W. Kernighan
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
>
--
Jon Smirl
jonsmirl@gmail.com
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-02-22 20:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 18:45 vm86 - DCC probes don't work Rik van Riel
2005-02-22 20:18 ` Jon Smirl [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-22 22:25 Ian Pratt
2005-02-22 22:31 ` Rik van Riel
2005-02-22 22:54 ` Jon Smirl
2005-02-22 22:59 Ian Pratt
2005-02-22 23:38 ` Jon Smirl
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=9e4733910502221218c104ebe@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=riel@redhat.com \
--cc=xen-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.