Bug 196360 (fc6-cciss)

Summary: Kernel panic on cciss caused by nash change in mkinitrd
Product: [Fedora] Fedora Reporter: Robert Scheck <redhat-bugzilla>
Component: mkinitrdAssignee: Peter Jones <pjones>
Status: CLOSED RAWHIDE QA Contact: David Lawrence <dkl>
Severity: high Docs Contact:
Priority: medium    
Version: rawhideCC: bpeck, herbert, robert.scheck, tibyke, ygelfand
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-09-28 16:08:49 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: 150224    
Attachments:
Description Flags
Screenshot via remote management chip
none
Diff between working and non-working code to locate the problem none

Description Robert Scheck 2006-06-22 19:14:50 UTC
Description of problem:
Your last change in nash/lib.c made mkinitrd absolutely unusable for cciss 
devices (which means HP Smart Arrays). Every initrd created with mkinitrd after
your last change to nash/lib.c change will result everytime in a kernel panic...

Version-Release number of selected component (if applicable):
mkinitrd-5.0.43

How reproducible:
Everytime, just install a kernel package when you've got a cciss/HP Smart Array 
system and try to boot it.

Actual results:
Kernel panic on cciss caused by nash change in mkinitrd :-(

Expected results:
Would be very nice, if you could fix your broken code very soon ;-)

Additional info:
I'm able to provide any filesystem & path information and system outputs - as 
long as I don't have to reboot the machine for, sorry.

Comment 1 Robert Scheck 2006-06-22 19:16:54 UTC
Created attachment 131376 [details]
Screenshot via remote management chip

Comment 2 Robert Scheck 2006-06-22 19:21:01 UTC
Created attachment 131377 [details]
Diff between working and non-working code to locate the problem

mkinitrd-5.0.43/nash/lib.c contains the broken code causing this bug report,
code from mkinitrd-5.0.32/nash/lib.c is working very well - have a lot of fun
when fixing this... ;-)

Comment 3 Robert Scheck 2006-07-19 20:49:24 UTC
Ping? IMHO this is a regression and should be a FC6Blocker...

Comment 4 Peter Jones 2006-08-01 20:25:50 UTC
*** Bug 200542 has been marked as a duplicate of this bug. ***

Comment 5 Peter Jones 2006-08-16 21:12:10 UTC
*** Bug 201746 has been marked as a duplicate of this bug. ***

Comment 6 Peter Jones 2006-08-16 21:28:49 UTC
*** Bug 188197 has been marked as a duplicate of this bug. ***

Comment 7 Peter Jones 2006-09-13 20:20:36 UTC
Currently this works for me -- are you still seeing it?

Comment 8 Robert Scheck 2006-09-23 15:23:00 UTC
Did you try both,

  kernel /vmlinuz ro root=LABEL=/

and e.g.

  kernel /vmlinuz ro root=/dev/cciss/c0d0p1

because normally one of these always was broken. And It would be easier to me if 
you could provide a (unified) diff of the relevant part which (sh|c)ould solve 
the problem.

Comment 9 tibyke 2006-09-24 08:18:48 UTC
yeah, Robert is right, LABEL=/ works, but /dev/cciss/whatever just causes a
kernel panic.

Comment 10 Peter Jones 2006-09-28 16:08:49 UTC
Should work in mkinitrd-5.1.19-1 .