public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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>
Subject: Re: [SCSI] Driver Broken in 2.6.x (attemp 2)
Date: Tue, 05 Apr 2005 12:48:23 -0500	[thread overview]
Message-ID: <1112723304.6463.17.camel@mulgrave> (raw)
In-Reply-To: <4252CA25.70803@punkt.pl>

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



  reply	other threads:[~2005-04-05 18:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-05 17:25 [SCSI] Driver Broken in 2.6.x (attemp 2) |TEcHNO|
2005-04-05 17:48 ` James Bottomley [this message]
2005-04-05 20:22   ` |TEcHNO|
2005-04-07 23:20   ` |TEcHNO|

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=1112723304.6463.17.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=techno@punkt.pl \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox