All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 15950] Hang in dc395x driver
Date: Mon, 10 May 2010 05:14:37 GMT	[thread overview]
Message-ID: <201005100514.o4A5Ebuh027931@demeter.kernel.org> (raw)
In-Reply-To: <bug-15950-11613@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=15950





--- Comment #3 from ltskinol@gmail.com  2010-05-10 05:14:36 ---
On Sun, May 9, 2010 at 6:07 PM,  <bugzilla-daemon@bugzilla.kernel.org> wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=15950
>
>
>
>
>
> --- Comment #1 from Anonymous Emailer <anonymous@kernel-bugs.osdl.org>  2010-05-09 22:07:58 ---
> Reply-To: James.Bottomley@suse.de
>
> On Sun, 2010-05-09 at 21:19 +0000, bugzilla-daemon@bugzilla.kernel.org
> wrote:
>> I'm not sure when this problem started, but it's somewhere in the 2.6.2x
>> region.
>>
>> I'd be happy to recompile, test and debug if needed.
>
> Retesting isn't necessary.  There have only been nine changes to that
> driver in 2.6.2x.  The versions of interest (as in works/doesn't work)
> should be
>
> 2.6.26 (should be identical to 2.6.31, so just a something else changed
> sanity check)
> 2.6.25 (lots of pointless changes + sense buffer replacement)
> 2.6.34 (pid removal and sg chaining)
> 2.6.23 (accessors change)
> 2.6.22 (spelling only fix!)
>
> James
>
> --
> Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
>

I downloaded the .1 versions of kernel's 2.6.22 through 2.6.26, and
found that 2.6.25 and above had no changes in the dc395x.c file, but
that a variety of changes were introduced in 2.6.24 and below.  Since
the older dc395x.c doesn't drop into my current 2.6.31 kernel, I tried
recompiling and running 2.6.24 without success.  On Gentoo, the
current udev doesn't work with that older kernel, so things like
networking and X fail to run properly and I was unable to test the
scanner.  Suggestions?

Tom

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2010-05-10  5:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-09 21:19 [Bug 15950] New: Hang in dc395x driver bugzilla-daemon
2010-05-09 21:31 ` James Bottomley
2010-05-09 22:08 ` [Bug 15950] " bugzilla-daemon
2010-05-10  4:16 ` bugzilla-daemon
2010-05-10 18:26   ` Guennadi Liakhovetski
2010-05-10  5:14 ` bugzilla-daemon [this message]
2010-05-10 20:28 ` bugzilla-daemon
2010-05-16  3:49 ` bugzilla-daemon
2013-12-10 18:29 ` bugzilla-daemon
2013-12-10 19:51 ` bugzilla-daemon
2013-12-10 20:13 ` bugzilla-daemon
2013-12-10 20:15 ` bugzilla-daemon
2013-12-10 22:15 ` bugzilla-daemon

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=201005100514.o4A5Ebuh027931@demeter.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    /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.