Re: Toshiba Satellite P10

Jaco Kroon
2005-12-24T00:07:03Z

[-- Attachment #1: Type: text/plain, Size: 3297 bytes --]

Pavel Machek wrote:
> Hi!
>
>
>>>But try _minimal config_, first.
>>
>>Doesn't include CONFIG_NET imho, but kernel/power/ui.h (part of
>>suspend2?) doesn't compile without it. I can probably write a patch,
>>the problem seems to be that ui_helper_data only gets declared if
>>CONFIG_NET is set, but it gets used elsewhere even if CONFIG_NET is
>>not set.
>
> You did not tell me your kernel contains suspend2. Revert those
> patches. In-kernel code tends to have less bells/whistles, but seems
> more reliable to me. (And it is the only one I can help you with.)

Oops. Reverted.

Still does the same thing though, doing:

# echo shutdown > /sys/power/disk
# echo disk > /sys/power/state

(then on that special VT):

Stopping tasks: =========|
Freeing memory... done (0 pages freed)
swsusp: Need to copy 10553 pages
swsusp: critical section/: done (10595 pages copied)
ACPI: PCI Interrupt 0000:00:14:

... and I didn't get the rest cause as soon as I accidentally pressed a
key it powered down ...

It halted directly after "Shutting down hda" (can't remember the exact
message). Powering up resuming worked just fine. Including issues I
had with suspend-to-ram (described below).

This happened at least twice. Having to hit some key to make it go away
is probably not the biggest issue I've had in my life, I guess if need
be I can live with that.

>>Setting CONFIG_NET works around this problem.
>>
>>With almost nothing in the kernel though (only what is essential to make
>>it boot) suspend-to-ram works. Still suspend-to-disk though.
>>
>>Guess it's time to go find the module that causes the problem and fix it
>>(if I can figure it out).
>
> Yep ;-). Keep us updated with name of offending module.

Actually, I lie. There are weird lockups. I can typically do "echo
foo", or "ls", but I for example can't run make, diff or anything funky
(mount without any params works but mount -o rw,remount /boot locks up).
This may be due to incompatibilities with the running kernel and the
installed glibc but I somehow suspect this is not the case. I can also
post my kernel config somewhere if that would help.

In both cases issues any further suspend/resume commands locks up the
system. As in this could also be that caused the lockup after resuming
from ram. Indeed. Retrying the suspend-to-ram and then performing a
remount works. However, running make menuconfig in /usr/src/linux after
that does not.

This feels like a post-wakeup racecondition to me... Disabling the big
kernel lock preemption think again... yes, seems to be working better
now. Suspending to ram and then to disk still fails. (resume from mem
works, can do make menuconfig - a few times - and then it starts
suspend-to-disk process and then just hangs).

Guess I should start by enable many more of those kernel debugging
options ..., right now I need some sleep however.

If I posted my DSDT, could you possibly take a look? It seems that the
compiler error message doesn't mean what it says. Under certain
conditions it will complain if a certain string is set but some index is
not. And I don't know enough with regards to DSL to be able to spot the
errors.

Jaco
--
There are only 10 kinds of people in this world,
those that understand binary and those that don't.
http://www.kroon.co.za/

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3166 bytes --]