From: Bart Van Assche <bart.vanassche@sandisk.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: 4.1-rc2 dm-multipath-mq kernel warning
Date: Tue, 5 May 2015 16:04:21 +0200 [thread overview]
Message-ID: <5548CDE5.9@sandisk.com> (raw)
Hello Mike,
While retesting my SRP initiator patches on top of kernel v4.1-rc2 with
DM_MQ_DEFAULT=y I ran into the kernel warning below. Does this mean that
I'm missing any device mapper related patches ? This warning was
reported shortly after scsi_remove_host() had been invoked.
Thanks,
Bart.
[ 636.982089] device-mapper: multipath: Failing path 8:16.
[ 636.982395] blk_update_request: I/O error, dev dm-1, sector 42378
[ 636.987025] ------------[ cut here ]------------
[ 636.987053] WARNING: CPU: 0 PID: 3 at drivers/md/dm.c:1090
free_rq_clone+0x7a/0xf0 [dm_mod]()
[ 636.987070] Modules linked in: dm_service_time dm_multipath scsi_dh
ib_srp scsi_transport_srp netconsole configfs fuse dm_crypt xts gf128mul
algif_skcipher af_alg loop rdma_ucm rdma_cm iw_cm ib_ipoib ib_cm
ib_uverbs ib_umad mlx4_en ptp pps_core iscsi_ibft iscsi_boot_sysfs
af_packet mlx4_ib ib_sa ib_mad ib_core ib_addr mlx4_core iTCO_wdt sky2
iTCO_vendor_support coretemp lpc_ich shpchp mfd_core pcspkr serio_raw
i2c_i801 acpi_cpufreq tpm_infineon tpm_tis tpm asus_atk0110 button
processor dm_mod sr_mod cdrom ata_generic radeon ata_piix firewire_ohci
i2c_algo_bit firewire_core crc_itu_t drm_kms_helper ttm pata_marvell drm
floppy sg [last unloaded: scsi_transport_srp]
[ 636.998755] CPU: 0 PID: 3 Comm: ksoftirqd/0 Not tainted
4.1.0-rc2-debug+ #1
[ 636.998771] Hardware name: System manufacturer P5Q DELUXE/P5Q DELUXE,
BIOS 2301 07/10/2009
[ 636.998786] ffffffffa02ce8ad ffff8801b81efca8 ffffffff81606de3
ffff8801bfc0fff8
[ 636.998862] 0000000000000000 ffff8801b81efce8 ffffffff81052940
ffffffff81e3d288
[ 636.998953] ffff8800a1f82580 ffff8800a1e40000 ffff8800a1f82530
ffff8800a1e40000
[ 636.999032] Call Trace:
[ 636.999054] [<ffffffff81606de3>] dump_stack+0x4c/0x6e
[ 636.999074] [<ffffffff81052940>] warn_slowpath_common+0x80/0xc0
[ 636.999092] [<ffffffff81052a25>] warn_slowpath_null+0x15/0x20
[ 636.999115] [<ffffffffa02bdc2a>] free_rq_clone+0x7a/0xf0 [dm_mod]
[ 636.999139] [<ffffffffa02be45c>] dm_softirq_done+0x13c/0x250 [dm_mod]
[ 636.999162] [<ffffffff812c6ec8>] blk_done_softirq+0x78/0x90
[ 636.999181] [<ffffffff81056a2a>] __do_softirq+0x10a/0x240
[ 636.999200] [<ffffffff81056b7a>] run_ksoftirqd+0x1a/0x70
[ 636.999218] [<ffffffff81076adf>] smpboot_thread_fn+0x16f/0x260
[ 636.999256] [<ffffffff81073099>] kthread+0xf9/0x110
[ 636.999294] [<ffffffff8160fce2>] ret_from_fork+0x42/0x70
[ 636.999338] ---[ end trace ba34bc950a902b8f ]---
next reply other threads:[~2015-05-05 14:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 14:04 Bart Van Assche [this message]
2015-05-06 2:23 ` 4.1-rc2 dm-multipath-mq kernel warning Mike Snitzer
2015-05-06 7:45 ` Bart Van Assche
2015-05-06 18:29 ` Mike Snitzer
2015-05-07 10:19 ` Bart Van Assche
2015-05-27 12:57 ` Mike Snitzer
2015-05-27 15:29 ` Bart Van Assche
2015-05-27 15:33 ` Bart Van Assche
2015-05-27 16:14 ` Mike Snitzer
2015-05-27 17:00 ` Mike Snitzer
2015-05-27 22:37 ` Mike Snitzer
2015-05-28 8:19 ` Bart Van Assche
2015-05-28 13:10 ` Mike Snitzer
2015-05-28 14:07 ` Mike Snitzer
2015-05-28 14:54 ` Bart Van Assche
2015-05-28 15:06 ` Mike Snitzer
2015-05-29 10:04 ` Bart Van Assche
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=5548CDE5.9@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=dm-devel@redhat.com \
--cc=snitzer@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.