From: Vid Strpic <strpic@bofhlet.net>
To: Linux Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: 2.2.18 dies on my 486..
Date: Fri, 29 Dec 2000 09:14:47 +0100 [thread overview]
Message-ID: <20001229091447.A4283@localhost> (raw)
In-Reply-To: <E14BSuz-00038b-00@the-village.bc.nu> <Pine.LNX.4.31.0012281859360.802-200000@asdf.capslock.lan>
In-Reply-To: <Pine.LNX.4.31.0012281859360.802-200000@asdf.capslock.lan>; from mharris@opensourceadvocate.org on Thu, Dec 28, 2000 at 07:09:34PM -0500
On Thu, Dec 28, 2000 at 07:09:34PM -0500, Mike A. Harris wrote:
> On Thu, 28 Dec 2000, Alan Cox wrote:
> >What hardware config, what hdparm tuning options ?
> AMD 486-DX2/66 12Mb RAM, ALi 14xx chipset. Using 2.2.18 stock
> and also 2.2.18+IDE.
>
> hdparm settings:
>
> /dev/hdb:
> multcount = 8 (on)
> I/O support = 1 (32-bit)
> unmaskirq = 0 (off)
> using_dma = 0 (off)
> keepsettings = 0 (off)
> nowerr = 0 (off)
> readonly = 0 (off)
> readahead = 8 (on)
> geometry = 827/32/63, sectors = 1667232, start = 0
>
> Model=Maxtor 7850 AR, FwRev=UA7X6059, SerialNo=P60133LS
> Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>5Mbs FmtGapReq }
> RawCHS=1654/16/63, TrkSize=0, SectSize=0, ECCbytes=11
> BuffType=3(DualPortCache), BuffSize=64kB, MaxMultSect=8, MultSect=8
> DblWordIO=yes, OldPIO=2, DMA=yes, OldDMA=1
> CurCHS=1654/16/63, CurSects=1889533977, LBA=yes, LBAsects=1667232
> tDMA={min:150,rec:150}, DMA modes: sword0 sword1 *sword2 *mword0
> IORDY=on/off, tPIO={min:240,w/IORDY:180}, PIO modes: mode3
>
> I am thinking possible hardware failure, but I havent spent time
> yet trying to narrow it down.
I think it's probably a hardware issue, yes. I've seen several Maxtors
doing just this kind of stuff before ... I have one @ork which gives
this kind of errors if I put the box sideways - if it stays upright, no
problems :)
> No special lilo options or any tweaking going on on this machine
> other than hdparm..
Well, have you tried setting 32-bit support to '0'? Just for hdb,
first, if that doesn't help, for hda and hdc also.
It happened to me on one machine (486 also, just one Quantum) but
inexplainably sometimes. On other occasions all is well.
--
)) Vid Strpic, IRC:Martin, strpic@bofhlet.net, /bin/zsh.
(( (I don't speak for my employer, just for myself.)
C|~~| UNIX fundamentalist - and an average chauvinistic male.
`--'
C>N>K Never anger a dragon, for you are crunchy and good with ketchup.
-
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/
prev parent reply other threads:[~2000-12-29 9:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-28 1:05 2.2.18 dies on my 486 Mike A. Harris
2000-12-28 1:13 ` Andreas Dilger
2000-12-28 2:15 ` Mike A. Harris
2000-12-28 2:35 ` Alan Cox
2000-12-29 0:09 ` Mike A. Harris
2000-12-29 8:14 ` Vid Strpic [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=20001229091447.A4283@localhost \
--to=strpic@bofhlet.net \
--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