On 17.12.2014. 6:34, Philip Guenther wrote:
Uh, ACPI *requires* that C1 exist. The halt instruction is defined as
entering C1, so not having C1 would mean your CPU lacks a basic
manadatory ia32 instruction. Hopefully the BIOS docs explain that
you're just disabling "deep" C-states or something
> Date: Fri, 19 Dec 2014 23:41:56 +1000
> From: Jonathan Matthew
>
> On Thu, Dec 18, 2014 at 11:14:54PM +0100, Frederic Nowak wrote:
> > Hi!
> >
> > The diff for extracting memory ranges from ACPI was obviously not tested
> > with ACPI disabled...so we definitely have to check if the values in
>
On Thu, Dec 18, 2014 at 11:14:54PM +0100, Frederic Nowak wrote:
> Hi!
>
> The diff for extracting memory ranges from ACPI was obviously not tested
> with ACPI disabled...so we definitely have to check if the values in
> pcimem_range make some sense. The diff below now uses the old values in
> case
Hi!
The diff for extracting memory ranges from ACPI was obviously not tested
with ACPI disabled...so we definitely have to check if the values in
pcimem_range make some sense. The diff below now uses the old values in
case ACPI is disabled or does not return valid values.
I hope this is somewhat
> Date: Tue, 16 Dec 2014 21:34:29 -0800
> From: Philip Guenther
>
> > R620 have similar settings and can't see C states in dmesg
> > acpicpu0 at acpi0
>
> That's either insane, or a bug in our acpicpu code, IMO.
Probably just the effect of the BIOS not advertising C states at all.
Like you said
> On 16 dec 2014, at 06:40, David Gwynne wrote:
>
> others have hit this on r620s as well
I donât see it on mine.
interrupt total rate
irq0/clock 9587998940 1599
irq0/ipi136166514 22
irq144/acpi02
Hi!
The below diff extracts the memory range information from ACPI. It looks
up all the memory ranges in _CRS and calculates minimal and maximal
values for pci_machdep.c.
I tested this on two amd64 machines and see no difference in pcidump.
Do you think we need to keep the old method in case the
On Tue, Dec 16, 2014 at 2:45 PM, Hrvoje Popovski wrote:
> on R630 i have custom bios settings and noticed that even if C states are
> disabled in bios i can see them in dmesg
> acpicpu0 at acpi0: C1
Uh, ACPI *requires* that C1 exist. The halt instruction is defined as
entering C1, so not having
On 16.12.2014. 6:16, Jonathan Matthew wrote:
We just got some r630s too, so I spent some time last week figuring out what's
going on here. Something in the AML wants to talk to the intel MEI device.
Normally this works, but on the new generation of dell machines (we've seen it
on r630s and r730s
> Date: Tue, 16 Dec 2014 15:16:58 +1000
> From: Jonathan Matthew
>
> On Sun, Dec 14, 2014 at 06:22:37PM +0100, Hrvoje Popovski wrote:
> > Hi all,
> >
> > I have got two new Dell R630 and have current on them from Sun Dec
> > 14 15:07:17. Installation went great and very fast.
> > The problem is
On 16.12.2014. 6:16, Jonathan Matthew wrote:
On Sun, Dec 14, 2014 at 06:22:37PM +0100, Hrvoje Popovski wrote:
Hi all,
I have got two new Dell R630 and have current on them from Sun Dec
14 15:07:17. Installation went great and very fast.
The problem is that I see around 11k interrupts on acpi0.
On Sun, Dec 14, 2014 at 06:22:37PM +0100, Hrvoje Popovski wrote:
> Hi all,
>
> I have got two new Dell R630 and have current on them from Sun Dec
> 14 15:07:17. Installation went great and very fast.
> The problem is that I see around 11k interrupts on acpi0. First I
> thought that problem is simi
> On 16 Dec 2014, at 15:16, Jonathan Matthew wrote:
>
> On Sun, Dec 14, 2014 at 06:22:37PM +0100, Hrvoje Popovski wrote:
>> Hi all,
>>
>> I have got two new Dell R630 and have current on them from Sun Dec
>> 14 15:07:17. Installation went great and very fast.
>> The problem is that I see around
13 matches
Mail list logo
