Yeah, upstart never actually used the threading features of libnih - it
made sense to permit disabling it since it makes the binary
smaller/faster
** Changed in: xen-source (Ubuntu)
Status: Needs Info => Fix Released
--
mkinitramfs does not bulid a xen-friendly initrd
https://launchpad.ne
A recent update in upstart (0.3.8-1) disabled the use of thread (and thus of
__thread).
I can confirm the 4gb fixup warning does not fire anymore for init and logd
(I've disabled the patch in latest xen-source which hides the warning)
--
mkinitramfs does not bulid a xen-friendly initrd
https://
I'm re-affecting this bug here to be sure it will not be abandonned and
it gets a sufficient audience.
Can someone confirm :
- he or she is experiencing the same problem (if using xen 3.0.3, there should
be only one fat "tls warning" without the name of the process, not plenty of
"seg fixup warn
Glad to hear this.
Can you explain what kind of problem is in the kernel ? (I have same
behaviour with kernels derived from other sources)
--
mkinitramfs does not bulid a xen-friendly initrd
https://launchpad.net/bugs/77972
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists
Nothing to do with upstart everything to do with the kernel. Will be
fixed in the next upload.
** Changed in: xen-3.0 (Ubuntu)
Sourcepackagename: xen-3.0 => xen-source
--
mkinitramfs does not bulid a xen-friendly initrd
https://launchpad.net/bugs/77972
--
ubuntu-bugs mailing list
ubuntu-bugs@l
Yes, libc6-xen (2.5-0ubuntu11) is installed.
There is absolutely no problem for processes other than those from upstart
(precisely init and logd).
If I uninstall libc6-xen, I have plenty of fixup warning for apt-get (for
example), none with libc6-xen installed.
With standard upstart (0.3.5-2) an
Have you installed libc6-xen?
** Changed in: xen-3.0 (Ubuntu)
Assignee: Cedric Schieli => ChuckShort
--
mkinitramfs does not bulid a xen-friendly initrd
https://launchpad.net/bugs/77972
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubun
That's just silly, sorry.
I'm rejecting this as an Upstart bug
** Changed in: upstart (Ubuntu)
Status: Confirmed => Rejected
--
mkinitramfs does not bulid a xen-friendly initrd
https://launchpad.net/bugs/77972
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubunt
Yes, this is a well known Xen (upstream) problem, but the only (well
known) solution is clearly to build code that uses the __thread
attribute with the no-tls-direct-seg-ref flag (see
http://wiki.xensource.com/xenwiki/XenSpecificGlibc). That's why even
glibc provides a libc6-xen.
So, the solution
Frankly, this sounds like a Xen problem. I shouldn't need random C
flags just for something "plain" to work on Xen
** Changed in: upstart (Ubuntu)
Sourcepackagename: upstart => xen
--
mkinitramfs does not bulid a xen-friendly initrd
https://launchpad.net/bugs/77972
--
ubuntu-bugs mailing list
I've tracked down this problem to upstart.
With xen-3.0.4, I have a lot of kernel messages like this :
"4gb seg fixup, process init (pid 1), cs:ip 73:08051546"
"4gb seg fixup, process logd (pid 2429), cs:ip 73:0804b0da"
The only processes generating such warnings are init and logd, both of
which
11 matches
Mail list logo
