From: Andrew Morton <akpm@osdl.org>
To: Ake <Ake.Sandgren@hpc2n.umu.se>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
Andrew Vasquez <andrew.vasquez@qlogic.com>
Subject: Re: 2.6.12-rc5: sleeping function called from invalid context (qla2xxx/scsi_transport_fc?)
Date: Mon, 30 May 2005 14:07:00 -0700 [thread overview]
Message-ID: <20050530140700.5a4fafa1.akpm@osdl.org> (raw)
In-Reply-To: <20050530125118.GG17514@hpc2n.umu.se>
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]
> May 30 14:12:45 ican-i kernel: [ 1109.964649] [pg0+946826440/1069622272] qla2x00_mark_all_devices_lost+0x78/0x80 [qla2xxx]
> May 30 14:12:45 ican-i kernel: [ 1109.980000] [pg0+946857000/1069622272] qla2x00_async_event+0x4b8/0xd20 [qla2xxx]
> May 30 14:12:45 ican-i kernel: [ 1109.993778] [pg0+946855321/1069622272] qla2300_intr_handler+0x149/0x220 [qla2xxx]
> May 30 14:12:45 ican-i kernel: [ 1110.007748] [handle_IRQ_event+51/112] handle_IRQ_event+0x33/0x70
> May 30 14:12:45 ican-i kernel: [ 1110.018709] [__do_IRQ+230/320] __do_IRQ+0xe6/0x140
> May 30 14:12:45 ican-i kernel: [ 1110.028321] [do_IRQ+55/112] do_IRQ+0x37/0x70
> May 30 14:12:45 ican-i kernel: [ 1110.037362] [common_interrupt+26/32] common_interrupt+0x1a/0x20
> May 30 14:12:45 ican-i kernel: [ 1110.048270] [cpu_idle+114/128] cpu_idle+0x72/0x80
> May 30 14:12:45 ican-i kernel: [ 1110.057657] [start_kernel+407/480] start_kernel+0x197/0x1e0
> May 30 14:12:45 ican-i kernel: [ 1110.068222] [L6+0/2] 0xc010020e
> May 30 14:13:03 ican-i kernel: [ 1127.266792] qla2300 0000:03:09.0: LIP reset occured (f8e8).
> May 30 14:13:03 ican-i kernel: [ 1127.373378] qla2300 0000:03:09.0: LIP occured (f7e8).
> May 30 14:13:03 ican-i kernel: [ 1127.384479] qla2300 0000:03:09.0: LOOP UP detected (2 Gbps).
>
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?
next parent reply other threads:[~2005-05-30 21:07 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 ` Andrew Morton [this message]
2005-06-01 18:48 ` 2.6.12-rc5: sleeping function called from invalid context (qla2xxx/scsi_transport_fc?) Andrew Vasquez
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=20050530140700.5a4fafa1.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=Ake.Sandgren@hpc2n.umu.se \
--cc=andrew.vasquez@qlogic.com \
--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