From: Vojtech Pavlik <vojtech@suse.cz>
To: "David D.W. Downey" <pgpkeys@hislinuxbox.com>
Cc: Mark Hahn <hahn@coffee.psychology.mcmaster.ca>,
David Raufeisen <david@fortyoz.org>,
linux-kernel@vger.kernel.org
Subject: Re: VT82C686A corruption with 2.4.x
Date: Wed, 31 Jan 2001 08:36:42 +0100 [thread overview]
Message-ID: <20010131083642.A964@suse.cz> (raw)
In-Reply-To: <Pine.LNX.4.21.0101301716490.3105-100000@ns-01.hislinuxbox.com> <Pine.LNX.4.21.0101301755330.3205-200000@ns-01.hislinuxbox.com>
In-Reply-To: <Pine.LNX.4.21.0101301755330.3205-200000@ns-01.hislinuxbox.com>; from pgpkeys@hislinuxbox.com on Tue, Jan 30, 2001 at 06:04:42PM -0800
Hi!
1) You don't seem to have any drives on the VIA controller. If this is
true, I don't think this can be a VIA IDE driver problem.
2) In your original message you suggest bs=1024M, which isn't a very
good idea, even on a 768 MB system. Here with bs=1024k it seems to run
fine.
3) You sent next to none VIA related debugging info. lspci -v itself
isn't much valuable because I don't get the register contents. Also
hdparm -i of the drives attached to the VIA chip would be useful. Plus
also the contents of /proc/ide/via.
4) Did you check the problem you're experiencing isn't a memory problem?
That'd go away with removing some RAM.
Vojtech
PS. I'm not sure how wise is to use both ACPI and APM at once. Well, I
never used either in a server environment - I don't think it makes much
sense.
PPS. What should I do with a ksyms dump of the Advansys SCSI and a Tulip
NIC drivers? It isn't related anyhow.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-31 7:37 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10101301743180.30535-100000@coffee.psychology.mcmaster.ca>
2001-01-31 1:18 ` VT82C686A corruption with 2.4.x David D.W. Downey
2001-01-31 2:04 ` David D.W. Downey
2001-01-31 7:36 ` Vojtech Pavlik [this message]
2001-01-31 7:55 ` David Raufeisen
2001-01-31 9:48 ` safemode
2001-01-31 11:43 ` Vojtech Pavlik
2001-01-31 12:54 ` Mark Hahn
2001-01-31 19:58 ` David Riley
2001-02-01 12:51 ` David D.W. Downey
2001-01-31 20:01 ` safemode
2001-01-31 22:04 ` Tobias Ringstrom
2001-01-31 22:40 ` safemode
2001-01-31 22:46 ` Alan Cox
2001-01-31 22:57 ` safemode
2001-02-01 6:31 ` Vojtech Pavlik
2001-02-01 0:46 ` Byron Stanoszek
2001-02-01 1:52 ` safemode
2001-02-01 6:52 ` Vojtech Pavlik
2001-02-01 11:32 ` safemode
2001-02-01 16:46 ` Byron Stanoszek
2001-02-01 18:06 ` Vojtech Pavlik
2001-02-01 18:20 ` Byron Stanoszek
2001-02-01 20:51 ` Vojtech Pavlik
2001-02-01 21:51 ` safemode
2001-02-01 21:56 ` Alan Chandler
2001-02-01 6:39 ` Vojtech Pavlik
2001-01-31 11:39 ` Vojtech Pavlik
2001-01-31 15:41 ` David D.W. Downey
2001-01-30 13:40 Nicholas Knight
2001-01-30 15:03 ` Tobias Ringstrom
2001-01-30 19:51 ` David D.W. Downey
2001-01-30 20:53 ` David Raufeisen
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=20010131083642.A964@suse.cz \
--to=vojtech@suse.cz \
--cc=david@fortyoz.org \
--cc=hahn@coffee.psychology.mcmaster.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=pgpkeys@hislinuxbox.com \
/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