From: Emilio Recio <polywog@navpoint.com>
To: Henning Schroeder <hgs@anna-strasse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VT8367 [KT266] and high IDE load crashes
Date: Sun, 28 Apr 2002 22:02:08 -0400 [thread overview]
Message-ID: <3CCCA9A0.70807@navpoint.com> (raw)
In-Reply-To: <19984436483.20020428183713@anna-strasse.de>
[-- Attachment #1: Type: text/plain, Size: 734 bytes --]
Henning Schroeder wrote:
> Hello,
>
> I have an ASUS A7V266-E Mainboard (VT8367 [KT266] Chipset, with VIA
> IDE and Promise 20265 IDE Controller on board) that keeps crashing
> under high IDE load. Athlon XP2000+ cpu, 1.5GiB DDR-RAM.
This is the same problem that I have attempted to report with regards to the
Athlon processors. It's especially nasty when you mix scsi modules + the ide
stuff. I hard compiled everything into the kernel before, but I still have
problems.
Just now my computer crashed when I was attempting to mount my floppy drive.
In fact, it crashes all the time (when in X) when I attempt to mount my floppy
drive during or after high IDE activity.
See attached messages for more information.
-Elmo
[-- Attachment #2: imap-message://erecio@polywog.navpoint.com/MailingLists/linux-kernel#966 --]
[-- Type: message/rfc822, Size: 2747 bytes --]
From: Richard Ems <r.ems.home@gmx.net>
To: Andre Hedrick <andre@linux-ide.org>, linux-kernel@vger.kernel.org
Subject: Re: AMD Athlon + VIA Crashing On Disk I/O
Date: Sat, 20 Apr 2002 19:15:20 +0200
Message-ID: <3CC1A228.2B9C72F6@gmx.net>
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[-- Attachment #3: imap-message://erecio@polywog.navpoint.com/MailingLists/linux-kernel#213 --]
[-- Type: message/rfc822, Size: 3626 bytes --]
From: Andre Hedrick <andre@linux-ide.org>
To: Josh McKinney <forming@comcast.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: AMD Athlon + VIA Crashing On Disk I/O
Date: Tue, 16 Apr 2002 20:47:49 -0700 (PDT)
Message-ID: <Pine.LNX.4.10.10204162039350.11230-100000@master.linux-ide.org>
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 majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[-- Attachment #4: imap-message://erecio@polywog.navpoint.com/MailingLists/linux-kernel#210 --]
[-- Type: message/rfc822, Size: 4257 bytes --]
From: Emilio Recio <polywog@navpoint.com>
To: Martin Eriksson <nitrax@giron.wox.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: AMD Athlon + VIA Crashing On Disk I/O
Date: Tue, 16 Apr 2002 23:14:02 -0400
Message-ID: <3CBCE87A.2080905@navpoint.com>
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2002-04-29 1:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-28 16:37 VT8367 [KT266] and high IDE load crashes Henning Schroeder
2002-04-29 2:02 ` Emilio Recio [this message]
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=3CCCA9A0.70807@navpoint.com \
--to=polywog@navpoint.com \
--cc=hgs@anna-strasse.de \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox