Bug 374521
| Summary: | init[1] trap divide error rip:2aaaab5638a4 rsp:7fff12013730 error:0 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ashish Shukla <wahjava> |
| Component: | mkinitrd | Assignee: | Peter Jones <pjones> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 8 | CC: | gnazio, paul.lipps, steve |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2007-12-07 18:39:06 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Ashish Shukla
2007-11-10 12:31:23 UTC
Same problem here, tried both upgrading from a working f7, and with fresh install on the same box. I'm trying to install the amd64 version (I'm not willing to try i386). My grub.conf was screwed up even if I choose to update it, living only the entry for a not working f8! The funny thing is that the amd64 rescue cd boots properly and it mount my partition successfully!!! I've also tried to run yum update from the rescue environment which successfully installed, among the other, kernel-2.6.23.1-49.fc8.x86_64 (but failed again updating grub.conf! this time on adding the new entry). Anyway the result is the same. According to this http://www.redhat.com/archives/fedora-test-list/2007-October/msg01386.html it seems that this has been introduced between 7.91 and 7.92 I can confirm that. The problem has been introduced in 7.92. I have done a fresh install of 7.90 (I can't find a mirror with 7.91) and it boots regularly, while 7.92 presents the same problem. In fedoraforums there are 2 threads, one is at least 5 pages long, with people with the same problem. If someone needs more info (e.g. hardware etc.) please ask! I'll provide any info and I can do tests if needed. Hey Ashish, do you have BSD partitions in any of your HDs? Yes, I've 3 BSD sub-partitions in BSD disklabel primary partition (partition ID=165). I have a simular issue and have try to set the partition type of the FreeBSD Partition to 0x00 without any success. But what does FreeBSD partition has to do with this bug ? I'm running FreeBSD and Fedora since 2 years without any problems. Are you running FreeBSD and **Fedora 8** since 2 years? :) Look my post (#3) https://bugzilla.redhat.com/show_bug.cgi?id=374521#c3 And look also at this bug report https://bugzilla.redhat.com/show_bug.cgi?id=375591 you'll be surprised by that https://bugzilla.redhat.com/show_bug.cgi?id=375591#c21 (In reply to comment #9) > Are you running FreeBSD and **Fedora 8** since 2 years? :) I'm not mentioned any version of Fedora. > > Look my post (#3) https://bugzilla.redhat.com/show_bug.cgi?id=374521#c3 > > And look also at this bug report https://bugzilla.redhat.com/show_bug.cgi?id=375591 > you'll be surprised by that > https://bugzilla.redhat.com/show_bug.cgi?id=375591#c21 > I'd changed partition type of FreeBSD partiton from 0xa5 to 0xc but no changes. ---->8---->8---- echo Setting up hotplug. hotplug echo Creating block device nodes. mkblkdevs echo "Loading ehci-hcd.ko module" insmod /lib/ehci-hcd.ko echo "Loading ohci-hcd.ko module" insmod /lib/ohci-hcd.ko echo "Loading uhci-hcd.ko module" insmod /lib/uhci-hcd.ko mount -t usbfs /proc/bus/usb /proc/bus/usb echo "Loading mbcache.ko module" insmod /lib/mbcache.ko echo "Loading jbd.ko module" insmod /lib/jbd.ko echo "Loading ext3.ko module" insmod /lib/ext3.ko echo "Loading scsi_mod.ko module" insmod /lib/scsi_mod.ko echo "Loading sd_mod.ko module" insmod /lib/sd_mod.ko echo "Loading libata.ko module" insmod /lib/libata.ko echo "Loading ata_piix.ko module" insmod /lib/ata_piix.ko echo Waiting for driver initialization. stabilized --hash --interval 250 /proc/scsi/scsi insmod /lib/scsi_wait_scan.ko rmmod scsi_wait_scan mkblkdevs resume LABEL=SWAP-sda6 echo Creating root device. mkrootdev -t ext3 -o defaults,ro LABEL=/ echo Mounting root filesystem. mount /sysroot echo Setting up other filesystems. setuproot echo Switching to new root and running init. switchroot echo Booting has failed. sleep -1 ----8<----8<---- Above is an excerpt from 'init' (from initrd.img) on my box. it seems, nash is not able to move beyond 'mkrootdev', right... (In reply to comment #10) > (In reply to comment #9) > > Are you running FreeBSD and **Fedora 8** since 2 years? :) > > I'm not mentioned any version of Fedora. Obviously my post was ironic (I even put a smile). Sorry if you got offended, it wasn't my intention. It was just to remark the fact that this is a problem of the last Fedora release. > > https://bugzilla.redhat.com/show_bug.cgi?id=375591#c21 > > I'd changed partition type of FreeBSD partiton from 0xa5 to 0xc but no changes. If I'm not wrong this has been tried in the other bug report (or maybe by someone on fedoraforum). Did you read about the fact that if I unplug the HDs on which FreeBSD is installed, Fedora boots regularly? Maybe they want to become the dominant OS banning the other operating systems from our HDs. :) (In reply to comment #12) > (In reply to comment #10) > > (In reply to comment #9) > > > Are you running FreeBSD and **Fedora 8** since 2 years? :) > > > > I'm not mentioned any version of Fedora. > > Obviously my post was ironic (I even put a smile). > Sorry if you got offended, it wasn't my intention. No need to feel sorry, as I'm not offended :). > It was just to remark the fact that this is a problem of the last Fedora release. > > > > https://bugzilla.redhat.com/show_bug.cgi?id=375591#c21 > > > > I'd changed partition type of FreeBSD partiton from 0xa5 to 0xc but no changes. > > If I'm not wrong this has been tried in the other bug report (or maybe by > someone on fedoraforum). > > Did you read about the fact that if I unplug the HDs on which FreeBSD is > installed, Fedora boots regularly? As Fedora and FreeBSD share the same disk, so won't be able to unplug the disk. > Maybe they want to become the dominant OS banning the other operating systems > from our HDs. :) > To me, it looks like a bug in 'nash'. FWIW, I'm seeing the same problem with a AM2 Athlon64 X2 system with no non-Linux partitions on the drive. Fedora 7 runs fine on the same hardware. I can provide hardware details if it is relevant. (In reply to comment #13) > No need to feel sorry, as I'm not offended :). Great! > To me, it looks like a bug in 'nash'. Did you read this? https://bugzilla.redhat.com/show_bug.cgi?id=375591#c25 Do you think it can exclude a problem with nash and/or mkinitrd or I'm missing something? (In reply to comment #14) > FWIW, I'm seeing the same problem with a AM2 Athlon64 X2 system with no > non-Linux partitions on the drive. And is it the *only* HD on that pc? (In reply to comment #16) > (In reply to comment #14) > > FWIW, I'm seeing the same problem with a AM2 Athlon64 X2 system with no > > non-Linux partitions on the drive. > > And is it the *only* HD on that pc? When I was testing it, yes. The system does have a couple of off-board IDE controllers, but there was nothing plugged into them or any of the on-board IDE or SATA other than that one drive. *** Bug 375591 has been marked as a duplicate of this bug. *** This should solve this bug and duplicates https://bugzilla.redhat.com/show_bug.cgi?id=398281 Peter, feel free to dup to bug #398281 if that looks appropriate to you. -Eric *** This bug has been marked as a duplicate of 398281 *** |