Bug 578245 - Kernel Panic - 2.6.32.10-90
Summary: Kernel Panic - 2.6.32.10-90
Keywords:
Status: CLOSED DUPLICATE of bug 578217
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-30 16:27 UTC by Francis Kong
Modified: 2010-04-05 06:47 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-04-05 06:47:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Francis Kong 2010-03-30 16:27:02 UTC
Description of problem:
After installing kernel 2.6.32.10-90 from updates, booting triggers a kernel panic.

Version-Release number of selected component (if applicable):
2.6.32.10-90.fc12.i686

How reproducible:
On the computer that has this problem, every boot triggers that kernel panic

Steps to Reproduce:
1.ensure kernel 2.6.32.10-90.fc12.i686 is installed through the official repo
2.reboot
3.
  
Actual results:
Kernel panic with the following error message in text mode:

RAMDISK: incomplete write (233 != 18264)
write error
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

Expected results:
normal boot sequence that eventually lead to runlevel 5 (as did when Kernel 2.6.32.9-70.fc12.i686 is used)

Additional info:

Same result whether I have nomodeset or not

Hardware list for the computer that reproduces the problem:
AMD Athlon XP 2000+ (Palomino)
Asus A7V133 motherboard
1.5 GB SDRAM
Highpoint rocketraid 1640 SATA Raid controller
1x WD 320GB SATA HDD
ATI Radeon x1650 (AGP) (NOT using nonfree driver)

Comment 1 Felix Schwarz 2010-04-03 20:43:27 UTC
can you check if the koji build mentioned in bug 578217 comment 8 resolves the issue?

Comment 2 Francis Kong 2010-04-05 04:08:41 UTC
The issue is resolved with that build.  Thank you very much.
P.S. As a new user if someone can set the status of this bug properly for me that would be helpful.

Comment 3 Felix Schwarz 2010-04-05 06:47:27 UTC

*** This bug has been marked as a duplicate of bug 578217 ***


Note You need to log in before you can comment on or make changes to this bug.