From: Chris Rankin <rankinc@pacbell.net>
To: vandrove@vc.cvut.cz (Petr Vandrovec)
Cc: b.twijnstra@chello.nl (Ben Twijnstra), linux-kernel@vger.kernel.org
Subject: Re: Hard lockup switching to X from vc; Matrox G400 AGP
Date: Sun, 27 May 2001 18:49:17 -0700 (PDT) [thread overview]
Message-ID: <200105280149.f4S1nIs10660@wellhouse.underworld> (raw)
In-Reply-To: <20010528024250.C1244@ppc.vc.cvut.cz>
Hi, thanks for confirming this. But if it's Matrox's code (we are
talking about the mga_hal_drv.o module for X, correct?) then the ball
is in their court. Has anyone reported this to them so that they can
fix it?
Cheers,
Chris
> On Mon, May 28, 2001 at 12:24:50AM +0200, Ben Twijnstra wrote:
> > Hi Chris,
> >
> > Seen the same behaviour; you're not alone. I'm running XF86 4.0.3 with
> > a G400. My guess is that mga_drv goes into some local loop while trying
> > to restore the display. mga_drv at that moment has I/O privileges and if
> > it hangs, Linux hangs too.
>
> It is problem with their driver. Their are resetting too much of
> hardware state during mode switches and if someone accesses memory
> at that moment, whole thing locks up your PCI bus - if you have ATX
> box, try hitting poweroff button next time it lockups. If poweroff
> does not work you'll have bad time to get it debugged. If poweroff
> button works, you can try kdb...
>
> On my machine it is 100% reproducible if I run 'fbtv -k' and start X.
> It will die immediately.
next parent reply other threads:[~2001-05-28 1:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010528024250.C1244@ppc.vc.cvut.cz>
2001-05-28 1:49 ` Chris Rankin [this message]
2001-05-30 11:59 Rahul Karnik
-- strict thread matches above, loose matches on Subject: below --
2001-05-27 22:24 Ben Twijnstra
2001-05-27 21:47 Chris Rankin
2001-05-27 21:53 ` Alan Cox
2001-05-28 3:21 ` Rafael Herrera
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=200105280149.f4S1nIs10660@wellhouse.underworld \
--to=rankinc@pacbell.net \
--cc=b.twijnstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=vandrove@vc.cvut.cz \
/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
all inboxes | Powered by JetHome®