From: Steve Roemen <stever@carlislefsp.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
iss_storagedev@hp.com, mike.miller@hp.com
Subject: Re: 2.6.19-git20 cciss: cmd f7b00000 timedout
Date: Thu, 14 Dec 2006 13:38:36 -0600 [thread overview]
Message-ID: <4581A83C.2090803@carlislefsp.com> (raw)
In-Reply-To: <20061214185112.GG5010@kernel.dk>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
2.6.19 does the same thing, except it's a cmd f7f00000 timedout error.
2.6.18 works just fine though.
Steve
Jens Axboe wrote:
> On Thu, Dec 14 2006, Steve Roemen wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> All,
>> I tried out the 2.6.19-git20 kernel on one of my machines (HP
>> DL380 G3) that has the on board 5i controller (disabled),
>> 2 smart array 642 controllers.
>>
>> I get the error (cciss: cmd f7b00000 timedout) with Buffer I/O error
>> on device cciss/c (all cards, and disks) logical block 0, 1, 2, etc
>
> I saw this on another box, but it works on the ones that I have. Does
> 2.6.19 work? Any chance you can try and narrow down when it broke?
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFgag7cA4cgQlZoQ8RAiXhAJ9eRe0Nh3JqFKO2H6iYKmxsVIKGDACgrCrx
QWG2sAQH4bL8+fa5mPnVhnM=
=DxGc
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-12-14 19:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-14 18:34 2.6.19-git20 cciss: cmd f7b00000 timedout Steve Roemen
2006-12-14 18:51 ` Jens Axboe
2006-12-14 19:38 ` Steve Roemen [this message]
[not found] ` <4581A748.5070509@carlislefsp.com>
2006-12-14 19:43 ` Jens Axboe
2006-12-14 19:44 ` Miller, Mike (OS Dev)
2006-12-14 20:13 ` Steve Roemen
2006-12-14 20:32 ` Miller, Mike (OS Dev)
2006-12-14 20:21 ` Jens Axboe
2006-12-14 21:12 ` dann frazier
2006-12-14 22:16 ` Miller, Mike (OS Dev)
2006-12-14 22:22 ` Steve Roemen
2006-12-15 0:59 ` dann frazier
2006-12-15 8:12 ` Jens Axboe
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=4581A83C.2090803@carlislefsp.com \
--to=stever@carlislefsp.com \
--cc=iss_storagedev@hp.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@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 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.