From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: John W Fort <johnf@whitsunday.net.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Patch-2.5.45-ac1 inia100 compile and run problems
Date: 05 Nov 2002 11:01:51 +0000 [thread overview]
Message-ID: <1036494111.4791.11.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <etkesucpk7plmukbdvmsa4gbs2f4rng1oa@4ax.com>
On Tue, 2002-11-05 at 05:16, John W Fort wrote:
> Trivial bits from 2.5.45-ac1 compile:
> drivers/scsi/inia100.h:78: warning: `inia100_detect' declared `static' but never defined
> drivers/scsi/inia100.h:79: warning: `inia100_release' declared `static' but never defined
> drivers/scsi/inia100.h:80: warning: `inia100_queue' declared `static' but never defined
> drivers/scsi/inia100.h:81: warning: `inia100_abort' declared `static' but never defined
> drivers/scsi/inia100.h:82: warning: `inia100_device_reset' declared `static' but never defined
> drivers/scsi/inia100.h:83: warning: `inia100_bus_reset' declared `static' but never defined
>
These should be little things because of the way the include is used
> Incorrect number of segments after building list
> counted 17, received 16
> req nr_sec 256, cur_nr_sec 8
> end request: I/O error, dev 08:10 sector 6685776
>
> and then hangs the bus.
> Would it be because there is no 'eh_host_reset_handler'?
No thats because something much nastier has occurred - you've got some
kind of block/scsi layer structure corruption. Most probably there is a
path where we called ->done(cmd) without holding the host lock
> The first run both drives reported similar I/O errors.
> Works fine with 'patch-2.5.45' from Linus.
> How can I help?
I'll go and review the changes. It looks like a locking error.
prev parent reply other threads:[~2002-11-05 10:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-05 5:16 John W Fort
2002-11-05 11:01 ` Alan Cox [this message]
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=1036494111.4791.11.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=johnf@whitsunday.net.au \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®