Re: [Xen-devel] kobject (null) without dirent 3.x domU

[Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>]

On Thu, Jul 12, 2012 at 10:08:59PM +0200, William Dauchy wrote:
> Hi,
> 
> On a 3.3.8 dom0 x86_32, I'm sometimes getting a "sysfs: kobject (null)
> without dirent" with a 3.4.4 x86_64 domU kernel during boot.
> The hypervisor is a Xen4.1.2
> I also tested it on a 3.2 and 3.3 domU kernel and got the same results.
> Sounds like a race since I can't reproduce it every time.
> Does anybody have any clue?

Do you see this with v3.5?

> 
> sysfs: kobject (null) without dirent
> BUG: unable to handle kernel NULL pointer dereference at           (null)
> IP: [<ffffffff8105aa59>] __wake_up_common+0x29/0x80
> PGD 0
> Oops: 0000 [#1] SMP
> CPU 2
> Modules linked in:
> 
> Pid: 46, comm: xenwatch Tainted: G        W    3.4.4-xenU-6816-x86_64 #2
> RIP: e030:[<ffffffff8105aa59>]  [<ffffffff8105aa59>] 
> __wake_up_common+0x29/0x80
> RSP: e02b:ffff88000c6f9d80  EFLAGS: 00010082
> RAX: ffffffffffffffe8 RBX: 0000000000000000 RCX: 0000000000000000
> RDX: 0000000000000000 RSI: 0000000000000003 RDI: ffff88000fc6c3c0
> RBP: 0000000000000200 R08: 0000000000000000 R09: 0000000000000000
> R10: 0000000000000000 R11: 0000000000000004 R12: ffff88000fc6c3b8
> R13: ffff88000fc6c3c8 R14: 0000000000000000 R15: 0000000000000003
> FS:  0000000000000000(0000) GS:ffff88000fc40000(0000) knlGS:0000000000000000
> CS:  e033 DS: 0000 ES: 0000 CR0: 000000008005003b
> CR2: 0000000000000000 CR3: 000000000160b000 CR4: 0000000000002660
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> Process xenwatch (pid: 46, threadinfo ffff88000c6f8000, task ffff88000c6eb0c0)
> Stack:
>  ffff88000c6f9e08 0000000081036335 0000000000000200 ffff88000fc6c3c0
>  0000000000000200 ffff88000fc6c3b8 ffffffff817148e2 ffff88000c6f9e98
>  ffff88000c6eb0c0 ffffffff8105b4d0 ffff88000fc6c308 0000000000000000
> Call Trace:
>  [<ffffffff8105b4d0>] ? complete_all+0x40/0x60
>  [<ffffffff81264fe0>] ? device_pm_remove+0x10/0x70
>  [<ffffffff8125a776>] ? device_del+0x36/0x1c0
>  [<ffffffff8125a909>] ? device_unregister+0x9/0x20
>  [<ffffffff8125f750>] ? unregister_cpu+0x30/0x60
>  [<ffffffff81239047>] ? handle_vcpu_hotplug_event+0xc7/0xd0
>  [<ffffffff81235942>] ? xenwatch_thread+0xb2/0x180
>  [<ffffffff8105aa80>] ? __wake_up_common+0x50/0x80
>  [<ffffffff81052ed0>] ? wake_up_bit+0x40/0x40
>  [<ffffffff81235890>] ? xenbus_thread+0x2f0/0x2f0
>  [<ffffffff81235890>] ? xenbus_thread+0x2f0/0x2f0
>  [<ffffffff81052a0e>] ? kthread+0x9e/0xb0
>  [<ffffffff8134b864>] ? kernel_thread_helper+0x4/0x10
>  [<ffffffff81349e78>] ? retint_restore_args+0x5/0x6
>  [<ffffffff8134b860>] ? gs_change+0x13/0x13
> Code: 00 00 41 57 41 89 f7 41 56 4d 89 c6 41 55 4c 8d 6f 08 41 54 55
> 53 89 cb 48 83 ec 18 89 54 24 0c 48 8b 57 08 48 8d 42 e8 49 39 d5 <48>
> 8b 68 18 74 40 48 83 ed 18 eb 0a 0f 1f 00 48 89 e8 48 8d 6a
> RIP  [<ffffffff8105aa59>] __wake_up_common+0x29/0x80
>  RSP <ffff88000c6f9d80>
> CR2: 0000000000000000
> ---[ end trace 4eaa2a86a8e2da23 ]---
> SMP alternatives: switching to UP code
> 
> Regards,
> -- 
> William
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxx
> http://lists.xen.org/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel