similar to: dma_alloc_coherent issue with tg3 in x86_64 build

Displaying 20 results from an estimated 2000 matches similar to: "dma_alloc_coherent issue with tg3 in x86_64 build"

2008 Jun 11
2
Not seeing all memory in CentOS 5.1 x86_64
I'm running CentOS 5.1 with all updates, and the xen kernel. For some reason the OS is not seeing the full amount of ram. #uname -a Linux CentOS-VM-A 2.6.18-53.1.21.el5xen #1 SMP Tue May 20 10:03:27 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux # free total used free shared buffers cached Mem: 6104064 3445136 2658928 0 1412236
2007 Mar 26
12
System time monotonicity
It seems that VCPU system time isn''t monotonic (using 3.0.4). It seems it might be correlated to when a VCPU is switched across real CPUs but I haven''t conclusively proved that. But e.g.: { old = { time = { version = 0x4ec pad0 = 0xe8e0 tsc_timestamp = 0x22cc8398b7194 system_time =
2012 Dec 14
8
3.8.0-rc0 on xen-unstable: RCU Stall during boot as dom0 kernel after IOAPIC
Hi Konrad, I just tried to boot a 3.8.0-rc0 kernel (last commit: 7313264b899bbf3988841296265a6e0e8a7b6521) as dom0 on my machine with current xen-unstable. The boot stalls: [ 0.000000] ACPI: PM-Timer IO Port: 0x808 [ 0.000000] ACPI: Local APIC address 0xfee00000 [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01]
2009 Sep 30
3
Gathering information about RAM in sockets
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi list, I have an IBM xseries 345, running CentOS 5.3, hosting a few Xen domUs. However, I need more RAM -- but cannot remember if all (four) RAM sockets are populated (which would mean to buy higher capacity modules) or if there are two slots left to use. However, I'd like (and think that it's possible, but don't remember how) to
2008 Apr 21
7
Weird network performance behaviour?
I'm recording TCP network throughput performance between Dom0 IP stack and all my guest domains (currently 6 running simultaneously). All guests are running simultaneously, but I only ever transmit between Dom0 and one of the DomUs while the other five are idle. When running a netperf TCP_STREAM test (netperf on Dom0, netserver on DomU) I record the following performance numbers, CPU % as
2010 May 21
2
Xen 4.1-unstable does not boot up
Hi, An APIC error continues happening. __ __ _ _ _ _ _ _ \ \/ /___ _ __ | || | / | _ _ _ __ ___| |_ __ _| |__ | | ___ \ // _ \ ''_ \ | || |_ | |__| | | | ''_ \/ __| __/ _` | ''_ \| |/ _ \ / \ __/ | | | |__ _|| |__| |_| | | | \__ \ || (_| | |_) | | __/ /_/\_\___|_| |_| |_|(_)_| \__,_|_|
2005 Nov 21
5
Error: Error creating domain: (22, ''Invalid argument'')
Hi there I get the following error message when i try to "xm create <domid>" Error: Error creating domain: (22, ''Invalid argument'') I have included everything i can think of Thanks The DomU config is kernel = "/boot/vmlinuz-2.6.12-xenU" ramdisk = "/boot/initrd-2.6.12.6-xenU.img" memory = 128 name = "xen01" nics=1 disk = [
2006 Nov 18
1
Xen 3.0.3 with CentOS 4.4
I''ve installed Xen kernel for dom0 on a CentOS 4.4 but when i reboot the kernel says: _/\_\___|_| |_| |____(_)___(_)____(_)___/ http://www.cl.cam.ac.uk/netos/xenmdev = 59.12 University of Cambridge Computer Laboratory6 Sep 26 01:52 qemu-dm.6463.log Xen version 3.0.3.0 (root@uk.xensource.com) (gcc version 3.4.6 20060404 (Red Hastart qemu- -rw-r--r-- 1 root root t 3.4.6-3)) Mon Oct
2005 Jun 15
2
x86_64 - Dom0 will not boot on EMT64
I am unable to boot Dom0 on my IBM eServer BladeCenter HS20, type 8843, EMT64 blades. I have read reports that Dom0 boots on Opteron boxes, but on my EMT64 blades, it does not. Has anyone else encountered this problem on EMT64 hardware? Here are the errors I am getting: This is on a SLES 9 box, gcc version 3.3.3 (SuSE Linux): kernel (hd0,0)/boot/xen.gz dom0_mem=256000 com2=19200,8n1
2012 Jul 27
4
3.5.0 dom0 crash on boot
Hi, I''ve not tried pv_ops for a long time but just got a new system (Supermicro X9DRL-iF) so decided to try 3.5.0 with the latest Xen 4.2-unstable, unfortunately the system crashes immediately after loading dom0: traps.c:486:d0 Unhandled invalid opcode fault/trap [#6] on VCPU 0 [ec=0000] I''ve tried loading both bzImage and vmlinuz (gzip compressed vmlinuz) with the same
2007 Aug 22
5
Bug#439156: xen-hypervisor-3.0.3-1-amd64: large memory not detected
Package: xen-hypervisor-3.0.3-1-amd64 Version: 3.0.3-0-2 Severity: important On a machine with 2 dual-core Opterons and 16GB of memory, only about 3GB is detected by the hypervisor. Transcript: root at thismachine:~# xm dmesg Xen version 3.0.3-1 (Debian 3.0.3-0-2) (ultrotter at debian.org) (gcc version 4.1.2 20061028 (prerelease) (Debian 4.1.1-19)) Fri Nov 3 00:21:27 CET 2006 Latest
2011 Feb 11
4
Xen hypervisor failed to startup when booting CPUs
Hi Folks: I run into a problem when enabling Xen in next generation server platforms with Xen c/s is 21380. Xen reported "CPU Not responding" when booting up 32 CPUs( 2 sockets with 8 cores/16threads total). The log files belonging showed something wrong with APCI. So I added x2apic=0 in the xen grub line, but the symptom remained. However, Native RHEL5.5 can
2018 Feb 09
2
retpoline mitigation and 6.0
On Fri, 2018-02-09 at 10:36 +0000, David Woodhouse wrote: > > Did you get anywhere with the function attribute? Having isolated the > next boot failure to "it goes away if I compile io_apic.c without > retpoline", bisecting it per-function would help to further delay the > bit where I actually have to start *thinking*... It's mp_register_ioapic(), and only when
2005 Nov 19
6
correct procedure for reporting kernel problems?
I''ve had domU''s hickup a few times with latest unstable, and I guess this can be expected. Is there a procedure in place to report these problems? For exampe: Unable to handle kernel paging request at virtual address c12b46c0 printing eip: cpanel cpanel.mydomain c02555f7 *pde = ma 7e9fc067 pa 00002067 *pte = ma 00000000 pa 55555000 Oops: 0002 [#1] PREEMPT SMP Modules
2011 Dec 20
10
Problem booting xen 4.1.2 on Athlon 64 X2
Adding apic_verbosity=debug gives me that (hope nothing miss-typed as I have no serial console on this box). I found a lot of suggested workarounds: - noapic as suggested in output gives an noapic isn''t support - acpi_skip_timer_override has no effect at all Thx, Florian (XEN) Initing memory sharing. (XEN) AMD-Vi: IOMMU not found! (XEN) I/O virtualisation disabled (XEN) Getting
2011 Dec 20
10
Problem booting xen 4.1.2 on Athlon 64 X2
Adding apic_verbosity=debug gives me that (hope nothing miss-typed as I have no serial console on this box). I found a lot of suggested workarounds: - noapic as suggested in output gives an noapic isn''t support - acpi_skip_timer_override has no effect at all Thx, Florian (XEN) Initing memory sharing. (XEN) AMD-Vi: IOMMU not found! (XEN) I/O virtualisation disabled (XEN) Getting
2018 Feb 09
0
retpoline mitigation and 6.0
On Fri, 2018-02-09 at 12:54 +0000, David Woodhouse wrote: > On Fri, 2018-02-09 at 10:36 +0000, David Woodhouse wrote: > >  > > Did you get anywhere with the function attribute? Having isolated the > > next boot failure to "it goes away if I compile io_apic.c without > > retpoline", bisecting it per-function would help to further delay the > > bit where I
2010 Nov 09
4
Xen 3.4.3and CentOS PCIback
Hi, I''m using CentOS 5.5 x86_64 xen 3.43 from gitco.de and I have an Openvox A1200P voip card and am passing it thru to another centos 5.5 DomU, when I 1st start the domain driver loads and everything seems quite nice and the device works, but after a reboor of the DomU, this is shown on my Dom0 dmesg Here''s Dom0 info [root@xen ~]# dmesg Bootdata ok (command line is ro
2010 Nov 09
4
Xen 3.4.3and CentOS PCIback
Hi, I''m using CentOS 5.5 x86_64 xen 3.43 from gitco.de and I have an Openvox A1200P voip card and am passing it thru to another centos 5.5 DomU, when I 1st start the domain driver loads and everything seems quite nice and the device works, but after a reboor of the DomU, this is shown on my Dom0 dmesg Here''s Dom0 info [root@xen ~]# dmesg Bootdata ok (command line is ro
2010 Dec 16
19
Hypervisor hangs on startup
Hi! We have a problem that the dom0 very often does not boot and hangs in the hypervisor - see screenshot. The last message is: (XEN) Dom0 has maximum 16 VCPUs (afterwards xen should overwrite the memory) We are using the xen kernel from kernel.org git. Kernel is 2.6.32.24-xen with Xen 4.0.1 Hardware is HP DL380. Is this a known problem? Any hints what could be the problem and how we can