that updates amdgpu_atif_handler() is already in
Linux.
But the LKPI ACPI glue seems to need a bit more polish (or a proper design).
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsub
(like radeon or amdgpu) is
supposed to listen to and then the driver should update the brightness.
(This can also be thought of as the brightness being controlled by the video
"card" / GPU rather than by a motherboard).
For my laptop I had to patch amdgpu driver:
https://github.com/Free
b.freebsd.org/base?view=revision=360657
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207086
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to "freebsd-acpi-unsubscr...@freebsd.org"
sleep_result, 1);
+ AcpiLeaveSleepStatePrep(state);
+
if (sleep_result == -1)
goto backout;
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any
before the spam covers the first 4 lines and makes it
> impossible to read or edit.
Are you saying that the messages go to all terminals / consoles?
Or are you stuck at a single console (like ttyv0) for some reason (e.g. single
user mode)?
--
Andriy Gapon
_
Perhaps you would be interested in this message on hackers@.
Forwarded Message
Subject: ACPICA missing support for device I/O port ranges
Date: Sat, 18 Nov 2017 18:52:54 +0100
From: Harald Böhm
To: 'freebsd-hack...@freebsd.org'
patch.
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to "freebsd-acpi-unsubscr...@freebsd.org"
between FreeBSD and Linux.
Or that HAL is no longer used at all in most Linux-based OSes...
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd-acpi-unsubscr
not jump to conclusions.
BTW, I am following up on the problem in the PR.
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org
on 02/09/2013 00:58 Adrian Chadd said the following:
On 1 September 2013 14:35, Andriy Gapon a...@freebsd.org
mailto:a...@freebsd.org wrote:
Do you have any evidence that there is anybody else besides Mike who has
this
problem?
Nope! but we can't assume that users
to be NULL for
one pair of the two HT CPUs?
Are you taking the whole core into an ACPI idle state if one of two logical
CPUs
representing a core is going idle?
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org
to
investigate / analyze that first.
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org
. */
error = ENXIO;
unit = 0;
@@ -417,6 +419,7 @@
error = EINVAL;
}
+mtx_unlock(Giant);
return (error);
}
The patch works for me without any problem. I guess it won't hurt
your system ;-) but I actually don't know if/how it relates to your
PR.
--
Andriy
the typical use too.
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org
() passed some extra stuff back to the nexus methods
which then added the IRQs. This approach is a bit cleaner. - Change the MSI sx
lock to a mutex. If we need to create new sources, drop the lock, create the
required number of sources, then get the lock and try the allocation again.
--
Andriy Gapon
in AcpiLeaveSleepStatePrep does not need to be with interrupts
disabled and can be moved to AcpiLeaveSleepState. This is after the _BFS and
_GTS support was removed.
What do you think?
Thank you.
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
http
on 16/03/2013 11:06 Andriy Gapon said the following:
on 16/03/2013 10:10 Sean Bruno said the following:
debug.acpi.level=ACPI_LV_VERBOSE
BTW, please also note what acpi(4) says about this level as opposed to e.g.
ACPI_LV_VERBOSITY3.
--
Andriy Gapon
either on ACPICA object cache or ACPICA
reference counting. But now I am inclined to think that it is caused by
something
in FreeBSD adaptation layer.
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
with the problem
I can provide more info (sorry, no crashdump, was not enabled),
do tests, etc.
Please at least enable printing of a stack trace.
Better do get the crash dump.
P.S. I suspect that the issue we are discussing with hps in this mailing list
could be related to this problem.
--
Andriy Gapon
, then it is not accessed as the
real object (via ACPI_OBJECT_COMMON_HEADER fields), it is accessed only as a
cached entity via the LinkOffset hackery.
So, I do not see any bug in the current code.
Your change makes it look a little bit less ugly, though. But I do not see any
functional change.
--
Andriy Gapon
on 24/01/2013 22:33 Jung-uk Kim said the following:
On 2013-01-24 13:49:07 -0500, Andriy Gapon wrote:
on 24/01/2013 20:29 Jung-uk Kim said the following:
BTW, I tried something like that long ago. In fact, the first
attempt goes all the way back to this patch (warning: it's naive,
broken
on 24/01/2013 22:33 Jung-uk Kim said the following:
On 2013-01-24 13:49:07 -0500, Andriy Gapon wrote:
on 24/01/2013 20:29 Jung-uk Kim said the following:
When utcache.c works, it works fairly well, actually. :-)
Well, my primary motivation for the patch is all the reports about
mysterious
If you have ACPI suspend/resume working, if it used to work but stopped working
at some time, if it never worked, but you are still hoping, could you please
test the following patch and report back?
http://svn.freebsd.by/files/acpi-apic-wakeup-final.patch
--
Andriy Gapon
)
This happens on 9.1-RELEASE amd64
Could you please try a patch from a parallel thread:
http://thread.gmane.org/gmane.os.freebsd.devel.acpi/7562/focus=7611
?
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman
it
using FreeBSD built-in debugging capabilities like INVARIANTS, WITNESS,
DEBUG_MEMGUARD, etc.
commit 12a6b3610b82e5370bf32f3c3ea5ac1fae46bb63
Author: Andriy Gapon a...@icyb.net.ua
Date: Sun Dec 23 19:52:26 2012 +0200
[test] acpi: use uma instead of acpica internal object cache implementation
on 15/12/2012 17:19 Alexey Dokuchaev said the following:
On Fri, Dec 14, 2012 at 09:25:51PM +0700, Alexey Dokuchaev wrote:
On Fri, Dec 14, 2012 at 02:45:32PM +0200, Andriy Gapon wrote:
How did you obtain these files?
acpixtract doesn't seem to recognize all.bin...
Could you please do
,
do you think you can ship those .symbols as well? :-)
./danfe
[1] http://193.124.210.26/10.0-acpi.dmesg
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any
on 14/12/2012 12:44 Alexey Dokuchaev said the following:
On Fri, Dec 14, 2012 at 11:48:10AM +0200, Andriy Gapon wrote:
Could you please obtain acpidump output using Ubuntu?
Yup, I already did [1]. Here is the what's inside:
all.bin dump of all tables
dsdt.bindump of DSDT
is added to the cache list and before the mutex is released.
And also, just in case, another copy to AcpiOsAcquireObject.
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe
on 01/12/2012 11:15 Jean-Sébastien Pédron said the following:
On 01.12.2012 10:10, Andriy Gapon wrote:
on 01/12/2012 11:02 Jean-Sébastien Pédron said the following:
By the way, should _CST appear in a dump from acpidump(8)?
Yes, it depends... :-) _CST could be defined in a dynamically
on 29/11/2012 17:29 Andriy Gapon said the following:
I am working on an alternative approach to these two issues.
Here is my WIP:
http://people.freebsd.org/~avg/acpi_cpu_notify.2.diff
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
http
Turned out not be so rosy...
on 25/11/2012 21:37 Sean Bruno said the following:
On Thu, 2012-11-22 at 16:53 +0200, Andriy Gapon wrote:
I would like to propose the following patch which should kill two birds with
one
stone:
- avoid race in acpi_cpu_cx_cst if more than one notifications
on 29/11/2012 10:46 Stefan Farfeleder said the following:
On Mon, Nov 26, 2012 at 01:13:46PM +0200, Andriy Gapon wrote:
Also, I've just realized that the check is racy...
Could you please move the whole check block (between and excluding
AcpiUtAcquireMutex and AcpiUtReleaseMutex) down right
on 26/11/2012 11:37 Stefan Farfeleder said the following:
On Mon, Nov 26, 2012 at 11:29:55AM +0200, Andriy Gapon wrote:
Very interesting, thank you.
Are you able to get a crash dump?
Yes.
Great!
Could you please cast those cycled objects to 'union acpi_operand_object' and
print them
))
{
return (Status);
}
Thank you.
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org
on 26/11/2012 13:10 Stefan Farfeleder said the following:
On Mon, Nov 26, 2012 at 01:06:18PM +0200, Andriy Gapon wrote:
on 26/11/2012 12:47 Stefan Farfeleder said the following:
BTW, I noticed the ACPI_SET_DESCRIPTOR_TYPE code is pointless, because the
DescriptorType is at offset 8 from
@@ AcpiOsReleaseObject (
if (Object == Curr) {
panic(freeing a free object %p, Object);
}
+Depth--;
+if (Depth 0) {
+panic(cycle in a cache list);
+}
}
(void) AcpiUtReleaseMutex (ACPI_MTX_CACHES);
--
Andriy Gapon
is full, just free this object */
if (Cache-CurrentDepth = Cache-MaxDepth)
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd-acpi-unsubscr
on 22/11/2012 12:24 Andriy Gapon said the following:
on 22/11/2012 10:18 Stefan Farfeleder said the following:
I'm afraid the AcpiOsAcquireObject panic is not directly related to
reference counting. I had the very same panic today with your patch.
OK, let's try to attack it from a different
*) Object != 0xCA) {
+panic(detected use after free %p\n, Object);
+}
+
ACPI_MEM_TRACKING (Cache-Hits++);
ACPI_DEBUG_PRINT ((ACPI_DB_EXEC,
Object %p from %s cache\n, Object, Cache-ListName));
--
Andriy Gapon
);
+sched_unbind(curthread);
+thread_unlock(curthread);
+
acpi_cpu_cx_list(sc);
ACPI_SERIAL_BEGIN(cpu);
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail
in Xfast_syscall () at /tmp/exception-EAhiLL.s:292
#29 0x00080093456a in ?? ()
Previous frame inner to this frame (corrupt stack?)
Current language: auto; currently minimal
(kgdb)
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
on 13/11/2012 17:14 Andriy Gapon said the following:
I have a better patch, which I tested at least. I'll send it to you soon-ish.
Here is a tested version of the ref-count patch (still a little bit
experimental):
http://people.freebsd.org/~avg/acpi-ref-count-exp.diff
--
Andriy Gapon
7 /* AML debugger */
+#define ACPI_MTX_REFCOUNTS 8 /* ACPI object reference counts */
-#define ACPI_MAX_MUTEX 7
+#define ACPI_MAX_MUTEX 8
#define ACPI_NUM_MUTEX ACPI_MAX_MUTEX+1
--
Andriy Gapon
that you have ACPI_DEBUG option enabled?
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org
on 08/11/2012 11:06 Tom Lislegaard said the following:
-Original Message-
From: Andriy Gapon [mailto:a...@freebsd.org]
Sent: 6. november 2012 19:53
To: Tom Lislegaard
Cc: freebsd-sta...@freebsd.org; freebsd-acpi@FreeBSD.org
Subject: Re: 9-Stable panic: resource_list_unreserve
) ?
debug.acpi.acpi_ca_version: 20110527
Thanks!
Could you please also do:
x/9a Cache-ListHead
?
I suspect that this bug is of very inconvenient nature: a memory corruption,
either semi-random or some sort of use after free.
--
Andriy Gapon
___
freebsd-acpi
=ACPI_LV_INFO
Also, is your system DTrace-enabled?
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org
.
Thank you for all the excellent debugging and testing!
P.S. I still believe that BIOS/ACPI on the machine behaves sub-optimally.
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
on 05/11/2012 12:26 Tom Lislegaard said the following:
-Original Message-
From: Andriy Gapon [mailto:a...@freebsd.org]
I see. Could you please try setting debug.acpi.max_threads=1 in
/boot/loader.conf, reboot and see if
that makes any difference?
It does make a difference. I've
in
/boot/loader.conf, reboot and see if that makes any difference?
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org
on 01/11/2012 11:45 Tom Lislegaard said the following:
-Original Message-
From: Andriy Gapon [mailto:a...@freebsd.org]
Sent: 31. oktober 2012 19:51
To: Tom Lislegaard
Cc: 'freebsd-sta...@freebsd.org'
Subject: Re: 9-Stable panic: resource_list_unreserve: can't find resource
control over that.
P.S. I hope you haven't confused this notification for a notification about
_current_ C-state changing.
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe
on 03/10/2012 19:21 Sean Bruno said the following:
On Wed, 2012-10-03 at 06:08 -0700, Andriy Gapon wrote:
So quick question, does this happen a lot on a system with a
sporadic
workload? Does this introduce overhead to the system to service the
notification requests?
I am not sure who can
Please take a look at the following patch and a commit message that explains it.
I observed the problem on a system with acpi_wmi instances where one instance
overrode GUID list from the other.
commit f1f4109b1588872906ed56086e2680ac1af96268
Author: Andriy Gapon a...@icyb.net.ua
Date: Thu Sep
on 03/10/2012 20:40 Ian Smith said the following:
So are you talking about a devd notification to trigger activity like
the AC/battery script, or a sysctl that scripts could poll, or?
devd notification like for AC line status change.
--
Andriy Gapon
[ping]
on 11/09/2012 09:32 Andriy Gapon said the following:
I think that we always expect to have a one-to-one correspondence between
acpi_cpu devices and actual (APIC) CPUs. acpi_pcpu_get_id() seems to even
assert that, if I am reading the code correctly.
The following patch adds
on 05/09/2012 19:23 Kevin Oberman said the following:
On Wed, Sep 5, 2012 at 9:12 AM, Andriy Gapon a...@freebsd.org wrote:
on 05/09/2012 18:17 Kevin Oberman said the following:
Thanks so much! This should finally make Cx states work on my
ThinkPad! I really appreciate it. Guess it's time to do
on 05/09/2012 20:41 Kevin Oberman said the following:
On Wed, Sep 5, 2012 at 9:32 AM, Andriy Gapon a...@freebsd.org wrote:
on 05/09/2012 19:23 Kevin Oberman said the following:
On Wed, Sep 5, 2012 at 9:12 AM, Andriy Gapon a...@freebsd.org wrote:
on 05/09/2012 18:17 Kevin Oberman said
not to commit it then.
Jung-uk?
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org
to be advertised via ACPI [modulo non-MADT, mptable-only
systems]) do not have corresponding Processor objects in DSDT?
Does acpi_pcpu_get_id provide such support?
Or can the code in question be just replaced with KASSERT?
Thank you in advance.
--
Andriy Gapon
on 10/07/2012 18:49 Sean Bruno said the following:
On Sun, 2012-07-08 at 03:22 -0700, Andriy Gapon wrote:
I would like to propose the following change for review and testing:
http://people.freebsd.org/~avg/acpi_cpu_cx_lowest.diff
Very nice. After a review I went ahead and applied
on 08/07/2012 19:49 Nate Lawson said the following:
On Jul 8, 2012, at 2:11 AM, Andriy Gapon wrote:
acpi_cpu.c has a block of code to write CST_CNT to SMI_CMD, but the block is
under #ifdef notyet. It seems that the code was added that many years ago
and
never enabled.
Now, judging from
in FADT please test
this?
Thank you.
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org
on 04/07/2012 18:04 Andriy Gapon said the following:
Our current approach of using C-state indexes as C-state identifiers/names
may be
not so bad after all if we remove confusion by properly documenting the
meaning
(index vs type).
Here is a link to a past discussion on this topic:
http
-state
(power, latency, ACPI (or HW-specific[*]) type, I/O-vs-MWAIT-vs-etc type of
entrance, etc).
[*] E.g. for intel_idle it could be C-state numbers from Intel specs.
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org
that early because they
need more of the system to be initialized (e.g. PCI bus). Hence the SYSINIT
hack to attach them later.
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe
on 20/06/2012 23:54 Sean Bruno said the following:
On Wed, 2012-06-20 at 13:18 -0700, Andriy Gapon wrote:
I also, disagree with the idea of FreeBSD C-states as that is not
the
intention of the code. The code, from my read, is trying to
interpret
C-states as though they are always defined
, is trying to interpret
C-states as though they are always defined sequentially and non-sparse.
I seem to recall that this is an ACPI requirement. I could be mistaken, but no
time to double-check at the moment.
I am still of the opinion that my patch is correct at this point.
--
Andriy Gapon
about a laptop here? Namely, judging from the reference to
'economy_lowest', are AC state changes in play?
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail
on 20/06/2012 00:42 Sean Bruno said the following:
On Tue, 2012-06-19 at 14:07 -0700, Andriy Gapon wrote:
on 19/06/2012 19:02 Sean Bruno said the following:
The first impact of this behavior is to list C3 as C2 in the list of
Cstates when you retrieve the cx_supported sysctls for the cpus.
I
be in
different P-states and provide support for that throughout the stack (from
powerd to drivers).
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail
on 07/06/2012 11:38 Alexander Motin said the following:
On 06/07/12 11:10, Andriy Gapon wrote:
on 07/06/2012 02:02 Jung-uk Kim said the following:
Any way, hwpstate still isn't quite right even without your patch.
sys/kern/kern_cpu.c cpufreq_curr_sysctl() - CPUFREQ_SET() -/* for all
CPU
make sense to provide a void pointer as a potential context for
for the context. As Attilio has said before this has many similarities to what
smp_rendezvous does, just for different kind of situations.
From: Andriy Gapon a...@freebsd.org
Subject: Re: cpu stopping
Date: Sun, 03 Jun 2012 22:45
what PCPU_GET(cpuid) a given cpuX device corresponds to). I
think
the last approach is really the right way to fix this.
I haven't been able to try this yet, but I have a first cut at
www.freebsd.org/~jhb/patches/acpi_cpu.patch
The patch has not been compile-tested? :)
--
Andriy Gapon
on 14/05/2012 01:43 Bruce Cran said the following:
On 13/05/2012 21:06, Andriy Gapon wrote:
Can you produce an equivalent snippet with verbose logging enabled? I have a
suspicion that these messages are a byproduct from r231161.
acpi0: reservation of fee0, 1000 (3) failed
acpi0
:
(unknown))
Can you produce an equivalent snippet with verbose logging enabled?
I have a suspicion that these messages are a byproduct from r231161.
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
to investigate further?
The chipset is not really supported by the driver. It shouldn't even try to
attach.
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail
The following reply was made to PR bin/126162; it has been noted by GNATS.
From: Andriy Gapon a...@freebsd.org
To: bug-follo...@freebsd.org, ad...@mail.ru
Cc:
Subject: Re: bin/126162: [acpi] ACPI autoload failed : loading required module
quot;pciquot; - no such file or directories
Date: Sun
on 26/01/2012 16:20 Glen Barber said the following:
On Thu, Jan 26, 2012 at 02:47:10PM +0200, Andriy Gapon wrote:
Prior to Monday's email, I was out of town and mostly away from the
laptop. I can't definitively say, but it's likely I didn't have the
laptop running long enough to experience
on 26/01/2012 16:49 Glen Barber said the following:
On Thu, Jan 26, 2012 at 04:45:26PM +0200, Andriy Gapon wrote:
Given that there hasn't been any changes to sys/dev/acpica (i.e. FreeBSD ACPI
code) at all since 2011-12-29, I am inclined to assume that the problem is
caused
by the ACPICA
or the hardware?
Also, what's debug.acpi.acpi_ca_version on this system?
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org
on 14/07/2011 18:22 Kevin Oberman said the following:
#define _COMPONENT ACPI_OEM
ACPI_MODULE_NAME(IBM)
I'm guessing that the OEMID and the ACPI_MODULE_NAME need to match.
No.
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
http
on 11/07/2011 19:07 Vitaly Magerya said the following:
Andriy Gapon a...@freebsd.org wrote:
on 06/07/2011 22:20 Vitaly Magerya said the following:
--- acpi_cpu.c.orig 2011-07-05 19:50:31.0 +
+++ acpi_cpu.c 2011-07-06 17:23:16.0 +
@@ -1194,7 +1194,7
on 11/07/2011 19:08 Vitaly Magerya said the following:
Andriy Gapon a...@freebsd.org wrote:
From what I heard this isn't a problem with FreeBSD ACPI code, it's
a problem with Samsung firmware. AFAIK to get brightness controls
working on Windows you need to setup Samsung software that uses
.
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org
on 06/07/2011 00:49 Vitaly Magerya said the following:
Andriy Gapon a...@freebsd.org wrote:
Possible courses of action:
1. Do nothing and leave you with your workaround.
2. Provide intel_idle-like driver for FreeBSD. I don't like this approach
for
reasons I've stated before.
3. Try
on 02/07/2011 23:30 Vitaly Magerya said the following:
Andriy Gapon a...@freebsd.org wrote:
VDRV: 00 - 01
Looks like this variable should tell if OS has ACPI Video driver, to be
precise
if _BCL method was invoked at least once.
Looks like in your case the driver doesn't attach for some
: Enhanced SpeedStep Frequency Control on cpu1
So this was improved. Thanks!
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd-acpi-unsubscr
on 01/07/2011 14:54 Andriy Gapon said the following:
Actually, it seems that they have them simply hardcoded:
http://lxr.linux.no/#linux+v2.6.39/drivers/idle/intel_idle.c#L171
Here is a presentation on intel_idle driver that describes reasons for its
existence and some additional information
on 01/07/2011 16:25 Andriy Gapon said the following:
on 01/07/2011 14:54 Andriy Gapon said the following:
Actually, it seems that they have them simply hardcoded:
http://lxr.linux.no/#linux+v2.6.39/drivers/idle/intel_idle.c#L171
Here
Yep, here :-)
http://events.linuxfoundation.org/slides
on 01/07/2011 07:16 Ed VanderPloeg said the following:
On 2011-06-30 1:59 PM, Andriy Gapon wrote:
on 30/06/2011 19:32 Ed VanderPloeg said the following:
I updated to 8-stable but am still getting ACPI error messages to console
every
10 seconds.
Just for my curiosity - has anything changed
errors, at best it could
improve something. At the very worst it may fry your machine, though...
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd
on 25/06/2011 18:47 Vitaly Magerya said the following:
Andriy Gapon a...@freebsd.org wrote:
on 24/06/2011 22:13 Vitaly Magerya said the following:
Right after I start the laptop I only see one supported power state:
# sysctl dev.cpu.0.cx_supported
dev.cpu.0.cx_supported: C1/1
.net/~magv/dmesg-n143-verbose.82.txt
[2] http://tx97.net/~magv/n143.asl
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org
ports.
Something like this?
http://www.serialice.com/News/News.html
Now that Intel/AMD support hardware virtualization and DMA isolation, it
would be better to do this with a modified Xen hypervisor.
--
Andriy Gapon
___
freebsd-acpi@freebsd.org
on 23/05/2011 11:12 Andriy Gapon said the following:
John,
it seems that possibly your recent changes for PCI bridges could have broken
something for my old 440BX/PIIX4/PIII type test machine.
Looks like now some I/O resources get assigned to a PCI bridge instead of
ACPI.
Some
in general it will
take some time.
Thanks,
Tom
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org
have some advices, they'll be welcome ! :)
Not sure if you picked the best mailing list.
--
Andriy Gapon
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd-acpi
The following reply was made to PR amd64/144551; it has been noted by GNATS.
From: Andriy Gapon a...@freebsd.org
To: bug-follo...@freebsd.org, dan.nau...@gmail.com
Cc:
Subject: Re: amd64/144551: [acpi] ACPI issues on SuperMicro X7SPA-H
Date: Sun, 05 Dec 2010 16:13:28 +0200
It's interesting
1 - 100 of 150 matches
Mail list logo