From: "Udo A. Steinberg" <sorisor@Hell.WH8.TU-Dresden.De>
To: Petr Vandrovec <VANDROVE@vc.cvut.cz>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: VIA silent disk corruption - bad news
Date: Tue, 06 Feb 2001 15:24:18 +0100 [thread overview]
Message-ID: <3A800912.1B77C3DB@Hell.WH8.TU-Dresden.De> (raw)
In-Reply-To: <14B049560B85@vcnet.vc.cvut.cz>
Petr Vandrovec wrote:
>
> On 5 Feb 01 at 23:08, Udo A. Steinberg wrote:
>
> > 00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 0305 (rev 02)
> > Subsystem: Asustek Computer, Inc.: Unknown device 8033
> > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> > Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium
> >TAbort- <TAbort- <MAbort+ >SERR- <PERR+
> ^^^^^^
> I tried all different settings in BIOS, and I even programmed values
> from your lspci to my VIA (except for SDRAM timmings) - and although
> it is a bit better, it is not still perfect.
> So for today I'm back on [UMS]DMA disabled. I'll try downgrading BIOS
> today, but it looks to me like that something is severely broken here.
Are your drives connected to the VIA or the Promise controller? Mine
are both connected to the PDC20265 and running in UDMA-100 mode. There
have been several threads on lkml about corruption on disks connected
to Via chipset IDE controllers, although I didn't follow them in great
detail. Maybe your problem is not related to the host bridge, but to
the IDE controller?
-Udo.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next parent reply other threads:[~2001-02-06 14:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <14B049560B85@vcnet.vc.cvut.cz>
2001-02-06 14:24 ` Udo A. Steinberg [this message]
2001-02-06 15:31 Petr Vandrovec
-- strict thread matches above, loose matches on Subject: below --
2001-02-05 19:53 Peter Horton
2001-02-05 22:02 ` Udo A. Steinberg
2001-02-05 22:08 ` Udo A. Steinberg
2001-02-06 13:48 ` Richard B. Johnson
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=3A800912.1B77C3DB@Hell.WH8.TU-Dresden.De \
--to=sorisor@hell.wh8.tu-dresden.de \
--cc=VANDROVE@vc.cvut.cz \
--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
all inboxes | Powered by JetHome®