Hide Forgot
Created attachment 531726 [details] Picture of backtrace Description of problem: After a few seconds (or minutes) of uptime, X is beeing stopped and instead a backtrace is shown. This happens sooner (right at the end of booting) for debug-kernels and a little later for normal kernels. The machine isn't reachable via ssh and doesn't respond to keypresses. Nothing is saved in /var/log/messages Version-Release number of selected component (if applicable): kernel-3.1.0-7.fc16 How reproducible: always Steps to Reproduce: 1. boot kernel 2. wait 3. Actual results: X is stopped and a backtrace is shown on the console Expected results: working laptop Additional info: it was working fine with F14, and still is if I boot kernel-PAE-2.6.35.14-100.fc14.i686. I have attached dmesg output and a few pictures of the backtraces Neither 3.2.0-0.rc0.git4.1.fc17 nor kernel-3.0.1-3.fc16 solve the issue. Going back to 2.6.39-1.fc16.i686.PAE works (as do earlier kernels).
Created attachment 531727 [details] Picture of backtrace #2
Created attachment 531728 [details] Picture of backtrace #3
Created attachment 531729 [details] dmesg output
All of those traces seem to be subsequent fallout from something else (note the D taint flag). Can you boot with pause_on_oops=60 (or some other suitable value) to see if you can capture the very first oops? Also, you might want to run memtest on this machine for a while.
Created attachment 531879 [details] Picture of backtrace #4
uploaded a hopefully better picture with pause_on_oops=60 It is definately related to the wireless card (rt2500pci). The laptop runs fine with deactived wifi, but as soon as I activate it with the hardware-button it takes 60 seconds to connect to the AP and another 45 until the bug appears.
Created attachment 531882 [details] Picture of backtrace #5 (with debug kernel)
seems to be fixed with 3.1.5