All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Anders <anders@anduras.de>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Subject: Re: Xen 4.0.1 freezes with no output
Date: Wed, 08 Sep 2010 14:44:21 +0200	[thread overview]
Message-ID: <4C878525.7090609@anduras.de> (raw)
In-Reply-To: <20100908111737.GG2804@reaktio.net>

Pasi Kärkkäinen schrieb:
> On Wed, Sep 08, 2010 at 11:49:07AM +0200, Sven Anders wrote:
>> Pasi Kärkkäinen schrieb:
>>> On Tue, Sep 07, 2010 at 08:50:10PM +0200, Sven Anders wrote:
>>>
>>>>> Also 2.6.32.21 is the latest pvops dom0 kernel atm.
>>> Yep, that'll give you 2.6.32.21 atm.
>> Ok, I tested the latest one. It crashes too. Same phenomenon.
> 
> Ok, I added xen-devel to CC.

>> I'm still uncertain about this error message:
>>  XENBUS: Unable to read cpu state
>>
>> Are these harmless and can I ignore them? What can be the cause?

Any comment to this ?

> How long does it take before it silently crashes?

Last time it took 26 minutes (running top with 0.5 seconds update in
parallel). Last active process was xend.

This time only 1½ minutes:

"Screenshot":

 top - 14:34:44 up 1 min,  1 user,  load average: 0.23, 0.16, 0.06
 Tasks: 158 total,   2 running, 156 sleeping,   0 stopped,   0 zombie
 Cpu(s):  0.0%us,  0.3%sy,  0.0%ni, 99.7%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
 Mem:   1919620k total,   190480k used,  1729140k free,     4576k buffers
 Swap:        0k total,        0k used,        0k free,    42384k cached

   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
  6782 root      20   0  2316 1168  872 R    2  0.1   0:00.99 top
     1 root      20   0  2852 1692  548 S    0  0.1   0:01.57 init


Intrestingly in my previous test the "xend" refused to start and the system
did not crash for 1 hour and 20 minutes. Then I rebooted, because the "xend" was
not running. The "xend" gave the following error message:

  File "usr/lib/python2.5/site-packages/xen/util/pci.py", line 1226, in find_capability
    ('Looped capability chain: %s' % self.name))
PciDeviceParseError: Looped capability chain: 0000:07:00.0
[2010-09-08 14:28:26 6885] INFO (SrvDaemon:220) Xend exited with status 1.

This seems to be caused by wrong PCI data (or initialization). An "lspci" gave
the following:

 07:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection (rev ff)
 08:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection (rev ff)

The revision of 'ff' is bogus. The pci config data presented in /sys or /proc was
only "ff,ff,...", hence the wrong revision.
I had to switch of the hardware to normalize this.

After this the "xend" was starting and the system crashed...

Regards
 Sven

-- 
 Sven Anders <anders@anduras.de>                 () UTF-8 Ribbon Campaign
                                                 /\ Support plain text e-mail
 ANDURAS intranet security AG
 Messestraße 3 - 94036 Passau - Germany
 Web: www.anduras.de - Tel: +49 (0)851-4 90 50-0 - Fax: +49 (0)851-4 90 50-55

Rechtsform: Aktiengesellschaft - Sitz: Passau - Amtsgericht: Passau HRB 6032
Mitglieder des Vorstands: Dipl.-Inf. Sven Anders, Dipl.-Inf. Marcus Junker
Vorsitzender des Aufsichtsrats: RA Mark Peters

  reply	other threads:[~2010-09-08 12:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4C864321.3070302@anduras.de>
     [not found] ` <20100907172401.GA2804@reaktio.net>
     [not found]   ` <4C868962.7040305@anduras.de>
     [not found]     ` <20100907185310.GB2804@reaktio.net>
     [not found]       ` <4C875C13.7030501@anduras.de>
2010-09-08 11:17         ` Xen 4.0.1 freezes with no output Pasi Kärkkäinen
2010-09-08 12:44           ` Sven Anders [this message]
2010-09-09 18:11             ` [Xen-users] " Pasi Kärkkäinen

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=4C878525.7090609@anduras.de \
    --to=anders@anduras.de \
    --cc=pasik@iki.fi \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-users@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.