Port-xen archive

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

Re: Instability issues with NetBSD-9, xen-4.11 and the xbdb backend driver

	hello.  Here are the results of trying an 8.1 kernel in place of my
5.2 kernel.  It actually does much worse than the 5.2 kernel.  The 5.2
kernel runs reliably under light loads.  8.1
doesn't run at all.


Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
    2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017,
    2018, 2019 The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
    The Regents of the University of California.  All rights reserved.

NetBSD 8.1_STABLE (XEN3_DOMU) #0: Wed Nov  6 10:27:05 UTC 2019
total memory = 8192 MB
avail memory = 7922 MB
cpu_rng: RDSEED
running cgd selftest aes-xts-256 aes-xts-512 done
mainbus0 (root)
hypervisor0 at mainbus0: Xen version 4.8.5nb0
vcpu0 at hypervisor0
vcpu0: Intel(R) Xeon(R) CPU E5-2623 v4 @ 2.60GHz, id 0x406f1
vcpu0: package 0, core 0, smt 0
xenbus0 at hypervisor0: Xen Virtual Bus Interface
xencons0 at hypervisor0: Xen Virtual Console Driver
xenbus: can't get state for device/suspend/event-channel (2)
xbd0 at xenbus0 id 2: Xen Virtual Block Device Interface
xennet0 at xenbus0 id 0: Xen Virtual Network Interface
xennet0: MAC address 00:16:3e:3a:68:80
balloon0 at xenbus0 id 0: Xen Balloon driver
balloon0: current reservation: 8388608 KiB
xennet0: using RX copy mode
boot device: xbd0
root on xbd0a dumps on xbd0b
Your machine does not initialize mem_clusters; sparse_dumps disabled
root file system type: ffs
xenbus: can't get state for device/suspend/event-channel (2)
balloon0: current reservation: 2097152 pages => target: 2097152 pages
ignore shutdown request: 
xenbus: can't get state for device/suspend/event-channel (2)
Wed Nov 13 10:04:58 PST 2019
Starting watchdog timer.
wdogctl: open /dev/watchdog: Operation not permitted
dk_lookup on device: /dev/sd0a failed!
dk_lookup on device: /dev/sd1a failed!
RAIDFRAME: Did not find any live disks in the array.
RAIDFRAME: failed rf_ConfigureDisks with 22
raid0: raidstart not ready
raidctl: ioctl (RAIDFRAME_CONFIGURE) failed: Invalid argument
swapctl: adding /dev/xbd0b as swap device at priority 0
/etc/rc: WARNING: $fixsb is not set properly - see rc.conf(5).
Starting file system checks:
panic: biodone2 already
fatal breakpoint trap in supervisor mode
trap type 1 code 0 rip 0xffffffff80205af5 cs 0xe030 rflags 0x246 cr2 0x797368906107 ilevel 0 rsp 0xffffa00183f7bde0
curlwp 0xffffa0000e8bc000 pid 0.4 lowest kstack 0xffffa00183f782c0
Stopped in pid 0.4 (system) at  netbsd:breakpoint+0x5:  leave
breakpoint() at netbsd:breakpoint+0x5
vpanic() at netbsd:vpanic+0x140
snprintf() at netbsd:snprintf
biointr() at netbsd:biointr
biointr() at netbsd:biointr+0x33
softint_thread() at netbsd:softint_thread+0x5c
ds          0
es          bda0
fs          bdf0
gs          8
rdi         0
rsi         a
rbp         ffffa00183f7bde0
rbx         104
rdx         ffffffff806593c0    cpu_info_primary
rcx         0
rax         1
r8          ffffa00183f7bd88
r9          8080808080808080
r10         73
r11         ffffffff806593c0    cpu_info_primary
r12         ffffffff805c0943    ostype+0x22510
r13         ffffa00183f7be28
r14         0
r15         ffffa0000e8bc000
rip         ffffffff80205af5    breakpoint+0x5
cs          e030
rflags      246
rsp         ffffa00183f7bde0
ss          e02b
netbsd:breakpoint+0x5:  leave
db{0}> xen-hardconnect# 

Home | Main Index | Thread Index | Old Index