2.4.5-ac14 on an Asus A7A266 w/ Athlon:
...
Jun 19 16:14:21 pollux kernel: probable hardware bug: clock timer
configuration lost - probably a VIA686a motherboard.
Jun 19 16:14:21 pollux kernel: probable hardware bug: restoring chip
configuration.
...
According to the documentation, this is an
I tried 2.4.5-ac16 on my Asus A7A266 w/ Athlon because the fixnotes
sounded like it might address the simplex vs. DMA problem that I
reported a while back, but I get a kernel panic early in the boot
sequence every time I try to boot.
FYI, 2.4.5-ac14 boots and runs OK, except for the disabled
I tried 2.4.5-ac16 on my Asus A7A266 w/ Athlon because the fixnotes
sounded like it might address the simplex vs. DMA problem that I
reported a while back, but I get a kernel panic early in the boot
sequence every time I try to boot.
FYI, 2.4.5-ac14 boots and runs OK, except for the disabled
2.4.5-ac14 on an Asus A7A266 w/ Athlon:
...
Jun 19 16:14:21 pollux kernel: probable hardware bug: clock timer
configuration lost - probably a VIA686a motherboard.
Jun 19 16:14:21 pollux kernel: probable hardware bug: restoring chip
configuration.
...
According to the documentation, this is an
Alan Cox wrote:
> > May 22 21:45:07 pollux kernel: ALI15X3: simplex device: DMA disabled
> > May 22 21:45:07 pollux kernel: ide0: ALI15X3 Bus-Master DMA disabled
> > (BIOS)
> > May 22 21:45:07 pollux kernel: ALI15X3: simplex device: DMA disabled
> > May 22 21:45:07 pollux kernel: ide1: ALI15X3
Mike Frisch wrote:
> On Mon, May 28, 2001 at 05:57:12PM +0200, Axel Thimm wrote:
> > What is the status of the support for this chipset, found for example in an
> > ASUS A7A266? Judging from
> > http://www.acerlabs.com/eng/support/faqlnx.htm
> > one gets the impression that ALi is respectfully
Mike Frisch wrote:
On Mon, May 28, 2001 at 05:57:12PM +0200, Axel Thimm wrote:
What is the status of the support for this chipset, found for example in an
ASUS A7A266? Judging from
http://www.acerlabs.com/eng/support/faqlnx.htm
one gets the impression that ALi is respectfully treating
Alan Cox wrote:
May 22 21:45:07 pollux kernel: ALI15X3: simplex device: DMA disabled
May 22 21:45:07 pollux kernel: ide0: ALI15X3 Bus-Master DMA disabled
(BIOS)
May 22 21:45:07 pollux kernel: ALI15X3: simplex device: DMA disabled
May 22 21:45:07 pollux kernel: ide1: ALI15X3
May 5 10:29:24 pollux kernel: Unable to handle kernel NULL pointer
dereference at virtual address 0014
Thereafter, almost nothing on the system worked.
This was within minutes of booting, and thus isn't the result of
long-term corruption.
The system is an Athlon on an Epox 8KTA3 (=VIA),
May 5 10:29:24 pollux kernel: Unable to handle kernel NULL pointer
dereference at virtual address 0014
Thereafter, almost nothing on the system worked.
This was within minutes of booting, and thus isn't the result of
long-term corruption.
The system is an Athlon on an Epox 8KTA3 (=VIA),
Aaron Tiensivu wrote:
> > What still stands out is that exactly _zero_ people have reported the same
> > problem with non VIA chipset Athlons.
>
> This might be grasping at straws [...] This could be (total conjecture)
> related somehow to the corruption bugs they are admitting to in
> the
Aaron Tiensivu wrote:
What still stands out is that exactly _zero_ people have reported the same
problem with non VIA chipset Athlons.
This might be grasping at straws [...] This could be (total conjecture)
related somehow to the corruption bugs they are admitting to in
the 686B
Apr 30 12:51:00 pollux kernel: kernel BUG at page_alloc.c:73!
Apr 30 12:51:00 pollux kernel: invalid operand:
This begins a cascade of similar messages, after which almost anything I
try to do results in a segfault.
The system is an Athlon on an Epox 8KTA3, with BIOS flashed up to
Apr 30 12:51:00 pollux kernel: kernel BUG at page_alloc.c:73!
Apr 30 12:51:00 pollux kernel: invalid operand:
This begins a cascade of similar messages, after which almost anything I
try to do results in a segfault.
The system is an Athlon on an Epox 8KTA3, with BIOS flashed up to
I have an Athlon + VIA system that would never boot an Athlon-optimized
2.4.3[-ac*], and just FYI, it will not boot an Athlon-optimized
2.4.4pre7 either.
It does compile without errors, and an otherwise identical i686 kernel
boots and appears to run fine.
With the Athlon kernel I get a flood of
Dennis Bjorklund wrote:
> On Tue, 17 Apr 2001, Alan Cox wrote:
>
> > try and avoid a hardware problem. VIA have finally released an 'official'
> > fix which seems to be a lot less damaging to performance on the whole. That
> > I hope will be in 2.4.4
>
> What is this official fix? I've only seen
Dennis Bjorklund wrote:
On Tue, 17 Apr 2001, Alan Cox wrote:
try and avoid a hardware problem. VIA have finally released an 'official'
fix which seems to be a lot less damaging to performance on the whole. That
I hope will be in 2.4.4
What is this official fix? I've only seen
[1.] One line summary of the problem:
ATA/100 drive on PCI ATA/100 controller was very fast under 2.4.0 and
2.4.2, but becomes *very* slow under 2.4.3
[2.] Full description of the problem/report:
I have an ATA/100 controller card in a PCI slot, and an ATA/100 drive
hanging off it. Under
[1.] One line summary of the problem:
ATA/100 drive on PCI ATA/100 controller was very fast under 2.4.0 and
2.4.2, but becomes *very* slow under 2.4.3
[2.] Full description of the problem/report:
I have an ATA/100 controller card in a PCI slot, and an ATA/100 drive
hanging off it. Under
19 matches
Mail list logo
