linux-kernel - Completely dead on resume (no caps lock, nada)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <1154721378.44d3a6627e951@webmail.stanford.edu>
Date:	Fri,  4 Aug 2006 12:56:18 -0700
From:	Brannon Barrett Klopfer <bklopfer@...nford.edu>
To:	linux-kernel@...r.kernel.org
Subject: Completely dead on resume (no caps lock, nada)

Hello,

Sorry to bug the entire list with such a vaugue post, but I'm not sure what
driver/subsystem is causing this problem. I'm sure you all are sick of "My
computer won't suspend, what do I do?" posts, but...well, my computer won't
suspend...

It's a brand-new HP dv8000t laptop (Phoenix BIOS, latest version, core duo,
ahci/ata_piix [native/legacy]). Suspending (echo mem > /sys/power/state)
works fine, but upon resuming, absolutly nothing works -- backlight stays
off, caps/numlock, network, etc. all dead. I've also tried

# cat `which poweroff` > /dev/null # cache it, in case disk dies upon resume
# echo mem > /sys/power/state ; poweroff -f

but it still just hangs (i.e., seems the entire system is just...dead). I've
tried numerous patches from here and there, and tried both native (ahci) and
legacy (ata_piix) sata, and a kernel with as little support as possible --
no usb, ide, smp, module, preempt, etc. I won't flood the lists with other
info, but it's all at

http://www.stanford.edu/~bklopfer/wontsuspend/

I'd be more than happy to try patches/let someone ssh into my box if it'd
help (new, so nothing sensitive on it yet).

Thanks,
Brannon Klopfer

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/