Segfault in initrd with 2.6.24-7 on intel x86_64

Hi,

Care to actually try running a LiveCD rather than just installing the latest kernel? You can download and try the new Hardy Heron Alpha release from http://cdimage.ubuntu.com/releases/hardy/ . You should be able to then test the new kernel via the LiveCD. Let us know if you witness the same errors. General information regarding the release can also be found here: http://www.ubuntu.com/testing/ . Thanks.

Won't the LiveCD have a different ramfs? If so, I fully expect the LiveCD to work. I just manually compiled the 2.6.24-7 kernel, and built-in the drivers for my motherboard, NV-SATA, SCSI, and EXT2/3 support, Set the CPU to Duo-Core, and installed it.

Since the drivers are built in, I do not need the initrd, so that line is left off in the menu.lst. This kernel booted just fine, and I am running it as I type.

Is the LIveCD still necessary to continue debugging?

Here is my config

I'm experiencing the same. I tried to compile kernel 2.6.24-7.11 from hardy on my amd64 feisty machine and it won't boot the new kernel. There are lots of "Segmentation fault" messages during the boot, then ide/sata is loaded and I end in busybox shell. There are so many "Segmentation fault" messages I can't scroll up to the point they start.

I'm downloading the dvd/current/hardy-dvd-amd64.iso and will test it tomorrow (CET time).

I can confirm that the dvd/current/hardy-dvd-amd64.iso boots smoothly.

But I can't still boot the 2.6.24-7-12 kernel, build according to the instructions in https://help.ubuntu.com/community/Kernel/Compile :-(

Care to test the latest 2.6.24-8 kernel. If the seg faults still occur, care to take a digital photo of your screen when they occur and attach it to this bug report. It may help with debugging. Thanks.

Tried the linux_2.6.24-9.15. The same result. :-( The kernel gets loaded, framebuffer gets loaded, then many many lines saying "Segmentation fault", then BusyBox, then SATA modules (over the BusyBox prompt). I've attached a screenshot of the part where "Segmentation fault" ends.

HTH
Patrik

Tried the linux_2.6.24-12.20 with the same result.

Patrik

Hi,

I suggest also installing the hardy udev and hal packages as well. This probably will also pull in a lot of other updated packages.

Let me know if this helps.

Hi,

unfortunately I can't do such big upgrade because it's my work PC and I can't risk breaking the system.

BTW how these packages relate to kernel boot process?

P.

Hi,

udev and hal should be kept in sync with the kernel that you are using.

udev enables Linux to provide a persistent naming of devices in the /dev directory as well as providing a dynamic device naming in /dev. Since udev relies on the structure of /sys (which is known it change from time to time in kernel releases) it is recommended to keep udev in sync with the kernel.

HAL provides an abstract view on the hardware and again it is highly coupled to the kernel.

I suspect that changing the kernel and not upgrading udev and hal is causing the segmentation fault at boot up.

Hi rickyrockrat,

Can you try installing the latest hardy udev and hal packages to see if this resolves the issue.

Hi rockyrockrat,

I was wondering if you have tried installing the latest hardy udev and hal packages to see if this resolved this issue. Please let me know, so that I can either close this bug, or look into resolving the bug further.

Thanks

Colin

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

This bug report is being closed because we received no response to the previous inquiry for information. Please reopen if this is still an issue in the current Ubuntu release, Jaunty Jackalope 9.04. To reopen the bug, click on the current status, under the Status column, and change the status back to "New". Thanks.