qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: linux-iscsi-target-dev@googlegroups.com
Cc: Kevin Wolf <kwolf@redhat.com>,
	stefanha@gmail.com, qemu-devel@nongnu.org,
	"Nicholas A. Bellinger" <nab@linux-iscsi.org>,
	kraxel@redhat.com, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] Megasas HBA emulation and SCSI update v.2
Date: Wed, 01 Dec 2010 15:18:34 +0100	[thread overview]
Message-ID: <4CF6593A.1060109@suse.de> (raw)
In-Reply-To: <1290591664.30138.216.camel@haakon2.linux-iscsi.org>

Hey Nic,

On 11/24/2010 10:41 AM, Nicholas A. Bellinger wrote:
> On Mon, 2010-11-22 at 11:34 +0100, Hannes Reinecke wrote:
[ .. ]
> 
> Hey Hannes,
> 
> Just a heads up, I noticed that the latest v2 megasas w/ scsi-generic ->
> TCM_loop appears to be broken on a Windows7 (Build 7600) guest, which
> hangs during boot -> LUN scan with the following:
> 
> truelife:/usr/src/qemu-kvm.git# ./x86_64-softmmu/qemu-system-x86_64 -m 512 -boot c ~/windows7.img \
> 		-drive if=none,id=mydisk1,file=/dev/sg4 -device megasas,id=raid
> 		-device scsi-generic,bus=raid.0,scsi-id=1,drive=mydisk1
> 
> megasas: Using 80 sges, 1000 cmds, raid mode
> megasas: Reset
> megasas: Mapping MMIO region 0 at f2040000
> megasas: Mapping IO region 2 at 0000c200
> megasas: Mapping QUEUE region 3 at f2080000
> megasas: Mapping MMIO region 0 at f2040000
> megasas: Mapping IO region 2 at 0000c200
> megasas: Mapping QUEUE region 3 at f2080000
> megasas: Mapping MMIO region 0 at f2040000
> megasas: Mapping IO region 2 at 0000c200
> megasas: Mapping QUEUE region 3 at f2080000
> megasas: readl mmio 0xb0
> megasas: writel mmio 20: 7
> megasas: Reset
> megasas: readl mmio 0x20
> megasas: writel mmio 40: 1ff9c041
> megasas: Received frame addr 1ff9c000 count 32
> megasas: MFI cmd 0 context 0 count 32
> megasas: Return new frame 0 cmd 0x7f7711654330
> megasas: Enqueue frame 0 count 32 context 0 tail 0 busy 1
> megasas: MFI init firmware: xfer len 0 pa 0
> megasas: MFI init firmware: queue at f000ff53f000e2c3 len -268370093 head f000ff53f000ff53 tail f000ff53f000ff53
> megasas: Complete frame context 0
> 
Okay, it looks as if I've fixed it up.
Win7 32bit works now with my megasas.v3 tree.
Curiously, Win7 64bit fails; it crashes at relative address
28F4, wherever that's supposed to be.
And, of course, Windows Vista with newest driver from LSI fails, too
:-(.
Guess I need to do some more debugging here.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)

  reply	other threads:[~2010-12-01 14:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-22 10:15 [Qemu-devel] [PATCH] Megasas HBA emulation and SCSI update v.2 Hannes Reinecke
2010-11-22 10:34 ` Hannes Reinecke
2010-11-24  9:41   ` Nicholas A. Bellinger
2010-12-01 14:18     ` Hannes Reinecke [this message]
2010-12-01 15:46       ` Hannes Reinecke
2010-12-02  0:14         ` Nicholas A. Bellinger
2010-12-02  7:51           ` Hannes Reinecke
2010-12-02  9:16             ` Nicholas A. Bellinger

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=4CF6593A.1060109@suse.de \
    --to=hare@suse.de \
    --cc=kraxel@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=linux-iscsi-target-dev@googlegroups.com \
    --cc=nab@linux-iscsi.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    /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).