Hi!
> > Some more clues - booting with noreplacement doesn't fix it, so I think
> > the alternatives code is off the hook.
>
> I don't think this adds any new information, but it has been open
> awhile:
>
> http://bugme.osdl.org/show_bug.cgi?id=6542
>
> I was able to narrow it down to the vmsplit setting but I wasn't able
> to debug it further.
Can we at least add error return or something? Or make CPU_HOTPLUG
depend on "normal" VM split, or...? Having s2ram breaking for known
problem is annoying...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
