linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Mike Miller <mike.miller@hp.com>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: cciss broken with 2.6.22-rc2
Date: Tue, 29 May 2007 14:01:23 +0200	[thread overview]
Message-ID: <465C1613.4050600@suse.de> (raw)

Hi Mike,

with the latest git snapshot the cciss driver hangs during
initialisation. Enabling debug output I get:

cciss0: <0x3230> at PCI 0000:06:00.0 IRQ 4338 using DAC
Sending cff0000 - down to controller
cciss:  FIFO Empty read
cciss:  Read cff00000 back from board
Sending cff0000 - down to controller
cciss:  FIFO Empty read
cciss:  Read cff00002 back from board
LUN Data
--------------------------
Sending cff0000 - down to controller
cciss:  FIFO Empty read
cciss:  Read cff00000 back from board
      blocks= 286677120 block_size= 512
Sending cff0000 - down to controller
cciss:  FIFO Empty read
cciss:  Read cff00002 back from board
      heads=255, sectors=32, cylinders=35132

Sending 5103000 - down to controller

and then the machine hangs.
I'll try to investigate, but as I'm no expert in cciss my results might
be limited.
Looks like one of your recent fixes broke it; 2.6.21 worked fine.

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)
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2007-05-29 12:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-29 12:01 Hannes Reinecke [this message]
2007-05-29 15:36 ` cciss broken with 2.6.22-rc2 Miller, Mike (OS Dev)
2007-05-30 11:50   ` Hannes Reinecke

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=465C1613.4050600@suse.de \
    --to=hare@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mike.miller@hp.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).