Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Jan 20, 2015 at 09:45:04PM +0100, Sabrina Dubroca wrote:

> printk(KERN_ERR "fn_lookup %s %d\n", name, retval);
> 
> and I get:
> 
> [    1.618558] fn_lookup bsg/0:0:0:0 -2
> [    1.619437] fn_lookup bsg 0
> [    1.620236] fn_lookup bsg/0:0:0:0 -2
> [    1.625996] fn_lookup sda 0
> [    1.626609] fn_lookup sda 0
> [    1.639007] fn_lookup sda1 0
> [    1.639691] fn_lookup sda1 0
> [    1.643656] fn_lookup bsg/1:0:0:0 -2
> [    1.644974] fn_lookup bsg 0
> [    1.645928] fn_lookup bsg/1:0:0:0 -2
> [    1.649483] fn_lookup /dev/ram -2
> [    1.650424] fn_lookup /dev/root -2
> [    1.651234] VFS: Cannot open root device "sda1" or unknown-block(8,1): error -2

That -2 is -ENOENT...  Wait a sec, what's in filename, filename->name and
what do you get from your printk on kernel with that commit reverted?
--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Kernel]     [Linux USB Development]     [Yosemite News]     [Linux SCSI]

  Powered by Linux