Subject: Re: [SCSI] Driver Broken in 2.6.x (attemp 2)
From: James Bottomley <James.Bottomley@SteelEye.com>
To: |TEcHNO| <techno@punkt.pl>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
       SCSI Mailing List <linux-scsi@vger.kernel.org>
In-Reply-To: <4252CA25.70803@punkt.pl>
References: <4252CA25.70803@punkt.pl>
Content-Type: text/plain
Date: Tue, 05 Apr 2005 12:48:23 -0500
Message-Id: <1112723304.6463.17.camel@mulgrave>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1223
Lines: 26

On Tue, 2005-04-05 at 19:25 +0200, |TEcHNO| wrote:
> 	This is my second attemp to make anyone notice the bug that is in the 
> 2.6.x tree. While many people tried to put blame on nvidia, here's a log 
> that shows that it's purely kernel fault not to work.
> 	At the end of this mail you can find some logs which show how 2.4.x and 
> 2.6.x kernels work with my card. I hope now someone can really  show 
> intrest into this, it's a shame something in 2.4.x worked (not perfect 
> but worked), and fails completely (system hang) in 2.6.x.
> 	It's also not nice if the system hangs (in 2.4.x) for a few seconds 
> while getting a preview (form the scanner), and gets jaggy and useless 
> while scanning, a userspace app (runned form normal user) shoudl not do 
> so, and it's not using more than 20% of CPU.

I don't think anyone has the actual hardware, without which it's quite
difficult to fix the problem.

What was the last 2.6 kernel version that this worked with?

James


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/