On Sun, Feb 11, 2001 at 12:06:14PM +0100, Pavel Machek wrote:
>
> > > > > >I've discovered that heavy use of vesafb can be a major source of clock
> > > > > >drift on my system, especially if I don't specify "ypan" or "ywrap". On my
> > > > >
> > > > > This is extremely interesting. What version
On Sat, Feb 10, 2001 at 03:24:06PM +0100, Tim Krieglstein wrote:
>
> I found a way which seems to lead to an "easy" way of fs-corruption:
> Install two sound-cards, use the newest ALSA-Drivers 0.5.10b
> (the standard sound drivers don't work to good with sf) and
[snip]
This could be that bus
On Sat, Feb 10, 2001 at 03:24:06PM +0100, Tim Krieglstein wrote:
I found a way which seems to lead to an "easy" way of fs-corruption:
Install two sound-cards, use the newest ALSA-Drivers 0.5.10b
(the standard sound drivers don't work to good with sf) and
[snip]
This could be that bus
On Sun, Feb 11, 2001 at 12:06:14PM +0100, Pavel Machek wrote:
I've discovered that heavy use of vesafb can be a major source of clock
drift on my system, especially if I don't specify "ypan" or "ywrap". On my
This is extremely interesting. What version of ntp are you using?
On Fri, Feb 09, 2001 at 11:01:13PM +, Alan Cox wrote:
> > I've noticed that -ac9 comes with the "Disable PCI-Master-Read-Caching
> > on VIA" patch that Peter Horton posted a while back. I don't know
> > whether it was applied in Linus' or your tree first, but
On Thu, Feb 08, 2001 at 03:35:00AM +0100, Udo A. Steinberg wrote:
>
> I'm not sure whether this is related to the ominous ps/2 mouse bug
> you have been chasing, but this problem is 100% reproducible and
> very annoying.
>
> After upgrading my Asus A7V Bios from 1003 to 1005D, gpm no longer
>
On Tue, Feb 06, 2001 at 05:01:46PM +0100, Udo A. Steinberg wrote:
> Dale Farnsworth wrote:
> >
> > However, if I enable the BIOS parameter "I/O Recovery Time", I can still
> > enable read caching without seeing any data corruption.
> > The lastest BIOS revision (1005C) enables "I/O Recovery
On Tue, Feb 06, 2001 at 05:01:46PM +0100, Udo A. Steinberg wrote:
Dale Farnsworth wrote:
However, if I enable the BIOS parameter "I/O Recovery Time", I can still
enable read caching without seeing any data corruption.
The lastest BIOS revision (1005C) enables "I/O Recovery Time" by
On Thu, Feb 08, 2001 at 03:35:00AM +0100, Udo A. Steinberg wrote:
I'm not sure whether this is related to the ominous ps/2 mouse bug
you have been chasing, but this problem is 100% reproducible and
very annoying.
After upgrading my Asus A7V Bios from 1003 to 1005D, gpm no longer
receives
On Tue, Feb 06, 2001 at 08:52:23AM -0700, Dale Farnsworth wrote:
>
> In article <[EMAIL PROTECTED]>,
> Peter Horton <[EMAIL PROTECTED]> wrote:
> > + * VIA VT8363 host bridge has broken feature 'PCI Master Read
> > + * Caching'. It caches mo
On Tue, Feb 06, 2001 at 08:52:23AM -0700, Dale Farnsworth wrote:
In article [EMAIL PROTECTED],
Peter Horton [EMAIL PROTECTED] wrote:
+ * VIA VT8363 host bridge has broken feature 'PCI Master Read
+ * Caching'. It caches more than is good for it, sometimes
+ * serving
The patch doesn't work for me. Maybe I need to disable some more of
those North bridge features :-(
Oh bum. Back to testing with "normal" ...
P.
- CORRUPTING SETUP -
00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 0305 (rev 02)
Subsystem: Asustek Computer, Inc.:
Okay, looks like this fixes it (for me anyways).
Thanks to Mark Hahn and Andre for their help with this problem.
P.
--- linux-2.4.1/arch/i386/kernel/pci-pc.c Thu Jun 22 15:17:16 2000
+++ linux-2.4.1-bm-fix/arch/i386/kernel/pci-pc.cMon Feb 5 18:37:35 2001
@@ -924,6 +924,22 @@
I've found the cause of silent disk corruption on my A7V motherboard,
and it might affect all boards with the same North bridge (KT133 etc).
For some reason the IDE controller(s) was sometimes picking up stale
data during bus master DMA to the drive. Assuming that there was no bug
in the CPU it
I've found the cause of silent disk corruption on my A7V motherboard,
and it might affect all boards with the same North bridge (KT133 etc).
For some reason the IDE controller(s) was sometimes picking up stale
data during bus master DMA to the drive. Assuming that there was no bug
in the CPU it
Okay, looks like this fixes it (for me anyways).
Thanks to Mark Hahn and Andre for their help with this problem.
P.
--- linux-2.4.1/arch/i386/kernel/pci-pc.c Thu Jun 22 15:17:16 2000
+++ linux-2.4.1-bm-fix/arch/i386/kernel/pci-pc.cMon Feb 5 18:37:35 2001
@@ -924,6 +924,22 @@
The patch doesn't work for me. Maybe I need to disable some more of
those North bridge features :-(
Oh bum. Back to testing with "normal" ...
P.
- CORRUPTING SETUP -
00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 0305 (rev 02)
Subsystem: Asustek Computer, Inc.:
On Fri, Jan 26, 2001 at 07:48:05PM +, Russell King wrote:
> Peter Horton writes:
> > The corruption is dependent on having a swapped on swap partition. If I
> > "swapoff" the corruption goes away, but it comes back when I "swapon"
> > again. I fe
On Fri, Jan 26, 2001 at 07:48:05PM +, Russell King wrote:
Peter Horton writes:
The corruption is dependent on having a swapped on swap partition. If I
"swapoff" the corruption goes away, but it comes back when I "swapon"
again. I feel this a kernel bug, but as I'm
On Fri, Jan 26, 2001 at 09:24:12AM +, Peter Horton wrote:
> On Fri, Jan 26, 2001 at 03:20:33AM +0100, Xuan Baldauf wrote:
> >
> > Peter Horton wrote:
> >
> > > I'm experiencing repeatable corruption whilst writing large volumes of
> > > dat
On Fri, Jan 26, 2001 at 03:20:33AM +0100, Xuan Baldauf wrote:
>
> Peter Horton wrote:
>
> > I'm experiencing repeatable corruption whilst writing large volumes of
> > data to disk. Kernel version is 2.4.1-pre8, on an 850MHz AMD Athlon on an
> > ASUS A7V (VIA KT133 ch
On Fri, Jan 26, 2001 at 03:20:33AM +0100, Xuan Baldauf wrote:
Peter Horton wrote:
I'm experiencing repeatable corruption whilst writing large volumes of
data to disk. Kernel version is 2.4.1-pre8, on an 850MHz AMD Athlon on an
ASUS A7V (VIA KT133 chipset) motherboard 128M RAM (tested
On Fri, Jan 26, 2001 at 09:24:12AM +, Peter Horton wrote:
On Fri, Jan 26, 2001 at 03:20:33AM +0100, Xuan Baldauf wrote:
Peter Horton wrote:
I'm experiencing repeatable corruption whilst writing large volumes of
data to disk. Kernel version is 2.4.1-pre8, on an 850MHz AMD Athlon
I'm experiencing repeatable corruption whilst writing large volumes of
data to disk. Kernel version is 2.4.1-pre8, on an 850MHz AMD Athlon on an
ASUS A7V (VIA KT133 chipset) motherboard 128M RAM (tested with 'memtest86'
for 10 hours).
First, I realised that the fsck was noticing small
I'm experiencing repeatable corruption whilst writing large volumes of
data to disk. Kernel version is 2.4.1-pre8, on an 850MHz AMD Athlon on an
ASUS A7V (VIA KT133 chipset) motherboard 128M RAM (tested with 'memtest86'
for 10 hours).
First, I realised that the fsck was noticing small
On Sun, Jan 21, 2001 at 12:40:30PM +0100, Vojtech Pavlik wrote:
> On Sat, Jan 20, 2001 at 04:32:36PM -0500, safemode wrote:
> > Peter Horton wrote:
> >
> > > On Thu, Jan 20, 2000 at 08:38:12AM +, Peter Horton wrote:
> > > >
> > > > I think
On Sun, Jan 21, 2001 at 12:40:30PM +0100, Vojtech Pavlik wrote:
On Sat, Jan 20, 2001 at 04:32:36PM -0500, safemode wrote:
Peter Horton wrote:
On Thu, Jan 20, 2000 at 08:38:12AM +, Peter Horton wrote:
I think I'm suffering the same thing on my new Asus A7V. Yesterday I got
On Thu, Jan 20, 2000 at 08:38:12AM +, Peter Horton wrote:
>
> I think I'm suffering the same thing on my new Asus A7V. Yesterday I got a
> single "error in bitmap, remounting read only" type error, and today I got
> some files in /tmp that returned I/O error when s
On Fri, Jan 19, 2001 at 07:33:21PM -0500, safemode wrote:
> I'm sorry I can't be more descriptive than that, but there aren't any
> errors ever displayed. What happened was after about a day of uptime, I
> began seeing IO errors when trying to access files. I realized that the
> IO errors
On Fri, Jan 19, 2001 at 07:33:21PM -0500, safemode wrote:
I'm sorry I can't be more descriptive than that, but there aren't any
errors ever displayed. What happened was after about a day of uptime, I
began seeing IO errors when trying to access files. I realized that the
IO errors occurred
On Thu, Jan 20, 2000 at 08:38:12AM +, Peter Horton wrote:
I think I'm suffering the same thing on my new Asus A7V. Yesterday I got a
single "error in bitmap, remounting read only" type error, and today I got
some files in /tmp that returned I/O error when stat()ed. I do have DM
Building 2.4.1-pre8 for K7 gives 'current' undefined errors in the headers
included from init/main.c. Looks like something included from asm/string.h
is missing an include. The problems go away if I remove
CONFIG_X86_USE3DNOW=y from the config.
P.
--
P. Horton
Software Engineer
Building 2.4.1-pre8 for K7 gives 'current' undefined errors in the headers
included from init/main.c. Looks like something included from asm/string.h
is missing an include. The problems go away if I remove
CONFIG_X86_USE3DNOW=y from the config.
P.
--
P. Horton
Software Engineer
ld.com/network.
Even the DFE-530-TX driver for NT downloaded from D-Link's site doesn't know
about this chip yet ... though changing the device ID in the .INF file seemed
to make it work ... shrug.
HTH
P.
--
++
| Peter
/network.
Even the DFE-530-TX driver for NT downloaded from D-Link's site doesn't know
about this chip yet ... though changing the device ID in the .INF file seemed
to make it work ... shrug.
HTH
P.
--
++
|Peter Horton
35 matches
Mail list logo
