@arturj -- The symptom implies that slub went to return some memory to
the main allocator that does not appear (at least at the time the free
occured) to have belonged to slub. Either slub freed it earlier or
someone who should not have (outside slub) has freed it without slub's
knowledge. Bad. is this reproducible? ie. does it occur often on
resume from suspend or is this a one off? if it is not reproducible we
are very unlikely to be able to find it via debug.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Andy Whitcroft (apw)
--
kernel BUG at /build/buildd/linux-2.6.28/mm/slub.c:2743!
https://bugs.launchpad.net/bugs/367744
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
