Displaying 2 results from an estimated 2 matches for "raw_lock".
Did you mean:
raw_block
2017 Oct 18
2
Null deference panic in CentOS-6.5
...ffffffff8109acd6
#13 [ffff8839c2a91f48] kernel_thread at ffffffff8100c20a
The [cbd] is a module developed by us, I think this bug has nothing to
do with it.
And the contents of rq in pick_next_task(struct rq *rq) is (see
attachement for full contents of struct rq):
struct rq {
lock = {
raw_lock = {
slock = 67109881
}
},
nr_running = 2,
cpu_load = {0, 5923, 14993, 13888, 9115},
last_load_update_tick = 4365159236,
nohz_balance_kick = 0 '\000',
skip_clock_update = 0,
load = {
weight = 2,
inv_weight = 0
},
nr_load_updates =...
2012 Oct 17
28
Xen PVM: Strange lockups when running PostgreSQL load
...y it is a byte value...
But putting aside those questions, the fact that two times
there was two cpus waiting on the same lock which from the
lock count (=0) was free seems a bit too much of a coincidence.
Oh and the spinners count in the lock was 2 as one would
expect.
struct rq {
lock = {
raw_lock = {
{
head_tail = 512,
tickets = {
head = 0 ''\000'',
tail = 2 ''\002''
}
}
}
},
nr_running = 1,
...
}
I really don''t know how this happens. Especially cpu#0 seems at
least past the wakeup...