From: safemode <safemode@voicenet.com>
To: Zdenek Kabelac <kabi@fi.muni.cz>
Cc: xOr <xor@x-o-r.net>, linux-kernel@vger.kernel.org
Subject: Re: lockups from heavy IDE/CD-ROM usage
Date: Thu, 21 Dec 2000 15:00:16 -0500 [thread overview]
Message-ID: <3A426150.1545FC96@voicenet.com> (raw)
In-Reply-To: <Pine.LNX.4.31.0012210421450.284-100000@bitch.x-o-r.net> <3A41FFD8.531DF534@fi.muni.cz>
[-- Attachment #1: Type: text/plain, Size: 1740 bytes --]
Zdenek Kabelac wrote:
> > Problem: When i am using my harddrive and cdrom, my computer will freeze.
> > It freezes in two different ways.. sometimes just the harddrive access
> > will freeze (can still do things in X as long as they dont require the
> > harddrive), and then everything freezes within a few seconds. or else
> > everything just locks instntly. the problem is reproducable, all i need to
> > do is be using the harddrive extensively for a couple separate functions
> > (like compiling the kernel, and copying a large file) and ripping cd audio
> > (cd paranoia) and i can lock the system in as little as seconds, or a few
> > minutes sometimes. This will happen more reliably, and much quicker and
>
> This is really very similar to my problem with BP6 I'm reporting for a
> long long time.
> But everyone says its faulty board.
>
> For BP6 somehow helps to set UDMA to mode 2.
> (I'm not getting these locks when I'm just using ATA33 controler)
> (hdparm -X66 /dev/hdX)
>
> Also could you look at what is being written to console ?
> (run those intesive programs and stay on console - BP6 lock with
> this message displayed:
>
> hdf: timeout waiting for DMA
> ide_dmaproc: chipset supported ide_dma_timeout: func only 14
>
> In this point it looks like timers are dead... :(
> And the situation is the same with SMP & NoSMP kernel with apic &
> noapic.
>
I get this on the 440LX with the same DMA timeout message. Everyone says it's
the board's fault as well. Funny. Anyways this happens accross just about
any Dev kernel but more so in the -test12 and up versions. . Test10 works
fine without locking. Blaming the hardware reminds me of the help given by
some other company I can't seem to remember the name to.
[-- Attachment #2: Type: text/html, Size: 1988 bytes --]
next prev parent reply other threads:[~2000-12-21 20:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-21 10:35 lockups from heavy IDE/CD-ROM usage xOr
2000-12-21 13:04 ` Zdenek Kabelac
2000-12-21 20:00 ` safemode [this message]
2000-12-21 20:19 ` Blow Torch (Re: lockups from heavy IDE/CD-ROM usage) Andre Hedrick
2000-12-21 20:43 ` Richard B. Johnson
2000-12-21 21:44 ` lockups from heavy IDE/CD-ROM usage Daniel Stone
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=3A426150.1545FC96@voicenet.com \
--to=safemode@voicenet.com \
--cc=kabi@fi.muni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=xor@x-o-r.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.