https://bugzilla.novell.com/show_bug.cgi?id=825373 https://bugzilla.novell.com/show_bug.cgi?id=825373#c1 --- Comment #1 from Otrebor Igorig 2013-06-18 15:16:29 UTC --- I did perform an additional test: Scenario 1: - Host 'super' is the Xen host (dom0) running OS12.3 - Client DomU running - OpenSuse 12.2 (dome122) on super - NFS3 Server (Netgear, NAS) with mounted /home (nas5) - Compile job on dome12 works without a problem Scenario 2: - Same Client DomU as above (dome122, OS12.2) on super - NFS Server is a DomU (vnas) running OS12.3 in super - Client DomU has mounted nfs3 directory form vnas server - Compile job crashes the kernel, see logs: - xentop has 'lost' vnas as a domU - domu (dome122) is usable, but has a hanging nfs mount 013-06-18T23:02:55+02:00 dome122 kernel: [88925.616965] gdb[9186]: segfault at 7f3646c1f14a ip 00000000005d593d sp 00007fff4b70a690 error 4 in gdb[400000+4fc000] 2013-06-18T23:02:58+02:00 super logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vkbd/1/0 2013-06-18T23:02:58+02:00 super logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/console/1/0 2013-06-18T23:02:58+02:00 super logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vfb/1/0 2013-06-18T23:02:58+02:00 super avahi-daemon[1001]: Interface vif1.0.IPv6 no longer relevant for mDNS. 2013-06-18T23:02:58+02:00 super kernel: [89036.863875] br0: port 2(vif1.0) entered disabled state 2013-06-18T23:02:58+02:00 super kernel: [89036.863944] device vif1.0 left promiscuous mode 2013-06-18T23:02:58+02:00 super kernel: [89036.863947] br0: port 2(vif1.0) entered disabled state 2013-06-18T23:02:58+02:00 super avahi-daemon[1001]: Leaving mDNS multicast group on interface vif1.0.IPv6 with address fe80::fcff:ffff:feff:ffff. 2013-06-18T23:02:58+02:00 super avahi-daemon[1001]: Withdrawing address record for fe80::fcff:ffff:feff:ffff on vif1.0. 2013-06-18T23:02:58+02:00 super avahi-daemon[1001]: Withdrawing workstation service for vif1.0. 2013-06-18T23:02:58+02:00 super logger: /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/1/51728 2013-06-18T23:02:58+02:00 super logger: /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/1/51712 2013-06-18T23:02:58+02:00 super logger: /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/1/51744 2013-06-18T23:02:58+02:00 super logger: /etc/xen/scripts/vif-bridge: offline type_if=vif XENBUS_PATH=backend/vif/1/0 2013-06-18T23:02:58+02:00 super logger: /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/1/51760 2013-06-18T23:02:58+02:00 super logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vbd/1/51728 2013-06-18T23:02:58+02:00 super logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vbd/1/51744 2013-06-18T23:02:58+02:00 super logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vbd/1/51712 2013-06-18T23:02:58+02:00 super logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vbd/1/51760 2013-06-18T23:02:58+02:00 super logger: /etc/xen/scripts/vif-bridge: brctl delif br0 vif1.0 failed 2013-06-18T23:02:58+02:00 super logger: /etc/xen/scripts/vif-bridge: ifconfig vif1.0 down failed 2013-06-18T23:02:58+02:00 super logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge offline for vif1.0, bridge br0. 2013-06-18T23:02:58+02:00 super logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vif/1/0 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=825373 https://bugzilla.novell.com/show_bug.cgi?id=825373#c3 --- Comment #3 from Otrebor Igorig 2013-06-23 08:32:10 UTC --- One more test: I have moved one client DomU (dome121, OS12.1) to a different Dom0 host running Xen and OS12.2. Mounte the /home from the older nas (nfs3 only). Performed a compile test. This works without problems. Was to be expected as this was the previous setup for years. Now, mounted the home now from the vnas vm on the OS12.3 host. This produces the following behaviour (performed the test with nfs3 and nfs4, no difference): - The vnas DomU (12.3) doesn't hang anymore and seems usable - The OS12.2 client on the different Host hangs after a while and does not recover. Directly logging in as root via the xen console works as long as nothing is affected that requires the network. e.g. a df -h fails/hangs as there is a mounted nfs directory. Even a simple ping hangs forever. It seems that either the Xen 12.3 host (Dom0) or the 12.3 vnas DomU trashes the network stack of the client. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=825373 https://bugzilla.novell.com/show_bug.cgi?id=825373#c5 --- Comment #5 from Otrebor Igorig 2013-06-23 12:52:20 UTC --- Another test: I moved the vnas nfs server to the same Dom0 host (OS12.2) the client is running. I mounted the nfs3 /home share again and started the compile job. I got this behaviour: the client DomU (dome121, OS12.1) hangs and has a totally unusable network stack. The DomU containing the nfs server (vnas) remains usable. My guess now is, that the nfs server or network code in the DomU containing the nfs server (vnas) is somehow trashing the client network stack. The only remediation for dome121 is to 'xm destroy dome121' it and then 'xm create dome121' it again. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=825373 https://bugzilla.novell.com/show_bug.cgi?id=825373#c7 Otrebor Igorig changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|otrebor@hispeed.ch | --- Comment #7 from Otrebor Igorig 2013-08-05 20:24:45 UTC --- Thanks for coming back. Sorry for the delay I have been away for vacation. I confirm that there were no logs. The server vm just disappeared from the dom0 (xm top) without any crash dump, nothing. In the meantime I have brought all vm's up to date with the available patches. Now, the behaviour changes. The server vm doesn't disappear anymore, but leaves the client vm with the compile job hanging with an unusable network stack. In xm top the client vm seems still running. However the client vm cannot be pinged anymore from the outside. The only remediation is to xm destroy and then xm create the client vm again. for the record: - dom0 is OS12.3 all patches applied (xen Xen 4.2.1_12-1.12.10) (4 CPUs) - domU server is OS12.3 all patches applied running in paravirt mode (2 vCPUS) - domU client is a OS12.1 all patches applied running in paravirt mode (4 vCPU) - domU client is reproducibly working well if I nfs mount a copy of the files from an older Netgear NAS. Then the compile job runs smoothly. Again, no logs i can provide you. There are none. Not in /var/log/* not in dmesg To my unterstanding, this is a load related problem (race condition?). Mounting the nfs share and jumping around manually within that filesystem works as expected. Even running a 'find . -ls' over the entire filesystem seems to work. For the compile job i do a 'make distclean; make -j 8' but even 'make distclean; make -j 1' does not work. Thanks for the support. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=825373 https://bugzilla.novell.com/show_bug.cgi?id=825373#c9 Otrebor Igorig changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|otrebor@hispeed.ch | --- Comment #9 from Otrebor Igorig 2013-08-05 20:53:59 UTC --- yes ifconfig -a eth0 Link encap:Ethernet HWaddr 00:16:3E:31:CE:C4 inet addr:192.168.200.121 Bcast:192.168.200.255 Mask:255.255.255.0 inet6 addr: fe80::216:3eff:fe31:cec4/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:19715 errors:1 dropped:0 overruns:0 frame:0 TX packets:22035 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:7589276 (7.2 Mb) TX bytes:6763377 (6.4 Mb) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:33 errors:0 dropped:0 overruns:0 frame:0 TX packets:33 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2436 (2.3 Kb) TX bytes:2436 (2.3 Kb) df -h (hangs forever, needs ^C) ping 192.168.200.1 PING 192.168.200.1 (192.168.200.1) 56(84) bytes of data.

From 192.168.200.121 icmp_seq=1 Destination Host Unreachable From 192.168.200.121 icmp_seq=2 Destination Host Unreachable From 192.168.200.121 icmp_seq=3 Destination Host Unreachable ^C --- 192.168.200.1 ping statistics --- 5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 4016ms

-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=825373 https://bugzilla.novell.com/show_bug.cgi?id=825373#c Jeff Mahoney changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bpoirier@suse.com, | |jbohac@suse.com AssignedTo|kernel-maintainers@forge.pr |jbeulich@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=825373 https://bugzilla.novell.com/show_bug.cgi?id=825373#c12 --- Comment #12 from Otrebor Igorig 2013-08-16 21:09:12 UTC --- ok, here you go. dome122 is the domU where the compile runs and then hangs domenas13 is a domU with the nfs server providing the sources dome60 is the dom0 (xen host) 2013-08-16T22:01:31+02:00 dome122 HANG_C: +++ start nfs hang test +++ 2013-08-16T22:01:32+02:00 domenas13 HANG_S: +++ start nfs hang test +++ 2013-08-16T22:01:54+02:00 dome122 HANG_C: +++ start nfs hang test +++ 2013-08-16T22:02:06+02:00 dome122 HANG_C: +++ start compile 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239651] BUG: unable to handle kernel paging request at 00000b9800000014 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239665] IP: [<ffffffff801e5e83>] ext4_mb_good_group+0x63/0x170 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239677] PGD 0 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239680] Oops: 0000 [#1] SMP 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239685] Modules linked in: md5 xt_tcpudp xt_pkttype xt_LOG xt_limit nfsd lockd nfs_acl auth_rpcgss sunrpc ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_raw ipt_REJECT iptable_raw xt_CT iptable_filter ip6table_mangle nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_ipv4 nf_defrag_ipv4 ip_tables xt_conntrack nf_conntrack ip6table_filter ip6_tables x_tables joydev hwmon domctl autofs4 dm_mod linear scsi_dh_rdac scsi_dh_alua scsi_dh_emc scsi_dh_hp_sw scsi_dh xennet xenblk cdrom 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239736] CPU 0 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239740] Pid: 1478, comm: nfsd Not tainted 3.7.10-1.16-xen #1 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239744] RIP: e030:[<ffffffff801e5e83>] [<ffffffff801e5e83>] ext4_mb_good_group+0x63/0x170 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239749] RSP: e02b:ffff88003c699868 EFLAGS: 00010293 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239752] RAX: ffff8800038f9c00 RBX: 00000b9800000000 RCX: 0000000000000000 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239754] RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff88003e293c00 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239757] RBP: 0000000000000001 R08: ffff880003aebc00 R09: 0000000000000000 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239760] R10: ffff88003c699914 R11: 0000000000000000 R12: ffff88003b71d898 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239762] R13: ffff88003e293c00 R14: 0000000000000004 R15: 0000000000000020 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239767] FS: 00007f3816d4d700(0000) GS:ffff88003ec00000(0000) knlGS:0000000000000000 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239770] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239773] CR2: 00000b9800000014 CR3: 0000000003443000 CR4: 0000000000002660 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239776] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239779] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239782] Process nfsd (pid: 1478, threadinfo ffff88003c698000, task ffff88003c696180) 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239784] Stack: 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239786] 0000000000000000 ffff88003b71d898 ffff88003b71d898 0000000000000000 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239792] 0000000000000000 ffff88003e293c00 0000000000000001 ffffffff801e80ba 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239797] ffff88003a6c5510 ffff880003c0e9e0 ffff880003aebc00 0000000003c0ea00 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239803] Call Trace: 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239814] [<ffffffff801e80ba>] ext4_mb_regular_allocator+0x16a/0x420 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239820] [<ffffffff801e9d48>] ext4_mb_new_blocks+0x3c8/0x510 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239826] [<ffffffff801e041b>] ext4_ext_map_blocks+0xbcb/0x1580 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239832] [<ffffffff801b1e45>] ext4_map_blocks+0x1c5/0x260 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239839] [<ffffffff801b6176>] mpage_da_map_and_submit+0x166/0x4b0 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239844] [<ffffffff801b6ca7>] ext4_da_writepages+0x317/0x560 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239850] [<ffffffff800e74bc>] __filemap_fdatawrite_range+0x4c/0x60 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239856] [<ffffffff800e7520>] filemap_write_and_wait_range+0x50/0x70 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239861] [<ffffffff801acf3a>] ext4_sync_file+0x7a/0x390 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239874] [<ffffffffa01a4ee2>] nfsd_commit+0xb2/0xd0 [nfsd] 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239894] [<ffffffffa01b1d6d>] nfsd4_proc_compound+0x56d/0x750 [nfsd] 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239918] [<ffffffffa019fada>] nfsd_dispatch+0xea/0x230 [nfsd] 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239938] [<ffffffffa012573e>] svc_process_common+0x32e/0x6b0 [sunrpc] 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239964] [<ffffffffa0125e17>] svc_process+0x107/0x160 [sunrpc]2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.240108] ---[ end trace 7279af7d36e193f6 ]--- 2013-08-16T22:05:57+02:00 dome122 kernel: [ 1839.840178] nfs: server 192.168.200.13 not responding, still trying 2013-08-16T22:15:02.032075+02:00 dome60 kernel: [137714.180980] btrfs: unlinked 3 orphans 2013-08-16T22:28:29+02:00 dome122 kernel: [ 3191.264195] nfs: server 192.168.200.13 not responding, timed out 2013-08-16T22:32:05+02:00 dome122 kernel: [ 3407.840101] nfs: server 192.168.200.13 not responding, timed out 2013-08-16T22:32:05+02:00 dome122 kernel: [ 3407.840116] NFS: state manager failed on NFSv4 server 192.168.200.13 with error 5 2013-08-16T22:32:05+02:00 dome122 kernel: [ 3407.840159] nfs: server 192.168.200.13 not responding, timed out 2013-08-16T22:35:42+02:00 dome122 kernel: [ 3624.416165] nfs: server 192.168.200.13 not responding, timed out 2013-08-16T22:35:42+02:00 dome122 kernel: [ 3624.416229] nfs: server 192.168.200.13 not responding, timed out 2013-08-16T22:35:42+02:00 dome122 kernel: [ 3624.416238] NFS: state manager failed on NFSv4 server 192.168.200.13 with error 5 2013-08-16T22:37:40.710558+02:00 dome60 kcheckpass[15833]: pam_unix(xdm:auth): authentication failure; logname=robi uid=1004 euid=0 tty=:0 ruser= rhost= user=robi 2013-08-16T22:37:40.966191+02:00 dome60 kcheckpass[15833]: pam_sss(xdm:auth): authentication success; logname=robi uid=1004 euid=0 tty=:0 ruser= rhost= user=robi 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744412] BUG: unable to handle kernel paging request at 0000100000000008 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744429] IP: [<ffffffff8028e6d2>] memcpy+0x12/0x110 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744443] PGD 0 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744448] Oops: 0002 [#2] SMP 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744456] Modules linked in: md5 xt_tcpudp xt_pkttype xt_LOG xt_limit nfsd lockd nfs_acl auth_rpcgss sunrpc ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_raw ipt_REJECT iptable_raw xt_CT iptable_filter ip6table_mangle nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_ipv4 nf_defrag_ipv4 ip_tables xt_conntrack nf_conntrack ip6table_filter ip6_tables x_tables joydev hwmon domctl autofs4 dm_mod linear scsi_dh_rdac scsi_dh_alua scsi_dh_emc scsi_dh_hp_sw scsi_dh xennet xenblk cdrom 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744535] CPU 0 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744542] Pid: 1745, comm: sshd Tainted: G D 3.7.10-1.16-xen #1 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744548] RIP: e030:[<ffffffff8028e6d2>] [<ffffffff8028e6d2>] memcpy+0x12/0x110 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744556] RSP: e02b:ffff88003a25fd80 EFLAGS: 00010006 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744561] RAX: 0000100000000008 RBX: 0000000000000003 RCX: 0000000000000003 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744565] RDX: 0000000000000003 RSI: ffff88003d3ae800 RDI: 0000100000000008 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744570] RBP: ffff88003d3a6800 R08: 0000000000000000 R09: ffff88003e02d000 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744574] R10: 0000000000000002 R11: 0000000000000246 R12: ffff88003d3ae803 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744578] R13: 0000000000000003 R14: 0000000000000003 R15: ffff880003917400 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744587] FS: 00007f15574947c0(0000) GS:ffff88003ec00000(0000) knlGS:0000000000000000 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744592] CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744596] CR2: 0000100000000008 CR3: 0000000003b46000 CR4: 0000000000002660 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744602] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744607] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744612] Process sshd (pid: 1745, threadinfo ffff88003a25e000, task ffff88003a276500) 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744615] Stack: 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744619] ffffffff80326d6c ffff88003d3a69b0 0000000000000003 0000000000000000 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744628] 0000000000000000 0000000000000000 ffff8800036f8000 ffff88003d3a6800 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744637] ffff8800036f8518 ffff88003a276500 ffff88003d6d6dc0 ffff8800036f8000 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744646] Call Trace: 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744661] [<ffffffff80326d6c>] tty_insert_flip_string_fixed_flag+0x9c/0x110 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744672] [<ffffffff803284c4>] pty_write+0x34/0x70 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744681] [<ffffffff80322075>] n_tty_write+0x365/0x470 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744690] [<ffffffff8031e855>] tty_write+0x145/0x2d0 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744699] [<ffffffff80133077>] vfs_write+0xa7/0x180 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744707] [<ffffffff801333c1>] sys_write+0x51/0xa0 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744717] [<ffffffff8050ad0b>] system_call_fastpath+0x1a/0x1f 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744727] [<00007f155562c9c0>] 0x7f155562c9bf 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744731] Code: 43 58 48 2b 43 50 88 43 4e eb e9 90 90 90 90 90 90 90 90 90 90 90 90 90 90 48 89 f8 48 89 d1 48 c1 e9 03 83 e2 07 f3 48 a5 89 d1 <f3> a4 c3 20 4c 8b 06 4c 8b 4e 08 4c 8b 56 10 4c 8b 5e 18 48 8d 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744825] RIP [<ffffffff8028e6d2>] memcpy+0x12/0x110 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744831] RSP <ffff88003a25fd80> 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744835] CR2: 0000100000000008 2013-08-16T22:38:54+02:00 domenas13 kernel: [ 3845.744841] ---[ end trace 7279af7d36e193f7 ]--- 2013-08-16T22:38:54+02:00 domenas13 systemd-logind[418]: Removed session 1. 2013-08-16T22:39:18+02:00 dome122 kernel: [ 3840.992125] nfs: server 192.168.200.13 not responding, timed out 2013-08-16T22:39:34+02:00 domenas13 kernel: last message repeated 6 times 2013-08-16T22:39:37+02:00 domenas13 sshd[31432]: Accepted keyboard-interactive/pam for root from 192.168.200.60 port 42085 ssh2 2013-08-16T22:39:38+02:00 domenas13 sshd[31432]: pam_unix(sshd:session): session opened for user root by (uid=0) 2013-08-16T22:39:38+02:00 domenas13 systemd-logind[418]: New session 6 of user root. 2013-08-16T22:40:02+02:00 domenas13 kernel: last message repeated 5 times 2013-08-16T22:40:06+02:00 domenas13 rsyslogd: [origin software="rsyslogd" swVersion="7.2.7" x-pid="1847" x-info="http://www.rsyslog.com"] exiting on signal 15. 2013-08-16T22:40:27+02:00 domenas13 kernel: last message repeated 3 times 2013-08-16T22:40:27+02:00 domenas13 rsyslogd: [origin software="rsyslogd" swVersion="7.2.7" x-pid="31508" x-info="http://www.rsyslog.com"] start 2013-08-16T22:40:27+02:00 domenas13 systemd[1]: Started System Logging Service. 2013-08-16T22:40:27+02:00 domenas13 systemd[1]: Started Trigger Flushing of Journal to Persistent Storage. 2013-08-16T22:40:27+02:00 domenas13 systemd[1]: Starting System Logging Service... 2013-08-16T22:40:27+02:00 domenas13 systemd[1]: systemd-journald.service: main process exited, code=killed, status=10/USR1 2013-08-16T22:40:48.164493+02:00 dome60 logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vkbd/11/0 2013-08-16T22:40:48.183745+02:00 dome60 logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/console/11/0 2013-08-16T22:40:48.212554+02:00 dome60 avahi-daemon[841]: Interface vif11.0.IPv6 no longer relevant for mDNS. 2013-08-16T22:40:48.213704+02:00 dome60 avahi-daemon[841]: Leaving mDNS multicast group on interface vif11.0.IPv6 with address fe80::fcff:ffff:feff:ffff. 2013-08-16T22:40:48.213717+02:00 dome60 avahi-daemon[841]: Withdrawing address record for fe80::fcff:ffff:feff:ffff on vif11.0. 2013-08-16T22:40:48.214647+02:00 dome60 avahi-daemon[841]: Withdrawing workstation service for vif11.0. 2013-08-16T22:40:48.215957+02:00 dome60 kernel: [139260.364564] br0: port 5(vif11.0) entered disabled state 2013-08-16T22:40:48.215985+02:00 dome60 kernel: [139260.364678] device vif11.0 left promiscuous mode 2013-08-16T22:40:48.215988+02:00 dome60 kernel: [139260.364681] br0: port 5(vif11.0) entered disabled state 2013-08-16T22:40:48.244443+02:00 dome60 logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vfb/11/0 2013-08-16T22:40:48.253683+02:00 dome60 logger: /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/11/51712 2013-08-16T22:40:48.283938+02:00 dome60 logger: /etc/xen/scripts/vif-bridge: offline type_if=vif XENBUS_PATH=backend/vif/11/0 2013-08-16T22:40:48.288525+02:00 dome60 logger: /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/11/51728 2013-08-16T22:40:48.288558+02:00 dome60 logger: /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/11/51760 2013-08-16T22:40:48.289953+02:00 dome60 logger: /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/11/51744 2013-08-16T22:40:48.317191+02:00 dome60 logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vbd/11/51712 2013-08-16T22:40:48.341042+02:00 dome60 logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vbd/11/51760 2013-08-16T22:40:48.341692+02:00 dome60 logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vbd/11/51744 2013-08-16T22:40:48.348021+02:00 dome60 logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vbd/11/51728 2013-08-16T22:40:48.355293+02:00 dome60 logger: /etc/xen/scripts/vif-bridge: brctl delif br0 vif11.0 failed 2013-08-16T22:40:48.369175+02:00 dome60 logger: /etc/xen/scripts/vif-bridge: ifconfig vif11.0 down failed 2013-08-16T22:40:48.375339+02:00 dome60 logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge offline for vif11.0, bridge br0. 2013-08-16T22:40:48.400310+02:00 dome60 logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vif/11/0 2013-08-16T22:42:37+02:00 dome122 kernel: [ 4039.288100] nfs: server 192.168.200.13 not responding, timed out 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239987] [<ffffffffa019f0ef>] nfsd+0x9f/0x140 [nfsd] 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.239994] [<ffffffff80052733>] kthread+0xb3/0xc0 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.240001] [<ffffffff8050ac7d>] ret_from_fork+0x6d/0xa0 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.240006] Code: 70 38 45 8b b0 3c 03 00 00 d3 e8 48 83 ee 01 89 c1 49 8b 80 70 02 00 00 21 ee 83 fa 03 48 8b 04 c8 48 8b 1c f0 0f 87 e2 00 00 00 <44> 8b 6b 14 45 85 ed 74 74 83 fa 03 0f 85 93 00 00 00 48 8b 03 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.240064] RIP [<ffffffff801e5e83>] ext4_mb_good_group+0x63/0x170 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.240069] RSP <ffff88003c699868> 2013-08-16T22:03:02+02:00 domenas13 kernel: [ 1693.240072] CR2: 00000b9800000014 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=825373 https://bugzilla.novell.com/show_bug.cgi?id=825373#c13 --- Comment #13 from Otrebor Igorig 2013-08-16 21:14:42 UTC --- One additional note after providing the logs above. I have installed an equivalent setup on a kvm host instead of a xen host (same dom0 os, same nfs server os, exactly the same dome122 vm). There I do not have this lockup/timeout/hang. Everything works as expected. I suspect, this is a bug specific to xen. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=825373 https://bugzilla.novell.com/show_bug.cgi?id=825373#c15 Otrebor Igorig changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|otrebor@hispeed.ch | --- Comment #15 from Otrebor Igorig 2013-08-25 15:41:23 UTC --- Created an attachment (id=554074) --> (http://bugzilla.novell.com/attachment.cgi?id=554074) /var/log/messages form dome60 (dom0) This is the log file from the hypervisor -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=825373 https://bugzilla.novell.com/show_bug.cgi?id=825373#c17 --- Comment #17 from Otrebor Igorig 2013-08-25 15:44:17 UTC --- Created an attachment (id=554076) --> (http://bugzilla.novell.com/attachment.cgi?id=554076) /var/log/messages from the compile host (dome122, domU) This is the log file from the compile host that hangs forever (dome122, domU) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=825373 https://bugzilla.novell.com/show_bug.cgi?id=825373#c18 Jan Beulich changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |otrebor@hispeed.ch --- Comment #18 from Jan Beulich 2013-08-26 15:44:02 UTC --- Nothing stands out from the logs. Since the earlier mentioned changes meanwhile went into the repo, please give the kernel at http://download.opensuse.org/repositories/Kernel:/openSUSE-12.3/standard/x86... a try (needs to be installed in both host and guest(s) since both netfront and netback got adjusted). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=825373 https://bugzilla.novell.com/show_bug.cgi?id=825373#c20 --- Comment #20 from Otrebor Igorig 2013-09-15 13:30:48 UTC --- Created an attachment (id=558007) --> (http://bugzilla.novell.com/attachment.cgi?id=558007) dmesg for xen host (dom0) - crashing vm dmesg file for dom0 xen host (dome60) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=825373 https://bugzilla.novell.com/show_bug.cgi?id=825373#c22 --- Comment #22 from Otrebor Igorig 2013-09-15 13:51:33 UTC --- Created an attachment (id=558009) --> (http://bugzilla.novell.com/attachment.cgi?id=558009) driver script for repeatable test -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=825373 https://bugzilla.novell.com/show_bug.cgi?id=825373#c24 Jan Beulich changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High Status|NEW |RESOLVED Resolution| |DUPLICATE --- Comment #24 from Jan Beulich 2013-09-16 06:41:53 UTC --- Thanks for letting us know. *** This bug has been marked as a duplicate of bug 826374 *** http://bugzilla.novell.com/show_bug.cgi?id=826374 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.