Bug 57401

Summary: linux-3.9: OOPS in cpumask_weight
Product: Timers Reporter: Martin Mokrejs (mmokrejs)
Component: OtherAssignee: john stultz (john.stultz)
Status: NEW ---    
Severity: normal CC: lenb
Priority: P1    
Hardware: All   
OS: Linux   
Kernel Version: 3.9 Subsystem:
Regression: Yes Bisected commit-id:
Attachments: OOPS stacktrace
.config
dmesg-3.9-next-20130501__attempt3.txt

Description Martin Mokrejs 2013-05-01 20:49:24 UTC
Created attachment 100381 [details]
OOPS stacktrace

Hi,
  I just this kernel crash on my laptop. I don't have issues like this with 3.8.5 nor 3.7.10.

? cpumask_weight
call_timer_fn.clone
? init_timer_key
run_timer_softirq
? cpumask_weight
__do_softirq
smp_apic_timer_interrupt
apic_timer_interrupt
? cpuidle_wrap_enter
? cpuidle_wrap_enter
cpuidle_enter_tk
cpuidle_enter_state
cpuidle_call
cpu_idel
rest_init
? csum_partial_copy_generic
start_kernel
? repair_env_string
x86_64_start_reservations
x86_64_start_kernel

  I am attaching a camera picture of the screen with the stacktrace.
Comment 1 Martin Mokrejs 2013-05-02 08:51:36 UTC
Created attachment 100421 [details]
.config
Comment 2 Martin Mokrejs 2013-05-02 15:50:13 UTC
Created attachment 100551 [details]
dmesg-3.9-next-20130501__attempt3.txt

I had to try two boot attempts to be able to just login and save dmesg into a file. That quickly happens the OOPS. Interestingly, while I was tetsing some patch applied over
" git clone http://cgit.freedesktop.org/~danvet/drm-intel drm-intel-nightly  "
that underlying linux snapshot does not have this bug. But I am not skilled enough to figure out whether the drm-intel is based on vanilla 3.9 or something else (supposedly not linux-next-20130501).