It is currently Sat, 24 Oct 2020 17:29:55 GMT



 
Author Message
 OOPS when switching consoles while closing X.

Someone is calling console functions from interrupt context.
Unfortunately your backtrace looks wrong.  Could you
please rerun ksymoops and send me the output?  Make
sure you're using the correct System.map (ksymoops -m).

It should be pretty straightforward to fix.  While we're there
we'll do something about do_SAK(), which is acquiring the
tasklist_lock from interrupt context.  For heaven's sake.

-
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at   http://www.**-**.com/
Please read the FAQ at   http://www.**-**.com/



 Mon, 01 Sep 2003 22:20:04 GMT   
 
   [ 1 post ] 

Similar Threads

1. how to switch resolutin from within X.

2. Keyboard lockup switching out of X.

3. switching from vga console to svga console

4. Press Ctrl-D whiling inputting

5. 2.5.20 -- Hanging (no oops and sysrq fails) after switching to rivafb

6. close applications in xterm vs console

7. Closing 'X' messes up text console

8. matroxfb console oops in 2.4.2x

9. Dead machine, blinking Keyboard and no Oops on console

10. console lockup and oops 2.5.27


 
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Designed by ST Software