From: Jon Smirl <jonsmirl@yahoo.com>
To: James Simmons <jsimmons@infradead.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
fb-devel <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Re: mode setting and console locking, nvidia failure
Date: Mon, 17 May 2004 20:00:08 -0700 (PDT) [thread overview]
Message-ID: <20040518030008.43467.qmail@web14925.mail.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0405172351550.796-100000@phoenix.infradead.org>
This patch didn't fix it. How does VGA routing work on the PCI bus, what gets
routed? Memory at A000 plus IO ports, just mem???
My top choice is still two enabled VGA devices. I suspect that X libvgahw is
writing to the registers and both cards are seeing the writes.
The bug has a very specific profile - a VT switch from X to console or vice
versa triggers it. But it also has the unique characteristic that if you switch
X to console to X things work ok. Same for console to X to console.
It is easy to recreate you need one PCI and one AGP card. Run without
framebuffer on the primary card. Reset the secondary card with a reset program
(you can use X to reset it). Load fbdev on secondary. Start X. fbset from an
xterm. System dies. This works for every combo of cards I own so it does not
seem to be driver specific.
--- James Simmons <jsimmons@infradead.org> wrote:
> Jon are you using a vanilla 2.6.6 kernel. If you are could you try this
> patch.
>
> http://phoenix.infradead.org/~jsimmons/mode.diff
>
> It might solve your problem. It might be a cons2fb mapping issue.
=====
Jon Smirl
jonsmirl@yahoo.com
__________________________________
Do you Yahoo!?
SBC Yahoo! - Internet access at a great low price.
http://promo.yahoo.com/sbc/
-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
next prev parent reply other threads:[~2004-05-18 3:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-16 15:57 mode setting and console locking Jon Smirl
2004-05-16 22:03 ` Benjamin Herrenschmidt
2004-05-17 2:29 ` Jon Smirl
2004-05-17 3:51 ` Jon Smirl
2004-05-17 3:51 ` Benjamin Herrenschmidt
2004-05-17 4:12 ` Jon Smirl
2004-05-17 4:15 ` Benjamin Herrenschmidt
2004-05-17 4:51 ` Re: mode setting and console locking, nvidia failure Jon Smirl
2004-05-17 5:03 ` Jon Smirl
2004-05-17 22:56 ` James Simmons
2004-05-17 23:26 ` Jon Smirl
2004-05-18 3:00 ` Jon Smirl [this message]
2004-05-18 3:38 ` Jon Smirl
2004-05-18 3:37 ` Benjamin Herrenschmidt
2004-05-18 3:53 ` 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=20040518030008.43467.qmail@web14925.mail.yahoo.com \
--to=jonsmirl@yahoo.com \
--cc=benh@kernel.crashing.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-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 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).