Joseph, sorry for the delay - I am somehow not getting email updates on
bugs that I've commented on.
So applying the patches requires them to be upstream - and while Dave
Airlie had not trouble with them, he did suggest to concentrate on
PCIe/PCI subset.
Anyhow, I can dust them off and start res
Joseph, ugh. I don't think Greg KH's would be OK with submitting feature
drivers in stable kernels? Has he done so in the past?
Anyhow here are the links to the gits for this driver and its belt-and-suspends:
Mechanism to disable the CPU freq drivers.
http://git.kernel.org/?p=linux/kernel/git/torv
And this one (which calls disable_cpufreq()):
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=48cdd8287f47a3cdad5b9273a5ef81bf605f7826
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
They are in #linux-next for 3.4:
http://git.kernel.org/?p=linux/kernel/git/konrad/xen.git;a=commit;h=59a56802918100c1e39e68c30a2e5ae9f7d837f0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/898112
Titl
On Mon, Jan 14, 2013 at 03:57:48PM -, Stefan Bader wrote:
> Starting with kernel v3.7 the following commit added a quirk
> to obtain the real frequencies of certain AMD systems:
>
> commit f594065faf4f9067c2283a34619fc0714e79a98d
> Author: Matthew Garrett
> Date: Tue Sep 4 08:28:06 2012 +00
On Tue, Jan 15, 2013 at 09:55:41AM -, Stefan Bader wrote:
> Actually the whole WRMSR trail is a red herring. The c0010020
> ones are from trying a microcode update. The c0010004 one is
> checking for performance counters and 0413, c408
> and c
To get a better idea of what is wrong can you run a test for me please?
That is to boot the kernel+Xen without the 'dom0_mem' flag so that it
crashes. But lets make sure that on the Linux command line you have:
"console=hvc0 earlyprintk=xen debug loglevel=8" and for extra measure on
the Xen command
Stefan, so your gut feeling about the 228000 was right.
he E820_UNUSABLE regions are memory that "can" be used (and if you look
in 'xen_memory_setup' that is how we set aside the memory for the
balloon region - look for the 'type = E820_UNUSABLE). So by that logic,
E820_UNUSABLE region should get
What is your dom0?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/824089
Title:
Xen blkfront i/o errors prevent boot in domU
To manage notifications about this bug go to:
https://bugs.launchpad.net/
Your card is AGP right? This patchset:
https://lkml.org/lkml/2010/12/6/464 fixes it but I haven't gone back to
that patch set since I figured nobody uses AGP anymore :-(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
On Wed, Mar 20, 2013 at 03:51:41PM -, Stefan Bader wrote:
> A bit more detail gather with dynamic debugging from smpboot.c:
.. snip..
> [0.115947] NMI watchdog: enabled on all CPUs, permanently consumes one
> hw-PMU counter.
> [0.116065] register_vcpu_info failed: err=-22
That fails.
On Mon, Nov 12, 2012 at 08:47:11PM -, Steven Noonan wrote:
> Stefan,
>
> I did our internal SSD and network performance testing qualifications on
> hi1.4xlarge with CONFIG_PARAVIRT_SPINLOCKS=n in the kernel build.
> There's very little discernible difference in performance (within
> statistica
Hm
I don't know what Ubuntu's 3.7 contains, but if I run the v3.6 vanilla on an
Intel SWQ6710H.86A.0052.2011.0520.1802
(i5-2100) I get:
> xenpm get-cpufreq-para
cpu id : 0
affected_cpus: 0
cpuinfo frequency: max [3301000] min [160] cur [330]
scaling_driver
19:40:45 # 10 :~/
> xl info
host : tst018.dumpdata.com
release: 3.7.0-rc5upstream
version: #1 SMP Fri Nov 16 14:15:58 EST 2012
machine: x86_64
nr_cpus: 4
max_cpu_id : 3
nr_nodes : 1
cores_pe
On Mon, Nov 19, 2012 at 10:36:45AM -, Stefan Bader wrote:
> May or may not related Xen messages:
>
> (XEN) traps.c:2584:d0 Domain attempted WRMSR c408 from
> 0xc4000100 to 0xc00804000100.
> (XEN) traps.c:2584:d0 Domain attempted WRMSR c409 from
> 0xc10
Stefan,
Is your patch somewhere accessible? Thx
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1011792
Title:
Kernel lockup running 3.0.0 and 3.2.0 on multiple EC2 instance types
To manage notificat
16 matches
Mail list logo
