From: christophe varoqui <christophe.varoqui@free.fr>
To: device-mapper development <dm-devel@redhat.com>
Cc: Linux-SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: further testing w/ multipath ... and bugs
Date: Mon, 13 Jun 2005 20:56:50 +0200 [thread overview]
Message-ID: <1118689011.1515.2.camel@zezette> (raw)
In-Reply-To: <20050613182042.GA24059@plap.qlogic.org>
> > qla2300 0000:05:0d.0: LOOP DOWN detected.
> > Debug: sleeping function called from invalid context at include/linux/rwsem.h:43
> > in_atomic():1, irqs_disabled():1
> > [<c0120a74>] __might_sleep+0xa4/0xc0
> > [<c026a466>] device_for_each_child+0x26/0x80
> > [<c02b3180>] target_block+0x0/0x30
> > [<c02bbdae>] fc_remote_port_block+0x2e/0x60
> > [<c02bdbf5>] qla2x00_mark_all_devices_lost+0x55/0x60
> > [<c02c597e>] qla2x00_async_event+0x83e/0xd60
> > [<c011dd2b>] find_busiest_group+0xbb/0x310
> > [<c02cdce4>] sd_rw_intr+0x164/0x320
> > [<c02c4e37>] qla2300_intr_handler+0x77/0x240
> > [<c0144882>] handle_IRQ_event+0x32/0x70
>
> Without wanting to making a number of large changes to the qla2xxx
> internals to deal with these pre-qualifications, could you try the
> following patch (lightly tested with latest linus git tree).
>
> We'll need to update the fc_remote_port docs in order to account for
> this semantic change in device_for_each_child().
>
Indeed, it fixed this bug. Thanks for the prompt fix.
This leaves us with DM related bugs only :/
Regards,
--
christophe varoqui <christophe.varoqui@free.fr>
prev parent reply other threads:[~2005-06-13 18:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050613081154.GA28251@averon.dyndns.org>
2005-06-13 18:20 ` further testing w/ multipath ... and bugs Andrew Vasquez
2005-06-13 18:56 ` christophe varoqui [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=1118689011.1515.2.camel@zezette \
--to=christophe.varoqui@free.fr \
--cc=dm-devel@redhat.com \
--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