On Thu, 16 Jan 2014 11:39:34 +0100, Jan Kara said:
> Hum, the complaint is for group->notification_waitq->lock which
> is an internal lock for the wait queue. Actually the corruption seems to be
> only a single bit flip - the whole spinlock structure looks correct, only
> owner_cpu got flipped
On Wed 15-01-14 13:20:12, Valdis Kletnieks wrote:
> Am seeing this at boot on next-20140114, but I hit this same exact stack trace
> at least once on next-20131218. v3.13-rc7 doesn't have the problem, so it's
> not a 3.13 release showstopper. I may not be able to bisect this, as there's
> 2
>
On Wed 15-01-14 13:20:12, Valdis Kletnieks wrote:
Am seeing this at boot on next-20140114, but I hit this same exact stack trace
at least once on next-20131218. v3.13-rc7 doesn't have the problem, so it's
not a 3.13 release showstopper. I may not be able to bisect this, as there's
2
or 3
On Thu, 16 Jan 2014 11:39:34 +0100, Jan Kara said:
Hum, the complaint is for group-notification_waitq-lock which
is an internal lock for the wait queue. Actually the corruption seems to be
only a single bit flip - the whole spinlock structure looks correct, only
owner_cpu got flipped from
4 matches
Mail list logo
