|
|
|
|
|
|
|
|
|
|
xen-bugs
[Xen-bugs] [Bug 757] kernel BUG at mm/rmap.c:560!
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=757
------- Comment #7 from paul@xxxxxxxxxxx 2007-10-15 17:42 -------
(In reply to comment #6)
> Any idea what commands or processes were running in the guest at the time of
> the crash?
I can give you a list of the 'standard' processes that are always running on
the guest. I'm not sure of any way to find out if anything additional was
running. The standard processes are:
init [2]
[migration/0]
[ksoftirqd/0]
[watchdog/0]
[events/0]
[khelper]
[kthread]
[xenwatch]
[xenbus]
[kblockd/0]
[kseriod]
[pdflush]
[pdflush]
[kswapd0]
[aio/0]
[kpsmoused]
[kmirrord]
/sbin/syslogd
/sbin/klogd -x
/usr/sbin/cvsd -f /etc/cvsd/cvsd.conf
/usr/lib/postfix/master
pickup -l -t fifo -u -c
qmgr -l -t fifo -u
/usr/sbin/sshd
/usr/sbin/cron
/usr/sbin/apache2 -k start
/usr/sbin/apache2 -k start
/usr/sbin/apache2 -k start
/usr/sbin/apache2 -k start
/sbin/getty 38400 tty1
sshd: root@pts/0
-bash
ps aux
> It would be great if you could try and come up with a reliable way to repro.
I'll do my best. I've got nothing in the logs which helps me see what causes
this...
> You could collect a guest crashdump, but to be honest this kind of bug is
> tough
> to debug via a dump.
>
> Were you exercising save/restore/live relo?
No.
> Were you using the balloon driver?
No.
> Were you doing anything fancy with your networking setup?
No. We use the default bridge setup.
> Were you exercising the LVM snapshot stuff at the time? (in guest or host)
No. We use loopback files.
--
Configure bugmail:
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs
|
|
|
|
|