Marking as invalid as it appears my issues stemmed from a failing hard
drive. It's quite possible that system files were corrupted and causing
the havoc I was experiencing. With a new, and tested, hard drive
installed, we've been rock solid so far. I'll open a new report lest I
come across the same
At this moment in time, yes, this is the first occurrence and I have not
been able to reproduce it in any way. Is there anything from the log
entry that might give a clue as to its origin that I may be able to
trigger a response in order to reproduce it?
--
kernel BUG at /build/buildd/linux-2.6.2
Hi Adam,
So is it safe to assume this was a random occurrence ie. this is not
readily reproducible and was the first time you'd experienced this?
Thanks.
** Summary changed:
- kernel bug
+ kernel BUG at /build/buildd/linux-2.6.28/mm/mmap.c
** Changed in: linux (Ubuntu)
Importance: Undecided
If anything else is needed, please don't hesitate to ask.
Like I said, other than the log entry I am at a loss to what caused it.
You can see from the timestamps from the log that it was a bit over two
hours before the kernel bug and the final entry before the reboot. I had
walked away from the ma
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This bug did not have a package associated with it,
which is important for ensuring that it gets looked at by the proper
developers. You can learn more about finding the right package at
https://wiki.ubuntu.com/Bu
It'd be helpful if you could add some more information about your system
to the bug report by executing the command 'apport-collect 360855' from
the problematic system in a terminal.
--
kernel bug
https://bugs.launchpad.net/bugs/360855
You received this bug notification because you are a member o
