Bug 57401 - linux-3.9: OOPS in cpumask_weight
Summary: linux-3.9: OOPS in cpumask_weight
Status: NEW
Alias: None
Product: Timers
Classification: Unclassified
Component: Other (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: john stultz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-01 20:49 UTC by Martin Mokrejs
Modified: 2013-05-02 15:53 UTC (History)
1 user (show)

See Also:
Kernel Version: 3.9
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments
OOPS stacktrace (287.65 KB, image/png)
2013-05-01 20:49 UTC, Martin Mokrejs
Details
.config (94.29 KB, text/plain)
2013-05-02 08:51 UTC, Martin Mokrejs
Details
dmesg-3.9-next-20130501__attempt3.txt (153.90 KB, text/plain)
2013-05-02 15:50 UTC, Martin Mokrejs
Details

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).

Note You need to log in before you can comment on or make changes to this bug.