From: joe briggs <jbriggs@briggsmedia.com>
To: dmeyer@dmeyer.net, linux-kernel@vger.kernel.org
Subject: Re: 2.4.21 IDE problems (lost interrupt, bad DMA status)
Date: Wed, 2 Jul 2003 06:34:42 -0400 [thread overview]
Message-ID: <200307020634.42705.jbriggs@briggsmedia.com> (raw)
In-Reply-To: <20030630224726.GA22579@jhereg.dmeyer.net>
Can anyone tell me what the -ac patches do with respect to this problem?
Also, what functionality is lost when CONFIG_X86_IO_APIC is not set, and
should it improve this hd timeout/lost interrupt problem?
Thanks!
On Monday 30 June 2003 06:47 pm, dmeyer@dmeyer.net wrote:
> In article <20030630221542.GA17416@alf.amelek.gda.pl> you write:
> > Hi,
> >
> > After upgrading the kernel from 2.4.20 to 2.4.21, sometimes I see
> > the following messages:
> >
> > hda: dma_timer_expiry: dma status == 0x24
> > hda: lost interrupt
> > hda: dma_intr: bad DMA status (dma_stat=30)
> > hda: dma_intr: status=0x50 { DriveReady SeekComplete }
> >
> > It happens especially when there is a lot of disk I/O (which stops
> > for a few seconds when these messages appear), with three different
> > disks (very unlikely they all decided to die at the same time...),
> > one old ATA33 (QUANTUM FIREBALL SE8.4A) and two newer ATA100 disks
> > (WDC WD300BB-32CCB0, ST340015A). IDE controller: VIA VT82C686B
> > on a MSI MS-6368L motherboard.
> >
> > I don't remember seeing anything like that in any earlier 2.4.x
> > kernels. Is this a known problem? Is this anything dangerous -
> > should I disable UDMA for now to play it safe?
>
> I never saw any corruption when I had it. I've seen this with stock
> kernels since 2.4.18 or so with ACPI and APIC enabled; with ac kernels
> I never get it (I'm suspecting the old ACPI in the stock kernels is
> the problem).
>
> So my suggestion is either turn off ACPI and/or APIC, or try
> 2.4.21-ac.
--
Joe Briggs
Briggs Media Systems
105 Burnsen Ave.
Manchester NH 01304 USA
TEL 603-232-3115 FAX 603-625-5809 MOBILE 603-493-2386
www.briggsmedia.com
next prev parent reply other threads:[~2003-07-02 9:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-30 22:15 Marek Michalkiewicz
2003-06-30 22:16 ` Alan Cox
2003-07-01 19:45 ` Marek Michalkiewicz
2003-06-30 22:39 ` Danny ter Haar
2003-06-30 22:47 ` dmeyer
2003-07-02 10:34 ` joe briggs [this message]
2003-07-02 10:00 ` Herbert Xu
2003-07-01 13:13 ` Edward King
2003-07-01 19:53 ` Marek Michalkiewicz
2003-07-21 21:57 Ronald Wahl
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=200307020634.42705.jbriggs@briggsmedia.com \
--to=jbriggs@briggsmedia.com \
--cc=dmeyer@dmeyer.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
all inboxes | Powered by JetHome®