From: Stephen Evanchik <evanchsa@clarkson.edu>
To: Manfred.Herrmann@zipptec.de
Cc: xen-devel@lists.sourceforge.net
Subject: Re: megaraid problem on hp netserver lh6000 - ignorebiostables o.k.
Date: 27 Feb 2004 22:13:40 -0500 [thread overview]
Message-ID: <1077938019.8129.38.camel@localhost> (raw)
In-Reply-To: <OF69D64430.10AF88F2-ONC1256E47.004D1AB2-C1256E47.005178F1@zipptec.de>
On Fri, 2004-02-27 at 09:46, Manfred.Herrmann@zipptec.de wrote:
> XEN1.2 democd default boot 2.4.25
> stop at ... megaraid scanning raidchannel with error:
>
> scsi0: scanning virtual channel0 for scsi devices.
> scsi_wait_req: still waiting...!
> scsi_wait_req: still waiting...!
> scsi_wait_req: still waiting...!
> scsi_wait_req: still waiting...!
> (... endless)
I can also confirm this behavior with a Dell PowerEdge, dual Xeon, 2GB
system with the MPT Fusion (LSI1030) SCSI controller.
This happens from 'time to time' with the driver I ported way back in
November. I brushed it off as a driver problem as its awful code. Of
course, we do have reports of the thing working quite well with a domain
configured sufficiently.
My machine is well within the specs too ;)
This machine has 3 SCSI controllers (aic79xx, sym83cxx_2 and the
mptfusion) and I think I only see the above when there is a drive
plugged in to the mptfusion controller.
I do have a spark of a memory creating a patch that timed out in
scsi.c:scsi_wait_req because this appeared with _NO_ drives attached and
the driver enabled.
Actually, the more I think about it the more I remeber that when this
happened something strange was going on with the DMA for the
request/reply frames.. and a quick check of some debug output confirms
that.
When this happens with the MPT Fusion controller you see this in the
initialization and subsequent commands:
http://www.clarkson.edu/~evanchsa/xen/debug/dma.txt
and then later that day I made changes to get this:
http://www.clarkson.edu/~evanchsa/xen/debug/dma.111003.txt
I now recall that I got rid of some of their PCI handling code as it was
no longer needed in the newer kernels. I think that was the change I
mentioned above.
I could be completely wrong of course ;) I'm not a pro at this by any
means.
The machine is currently being used so I'll have to schedule some time
to check in to this more.
Stephen
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
prev parent reply other threads:[~2004-02-28 3:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-27 14:46 megaraid problem on hp netserver lh6000 - ignorebiostables o.k Manfred.Herrmann
2004-02-27 16:11 ` Ian Pratt
2004-02-27 16:46 ` Manfred.Herrmann
2004-02-27 17:46 ` Ian Pratt
2004-02-27 18:14 ` Manfred.Herrmann
2004-02-27 18:42 ` Ian Pratt
2004-02-28 17:18 ` Manfred.Herrmann
2004-02-28 18:27 ` Ian Pratt
2004-02-29 10:06 ` Manfred.Herrmann
2004-03-01 23:15 ` Ian Pratt
2004-03-02 8:26 ` Manfred.Herrmann
2004-03-04 14:58 ` Steven Hand
2004-03-04 15:04 ` Steven Hand
2004-02-27 16:57 ` Keir Fraser
2004-02-27 17:44 ` Manfred.Herrmann
2004-02-27 17:47 ` Keir Fraser
2004-02-27 18:22 ` Manfred.Herrmann
2004-02-28 3:13 ` Stephen Evanchik [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=1077938019.8129.38.camel@localhost \
--to=evanchsa@clarkson.edu \
--cc=Manfred.Herrmann@zipptec.de \
--cc=xen-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.