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

2013-07-08 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/174766  acpi   [acpi] Random acpi panic
o kern/174504  acpi   [ACPI] Suspend/resume broken on Lenovo x220
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

25 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: USB ports on Lenovo T400 do not work after a suspend/resume

2013-07-08 Thread Adrian Chadd
On 7 July 2013 22:00, Ian Smith smi...@nimnet.asn.au wrote:

 Checking one more point .. do the USB ports come up ok if you originally
 boot with nothing plugged in?  If so (or if not), does that local APIC

Yes.

 error message appear the same then too?



No


-adrian
___
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: USB ports on Lenovo T400 do not work after a suspend/resume

2013-07-08 Thread John Baldwin
On Sunday, June 30, 2013 10:22:09 am Ian Smith wrote:
 On Sat, 29 Jun 2013, Adrian Chadd wrote:
   On 27 June 2013 04:58, Ian Smith smi...@nimnet.asn.au wrote:
We don't yet know if this is a bus, ACPI /or USB issue.  Home yet? :)
   
   Yup:
   
   http://people.freebsd.org/~adrian/usb/
   
   dmesg.boot = dmesg at startup
   
   1 - after powerup, usb device in
   2 - after acpiconf -s3 suspend/resume, w/ a USB device plugged in
   3 - after acpiconf -s3 suspend/resume, with a USB device removed
   before suspend/resume
 
 After removing [numbers] (for WITNESS?), diff started making sense.  
 The below is between the first and second suspend/resume cycles in 
 dmesg-3.txt, encompassing the others.
 
 Nothing of note that I can see, if that usb hub-to-bus remapping is 
 normal.  As you said, 'CPU0: local APIC error 0x40' looks maybe sus.  
 Maybe someone who knows might comment on that?

From sys/amd64/include/apicreg.h:

/* fields in ESR */
#define APIC_ESR_SEND_CS_ERROR  0x0001
#define APIC_ESR_RECEIVE_CS_ERROR   0x0002
#define APIC_ESR_SEND_ACCEPT0x0004
#define APIC_ESR_RECEIVE_ACCEPT 0x0008
#define APIC_ESR_SEND_ILLEGAL_VECTOR0x0020
#define APIC_ESR_RECEIVE_ILLEGAL_VECTOR 0x0040
#define APIC_ESR_ILLEGAL_REGISTER   0x0080

Receive illegal vector (if look in Intel's SDM manuals) means it
got an interrupt vector  32 (probably zero).  Perhaps it asserted
an interrupt in an I/O APIC before the I/O APIC was properly reset?
Are you using MSI at all?

-- 
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