Re: [Xen-devel] tapdisk2 makes HP multi-core hang

[Daniel Stodden <daniel.stodden@xxxxxxxxxx>]

On Sun, 2011-01-30 at 18:37 -0500, K L wrote:
> Thanks for the links. I will try other kernels as well. BTW, there is
> another crash happened today.

thanks. 

& sorry for the inconvenience.

Daniel

> //////////////////////////////////////////////////////////////////////////
> blktap_device_create: minor 0 sectors 8388608 sector-size 512
> blktap_device_create: creation of 254:0: 0
> ----------- [cut here ] --------- [please bite here ] ---------
> Kernel BUG at ...ssd_disk/xen-4.0.1/linux-2.6.18-xen.hg/mm/memory.c:2251
> invalid opcode: 0000 [1] SMP
> CPU 0
> Modules linked in: rtc_cmos rtc_core rtc_lib thermal processor fan
> Pid: 11164, comm: tapdisk2 Not tainted 2.6.18.8-xen0 #1
> RIP: e030:[<ffffffff80273f91>]  [<ffffffff80273f91>]
> __handle_mm_fault+0x6f1/0x12e0
> RSP: e02b:ffff88001ab4fdb8  EFLAGS: 00010202
> RAX: ffff88003b294b10 RBX: 0000000000000000 RCX: ffffffff80704360
> RDX: 000000003ca34000 RSI: 0000000000000f50 RDI: 00000001557a2067
> RBP: ffff88001ab4fe48 R08: 0000000000000000 R09: 0000000000000000
> R10: ffff880000000f50 R11: 0000000000000246 R12: ffff88001fa59be0
> R13: 00002b627c5ea218 R14: ffff88003ca34f50 R15: ffffffff807cc420
> FS:  00002b627b959510(0000) GS:ffffffff80771000(0000) knlGS:0000000000000000
> CS:  e033 DS: 0000 ES: 0000
> Process tapdisk2 (pid: 11164, threadinfo ffff88001ab4e000, task
> ffff880036de9790)
> Stack:  0000000000000000 0000000000000020 0000000000000000 0000000000000000
>  ffff88003b294b10 ffff88001fa59b80 ffff880036575f10 ffff88001ab4ff48
>  ffff88001ab4ff08 ffffffff80265cc6 0000000000000000 ffffffff00000001
> Call Trace:
>  [<ffffffff80265cc6>] generic_file_read+0xc6/0xf0
>  [<ffffffff8021e1ef>] do_page_fault+0xc9f/0x11c0
>  [<ffffffff8024f230>] autoremove_wake_function+0x0/0x40
>  [<ffffffff8020ec48>] do_gettimeofday+0x288/0x2b0
>  [<ffffffff8020a287>] error_exit+0x0/0x71
> 
> 
> Code: 0f 0b 68 c0 38 61 80 c2 cb 08 0f 1f 44 00 00 48 8b 55 90 45
> RIP  [<ffffffff80273f91>] __handle_mm_fault+0x6f1/0x12e0
>  RSP <ffff88001ab4fdb8>
>  <6>blktap_device_destroy: destroy device 0 users 1
> 
> Thanks,
> Jeff
> 
> On Sun, Jan 30, 2011 at 2:57 PM, Daniel Stodden
> <daniel.stodden@xxxxxxxxxx> wrote:
> > On Sun, 2011-01-30 at 08:46 -0500, K L wrote:
> >> I am using 2.6.18.8-xen. I don't think it's the kernel's problem.
> >
> > No, it may very well be a blktap problem, I don't dispute that. It's
> > just that I don't know if there's still a 2.6.18 tree with blktap
> > maintained anywhere.
> >
> > The blktap head branch is in the pvops kernel:
> > http://git.us.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=shortlog;h=refs/heads/xen/dom0/backend/blktap2
> >
> > Alternatively, there are  more recent vendor kernels, like the XCP tree.
> >
> > http://wiki.xensource.com/xenwiki/XenDom0Kernels
> >
> > Cheers,
> > Daniel
> >
> >> Jeff
> >>
> >> On Sun, Jan 30, 2011 at 3:57 AM, Daniel Stodden
> >> <daniel.stodden@xxxxxxxxxx> wrote:
> >> > On Sat, 2011-01-29 at 22:06 -0500, K L wrote:
> >> >> Hi all,
> >> >>
> >> >> I am running tapdisk2 on HP proliant DL360 and found the following
> >> >> error when tapdisk2 running for a while. Could any body help me look
> >> >> at this?
> >> >
> >> > What kernel are you running? Can you upgrade?
> >> >
> >> > Daniel
> >> >
> >> >> Many thanks,
> >> >> Jeff
> >> >>
> >> >> ///////////////////////////////////////////////
> >> >>
> >> >> EXT3-fs error (device tapdeva): ext3_add_entry: bad entry in directory
> >> >> #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0,
> >> >> name_len=0
> >> >> Aborting journal on device tapdeva.
> >> >> EXT3-fs error (device tapdeva) in ext3_reserve_inode_write: Journal has 
> >> >> aborted
> >> >> ext3_abort called.
> >> >> EXT3-fs error (device tapdeva): ext3_journal_start_sb: Detected aborted 
> >> >> journal
> >> >> Remounting filesystem read-only
> >> >> EXT3-fs error (device tapdeva) in start_transaction: Journal has aborted
> >> >> __journal_remove_journal_head: freeing b_committed_data
> >> >> BUG: soft lockup detected on CPU#2!
> >> >>
> >> >> Call Trace:
> >> >>  <IRQ> [<ffffffff8022ef40>] wake_up_process+0x10/0x20
> >> >>  [<ffffffff8025fbed>] softlockup_tick+0xfd/0x130
> >> >>  [<ffffffff80242623>] run_local_timers+0x13/0x20
> >> >>  [<ffffffff8020f53d>] timer_interrupt+0x49d/0x500
> >> >>  [<ffffffff8024aa90>] delayed_work_timer_fn+0x0/0x40
> >> >>  [<ffffffff8026013c>] handle_IRQ_event+0x5c/0xb0
> >> >>  [<ffffffff8026024f>] __do_IRQ+0xbf/0x140
> >> >>  [<ffffffff8020c802>] do_IRQ+0x52/0x70
> >> >>  [<ffffffff8043f626>] evtchn_do_upcall+0x126/0x350
> >> >>  [<ffffffff8020a332>] do_hypervisor_callback+0x1e/0x2c
> >> >>  <EOI> [<ffffffff8030da26>] ext3fs_dirhash+0x206/0x220
> >> >>  [<ffffffff8030a300>] htree_dirblock_to_tree+0x70/0x100
> >> >>  [<ffffffff8030a400>] ext3_htree_fill_tree+0x70/0x220
> >> >>  [<ffffffff802743ce>] __handle_mm_fault+0xb2e/0x12e0
> >> >>  [<ffffffff8030026e>] ext3_readdir+0x1ce/0x5e0
> >> >>  [<ffffffff8028e368>] file_move+0x28/0x60
> >> >>  [<ffffffff802a2930>] filldir+0x0/0xe0
> >> >>  [<ffffffff80252799>] up_read+0x9/0x10
> >> >>  [<ffffffff8021e23f>] do_page_fault+0xcef/0x11c0
> >> >>  [<ffffffff802a2930>] filldir+0x0/0xe0
> >> >>  [<ffffffff802a2b40>] vfs_readdir+0x70/0xc0
> >> >>  [<ffffffff802a2ce3>] sys_getdents+0x83/0xd0
> >> >>  [<ffffffff8020a287>] error_exit+0x0/0x71
> >> >>  [<ffffffff80209b48>] system_call+0x68/0x6d
> >> >>  [<ffffffff80209ae0>] system_call+0x0/0x6d
> >> >>
> >> >> _______________________________________________
> >> >> Xen-devel mailing list
> >> >> Xen-devel@xxxxxxxxxxxxxxxxxxx
> >> >> http://lists.xensource.com/xen-devel
> >> >
> >> >
> >> >
> >
> >
> >



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