From: Sander Eikelenboom <linux@eikelenboom.it>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: infrequent kernel crash just before reboot
Date: Sun, 27 Jun 2010 10:16:49 +0200 [thread overview]
Message-ID: <93762471.20100627101649@eikelenboom.it> (raw)
In-Reply-To: <4C2614FE.4080007@goop.org>
Saturday, June 26, 2010, 4:55:58 PM, you wrote:
> On 06/26/2010 09:13 AM, Sander Eikelenboom wrote:
>> Hi All,
>>
>> Once in a while when i try to reboot my machine the kernel crashes, because it's so infrequently i haven't been able to capture it via a serial log yet.
>> I have made 2 photographs from what's left on screen from the oops.
>>
> Unfortunately your screenshots just miss out on the vital info to
> identify the source of the problem. However, one question: are there
> any domUs running at the the time? Or any stray tapdisk processes?
I was allready afraid for that, i also can't give you that info, since i was not paying much attention, since rebooting goes well most of the time.
I will try to keep an eye on it and hope i can report back again with more info.
> Thanks,
> J
>> Machine is running :
>>
>> serveerstertje:~# xm info
>> host : serveerstertje
>> release : 2.6.32.15+xen-2.6.32.x-20100622-b
>> version : #2 SMP Fri Jun 25 19:29:24 CEST 2010
>> machine : x86_64
>> nr_cpus : 6
>> nr_nodes : 1
>> cores_per_socket : 6
>> threads_per_core : 1
>> cpu_mhz : 3200
>> hw_caps : 178bf3ff:efd3fbff:00000000:00001310:00802001:00000000:000037ff:00000000
>> virt_caps : hvm
>> total_memory : 8126
>> free_memory : 3958
>> node_to_cpu : node0:0-5
>> node_to_memory : node0:3958
>> node_to_dma32_mem : node0:2810
>> max_node_id : 0
>> xen_major : 4
>> xen_minor : 0
>> xen_extra : .1-rc4-pre
>> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
>> xen_scheduler : credit
>> xen_pagesize : 4096
>> platform_params : virt_start=0xffff800000000000
>> xen_changeset : Tue Jun 22 07:31:14 2010 +0100 21226:7dcfdd45bc9e
>> xen_commandline : dom0_mem=768M loglvl=all loglvl_guest=all
>> cc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1)
>> cc_compile_by : root
>> cc_compile_domain :
>> cc_compile_date : Tue Jun 22 23:48:22 CEST 2010
>> xend_config_format : 4
>> serveerstertje:~#
>>
>>
>> kernel:
>> commit 01d9fbca207ec232c758d991d66466fc6e38349e
>> Merge: cfce2d4... 0a904db...
>> Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
>> Date: Tue Jun 15 14:09:48 2010 +0100
>>
>> Merge branch 'xen/next' into xen/stable-2.6.32.x
>>
>> * xen/next:
>> netback: minor code formatting fixup
>> Netback: Set allocated memory to zero from vmalloc.
>> xen/netback: linearise SKBs as we copy them into guest memory on guest-RX.
>> xen: netback: drop frag member from struct netbk_rx_meta
>> xen: netback: handle NET_SKBUFF_DATA_USES_OFFSET correctly
>> xen: netback: Fixes for delayed copy of tx network packets.
>> xen/gntdev: use spinlocks rather than rwsem for locking
>> xen: Fix to hugepages to work around new PWT handling
>> Fix compiler warning.
>> xen/balloon: update 'page' for each page
>>
>>
>>
>> --
>> Sander
--
Best regards,
Sander mailto:linux@eikelenboom.it
prev parent reply other threads:[~2010-06-27 8:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-26 8:13 infrequent kernel crash just before reboot Sander Eikelenboom
2010-06-26 14:55 ` Jeremy Fitzhardinge
2010-06-27 8:16 ` Sander Eikelenboom [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=93762471.20100627101649@eikelenboom.it \
--to=linux@eikelenboom.it \
--cc=jeremy@goop.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.