Hi Alexander, Alexander Kudrevatykh wrote:
> with new kernel from testing (but only 3.0.0-1-amd64, not latest) I > don't see any crashes, but kernel oopses. To be clear, that means 3.0.0-4 reproduces the BUG but 3.0.0-5 does not? If so, why would that affect anyone? :) [...] > smth like this on every ps/w/top invocation but it worked properly just > after boot, only after some time kernel started oopsing. Please send the first oops (it should say "Not tainted" where this one says "Tainted: G D"). Thanks and hope that helps, Jonathan -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
