[root@apone athlon]# rpm -ivh kernel-2.4.18-0.40.athlon.rpm Preparing... ########################################### [100%] 1:kernel ########################################### [100%] /sbin/new-kernel-pkg: line 23: 2671 Segmentation fault /sbin/grubby --add-kernel=/boot/vmlinuz-$version $INITRD --copy-default --title "Red Hat Linux ($version)" [root@apone athlon]# [root@apone athlon]# rpm -q mkinitrd mkinitrd-3.4.3-1 grub.conf attached.
Created attachment 59625 [details] the grub.conf in use
I can't recreate this... Do you have a machine I can see this on?
fixed in 3.4.4 (blush) don't know why apone showed this so easily and other machines didn't -- pretty basic bug
I'm seeing this in upgrade.log with re0726.1. Upgrades from both 7.2 and 7.3. Upgrading mkinitrd-3.4.19-1. Upgrading kernel-smp-2.4.18-7.80. /sbin/new-kernel-pkg: line 247: 1078 Segmentation fault /sbin/grubby --add-kernel=/boot/vmlinuz-$version $INITRD --copy-default --title "$title" --args="root=$rootdevice" --remove-kernel="TITLE=$title" Upgrading iptables-1.2.5-5. /var/tmp/rpm-tmp.22440: line 1: [: /var/tmp/rpm-tmp.22440: integer expression expected Upgrading kernel-2.4.18-7.80. /sbin/new-kernel-pkg: line 247: 1427 Segmentation fault /sbin/grubby --add-kernel=/boot/vmlinuz-$version $INITRD --copy-default --title "$title" --args="root=$rootdevice" --remove-kernel="TITLE=$title"
My logs show that it stopped after 0531.1 but reappeared with 0725.0.
This should be fixed in 3.4.20 -- please make sure you test and confirm. The ip-tables problem is separate; I assume it got reported elsewhere.
I meant 3.4.19 -- please holler (loudly) if this fails in tonights build.
> I meant 3.4.19 -- please holler (loudly) if this fails in tonights build. This was with 3.4.19-1, and I am seeing it with Milan-re0728.nightly.
Jeremey Katz fixed this.
I am still seeing this in upgrade.log with Milan-re0812.nightly and Milan-re0813.nightly: Upgrading mkinitrd-3.4.22-1. Upgrading kernel-smp-2.4.18-7.95. /sbin/new-kernel-pkg: line 247: 1029 Segmentation fault /sbin/grubby --add-kernel=/boot/vmlinuz-$version $INITRD --copy-default --title "$title" --args="root=$rootdevice" --remove-kernel="TITLE=$title"
The same here: root@wombat:~> rpm -ivh /scratch/8.0/kernel/2.4.18-10.98/athlon/kernel-2.4.18-10.98.athlon.rpm --oldpackage Preparing... ########################################### [100%] 1:kernel ########################################### [100%] /sbin/new-kernel-pkg: line 249: 6249 Segmentation fault /sbin/grubby --add-kernel=$bootPrefix/vmlinuz-$version $INITRD --copy-default --title $version --args="root=$rootdevice" --remove-kernel="TITLE=$version" --lilo root@wombat:~> rpm -qf /sbin/grubby mkinitrd-3.4.23-1
Created attachment 70705 [details] another grub.conf where grubby crashes
Still seeing this.
Nils, the crash you saw was due to the lilo.conf, not the grub.conf. Mike -- is the one you see when running with --lilo or not?
No, there is no --lilo in my cases. I am only seeing this with 7.2 and 7.3 upgrade cases right now. (This error message has not appeared in a <7.2 upgrade case since late July). I believe that in all these cases, the original install used grub. In all the kickstart cases (either the 7.[23] install or the beta upgrade ks) I am using the 'bootloader' directive with no arguments. It has also been observed with some manual upgrades (where I almost certainly picked the defaults on the bootloader screen).
still seeing this with -re1202.nightly * ks upgrade * RH-everything-upgrade_from_7.3-mirror-english-nfs-GUI * mkinitrd-3.4.32-1. Upgrading kernel-2.4.19-0.pp.20. /sbin/new-kernel-pkg: line 249: 3183 Segmentation fault /sbin/grubby --add-kernel=$bootPrefix/vmlinuz-$version $INITRD --copy-default --title "$title" --args="root=$rootdevice" --remove-kernel="TITLE=$title"
Created attachment 87247 [details] full upgrade/log for -re1202.nightly-i386, RH-everything-upgrade_from_7.3-mirror-english-nfs-GUI
Commiting another fix to fix mikem's case. If the default doesn't have root=, we shouldn't try to use it as the default. Will be in 3.4.34-1
Assuming fixed these days.