please test latest acpi patch
There are some very important -- and in some cases, potentially disruptive -- changes in the latest ACPI patch.
EC Burst Mode -- battery status AE_TIME etc.
Binding ACPI power states to PCI devices -- power loss in S3 Generic Hot Key Driver -- needs configuration from user space S3 Resume PCI Interrupt Link fix, requiring drivers to behave better Poweroff fix -- compatible with kexec patch
Improved "Implicit Return" AML workaround -- toshiba, compaq etc. Relaxed AE_AML_BUFFER_LIMIT code -- reflects proposed ACPI spec update
Please try it out on a system near you!
Thanks,
-Len
bk pull bk://linux-acpi.bkbits.net/to-akpm
or a plain patch is also available here:
http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/release/2.6.12/acpi-20050309-2.6.12-rc1.diff.gz
This will update the following files:
Documentation/acpi-hotkey.txt | 35 arch/i386/kernel/acpi/sleep.c | 3 arch/ia64/kernel/acpi.c | 2 drivers/acpi/Kconfig | 32 drivers/acpi/Makefile | 6 drivers/acpi/ac.c | 18 drivers/acpi/acpi_memhotplug.c | 542 ++++++++++++ drivers/acpi/asus_acpi.c | 4 drivers/acpi/battery.c | 2 drivers/acpi/bus.c | 8 drivers/acpi/button.c | 4 drivers/acpi/container.c | 15 drivers/acpi/debug.c | 4 drivers/acpi/dispatcher/dsmethod.c | 11 drivers/acpi/dispatcher/dsopcode.c | 8 drivers/acpi/dispatcher/dsutils.c | 166 +++ drivers/acpi/dispatcher/dswexec.c | 61 + drivers/acpi/ec.c | 392 ++++++--- drivers/acpi/events/evxface.c | 4 drivers/acpi/executer/exmisc.c | 5 drivers/acpi/executer/exoparg2.c | 6 drivers/acpi/executer/exresolv.c | 6 drivers/acpi/executer/exstoren.c | 7 drivers/acpi/executer/exstorob.c | 27 drivers/acpi/fan.c | 33 drivers/acpi/glue.c | 362 ++++++++ drivers/acpi/hotkey.c | 1018 ++++++++++++++++++++++++ drivers/acpi/ibm_acpi.c | 12 drivers/acpi/numa.c | 2 drivers/acpi/osl.c | 22 drivers/acpi/parser/psopcode.c | 2 drivers/acpi/parser/psparse.c | 42 drivers/acpi/parser/pswalk.c | 254 ----- drivers/acpi/pci_irq.c | 38 drivers/acpi/pci_link.c | 50 - drivers/acpi/pci_root.c | 4 drivers/acpi/power.c | 10 drivers/acpi/processor_core.c | 6 drivers/acpi/processor_thermal.c | 2 drivers/acpi/processor_throttling.c | 2 drivers/acpi/resources/rsaddr.c | 146 +-- drivers/acpi/resources/rscalc.c | 14 drivers/acpi/resources/rsdump.c | 23 drivers/acpi/resources/rslist.c | 1 drivers/acpi/scan.c | 47 - drivers/acpi/sleep/main.c | 74 - drivers/acpi/sleep/poweroff.c | 81 + drivers/acpi/thermal.c | 2 drivers/acpi/toshiba_acpi.c | 7 drivers/acpi/utilities/utcopy.c | 19 drivers/acpi/utilities/utdelete.c | 18 drivers/acpi/utilities/utglobal.c | 10 drivers/acpi/utilities/utmisc.c | 44 - drivers/acpi/video.c | 2 drivers/base/sys.c | 1 drivers/net/b44.c | 3 drivers/net/e1000/e1000_main.c | 3 drivers/net/ne2k-pci.c | 3 drivers/pci/pci-acpi.c | 121 ++ drivers/pci/pci.c | 18 drivers/pci/pci.h | 4 drivers/pcmcia/yenta_socket.c | 3 drivers/pnp/pnpacpi/rsparser.c | 9 drivers/usb/core/hcd-pci.c | 1 include/acpi/acconfig.h | 4 include/acpi/acdisasm.h | 5 include/acpi/acdispat.h | 10 include/acpi/acinterp.h | 1 include/acpi/aclocal.h | 4 include/acpi/acpi_bus.h | 22 include/acpi/acpi_drivers.h | 8 include/acpi/acstruct.h | 1 include/acpi/actbl.h | 4 include/acpi/actbl2.h | 79 + include/acpi/actypes.h | 33 include/acpi/platform/acenv.h | 2 include/acpi/processor.h | 2 include/linux/acpi.h | 2 include/linux/device.h | 6 include/linux/pm.h | 2 kernel/power/main.c | 16 81 files changed, 3354 insertions(+), 728 deletions(-)
through these ChangeSets:
<[email protected]> (05/03/19 1.2226)
[ACPI] Enable EC Burst Mode
Fixes several Embedded Controller issues, including button failure and battery status AE_TIME failure.
http://bugzilla.kernel.org/show_bug.cgi?id=3851
Based on patch by: Andi Kleen <[email protected]>
<[email protected]> (05/03/19 1.2225)
[ACPI] pci_set_power_state() now calls
platform_pci_set_power_state()
and ACPI can answer
http://bugzilla.kernel.org/show_bug.cgi?id=4277
<[email protected]> (05/03/19 1.2224)
[ACPI] PCI can now get suspend state from firmware
pci_choose_state() can now call
platform_pci_choose_state()
and ACPI can answer
http://bugzilla.kernel.org/show_bug.cgi?id=4277
<[email protected]> (05/03/18 1.2223)
[ACPI] Bind ACPI and PCI devices
http://bugzilla.kernel.org/show_bug.cgi?id=4277
<[email protected]> (05/03/18 1.2222)
[ACPI] Bind PCI devices with ACPI devices
Implement the framework for binding physical devices with ACPI devices. A physical bus like PCI bus should create a 'acpi_bus_type', with:
.find_device:
For device which has parent such as normal PCI devices.
.find_bridge:
It's for special devices, such as PCI root bridge
or IDE controller. Such devices generally haven't a parent or ->bus. We use the special method to get an ACPI handle.
Uses new field in struct device: firmware_data
http://bugzilla.kernel.org/show_bug.cgi?id=4277
<[email protected]> (05/03/18 1.2221)
[ACPI] generic Hot Key support
See Documentation/acpi-hotkey.txt
Use cmdline "acpi_specific_hotkey" to enable
legacy platform specific drivers.
http://bugzilla.kernel.org/show_bug.cgi?id=3887
<[email protected]> (05/03/18 1.2220)
[ACPI] S3 Suspend to RAM: fix driver suspend/resume methods
Drivers should do this:
.suspend()
pci_disable_device()
.resume()
pci_enable_device()
http://bugzilla.kernel.org/show_bug.cgi?id=3469
<[email protected]> (05/03/18 1.2219)
[ACPI] S3 Suspend to RAM: interrupt resume fix
Delete PCI Interrupt Link Device .resume method -- it is the device driver's job to request interrupts, not the Link's job to remember what the devices want.
This addresses the issue of attempting to run
the ACPI interpreter too early in resume, when
interrupts are still disabled.
http://bugzilla.kernel.org/show_bug.cgi?id=3469
<[email protected]> (05/03/18 1.2218)
[ACPI] Suspend to RAM fix
Free some RAM before entering S3 so that upon resume we can be sure early allocations will succeed.
http://bugzilla.kernel.org/show_bug.cgi?id=3469
<[email protected]> (05/03/18 1.2217)
[ACPI] ACPI poweroff fix
Register an "acpi" system device to be notified of shutdown
preparation.
This depends on CONFIG_PM
http://bugzilla.kernel.org/show_bug.cgi?id=4041
<[email protected]> (05/03/18 1.2216)
[ACPI] CONFIG_ACPI now depends on CONFIG_PM
<[email protected]> (05/03/17 1.2213)
[ACPI] build fix in acpi_pci_irq_disable()
bk-acpi-acpi_pci_irq_disable-build-fix.patch
<[email protected]> (05/03/09 1.1938.505.27)
[ACPI] ACPICA 20050309 from Bob Moore
The string-to-buffer implicit conversion code has been modified again after a change to the ACPI specification. In order to match the behavior of the other major ACPI implementation, the target buffer is no longer truncated if the source string is smaller than an existing target buffer. This change requires an update to the ACPI spec, and should eliminate the recent AE_AML_BUFFER_LIMIT issues.
The "implicit return" support was rewritten to a new algorithm that solves the general case. Rather than attempt to determine when a method is about to exit, the result of every ASL operator is saved momentarily until the very next ASL operator is executed. Therefore, no matter how the method exits, there will always be a saved implicit return value. This feature is only enabled with the acpi_gbl_enable_interpreter_slack flag which Linux enables unless "acpi=strict". This should eliminate AE_AML_NO_RETURN_VALUE errors.
Implemented implicit conversion support for the predicate (operand) of the If, Else, and While operators. String and Buffer arguments are automatically converted to Integers.
Changed the string-to-integer conversion behavior to match the new ACPI errata: "If no integer object exists, a new integer is created. The ASCII string is interpreted as a hexadecimal constant. Each string character is interpreted as a hexadecimal value ('0'-'9', 'A'-'F', 'a', 'f'), starting with the first character as the most significant digit, and ending with the first non-hexadecimal character or end-of-string." This means that the first non-hex character terminates the conversion and this is the code that was changed.
Fixed a problem where the ObjectType operator would fail (fault) when used on an Index of a Package which pointed to a null package element. The operator now properly returns zero (Uninitialized) in this case.
Fixed a problem where the While operator used excessive memory by not properly popping the result stack during execution. There was no memory leak after execution, however. (Code provided by Valery Podrezov.)
Fixed a problem where references to control methods within Package objects caused the method to be invoked, instead of producing a reference object pointing to the method.
Restructured and simplified the pswalk.c module (acpi_ps_delete_parse_tree) to improve performance and reduce code size. (Code provided by Alexey Starikovskiy.)
<[email protected]> (05/03/09 1.1994.11.5)
[ACPI] limit scope of various globals to static
<[email protected]> (05/03/09 1.1938.505.26)
[ACPI] fix acpi_numa_init() build warning
<[email protected]> (05/03/09 1.1938.505.25)
[ACPI] Allow 4 digits when printing PCI segments
to be consistent with the rest of the kernel.
<[email protected]> (05/03/08 1.1938.505.24)
[ACPI] Make PCI device -> interrupt link associations explicit,
ACPI: PCI Interrupt 0000:00:0f.2[A] -> Link [IUSB] -> GSI 10 (level,
low) -> IRQ 10
Previously, you could sometimes infer an association based on the
output
when an interrupt link is enabled, but when interrupt links are
shared
among several PCI devices, you could only make the inference for the
first
device to be enabled.
<[email protected]> (05/03/08 1.1938.505.23)
[ACPI] PNPACPI should ignore vendor-defined resources
<[email protected]> (05/03/03 1.1938.505.22)
[ACPI] fix [ACPI_MTX_Hardware] AE_TIME warning
which resulted from enabling the wake-on-RTC feature
http://bugme.osdl.org/show_bug.cgi?id=3967
<[email protected]> (05/03/03 1.1938.505.21)
[ACPI] ACPICA 20050303 from Bob Moore for AE_AML_BUFFER_LIMIT issue.
It turns out that tightening up the interpreter to truncate buffers per the ACPI spec was a bad idea -- BIOS' in the field depended on old behaviour. Instead, we'll endeavor to update the ACPI spec to reflect industry practice in this area.
http://bugme.osdl.org/show_bug.cgi?id=4263
<[email protected]> (05/03/02 1.1938.505.20)
[ACPI] fix sysfs "eject" file
This fixes a if-statement in setup_sys_fs_device_files(). It seems
to
assume that 'struct acpi_device_flags.ejectable' indicates whether a
device
has _EJ0 or not. But this is not a right assumption. It indicates
whether
a device has _EJ0|_EJD (See acpi_bus_get_flags() function).
setup_sys_fs_device_files() creates 'eject' file for devices that
have _EJ0
control method under a corresponding directory in /sys/firmware/acpi/namespace/ACPI/. 'eject' file is used to trigger hot-removal function from userland.
<Note that we expect this file location to change in the future.>
<[email protected]> (05/03/02 1.1938.505.19)
[ACPI] fix ACPI container driver's notify handler.
Previously, the handler tried to make a container device be offline
if an
ACPI_NOTIFY_BUS/DEVICE_CHECK notification is performed on the device
was
present and has its acpi_device. But, the condition is weird.
Whenever
the notification is performed, there should be only the following two conditions:
1. the device is present, but does not have its acpi_device.
2. the device is not present, but has its acpi_device.
#1 is a hot-addition case, which was handled properly also in
previous
handler. #2 is a surprising hot-removal case, which was not handled
in
previous handler.
<[email protected]> (05/03/02 1.1938.505.18)
[ACPI] fix kobject_hotplug() use by ACPI processor and container
drivers
A while ago, the drivers used their own function 'processor_run_sbin_hotplug() and container_run_sbin_hotplug()' to
notify
the agent script using /sbin/hotplug mechanism. But, they were
changed to
use kobject_hotplug() instead and this has caused a side effect.
The container driver was supposed to invoke a container.agent (user
mode
agent script) using /sbin/hotplug mechanism, but after the changes,
it is
not able to call the agent any more and kobject_hotplug() in the container.c became to invoke a namespace.agent instead if exists.
So, I
would like to use the namespace.agent to handle container hotplug
event (or
something else) and let the agent to call proper agent (e.g. container.agent). But, there is an issue we need to solve. When the namespace.agent is called, a path name of associated kobject is
passed as a
DEVPATH (e.g./sys/firmware/ acpi/namespace/ACPI/_SB/DEV0). However,
the
agent would not know what device is associated with the DEVPATH nor
which
agents to call since the DEVPATH name depends on platform. The
attached
patch is to add .hotplug_ops member to acpi_namespace_kset structure
and
let it to set a driver name attached to the target kobject into the
envp[]
variable as a DRV_NAME element. With this, the namespace.agent can
call
proper agents (e.g. container.agent) by refering the DRV_NAME.
<[email protected]> (05/03/02 1.1938.505.17)
[ACPI] flush TLB in init_low_mappings()
From: Li Shaohua <[email protected]>
<[email protected]> (05/03/02 1.1938.505.16)
[ACPI] enhance fan output in error path
Currently, fan.c ignores errors from acpi_bus_get_power. On compaq
evo
notebook that leads to very confusing empty output.
From: Pavel Machek <[email protected]>
<[email protected]> (05/03/02 1.1938.505.15)
[ACPI] CONFIG_ACPI_NUMA build fix
<[email protected]> (05/03/01 1.1938.505.14)
[ACPI] ACPICA 20050228 from Bob Moore
Fixed a problem where the result of an Index() operator (an object reference) must increment the reference count on the target object for the life of the object reference.
Implemented AML Interpreter and Debugger support for the new ACPI 3.0 Extended Address (IO, Memory, Space), QwordSpace, DwordSpace, and WordSpace resource descriptors.
Implemented support in the _OSI method for the ACPI 3.0 "Extended Address Space Descriptor" string, indicating interpreter support for the descriptors above.
Implemented header support for the new ACPI 3.0 FADT flag bits.
Implemented header support for the new ACPI 3.0 PCI Express bits for the PM1 status/enable registers.
Updated header support for the MADT processor local Apic struct and MADT platform interrupt source struct for new ACPI 3.0 fields.
Implemented header support for the SRAT and SLIT ACPI tables.
<[email protected]> (05/02/17 1.1982.92.2)
[ACPI] Add ACPI-based memory hot plug driver.
The ACPI based memory hot plug driver patch supports physical hotplug operations on memory. This driver fields notifications for memory add and remove operations from firmware and notifies the VM of the
affected
memory ranges. Accordingly, this driver also maintains and updates
the
states of all the memory ranges. This driver is useful on hardware
which
helps firmware generating ACPI events for every physical hotplug operation of memory boards on the system during runtime.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
Len Brown wrote:
: There are some very important -- and in some cases, : potentially disruptive -- changes in the latest ACPI patch. :
: EC Burst Mode -- battery status AE_TIME etc.
The bug #4150 (http://bugme.osdl.org/show_bug.cgi?id=4150)
is not fixed wit this patch (i.e. AE_TIME errors are still there if CONFIG_PREEMPT is disabled).
-Yenya
Signature · 3 lines
| Jan "Yenya" Kasprzak <kas at {fi.muni.cz - work | yenya.net - private}> |
| GPG: ID 1024/D3498839 Fingerprint 0D99A7FB206605D7 8B35FCDE05B18A5E |
| http://www.fi.muni.cz/~kas/ Czech Linux Homepage: http://www.linux.cz/ |Quoted 2 lines
Whatever the Java applications and desktop dances may lead to, Unix will <
still be pushing the packets around for a quite a while. --Rob Pike <
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
Quoted 11 lines · Len Brown
There are some very important -- and in some cases, potentially disruptive -- changes in the latest ACPI patch.
EC Burst Mode -- battery status
AE_TIMEetc.
Binding ACPI power states to PCI devices -- power loss in S3 Generic Hot Key Driver -- needs configuration from user space S3 Resume PCI Interrupt Link fix, requiring drivers to behave better Poweroff fix -- compatible with kexec patch
Improved "Implicit Return" AML workaround -- toshiba, compaq etc. RelaxedAE_AML_BUFFER_LIMITcode -- reflects proposed ACPI spec update
Quoted 1 line
Please try it out on a system near you!
Tested on my Samsung P35 notebook:
dmesg.2.6.12-rc1-latest-s3test21-acpi 2005-03-21 18:15:27.000000000 +0100 renamed from dmesg.2.6.11-latest-s3test19 2005-03-21 18:11:50.000000000 +0100 +55 -21
@@ -1,4 +1,4 @@ -Linux version 2.6.11-latest (compiler@p35) (gcc version 3.3.4) #1 Thu Mar 17 23:57:36 CET 2005 +Linux version 2.6.12-rc1-latest-acpi (compiler@p35) (gcc version 3.3.4) #4 Mon Mar 21 17:53:09 CET 2005 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009f800 (usable) BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
@@ -59,14 +59,18 @@ PCI: PCI BIOS revision 2.10 entry at 0xfd9d3, last bus=4 PCI: Using configuration type 1 mtrr: v2.0 (20020519) -ACPI: Subsystem revision 20050211 +ACPI: Subsystem revision 20050309 ACPI: Interpreter enabled ACPI: Using PIC for interrupt routing -ACPI: PCI Root Bridge [PCI0] (00:00) +ACPI: PCI Root Bridge [PCI0] (0000:00) PCI: Probing PCI hardware (bus 00) +ACPI: Assume root bridge [\_SB_.PCI0] segment is 0 PCI: Enabled i801 SMBus device PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1 PCI: Transparent bridge - 0000:00:1e.0 +ACPI: Can't get handler for 0000:00:00.0 +ACPI: Can't get handler for 0000:02:01.0 +ACPI: Can't get handler for 0000:02:01.2 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGPB._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIB._PRT]
@@ -82,6 +86,16 @@ ACPI: Power Resource [CFN1] (off) Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI init +ACPI: No ACPI bus support for 00:00 +ACPI: No ACPI bus support for 00:01 +ACPI: No ACPI bus support for 00:02 +ACPI: No ACPI bus support for 00:03 +ACPI: No ACPI bus support for 00:04 +ACPI: No ACPI bus support for 00:05 +ACPI: No ACPI bus support for 00:06 +ACPI: No ACPI bus support for 00:07 +ACPI: No ACPI bus support for 00:08 +ACPI: No ACPI bus support for 00:09 pnp: PnP ACPI: found 10 devices PCI: Using ACPI for IRQ routing PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
@@ -94,10 +108,12 @@ VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Initializing Cryptographic API +ACPI: No ACPI bus support for vesafb.0 isapnp: Scanning for PnP cards... isapnp: No Plug & Play device found Real Time Clock Driver v1.12 PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12 +ACPI: No ACPI bus support for i8042 i8042.c: Detected active multiplexing controller, rev 1.1. serio: i8042 AUX0 port at 0x60,0x64 irq 12 serio: i8042 AUX1 port at 0x60,0x64 irq 12
@@ -105,11 +121,17 @@ serio: i8042 AUX3 port at 0x60,0x64 irq 12 serio: i8042 KBD port at 0x60,0x64 irq 1 Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing enabled +ACPI: No ACPI bus support for serio0 +ACPI: No ACPI bus support for serio1 +ACPI: No ACPI bus support for serio2 +ACPI: No ACPI bus support for serio3 +ACPI: No ACPI bus support for serio4 +ACPI: No ACPI bus support for serial8250 ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 5 PCI: setting IRQ 5 as level-triggered -ACPI: PCI interrupt 0000:00:1f.6[B] -> GSI 5 (level, low) -> IRQ 5 +ACPI: PCI Interrupt 0000:00:1f.6[B] -> Link [LNKB] -> GSI 5 (level, low) -> IRQ 5 io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered
@@ -140,7 +162,7 @@ ICH4: IDE controller at PCI slot 0000:00:1f.1 PCI: Enabling device 0000:00:1f.1 (0005 -> 0007) ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 5 -ACPI: PCI interrupt 0000:00:1f.1[A] -> GSI 5 (level, low) -> IRQ 5 +ACPI: PCI Interrupt 0000:00:1f.1[A] -> Link [LNKC] -> GSI 5 (level, low) -> IRQ 5 ICH4: chipset revision 3 ICH4: not 100% native mode: will probe irqs later ide0: BM-DMA at 0x1860-0x1867, BIOS settings: hda:pio, hdb:pio
@@ -158,9 +180,11 @@ -> palm detection input: SynPS/2 Synaptics TouchPad on isa0060/serio4 ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 +ACPI: No ACPI bus support for 0.0 Probing IDE interface ide1... hdc: DV-W24ES, ATAPI CD/DVD-ROM drive ide1 at 0x170-0x177,0x376 on irq 15 +ACPI: No ACPI bus support for 1.0 hda: max request size: 1024KiB hda: 156368016 sectors (80060 MB) w/8192KiB Cache, CHS=16383/255/63, UDMA(100) hda: cache flushes supported
@@ -184,67 +208,78 @@ Trying to free ramdisk memory ... failed Freeing unused kernel memory: 192k freed 8139too Fast Ethernet driver 0.9.27 -ACPI: PCI interrupt 0000:02:00.0[A] -> GSI 5 (level, low) -> IRQ 5 -eth0: RealTek RTL8139 at 0xe0860800, 00:00:de:ad:be:ef, IRQ 5 +ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [LNKB] -> GSI 5 (level, low) -> IRQ 5 +eth0: RealTek RTL8139 at 0xe083a800, 00:00:de:ad:be:ef, IRQ 5 eth0: Identified 8139 chip type 'RTL-8101' usbcore: registered new driver usbfs usbcore: registered new driver hub device-mapper: 4.4.0-ioctl (2005-01-12) initialised: [email protected] USB Universal Host Controller Interface driver v2.2 ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 5 -ACPI: PCI interrupt 0000:00:1d.0[A] -> GSI 5 (level, low) -> IRQ 5 +ACPI: PCI Interrupt 0000:00:1d.0[A] -> Link [LNKA] -> GSI 5 (level, low) -> IRQ 5 PCI: Setting latency timer of device 0000:00:1d.0 to 64 uhci_hcd 0000:00:1d.0: UHCI Host Controller +Linux agpgart interface v0.101 (c) Dave Jones uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1 uhci_hcd 0000:00:1d.0: irq 5, io base 0x00001800 +ACPI: No ACPI bus support for usb1 hub 1-0:1.0: USB hub found hub 1-0:1.0: 2 ports detected +ACPI: No ACPI bus support for 1-0:1.0 ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11 PCI: setting IRQ 11 as level-triggered -ACPI: PCI interrupt 0000:00:1d.1[B] -> GSI 11 (level, low) -> IRQ 11 +ACPI: PCI Interrupt 0000:00:1d.1[B] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11 PCI: Setting latency timer of device 0000:00:1d.1 to 64 uhci_hcd 0000:00:1d.1: UHCI Host Controller uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2 uhci_hcd 0000:00:1d.1: irq 11, io base 0x00001820 +ACPI: No ACPI bus support for usb2 hub 2-0:1.0: USB hub found hub 2-0:1.0: 2 ports detected -ACPI: PCI interrupt 0000:00:1d.2[C] -> GSI 5 (level, low) -> IRQ 5 +ACPI: No ACPI bus support for 2-0:1.0 +ACPI: PCI Interrupt 0000:00:1d.2[C] -> Link [LNKC] -> GSI 5 (level, low) -> IRQ 5 PCI: Setting latency timer of device 0000:00:1d.2 to 64 uhci_hcd 0000:00:1d.2: UHCI Host Controller -Linux agpgart interface v0.101 (c) Dave Jones +hw_random: RNG not detected uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3 uhci_hcd 0000:00:1d.2: irq 5, io base 0x00001840 +ACPI: No ACPI bus support for usb3 hub 3-0:1.0: USB hub found hub 3-0:1.0: 2 ports detected +ACPI: No ACPI bus support for 3-0:1.0 ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 11 -ACPI: PCI interrupt 0000:00:1d.7[D] -> GSI 11 (level, low) -> IRQ 11 +ACPI: PCI Interrupt 0000:00:1d.7[D] -> Link [LNKH] -> GSI 11 (level, low) -> IRQ 11 PCI: Setting latency timer of device 0000:00:1d.7 to 64 ehci_hcd 0000:00:1d.7: EHCI Host Controller ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 4 ehci_hcd 0000:00:1d.7: irq 11, io mem 0xd0000000 PCI: cache line size of 32 is not supported by device 0000:00:1d.7 ehci_hcd 0000:00:1d.7: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004 +Linux Kernel Card Services + options: [pci] [cardbus] [pm] +ACPI: No ACPI bus support for usb4 hub 4-0:1.0: USB hub found hub 4-0:1.0: 6 ports detected +ACPI: No ACPI bus support for 4-0:1.0 agpgart: Detected an Intel 855PM Chipset. agpgart: AGP aperture is 256M @ 0xe0000000 -Linux Kernel Card Services - options: [pci] [cardbus] [pm] -ACPI: PCI interrupt 0000:02:01.0[A] -> GSI 5 (level, low) -> IRQ 5 +ACPI: PCI Interrupt 0000:02:01.0[A] -> Link [LNKB] -> GSI 5 (level, low) -> IRQ 5 Yenta: CardBus bridge found at 0000:02:01.0 [144d:c00c] Yenta: ISA IRQ mask 0x0498, PCI irq 5 Socket status: 30000006 -hw_random: RNG not detected PCI: Enabling device 0000:02:01.1 (0000 -> 0002) -ACPI: PCI interrupt 0000:02:01.1[B] -> GSI 5 (level, low) -> IRQ 5 +ACPI: PCI Interrupt 0000:02:01.1[B] -> Link [LNKA] -> GSI 5 (level, low) -> IRQ 5 Yenta: CardBus bridge found at 0000:02:01.1 [144d:c00c] Yenta: ISA IRQ mask 0x0498, PCI irq 5 Socket status: 30000006 ieee1394: Initialized config rom entry `ip1394' ohci1394: $Rev: 1250 $ Ben Collins <[email protected]> -ACPI: PCI interrupt 0000:02:01.2[C] -> GSI 5 (level, low) -> IRQ 5 +ACPI: PCI Interrupt 0000:02:01.2[C] -> Link [LNKC] -> GSI 5 (level, low) -> IRQ 5 +ACPI: No ACPI bus support for fw-host0 ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[5] MMIO=[d0201000-d02017ff] Max Packet=[2048] +ACPI: No ACPI bus support for 0000f0414012c7ff ieee1394: Host added: ID:BUS[0-00:1023] GUID[0000f0414012c7ff] +ACPI: No ACPI bus support for 0000f0414012c7ff-0 SCSI subsystem initialized ReiserFS: hda7: found reiserfs format "3.6" with standard journal ReiserFS: hda7: using ordered data mode
@@ -280,8 +315,8 @@ ip6_tables: (C) 2000-2002 Netfilter core team ip_tables: (C) 2000-2002 Netfilter core team ip_conntrack version 2.1 (4091 buckets, 32728 max) - 248 bytes per conntrack eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 -ACPI: PCI interrupt 0000:00:1f.5[B] -> GSI 5 (level, low) -> IRQ 5 +ACPI: PCI Interrupt 0000:00:1f.5[B] -> Link [LNKB] -> GSI 5 (level, low) -> IRQ 5 PCI: Setting latency timer of device 0000:00:1f.5 to 64 intel8x0_measure_ac97_clock: measured 49457 usecs intel8x0: clocking to 48000
@@ -293,8 +328,7 @@ ACPI: Fan [FAN1] (off) ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3]) ACPI: Thermal Zone [THRM] (53 C) -Asus Laptop ACPI Extras version 0.29 - Samsung P30 detected, supported +Using generic hotkey driver BIOS EDD facility v0.16 2004-Jun-25, 1 devices found eth0: no IPv6 routers present parport: PnPBIOS parport detected.
Seems to work so far. I only tested S3 suspend/resume; my battery is unplugged right now.
Regards,
Carl-Daniel
Signature · 8 lines
http://www.hailfinger.org/ ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 13 lines · Carl-Daniel Hailfinger
Quoted 11 lines · Len Brown
There are some very important -- and in some cases, potentially disruptive -- changes in the latest ACPI patch.
EC Burst Mode -- battery status
AE_TIMEetc.
Binding ACPI power states to PCI devices -- power loss in S3 Generic Hot Key Driver -- needs configuration from user space S3 Resume PCI Interrupt Link fix, requiring drivers to behave better Poweroff fix -- compatible with kexec patch
Improved "Implicit Return" AML workaround -- toshiba, compaq etc. RelaxedAE_AML_BUFFER_LIMITcode -- reflects proposed ACPI spec update
Quoted 7 lines
Quoted 1 line
Please try it out on a system near you!
Tested on my Samsung P35 notebook:
Seems to work so far. I only tested S3 suspend/resume; my battery is unplugged right now.
I take that back. Adjusting display brightness is now at least 10x slower than before. Normally, pressing the keys to change brightness resulted in immediate action. Now, the machine needs 1 second and more to react. Before anybody asks: I have ACPI debugging switched off since it became unbearably slow, so that is not my problem.
Regards,
Carl-Daniel
Signature · 8 lines
http://www.hailfinger.org/ ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click