From: Jamie Lenehan <lenehan@twibble.org>
To: Andrew Schulman <andrex@alumni.utexas.net>
Cc: linux-scsi@vger.kernel.org, dc395x@twibble.org
Subject: Re: dc395x: CD writer causes endless "sg_to_virt failed" loop
Date: Tue, 30 Mar 2004 13:51:15 +1000 [thread overview]
Message-ID: <20040330035115.GA3680@twibble.org> (raw)
In-Reply-To: <200403282303.02146.andrex@alumni.utexas.net>
On Sun, Mar 28, 2004 at 11:03:02PM -0500, Andrew Schulman wrote:
[...]
> Tried it with 2.6.5-rc2. Now 'modprobe dc395x' hangs (though without all of
> the 'sg_to_virt failed' messages) as the drive keeps spinning. 'reboot' also
Yeah, it's no longer getting to where you were having problems previously.
> eventually hangs, and again I need to hit the case reset button to get back
> to normal. syslog shows "Unable to handle kernel NULL pointer dereference"--
> see excerpt below. I'll try the debugging and send you a log soon.
This is an unrelated problem. It's something to do with scsi tape sysfs
support and it looks like a fix for this problem went in just after
2.6.5-rc2 was released (patch-2.6.5-rc2-bk2.bz2).
So you could wait for 2.6.5-rc3/2.6.5 to be released, upgrade to
2.6.5-rc3-bkx (where bkx is a bk snapshot with x >=2), or go back to the
kernel you were using previously but copy the drivers/scsi/dc395x.c and
drivers/scsi/dc395x.h from the 2.6.5-rc2 kernel into it.
--
Jamie Lenehan <lenehan@twibble.org>
next prev parent reply other threads:[~2004-03-30 3:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-27 14:57 dc395x: CD writer causes endless "sg_to_virt failed" loop Andrew Schulman
2004-03-27 16:10 ` Jamie Lenehan
2004-03-29 4:03 ` Andrew Schulman
2004-03-30 3:51 ` Jamie Lenehan [this message]
2004-03-31 8:29 ` Andrew Schulman
[not found] ` <200403271759.08361.andrex@alumni.utexas.net>
2004-04-05 5:20 ` Andrew Schulman
2004-04-06 14:01 ` Jamie Lenehan
2004-04-06 16:06 ` Andrew Schulman
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=20040330035115.GA3680@twibble.org \
--to=lenehan@twibble.org \
--cc=andrex@alumni.utexas.net \
--cc=dc395x@twibble.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.