Okay, I think I have figured this out. Pretty scary if I'm right

The box runs headless and has a serial console. I basically copied the
configuration from a gutsy box for this which gives me the following
settings in grub/menu.lst

---
## Xen hypervisor options to use with the default Xen boot option
# xenhopt=console=com1,vga com1=57600,8n1

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=ttyS0,57600n1
---

This shows all xen, kernel and bootup messages right until the "Running
local boot scripts", but obviously no prompt. For that I copied the file
/etc/event.d/ttyS0 from a gutsy box as well

---
start on stopped rc2
start on stopped rc3
start on stopped rc4
start on stopped rc5

stop on runlevel 0
stop on runlevel 1
stop on runlevel 6

respawn
exec /sbin/getty -L ttyS0 57600 vt102
---

I still did not get a prompt but did not have a second look, because the
box was crashing very frequently and I tried to figure out this problem
first.

Today I learned that I need to use xvc0 instead of ttyS0. I changed my
config, got a login prompt and the box was suddenly way more stable. It
usually died within minutes when I did something I/O intensive (e.g.
bonnie++, no matter whether on a local partition or a drbd8 volume, or
using debootstrap)

I did the test, after reenabling ttyS0 the box crashed as violent and
often as before. It does not appear to happen when ttyS0 is started
after the bootup process. Every access to ttyS0 is blocked with an
Input/Output error, so getty is restarted in a loop by upstart.

My guess is that accessing/writing to ttyS0 from within dom0 compromises
kernel memory and leads to a crash at some time.

Removed ttyS0 now and will be running bonnie++ on a drbd volume over
night, I hope I can confirm this tomorrow.

-- 
[hardy][xen] Oops in free_hot_cold_cache, probably drbd8-related
https://bugs.launchpad.net/bugs/235783
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to