On Fri, Dec 12, 2014 at 12:29 AM, Joe Zeff <j...@zeff.us> wrote: > On 12/11/2014 06:21 PM, Sam Varshavchik wrote: > >> We're talking about fedup doing its thing after rebooting into the >> upgrade kernel. It appears that the sysrq is enabled in the upgrade >> kernel, and I do believe that I accurately explained that sysrq did >> produce a response; unfortunately the response did not solve the problem >> the sysrq key was intended to solve. >> > > Sysrq key did produce an effect, but not, if memory serves, the effect > it's supposed to. Rather similar to a lock-up issue I had before swapping > in a new mobo, where it worked reliably when I tested it, but not when I > needed it because of hardware trouble. No, I don't think that's what's > going on with your system, but the responses you describe just don't sound > right. (And, if you're using the Magic Sysrq Key, it's ^Alt-Sysrq that's > needed, not just sysrq.)
Only sync is enabled by default on Fedora. https://www.kernel.org/doc/Documentation/sysrq.txt # cat /proc/sys/kernel/sysrq 16 So you have to do: echo 1 > /proc/sys/kernel/sysrq Now the other commands will work. I usually just echo the letter to /proc/sysrq-trigger. Chris Murphy -- Chris Murphy
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
