All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Bienzeisler <chosi@amd.co.at>
To: xen-devel@lists.xen.org
Subject: Re: 4.2.2 pci-passthrough crashes Dell Poweredge R710
Date: Wed, 15 May 2013 03:58:19 +0200	[thread overview]
Message-ID: <5192EBBB.50001@amd.co.at> (raw)
In-Reply-To: <20130515003145.GA14641@phenom.dumpdata.com>

Hello Konrad,

i pass it exactly the same way i did with 4.2.1. I have changed nothing. 
Right now i reverted to 4.2.1 and i'm not seeing this anymore. The 
problem right now is, that it seems like the hard crashes this corrupted 
my HVM LV filesystems and stuff is broken now. However, this is not 
related. I don't see this with 4.2.1.

passing through like this:

module options: xen-pciback.hide=(00:1a.0), which is an usb controller
win2k8.cfg (xl): pci = [ '00:1a.0' ]
xl pci-assignable-list output: 0000:00:1a.0

it worked flawlessly before and started breaking with 4.2.2 - i'm 
actually pretty sure this is not a hardware issue, since i can't 
reproduce it with 4.2.1. I think i might lack the skills to provide 
proper logs and crashdumps of whatever sort. That's all i can tell you 
right now.

cheers,
Alex


Am 15.05.2013 02:31, schrieb Konrad Rzeszutek Wilk:
> On Tue, May 14, 2013 at 10:29:27AM +0200, Alexander Bienzeisler wrote:
>> Hello everyone,
>>
>> i just updated from 4.2.1 to 4.2.2. If i try to fire up my win2k8
>> domU with a pci device attached, the dom0 machine hardcrashes.
> How do you pass in the PCI device? I don't see in your xl info the
> capability listed to do VT-d. Does your machine do VT-d?
>> my system log (idrac) shows the following:
>>
>> CPU 2 has an internal error (IERR).
>> A bus fatal error was detected on a component at bus 0 device 0 function 0.
>> CPU 1 machine check detected.
>>
>> and plenty of other entries. The machine hardresets then.
>> If i leave the faulty machine down after a reboot, nothing like this
>> happens.
>>
>> xl info:
>>> host                   : susi-0
>>> release                : 3.8.2-ipmi
>>> version                : #4 SMP Mon Mar 11 12:54:31 CET 2013
>>> machine                : x86_64
>>> nr_cpus                : 12
>>> max_cpu_id             : 31
>>> nr_nodes               : 2
>>> cores_per_socket       : 6
>>> threads_per_core       : 1
>>> cpu_mhz                : 3325
>>> hw_caps                : bfebfbff:2c100800:00000000:00003f40:029ee3ff:00000000:00000001:00000000
>>> virt_caps              : hvm
>>> total_memory           : 98291
>>> free_memory            : 62390
>>> sharing_freed_memory   : 0
>>> sharing_used_memory    : 0
>>> free_cpus              : 0
>>> xen_major              : 4
>>> xen_minor              : 2
>>> xen_extra              : .2
>>> 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          : unavailable
>>> xen_commandline        : placeholder loglvl=all dom0_mem=2048M
>>> dom0_max_vcpus=2 com2=115200 console=com2,vga
>>> cc_compiler            : gcc (Debian 4.4.5-8) 4.4.5
>>> cc_compile_by          : root
>>> cc_compile_domain      : wsk.tu-chemnitz.de
>>> cc_compile_date        : Tue May 14 09:16:43 CEST 2013
>>> xend_config_format     : 4
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> http://lists.xen.org/xen-devel
>>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  reply	other threads:[~2013-05-15  1:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-14  8:29 4.2.2 pci-passthrough crashes Dell Poweredge R710 Alexander Bienzeisler
2013-05-14 13:32 ` Jan Beulich
2013-05-15  0:31 ` Konrad Rzeszutek Wilk
2013-05-15  1:58   ` Alexander Bienzeisler [this message]
2013-05-15  6:32     ` Pasi Kärkkäinen
2013-05-15  8:33       ` Jan Beulich

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=5192EBBB.50001@amd.co.at \
    --to=chosi@amd.co.at \
    --cc=xen-devel@lists.xen.org \
    /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.