linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Heckmann <mh@nadir.org>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: Marc-Christian Petersen <m.c.p@wolk-project.de>,
	linux-kernel@vger.kernel.org
Subject: Re: UP IO-APIC fix in 2.4.22-pre?
Date: Thu, 31 Jul 2003 18:23:08 -0400	[thread overview]
Message-ID: <20030731222307.GH1661@nadir.org> (raw)
In-Reply-To: <Pine.LNX.4.55L.0307311225350.4226@freak.distro.conectiva>

hi,

the patch solves the bug for me.

-m

On Thu, Jul 31, 2003 at 12:26:58PM -0300, Marcelo Tosatti wrote:
> 
> Marc,
> 
> I just applied that patch in the 2.4 BK tree.
> 
> -pre10 will be release today with it included.
> 
> On Thu, 31 Jul 2003, Marc-Christian Petersen wrote:
> 
> > On Thursday 31 July 2003 02:28, Marc Heckmann wrote:
> >
> > Hi Marc,
> >
> > > I was just wondering about the bugfix for UP IO-APIC that is in 2.4-ac
> > > and that went into 2.5:
> > > http://linux.bkbits.net:8080/linux-2.5/cset@1.1455.1.9
> > > Will it make it into 2.4.22? From what I understand this fixes the
> > > following problem that many of us are seeing:
> > > 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 }
> >
> > I sent it to Marcelo yesterday. In the meantime you might want to try out the
> > attached patch ontop of 2.4.22-pre9 and see if it fixes the problems for you.
> >
> > ciao, Marc
> >

      parent reply	other threads:[~2003-07-31 22:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-31  0:28 UP IO-APIC fix in 2.4.22-pre? Marc Heckmann
2003-07-31  7:08 ` Marc-Christian Petersen
2003-07-31 15:26   ` Marcelo Tosatti
2003-07-31 15:45     ` Marc Heckmann
2003-07-31 18:45     ` Marc-Christian Petersen
2003-07-31 22:23     ` Marc Heckmann [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=20030731222307.GH1661@nadir.org \
    --to=mh@nadir.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.c.p@wolk-project.de \
    --cc=marcelo@conectiva.com.br \
    /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).