Bug#530357: grub2: Grub2 after 1.96+20090317-1(last working ver) broken. root=UUID=... cannot be found.
severity 530357 important thanks Am Sonntag, den 24.05.2009, 12:56 +0200 schrieb Mateusz Kaduk: After upgrading to older than 1.96+20090317-1 grub2. I experience rootfs timeout due to missing UUID and falling back to (initramfs) busybox. After ls /dev/disk/by-uuid on (initramfs) directory does not contain that UUID, while after activating lvm and chrooting I see that those UUID exist there. Seems like the LVM package still doestn't have proper udev rules to export the UUID in the initrd or it just was created with an older version which doestn't have yet this feature. As workaround you can set GRUB_DISABLE_LINUX_UUID=true in /etc/default/grub and then run update-grub again, so that UUIDs won't be used for the root= kernel parameter. -- Felix Zielcke -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#518791: PC not bootable after update of grub 1.96
forcemerge 497791 518791 thanks Am Sonntag, den 08.03.2009, 18:19 +0100 schrieb Debian: Because this PC is running very bad with grub 1.96 i will go back to the old legacy version of grub! One the most problems is that grub 1.96 does not suffer to hide partitions. And now i can't reconstruct the original grub.cfg that worked before because there is no backup!!! This newer grub is working with this crazy ID's and i don't know how to reconstruct it with a booted knoppix (32 bit on a 64 bit-system. So grub 1.96 is just a catastrophe for me! I will kill the complete system now and restore a backup from an other system with a perfectly running debian-squeeze with grub 0.96 now. You must do something with the new grub please! Known problem, see #497791, #512787 and #514673. You need to run `grub-install /dev/sda' to really update grub2. -- Felix Zielcke -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514673: grub2: Command initrd not found
forcemerge 497791 514673 thanks Am Dienstag, den 10.02.2009, 00:08 +0100 schrieb Thomas Schweikle: grub starts, but then stops with the message command initrd not found. The system remains unbootable. If you have an older version of grub available on CD or FD you can use this to boot the system. The latest version of grub is indeed missing the command initrd. This isn't documented anywhere and it seems as if this command was canceled in favour of some other idea. Because of missing docs I was not able to find out what new idea this was! Please see bug 512787 and 497791. The problem is the `search --fs-uuid' line. It seems like an old version of grub2 had a bug in the parser which is already fixed, but grub-install is not run automatically on an upgrade. Which reportbug should normally tell you if you report a bug against grub-pc. -- Felix Zielcke -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#502333: Bug #502333 ext3 external journal_dev crashes grub2
Hello,
can you please try out if the attached patch solves your problem?
You can find instructions for compiling your own grub packages at the
Debian wiki:
http://wiki.debian.org/de/GRUB2/Anleitung/DebianPaketVonOriginalQuelltext
Just place the patch in debian/patches.
--
Felix Zielcke
Index: fs/ext2.c
===
--- fs/ext2.c (revisión: 1799)
+++ fs/ext2.c (copia de trabajo)
@@ -71,8 +71,53 @@
? EXT2_GOOD_OLD_INODE_SIZE \
: grub_le_to_cpu16 (data-sblock.inode_size))
-#define EXT3_FEATURE_COMPAT_HAS_JOURNAL 0x0004
+/* Superblock filesystem feature flags (RW compatible)
+ * A filesystem with any of these enabled can be read and written by a driver
+ * that does not understand them without causing metadata/data corruption */
+#define EXT2_FEATURE_COMPAT_DIR_PREALLOC 0x0001
+#define EXT2_FEATURE_COMPAT_IMAGIC_INODES 0x0002
+#define EXT3_FEATURE_COMPAT_HAS_JOURNAL 0x0004
+#define EXT2_FEATURE_COMPAT_EXT_ATTR 0x0008
+#define EXT2_FEATURE_COMPAT_RESIZE_INODE 0x0010
+#define EXT2_FEATURE_COMPAT_DIR_INDEX 0x0020
+/* Superblock filesystem feature flags (RO compatible)
+ * A filesystem with any of these enabled can be safely read by a driver that
+ * does not understand them, but should not be written to, usually because
+ * additional metadata is required */
+#define EXT2_FEATURE_RO_COMPAT_SPARSE_SUPER 0x0001
+#define EXT2_FEATURE_RO_COMPAT_LARGE_FILE 0x0002
+#define EXT2_FEATURE_RO_COMPAT_BTREE_DIR 0x0004
+#define EXT4_FEATURE_RO_COMPAT_GDT_CSUM 0x0010
+#define EXT4_FEATURE_RO_COMPAT_DIR_NLINK 0x0020
+#define EXT4_FEATURE_RO_COMPAT_EXTRA_ISIZE 0x0040
+/* Superblock filesystem feature flags (back-incompatible)
+ * A filesystem with any of these enabled should not be attempted to be read
+ * by a driver that does not understand them, since they usually indicate
+ * metadata format changes that might confuse the reader. */
+#define EXT2_FEATURE_INCOMPAT_COMPRESSION 0x0001
+#define EXT2_FEATURE_INCOMPAT_FILETYPE 0x0002
+#define EXT3_FEATURE_INCOMPAT_RECOVER 0x0004 /* Needs recovery */
+#define EXT3_FEATURE_INCOMPAT_JOURNAL_DEV 0x0008 /* Volume is journal device */
+#define EXT2_FEATURE_INCOMPAT_META_BG 0x0010
+#define EXT4_FEATURE_INCOMPAT_EXTENTS 0x0040 /* Extents used */
+#define EXT4_FEATURE_INCOMPAT_64BIT 0x0080
+#define EXT4_FEATURE_INCOMPAT_FLEX_BG 0x0200
+/* The set of back-incompatible features this driver DOES support. Add (OR)
+ * flags here as the related features are implemented into the driver */
+#define EXT2_DRIVER_SUPPORTED_INCOMPAT ( EXT2_FEATURE_INCOMPAT_FILETYPE \
+ | EXT4_FEATURE_INCOMPAT_EXTENTS )
+/* List of rationales for the ignored incompatible features:
+ * needs_recovery: Not really back-incompatible - was added as such to forbid
+ * ext2 drivers from mounting an ext3 volume with a dirty
+ * journal because they will ignore the journal, but the next
+ * ext3 driver to mount the volume will find the journal and
+ * replay it, potentially corrupting the metadata written by
+ * the ext2 drivers
+ */
+#define EXT2_DRIVER_IGNORED_INCOMPAT ( EXT3_FEATURE_INCOMPAT_RECOVER )
+
+
#define EXT3_JOURNAL_MAGIC_NUMBER 0xc03b3998U
#define EXT3_JOURNAL_DESCRIPTOR_BLOCK 1
@@ -486,10 +531,12 @@
return 0;
}
+#define EXT2_DRIVER_MOUNT_FAIL(message) { local_error = (message); goto fail; }
static struct grub_ext2_data *
grub_ext2_mount (grub_disk_t disk)
{
struct grub_ext2_data *data;
+ const char *local_error = 0;
data = grub_malloc (sizeof (struct grub_ext2_data));
if (!data)
@@ -498,13 +545,19 @@
/* Read the superblock. */
grub_disk_read (disk, 1 * 2, 0, sizeof (struct grub_ext2_sblock),
(char *) data-sblock);
- if (grub_errno)
-goto fail;
+ if (grub_errno != GRUB_ERR_NONE)
+EXT2_DRIVER_MOUNT_FAIL(0);
/* Make sure this is an ext2 filesystem. */
if (grub_le_to_cpu16 (data-sblock.magic) != EXT2_MAGIC)
-goto fail;
+EXT2_DRIVER_MOUNT_FAIL(not an ext2 filesystem);
+ /* Check the FS doesn't have feature bits enabled that we don't support. */
+ if (grub_le_to_cpu32 (data-sblock.feature_incompat)
+ ~(EXT2_DRIVER_SUPPORTED_INCOMPAT | EXT2_DRIVER_IGNORED_INCOMPAT))
+EXT2_DRIVER_MOUNT_FAIL(filesystem has unsupported incompatible features);
+
+
data-disk = disk;
data-diropen.data = data;
@@ -514,13 +567,15 @@
data-inode = data-diropen.inode;
grub_ext2_read_inode (data, 2, data-inode);
- if (grub_errno)
-goto fail;
+ if (grub_errno != GRUB_ERR_NONE)
+EXT2_DRIVER_MOUNT_FAIL(0);
return data;
fail:
- grub_error (GRUB_ERR_BAD_FS, not an ext2 filesystem);
+ /* Only call grub_error if the fail was _not_ caused by underlying errors. */
+ if (local_error)
+grub_error (GRUB_ERR_BAD_FS, local_error);
grub_free (data);
return 0;
}
Bug#512787: upgrade makes system unbootable
Am Montag, den 26.01.2009, 10:38 +0100 schrieb Michael Schuerig: I checked in grub-emu (...-14!) and search --fs-uuid --set 546d6205-7424-4a37-86e5-d1e355c3d2ba didn't produce any output at all. Whatever it did, I got another prompt afterwards. With `--set' argument it just sets the root variable to the device and doestn't print out any output. With `set' command you can check the value of the root variable. -- Felix Zielcke -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#501306: update-grub fails silently with wrong device.map
Am Mittwoch, den 29.10.2008, 14:30 +0100 schrieb Robert Millan: I don't like that it is an ugly hack, in the sense that we're trying to stop reliing on this sort of heuristic, and this only works around the problem. Our long-term fix is to use only reliable identifiers like UUIDs. But since all of this is temporary, I suppose we could live with it. Felix, what do you think? I aggree. -- Felix Zielcke -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#501306: update-grub fails silently with wrong device.map
Attached is now an ugly patch which would display the grub-probe error
Check your device.map if it fails.
Else I had the idea to make an environment variable like
GRUB_PROBE_HIDE_ERRORS=1 which would hide the output of
grub_print_error() but then we would need to change grub-common and grub
package to fix this bug.
What do you think Robert?
--
Felix Zielcke
Index: update-grub
===
--- update-grub (revision 1080)
+++ update-grub (working copy)
@@ -115,7 +115,8 @@ find_device ()
if ! test -e ${device_map} ; then
echo quit | grub --batch --no-floppy --device-map=${device_map} /dev/null
fi
- grub-probe --device-map=${device_map} -t device $1 2 /dev/null
+ grub-probe --device-map=${device_map} -t device $1 2 /dev/null || \
+ (echo Cannot find a GRUB drive for $1. Check your device.map. exit 1)
}
# Usage: convert_raid1 os_device
@@ -152,7 +153,8 @@ convert () {
if ! test -e ${device_map} ; then
echo quit | grub --batch --no-floppy --device-map=${device_map} /dev/null
fi
- GRUB_LEGACY_0_BASED_PARTITIONS=1 grub-probe --device-map=${device_map} -t drive -d $1 2 /dev/null
+ GRUB_LEGACY_0_BASED_PARTITIONS=1 grub-probe --device-map=${device_map} -t drive -d $1 2 /dev/null || \
+(echo Cannot find a GRUB drive for $1. Check your device.map. exit 1)
}
# Usage: convert_default os_device
Bug#500336: grub - Misguides Xen images
Hi, sorry for not replying directly but somehow the mails of this report got lost for me, update-grub adds 2.6.26-1-686-bigmem with a Xen hypervisor to the grub config. This image does not support to be loaded as initial domain by the hypervisor. I don't get this Xen stuff There is this [0] message from Ian Campbell which says that there's no way to dertermine if a CONFIG_PARAVIRT=y + CONFIG_XEN=y runs in a Dom0 or not. # diff -u config-2.6.26-1-*|egrep 'XEN|PARAVIRT' CONFIG_PARAVIRT_GUEST=y CONFIG_XEN=y CONFIG_XEN_MAX_DOMAIN_MEMORY=8 +CONFIG_XENCTRL=y CONFIG_PARAVIRT=y -CONFIG_XEN_BLKDEV_FRONTEND=m +CONFIG_XEN_BLKDEV_FRONTEND=y -CONFIG_NETXEN_NIC=m -CONFIG_XEN_NETDEV_FRONTEND=m +CONFIG_XEN_NETDEV_FRONTEND=y CONFIG_HVC_XEN=y CONFIG_XEN_FBDEV_FRONTEND=y CONFIG_XEN_BALLOON=y CONFIG_XEN_SCRUB_PAGES=y So should we also grep for CONFIG_XENCTRL=y to be more on the safe side that this kernel can be loaded with the Xen hypervisor? There was a bugreport that we shouldn't look for *-xen-* in the filename, because some other thing uses xen too which has nothing to do with the Xen virtualization if I remember correctly and for custom kernels this wouldn't work anyway. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#501306: update-grub fails with raid1 boot partition
Hello, Am Montag, den 06.10.2008, 13:44 +0100 schrieb Dan Poltawski: [EMAIL PROTECTED]:~# /usr/sbin/grub-probe --device-map=/boot/grub/device.map -t drive -d /dev/sda1 error: cannot open `/dev/sdf' error: cannot open `/dev/sdf' grub-probe: error: Cannot find a GRUB drive for /dev/sda1. Check your device.map. *** BEGIN /boot/grub/device.map (hd0) /dev/sde (hd1) /dev/sdf *** END /boot/grub/device.map If you do `grub-install /dev/sda' then it should be in your device.map. Either run grub-mkdevicemap --no-floppy or grub-install with `--recheck --no-floppy'. By the way grub2 does support the linux software raid fully, with it you could just do `grub-install (md0)' if /dev/md0 is your /boot, to install it on all raid disks. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#501306: update-grub fails with raid1 boot partition
Am Montag, den 06.10.2008, 19:02 +0200 schrieb Felix Zielcke: If you do `grub-install /dev/sda' then it should be in your device.map. Either run grub-mkdevicemap --no-floppy or grub-install with `--recheck --no-floppy'. Urm I forgot somehow that you're talking about update-grub not grub-install. But somewhere /dev/sda has to come from which isn't visible on the report. Is your /dev/md0 over sda or something like that? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500482: Segmentation fault in grub-probe
Am Montag, den 29.09.2008, 00:45 +0200 schrieb ziborski.net admin: No, there are no removed devices, all are active sync. Please note that /dev/md3 is a RAID0 built on top of two RAID1 (md1 and md2) which causes md2 - and its underlying partitions sdc3 and sdd3 to start with the second 16 KiB chunk of /dev/md3 (and LVM pv it is containing). Ah you use LVM. There's a known problem with it's circular metadata which isn't yet fixed upstream but there's a patch floating around which solves this. Maybe that's your problem. I just tried now a mdraid md2 which goes over mdraid md1 and md0 and this didn't lead to a segfault in grub-probe. Here you find the patch and intructions how to compile it: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495949#69 If this still doestn't solve your problem then we need a GDB backtrace. Instructions for this are in same report. Maybe this is even related to it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500482: Segmentation fault in grub-probe
Am Sonntag, den 28.09.2008, 19:34 +0200 schrieb Zrin Ziborski: Package: grub Version: 0.97-47 Severity: grave Justification: renders package unusable for many users Segmentation fault in grub-probe prevents any automated install. Only manual installation within grub shell is possible. Does `mdadm -Q --detail /dev/mdN' show a removed disk on any of your RAID? If so then this has been already fixed upstream. If not then I don't have a clue where it comes from. Would be good if you could compile a debug grub-probe from the source to get a backtrace. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#496967: general: System completely blocks any input
Hello, Am Freitag, den 29.08.2008, 19:51 +0200 schrieb Frank Küster: Since late last week, my system completely hangs - it stops accepting any input from keyboard or mouse - after 3 to 5 minutes after booting. This happens both in a text console and when running X. I should have been more specific here. It's not only the input, it's the output as well. For example, if aptitude is downloading packages in an rxvt window, the percent count stops changing as well, the display is also frozen. I noticed something similiar, with the VMware Workstation 6.5 Beta I thought this was just a bug in the beta but maybe it's somewhere in Debian. For example sometimes I just rsync a whole system to another one. and then it seems to hang like you experience it. But if I then just hide the window and unhide it again, then it get's updated once. I had to do it a few times to check if rsync was finished or not. So the system was still running it was just the graphic output in my case which wasn't updated. Any (ethernet) network also seems to stop: It no longer answers to pings, and a remote ssh login stops working, too. Hm unfortunately I don't know if in my case the network still worked or not. If it happens again for me I try to find more about it. On my native real Debian sid/experimental system I hadn't this problem yet. -- Felix Zielcke -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495049: grub-pc: does not boot because module normal is not loaded
Am Mittwoch, den 13.08.2008, 19:13 -0700 schrieb Ian Bruce: I installed grub because lilo wouldn't boot any more. My root fs is on lvm; I don't know if this is related. After running grub-install and rebooting, grub drops into the grub rescue prompt. The pc, lvm, and ext2 modules are loaded, ls finds the root volume, and the variable root is set appropriately. Only the variable root or the prefix too? Investigation shows that if the following commands are issued: insmod normal normal -- then the boot menu specified by grub.cfg appears, and the system boots properly. It turns out that the file core.img does not contain the string normal. It seems like this problem should be easy to fix. Are sure that if you boot you only type insmod normal normal and then the menu shows? i.e. nothing before like set prefix or set root? That would be very weird if GRUB set it's variables right, but still fails to load grub.cfg by it's own. [EMAIL PROTECTED]:~$ strings /boot/grub/core.img|grep normal [EMAIL PROTECTED]:~$ I think that core.img doestn't contain the string `normal' is just well normal, grub2 works fine for me, but I don't have LVM or RAID ;) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491977: grub-probe fails with Cannot find a GRUB drive for /dev/dm-N.
Am Montag, den 28.07.2008, 22:36 +0200 schrieb Moritz Naumann: Number Major Minor RaidDevice State 0 25450 active sync /dev/dm-5 1 2542- spare /dev/dm-2 debby:~# That's very strange. Normally you should have your md devices on real disks or real partitions and then using the md devices for your LVM You shouldn't do this and I even don't see a sense in there. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491977: grub-probe fails with Cannot find a GRUB drive for /dev/dm-N.
Am Sonntag, den 27.07.2008, 15:07 +0200 schrieb Moritz Naumann: Unfortunately, it doesn't work with 1.96+20080724-2 either: I just saw that PATH contains /usr/local before /usr, I always thought it would be the other way round. So please remove any old grub files lyning there around and maybe even purge grub-common comepletely and install it again. Postinst uses grub-probe in your PATH not directly /usr/sbin/grub-probe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491977: grub-probe fails with Cannot find a GRUB drive for /dev/dm-N.
Am Samstag, den 26.07.2008, 18:00 +0200 schrieb Moritz Naumann:
debby:~# dpkg-query -W -f '${Package} ${Status} ${Version}\n' grub\*
grub-common install ok installed 1.96+20080724-1
Am I missing something? Should I take additional measures before retrying?
Please see the message above in the report, The patch from Robert is in
1.96+20080724-2 not -1 which you have installed.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#488193: update-grub fails
From: Shams Fantar [EMAIL PROTECTED] /boot/grub/device.map : (hd0) /dev/hda (hd1) /dev/sda /etc/fstab : Now we know why grub thinks hd1 is your / try grub-install with --recheck if that creates device.map right else you have to change device.map manually and then update-grub works right. device.map is only created if it either doestn't exist or if you run grub-install with --recheck -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491977: grub-probe fails with Cannot find a GRUB drive for /dev/dm-N.
From: Moritz Naumann [EMAIL PROTECTED] About the md issue: The patch does not seem to fix it (assuming, after 'make install', invoking the the freshly built ./update-grub is the right way to invoke it, and I'm also calling grub-probe the right way): ./configure; make install installs everything to /usr/local not /usr and /usr is before /usr/local in PATH update-grub is just a bash script which invokes some commands In your case it still took the old grub-probe in /usr/sbin/ The best would be to use directly ./grub-probe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491977: grub-probe fails with Cannot find a GRUB drive for /dev/dm-N.
From: Moritz Naumann [EMAIL PROTECTED] debby:~/grub2-1.96+20080704# ./grub-probe -v -d /dev/dm-5 Urm sorry didn't see that you invoked it with ./ and update-grub just generates grub.cfg. grub-install uses grub-probe. grub-probe: error: Cannot find a GRUB drive for /dev/dm-5. Check your device.map Delele /boot/grub/device.map and call grub-install so that it gets regenerated. But make sure it's using the new grub-probe and not the old one from /usr -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#489426: grub-pc: patches/02_old_linux_version_comparison.diff broke update-grub
Package: grub-pc Version: 1.96+20080704-1 Severity: grave Justification: renders package unusable Just installed grub2 from incoming update-grub failed with the following: # update-grub Updating /boot/grub/grub.cfg ... [: 212: ==: unexpected operator Found linux image: basename: missing operand Try `basename --help' for more information. In /etc/grub.d/10_linux line 137 must be changed from [ `CompareVersions $a $b` == 1 ] to [ `CompareVersions $a $b` = 1 ] i.e. changing == to = -- Package-specific info: *** BEGIN /proc/mounts /dev/root / ext4dev rw,errors=remount-ro,barrier=1,data=ordered 0 0 /dev/root /dev/.static/dev ext4dev ro,errors=remount-ro,barrier=1,data=ordered 0 0 /dev/sda1 /boot ext2 rw,errors=continue 0 0 *** END /proc/mounts *** BEGIN /boot/grub/device.map (hd0) /dev/sda (hd1) /dev/sdb *** END /boot/grub/device.map -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (1, 'experimental'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-rc8 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages grub-pc depends on: ii debconf [debconf-2.0]1.5.22 Debian configuration management sy ii grub-common 1.96+20080704-1 GRand Unified Bootloader, version ii libc62.7-12 GNU C Library: Shared libraries ii liblzo2-22.03-1 data compression library ii libncurses5 5.6+20080621-2 shared libraries for terminal hand grub-pc recommends no packages. -- debconf information: grub-pc/linux_cmdline: fillme grub-pc/chainload_from_menu.lst: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#298709: chrony: just segfaults on amd64
John Hasler writes:This may actually be useful. This may actually be useful. Ok. Now i know that, too. by the way: this is my first bug report on debian bts ever :) [EMAIL PROTECTED] writes: - cd /tmp/ ; apt-get source chrony ; cd chrony-1.20 - build with DEB_BUILD_OPTIONS=nostrip dpkg-buildpackage -rfakeroot -b that worked now fine :) the other package was already self compiled but i'm not so familiar with the debian build system here now a bt and a bt full: Program received signal SIGSEGV, Segmentation fault. open_node (node=0x5280f0) at addrfilt.c:130 130 child_node-state = AS_PARENT; (gdb) bt #0 open_node (node=0x5280f0) at addrfilt.c:130 #1 0x004113d1 in set_subnet (start_node=Variable start_node is not available. ) at addrfilt.c:168 #2 0x0040585d in NCR_AddAccessRestriction (ip_addr=Variable ip_addr is not available. ) at ntp_core.c:1800 #3 0x0040c991 in CNF_SetupAccessRestrictions () at conf.c:1172 #4 0x00404552 in post_acquire_hook (anything=Variable anything is not available. ) at main.c:134 #5 0x00404883 in main (argc=0, argv=0x7fbe1ec8) at main.c:292 (gdb) bt full #0 open_node (node=0x5280f0) at addrfilt.c:130 child_node = (TableNode *) 0x0 #1 0x004113d1 in set_subnet (start_node=Variable start_node is not available. ) at addrfilt.c:168 N = Variable N is not available. (gdb) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#298709: chrony: just segfaults on amd64
as i said nothing useful but i should have made this clearer on my first post :) but now the complete gdb output except the text cut off between the ... because it's just the same as the other lines penna-deb:/tmp# gdb /usr/sbin/chronyd GNU gdb 6.3-debian Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as x86_64-linux...(no debugging symbols found) Using host libthread_db library /lib/libthread_db.so.1. (gdb) r -d Starting program: /usr/sbin/chronyd -d (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) sys_linux.c:649:(get_version_specific_details)[24-18:27:14] Initial txc.tick=1 txc.freq=0 (0.) txc.offset=0 = hz=100 shift_hz=7 sys_linux.c:665:(get_version_specific_details)[24-18:27:14] set_config_hz=0 hz=100 shift_hz=7 basic_freq_scale=1.2800 nominal_tick=1 slew_delta_tick=833 max_tick_bias=1000 sys_linux.c:703:(get_version_specific_details)[24-18:27:14] Linux kernel major=2 minor=6 patch=14 sys_linux.c:787:(get_version_specific_details)[24-18:27:14] calculated_freq_scale=0.99902439 freq_scale=0.99902439 Program received signal SIGSEGV, Segmentation fault. 0x004111e5 in ?? () (gdb) bt #0 0x004111e5 in ?? () #1 0x004113d1 in ?? () #2 0x0040585d in ?? () #3 0x0040c991 in ?? () #4 0x00404552 in ?? () #5 0x00404883 in ?? () #6 0x2ad644ba in __libc_start_main () from /lib/libc.so.6 #7 0x00401aca in ?? () #8 0x7fa72868 in ?? () #9 0x2abc29c0 in ?? () from /lib64/ld-linux-x86-64.so.2 ... #237 0x3a42475f6e653a65 in ?? () #238 0x504f5f534c006e65 in ?? () #239 0x2d2d3d534e4f4954 in ?? () #240 0x75613d726f6c6f63 in ?? () #241 0x4c0068412d206f74 in ?? () #242 0x723d454d414e474f in ?? () #243 0x5f48535300746f6f in ?? () #244 0x495443454e4e4f43 in ?? () #245 0x2e302e30313d4e4f in ?? () #246 0x3439322030312e30 in ?? () #247 0x302e302e30312032 in ?? () #248 0x752f00323220392e in ?? () #249 0x2f6e6962732f7273 in ?? () #250 0x0064796e6f726863 in ?? () #251 0x in ?? () Cannot access memory at address 0x7fa73000 (gdb) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#298709: chrony: just segfaults on amd64
Package: chrony Version: 1.20-8 Followup-For: Bug #298709 Chrony just segfaults on amd64 with that patch. Compiled with gcc 4.0.2 on testing. gdb doestn't provide anything useful if I start it with the -d option I tested it even with standard debian 2.6.8 kernel and gcc 3.4.5 (gdb) r -d Starting program: /usr/sbin/chronyd -d (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) sys_linux.c:649:(get_version_specific_details)[23-07:07:48] Initial txc.tick=1 txc.freq=0 (0.) txc.offset=0 = hz=100 shift_hz=7 sys_linux.c:665:(get_version_specific_details)[23-07:07:48] set_config_hz=0 hz=100 shift_hz=7 basic_freq_scale=1.2800 nominal_tick=1 slew_delta_tick=833 max_tick_bias=1000 sys_linux.c:703:(get_version_specific_details)[23-07:07:48] Linux kernel major=2 minor=6 patch=13 sys_linux.c:787:(get_version_specific_details)[23-07:07:48] calculated_freq_scale=0.99902439 freq_scale=0.99902439 Program received signal SIGSEGV, Segmentation fault. 0x004111e5 in ?? () (gdb) -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.13 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages chrony depends on: ii libc6 2.3.5-6GNU C Library: Shared libraries an ii libncurses5 5.4-9 Shared libraries for terminal hand ii libreadline4 4.3-17 GNU readline and history libraries chrony recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
