Hiya,
I have an AMD Athlon 1.2 with a VIA 8259A Chipset (see bottom). If I
compile the kernel with the Athlon option it crashes all the time. In
fact, I can't even get Redhat 7.2 installed without a core dump when it
tries to mount the filesystem. With the later kernels, it doesn't core
dump, but just freezes.
IE: If I have ide-scsi module loaded, and I try to access the floppy
drive, it locks up the machine (regardless of whether cputype is Athlon
or K6.)
IE: Updatedb locks up the machine.
I get (when FSCK):
spurious 8259A IRQ7
Does anyone know if there's a bug fix for this chipset? My board is
made from FIC (crappy, instructions don't even matchup). I used to be
able to fix it by changing the CPU type to K6 but that doesn't work now
with the later kernels (2.4.15 and up.)
5000-500f : VIA Technologies, Inc. VT82C686 [Apollo Super ACPI]
6000-607f : VIA Technologies, Inc. VT82C686 [Apollo Super ACPI]
c000-c00f : VIA Technologies, Inc. Bus Master IDE
--
Best Regards,
E. M. Recio
****************************************************
* Email: < [email protected] > ICQ: < 458043 > *
* Homepage: < http://polywog.navpoint.com > *
****************************************************
On 16 April 2002 11:28, E M Recio wrote:
> Hiya,
>
> I have an AMD Athlon 1.2 with a VIA 8259A Chipset (see bottom). If I
> compile the kernel with the Athlon option it crashes all the time. In
> fact, I can't even get Redhat 7.2 installed without a core dump when it
> tries to mount the filesystem. With the later kernels, it doesn't core
> dump, but just freezes.
Kernel version?
> IE: If I have ide-scsi module loaded, and I try to access the floppy
> drive, it locks up the machine (regardless of whether cputype is Athlon
> or K6.)
>
> IE: Updatedb locks up the machine.
>
> I get (when FSCK):
>
> spurious 8259A IRQ7
cat /proc/interrupts, is ther lots of ERR: interrupts?
> Does anyone know if there's a bug fix for this chipset? My board is
> made from FIC (crappy, instructions don't even matchup). I used to be
> able to fix it by changing the CPU type to K6 but that doesn't work now
> with the later kernels (2.4.15 and up.)
Try to compile for 486.
--
vda
----- Original Message -----
From: "E M Recio" <[email protected]>
To: <[email protected]>
Sent: Tuesday, April 16, 2002 3:28 PM
Subject: AMD Athlon + VIA Crashing On Disk I/O
> Hiya,
>
> I have an AMD Athlon 1.2 with a VIA 8259A Chipset (see bottom). If I
> compile the kernel with the Athlon option it crashes all the time. In
> fact, I can't even get Redhat 7.2 installed without a core dump when it
> tries to mount the filesystem. With the later kernels, it doesn't core
> dump, but just freezes.
>
> IE: If I have ide-scsi module loaded, and I try to access the floppy
> drive, it locks up the machine (regardless of whether cputype is Athlon
> or K6.)
>
> IE: Updatedb locks up the machine.
>
> I get (when FSCK):
>
> spurious 8259A IRQ7
This is not the VIA chipset, it's the "8259A interrupt controller".
> Does anyone know if there's a bug fix for this chipset? My board is
> made from FIC (crappy, instructions don't even matchup). I used to be
> able to fix it by changing the CPU type to K6 but that doesn't work now
> with the later kernels (2.4.15 and up.)
First check out what kind of chipset you really have;
lspci -xs 0:0
should do the thing. Post the results.
In the meantime, you can try to compile for
"Pentium-Pro/Celeron/Pentium-II", and check your BIOS settings one more time
(set stuff to "safe" values). Also, do you have a really recent kernel, such
as 2.4.18? There were some changes in the Athlon/VIA "quirks" department a
while ago, but after 2.4.15 (i think).
_____________________________________________________
| Martin Eriksson <[email protected]>
| MSc CSE student, department of Computing Science
| Ume? University, Sweden
hi,
>>I get (when FSCK):
>>
>>spurious 8259A IRQ7
I also get this message every time i boot my machine when the fs are
mounted. but i don't had a machine lock yet.
Configuration: Athlon 1GHz on a VIA chip (ASUS A7V).
Btw. What does this message say?
> First check out what kind of chipset you really have;
> lspci -xs 0:0
> should do the thing. Post the results.
Kernel is 2.4.19pre5
my result is:
00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133]
(rev 02)
00: 06 11 05 03 06 00 10 22 02 00 00 06 00 08 00 00
10: 08 00 00 e4 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 33 80
30: 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00
I hope you can do s.th. with that.
Regards,
Michael
------------------------------------------------------
do you want to rock?
http://www.rocklinux.org/
------------------------------------------------------
Hi Michael!
On: Tue, 16 Apr 2002 23:44:34 +0000,
Michael Obster <[email protected]> wrote:
> hi,
>
> >>I get (when FSCK):
> >>
> >>spurious 8259A IRQ7
>
> I also get this message every time i boot my machine when the fs are
I also get this on all machines since arround 2.4.5(+-5) or so! It
doesn't matter if ALI Super7 + K6-2, SiS 630 + Celeron, Intel BX + PII
or SiS 730 + Athlon XP ...
But non machine has looked up, oopsed or crashed so far ...
k33p h4ck1n6
Ren?
--
Ren? Rebe (Registered Linux user: #248718 <http://counter.li.org>)
eMail: [email protected]
[email protected]
Homepage: http://drocklinux.dyndns.org/rene/
Anyone sending unwanted advertising e-mail to this address will be
charged $25 for network traffic and computing time. By extracting my
address from this message or its header, you agree to these terms.
----- Original Message -----
From: "Michael Obster" <[email protected]>
To: <[email protected]>
Sent: Wednesday, April 17, 2002 1:44 AM
Subject: Re: AMD Athlon + VIA Crashing On Disk I/O
> hi,
>
> >>I get (when FSCK):
> >>
> >>spurious 8259A IRQ7
>
> I also get this message every time i boot my machine when the fs are
> mounted. but i don't had a machine lock yet.
> Configuration: Athlon 1GHz on a VIA chip (ASUS A7V).
> Btw. What does this message say?
Nothing to worry about.
Interrupts which are not known where they originate from are sent to IRQ7
(per 8259A spec). It could be just about anything in your machine generating
these interrupts, and this is only a problem if it happens very often. There
were a discussion about this a while ago and the conclusion is that it
happens with just about every chipset.
>
> > First check out what kind of chipset you really have;
> > lspci -xs 0:0
> > should do the thing. Post the results.
>
> Kernel is 2.4.19pre5
>
> my result is:
> 00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133]
> (rev 02)
> 00: 06 11 05 03 06 00 10 22 02 00 00 06 00 08 00 00
> 10: 08 00 00 e4 00 00 00 00 00 00 00 00 00 00 00 00
> 20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 33 80
> 30: 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00
You should have no problem with this chipset if it is the KT133 without
onboard graphics (99% chance).
>
> I hope you can do s.th. with that.
LOL! I mistakenly read your acronym as "sh*t".
_____________________________________________________
| Martin Eriksson <[email protected]>
| MSc CSE student, department of Computing Science
| Ume? University, Sweden
On approximately Tue, Apr 16, 2002 at 09:45:43PM -0200, Denis Vlasenko wrote:
> >
> > I get (when FSCK):
> >
> > spurious 8259A IRQ7
>
> cat /proc/interrupts, is ther lots of ERR: interrupts?
>
I also get the spurious 8259A messages upon booting my Soyo Dragon+ board, KT266A chipset.
Here is the output of /proc/interrupts:
CPU0
0: 1146449 XT-PIC timer
1: 1258 XT-PIC keyboard
2: 0 XT-PIC cascade
8: 1 XT-PIC rtc
10: 10584 XT-PIC eth0
11: 0 XT-PIC es1370
12: 20 XT-PIC PS/2 Mouse
14: 17 XT-PIC ide0
15: 15193 XT-PIC ide1
NMI: 0
LOC: 1146346
ERR: 78
MIS: 0
I am just curious as to what this means, I haven't seen any real problems with the board,
except for everything wanting to go to IRQ 11, but that isn't a kernel issue.
Josh
Martin Eriksson wrote:
>First check out what kind of chipset you really have;
>lspci -xs 0:0
>should do the thing. Post the results.
>
>In the meantime, you can try to compile for
>"Pentium-Pro/Celeron/Pentium-II", and check your BIOS settings one more time
>(set stuff to "safe" values). Also, do you have a really recent kernel, such
>as 2.4.18? There were some changes in the Athlon/VIA "quirks" department a
>while ago, but after 2.4.15 (i think).
>
I think I tried the pentium stuff, but that would freeze up the computer
too (the HD light comes on, and nothing else works, not even ping(!))
But I think that was for a <=2.4.14. I should try it again.
Here's the output of lspci:
polywog:~ # lspci -xs 0:0
00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133]
(rev 03)
00: 06 11 05 03 06 00 10 22 03 00 00 06 00 08 00 00
10: 08 00 00 d0 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00
polywog:~ # lspci -xs 0:7.1
00:07.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06)
00: 06 11 71 05 07 00 90 02 06 8a 01 01 00 20 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 c0 00 00 00 00 00 00 00 00 00 00 06 11 71 05
30: 00 00 00 00 c0 00 00 00 00 00 00 00 ff 00 00 00
New news, I got up this morning and the computer was frozen again. This
time, I compiled in the kernel (not as modules) SCSI, SCSI CD, SCSI
Disk, PPA, completely removed ide-scsi stuff, compiled in ide-cdrom. So
I took ide-scsi out of the loop altogether.
polywog:~ # cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 4
model name : AMD Athlon(tm) Processor
stepping : 2
cpu MHz : 1199.714
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov
pat pse36 mmx fxsr syscall mmxext 3dnowext 3dnow
bogomips : 2392.06
Hi Josh,
I think I have an answer why the crash but I need to verify with a client
as we are seeing the same problem on various VIA boards. The good new is
we found on board that does not do this nasty. So we are doing a
component wide comparisong of settings.
It is a really cool and smart embedded server found at
http://www.nit.ca/
Cheers,
Andre Hedrick
LAD Storage Consulting Group
On Tue, 16 Apr 2002, Josh McKinney wrote:
> On approximately Tue, Apr 16, 2002 at 09:45:43PM -0200, Denis Vlasenko wrote:
> > >
> > > I get (when FSCK):
> > >
> > > spurious 8259A IRQ7
> >
> > cat /proc/interrupts, is ther lots of ERR: interrupts?
> >
>
> I also get the spurious 8259A messages upon booting my Soyo Dragon+ board, KT266A chipset.
> Here is the output of /proc/interrupts:
>
> CPU0
> 0: 1146449 XT-PIC timer
> 1: 1258 XT-PIC keyboard
> 2: 0 XT-PIC cascade
> 8: 1 XT-PIC rtc
> 10: 10584 XT-PIC eth0
> 11: 0 XT-PIC es1370
> 12: 20 XT-PIC PS/2 Mouse
> 14: 17 XT-PIC ide0
> 15: 15193 XT-PIC ide1
> NMI: 0
> LOC: 1146346
> ERR: 78
> MIS: 0
>
> I am just curious as to what this means, I haven't seen any real problems with the board,
> except for everything wanting to go to IRQ 11, but that isn't a kernel issue.
>
> Josh
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
Hi Andre, hi list!
I'm also having random lockups with an ASUS A7V266-E Mainboard, Athlon
XP 1800+.
Chipset is the VIA KT266A, kernel 2.4.18 (SuSE version 2.4.18-58, from
SuSE 8.0).
Nothing in the logs.
Andre, could you verify your possible answer? Any results?
Thanks, Richard
Andre Hedrick wrote:
>Hi Josh,
>
>I think I have an answer why the crash but I need to verify with a
client
>as we are seeing the same problem on various VIA boards. The good new
is
>we found on board that does not do this nasty. So we are doing a
>component wide comparisong of settings.
>
>It is a really cool and smart embedded server found at
>
> http://www.nit.ca/
>
>Cheers,
>
>Andre Hedrick
>LAD Storage Consulting Group
We gave up using kt266A chipset motherboards with anything faster than ATA100.
I can reproduce disk corruption within 30 seconds on any of the KT266A
motheroards we've tried that have a highpoint 370/372/372a either onboard
or on the RocketRaid133 controller.
Did not get the corruption when using ATA100 or slower (e.g. promise
fastrak 100 tx2).
Simple program that writes 1.2 gig to a file and reads them back (checking
the value) will find corruption every time on these boards, and I tried 5
motherboards (2 asus, 3 abit).
We switched to Intel I845 chipset and to AMD MPX chipset and haven't seen
the problem.
I thought this problem was linked with the VIA chipset PCI latency issue as
people were having the problem with high speed framegrabbers as well.
****************************************************
Nicolae P. Costescu, Ph.D. / Senior Developer
Stronghold Technologies
46040 Center Oak Plaza, Suite 160 / Sterling, Va 20166
Tel: 571-434-1472 / Fax: 571-434-1478