Is the "ciss" driver unmaintained? (For HP RAID/HBA cards)

[Peter Eriksson]

Thanks. I hope someone steps forward. I’d love to have some interaction with someone soon… :-)

For the moment I have a test server (running 12.1-STABLE, but if needed I could boot it with a 13-CURRENT kernel on it to test stuff) set up with two HP H241 SmartHBA controllers and three HP D6020 70-drive JBOD external cabinets attached (two of the D6020:s are connected to one controller so I can test with 140 12TB drives on one controller right now, the third D6020 only have 10 drives or so). 

However, I’ll have to move the fully equipped ones to production servers sometime in the near future and then it’ll be more difficult to test stuff...

- Peter

> On 2 Jun 2020, at 05:04, Rodney W. Grimes <freebsd-rwg at gndrsh.dnsmgr.net> wrote:
> 
>> On Mon, Jun 01, 2020 at 11:39:36PM +0200, Peter Eriksson wrote:
>>> I submitted a couple of bug reports (and patches) for the ?ciss? driver about a month ago but it seems there is no response to it?
>>> 
>>>  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279>
>>> 
>>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246280 <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246280>
>>> 
>>> Now I can run a locally built kernel but I prefer to stay away from that if possible so would really like to have it merged into the official release (if possible) in the long run.
>>> 
>>> Is there some way to find out who (if anyone) is responsible for that part of the kernel? Or should I just assume it?s abandoned and try to submit a fix somewhere else? And if so how?
>>> 
>>> - Peter
>>> 
>> 
>> Hi Peter,
>> 
>> I'm not yet a commiter, so I can't speak on behalf of those that are - but when 
>> working on documentation for man-pages I tend to following procedure:
>> 
>> To start with the first thing I do is look in src/MAINTAINERS or, failing that, 
>> see who last had a good set of commits going for the chunk of code that's being 
>> touched - and then simply try reaching out to them.
>> 
>> If you have a patch prepared that applies against the head of the tree, and on 
>> top of that if it's build and runtime tested in production, that at least mean 
>> you've done everything that can be reasonably expected.
>> 
>> Who knows, you may be in luck that someone who's interested might read hackers@ 
>> too. :)
> 
> It looks like these bugs have not been triaged by bugmaster@ they
> are still on the incomping bugs@ mail list.  But after a quick read
> of them I boldly stuck imp@ on them who is probably the person most
> knowing about the cam layer and large storage arrays.
> 
> He can slap my hand later...
> 
>> Yours,
>> Daniel Ebdrup Jensen
> 
> -- 
> Rod Grimes                                                 rgrimes at freebsd.org <mailto:rgrimes at freebsd.org>
> _______________________________________________
> freebsd-hackers at freebsd.org <mailto:freebsd-hackers at freebsd.org> mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers <https://lists.freebsd.org/mailman/listinfo/freebsd-hackers>
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at freebsd.org <mailto:freebsd-hackers-unsubscribe at freebsd.org>"