All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: "Sven Köhler" <skoehler@upb.de>,
	"James Bottomley" <James.Bottomley@SteelEye.com>,
	"Matthew Wilcox" <matthew@wil.cx>
Cc: linux-scsi <linux-scsi@vger.kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [BUG?] GDTH driver not working after upgrade to 2.6.24
Date: Thu, 31 Jan 2008 14:35:49 +0200	[thread overview]
Message-ID: <47A1C0A5.7090303@panasas.com> (raw)
In-Reply-To: <47A1ABF8.4050408@upb.de>

On Thu, Jan 31 2008 at 13:07 +0200, Sven Köhler <skoehler@upb.de> wrote:
>> Yes the gdth driver passed an open hart surgery in kernel 2.6.24. The bad thing
>> about it is that all three of the Coders that did that did not have any HW to work
>> on. One of them is me. We did cry for tester for a long time but no one came forward.
> 
> All i'd like to ask is WHY!?
> WHY such a big open heart surgery?
> OK, you have your reasons.
> 
>> Could you test patches for us? first thing would be to enable debug output patch below.
> 
> The machine is still production. It will be replaced by a 64bit system 
> with an AACRAID card some time in the future. Then, i could maybe test 
> patches on the old machine. But unfortunatly, it's not my machine. It's 
> just administrated by me. And i don't know, what's exactly is the future 
> of it.
> 
>> If you absolutely need a 2.6.24 kernel, + gdth in a production system you could
>> checkout the 2.6.23 driver and compile. The old driver will work the same in 2.6.24.
>> It will not however even compile in 2.6.25-rcx.
> 
> I see. Thanks for the hint. Would be an alternative. Actually, i don't 
> need 2.6.24 - but if something security related is fixed, then i'm not 
> able to move on to 2.6.24. And i'm using Gentoo. There's not really a 
> kernel maintained by the distribution.
> 
>> If any one wants to send me a card that uses the gdth driver, I will be very happy
>> to debug this card, and return it once I'm done.
> 
> I don't think, it's a seperate card, that i could send you. It's some 
> 19" rack server with such a card on-board, i think.
> 
> 
> So it don't see much opportunity for me to test patched and stuff :-(
> 

Thanks, Perhaps someone else then. 
Anyone with gdth HW that can test patches?
Your lspci said: "Intel Corporation RAID Controller" Matthew
is there a gdth card lying around in an Intel lab near you?

James do we need to mark gdth BROKEN for 2.6.24 and higher?

Boaz
-
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

WARNING: multiple messages have this Message-ID (diff)
From: Boaz Harrosh <bharrosh@panasas.com>
To: "Sven Köhler" <skoehler@upb.de>,
	"James Bottomley" <James.Bottomley@SteelEye.com>,
	"Matthew Wilcox" <matthew@wil.cx>
Cc: linux-scsi <linux-scsi@vger.kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [BUG?] GDTH driver not working after upgrade to 2.6.24
Date: Thu, 31 Jan 2008 14:35:49 +0200	[thread overview]
Message-ID: <47A1C0A5.7090303@panasas.com> (raw)
In-Reply-To: <47A1ABF8.4050408@upb.de>

On Thu, Jan 31 2008 at 13:07 +0200, Sven Köhler <skoehler@upb.de> wrote:
>> Yes the gdth driver passed an open hart surgery in kernel 2.6.24. The bad thing
>> about it is that all three of the Coders that did that did not have any HW to work
>> on. One of them is me. We did cry for tester for a long time but no one came forward.
> 
> All i'd like to ask is WHY!?
> WHY such a big open heart surgery?
> OK, you have your reasons.
> 
>> Could you test patches for us? first thing would be to enable debug output patch below.
> 
> The machine is still production. It will be replaced by a 64bit system 
> with an AACRAID card some time in the future. Then, i could maybe test 
> patches on the old machine. But unfortunatly, it's not my machine. It's 
> just administrated by me. And i don't know, what's exactly is the future 
> of it.
> 
>> If you absolutely need a 2.6.24 kernel, + gdth in a production system you could
>> checkout the 2.6.23 driver and compile. The old driver will work the same in 2.6.24.
>> It will not however even compile in 2.6.25-rcx.
> 
> I see. Thanks for the hint. Would be an alternative. Actually, i don't 
> need 2.6.24 - but if something security related is fixed, then i'm not 
> able to move on to 2.6.24. And i'm using Gentoo. There's not really a 
> kernel maintained by the distribution.
> 
>> If any one wants to send me a card that uses the gdth driver, I will be very happy
>> to debug this card, and return it once I'm done.
> 
> I don't think, it's a seperate card, that i could send you. It's some 
> 19" rack server with such a card on-board, i think.
> 
> 
> So it don't see much opportunity for me to test patched and stuff :-(
> 

Thanks, Perhaps someone else then. 
Anyone with gdth HW that can test patches?
Your lspci said: "Intel Corporation RAID Controller" Matthew
is there a gdth card lying around in an Intel lab near you?

James do we need to mark gdth BROKEN for 2.6.24 and higher?

Boaz

  reply	other threads:[~2008-01-31 12:36 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-30 19:47 [BUG?] GDTH driver not working after upgrade to 2.6.24 Sven Köhler
2008-01-31 10:08 ` Boaz Harrosh
2008-01-31 10:08   ` Boaz Harrosh
2008-01-31 11:07   ` Sven Köhler
2008-01-31 12:35     ` Boaz Harrosh [this message]
2008-01-31 12:35       ` Boaz Harrosh
2008-01-31 16:39       ` Jan Engelhardt
2008-01-31 16:52         ` Boaz Harrosh
2008-02-12 17:30   ` [BUGFIXES 0/2] gdth: fix 2.6.24 driver breakage Boaz Harrosh
2008-02-12 17:30     ` Boaz Harrosh
2008-02-12 17:35     ` [BUGFIX 1/2] gdth: scan for scsi devices Boaz Harrosh
2008-02-12 17:35       ` Boaz Harrosh
2008-02-12 18:05       ` Christoph Hellwig
2008-02-12 17:40     ` [BUGFIX 2/2] gdth: bugfix for the Timer at exit crash Boaz Harrosh
2008-02-13  7:06       ` Stefan Priebe - allied internet ag
2008-02-13  9:03         ` Boaz Harrosh
2008-02-13 19:38           ` Jan Engelhardt
2008-02-14 15:58             ` Boaz Harrosh
2008-02-13 10:48       ` Boaz Harrosh
2008-02-13 15:44       ` James Bottomley
2008-02-13 15:54         ` Boaz Harrosh
2008-02-13 16:33           ` Boaz Harrosh
2008-02-13 16:35             ` [PATCH ver2] gdth: bugfix for the at-exit problems Boaz Harrosh
2008-02-13 16:45             ` [BUGFIX 2/2] gdth: bugfix for the Timer at exit crash James Bottomley
2008-02-13 16:50               ` Boaz Harrosh
2008-02-13 17:03                 ` James Bottomley
2008-02-13 17:12                   ` Boaz Harrosh
2008-02-13 17:36                     ` James Bottomley
2008-02-14 10:49                       ` Boaz Harrosh
2008-02-14 11:58                         ` [PATCH] gdth: bugfix for the at-exit problems Boaz Harrosh
2008-02-14 16:10                           ` James Bottomley
2008-02-14 16:18                             ` Boaz Harrosh
2008-02-13 17:18                   ` [BUGFIX 2/2] gdth: bugfix for the Timer at exit crash Boaz Harrosh
2008-02-13 17:33                     ` James Bottomley
2008-02-14  6:51                   ` Christoph Hellwig

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=47A1C0A5.7090303@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=skoehler@upb.de \
    /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.