From: <christian@scharff-home.de>
To: <linux-kernel@vger.kernel.org>
Cc: <christian@scharff-home.de>
Subject: EPIA-M: DMA & VT8235 Lock-up
Date: Tue, 4 Apr 2006 18:07:57 +0200 [thread overview]
Message-ID: <17624747.9731144160783244.JavaMail.servlet@kundenserver> (raw)
Hi,
I am writing to this list since I think solving this issue may have some
importance also to other Linux users.
Please CC me if you answer since I am not subscribed to this list!
Here is the issue:
I have severe lock-ups with Vias ME6000 motherboard with UDMA100
transfers.
MY Hardaware:
VIA EPIA ME6000 (VIA VT8235 south bridge)
512 MB DDR400 RAM (verified OK!)
Technotrend DVBs 1.5 card
Intel Pro 1000 desktop ethernet card (e1000)
Linux Kernel 2.6.13
Bios: 1.16
hard drive Samsung HM100JC (UDMA 100 capable)
I made some test copying some files back and forth on my HD
When I run this in dma4 and dma5 mode my systems stops working after a
while.
With lower DMA modes or in PIO mode everything is fine.
I tested already different 80 pin ATA cables, but the cable does not
solve the problem.
So the board or the drivers have a DMA issue.
I am wondering if this can be fixed in the LINUX Kernel or if this is an
unsolved VT8235 hardware issue.
Lockups usually occur if there is also other traffic, like network
traffic.
Via seems to have a solution for its Windows drivers since it has been
reported that with a driver update in 2005 the issue was solved.
Others users report similar problems. See related thread here:
http://forums.viaarena.com/messageview.aspx?catid=28&threadid=60131&STAR
TPAGE=1&FTVAR_FORUMVIEWTMP=Linear
Are there any suggestions if this can be fixed by modifying kernel
divers?
RGDS
Christian
reply other threads:[~2006-04-04 16:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=17624747.9731144160783244.JavaMail.servlet@kundenserver \
--to=christian@scharff-home.de \
--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