From: James Cort <jim@whitepost.org.uk>
To: linux-kernel@vger.kernel.org
Subject: Stability problem on a Gigabyte motherboard
Date: Wed, 7 Jan 2004 23:52:38 +0000 [thread overview]
Message-ID: <200401072352.38578.jim@whitepost.org.uk> (raw)
I've been using Linux for ages now, and I think the time has finally come to
ask a question in this forum.
Doubtless I'm totally wrong and will be flamed into oblivion, but hey...
I have a Gigabyte GA-7VAXP motherboard, and I'm using kernel 2.4.23. This
board is based on a VIA-KT400 chipset, with UDMA-133 and USB 2 support.
Versions of the BIOS prior to F11 are stable but USB 2 support is broken.
Later BIOS versions have fixed USB 2 support, but render my system unstable -
va-ctcs dies in under 10 seconds, locking the entire machine such that there
are no logs, no visible kernel panic to console and the magic sys-rq key
doesn't work. Similar symptoms can be observed doing heavy disk writes to a
USB 2 external hard disk or decompressing a large archive (such as the kernel
source) to the internal IDE disk.
I've searched the mailing list archives, asked Gigabyte, Googled, asked my
local LUG and looked at the VIA web forums, all to no avail. So now I ask the
good people here - are there any known issues with VIA chipset support which
might cause this?
TBH, the lack of logs I'm getting means I'm not sure if the problem is because
of lousy BIOS writing on the part of Gigabyte or a genuine bug in the kernel.
However, any helpful suggestions will be most gratefully received.
James Cort
--
Conserve wildlife - pickle a squirrel
reply other threads:[~2004-01-07 23:49 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=200401072352.38578.jim@whitepost.org.uk \
--to=jim@whitepost.org.uk \
--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
all inboxes | Powered by JetHome®