Note to the triagers: while I can't exclude the possibility, it doesn't smell like an architecture bug to me, more like a generic bug. The quad is SMPx4 and I was doing extensive disk accesses while trackerd was running, using multiple filesystems (ext3 and xfs), so the kernel was quite "exercized" in ways that I suspect a lot of users don't, which would explain why this didnt' show up on x86.
I'll torture the machine see if I can get that to happen again, and maybe find out a repro-case. -- [hardy] kernel oops triggered by trackerd https://bugs.launchpad.net/bugs/204937 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs