On Tuesday 08 June 2010, Alan Jenkins wrote: > I found this bug 2.6.34 on my Asus EeePC 701 (x86_32 arch). It didn't > happen to me before, when I was running nearly-2.6.33 or 2.6.32-release. > > I used git-bisect, but unfortunately the result isn't very helpful. My > next step will be to try to narrowing down the culprits by disabling > individual CONFIG options. Here are my results so far, in case anyone > is interested. > > > == Steps to reproduce == > > I) Boot off mains power, with battery removed. Login to KDE4 session, > with Konsole as the only running application. > II) Run "sudo pm-hibernate" > > 1. When the system switches to text mode (a.k.a the console), > immediately insert the battery. > 2. Once the system has fully hibernated, remove the battery. > 3. Press the power button to resume. The backtrace below is generated > during resume.
You're not supposed to be doing that. Rafael -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
