With _TMP faked in the kernel and one whole zone ignored, this is what I
get:
Zone to ignore | Result
THM0OK (10 cycles)
THM2kernel panic! attempted to kill init
THM6
Mark Lord wrote:
I copy all stuff need into tmpfs to ensure that it can restore the video
without hard disk access.
OOhh.. clever, wish I'd thought of that,
One should not forget to disable swap first :)
as all of my (now solved) suspend/resume issues
were *all* libata related.
So I
Two more experiments:
With a vanilla kernel, I faked EC0.UPDT() to just return 0x00, and the
system hung on the second sleep.
Then, again in the DSDT, I also faked the 4 _TMP methods (one in each
thermal zone), and the system hung on the second sleep.
I think we've raced too far ahead
Two more experiments:
With a vanilla kernel, I faked EC0.UPDT() to just return
0x00, and the
system hung on the second sleep.
Then, again in the DSDT, I also faked the 4 _TMP methods (one in each
thermal zone), and the system hung on the second sleep.
I think we've raced too far ahead
Please don't give up . :-)
I haven't!
I need to know which statement in EC0.UPDT that could trigger the
problem. That is very important to understand the problem
correctly.
This is still my assumption that some AML code needed to be avoided
in suspend/resume, I need data support. So, we
WARNING: remove_memory [drivers/acpi/acpi_memhotplug.ko] undefined!
WARNING: add_memory [drivers/acpi/acpi_memhotplug.ko] undefined!
WARNING: acpi_os_allocate [drivers/acpi/acpi_memhotplug.ko] undefined!
Does it actually make sense to load acpi_memhotplug.ko as a module? Will
it all work?
-
To
From: Bjorn Helgaas [EMAIL PROTECTED]
ACPI address space descriptors contain _MIN, _MAX, and _LEN. _MIN and _MAX
are the bounds within which the region can be moved (this is clarified in
Table 6-38 of the ACPI 3.0 spec). We should use _LEN to determine the size
of the region, not _MAX - _MIN +
From: Jiri Slaby [EMAIL PROTECTED]
On some boxes ecdt uid may be equal to 0, so do not test for uids equality,
so that fake handler will be unconditionally removed to allow loading the
real one.
See http://bugzilla.kernel.org/show_bug.cgi?id=6111
Signed-off-by: Jiri Slaby [EMAIL PROTECTED]
Cc:
From: Bjorn Helgaas [EMAIL PROTECTED]
Remove the assumption that acpi_bus_register_driver() returns the number of
devices claimed. Returning the count is unreliable because devices may be
hot-plugged in the future (admittedly not applicable for this driver).
This also fixes a bug: if
From: Bjorn Helgaas [EMAIL PROTECTED]
Tidy up whitespace. No functional change.
Signed-off-by: Bjorn Helgaas [EMAIL PROTECTED]
Cc: Brown, Len [EMAIL PROTECTED]
Signed-off-by: Andrew Morton [EMAIL PROTECTED]
---
drivers/pnp/pnpacpi/rsparser.c | 97 +++
1 files
From: Bjorn Helgaas [EMAIL PROTECTED]
With the combination of PNPACPI and 8250_pnp, we no longer need 8250_acpi.
Signed-off-by: Bjorn Helgaas [EMAIL PROTECTED]
Cc: Russell King [EMAIL PROTECTED]
Cc: Brown, Len [EMAIL PROTECTED]
Cc: Adam Belay [EMAIL PROTECTED]
Signed-off-by: Andrew Morton
From: Bjorn Helgaas [EMAIL PROTECTED]
Even though the devices claimed by asus_acpi.c can not be hot-plugged, the
driver registration infrastructure allows the .add() and .remove() methods to
be called at any time while the driver is registered. So remove __init and
__exit from them.
From: Bjorn Helgaas [EMAIL PROTECTED]
acpi_bus_register_driver() should not return the number of devices claimed.
We're not asking to find devices, we're making a driver available to devices,
including hot-pluggable devices that may appear in the future.
I audited all callers of
From: Andrew Morton [EMAIL PROTECTED],
Venkatesh Pallipadi [EMAIL PROTECTED]
cpu_online_map doesn't exist if !CONFIG_SMP.
This path is rather lame and it'd be nice to fix it better.
Cc: Venkatesh Pallipadi [EMAIL PROTECTED]
Cc: Len Brown [EMAIL PROTECTED]
Signed-off-by: Andrew Morton
From: Bjorn Helgaas [EMAIL PROTECTED]
Remove the assumption that acpi_bus_register_driver() returns the number of
devices claimed. Returning the count is unreliable because devices may be
hot-plugged in the future (admittedly not applicable for this driver).
Since the hardware for this driver
From: Bjorn Helgaas [EMAIL PROTECTED]
Address space descriptors contain _MIN, _MAX, and _LEN. _MIN and _MAX are
the bounds within which the region can be moved (this is clarified in Table
6-38 of the ACPI 3.0 spec). We should use _LEN to determine the size of
the region, not _MAX - _MIN + 1.
From: Adrian Bunk [EMAIL PROTECTED]
ACPI should depend on, not select PCI.
Otherwise, illegal configurations like X86_VOYAGER=y, PCI=y are
possible.
This patch also fixes the options select'ing ACPI to also select PCI.
Signed-off-by: Adrian Bunk [EMAIL PROTECTED]
Cc: Brown, Len [EMAIL
From: Bjorn Helgaas [EMAIL PROTECTED]
ACPI supports fixed hardware (PM_TMR, GPE blocks, etc) in either I/O port
or MMIO space, but used to always request the regions from I/O space
because it didn't check the address_space_id.
Sample ACPI fixed hardware in MMIO space (HP rx2600), was
From: Ashok Raj [EMAIL PROTECTED]
Local apic entries are only 8 bits, but it seemed to not be caught with u8
return value result in the check
cpu_index = NR_CPUS becomming always false.
drivers/acpi/processor_core.c: In function `acpi_processor_get_info':
drivers/acpi/processor_core.c:483:
I tried the following kernels (all with only THM0):
1. No other changes: It hangs, as before and as expected.
2. Commented out a large chunk of the UPDT() method:
diff -r ac2b38909dfa -r c431c477d3b6 dsdt/600x.dsl
--- a/dsdt/600x.dsl Tue Mar 21 17:12:47 2006 -0500
+++ b/dsdt/600x.dsl
Since I don't think Fatal() isn't being called, I guess the problem is
in I2RB. But all those magic numbers in I2RB make me recultant to take
out lines, unless you tell me which changes won't harm the hardware.
How about this. The side effect of this change is that _BIF, _BST could
NOT
work.
21 matches
Mail list logo
