On Thu, 2012-12-27 at 12:44 +0100, Mattias wrote: > Hi! > > I have a VIA VB8001-16 motherboard running xen and when using > linux-image-3.2.0-0.bpo.4-amd64 I can trigger a kernel oops in domU. > I suspect that this is caused by the bug > corrected in commit a349e23d1cf746f8bdc603dcc61fae9ee4a695f6 upstream. > But that is just my unqualified guess. > > And for debian testing: > > linux (3.2.35-1) unstable; urgency=low > . > * New upstream stable update: > ... > - [x86] xen: don't corrupt %eip when returning from a signal > handler This particular bug would cause a userland crash or other misbehaviour - not a kernel oops. Also I think it only affects i386 and not amd64. > Sorry for the poor formatting, below: > > [ 854.826235] alignment check: 0000 [#1] SMP Alignment check is surprising but could be introduced by the hypervisor. [...] > Does anyone know more about this, or have any advice how to debug this? > I'm fairly capable (I think) of debugging code using gdb in userspace, never > tried kernel gdb though. Try asking on debian-kernel; we have at least one Xen developer reading. Ben. -- Ben Hutchings The world is coming to an end. Please log off.
Description: This is a digitally signed message part