Date: Wed, 04 Jan 2017 11:41:39 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-acpi@FreeBSD.org Subject: [Bug 146436] [cpufreq] [panic] Panic when changing profile to economy Message-ID: <bug-146436-13733-w0hAuE14DM@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-146436-13733@https.bugs.freebsd.org/bugzilla/> References: <bug-146436-13733@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=146436 --- Comment #5 from smithi@nimnet.asn.au --- (In reply to cyril.elkaim from comment #4) The first thing I'd do is make sure that your compaq mini 1000 isn't just running out of battery. The gap between going to 'economy' and reboot above is about 22 minutes, but unless the battery is more recent than say three years or so, that could be the case? If you resume more or less immediately after suspend, does it normally resume correctly? I'd try running something like this in a script, in background, before switching to battery: % sh /somewhere/myscript & #!/bin/sh while true; do date; acpiconf -i0 | egrep 'State|Remain|Present' >> /somewhere/logfile sleep 60 # perhaps done If that shows any problem, post full 'acpiconf -i0' output here. If that's ok, then as per https://wiki.freebsd.org/DebuggingSuspendResume you could try unloading anything not immediately needed before suspending, I'd first try unloading (or not loading in the first place): a) everything to do with bluetooth, and therefore all netgraph modules. b) if you can do without for a while, everything to do with wireless. c) anything else you can do without during testing, including Xorg. If none of that makes any difference, we can dig deeper into sysctls etc. I'm no expert at any of this .. hopefully others will offer suggestions. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-146436-13733-w0hAuE14DM>