public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Vasquez <andrew.vasquez@qlogic.com>
To: Andrew Morton <akpm@osdl.org>, Greg KH <gregkh@suse.de>
Cc: Ake <Ake.Sandgren@hpc2n.umu.se>,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	James Bottomley <James.Bottomley@SteelEye.com>,
	James Smart <James.Smart@emulex.com>
Subject: Re: 2.6.12-rc5: sleeping function called from invalid context (qla2xxx/scsi_transport_fc?)
Date: Wed, 1 Jun 2005 11:48:20 -0700	[thread overview]
Message-ID: <20050601184820.GE22083@plap.qlogic.org> (raw)
In-Reply-To: <20050530140700.5a4fafa1.akpm@osdl.org>

On Mon, 30 May 2005, Andrew Morton wrote:

> Ake.Sandgren@hpc2n.umu.se (Ake) wrote:
> >
> > Hi!
> > I got the following when i pulled the FC cable from one of my qla2312
> > cards.
> > This is a 2.6.12-rc5 kernel (with udm1 patches for 2.6.12-rc2)
> > 
> > 
> > May 30 14:12:45 ican-i kernel: [ 1109.864830] qla2300 0000:03:09.0: LOOP DOWN detected.
> > May 30 14:12:45 ican-i kernel: [ 1109.875948] Debug: sleeping function called from invalid context at include/linux/rwsem.h:43
> > May 30 14:12:45 ican-i kernel: [ 1109.894492] in_atomic():1, irqs_disabled():1
> > May 30 14:12:45 ican-i kernel: [ 1109.903864]  [dump_stack+30/48] dump_stack+0x1e/0x30
> > May 30 14:12:45 ican-i kernel: [ 1109.913648]  [__might_sleep+167/176] __might_sleep+0xa7/0xb0
> > May 30 14:12:45 ican-i kernel: [ 1109.924003]  [device_for_each_child+35/144] device_for_each_child+0x23/0x90
> > May 30 14:12:45 ican-i kernel: [ 1109.935865]  [pg0+944279047/1069622272] scsi_target_block+0x57/0x60 [scsi_mod]
> > May 30 14:12:45 ican-i kernel: [ 1109.949142]  [pg0+944996009/1069622272] fc_remote_port_block+0x39/0x60 [scsi_transport_fc]
...
> 
> This was reported (and anaylsed) a month ago:
> 
> 	http://lkml.org/lkml/2005/4/29/82
> 
> I don't know if anything has been done about it yet though?

Greg,

Is there some other interrupt-safe alternative:

	http://lkml.org/lkml/2005/4/29/129

to using device_for_each_child()?  The scsi_target_[block/unblock]()
functions need to iterate over all the child-scsi_device's belonging
to an fc_rport.

Thanks,
Andrew Vasquez

  reply	other threads:[~2005-06-01 18:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050530125118.GG17514@hpc2n.umu.se>
2005-05-30 21:07 ` 2.6.12-rc5: sleeping function called from invalid context (qla2xxx/scsi_transport_fc?) Andrew Morton
2005-06-01 18:48   ` Andrew Vasquez [this message]
2005-06-01 20:39     ` Greg KH

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=20050601184820.GE22083@plap.qlogic.org \
    --to=andrew.vasquez@qlogic.com \
    --cc=Ake.Sandgren@hpc2n.umu.se \
    --cc=James.Bottomley@SteelEye.com \
    --cc=James.Smart@emulex.com \
    --cc=akpm@osdl.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox