It seems Kristian K. Nielsen wrote:
> Hey Søren,
>
> Do you have any idea what to do with the problems I am experiencing with the
> Intel-series chipset?
Uhm, what Intel chipset exactly, or is it a VIA chipset for Intel you mean ?
Throw me a pciconf -l and I'll check..
-Søren
To Unsubscribe:
ew Dillon" <[EMAIL PROTECTED]>; "Mike Silbersack"
<[EMAIL PROTECTED]>; "Brandon S. Allbery KF8NH" <[EMAIL PROTECTED]>; "ian j
hart" <[EMAIL PROTECTED]>; "Matthew Gilbert" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>; <[EMAIL PROT
It seems Nils Holland wrote:
> root@poison> pciconf -r -b pci0:0:0 0x0:0xff
Thanks! this was a kernel without the corruption fix, and it shows
that you need it, the MWQ bug has been fixed in your BIOS...
I have a new improved patch in the works that covers more chipset
comboes, it'll go into -cu
On Sun, Dec 30, 2001 at 01:18:45AM +0100, Søren Schmidt stood up and spoke:
> > Is the 0x03051106 the KT133A? I guess so. Well, since I seem to have the
> > KT133 (without the A), I guess my values would be fairly useless...
> > However, if I'm wrong and the 0x03051106 *is* the KT133 that I have,
It seems Nils Holland wrote:
> On Sat, Dec 29, 2001 at 10:42:20PM +0100, Søren Schmidt stood up and spoke:
> > It seems Matthew Dillon wrote:
> > > :Anyways could I have you guys read out all 256 PCI regs from the
> > > :main chip that is the 0x03051106 one ?
> > > :
> > > :-Søren
> > >
> > >
On Sat, Dec 29, 2001 at 10:42:20PM +0100, Søren Schmidt stood up and spoke:
> It seems Matthew Dillon wrote:
> > :Anyways could I have you guys read out all 256 PCI regs from the
> > :main chip that is the 0x03051106 one ?
> > :
> > :-Søren
> >
> > How is this done?
>
> With pciconf, fx:
It seems Matthew Dillon wrote:
> :Anyways could I have you guys read out all 256 PCI regs from the
> :main chip that is the 0x03051106 one ?
> :
> :-Søren
>
> How is this done?
With pciconf, fx:
sos# pciconf -r -b pci0:0:0 0x0:0xff
06 11 05 03 06 00 10 22 03 00 00 06 00 08 00 00
08 00 0
:Anyways could I have you guys read out all 256 PCI regs from the
:main chip that is the 0x03051106 one ?
:
:-Søren
How is this done?
-Matt
Matthew Dillon
<[EMAIL PROTEC
--text follows this line--
Søren Schmidt <[EMAIL PROTECTED]> writes:
> If the BIOS has the option to disable "page mode" access to RAM try
> to switch that off, it has shown problems here (as I mentioned in
> another mail)
Just tried that now, no luck. I'm currently looking to see if there's
a
Most like, you can investigate the issues with VIA chipsets and AMD chipsets
through Microsoft's or VIA's driver support and Linux kernel v2.4.17. For
most of the issues I've seen dealing with AMD or VIA-type issues I've found
a solution or issue crop up in those areas.
I suggest if you are ha
It seems Matthew Dillon wrote:
> Note that we aren't complaining about your patch or anything, you
> are simply the closest thing we have to a VIA chip expert right now :-)
I know, I want to nail this as badly as you guys do, I just want to
have the info I use verified before I base any p
On Fri, Dec 28, 2001 at 11:23:01PM +0100, Søren Schmidt stood up and spoke:
> It seems Matthew Dillon wrote:
> > Ok, I have more information on Nils problem. First of all, Soren's
> > patch greatly reduced the rate of corruption. It took 25 loops of
> > Nils 'cp' test to generate the
On Fri, 28 Dec 2001, Søren Schmidt wrote:
> I know that change as well, but so far I havn't been able to verify
> that it does what it intends to do, VIA's docs are very vague on this.
>
> There is alot about this on the net, but *lots* of it are just notes
> scribbled together by nerds^H^H^H^H^
Note that we aren't complaining about your patch or anything, you
are simply the closest thing we have to a VIA chip expert right now :-)
-Matt
Matthew Dillon
<[EMAIL P
It seems Mike Silbersack wrote:
> Agreed, it looks like the "MWQ bug" isn't addressed by soren's patch. The
> decription at
> http://www.networking.tzo.com/net/software/readme/faqvl019.htm
> doesn't give enough info to patch it, but this post to the linux-kernel
> mailing list seems to shed more
On Fri, 28 Dec 2001, Matthew Dillon wrote:
> Ok, I have more information on Nils problem. First of all, Soren's
> patch greatly reduced the rate of corruption. It took 25 loops of
> Nils 'cp' test to generate the corruption.
>
> However, Soren's patch did not fiix the corruptio
It seems Matthew Dillon wrote:
> Ok, I have more information on Nils problem. First of all, Soren's
> patch greatly reduced the rate of corruption. It took 25 loops of
> Nils 'cp' test to generate the corruption.
Hmm, did the second change I posted change anything ?
> However,
:...
:> >
:> > There is also the "only supports 16MxN RAM" feature.
:>
:> Maybe I should toss in that I've had spontaneous reboots during heavy
:> IDE activity both on my desktop (VIA 82C686) and my laptop (Intel
:> 82443BX). And before that, random disk corruption during heavy SCSI
:> activit
I don't know if this is relevent, but my asus a7v266, with
a chip=0x30991106, bios rev 1003
(most recent), works very, very badly with my soundblaster card
chip=0x50001274, unless i change the parameter
'PCI Latency Timer' from 32 to 64. then, it works perfectly...
thanks,
-
t;
To: "Kristian K. Nielsen" <[EMAIL PROTECTED]>
Cc: "Nils Holland" <[EMAIL PROTECTED]>; "Søren Schmidt" <[EMAIL PROTECTED]>;
"Matthew Gilbert" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Friday, Dec
:In article <005101c18ee1$9b5d66e0$fa01a8c0@ABERRATION>, Predius
:<[EMAIL PROTECTED]> writes
:>There are a couple known issues going on with the VIA Chipset line (Some
:>acknowledge by VIA partially, some not.) beyond just the 686B bug.
:>
:>Here's a couple sites with details. Myself, I think it'
:Hey,
:
:It is great if you are finding a solution for the VIA-chipset.
:Do you have any idea if it is a simular problem that I am experiencing?
:
:I am not enough into chip code to have a clue what exactly the patch
:is doing - but maybe it is just decreasing the load on the kernel/system in
:a
n
- Original Message -
From: "Matthew Dillon" <[EMAIL PROTECTED]>
To: "Nils Holland" <[EMAIL PROTECTED]>
Cc: "Søren Schmidt" <[EMAIL PROTECTED]>; "Matthew Gilbert"
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
<[EMAIL PROTECTE
In article <005101c18ee1$9b5d66e0$fa01a8c0@ABERRATION>, Predius
<[EMAIL PROTECTED]> writes
>There are a couple known issues going on with the VIA Chipset line (Some
>acknowledge by VIA partially, some not.) beyond just the 686B bug.
>
>Here's a couple sites with details. Myself, I think it's a BI
It seems Brandon S. Allbery KF8NH wrote:
> On Thu, 2001-12-27 at 15:20, ian j hart wrote:
> > Myself and others have had IDE related problems. Search
> > the stable and hardware mail archives for
> > UDMA and ICRC [and ianjhart] for examples.
> >
> > There is also the "only supports 16MxN RAM" f
On Thu, 2001-12-27 at 15:20, ian j hart wrote:
> Myself and others have had IDE related problems. Search
> the stable and hardware mail archives for
> UDMA and ICRC [and ianjhart] for examples.
>
> There is also the "only supports 16MxN RAM" feature.
Maybe I should toss in that I've had spontane
SXren Schmidt wrote:
>
> It seems Matthew Dillon wrote:
> > Sorry, I meant I'd follow up with Matthew Gilbert. Also, I've
> > been trying to track down a crash in nfs_node that Nils Holland
> > has been having - he appears to have the same chipset and could
> > have the same prob
It seems Matthew Dillon wrote:
> This is great news! I'm crossing my fingers and hoping that Nils can't
> reproduce the crash any more with Soren's fix.
Me too :)
I have a small change that can be used if performace suffers too badly,
it has not provoked the problem again on any of the
This is great news! I'm crossing my fingers and hoping that Nils can't
reproduce the crash any more with Soren's fix.
Just to let you all know, Nils has been working his ass off helping me
track his crash down. I've been pulling my hair out... I gave him patch
after patch to
On Thu, Dec 27, 2001 at 10:45:01AM +0100, Søren Schmidt stood up and spoke:
>
> OK, here goes the VIA 686b patch, it is hand cut out from the bulk patches
> to go into 4.5 so beware :)
Well, as Matt has said, I reported a crash that he's trying to debug. Since
I have the 686b in my machine, I ap
On Thu, Dec 27, 2001 at 03:15:15PM +0100, Søren Schmidt wrote:
> It seems Pete French wrote:
> > > Anyhow since this is not always the case I did the fix for -current,
> > > granted it should not be in the ATA driver, but since nobody else
> > > really cared at the time
> >
> > Does this mean
t;
Sent: Thursday, December 27, 2001 8:49 AM
Subject: Re: Need PCI/VIA chipset help (was Re: 4.4-STABLE crashes -
suspects new ata-driver over wd-drivers)
> > Anyhow since this is not always the case I did the fix for -current,
> > granted it should not be in the ATA driver, but since n
> Anyhow since this is not always the case I did the fix for -current,
> granted it should not be in the ATA driver, but since nobody else
> really cared at the time
Does this mean that if you dont have the ATA drivers in the kernel then
you wont get the fix ? As the bug occurs under high PCI
On Thu, Dec 27, 2001 at 02:07:22PM +0100, Søren Schmidt wrote:
> It seems Wilko Bulte wrote:
> > On Thu, Dec 27, 2001 at 12:15:56AM +0100, Søren Schmidt wrote:
> > > It seems Matthew Gilbert wrote:
> > > > > So, general question to everyone having crashes during heavy
> > > > > IDE workloa
It seems Wilko Bulte wrote:
> On Thu, Dec 27, 2001 at 12:15:56AM +0100, Søren Schmidt wrote:
> > It seems Matthew Gilbert wrote:
> > > > So, general question to everyone having crashes during heavy
> > > > IDE workloads: Please post your /var/run/dmesg.boot
> > > > output.
> >
> > >
On Thu, Dec 27, 2001 at 12:15:56AM +0100, Søren Schmidt wrote:
> It seems Matthew Gilbert wrote:
> > > So, general question to everyone having crashes during heavy
> > > IDE workloads: Please post your /var/run/dmesg.boot
> > > output.
>
> > atapci0: port 0xd000-0xd00f at device 7.1
It seems Danny Braniss wrote:
> > It seems Matthew Gilbert wrote:
> > > > So, general question to everyone having crashes during heavy
> > > > IDE workloads: Please post your /var/run/dmesg.boot
> > > > output.
> >
> > > atapci0: port 0xd000-0xd00f at device 7.1 on
> >
> > You hav
It seems Matthew Dillon wrote:
> Soren, if you post a patch for 4.x I will be happy to follow-up
> with Brady. I've been working with Brady for several days now trying
> to track down corruption in the vm_page array. I *really* want to know
> if a VIA chipset patch solves his p
It seems Matthew Dillon wrote:
> Sorry, I meant I'd follow up with Matthew Gilbert. Also, I've
> been trying to track down a crash in nfs_node that Nils Holland
> has been having - he appears to have the same chipset and could
> have the same problem, and he can reproduce the pan
> It seems Matthew Gilbert wrote:
> > > So, general question to everyone having crashes during heavy
> > > IDE workloads: Please post your /var/run/dmesg.boot
> > > output.
>
> > atapci0: port 0xd000-0xd00f at device 7.1 on
>
> You have the VIA 82c686b southbridge chip which is kn
:
::
::> atapci0: port 0xd000-0xd00f at device 7.1 on
::
::You have the VIA 82c686b southbridge chip which is known to cause severe
::data corruption problems if the BIOS does not setup the northbidge
::chip correctly. Please check with your board vendor if they have a
::new updated BIOS that f
:
:It seems Matthew Gilbert wrote:
:> > So, general question to everyone having crashes during heavy
:> > IDE workloads: Please post your /var/run/dmesg.boot
:> > output.
:
:> atapci0: port 0xd000-0xd00f at device 7.1 on
:
:You have the VIA 82c686b southbridge chip which is known t
It seems Matthew Gilbert wrote:
> > So, general question to everyone having crashes during heavy
> > IDE workloads: Please post your /var/run/dmesg.boot
> > output.
> atapci0: port 0xd000-0xd00f at device 7.1 on
You have the VIA 82c686b southbridge chip which is known to cause sev
> So, general question to everyone having crashes during heavy
> IDE workloads: Please post your /var/run/dmesg.boot
> output.
This is after a second reboot (that is why the disks come up clean). -Matt
Copyright (c) 1992-2001 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986
I am trying to determine if our ATA/VIA setup code may have issues. I
did a google search and came up with a linux-quirks patch which may
apply to the random corruption problems people have been reporting.
Here is the URL:
http://www.linuxhq.com/kernel/v2.4/patch/patch-2.4.8
45 matches
Mail list logo
