WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Help: how do I debug this: kernel: BUG: warning at block/ll_

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Help: how do I debug this: kernel: BUG: warning at block/ll_rw_blk.c:1767/blk_start_queue() (Tainted: G)
From: "Joe Linoff" <jlinoff@xxxxxxxxxx>
Date: Wed, 23 Feb 2011 18:40:52 -0800
Cc: Joe Linoff <jlinoff@xxxxxxxxxx>
Delivery-date: Wed, 23 Feb 2011 18:42:19 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcvTzECUqZthDI3cSPiYVL4Hk9ZCIQ==
Thread-topic: Help: how do I debug this: kernel: BUG: warning at block/ll_rw_blk.c:1767/blk_start_queue() (Tainted: G)
Hi:

O/S: CentOS 5.5
Xen: 3.4.3

We are getting this error from one of our VMs (/var/log/messages) and I
don't know where to start debugging. Any hints would be greatly
appreciated.

   kernel: BUG: warning at block/ll_rw_blk.c:1767/blk_start_queue()
(Tainted: G)

These VM's are using DRBD to implement high availability server data.
One is the master and the other is a slave. Only the master (writer)
exhibits the problem. When the other VM is converted to the master the
problem then moves over there.

I suspect that DRBD is part of the problem because the error message
went away when I turned it off but we have a similar setup running under
xenserver and it works without these errors.

We have tried starting/stopping drbd and nfs. We tried mkfs.ext3 on the
filesystems.

Thank you,

Joe

FULL LOG ENTRY:

Feb 23 18:30:43 sgs-01 kernel: BUG: warning at
block/ll_rw_blk.c:1767/blk_start_queue() (Tainted: G     )
Feb 23 18:30:43 sgs-01 kernel: 
Feb 23 18:30:43 sgs-01 kernel: Call Trace:
Feb 23 18:30:43 sgs-01 kernel:  <IRQ>  [<ffffffff80336e7e>]
blk_start_queue+0x3c/0x7a
Feb 23 18:30:43 sgs-01 kernel:  [<ffffffff88075964>]
:xenblk:kick_pending_request_queues+0x1b/0x2a
Feb 23 18:30:43 sgs-01 kernel:  [<ffffffff88075d66>]
:xenblk:blkif_int+0x168/0x18d
Feb 23 18:30:43 sgs-01 kernel:  [<ffffffff802115d1>]
handle_IRQ_event+0x55/0xae
Feb 23 18:30:43 sgs-01 kernel:  [<ffffffff802b3562>] __do_IRQ+0xa4/0x103
Feb 23 18:30:43 sgs-01 kernel:  [<ffffffff8029032a>]
_local_bh_enable+0x61/0xc5
Feb 23 18:30:43 sgs-01 kernel:  [<ffffffff8026df50>] do_IRQ+0xe7/0xf5
Feb 23 18:30:43 sgs-01 kernel:  [<ffffffff803b3e7b>]
evtchn_do_upcall+0x13b/0x1fb
Feb 23 18:30:43 sgs-01 kernel:  [<ffffffff802608d6>]
do_hypervisor_callback+0x1e/0x2c
Feb 23 18:30:43 sgs-01 kernel:  <EOI>  [<ffffffff802063aa>]
hypercall_page+0x3aa/0x1000
Feb 23 18:30:43 sgs-01 kernel:  [<ffffffff802063aa>]
hypercall_page+0x3aa/0x1000
Feb 23 18:30:43 sgs-01 kernel:  [<ffffffff8026f4f3>]
raw_safe_halt+0x84/0xa8
Feb 23 18:30:43 sgs-01 kernel:  [<ffffffff8026ca88>] xen_idle+0x38/0x4a
Feb 23 18:30:43 sgs-01 kernel:  [<ffffffff8024af6c>] cpu_idle+0x97/0xba
Feb 23 18:30:43 sgs-01 kernel:  [<ffffffff8064eb0f>]
start_kernel+0x21f/0x224
Feb 23 18:30:43 sgs-01 kernel:  [<ffffffff8064e1e5>]
_sinittext+0x1e5/0x1eb
Feb 23 18:30:43 sgs-01 kernel:


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Help: how do I debug this: kernel: BUG: warning at block/ll_rw_blk.c:1767/blk_start_queue() (Tainted: G), Joe Linoff <=