Bug 37692

Summary: Linux 2.6.39.x fails to boot - unable to mount root fs
Product: Platform Specific/Hardware Reporter: Dan Dart (dandart)
Component: x86-64Assignee: platform_x86_64 (platform_x86_64)
Status: CLOSED INVALID    
Severity: normal CC: florian, maciej.rutecki, rjw
Priority: P1    
Hardware: All   
OS: Linux   
Kernel Version: 2,6,39,x Subsystem:
Regression: Yes Bisected commit-id:
Bug Depends on:    
Bug Blocks: 32012    
Attachments: 2.6.39.1 .config

Description Dan Dart 2011-06-16 18:55:24 UTC 
Created attachment 62342 [details]
2.6.39.1 .config

When I start 2.6.39 or 2.6.39.1 it fails to boot with SATA messages clearly showing that partitions were detected, and "unable to mount root fs"

Demonstration:
http://www.youtube.com/watch?v=-8cTu7Xu8QE

This does not happen on 2.6.38.x

Attached .config
Comment 1 Florian Mickler 2011-06-22 08:06:10 UTC 
Can you post a diff of your 2.6.38.x config and the failing config? Also what fs do you have on your root partition and what is your kernel commandline, and what is your disk setup?
Comment 2 Dan Dart 2011-07-04 22:08:49 UTC 
Can't honestly get back to the 2.6.38.x config - but I'll keep trying. It's gone. I'm unable to do make oldconfig back to it right now, compiling it stops half way through....

My cmdline:
root=UUID=8613a5bc-0ddc-4a8d-b6bd-780faeee25e7 ro vt.handoff=7

Disks: http://pastebin.com/1bRWQhx2
Comment 3 Dan Dart 2011-07-04 22:31:48 UTC 
I keep getting a "arch/x86/kernel/entry_64.S:1544: Error: .size expression for do_hypervisor_callback does not evaluate to a constant" when I try oldconfig'ing the 2.6.39 one...
Comment 4 Florian Mickler 2011-07-05 08:23:40 UTC 
Don't know about that. Sorry.
Maybe a copy still lingers in /boot/ ?  
Or if you boot on the 2.6.38.x kernel, maybe you have it in /proc/config.gz available (If CONFIG_IKCONFIG_PROC was set at compiletime)


What filesystem do you have on your root-partition? (sorry, I'm still trying to figure out if you set up everything correctly)
Comment 5 Dan Dart 2011-07-23 15:52:55 UTC 
ext4 

The same thing happened on 3.0.
The solution was to set the root=/dev/sdb7 to /dev/sda7 in the grub config. I don't know why it decided on the wrong one. It also doesn't work with UUID like:

root=UUID=xxx-xx-xx etc..

Cheers