All of lore.kernel.org
 help / color / mirror / Atom feed
From: Emmanuele Bassi <emmanuele.bassi@iol.it>
To: linux-kernel@vger.kernel.org
Subject: Re: Deadlock on kernels > 2.4.13-pre6
Date: Sat, 1 Dec 2001 14:39:43 +0100	[thread overview]
Message-ID: <20011201143943.A1851@wolverine.lohacker.net> (raw)
In-Reply-To: <20011130221334.A15353@wolverine.lohacker.net> <E169wJt-00052j-00@the-village.bc.nu>
In-Reply-To: <E169wJt-00052j-00@the-village.bc.nu>

* Alan Cox <alan@lxorguk.ukuu.org.uk>:

> > Even if it shows up to be a VIA problem, what do I have to do, to get my
> > system work properly with this chipset?
> 
> The reason I ask is VIA have had a history of weird ISA DMA hangs when doing
> certain other operations. It could be some combination of these triggering
> problems.

Considering this issue, and that everything else I've tried this far, I
beginning to think that the controller is, indeed, guilty as charged.

> > 01:00.0 VGA compatible controller: nVidia Corporation Riva TnT [NV04] (rev 04) (prog-if 00 [VGA])
> 
> Are you seeing the hangs in X11, and which X setup (one with agp loaded ?)

I see hangs in both X11 and console, but under console I use the
framebuffer device (rivafb).

This is the section about my hardware inside /etc/X11/XF86Config-4:

# **********************************************************************
# Graphics device section
# **********************************************************************

# Device configured by xf86config:

Section "Device"
    Identifier  "Creative VideoBlaster"
    Driver      "nv"
    VideoRam    16384
EndSection

+++

Just to be certain, I have an old PCI graphic card (a Matrox Mystique)
that worked nicely since three years now... If that works nice, this
should be the final proof...

> Also does it print "Activiating ISA DMA workarounds" during the boot ?

Yes.

Bye,
 Emmanuele.

-- 
Emmanuele Bassi (Zefram)               [ http://digilander.iol.it/ebassi ]
GnuPG Key fingerprint = 4DD0 C90D 4070 F071 5738  08BD 8ECC DB8F A432 0FF4

  reply	other threads:[~2001-12-01 13:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-30 15:40 Deadlock on kernels > 2.4.13-pre6 Emmanuele Bassi
2001-11-30 15:54 ` Alan Cox
2001-11-30 16:04   ` Andreas Steinmetz
2001-11-30 21:13   ` Emmanuele Bassi
2001-11-30 22:39     ` Alan Cox
2001-12-01 13:39       ` Emmanuele Bassi [this message]
2001-12-01 17:41         ` Emmanuele Bassi
2001-12-03  7:52 ` Chris Siebenmann

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=20011201143943.A1851@wolverine.lohacker.net \
    --to=emmanuele.bassi@iol.it \
    --cc=linux-kernel@vger.kernel.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 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.