Bug 320571
| Summary: | Kernel 2.6.22 panic on GDT8546RZ | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Alexander Shadchnev <ashura> |
| 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: | low | ||
| Version: | 6 | CC: | jonstanley, peregrine |
| 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: | 2008-02-08 04:25: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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 427887 | ||
| Attachments: | |||
|
Description
Alexander Shadchnev
2007-10-05 17:45:33 UTC
Can you remove kernel's the "quiet" option? Edit /etc/grub.conf and remove that from the "kernel" line for the new kernel. Then boot and see what the last few lines before the panic say. Or take a picture with a digital camera and attach that. I've experienced a similar problem on my AMD64 box. Installing F7 errata kernels for 2.6.22..x all failed to boot properly. The kernel panic would come because the root LVM volume could not be found. This was because the lvm driver (from the initrd) couldn't see the SATA drive, which was because the kernel was trying to load the wrong (I think) driver (again, in initrd). It was loading the pata_amd.ko module, but I have a sil_sata on my Tyan K8W (S2875 or S2885, don't remember which off the top of my head) motherboard. When errata kernels were being installed (via yum or rpm, doesn't matter), there was an SELinux denial occuring which prevented depmod from reading the /boot/System-map-2.6.22.x-x.fc7 file. I was able to successfully install errata and boot errata kernels by placing the system in Permissive mode before running "yum update kernel" (on an otherwise freshly booted box, no other changes). I did this with the 2.6.22.9-91.fc7 kernel. I would guess that this workaround would have helped other 2.6.22.x kernels, but I have not tested that. My filesystem is on LVM, I have carved up the system into a few logical volumes, which are using either ext3 or xfs filesystems. There are no other SELinux related issues occurring. Created attachment 221171 [details]
screenshot of PC monitor when kernel panic
Created attachment 221181 [details]
screenshot of PC monitor when kernel panic
I put system in permisive mode and reboot into 2.6.22 and again kernel panic I reinstall last kernel in permisive mode and reboot intp 2.6.22 kernel panic (In reply to comment #4) > Created an attachment (id=221181) [edit] > screenshot of PC monitor when kernel panic > Still can't see the whole trace. Can you boot with the kernel option "vga=792" and capture the entire thing? This bug can possibly be avoided by booting with the option: slub_debug=- (a single minus sign.) slub_debug doesnt help Created attachment 225111 [details]
screenshot of PC monitor when kernel panic
screenshot of PC monitor when kernel panic
Created attachment 225141 [details]
screenshot of PC monitor when kernel panic
screenshot of PC monitor when kernel panic
(This is a mass-update to all current FC6 kernel bugs in NEW state) Hello, I'm reviewing this bug list 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, however this version of Fedora is no longer maintained. Please attempt to reproduce this bug with a current version of Fedora (presently Fedora 8). If the bug no longer exists, please close the bug or I'll do so in a few days if there is no further information lodged. Thanks for using Fedora! Per the previous comment in this bug, I am closing it as INSUFFICIENT_DATA, since no information has been lodged for over 30 days. Please re-open this bug or file a new one if you can provide the requested data, and thanks for filing the original report! |