[Bug 851445] New: OOPS on Opensuse 13.1 Xen Guest launch @ boot; relaunch after boot == error, NO oops, functions OK
https://bugzilla.novell.com/show_bug.cgi?id=851445 https://bugzilla.novell.com/show_bug.cgi?id=851445#c0 Summary: OOPS on Opensuse 13.1 Xen Guest launch @ boot; relaunch after boot == error, NO oops, functions OK Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Xen AssignedTo: jdouglas@suse.com ReportedBy: ar16@imapmail.org QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 I'll start here @Xen ... I upgraded an existing Xen Guest, running on an exsiting 12.3 Dom0, from 123 -> 13.1 After boot xl list Name ID Mem VCPUs State Time(s) Domain-0 0 1241 4 r----- 41.6 test0013 1 1024 2 -b---- 7.3 Unable to connect to the Guest xl console 1 [ 0.170235] PCI: Fatal: No config space access function found [ 0.170285] Unable to read sysrq code in control/sysrq [ 1.258696] i8042: No controller found [ 1.259522] /home/abuild/rpmbuild/BUILD/kernel-xen-3.11.6/linux-3.11/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 12.431003] BUG: unable to handle kernel NULL pointer dereference at 0000000000000010 [ 12.431180] IP: [<ffffffffa00f9b0c>] rpc_pipefs_event+0x17c/0x270 [sunrpc] [ 12.431342] PGD 0 [ 12.431392] Oops: 0000 [#1] SMP [ 12.431468] Modules linked in: rpcsec_gss_krb5 nfsv4 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 n_hdlc slhc nfsd auth_rpcgss oid_registry nfs_acl nfs fscache lockd sunrpc sg autofs4 scsi_dh_alua scsi_dh_emc scsi_dh_rdac scsi_dh_hp_sw scsi_dh dm_mirror dm_region_hash dm_log dm_snapshot dm_crypt dm_mod sha512_generic sha256_generic sha1_generic ablk_helper cryptd lrw gf128mul glue_helper aes_x86_64 fuse xennet xenblk cdrom [ 12.432068] CPU: 0 PID: 1160 Comm: mount Not tainted 3.11.6-4-xen #1 [ 12.432068] Hardware name: Xen 4.3.0_14-281.1 PV guest [ 12.432068] task: ffff88003cf3c7c0 ti: ffff88003d37e000 task.ti: ffff88003d37e000 [ 12.432068] RIP: e030:[<ffffffffa00f9b0c>] [<ffffffffa00f9b0c>] rpc_pipefs_event+0x17c/0x270 [sunrpc] [ 12.432068] RSP: e02b:ffff88003d37fd38 EFLAGS: 00010287 [ 12.432068] RAX: ffff88003df150c0 RBX: ffff880001567e00 RCX: 0000000000000002 [ 12.432068] RDX: 0000000000000000 RSI: 0000000000070007 RDI: 0000000000000000 [ 12.432068] RBP: 0000000000000000 R08: ffff88003dfb1350 R09: 0000000000000000 [ 12.432068] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 [ 12.432068] R13: ffff88000176f000 R14: ffff8800015cba00 R15: ffff8800015cba70 [ 12.432068] FS: 00007f0f2f21a840(0000) GS:ffff88003ec00000(0000) knlGS:0000000000000000 [ 12.432068] CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 12.432068] CR2: 0000000000000010 CR3: 000000003cd48000 CR4: 0000000000000660 [ 12.432068] Stack: [ 12.432068] 00000000ffffffff ffffffffa01f1740 0000000000000000 0000000000000000 [ 12.432068] ffff88000176f000 ffff8800015cba30 ffffffff80521304 ffffffffa0128740 [ 12.432068] 0000000000000000 0000000000000000 ffff88000176f000 00000000ffffffff [ 12.432068] Call Trace: [ 12.432068] [<ffffffff80521304>] notifier_call_chain+0x44/0x70 [ 12.432068] [<ffffffff800564c2>] __blocking_notifier_call_chain+0x42/0x60 [ 12.432068] [<ffffffffa0111cd8>] rpc_fill_super+0xe8/0x1a0 [sunrpc] [ 12.432068] [<ffffffff8013c07a>] mount_ns+0x9a/0xe0 [ 12.432068] [<ffffffff8013ca5f>] mount_fs+0x2f/0x1a0 [ 12.432068] [<ffffffff80157135>] vfs_kern_mount+0x55/0xe0 [ 12.432068] [<ffffffff80159380>] do_mount+0x230/0xa40 [ 12.432068] [<ffffffff80159c0c>] SyS_mount+0x7c/0xc0 [ 12.432068] [<ffffffff805252ab>] system_call_fastpath+0x1a/0x1f [ 12.432068] [<00007f0f2eb0709a>] 0x7f0f2eb07099 [ 12.432068] Code: 89 ef 48 8b 50 20 e8 f4 d5 ff ff 48 85 c0 0f 84 de 00 00 00 48 3d 00 f0 ff ff 0f 87 ec 00 00 00 48 8b 7b 58 48 89 83 b0 00 00 00 <48> 8b 47 10 48 8b 40 38 48 85 c0 0f 84 5d ff ff ff ff d0 85 c0 [ 12.432068] RIP [<ffffffffa00f9b0c>] rpc_pipefs_event+0x17c/0x270 [sunrpc] [ 12.432068] RSP <ffff88003d37fd38> [ 12.432068] CR2: 0000000000000010 [ 12.457222] ---[ end trace 98855f9763b690d5 ]--- destroy the guest xl destroy 1 relaunch it @ shell xl create -c /etc/xen/auto/test0013.cfg it displays ... Daemon running with PID 5173 [ 0.164960] PCI: Fatal: No config space access function found [ 0.165538] Unable to read sysrq code in control/sysrq [ 1.251525] i8042: No controller found [ 1.352166] /home/abuild/rpmbuild/BUILD/kernel-xen-3.11.6/linux-3.11/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) then waits ~ 30 seconds ... and suddenly proceeds to login pyGRUB version 0.6 ┌────────────────────────────────────────────────────────────────────────┐ │ Xen4 - openSUSE 13.1 │ │ Hard Disk │ │ │ Welcome to openSUSE 13.1 "Bottle" - Kernel 3.11.6-4-xen (xvc0). test0013 login: test0013 Password: ############ Have a lot of fun... [1][test0013@test0013: /home/test0013]$ uname -a Linux test0013 3.11.6-4-xen #1 SMP Wed Oct 30 18:04:56 UTC 2013 (e6d4a27) x86_64 x86_64 x86_64 GNU/Linux and appears to function correctly from here on The OOPS is reproducible -- on boot; the subsequent OK launch -- despite the error/delay -- is too. Retry with a similarly configured 12.3 Guest -- no problems. It's something unique to this upgrade, v13.1 Guest ... Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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=851445
https://bugzilla.novell.com/show_bug.cgi?id=851445#c
Charles Arnold
https://bugzilla.novell.com/show_bug.cgi?id=851445
https://bugzilla.novell.com/show_bug.cgi?id=851445#c1
Jan Beulich
https://bugzilla.novell.com/show_bug.cgi?id=851445
https://bugzilla.novell.com/show_bug.cgi?id=851445#c2
--- Comment #2 from A R
What's the reason you picked component Xen rather than Kernel?
this OOPS was only occurring when booting to kernel-xen+Xen. hence, "Xen", and the initial caveat: "I'll **start** here ..."
Also posting partial logs is generally not helpful - please attach full guest kernel logs (from both the oopsing and non-oopsing attempts).
as I've continued to investigate, I find -- so far -- ALL my machines (atm, 4) that (1) are working 12.3+xen Dom0 servers (2) have /boot-on-RAID(soft, RAID-1) and LVM-on-RAID(soft, RAID1 or RAID10) (3) have nfs-kernel-server installed (4) mount shares @ other nfs servers (5) have been in-place upgraded to 13.1 are now failing to boot. Booting these machines to kernel-xen+Xen always hangs, and results frequently-not-always in an OOPS; booting the same machines to kernel-default always hangs, but no OOPS. OTOH, all upgraded machines that are Xen Guests, or just kernel-desktop or kernel-default boots, and have NO RAID in the mix, but DO have !boot-on-LVM are booting OK. that's true for both new installs, and in-place 12.3 -> 13.3 upgrades. ATM, I'm trying to figure out if/how mdadm + lvm2 is involved, if not responsible ... (https://bugzilla.novell.com/show_bug.cgi?id=851741 and http://www.spinics.net/lists/raid/msg44943.html) I'm working to get something consistent/useful to post/attach. No problem for me if this issue gets moved 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=851445
https://bugzilla.novell.com/show_bug.cgi?id=851445#c3
A R
participants (1)
-
bugzilla_noreply@novell.com