Bug 280871
Summary: | crash on AMD with 2.6.22.4-65 kernel | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Rob Ristroph <rgristroph> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7 | CC: | chris.brown |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | athlon | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-01-13 23:01:20 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
Rob Ristroph
2007-09-06 16:28:20 UTC
Is the package e2fsprogs-libs installed? If not, install it. Then make sure the mkinitrd package is current, and uninstall/reinstall the latest 2.6.22 kernel. (Or rebuild the initrd if you know how to use mkinitrd.) I checked that e2fsprogs-libs was installed, and also removed and re-installed the newer kernel. It made no difference. However, I have learned that this hardware has a history of problems. Currently on the PCI cards in it doesn't work on some boots, until you rmmod and modprobe the driver to reload it. It once suffered a power outage that killed the on-board ethernet, and was moved recently because someone claimed the video would not work through a KVM switch, only directly connected to the monitor. In short, perhaps nothing should be done with this bug report until someone else can confrim it on different hardware ? Sorry for false alarm (at least I hope it is) Hello Rob, I'm reviewing this bug as part of the kernel bug triage project, an attempt to isolate current bugs in the fedora kernel. http://fedoraproject.org/wiki/KernelBugTriage I am CC'ing myself to this bug and will try and assist you in resolving it if I can. I would first attempt what Chuck suggests - this could be resolved by updating to the latest kernel (I appreciate you have already done this once but running the latest stable wont hurt) and if this does not resolve the issue then could you run: rpm -qa | grep -i mkinitrd and post back the output. If you're willing and able you could also run the following on a working and a failing initrd image under /boot: mkdir ~/bad-initrd cd ~/bad-initrd/ gzip -dc /boot/initrd-bad-kernel-version.img | cpio -id mkdir ~/good-initrd cd ~/good-initrd/ gzip -dc /boot/initrd-good-kernel-version.img | cpio -id obviously replacing the initrd-bad-kernel-version.img and initrd-good-kernel-version.img with the appropriate values. The run: diff -u ~/bad-initrd/init ~/good-initrd/init > ~/init-diff.txt and attach init-diff.txt as text/plain attachment to this bug. Only do this if you feel comfortable with it. Alternatively, you can send both init images to me directly with this bug number as the subject. Cheers Chris As indicated previously there has been no update on the progress of this bug therefore I am closing it as INSUFFICIENT_DATA. Please re-open if the issue still occurs for you and I will try to assist in its resolution. Thank you for taking the time to report the initial bug. |