[Xen-devel] Re: [Xen-users] Xen-4 PVUSB kernel bug

[Pasi Kärkkäinen <pasik@xxxxxx>]

On Mon, Jun 07, 2010 at 05:57:25PM +0200, Peter Klar wrote:
> On Tuesday 01 June 2010, Andrew Lyon wrote:
> > I've only tried using pvusb once and that was a long time ago so I'm
> > not all that surprised that there are issues with it in this kernel,
> > I have much less time available now to debug issues with the dom0
> > kernel patch sets than I did a few months ago but if you could try
> > 2.6.32-r2 from http://code.google.com/p/gentoo-xen-kernel/downloads/list
> > and if the issue persists I will try to replicate it and see if I can
> > fix it.
> > 
> > I'm not sure if novell/suse support pv_usb or not, if they do then I
> > can probably get some assistance from Jan as he will certainly be
> > interested in fixing any bug that exists in the SLE11-SP1 kernel that
> > the patches originate from.
> 
> I tried the 2.6.32-r2 and the 2.6.34 kernels, the problem still exists, even 
> though the dom0 doesn't freeze anymore, it logs some kernel messages (see 
> below) but seems to work w/o any problems.
> 
> The printer still receives some data but doesn't print anything.
> The domU doesn't report any kernel messages or similar.
> 

Ok.. CC'ing to xen-devel.

-- Pasi

> Regards
> 
> 
> ------------[ cut here ]------------
> kernel BUG at mm/slub.c:2846!
> invalid opcode: 0000 [#1] SMP 
> last sysfs file: /sys/devices/xen-backend/vbd-3-51745/statistics/wr_sect
> CPU 0 
> Modules linked in: usbbk ipv6 bridge stp llc usbhid hid ide_pci_generic 
> usb_storage evdev atiixp ide_core pcspkr ehs
> 
> Pid: 6169, comm: usbback.3.0 Not tainted 2.6.34-xen-mcclure #1 A780FullHD/To 
> Be Filled By O.E.M.
> RIP: e030:[<ffffffff802a9c0a>]  [<ffffffff802a9c0a>] kfree+0xea/0xf0
> RSP: e02b:ffff88000ccfbbc0  EFLAGS: 00010246
> RAX: 4000000000000000 RBX: ffff88000bd44000 RCX: ffff88000125d470
> RDX: 000000000005ea20 RSI: ffff8800013996e0 RDI: ffff88000bd44000
> RBP: ffffffffa0011350 R08: 0000000000000000 R09: ffff88000181f1c0
> R10: 0000000000000000 R11: ffffffff80209730 R12: 0000000000000000
> R13: 000000000000000e R14: 000000000000000e R15: 0000000000000001
> FS:  00007f7bd85be910(0000) GS:ffff880001004000(0000) knlGS:0000000000000000
> CS:  e033 DS: 0000 ES: 0000 CR0: 000000008005003b
> CR2: 00007f7bdf7c8000 CR3: 000000000d783000 CR4: 0000000000000660
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> Process usbback.3.0 (pid: 6169, threadinfo ffff88000ccfa000, task 
> ffff88000b0e0ba0)
> Stack:
>  ffff8800061c9cc0 ffffffffa0011350 0000000000000000 ffffffffa0011363
> <0> ffff8800061c9cc0 ffffffff80369b43 000000000000000e ffff8800061c9cc0
> <0> ffff88000ccfbc10 ffffffffa016b72a ffff88000ccfbc10 ffff88000ccfbc10
> Call Trace:
>  [<ffffffffa0011350>] ? urb_destroy+0x0/0x20 [usbcore]
>  [<ffffffffa0011363>] ? urb_destroy+0x13/0x20 [usbcore]
>  [<ffffffff80369b43>] ? kref_put+0x33/0x70
>  [<ffffffffa016b72a>] ? usbbk_free_urbs+0x9a/0x120 [usbbk]
>  [<ffffffffa016c434>] ? usbbk_schedule+0x414/0x1070 [usbbk]
>  [<ffffffff802257fc>] ? update_curr+0x6c/0xf0
>  [<ffffffff8022b9ff>] ? check_preempt_wakeup+0x9f/0x100
>  [<ffffffff80228d5b>] ? try_to_wake_up+0xab/0x2d0
>  [<ffffffff8022437b>] ? target_load+0x2b/0x60
>  [<ffffffff8022c67a>] ? select_task_rq_fair+0x5ba/0x690
>  [<ffffffff802257fc>] ? update_curr+0x6c/0xf0
>  [<ffffffff8022594d>] ? __dequeue_entity+0x3d/0x50
>  [<ffffffff80227e21>] ? finish_task_switch+0x41/0xf0
>  [<ffffffff804f466d>] ? schedule+0x25d/0x780
>  [<ffffffff80224b3b>] ? __wake_up_common+0x5b/0x90
>  [<ffffffffa016c020>] ? usbbk_schedule+0x0/0x1070 [usbbk]
>  [<ffffffff80246876>] ? kthread+0x96/0xa0
>  [<ffffffff80205094>] ? kernel_thread_helper+0x4/0x10
>  [<ffffffff802467e0>] ? kthread+0x0/0xa0
>  [<ffffffff80205090>] ? kernel_thread_helper+0x0/0x10
> Code: 18 49 8b 00 48 89 04 13 49 89 18 eb b8 66 a9 00 c0 74 18 5b 5d 41 5c 
> 48 89 f7 e9 52 86 fd ff 48 8b 76 10 48 8 
> RIP  [<ffffffff802a9c0a>] kfree+0xea/0xf0
>  RSP <ffff88000ccfbbc0>
> ---[ end trace a9e5ebb40790f3ae ]---

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