public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <3CBCE87A.2080905@navpoint.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0204160921060.472-100000@polywog.navpoint.com> <00dc01c1e58b$668dd2f0$0201a8c0@homer>

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


  parent reply	other threads:[~2002-04-17  3:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-16 13:28 AMD Athlon + VIA Crashing On Disk I/O E M Recio
2002-04-16 21:12 ` Martin Eriksson
2002-04-16 23:44   ` Michael Obster
2002-04-16 22:50     ` Rene Rebe
2002-04-16 22:55     ` Martin Eriksson
2002-04-17  3:14   ` Emilio Recio [this message]
2002-04-16 23:45 ` Denis Vlasenko
2002-04-17  1:55   ` Josh McKinney
2002-04-17  3:47     ` Andre Hedrick
  -- strict thread matches above, loose matches on Subject: below --
2002-04-20 17:15 Richard Ems
2002-04-20 17:32 ` Nicolae P. Costescu

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=3CBCE87A.2080905@navpoint.com \
    --to=polywog@navpoint.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nitrax@giron.wox.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