From: VDA <VDA@port.imtp.ilyichevsk.odessa.ua>
To: "Marek Mentel" <mmark@koala.ichpw.zabrze.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Athlon bug - Abit KT7E
Date: Mon, 17 Sep 2001 17:27:59 +0300 [thread overview]
Message-ID: <312430534.20010917172759@port.imtp.ilyichevsk.odessa.ua> (raw)
In-Reply-To: <200109171242.f8HCgVZ00681@koala.ichpw.zabrze.pl>
In-Reply-To: <200109171242.f8HCgVZ00681@koala.ichpw.zabrze.pl>
Hello Marek,
Glad our patch works for you.
Thanks for lspci -vvvxxx dump.
HDD DMA failure is probably unrelated to Athlon bug.
However, report anything strange you see.
Monday, September 17, 2001, 9:31:21 PM, you wrote:
MM> Abit KT7E mobo , 256 M noname RAM
MM> Duron 800 cpu
MM> processor : 0
MM> vendor_id : AuthenticAMD
MM> cpu family : 6
MM> model : 3
MM> model name : AMD Duron(tm) Processor
MM> stepping : 1
MM> cpu MHz : 800.045
MM> cache size : 64 KB
MM> fdiv_bug : no
MM> hlt_bug : no
MM> f00f_bug : no
MM> coma_bug : no
MM> fpu : yes
MM> fpu_exception : yes
MM> cpuid level : 1
MM> wp : yes
MM> flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr
MM> pge mca cmov pat pse36 mmx fxsr syscall mmxext 3dnowext 3dnow
MM> bogomips : 1595.80
MM> K7-optimized kernel works ok with bios ZT , crash with 3R bios.
MM> K7-optimized kernel + patch boot ok with 3R bios, but I have
MM> found in log :
MM> (after 20 min of work ):
MM> Sep 15 13:19:40 bulma kernel: hda: dma_intr: status=0x71 { DriveReady
MM> DeviceFaul
MM> t SeekComplete Error }
MM> Sep 15 13:19:40 bulma kernel: hda: dma_intr: error=0x10 {
MM> SectorIdNotFound }, LB
MM> Asect=9484373, sector=3604580
MM> Sep 15 13:19:40 bulma kernel: hda: DMA disabled
MM> Sep 15 13:19:40 bulma kernel: ide0: reset: success
--
Best regards, VDA
mailto:VDA@port.imtp.ilyichevsk.odessa.ua
http://port.imtp.ilyichevsk.odessa.ua/vda/
prev parent reply other threads:[~2001-09-17 14:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-17 18:31 Athlon bug - Abit KT7E Marek Mentel
2001-09-17 13:02 ` Alan Cox
2001-09-17 14:27 ` VDA [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=312430534.20010917172759@port.imtp.ilyichevsk.odessa.ua \
--to=vda@port.imtp.ilyichevsk.odessa.ua \
--cc=linux-kernel@vger.kernel.org \
--cc=mmark@koala.ichpw.zabrze.pl \
/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;
as well as URLs for NNTP newsgroup(s).