From: jerry <jdinardo@ix.netcom.com>
To: linux-kernel@vger.kernel.org
Subject: Re: USB and 2.4.2: "uhci: host system error, PCI problems?"
Date: Mon, 26 Feb 2001 15:14:24 -0500 [thread overview]
Message-ID: <20010226151424.A857@ix.netcom.com> (raw)
In-Reply-To: <20010223144004.A30274@convergence.de> <E14XPcd-00085C-00@aleph0.datakart.hu>
In-Reply-To: <E14XPcd-00085C-00@aleph0.datakart.hu>; from fero@drama.obuda.kando.hu on Mon, Feb 26, 2001 at 04:31:22PM +0100
I do not think the problem has anything to do with rivafb. I get the same
problem with 2.4.2 when i have dma enabled on my ide disk on my ABIT kt7
which is a via base Athlon mobo as well.
If you have dma enabled , try disabling it and see if the problem goes away
, although now you have a new problem ( slow disk).
jpd
> > Any ideas? It's a VIA based Athlon board. Worked fine with 2.4.0 and
> > 2.4.1. The only change was that I added rivafb, which finally adds
> > Geforce support in 2.4.2. /proc/interrupts does not show any interrupts
> > assigned to rivafb, maybe there is a conflict?
prev parent reply other threads:[~2001-02-26 20:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-23 13:40 USB and 2.4.2: "uhci: host system error, PCI problems?" Felix von Leitner
2001-02-26 15:31 ` Bakonyi Ferenc
2001-02-26 20:14 ` jerry [this message]
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=20010226151424.A857@ix.netcom.com \
--to=jdinardo@ix.netcom.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox