This release has reached end-of-life [0].
[0] https://wiki.ubuntu.com/Releases
** Changed in: linux (Ubuntu Maverick)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/67323
newer kernels do work with the changes binutils
maverick isn't supported anymore.
** Changed in: binutils (Ubuntu)
Status: New => Fix Released
** Changed in: binutils (Ubuntu Maverick)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubun
Hi Leann,
The patch you said is included upstream was reverted the next day in
v2.6.38-rc2, so the reason given for Fix Released status is not
applicable.
I don't have permission to revert the status change, so please do that
if you agree.
$ git describe --contains 6b35eb9ddcddde7b510726de03fae0
With regards to the kernel, it appears the patch noted in comment #17 is
included as of upstream v2.6.38-rc1:
$ git describe --contains 86b1e8dd83cbb0fcbf3d61d2b461df8be1f528cf
v2.6.38-rc1~3^2~1
As such I'm marking the actively developed linux task (ie currently
Oneiric) as Fix Released. I'll op
thanks. the patch mentioned, 86b1e8dd83cbb0fcbf3d61d2b461df8be1f528cf,
currently available at https://patchwork.kernel.org/patch/485751/ fixes the
issue. i've attached the patch also.
-matt
** Patch added: "x86: Make relocatable kernel work with new binutils"
https://bugs.launchpad.net/ubunt
Working kernels can be built in Maverick with any one of these:
1. Disabled CONFIG_RELOCATABLE. That makes the problem go away,
and it makes a bunch of build warnings go away too (they indicate the
problem, and they really should cause the build to fail, but they just
warn).
2. Use an o
thanks jools. hopefully this won't be an issue in natty. i'll find out in the
next week.
-matt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/673236
Title:
maverick toolchain producing unbootable (h
I can confirm this issue. I currently build kernels on a lucid
virtualbox to use on maverick/natty.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags removed: needs-kernel-logs needs-upstream-testing
--
You received this bug notification because you are a member of Ub
also, i'm a little unclear as to why this was marked as being invalid,
without any comment or explanation. if it's not a problem with binutils,
please explain why, and what is necessary to have upstream vanilla
kernels build properly.
thanks,
-matt
** Changed in: binutils (Ubuntu)
Status:
yes, this is still an issue. i've been compiling kernels in a lucid
chroot as noted in previous posts. this issue did not present itself
using squeeze/amd64 and compiling 2.6.36.2. it may be limited to 32bit
x86.
-matt
--
You received this bug notification because you are a member of Ubuntu
Bugs
Hi m4t,
This bug was reported a while ago and there hasn't been any activity in it
recently. We were wondering if this is still an issue? Can you try with the
latest development release of Ubuntu? ISO CD images are available from
http://cdimage.ubuntu.com/releases/ .
If it remains an
hey jamie,
thanks for bringing those changes to light. please do post the patch.
-matt
--
maverick toolchain producing unbootable (hanging) kernels
https://bugs.launchpad.net/bugs/673236
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: binutils (Ubuntu)
Status: New => Invalid
--
maverick toolchain producing unbootable (hanging) kernels
https://bugs.launchpad.net/bugs/673236
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
maverick toolchain producing unbootable (hanging) kernels
https://bugs.launchpad.net/bugs/673236
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
Ok, I've found the problem. Binutils changed the meaning of symbol
assignments in linker scripts. It is actually documented, but rather
obscurely in /usr/share/doc/binutils/ld/NEWS.gz.
This breaks the relocation of "jiffies". It also makes got.plt go away
in each vdso (a small improvement).
Th
** Also affects: linux
Importance: Undecided
Status: New
--
maverick toolchain producing unbootable (hanging) kernels
https://bugs.launchpad.net/bugs/673236
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
I can confirm this problem, although my symptoms are slightly different.
I've been using vanilla kernels (tracking kernel.org) since Lucid on my x86
32-bit laptop.
After upgrading to Maverick, subsequent built kernels all failed to boot,
panicing early with a message about timer IRQ routing and
i tested with debian experimental (2.20.90.20101105-1) in lucid chroot
with same results.
i've attached a very minimal .config for 2.6.36 that results in a hang
at 'Calibrating delay loop...' when run like: qemu -cpu coreduo -m 512M
-kernel arch/x86/boot/bzImage -s
unsetting CONFIG_RELOCATABLE wi
please could you check with binutils from Debian/experimental too? The
last armel build in natty didn't pass the testsuite.
--
maverick toolchain producing unbootable (hanging) kernels
https://bugs.launchpad.net/bugs/673236
You received this bug notification because you are a member of Ubuntu
Bug
brief testing of natty's binutils_2.20.90.20101105-0ubuntu1_i386.deb
shows the bug is also present there.
-matt
--
maverick toolchain producing unbootable (hanging) kernels
https://bugs.launchpad.net/bugs/673236
You received this bug notification because you are a member of Ubuntu
Bugs, which is
further investigation shows that maverick binutils is more likely the
culprit than maverick gcc.
** Package changed: gcc-4.4 (Ubuntu) => binutils (Ubuntu)
--
maverick toolchain producing unbootable (hanging) kernels
https://bugs.launchpad.net/bugs/673236
You received this bug notification becaus
this actually seems to be directly related to the maverick binutils
package, binutils_2.20.51.20100908-0ubuntu2_i386.deb
replacing lucid's binutils with this inside a chroot causes the same
boot failures with CONFIG_RELOCATABLE=y, when used alongside the rest of
lucid's toolchain.
-matt
--
mave
after some further narrowing of kernel config, it appears that
'CONFIG_RELOCATABLE=y' is causing the kernel to become unbootable with
maverick's 32bit toolchain. unsetting this parameter produces a bootable
kernel on maverick. again, lucid toolchain produces bootable kernels
with or without 'CONFIG
** Attachment added: "2.6.36 .config resulting in hanging kernel"
https://bugs.launchpad.net/bugs/673236/+attachment/1728348/+files/.config
--
maverick toolchain producing unbootable (hanging) kernels
https://bugs.launchpad.net/bugs/673236
You received this bug notification because you are a
24 matches
Mail list logo
