From: Artyom Tarasenko <atar4qemu@googlemail.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: sparc32 fix spurious dma interrupts
Date: Fri, 12 Feb 2010 23:32:22 +0100 [thread overview]
Message-ID: <fb8d4f71002121432t369ee5f6w7b39a1dee91ec7d0@mail.gmail.com> (raw)
In-Reply-To: <f43fc5581002121127g13e540c3w30dd3abf09ed70a@mail.gmail.com>
2010/2/12 Blue Swirl <blauwirbel@gmail.com>:
> On Thu, Feb 11, 2010 at 12:40 AM, Artyom Tarasenko
> <atar4qemu@googlemail.com> wrote:
>> Don't raise interrupt when not enabled.
>> Don't set DMA_INTR bit spuriously.
>> Don't print misleading debug messages "Raise IRQ" when not raising any.
>
> This breaks most of my Linux tests. *BSD are unaffected. For example
> sparc-test 2.0:
>
> eth0: LANCE 52:54:00:12:34:56
> esp0: IRQ 36 SCSI ID 7 Clk 40MHz CCYC=25000 CCF=8 TOut 167 NCR53C9XF(espfast)
> ESP: Total of 1 ESP hosts found, 1 actually in use.
> scsi0 : Sparc ESP100A-FAST
> esp0: Aborting command
> esp0: dumping state
> esp0: dma -- cond_reg<a4400311> addr<f0010e64>
> esp0: SW [sreg<11> sstep<04> ireg<18>]
> esp0: HW reread [sreg<93> sstep<00> ireg<10>]
> esp0: current command [tgt<02> lun<00> pphase<CLUELESS> cphase<DATAIN>]
> esp0: disconnected
> esp0: Aborting command
> esp0: dumping state
> esp0: dma -- cond_reg<a4400310> addr<f0010e64>
> esp0: SW [sreg<11> sstep<04> ireg<18>]
> esp0: HW reread [sreg<03> sstep<04> ireg<00>]
> esp0: current command [tgt<02> lun<00> pphase<UNISSUED> cphase<UNISSUED>]
> esp0: disconnected
> esp0: Resetting scsi bus
> esp0: SCSI bus reset interrupt
> esp0: Aborting command
> esp0: dumping state
> esp0: dma -- cond_reg<a4400211> addr<f000d007>
> esp0: SW [sreg<03> sstep<04> ireg<80>]
> esp0: HW reread [sreg<91> sstep<04> ireg<18>]
> esp0: current command [tgt<02> lun<00> pphase<UNISSUED> cphase<UNISSUED>]
> esp0: disconnected
> scsi: Device offlined - not ready after error recovery: host 0 channel
> 0 id 2 lun 0
>
> Since Open/NetBSD still works, there may be yet again another bug that
> your patch uncovers.
Looks like Linux has problems with the fist part of the patch: not
raising irqs when they are not enabled.
The part is actually not relevant for Solaris, so we could just skip
it. But it would be nicer to find this another bug.
It seems that there is some asymmetry: Solaris complained about
spurious interrupts only on write operations.
Do you have an idea why setting the DMA_INTR bit and raising the irq
was split between multiple functions?
--
Regards,
Artyom Tarasenko
solaris/sparc under qemu blog: http://tyom.blogspot.com/
next prev parent reply other threads:[~2010-02-12 22:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 22:40 [Qemu-devel] sparc32 fix spurious dma interrupts Artyom Tarasenko
2010-02-12 18:40 ` [Qemu-devel] " Artyom Tarasenko
2010-02-12 19:27 ` Blue Swirl
2010-02-12 22:32 ` Artyom Tarasenko [this message]
2010-02-13 7:52 ` Blue Swirl
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=fb8d4f71002121432t369ee5f6w7b39a1dee91ec7d0@mail.gmail.com \
--to=atar4qemu@googlemail.com \
--cc=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).