Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Lars Ellenberg wrote:
>
> If your kernel source looks like mine, then this would indicate something in
> between spin_lock_irqsave and spin_unlock_irqrestore above would enable
> spinlocks again, where is must not.
My kernel source is 2.6.32.25 (vanilla).
> If that something is some part of DRBD, then that would be a serious bug.
>
> If you run with spin lock debug enabled, that may provide some more insight.
> We'll try to reproduce here anyways.
Switched on:
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_SPINLOCK_SLEEP=y
Hope this helps:
[ 1196.324309] block drbd0: Began resync as SyncSource (will sync
7814892 KB [1953723 bits set]).
[ 1196.325278] ------------[ cut here ]------------
[ 1196.325486] WARNING: at block/blk-core.c:337 blk_start_queue+0x29/0x42()
[ 1196.325489] Hardware name: Bochs
[ 1196.325495] Modules linked in: ocfs2 jbd2 ocfs2_nodemanager
ocfs2_stack_user ocfs2_stackglue dlm bonding dummy drbd cn 8021q garp
bridge stp llc autofs4 rpcsec_gss_krb5 nfsd exportfs nfs lockd fscache
nfs_acl auth_rpcgss sunrpc xt_NOTRACK xt_TCPMSS xt_connmark xt_conntrack
xt_CONNMARK xt_state xt_policy iptable_nat nf_nat_tftp nf_conntrack_tftp
nf_nat_pptp nf_nat_proto_gre nf_conntrack_pptp nf_conntrack_proto_gre
nf_nat_irc nf_conntrack_irc nf_nat_sip nf_conntrack_sip nf_nat_ftp
nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack_ftp nf_conntrack
xfrm_user ipmi_devintf ipmi_msghandler 8139too ppdev parport_pc parport
st virtio_net virtio_balloon tpm_tis tpm tpm_bios rtc_cmos rtc_core
rtc_lib floppy evdev i2c_piix4 sg button i2c_core [last unloaded:
ocfs2_stackglue]
[ 1196.325589] Pid: 0, comm: swapper Not tainted 2.6.32.25 #1
[ 1196.325592] Call Trace:
[ 1196.325594] <IRQ> [<ffffffff811871c1>] ? blk_start_queue+0x29/0x42
[ 1196.325698] [<ffffffff8104d006>] warn_slowpath_common+0x77/0x8f
[ 1402.406817] block drbd0: helper command: /sbin/drbdadm
before-resync-target minor-0
[ 1196.325702] [<ffffffff8104d02d>] warn_slowpath_null+0xf/0x11
[ 1196.325705] [<ffffffff811871c1>] blk_start_queue+0x29/0x42
[ 1196.325797] [<ffffffff81239fae>] blk_done+0xe0/0xfa
[ 1196.325860] [<ffffffff8101683e>] ? sched_clock+0x9/0xd
[ 1196.325923] [<ffffffff811f7e85>] vring_interrupt+0x27/0x30
[ 1196.325988] [<ffffffff8108df65>] handle_IRQ_event+0x2d/0xb7
[ 1196.326007] [<ffffffff8108f7d2>] handle_edge_irq+0xc6/0x10c
[ 1196.326010] [<ffffffff81013534>] handle_irq+0x89/0x94
[ 1196.326013] [<ffffffff8101326b>] do_IRQ+0x5a/0xab
[ 1196.326016] [<ffffffff81011593>] ret_from_intr+0x0/0x11
[ 1196.326018] <EOI> [<ffffffff8102c718>] ? native_safe_halt+0x6/0x8
[ 1196.326054] [<ffffffff810175b1>] ? need_resched+0x1e/0x28
[ 1196.326057] [<ffffffff810175e0>] ? default_idle+0x25/0x42
[ 1196.326060] [<ffffffff8100fc3b>] ? cpu_idle+0xa8/0xca
[ 1196.326194] [<ffffffff814dd342>] ? rest_init+0x66/0x68
[ 1196.326315] [<ffffffff81867d35>] ? start_kernel+0x3a5/0x3b1
[ 1196.326318] [<ffffffff81867140>] ? early_idt_handler+0x0/0x71
[ 1196.326321] [<ffffffff818672c3>] ? x86_64_start_reservations+0xae/0xb2
[ 1196.326324] [<ffffffff818673c5>] ? x86_64_start_kernel+0xfe/0x10d
[ 1196.326327] ---[ end trace d73380a0fa08d83a ]---
[ 1196.326329] ------------[ cut here ]------------
> You say you simply start drbd 8 in a VM with virtio-blk,
> and that warning triggers?
Yes, using drbd 8.3.9 and virtio-blk.
drbd 8.3.8.1 and previous didn't trigger the warning.
Thomas