Bug 199034
Summary: | SATA -> Failed to set xfermode -> Kernel panic | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jerry Williams <sa84120> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-10-14 03:31:41 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
Jerry Williams
2006-07-16 05:06:19 UTC
[This comment added as part of a mass-update to all open FC4 kernel bugs] FC4 has now transitioned to the Fedora legacy project, which will continue to release security related updates for the kernel. As this bug is not security related, it is unlikely to be fixed in an update for FC4, and has been migrated to FC5. Please retest with Fedora Core 5. Thank you. Not sure if I can go to FC5 and have it work since all the newer kernels have this bug. I am going to have to see if I can boot off another device and be able to use my machine. If I upgrade to FC5 and can't boot then my machine isn't any good. I upgraded my machine to FC5 and broke it. I booted my system with linux rescue and copied over the kernel-2.6.15-1.1833_FC4.i686.rpm and installed it and it boots fine with that kernel. Can't boot with either of the FC5 kernels. I did find that I appear to be using dmraid. Booting 'Fedora Core (2.6.15-1.2054_FC5)' root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /vmlinux-2.6.15-1.2054_FC5 ro root=/dev/V0/L1 acpi=off rhgb quiet [Linux-bzImage, setup=0x1e00, size=0x16eb71] initrd /initrd-2.6.15-1.2054_FC5.img [Linux-initrd @ 0x37e3c000, 0x1b312a bytes] Uncompressing Linux... Ok, booting the kernel. Red Hat nash version 5.0.32 starting ata1: failed to set xfermode, disabled ata2: failed to set xfermode, disabled device-mapper: dm-mirror: Device lookup failure device-mapper: reload ioctl failed: No such device or address Unable to open /dev/mapper/via_jheaibjjh - unrecognised disk label. Reading all physical volumes. This may take a while... No volume groups found Unable to find volume group "V0" Unable to access resume device (/dev/V0/L0) mount: could not find filesystem '/dev/root' setuproot: moving /dev failed: No such file or directory setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init! With kernel 2.6.17-1.2187_FC5 the message is pretty much the same except for: ata1: failed to set xfermode (err_mask=0x4) ata2: failed to set xfermode (err_mask=0x4) Looks like there is something to do with dmraid. I recompiled the kernel with #define ATA_DEBUG in libata.h and when I ran it I expected it to fail, but it didn't. I am thinking that because of all of the debug info that it slowed things down enough for it to do some kind of recover to the raid information. Once that happened I can now boot from any of the newer kernels. |