[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: troubles with DAC960



dann frazier wrote:
> On Sat, Mar 24, 2007 at 03:38:20PM +0100, Boris Andratzek wrote:
>> Hello members of the debian kernel list,
>>
>>
>> I'm new to this and hope I don't misuse the list in any way.
> 
>> Doing the update from debian sarge to etch on my server I ran into the
>> bug documented here: bugzilla.kernel.org/show_bug.cgi?id=7177
>> I already made some comments there. I tried to contact the maintainer of
>> the DAC960 driver but as far as I found out, Leonard N. Zubkoff
>> unfortunatly died in a helicopter crash.
>>
>> Without being impious, I want to ask if anybody can give me an idea of
>> how this thing will go on. Is there anybody new doing the maintaining?
> 
> hey Boris,
>  That's a question for upstream - the upstream list is here:
>    http://vger.kernel.org/vger-lists.html#linux-scsi
> 
>> Is there hope for a fix? Where can I find more information? Can I do
>> anything to help (testing, logging)?
> 
> I think the most useful information you could add to 7177 is to
> identify the specific change that broke it. The original reporter
> claims that this was broken after 2.6.11 - can you verify that 2.6.11
> worked and 2.6.12 is broken?
> 
> If you can do that, then you can try to use git bisect to identify
> the commit that changed this behavior. Since this is pre-2.6.12, you
> probably need to use the bitkeeper import git tree:
>   git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/old-2.6-bkcvs.git
> 
> Instructions for using git bisect can be found here:
>  http://dannf.org/bloggf/tech/git-bisect.html
> 
> And please contact us when there is an upstream fix so that we can
> include it in Debian.
> 

Hej Dann,

thanks for your reply, I'll try to contact the upstream list! And I will
spend some time to discover what git can do....

In the meanwhile I got mail from Andy, who told me he hat a working
system but I cannot confirm until now. More in the answer to him in this
thread.

Boris



Reply to: