From: Mike Christie <michaelc@cs.wisc.edu>
To: Mike Christie <michaelc@cs.wisc.edu>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Anton Blanchard <anton@samba.org>,
James Bottomley <James.Bottomley@SteelEye.com>,
Dipankar Sarma <dipankar@in.ibm.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.14-rc1] sym scsi boot hang
Date: Wed, 14 Sep 2005 11:53:45 -0500 [thread overview]
Message-ID: <43285599.9040002@cs.wisc.edu> (raw)
In-Reply-To: <4328553D.10501@cs.wisc.edu>
Mike Christie wrote:
> Alan Stern wrote:
>
>> On Wed, 14 Sep 2005, Anton Blanchard wrote:
>>
>>
>>> Hi,
>>>
>>>
>>>> If that's the cause, it's probably a double down of the host scan
>>>> semaphore somewhere in the code. alt-sysrq-t should work in this case,
>>>> can you get a stack trace of the blocked process?
>>>
>>>
>>> It appears to be this patch:
>>>
>>> [SCSI] SCSI core: fix leakage of scsi_cmnd's
>>>
>>> From: Alan Stern <stern@rowland.harvard.edu>
>>
>>
>>
>>> And in particular it looks like the scsi_unprep_request in
>>> scsi_queue_insert is causing it. The following patch fixes the boot
>>> problems on the vscsi machine:
>>
>>
>>
>> In general the scsi_unprep_request routine is correct and needs to be
>> there. The one part that might be questionable is the assignment to
>> req->special. It may turn out that the real solution is to have
>> scsi_execute set req->special to NULL; I assumed it would be NULL already
>> but perhaps I was wrong.
>
>
> I think we have scsi_execute and friends setting REQ_SPECIAL. This is
> could cause a problem becuase it does not have a scsi_request.
>
well now actually it won't becuase sc_request should be null for those
scsi_execute block pc commands I think.
next prev parent reply other threads:[~2005-09-14 16:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 12:48 [2.6.14-rc1] sym scsi boot hang Dipankar Sarma
2005-09-13 13:17 ` Anton Blanchard
2005-09-13 14:29 ` Anton Blanchard
2005-09-13 16:35 ` James Bottomley
2005-09-13 16:47 ` Anton Blanchard
2005-09-13 17:32 ` James Bottomley
2005-09-13 17:13 ` Anton Blanchard
2005-09-13 17:33 ` Dipankar Sarma
2005-09-14 8:06 ` Anton Blanchard
2005-09-14 15:49 ` Alan Stern
2005-09-14 16:52 ` Mike Christie
2005-09-14 16:53 ` Mike Christie [this message]
2005-09-14 20:35 ` James Bottomley
2005-09-14 16:57 ` James Bottomley
2005-09-14 20:19 ` Alan Stern
2005-09-14 20:44 ` James Bottomley
2005-09-14 21:33 ` Alan Stern
2005-09-15 13:56 ` James Bottomley
2005-09-15 14:13 ` Alan Stern
2005-09-15 17:52 ` Alan Stern
2005-09-16 10:28 ` Anton Blanchard
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=43285599.9040002@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=James.Bottomley@SteelEye.com \
--cc=anton@samba.org \
--cc=dipankar@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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