Seeing this on my Dell Latitude. The timestamps from the 'cut here' and
WARNING lines are different even though they're issued by sequential lines in
panic.c - but then the printk timestamps remain identical even through an
*entire second* WARN call. Is somebody blocking clock interrupts and failing
to re-enable them, or is something different going on here?
[42875.543219] ------------[ cut here ]------------
[42875.544006] WARNING: at lib/plist.c:57 plist_check_head+0x47/0x114()
[42875.544006] WARNING: at lib/plist.c:57 plist_check_head+0x47/0x114()
[42875.544006] Hardware name: Latitude E6500
[42882.428016] ------------[ cut here ]------------
[42882.428016] WARNING: at lib/plist.c:57 plist_check_head+0x47/0x114()