Q: how to increase ACPI_MAX_TASKS

2013-09-09 Thread moto kawasaki

Hello,

Could you please advice me how to increase ACPI_MAX_TASKS from 32
(default) to 64 or 128 ?


(1) I am running FreeBSD 9.1-RELEASE-p6, which was updated via freebsd-update.

# uname -srmv
FreeBSD 9.1-RELEASE-p6 FreeBSD 9.1-RELEASE-p6 #0: Wed Aug 21 20:40:52 UTC 2013  
   r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64

(2) Now, dmesg shows an error regarding AE_NO_MEMORY.

# dmesg
(snip)
AcpiOsExecute: failed to enqueue task, consider increasing the 
debug.acpi.max_tasks tunable
ACPI Error: Method parse/execution failed [\\_SB_.PCI0.HEC2.HSCI] (Node 
0xfe001d208380), AE_NO_MEMORY (20110527/psparse-560)
ACPI Error: Method parse/execution failed [\\_GPE._L06] (Node 
0xfe001d20c6c0), AE_NO_MEMORY (20110527/psparse-560)
ACPI Exception: AE_NO_MEMORY, while evaluating GPE method [_L06] 
(20110527/evgpe-606)
AcpiOsExecute: failed to enqueue task, consider increasing the 
debug.acpi.max_tasks tunable
(snip)

If needed, I will show all dmesg output. please request.

(3) This is because ACPI_MAX_TASKS is defined as 32 in 
/usr/src/sys/dev/acpica/acpivar.h

=
/* Default maximum number of tasks to enqueue. */
#ifndef ACPI_MAX_TASKS
#define ACPI_MAX_TASKS  32
#endif
=

(4) When I rewrite it to 64, the error in dmesg disappeared.
So far so good, but I have to re-compile the kernel in this case.

If possible, I'd like to change ACPI_MAX_TASKS value by
sysctl.conf or something like that.

(5) /usr/src/sys/dev/acpica/Osd/OsdSchedule.c mentions debug.acpi.max_tasks.

=
/*
 * Allow the user to tune the maximum number of tasks we may enqueue.
 */
static int acpi_max_tasks = ACPI_MAX_TASKS;
TUNABLE_INT(debug.acpi.max_tasks, acpi_max_tasks);
=

But, I cannot write this sysctl tunable. That is unknown oid.

# sysctldebug.acpi.max_tasks
sysctl: unknown oid 'debug.acpi.max_tasks'

# sysctl -w debug.acpi.max_tasks=64
sysctl: unknown oid 'debug.acpi.max_tasks'

(6) If I have to re-compile the GENERIC kernel, where should I define
ACPI_MAX_TASKS ? /etc/make.conf? kernel configuration file? or
acpivar.h ?




Thank you very much!!



Best Regards



-- 
moto kawasaki m...@kawasaki3.org 090-2464-8454
___
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


Current problem reports assigned to freebsd-acpi@FreeBSD.org

2013-09-09 Thread FreeBSD bugmaster
Note: to view an individual PR, use:
  http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.


S Tracker  Resp.  Description

o kern/181665  acpi   [acpi] System will not go into S3 state.
o kern/180897  acpi   [acpi] ACPI error with MB p8h67 v.1405
o kern/174766  acpi   [acpi] Random acpi panic
o kern/174504  acpi   [ACPI] Suspend/resume broken on Lenovo x220
o kern/173408  acpi   [acpi] [regression] ACPI Regression: battery does not 
o kern/171305  acpi   [acpi] acpi_tz0: _CRT value is absurd, ignored (256.0C
o kern/165381  acpi   [cpufreq] powerd(8) eats CPUs for breakfast
o kern/164329  acpi   [acpi] hw.acpi.thermal.tz0.temperature shows strange v
o kern/162859  acpi   [acpi] ACPI battery/acline monitoring partialy working
o kern/161715  acpi   [acpi] Dell E6520 doesn't resume after ACPI suspend
o kern/161713  acpi   [acpi] Suspend on Dell E6520
o kern/160838  acpi   [acpi] ACPI Battery Monitor Non-Functional
o kern/160419  acpi   [acpi_thermal] acpi_thermal kernel thread high CPU usa
o kern/158689  acpi   [acpi] value of sysctl hw.acpi.thermal.polling_rate ne
o kern/154955  acpi   [acpi] Keyboard or ACPI doesn't work on Lenovo S10-3
o kern/152098  acpi   [acpi] Lenovo T61p does not resume
o i386/146715  acpi   [acpi] Suspend works, resume not on a HP Probook 4510s
o kern/145306  acpi   [acpi]: Can't change brightness on HP ProBook 4510s
o i386/143798  acpi   [acpi] shutdown problem with SiS K7S5A
o kern/143420  acpi   [acpi] ACPI issues with Toshiba
o kern/142009  acpi   [acpi] [panic] Panic in AcpiNsGetAttachedObject
o kern/139088  acpi   [acpi] ACPI Exception: AE_AML_INFINITE_LOOP error
o amd64/138210 acpi   [acpi] acer aspire 5536 ACPI problems (S3, brightness,
o i386/136008  acpi   [acpi] Dell Vostro 1310 will not shutdown (Requires us
o kern/132602  acpi   [acpi] ACPI Problem with Intel SS4200: System does not
a i386/122887  acpi   [panic] [atkbdc]  7.0-RELEASE on IBM HS20 panics immed
s kern/112544  acpi   [acpi] [patch] Add High Precision Event Timer Driver f
o kern/73823   acpi   [request] acpi / power-on by timer support

28 problems total.

___
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


Re: panic after acpi suspend/resume 9.1, 9.2rc3

2013-09-09 Thread John Baldwin
On Sunday, September 08, 2013 5:24:54 pm J.R. Oldroyd wrote:
 This problem may have existed for some time in the 9.x kernel.
 I've had similar panics for a while, but not had time to look into
 it.  I did not have this problem on 8.x kernels on this laptop.
 
 It never happens when the system is cold-booted.  It only happens
 after a suspend/resume cycle or two which is why I am posting to
 freebsd-apci to start with...
 
 
 The repeat-by goes something like this:
 - boot system
 - suspend system
 - resume system
 - use as normal (mix of email/firefox/sh  nvi/openvpn)
 - perhaps suspend/resume again
 - keep using as normal
 - system panics, seems often to be when using firefox
 
 
 Fatal trap 12: page fault while in kernel mode
 cpuid = 0; apic id = 00
 fault virtual address   = 0x0
 fault code  = supervisor write data, page not present
 instruction pointer = 0x20:0x80ceddcd
 stack pointer   = 0x28:0xff80dbfe25e0
 frame pointer   = 0x28:0xff80dbfe2660
 code segment= base 0x0, limit 0xf, type 0x1b
 = DPL 0, pres 1, long 1, def32 0, gran 1
 processor eflags= interrupt enabled, resume, IOPL = 0
 current process = 52022 (firefox)
 trap number = 12
 panic: page fault
 cpuid = 0
 KDB: stack backtrace:
 #0 0x80947986 at kdb_backtrace+0x66
 #1 0x8090d9ae at panic+0x1ce
 #2 0x80cf1db0 at trap_fatal+0x290
 #3 0x80cf2111 at trap_pfault+0x211
 #4 0x80cf26c4 at trap+0x344
 #5 0x80cdb9f3 at calltrap+0x8
 #6 0x80b797a7 at vm_fault_hold+0x1b87

This is where the NULL pointer is.  Frame 9 (listed below) is above this.

 (kgdb) list *0x80ceddcd
 0x80ceddcd is in pmap_enter (../../../amd64/amd64/pmap.c:3577).
 3572if ((m-oflags  VPO_UNMANAGED) == 0) {
 3573newpte |= PG_MANAGED;
 3574pv = get_pv_entry(pmap, lock);
 3575pv-pv_va = va;
 3576CHANGE_PV_LIST_LOCK_TO_PHYS(lock, pa);
 3577TAILQ_INSERT_TAIL(m-md.pv_list, pv, pv_list);
 3578if ((newpte  PG_RW) != 0)
 3579vm_page_aflag_set(m, PGA_WRITEABLE);
 3580}
 3581

So it seems like pv_list of a page might be busted?  Can you try looking at
the disassembly to see if you can find 'm' in one of the registers?

-- 
John Baldwin
___
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