GNU GRUB - Bugs: bug #25614, Floating-point exception in...
You are not allowed to post comments on this tracker with your current authentication level.
bug #25614: Floating-point exception in grub-install
Submitter: | David Abrahams <bewst> | ||
Submitted: | Tue 17 Feb 2009 07:49:12 PM UTC | ||
Category: | None | Severity: | Major |
Priority: | 5 - Normal | Item Group: | Software Error |
Status: | Fixed | Privacy: | Public |
Assigned to: | None | Originator Name: | |
Open/Closed: | Closed | Release: | Bazaar - trunk |
Release: | svn-1996 | Reproducibility: | Every Time |
Planned Release: | None |
Mon 04 Apr 2011 12:05:20 AM UTC, comment #4: |
Vladimir Serbinenko <phcoder> |
Wed 18 Feb 2009 07:03:15 AM UTC, comment #3: I've attached that info for both my RAID arrays |
David Abrahams <bewst> |
Tue 17 Feb 2009 09:48:08 PM UTC, comment #2: I'll tell you as soon as I recover bootability. However, you should know that md0 (RAID1) has three devices while md1 (RAID6) has eight. The array in question here sure appears to be md1, at least to me. I think I got you a great deal of information in the debugger output there, if you comb through it. |
David Abrahams <bewst> |
Tue 17 Feb 2009 09:14:33 PM UTC, comment #1: what does `mdadm -Q --detail /dev/md0' say about your raid? |
Felix Zielcke <fzielcke> |
Tue 17 Feb 2009 07:49:12 PM UTC, original submission:
This is with my attempted port to ubuntu package; I haven't tried the raw source.
|
David Abrahams <bewst> |
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 4 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2011-04-04 | phcoder | Status | None | Fixed | |
Open/Closed | Open | Closed | |||
Release | None | Bazaar - trunk | |||
2009-02-18 | bewst | Attached File | - | Added md.log, #17472 |
Powered by Savane 3.13-d3ae.
Corresponding source code
Reading through backtrace I've noticed the cause:
#11 0x000000000041aab4 in grub_raid_scan_device (head_only=<value optimized out>) at /home/dave/src/grub2/grub2-1.97+svn1996/disk/raid.c:641
#12 0x000000000041c14d in grub_fini_all () at grub_setup_init.c:73
In other words a rescan happened after some subsystems were finalised. In particular lvm_fini was called after mdraid_fini. I've checked and it's no longer the case. Closing