From: Jon Smirl <jonsmirl@gmail.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: fbdev <linux-fbdev-devel@lists.sourceforge.net>,
Xserver development <xorg@freedesktop.org>
Subject: Re: Who is stomping PCI config space?
Date: Thu, 3 Mar 2005 19:15:06 -0500 [thread overview]
Message-ID: <9e473391050303161559c17955@mail.gmail.com> (raw)
In-Reply-To: <1109891245.5611.246.camel@gaston>
My understanding of the X source code is limited, can anyone tell me
where X is turning off secondary cards on VT switch?
The patch looks like it keeps X from getting secondary cards onto the
list of cards to begin with.
Can anyone explain why X is disabling cards on VT switch that it does
not have drivers loaded for? This behavior just toasts my fbdev
driver. My driver is getting interrupts, now I switch VTs to X and the
card's MMIO window disappears. Of course my driver messes up, it go
into a hard loop servicing an interrupt it can't acknowledge.
On Fri, 04 Mar 2005 10:07:25 +1100, Benjamin Herrenschmidt
<benh@kernel.crashing.org> wrote:
> On Thu, 2005-03-03 at 14:03 -0500, Jon Smirl wrote:
> > I have two video cards:
> > PCI Rage128
> > AGP Radeon
> >
> > X is loaded on the Rage128 on VT7
> > X is not configured to support the radeon
> >
> > I switch to VT1 and load radeonfb
> > This works fine.
> >
> > Now I switch to VT7 and dump PCI config space for the radeon
> >
> > [root@jonsmirl 0000:01:00.0]# hexdump config >/foo
> > [root@jonsmirl 0000:01:00.0]# diff /foo /bar
> > 1c1
> > < 0000000 1002 4966 0080 02b0 0001 0300 4010 0080
> > ---
> > > 0000000 1002 4966 0083 02b0 0001 0300 4010 0080
> > 4c4
> > < 0000030 0000 fea0 0058 0000 0000 0000 010b 0008
> > ---
> > > 0000030 0000 fe90 0058 0000 0000 0000 010b 0008
> > [root@jonsmirl 0000:01:00.0]#
> >
> > Somebody is changing PCI command from 83 to 80 and disabling my
> > radeon's memory and iospace. Who is doing this? It has to be X since
> > it doesn't happen if I switch to VT6 or VT8.
> >
> > Why is X mucking with a card it doesn't have a driver loaded for?
> > Where is this happening in the X code?
>
> I had a report of something similar with X and a mach64 ... I haven't
> yet investigated, but basically, X is using "fbdev" (so no specific
> driver) and seem to be disabling memory access to the card, thus blowing
> up the kernel fbdev.
>
> Ben.
>
>
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2005-03-04 0:15 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 19:03 Who is stomping PCI config space? Jon Smirl
2005-03-03 23:07 ` Benjamin Herrenschmidt
2005-03-04 0:15 ` Jon Smirl [this message]
2005-03-04 3:03 ` Jon Smirl
2005-03-04 6:40 ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2005-03-04 12:07 ` Egbert Eich
2005-03-04 17:35 ` Jon Smirl
2005-03-04 22:42 ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2005-03-05 19:06 ` Egbert Eich
2005-03-05 22:42 ` Benjamin Herrenschmidt
2005-03-07 11:19 ` Egbert Eich
2005-03-08 3:21 ` Benjamin Herrenschmidt
2005-03-05 17:33 ` Egbert Eich
2005-03-04 17:58 ` Jon Smirl
2005-03-04 22:45 ` Benjamin Herrenschmidt
2005-03-05 19:07 ` Egbert Eich
2005-03-05 22:43 ` Benjamin Herrenschmidt
2005-03-04 22:27 ` Benjamin Herrenschmidt
2005-03-05 18:26 ` Egbert Eich
2005-03-05 22:39 ` Benjamin Herrenschmidt
2005-03-07 11:05 ` Egbert Eich
2005-03-04 12:02 ` Egbert Eich
2005-03-04 11:25 ` Egbert Eich
2005-03-04 22:16 ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2005-03-05 17:36 ` Egbert Eich
2005-03-04 11:12 ` Egbert Eich
2005-03-04 22:51 ` Benjamin Herrenschmidt
[not found] ` <42278AEC.4080706@dunaweb.hu>
2005-03-04 11:21 ` Egbert Eich
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=9e473391050303161559c17955@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=xorg@freedesktop.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).