Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Here's the data from the kernel panic - I'm not sure where the core would be kept to get the stack trace from. Starting DRBD resources: [ d(backup) Unable to handle kernel paging request at ffff81017480403c RIP: [<ffffffff8836271c>] :drbd:drbd_md_read+0xd7/0x236 PGD 17b65c063 PUD 0 Oops: 0000 [1] SMP last sysfs file: /module/drbd/parameters/cn_idx CPU 0 Modules linked in: drbd(U) nfsd exportfs nfs_acl auth_rpcgss ipv6 xfrm_nalgo crypto_api autofs4 hidp rfcomm l2cap bluetooth lockd sunrpc dm_mirror dm_multipath scsi_dh scsi_mod parport_pc lp parport xennet pcspkr dm_raid45 dm_message dm_region_hash dm_log dm_mod dm_mem_cache xenblk ext3 jbd uhci_hcd ohci_hcd ehci_hcd Pid: 35, comm: cqueue/0 Tainted: G 2.6.18-164.6.1.el5xen #1 RIP: e030:[<ffffffff8836271c>] [<ffffffff8836271c>] :drbd:drbd_md_read+0xd7/0x236 RSP: e02b:ffff880195fa3d30 EFLAGS: 00010a06 RAX: ffff810000000000 RBX: 0000000174804000 RCX: ffff880172b847a0 RDX: ffffffffff578000 RSI: ffff810174804000 RDI: 0000000000000000 RBP: ffff880178dbb000 R08: ffff8801773c4340 R09: 0000000000000000 R10: 0000000000000010 R11: ffffffff80246ce3 R12: ffff8800000cdc00 R13: ffff8800026d6000 R14: ffff880178dbb4f8 R15: ffff880178dbb7a0 FS: 00002aba57d58710(0000) GS:ffffffff805ca000(0000) knlGS:0000000000000000 CS: e033 DS: 0000 ES: 0000 Process cqueue/0 (pid: 35, threadinfo ffff880195fa2000, task ffff8800093b17a0) Stack: ffff880195fa3d28 ffff8800000cdc00 ffff880178dbb000 0000000000000001 ffff8800000cdc00 ffff88019295d1c8 ffff88019295d1c8 ffffffff88368281 ffff88018381ed14 ffff880172012cc0 Call Trace: [<ffffffff88368281>] :drbd:drbd_nl_disk_conf+0x6b5/0xc83 [<ffffffff803a5af9>] cn_queue_wrapper+0x0/0x23 [<ffffffff802fb6e5>] register_disk+0x158/0x190 [<ffffffff803a5af9>] cn_queue_wrapper+0x0/0x23 [<ffffffff88366f8a>] :drbd:drbd_connector_callback+0xe9/0x1a8 [<ffffffff803a5af9>] cn_queue_wrapper+0x0/0x23 [<ffffffff803a5b04>] cn_queue_wrapper+0xb/0x23 [<ffffffff8024f5ff>] run_workqueue+0x94/0xe4 [<ffffffff8024bed8>] worker_thread+0x0/0x122 [<ffffffff8029b9ec>] keventd_create_kthread+0x0/0xc4 [<ffffffff8024bfc8>] worker_thread+0xf0/0x122 [<ffffffff8028883e>] default_wake_function+0x0/0xe [<ffffffff8029b9ec>] keventd_create_kthread+0x0/0xc4 [<ffffffff8029b9ec>] keventd_create_kthread+0x0/0xc4 [<ffffffff80233bcd>] kthread+0xfe/0x132 [<ffffffff80260b2c>] child_rip+0xa/0x12 [<ffffffff8029b9ec>] keventd_create_kthread+0x0/0xc4 [<ffffffff80233acf>] kthread+0x0/0x132 [<ffffffff80260b22>] child_rip+0x0/0x12 Code: 8b 46 3c 0f c8 3d 6b 02 74 83 74 16 8b b5 44 08 00 00 48 c7 RIP [<ffffffff8836271c>] :drbd:drbd_md_read+0xd7/0x236 RSP <ffff880195fa3d30> CR2: ffff81017480403c <0>Kernel panic - not syncing: Fatal exception -------------------------- Mike Sweetser, RHCT, WCSP | Systems Administrator Adhost Internet 140 Fourth Avenue North, Suite 360, Seattle, Washington 98109 USA P 206.404.9000 T 888.234.6781 (ADHOST-1) F 206.404.9050 E mikesw at adhost.com W adhost.com > -----Original Message----- > From: drbd-user-bounces at lists.linbit.com [mailto:drbd-user- > bounces at lists.linbit.com] On Behalf Of Florian Haas > Sent: Wednesday, December 09, 2009 11:47 AM > To: drbd-user at lists.linbit.com > Subject: Re: [DRBD-user] Kernel panic - DRBD 8.3.6 and RHEL 5.4 x64 xen > > Can we please get a complete stack trace? > > Thanks. > > Cheers, > Florian > > On 2009-12-09 20:37, Mike Sweetser - Adhost wrote: > > As a followup, I tried different versions of DRBD on the Xen > machines, > > and was able to get it working with DRBD 8.3.2 and earlier. 8.3.3 > and > > later causes the kernel panic.