Hi!
> > > > Hmm, yes, I guess I want to now. So you have thinkpad that is broken
> > > > with -a1 -m, in 64-bit mode only? And no other differences? (Like,
> > > > same kernel framebuffer driver, both time from console?)
> > >
> > > I have a thinkpad on my desk (T61 with intel graphics) that is broken with
> > > "-a 3" in 64bit mode only (works in 32bit mode). It does, however, work
> > > with "-a 1 -m" in both modes. Everything else is pretty much the same.
> > > Oh - and "-p -m" does not work in both modes.
> >
> > Could you try removing "call verify_cpu" from x86-64 wakeup.S? That's
> > only significant difference I can see...
> >
> > ...hmm, and we may need a bigger stack space on x86-64...
>
> I just verified it, and found out, that only on an old kernel (2.6.16.46)
> "-a 1 -m" was necessary on 64bit, newer kernels (2.6.22 and 2.6.23-rc1)
> worked fine with "-a 3".
>
> So recent kernels might have this already fixed.
I do not know what fixed it, but 2.6.16 is old, so I guess that's
okay. Can anyone see the i386-vs-x86-64 difference in quirks with
2.6.22+?
Hmm, question is what to do with the whitelist :-(.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Suspend-devel mailing list
Suspend-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/suspend-devel
