This is not a kernel bug, and a fix has already been implemented. It
should be available shortly, at which point you merely need to install
available updates for Gutsy.
** Summary changed:
- segfault when booting 2.6.22-9-generic
+ Segfaults during boot (from mount)
--
Segfaults during boot (f
Also occurs on 2.6.22-8
Unfortunately removed 22-7 prior to rebooting so cant say if that's
affected too.
--
segfault when booting 2.6.22-9-generic
https://bugs.launchpad.net/bugs/131961
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubun
busybox (1:1.1.3-5ubuntu4) gutsy; urgency=low
* Fix mount segfault while doing bind/move mounts or remounts, introduced
by my external mount helper change (thanks, Ben Collins; LP: #131961).
-- Colin Watson <[EMAIL PROTECTED]> Sat, 18 Aug 2007 19:06:43 +0100
--
segfault when booting 2.
Sorry, this was my fault; I'd tested my external mount helper changes,
but not in the particular scenario that reproduces this bug (use of the
bind/move/remount options). Ben Collins sent me a patch, which I've
uploaded.
** Changed in: busybox (Ubuntu)
Status: Triaged => Fix Released
--
s
I really enjoyed Allan's comment. So much so that I feel I need to say
the same thing. 3 seg faults on boot that seem to cause me no harm
whatsoever.
--
segfault when booting 2.6.22-9-generic
https://bugs.launchpad.net/bugs/131961
You received this bug notification because you are a member of Ubu
I have nothing new to add but I have the same bug.
--
segfault when booting 2.6.22-9-generic
https://bugs.launchpad.net/bugs/131961
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubun
Uh.. did you forget an attachment there?
--
segfault when booting 2.6.22-9-generic
https://bugs.launchpad.net/bugs/131961
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
htt
And my /etc/crypttab has just
home/dev/disk/by-uuid/8ce2a7ce-13c6-4496-9302-2506bf89d7ba none
luks,tries=5,loud
which is used as an LVM PV.
--
segfault when booting 2.6.22-9-generic
https://bugs.launchpad.net/bugs/131961
You received this bug notification because you are a member of Ubuntu
Apparently Launchpad doesn't turn mail attachments into bug attachments?
Let's try again.
** Attachment added: "/etc/fstab"
http://launchpadlibrarian.net/8846877/fstab
--
segfault when booting 2.6.22-9-generic
https://bugs.launchpad.net/bugs/131961
You received this bug notification because y
On 8/16/07, dwg <[EMAIL PROTECTED]> wrote:
> Ok. How are the devices for your secondary filesystems specified in
> /etc/fstab? For me at least, the problem seems to be that some of the
> convenience symlinks are not created, so depending on the names you use,
> it might work.
Like this.
--
Mar
Ok. How are the devices for your secondary filesystems specified in
/etc/fstab? For me at least, the problem seems to be that some of the
convenience symlinks are not created, so depending on the names you use,
it might work.
--
segfault when booting 2.6.22-9-generic
https://bugs.launchpad.net/
On 8/16/07, dwg <[EMAIL PROTECTED]> wrote:
> Martin, but are you seeing the SEGVs during boot?
Hi David,
Yes, I see the message during bootup, but it does not seem to have any
lasting ill effects. I think I filed one of the duplicate bugs.
--
Martin
--
segfault when booting 2.6.22-9-generic
Martin, but are you seeing the SEGVs during boot?
--
segfault when booting 2.6.22-9-generic
https://bugs.launchpad.net/bugs/131961
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
fwiw I have lvm-on-luks, and multiple filesystems, and they seem to
all get mounted properly - but maybe they're getting mounted later on.
--
Martin
--
segfault when booting 2.6.22-9-generic
https://bugs.launchpad.net/bugs/131961
You received this bug notification because you are a member of Ub
I submitted a new bug report [bug 132790], using the command provided by
Matt, as I am not sure the retracing service will retrace a crash report
attached to an existing bug.
--
segfault when booting 2.6.22-9-generic
https://bugs.launchpad.net/bugs/131961
You received this bug notification becaus
** Tags added: needs-i386-retrace
--
segfault when booting 2.6.22-9-generic
https://bugs.launchpad.net/bugs/131961
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://li
** Tags removed: need-i386-retrace
--
segfault when booting 2.6.22-9-generic
https://bugs.launchpad.net/bugs/131961
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://l
** Tags added: need-i386-retrace
--
segfault when booting 2.6.22-9-generic
https://bugs.launchpad.net/bugs/131961
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lis
This is easily reproduced with, e.g.:
sudo /usr/lib/initramfs-tools/bin/busybox mount -o bind /tmp /mnt
I'm attaching an apport crash report, which includes the core file. I'm
not sure whether the retracing service will pick it up automatically; if
it doesn't, then hopefully someone who knows th
Well, i gave a it a shot. Seems that both the scripts/init-bottom/udev
script and the two subsequent mounts cause the segmentation faults. 3 in
total.
Could be that the pkill call inside the udev script is also managing to
segfault.
I'd set this to busybox.
--
segfault when booting 2.6.22-9-gen
As eluded to, this appears to be a regression. Busybox mount -o bind
works fine in Feisty.
--
segfault when booting 2.6.22-9-generic
https://bugs.launchpad.net/bugs/131961
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu
** Changed in: busybox (Ubuntu)
Importance: Undecided => High
Status: Confirmed => Triaged
Target: None => tribe-5
--
segfault when booting 2.6.22-9-generic
https://bugs.launchpad.net/bugs/131961
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I can confirm that this is busybox. I get segfaults when calling
'busybox mount -o move ...' for both /usr/lib/initramfs-
tools/bin/busybox and /bin/busybox (from the plain busybox package as
well as busybox-static).
** Changed in: busybox (Ubuntu)
Sourcepackagename: initramfs-tools => busybox
--
In reference to Robert Vollmert's comment: not having any other
filesystems would explain why you don't get further symptoms.
For me, this is a serious bug. In fact, contrary to my previous
comment, the system won't really boot after this - instead it will give
the "give root password for mainten
As bug #132120 suggests, I've verified that just replacing the busybox
binary (both as /bin/busybox and /bin/sh on the initramfs) with an
older, working version is sufficient to fix the problem.
Replacing the failing calls to mount with explicit calls to /bin/mount -
thereby invoking the klibc ver
I should note that I have root on lvm also, but I don't have any further
problems. I don't have any other filesystems mounted automatically,
though.
Also, /var/crash doesn't seem to contain anything relevant (kvm, gnome-
panel_sensors-applet, apport-gtk).
--
segfault when booting 2.6.22-9-generi
I'm also observing this problem. Here, with a root-on-lvm-on-raid1
setup, these failures confuse the udev initialization sufficiently that
although the system boots, it fails to mount any filesystems other than
root, and things are generally confused later on.
This looks like the same problem as
I have the same / a similar problem:
> [ 62.691534] kjournald starting. Commit interval 5 seconds
> [ 62.691590] EXT3-fs: sdb1: orphan cleanup on readonly fs
> [ 62.691632] ext3_orphan_cleanup: deleting unreferenced inode 16239956
> [ 66.954441] EXT3-fs: sdb1: 1 orphan inode deleted
> [
These are happening here:
/scripts/init-bottom/udev
> mount -n -o move /dev /root/dev
/init
> mount -n -o move /sys /root/sys
> Segmentation fault
> mount -n -o move /proc /root/proc
> Segmentation fault
--
segfault when booting 2.6.22-9-generic
https://bugs.launchpad.net/bugs/131961
You receive
kernel: 2.6.22-9-generic
initramfs-tools: 0.85eubuntu16
arch: i386
I'm having similar/same segfaults when init-bottom script is executed during
boot.
Boot messages contain:
"
Begin: Running /scripts/local-bottom ...
Done.
Done.
Begin: Running /scripts/init-bottom ...
Segmentation fault
Done.
Seg
30 matches
Mail list logo
