In order to get my Pacemaker/Corosync lsb resources working correctly, I
applied a modified version of Psi-Jack's patch. I'm not sure why he
removed the setting of the "specified" local var, but I left that in
because I have resources that specify their own path to a pidfile.
However, I unconditio
I was hit by this bug, on multiple machines and architectures (x86,
x86_64). I installed the provisional version 1.1.0-15ubuntu1, from
comment #16, and the problems went away.
--
802.3ad interface bonding fails if started too early
https://bugs.launchpad.net/bugs/482419
You received this bug not
I'm also seeing this running On a Penguin Relion 2612, using the
forcedeth gigabit ethernet driver, bonding eth0 and eth1 with bond-mode
4. Also, I'm running a vlan setup on top of the bonded driver.
I can generally get the setup to work by hand, although seemingly not
with a mere "/etc/init.d/ne
An update:
We are now using Intrepid's kernel-2.6.27-7-generic and -server, and
have stopped having the autofs4 issues seen above (at least so far).
For now, we are sticking with Hardy for LTS, but just upgrading to
Intrepid kernel images. FYI.
As for backporting, when I tried Colin's kernel, we
I actually just today built the current Intrepid kernel with "prevu",
but have to wait a bit to reboot. In the meantime, for my colleague who
was experiencing this Oops 2-3 times a week, we compiled and installed
2.6.26.3, and now he hasn't had the problem occur again in over 4 weeks.
However, an
Colin, sorry to bug you again, but can you tell me if this is the same
patch as you applied in your kernel binaries mentioned earlier in the
thread? I was running your kernel for a couple days and just had the
same Oops occur again. My next step is to take the existing ubuntu
kernel, apply just t
Thanks Colin,
You don't have the "server" versions of linux-ubuntu-modules, and
linux-restricted-modules, which we are using to access all our memory
(4G). I can try the generic kernel in the meantime. Can you publish
the actual patch you made (or at least email it to me while I test?)
Thanks!
We have been coming across this bug quite frequently since moving to
8.04. Happened again today on 8.04.1. My work colleague tracked down
the oops, and it is related to a bug in mainline:
http://www.kerneloops.org/search.php?search=graft_tree&btnG=Function+Search
He then found this discussion o
*** This bug is a duplicate of bug 214810 ***
https://bugs.launchpad.net/bugs/214810
** This bug has been marked a duplicate of bug 214810
Kernel Panic due to null pointer dereference in do_add_mount()
--
BUG: Oops when trying to use NFS with autofs
https://bugs.launchpad.net/bugs/242012
