[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#607141: marked as done (xm block-attach failed on domU)



Your message dated Thu, 9 Feb 2012 15:59:02 -0600
with message-id <20120209215902.GA3120@burratino>
and subject line Re: xm block-attach failed on domU
has caused the Debian Bug report #607141,
regarding xm block-attach failed on domU
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
607141: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607141
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6-xen-amd64
Version:  2.6.26-26lenny1
Severity: critical
Tags: lenny

Execution of xm block-attach to PV domU failed and I have got Ooops kernel messages in attachment. After that domU wasn't manageable from dom0 - all xm commands were not successful and I had to shutdown the domU from the pty (ssh) console.
Both dom0 and domU were running same kernel version.

--
Peter Viskup
Dec 13 16:29:04 tis kernel: [83118.676876] BUG: unable to handle kernel NULL pointer dereference at 0000000000000000
Dec 13 16:29:04 tis kernel: [83118.676898] IP: [<ffffffff8038d104>] backend_changed+0x1bf/0x23a
Dec 13 16:29:04 tis kernel: [83118.676920] PGD 1e82f067 PUD 1f1a8067 PMD 0 
Dec 13 16:29:04 tis kernel: [83118.676933] Oops: 0000 [1] SMP 
Dec 13 16:29:04 tis kernel: [83118.676941] CPU 0 
Dec 13 16:29:04 tis kernel: [83118.676948] Modules linked in: iptable_filter ip_tables x_tables ipv6 xfs evdev ext3 jbd mbcache dm_mirror dm_log dm_snapshot dm_mod thermal_sys cciss scsi_mod
Dec 13 16:29:04 tis kernel: [83118.676991] Pid: 19, comm: xenwatch Not tainted 2.6.26-2-xen-amd64 #1
Dec 13 16:29:04 tis kernel: [83118.677000] RIP: e030:[<ffffffff8038d104>]  [<ffffffff8038d104>] backend_changed+0x1bf/0x23a
Dec 13 16:29:04 tis kernel: [83118.677015] RSP: e02b:ffff88001fd11e60  EFLAGS: 00010246
Dec 13 16:29:04 tis kernel: [83118.677023] RAX: 0000000000000000 RBX: ffff880006dec000 RCX: 0000000000000000
Dec 13 16:29:04 tis kernel: [83118.677032] RDX: ffff88001fd11de8 RSI: 0000000000000005 RDI: ffff88001f12c400
Dec 13 16:29:04 tis kernel: [83118.677041] RBP: ffffffff8038327f R08: 0000000000000005 R09: 00000000ffffffff
Dec 13 16:29:04 tis kernel: [83118.677050] R10: ffff8800850bb000 R11: ffffffff8038cf45 R12: ffff88001f12c400
Dec 13 16:29:04 tis kernel: [83118.677059] R13: ffffffff8057c580 R14: ffffffff8057d1c0 R15: 0000000000000000
Dec 13 16:29:04 tis kernel: [83118.677070] FS:  00007f53a5d766e0(0000) GS:ffffffff8053a000(0000) knlGS:0000000000000000
Dec 13 16:29:04 tis kernel: [83118.677080] CS:  e033 DS: 0000 ES: 0000
Dec 13 16:29:04 tis kernel: [83118.677087] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Dec 13 16:29:04 tis kernel: [83118.677097] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Dec 13 16:29:04 tis kernel: [83118.677106] Process xenwatch (pid: 19, threadinfo ffff88001fd10000, task ffff88001fd08140)
Dec 13 16:29:04 tis kernel: [83118.677116] Stack:  ffffffff8057c580 ffffffff80383a01 ffff88001f059c40 ffff88001f12c400
Dec 13 16:29:04 tis kernel: [83118.677133]  ffffffff8052a968 ffffffff8057c580 ffffffff8057d1c0 ffffffff80381c19
Dec 13 16:29:04 tis kernel: [83118.677148]  0000000000000000 0000000000000000 000000058038327f ffff88001f1f2d80
Dec 13 16:29:04 tis kernel: [83118.677161] Call Trace:
Dec 13 16:29:04 tis kernel: [83118.677172]  [<ffffffff80383a01>] ? xenbus_device_find+0x28/0x31
Dec 13 16:29:04 tis kernel: [83118.677184]  [<ffffffff80381c19>] ? xenbus_read_driver_state+0x26/0x3b
Dec 13 16:29:04 tis kernel: [83118.677195]  [<ffffffff8038327f>] ? xenwatch_thread+0x0/0x186
Dec 13 16:29:04 tis kernel: [83118.677206]  [<ffffffff8038295d>] ? xenwatch_handle_callback+0x15/0x48
Dec 13 16:29:04 tis kernel: [83118.677216]  [<ffffffff803833ec>] ? xenwatch_thread+0x16d/0x186
Dec 13 16:29:04 tis kernel: [83118.677227]  [<ffffffff8023f6ad>] ? autoremove_wake_function+0x0/0x2e
Dec 13 16:29:04 tis kernel: [83118.677237]  [<ffffffff8023f57f>] ? kthread+0x47/0x74
Dec 13 16:29:04 tis kernel: [83118.677247]  [<ffffffff802282ec>] ? schedule_tail+0x27/0x5c
Dec 13 16:29:04 tis kernel: [83118.677257]  [<ffffffff8020be28>] ? child_rip+0xa/0x12
Dec 13 16:29:04 tis kernel: [83118.677268]  [<ffffffff8023f538>] ? kthread+0x0/0x74
Dec 13 16:29:04 tis kernel: [83118.677276]  [<ffffffff8020be1e>] ? child_rip+0x0/0x12
Dec 13 16:29:04 tis kernel: [83118.677283] 
Dec 13 16:29:04 tis kernel: [83118.677287] 
Dec 13 16:29:04 tis kernel: [83118.677291] Code: 23 3e 17 00 c6 40 01 00 80 38 00 74 05 e8 f1 00 ff ff 48 8b 7b 08 e8 56 8e f7 ff c7 83 9c 1a 00 00 01 00 00 00 eb 74 48 8b 43 08 <8b> 38 c1 e7 14 0b 78 04 e8 10 40 f2 ff 48 85 c0 48 89 c5 75 16 
Dec 13 16:29:04 tis kernel: [83118.677391] RIP  [<ffffffff8038d104>] backend_changed+0x1bf/0x23a
Dec 13 16:29:04 tis kernel: [83118.677402]  RSP <ffff88001fd11e60>
Dec 13 16:29:04 tis kernel: [83118.677408] CR2: 0000000000000000
Dec 13 16:29:04 tis kernel: [83118.677419] ---[ end trace 75e2ecdeadd46e28 ]---

--- End Message ---
--- Begin Message ---
Hi Peter,

Peter Viskup wrote:

> Execution of xm block-attach to PV domU failed and I have got Ooops
> kernel messages in attachment.
> After that domU wasn't manageable from dom0 - all xm commands were
> not successful and I had to shutdown the domU from the pty (ssh)
> console.
> Both dom0 and domU were running same kernel version.
[...]
> BUG: unable to handle kernel NULL pointer dereference at 0000000000000000
> IP: [<ffffffff8038d104>] backend_changed+0x1bf/0x23a
[...]
> Process xenwatch (pid: 19, threadinfo ffff88001fd10000, task ffff88001fd08140)
[...]
> Call Trace:
>  [<ffffffff80383a01>] ? xenbus_device_find+0x28/0x31
>  [<ffffffff80381c19>] ? xenbus_read_driver_state+0x26/0x3b
>  [<ffffffff8038327f>] ? xenwatch_thread+0x0/0x186
>  [<ffffffff8038295d>] ? xenwatch_handle_callback+0x15/0x48
>  [<ffffffff803833ec>] ? xenwatch_thread+0x16d/0x186
>  [<ffffffff8023f6ad>] ? autoremove_wake_function+0x0/0x2e
[...]
> Code: 23 3e 17 00 c6 40 01 00 80 38 00 74 05 e8 f1 00 ff ff 48 8b 7b 08 e8 56 8e f7 ff c7 83 9c 1a 00 00 01 00 00 00 eb 74 48 8b 43 08 <8b> 38 c1 e7 14 0b 78 04 e8 10 40 f2 ff 48 85 c0 48 89 c5 75 16 

Thanks for reporting.  Closing since lenny is not receiving updates
any more.

IIRC Timo tried to reproduce this on squeeze and wasn't able to.
Anyway, I'm curious: are you still using this system?  What kernel
version do you use now, and does it work?

Ciao,
Jonathan


--- End Message ---

Reply to: