From: Juan Quintela <quintela@mandrakesoft.com>
To: <whitney@math.berkeley.edu>
Cc: LKML <linux-kernel@vger.kernel.org>, <toddroy@softhome.net>
Subject: Re: 2.4.3-p8 pci_fixup_vt8363 + ASUS A7V "Optimal" = IDE disk corruption
Date: 09 May 2001 19:31:51 +0200 [thread overview]
Message-ID: <m2eltyo2d4.fsf@trasno.mitica> (raw)
In-Reply-To: <Pine.LNX.4.30.0103290931330.12531-100000@mf1.private>
In-Reply-To: <Pine.LNX.4.30.0103290931330.12531-100000@mf1.private>
Hi
sorry for the delay, it is working for your motherboard the
lastest kernels of Mandrake? I think that all the problems
have been solved?
Sorry for the delay, as I was finishing more things.
Later, Juan.
>>>>> "wayne" == Wayne Whitney <whitney@math.berkeley.edu> writes:
wayne> On 29 Mar 2001, Juan Quintela wrote:
>> Hi I have the same motherboard and BIOS version. I was having
>> filesystem corruption. There is a bugfix (from Arjan van der Ven) in
>> the ac tree (around ac20 I think), could you test the last ac patch
>> and test if the filesystem corruption persist??
wayne> I took a look at 2.4.2-ac28; rather than test the kernel itself, I used
wayne> setpci to duplicate what the fixup function does. The upshot is that
wayne> 2.4.2-ac28 does not cause any corruption with the ASUS A7V 1007 "Optimal".
wayne> Its pci_fixup_vt8363 function has a subset of the tests from 2.4.3-pre8,
wayne> namely it omits:
wayne> pci_read_config_byte(d, 0x54, &tmp);
wayne> if(tmp & (1)) {
wayne> printk("PCI: Fast Write to Read turnaround disabled\n");
wayne> pci_write_config_byte(d, 0x54, tmp & ~(1));
wayne> }
wayne> pci_read_config_byte(d, 0x70, &tmp);
wayne> if(tmp & (1<<2)) {
wayne> printk("PCI: Disabled Master Read Caching\n");
wayne> pci_write_config_byte(d, 0x70, tmp & ~(1<<2));
wayne> }
wayne> This second test was part of the 2.4.3-pre8 pci_fixup_vt8363 subset from
wayne> my previous email which causes corruption on the ASUS A7V 1007 for both
wayne> Optimal and Normal settings. I verified that if I add it back in, I do
wayne> get corruption with ASUS A7V 1007 "Optimal". By omitting it, I guess
wayne> 2.4.2-ac28 avoids the corruption of 2.4.3-pre8.
wayne> Perhaps 2.4.3-pre9 should adopt the pci_fixup_vt8363 from 2.4.2-ac28?
wayne> Below is a patch.
wayne> Cheers,
wayne> Wayne
wayne> --- linux-2.4.3-pre8/arch/i386/kernel/pci-pc.c Wed Mar 28 22:56:04 2001
wayne> +++ linux-2.4.2-ac28/arch/i386/kernel/pci-pc.c Wed Mar 28 22:51:00 2001
wayne> @@ -968,23 +971,13 @@
wayne> printk("PCI: Bus master Pipeline request disabled\n");
wayne> pci_write_config_byte(d, 0x54, tmp & ~(1<<2));
wayne> }
wayne> - pci_read_config_byte(d, 0x54, &tmp);
wayne> - if(tmp & (1)) {
wayne> - printk("PCI: Fast Write to Read turnaround disabled\n");
wayne> - pci_write_config_byte(d, 0x54, tmp & ~(1));
wayne> - }
wayne> pci_read_config_byte(d, 0x70, &tmp);
wayne> if(tmp & (1<<3)) {
wayne> printk("PCI: Disabled enhanced CPU to PCI writes\n");
wayne> pci_write_config_byte(d, 0x70, tmp & ~(1<<3));
wayne> }
wayne> - pci_read_config_byte(d, 0x70, &tmp);
wayne> - if(tmp & (1<<2)) {
wayne> - printk("PCI: Disabled Master Read Caching\n");
wayne> - pci_write_config_byte(d, 0x70, tmp & ~(1<<2));
wayne> - }
wayne> pci_read_config_byte(d, 0x71, &tmp);
wayne> - if ((tmp & (1<<3))==0) {
wayne> + if((tmp & (1<<3)) == 0) {
wayne> printk("PCI: Bursting cornercase bug worked around\n");
wayne> pci_write_config_byte(d, 0x71, tmp | (1<<3));
wayne> }
--
In theory, practice and theory are the same, but in practice they
are different -- Larry McVoy
next prev parent reply other threads:[~2001-05-09 17:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m2puf0hft9.fsf@trasno.mitica>
2001-03-29 18:09 ` 2.4.3-p8 pci_fixup_vt8363 + ASUS A7V "Optimal" = IDE disk corruption Wayne Whitney
2001-05-09 17:31 ` Juan Quintela [this message]
2001-03-29 12:05 Todd M. Roy
-- strict thread matches above, loose matches on Subject: below --
2001-03-29 5:29 Wayne Whitney
2001-03-29 16:16 ` Arjan van de Ven
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=m2eltyo2d4.fsf@trasno.mitica \
--to=quintela@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=toddroy@softhome.net \
--cc=whitney@math.berkeley.edu \
/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.