mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hugo Mills <hugo-lkml@carfax.org.uk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Per Andreas Buer <perbu@linpro.no>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: SiI3112: problemes with shared interrupt line?
Date: Mon, 22 Sep 2003 20:59:20 +0100	[thread overview]
Message-ID: <20030922195920.GH10409@carfax.org.uk> (raw)
In-Reply-To: <1064256539.9008.13.camel@dhcp23.swansea.linux.org.uk>

[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]

On Mon, Sep 22, 2003 at 07:49:00PM +0100, Alan Cox wrote:
> Just about every bug report I have about SI3112 now is on Nforce
> chipsets. At the moment however I don't know what the magic connection
> is.

   I don't know if this comes under the heading of "SiI3112 bugs", but
Adaptec AAR-1210SA still doesn't work for me (and I've seen one other
identical report on LKML in the last fortnight).

   Any attempt to access the drive (Seagate Barracuda V) causes this
to happen:

Sep 22 20:56:00 src@vlad kernel: hda: dma_timer_expiry: dma status == 0x24
Sep 22 20:56:10 src@vlad kernel: hda: DMA interrupt recovery
Sep 22 20:56:10 src@vlad kernel: hda: lost interrupt

   Data does eventually get to/from the drive, but so slowly as to be
unusable.

   Hugo.

-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 1C335860 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
      --- In event of Last Trump,  please form an orderly queue ---      
                          and await judgement.                           

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-09-22 19:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-22 17:06 Per Andreas Buer
2003-09-22 18:49 ` Alan Cox
2003-09-22 19:59   ` Hugo Mills [this message]
2003-09-22 19:42 Allen Martin
2003-09-22 19:49 ` Per Andreas Buer
2003-09-22 19:59   ` Witold Krecicki
2003-09-22 20:35 Allen Martin

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=20030922195920.GH10409@carfax.org.uk \
    --to=hugo-lkml@carfax.org.uk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perbu@linpro.no \
    /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®