Hello !

> We definitely want to robustify scheduler init code to not crash and to (if 
> possible) print a warning about the borkage.

I just tested the last 2.6.32-5 update and it still crashes in the same
manner.

Best regards
Tilo Hacke




-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1292321241.4511.2.ca...@localhost

Reply via email to