[GIT,PULL] SOCFPGA DTS updates for 3.17
mbox

Message ID 1405397216-909-1-git-send-email-dinguyen@altera.com
State New
Headers show

Pull-request

git://git.rocketboards.org/linux-socfpga-next.git tags/socfpga_updates_for_3.17

Message

dinguyen@altera.com July 15, 2014, 4:06 a.m. UTC
Hi Arnd, Kevin and Olof,

Please consider pulling in these 2 patches for v3.17. 1 is just a defconfig
update and the other is a simple DTS fix.

Thanks,
Dinh

The following changes since commit cd3de83f147601356395b57a8673e9c5ff1e59d1:

  Linux 3.16-rc4 (2014-07-06 12:37:51 -0700)

are available in the git repository at:

  git://git.rocketboards.org/linux-socfpga-next.git tags/socfpga_updates_for_3.17

for you to fetch changes up to 7a0385c71fcec129d79ef219eebfcfce16d20417:

  ARM: socfpga: Add missing #reset-cells to socfpga device tree (2014-07-14 22:39:00 -0500)

----------------------------------------------------------------
defconfig and DTS updates for v3.17

----------------------------------------------------------------
Vince Bridgers (2):
      ARM: socfpga: Update socfpga_defconfig
      ARM: socfpga: Add missing #reset-cells to socfpga device tree

 arch/arm/boot/dts/socfpga.dtsi     |    1 +
 arch/arm/configs/socfpga_defconfig |   35 +++++++++++++++++++++++++++++++++++
 2 files changed, 36 insertions(+)

Comments

Olof Johansson July 15, 2014, 4:41 a.m. UTC | #1
Hi,



On Mon, Jul 14, 2014 at 9:06 PM,  <dinguyen@altera.com> wrote:
> Hi Arnd, Kevin and Olof,
>
> Please consider pulling in these 2 patches for v3.17. 1 is just a defconfig
> update and the other is a simple DTS fix.

They're for different topics here (one goes into next/defconfig, the
other in next/dt). It's silly to ask you to make one pull request per
patch though, so I just cherry-picked them into the two branches.

In other words: Patches have been applied, but I didn't merge the
branch. Thanks!


-Olof
Jaehoon Chung July 15, 2014, 7:29 a.m. UTC | #2
Hi Dinh.

Could you check this patch?
https://patchwork.kernel.org/patch/4529891/

Best Regards,
Jaehoon Chung

On 07/15/2014 01:06 PM, dinguyen@altera.com wrote:
> Hi Arnd, Kevin and Olof,
> 
> Please consider pulling in these 2 patches for v3.17. 1 is just a defconfig
> update and the other is a simple DTS fix.
> 
> Thanks,
> Dinh
> 
> The following changes since commit cd3de83f147601356395b57a8673e9c5ff1e59d1:
> 
>   Linux 3.16-rc4 (2014-07-06 12:37:51 -0700)
> 
> are available in the git repository at:
> 
>   git://git.rocketboards.org/linux-socfpga-next.git tags/socfpga_updates_for_3.17
> 
> for you to fetch changes up to 7a0385c71fcec129d79ef219eebfcfce16d20417:
> 
>   ARM: socfpga: Add missing #reset-cells to socfpga device tree (2014-07-14 22:39:00 -0500)
> 
> ----------------------------------------------------------------
> defconfig and DTS updates for v3.17
> 
> ----------------------------------------------------------------
> Vince Bridgers (2):
>       ARM: socfpga: Update socfpga_defconfig
>       ARM: socfpga: Add missing #reset-cells to socfpga device tree
> 
>  arch/arm/boot/dts/socfpga.dtsi     |    1 +
>  arch/arm/configs/socfpga_defconfig |   35 +++++++++++++++++++++++++++++++++++
>  2 files changed, 36 insertions(+)
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
Dinh Nguyen July 15, 2014, 3:01 p.m. UTC | #3
Hi Jaehoon,

On 07/15/2014 02:29 AM, Jaehoon Chung wrote:
> Hi Dinh.
>
> Could you check this patch?
> https://patchwork.kernel.org/patch/4529891/
>

Sorry that I missed this. I just applied it. Will test and send out an 
updated pull-request.

Dinh
Jaehoon Chung July 16, 2014, 1:34 a.m. UTC | #4
CC'd Chris/Ulf.

If you are ok, this patch will apply mmc tree.(3.16-rc5)
To prevent conflict, we want to get your opinion.

Best Regards,
Jaehoon Chung

On 07/16/2014 12:01 AM, Dinh Nguyen wrote:
> Hi Jaehoon,
> 
> On 07/15/2014 02:29 AM, Jaehoon Chung wrote:
>> Hi Dinh.
>>
>> Could you check this patch?
>> https://patchwork.kernel.org/patch/4529891/
>>
> 
> Sorry that I missed this. I just applied it. Will test and send out an updated pull-request.
> 
> Dinh
>
dinguyen@altera.com July 16, 2014, 9:05 p.m. UTC | #5
On Wed, 2014-07-16 at 10:34 +0900, Jaehoon Chung wrote:
> CC'd Chris/Ulf.
> 
> If you are ok, this patch will apply mmc tree.(3.16-rc5)
> To prevent conflict, we want to get your opinion.
> 

Oh okay...The patch looks fine to me.

Dinh
> Best Regards,
> Jaehoon Chung
> 
> On 07/16/2014 12:01 AM, Dinh Nguyen wrote:
> > Hi Jaehoon,
> > 
> > On 07/15/2014 02:29 AM, Jaehoon Chung wrote:
> >> Hi Dinh.
> >>
> >> Could you check this patch?
> >> https://patchwork.kernel.org/patch/4529891/
> >>
> > 
> > Sorry that I missed this. I just applied it. Will test and send out an updated pull-request.
> > 
> > Dinh
> > 
>
Pavel Machek Aug. 14, 2014, 6:47 p.m. UTC | #6
Hi!

I tried booting kernel based on ba36899, and got:

mmc0: new SDHC card at address b368                                             
mmcblk0: mmc0:b368 USD   7.45 GiB                                               
 mmcblk0: p1 p2 p3 p4                                                           
VFS: Cannot open root device "mmcblk0p2" or unknown-block(0,0): error
-6        
Please append a correct "root=" boot option; here are the available
partitions: 
b300         7822336 mmcblk0  driver: mmcblk                                    
  b301          102400 mmcblk0p1 00082434-01                                    
  b302         1048576 mmcblk0p2 00082434-02                                    
  b303            1024 mmcblk0p3 00082434-03                                    
  b304         6086656 mmcblk0p4 00082434-04                                    
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)  
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.16.0-11208-gef74117-dirty
#2        

IIRC it worked ok in 3.16 in similar config. It may be stupid mistake,
but if you know what I did wrong, I'd like to know... (-6 is ENXIO, so
-- how can the device be there and not be there at the same time?)

									Pavel
Dinh Nguyen Aug. 14, 2014, 8:56 p.m. UTC | #7
On 8/14/14, 1:47 PM, Pavel Machek wrote:
> Hi!
> 
> I tried booting kernel based on ba36899, and got:
> 
> mmc0: new SDHC card at address b368                                             
> mmcblk0: mmc0:b368 USD   7.45 GiB                                               
>  mmcblk0: p1 p2 p3 p4                                                           
> VFS: Cannot open root device "mmcblk0p2" or unknown-block(0,0): error
> -6        
> Please append a correct "root=" boot option; here are the available
> partitions: 
> b300         7822336 mmcblk0  driver: mmcblk                                    
>   b301          102400 mmcblk0p1 00082434-01                                    
>   b302         1048576 mmcblk0p2 00082434-02                                    
>   b303            1024 mmcblk0p3 00082434-03                                    
>   b304         6086656 mmcblk0p4 00082434-04                                    
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(0,0)  
> CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.16.0-11208-gef74117-dirty
> #2        

Hmm...today's tip-top(899552d6) and ba36899 booted just fine for me. I
noticed something, you must have commits on top of your ba36899? Mine
shows 3.16.0-11149-gba36899.

But just a thought, should one really be developing and debugging with
commits in a merge window?

Dinh
> 
> IIRC it worked ok in 3.16 in similar config. It may be stupid mistake,
> but if you know what I did wrong, I'd like to know... (-6 is ENXIO, so
> -- how can the device be there and not be there at the same time?)
> 
> 									Pavel
>
Pavel Machek Aug. 14, 2014, 9:02 p.m. UTC | #8
On Thu 2014-08-14 15:56:02, Dinh Nguyen wrote:
> 
> 
> On 8/14/14, 1:47 PM, Pavel Machek wrote:
> > Hi!
> > 
> > I tried booting kernel based on ba36899, and got:
> > 
> > mmc0: new SDHC card at address b368                                             
> > mmcblk0: mmc0:b368 USD   7.45 GiB                                               
> >  mmcblk0: p1 p2 p3 p4                                                           
> > VFS: Cannot open root device "mmcblk0p2" or unknown-block(0,0): error
> > -6        
> > Please append a correct "root=" boot option; here are the available
> > partitions: 
> > b300         7822336 mmcblk0  driver: mmcblk                                    
> >   b301          102400 mmcblk0p1 00082434-01                                    
> >   b302         1048576 mmcblk0p2 00082434-02                                    
> >   b303            1024 mmcblk0p3 00082434-03                                    
> >   b304         6086656 mmcblk0p4 00082434-04                                    
> > Kernel panic - not syncing: VFS: Unable to mount root fs on
> > unknown-block(0,0)  
> > CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.16.0-11208-gef74117-dirty
> > #2        
> 
> Hmm...today's tip-top(899552d6) and ba36899 booted just fine for me. I
> noticed something, you must have commits on top of your ba36899? Mine
> shows 3.16.0-11149-gba36899.

Ok, thanks for info. I went back to 3.16, and it worked in same
config, and went to 3.17, and it broke.

> But just a thought, should one really be developing and debugging with
> commits in a merge window?

Well, some people test -next :-). I must admit it was initially a
mistake, but it is usually good to catch bugs ASAP.

Best regards,
									Pavel
Dinh Nguyen Aug. 14, 2014, 9:25 p.m. UTC | #9
On 8/14/14, 4:02 PM, Pavel Machek wrote:
> On Thu 2014-08-14 15:56:02, Dinh Nguyen wrote:
>>
>>
>> On 8/14/14, 1:47 PM, Pavel Machek wrote:
>>> Hi!
>>>
>>> I tried booting kernel based on ba36899, and got:
>>>
>>> mmc0: new SDHC card at address b368                                             
>>> mmcblk0: mmc0:b368 USD   7.45 GiB                                               
>>>  mmcblk0: p1 p2 p3 p4                                                           
>>> VFS: Cannot open root device "mmcblk0p2" or unknown-block(0,0): error
>>> -6        
>>> Please append a correct "root=" boot option; here are the available
>>> partitions: 
>>> b300         7822336 mmcblk0  driver: mmcblk                                    
>>>   b301          102400 mmcblk0p1 00082434-01                                    
>>>   b302         1048576 mmcblk0p2 00082434-02                                    
>>>   b303            1024 mmcblk0p3 00082434-03                                    
>>>   b304         6086656 mmcblk0p4 00082434-04                                    
>>> Kernel panic - not syncing: VFS: Unable to mount root fs on
>>> unknown-block(0,0)  
>>> CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.16.0-11208-gef74117-dirty
>>> #2        
>>
>> Hmm...today's tip-top(899552d6) and ba36899 booted just fine for me. I
>> noticed something, you must have commits on top of your ba36899? Mine
>> shows 3.16.0-11149-gba36899.
> 
> Ok, thanks for info. I went back to 3.16, and it worked in same
> config, and went to 3.17, and it broke.
> 
>> But just a thought, should one really be developing and debugging with
>> commits in a merge window?
> 
> Well, some people test -next :-). I must admit it was initially a
> mistake, but it is usually good to catch bugs ASAP.
> 

I see. Just booted linux-next and it booted fine and was able to mount
/dev/mmcblk0p2 as the RFS.

Dinh
Dinh Nguyen Aug. 26, 2014, 9 p.m. UTC | #10
On Tue, Aug 26, 2014 at 6:47 AM, Pavel Machek <pavel@denx.de> wrote:
> Hi!
>
>> > > mmc0: new SDHC card at address b368
>> > > mmcblk0: mmc0:b368 USD   7.45 GiB
>> > >  mmcblk0: p1 p2 p3 p4
>> > > VFS: Cannot open root device "mmcblk0p2" or unknown-block(0,0): error
>> > > -6
>> > > Please append a correct "root=" boot option; here are the available
>> > > partitions:
>> > > b300         7822336 mmcblk0  driver: mmcblk
>> > >   b301          102400 mmcblk0p1 00082434-01
>> > >   b302         1048576 mmcblk0p2 00082434-02
>> > >   b303            1024 mmcblk0p3 00082434-03
>> > >   b304         6086656 mmcblk0p4 00082434-04
>> > > Kernel panic - not syncing: VFS: Unable to mount root fs on
>> > > unknown-block(0,0)
>> > > CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.16.0-11208-gef74117-dirty
>> > > #2
>> >
>> > Hmm...today's tip-top(899552d6) and ba36899 booted just fine for me. I
>> > noticed something, you must have commits on top of your ba36899? Mine
>> > shows 3.16.0-11149-gba36899.
>>
>> Ok, thanks for info. I went back to 3.16, and it worked in same
>> config, and went to 3.17, and it broke.
>
> The problem is still there in 3.17-rc2. 3.16 does not have the
> problem. Messages are still similar:
>
> mmc0: new high speed SDHC card at address b368
> mmcblk0: mmc0:b368 USD   7.45 GiB
>  mmcblk0: p1 p2 p3 p4
> VFS: Cannot open root device "mmcblk0p2" or unknown-block(0,0): error
> -6
> Please append a correct "root=" boot option; here are the available
> partitions:
> b300         7822336 mmcblk0  driver: mmcblk
>   b301          102400 mmcblk0p1 00082434-01
>   b302         1048576 mmcblk0p2 00082434-02
>   b303            1024 mmcblk0p3 00082434-03
>   b304         6086656 mmcblk0p4 00082434-04
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
> CPU: 0 PID: 1 Comm: swapper/0 Not tainted
> 3.17.0-rc2-00368-gec0400b-dirty #83
>
>
> What is going on there? Clearly partition table was parsed and
> partitions are available; does the mention of unknown-block(0,0) mean
> that kernel failed to parse the command line?
>
> I replaced "root=/dev/mmcblk0p2" with "root=b302" and have a booting
> system.


Can you do a bisect? 3.17-rc2 booted fine for me today:

EXT3-fs (mmcblk0p2): mounted filesystem with ordered data mode
VFS: Mounted root (ext3 filesystem) on device 179:2.
Freeing unused kernel memory: 252K (c052d000 - c056c000)
random: nonblocking pool is initialized

Poky 8.0 (Yocto Project 1.3 Reference Distro) 1.3 socfpga_cyclone5 ttyS0

socfpga_cyclone5 login: root
root@socfpga_cyclone5:~# uname -a
Linux socfpga_cyclone5 3.17.0-rc2-00006-gdd7ad78 #1 SMP Tue Aug 26
15:51:56 CDT 2014 armv7l GNU/Linux

Dinh
Pavel Machek Sept. 9, 2014, 11:49 a.m. UTC | #11
Hi!

> > The problem is still there in 3.17-rc2. 3.16 does not have the
> > problem. Messages are still similar:
> >
> > mmc0: new high speed SDHC card at address b368
> > mmcblk0: mmc0:b368 USD   7.45 GiB
> >  mmcblk0: p1 p2 p3 p4
> > VFS: Cannot open root device "mmcblk0p2" or unknown-block(0,0): error
> > -6
> > Please append a correct "root=" boot option; here are the available
> > partitions:
> > b300         7822336 mmcblk0  driver: mmcblk
> >   b301          102400 mmcblk0p1 00082434-01
> >   b302         1048576 mmcblk0p2 00082434-02
> >   b303            1024 mmcblk0p3 00082434-03
> >   b304         6086656 mmcblk0p4 00082434-04
> > Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
> > CPU: 0 PID: 1 Comm: swapper/0 Not tainted
> > 3.17.0-rc2-00368-gec0400b-dirty #83
> >
> >
> > What is going on there? Clearly partition table was parsed and
> > partitions are available; does the mention of unknown-block(0,0) mean
> > that kernel failed to parse the command line?
> >
> > I replaced "root=/dev/mmcblk0p2" with "root=b302" and have a booting
> > system.
> 
> 
> Can you do a bisect? 3.17-rc2 booted fine for me today:
> 
> EXT3-fs (mmcblk0p2): mounted filesystem with ordered data mode
> VFS: Mounted root (ext3 filesystem) on device 179:2.
> Freeing unused kernel memory: 252K (c052d000 - c056c000)
> random: nonblocking pool is initialized

Bisect would be hard... and I believe the problem is somewhere in
block layer now -- not socfpga-specific.

Best regards,
								Pavel
Russell King - ARM Linux Sept. 17, 2014, 1:20 p.m. UTC | #12
On Tue, Sep 09, 2014 at 01:49:41PM +0200, Pavel Machek wrote:
> Hi!
> 
> > > The problem is still there in 3.17-rc2. 3.16 does not have the
> > > problem. Messages are still similar:
> > >
> > > mmc0: new high speed SDHC card at address b368
> > > mmcblk0: mmc0:b368 USD   7.45 GiB
> > >  mmcblk0: p1 p2 p3 p4
> > > VFS: Cannot open root device "mmcblk0p2" or unknown-block(0,0): error
> > > -6
> > > Please append a correct "root=" boot option; here are the available
> > > partitions:
> > > b300         7822336 mmcblk0  driver: mmcblk
> > >   b301          102400 mmcblk0p1 00082434-01
> > >   b302         1048576 mmcblk0p2 00082434-02
> > >   b303            1024 mmcblk0p3 00082434-03
> > >   b304         6086656 mmcblk0p4 00082434-04
> > > Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
> > > CPU: 0 PID: 1 Comm: swapper/0 Not tainted
> > > 3.17.0-rc2-00368-gec0400b-dirty #83
> > >
> > >
> > > What is going on there? Clearly partition table was parsed and
> > > partitions are available; does the mention of unknown-block(0,0) mean
> > > that kernel failed to parse the command line?
> > >
> > > I replaced "root=/dev/mmcblk0p2" with "root=b302" and have a booting
> > > system.
> > 
> > 
> > Can you do a bisect? 3.17-rc2 booted fine for me today:
> > 
> > EXT3-fs (mmcblk0p2): mounted filesystem with ordered data mode
> > VFS: Mounted root (ext3 filesystem) on device 179:2.
> > Freeing unused kernel memory: 252K (c052d000 - c056c000)
> > random: nonblocking pool is initialized
> 
> Bisect would be hard... and I believe the problem is somewhere in
> block layer now -- not socfpga-specific.

[Adding those on the commit mentioned below to this thread.]

I just updated my nightly build system from -rc3 to -rc5, and I'm seeing
this on the LDP3430 platform (but not the SDP4430) despite both using
MMC rootfs.

On SD4430, I see:

Kernel command line: root=/dev/mmcblk0p2 rw mem=512M vmalloc=1G console=ttyO2,115200n8 rootdelay=2 debug
...
mmc0: new high speed SD card at address 0002
mmcblk0: mmc0:0002 00000 971 MiB
 mmcblk0: p1 p2
leds_pwm pwmleds: unable to request PWM for omap4:green:chrg: -517
platform pwmleds: Driver leds_pwm requests probe deferral
Waiting 2 sec before mounting root device...
mmc1: new high speed MMC card at address 0001
mmcblk1: mmc1:0001 SEM08G 7.39 GiB
mmcblk1boot0: mmc1:0001 SEM08G partition 1 1.00 MiB
mmcblk1boot1: mmc1:0001 SEM08G partition 2 1.00 MiB
 mmcblk1: unknown partition table
 mmcblk1boot1: unknown partition table
 mmcblk1boot0: unknown partition table
leds_pwm pwmleds: unable to request PWM for omap4:green:chrg: -517
platform pwmleds: Driver leds_pwm requests probe deferral
kjournald starting.  Commit interval 5 seconds
EXT3-fs (mmcblk0p2): warning: maximal mount count reached, running e2fsck is recommended
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): recovery complete
EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) on device 179:2.

However, on LDP3430:

Kernel command line: console=ttyO2,115200n8 noinitrd vmalloc=1G mem=128M root=/dev/mmcblk0p2 rw ip=none rootdelay=2 video=omap24xxfb:rotation=270
...
mmc0: host does not support reading read-only switch. assuming write-enable.
Waiting 2 sec before mounting root device...
mmc0: new high speed SD card at address 0002
mmcblk0: mmc0:0002 00000 971 MiB
 mmcblk0: p1 p2
VFS: Cannot open root device "mmcblk0p2" or unknown-block(0,0): error -6
Please append a correct "root=" boot option; here are the available partitions:
b300          994816 mmcblk0  driver: mmcblk
  b301           72261 mmcblk0p1 0b4c6c45-01
  b302          915705 mmcblk0p2 0b4c6c45-02
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

I think the problem may be 4dfe694f616e00e6fd83e5bbcd7a3c4d7113493d
("init: make rootdelay=N consistent with rootwait behaviour") which
was merged during the recent window.  This moved the delay after the
saved_root_name[] handling.  As we can see in the SDP4430 case, the
order was:

 - mmcblk0p2 detected
 - delay message
 - rootfs failure

and everything worked.  However, in the LDP3430 case:

 - delay message
 - mmcblk0p2 detected
 - rootfs failure

and it failed.  If we look at the code as it stands today:

        if (saved_root_name[0]) {
                root_device_name = saved_root_name;
                if (!strncmp(root_device_name, "mtd", 3) ||
                    !strncmp(root_device_name, "ubi", 3)) {
                        mount_block_root(root_device_name, root_mountflags);
                        goto out;
                }
                ROOT_DEV = name_to_dev_t(root_device_name);
                if (strncmp(root_device_name, "/dev/", 5) == 0)
                        root_device_name += 5;
        }

This tries to look up the root device name and translate to a dev_t.
We know that "mmcblk0p2" doesn't exist at this point, so ROOT_DEV is
zero here.

        if (initrd_load())
                goto out;

        if (root_delay) {
                pr_info("Waiting %d sec before mounting root device...\n",
                        root_delay);
                ssleep(root_delay);
        }

Here's our delay.

        /* wait for any asynchronous scanning to complete */
        if ((ROOT_DEV == 0) && root_wait) {
                printk(KERN_INFO "Waiting for root device %s...\n",
                        saved_root_name);
                while (driver_probe_done() != 0 ||
                        (ROOT_DEV = name_to_dev_t(saved_root_name)) == 0)
                        msleep(100);
                async_synchronize_full();
        }

If ROOT_DEV was still zero, and root_wait was set (it isn't) we'd then
try to re-evaluate ROOT_DEV.  ROOT_DEV must be set to mount the rootfs,
and we can see from the above failure messages that it was still zero.
That works out, because this code would never be run with root_wait=false.

The reason it used to work is because the delay came _before_ the first
"if" above, so causing the first ROOT_DEV lookup to succeed.

I think it may be better to move the root_delay handling either immediately
after md_run_setup(), or we need to re-lookup ROOT_DEV after the delay.
Paul, any thoughts?
Paul Gortmaker Sept. 17, 2014, 2:25 p.m. UTC | #13
[Re: 3.17-rc2: root=/dev/mmcblk0p2 command line parsing fails] On 17/09/2014 (Wed 14:20) Russell King - ARM Linux wrote:

[...]

> I think the problem may be 4dfe694f616e00e6fd83e5bbcd7a3c4d7113493d
> ("init: make rootdelay=N consistent with rootwait behaviour") which
> was merged during the recent window.  This moved the delay after the
> saved_root_name[] handling.  As we can see in the SDP4430 case, the
> order was:

[...]

> 
> 
> If ROOT_DEV was still zero, and root_wait was set (it isn't) we'd then
> try to re-evaluate ROOT_DEV.  ROOT_DEV must be set to mount the rootfs,
> and we can see from the above failure messages that it was still zero.
> That works out, because this code would never be run with root_wait=false.
> 
> The reason it used to work is because the delay came _before_ the first
> "if" above, so causing the first ROOT_DEV lookup to succeed.
> 
> I think it may be better to move the root_delay handling either immediately
> after md_run_setup(), or we need to re-lookup ROOT_DEV after the delay.
> Paul, any thoughts?

After discussing it more on irc, it seems like moving the delay/wait
handling after md_run_setup [i.e. to the original location of delay vs.
the original location of wait] is probably best.

But, given as the original commit log indicated -- there may be a risk
of other corner cases subtly being broken by such a change, it is
probably best if we just revert the original now, and then try again in
the alternate location in the next dev cycle.  I'll send a revert
shortly.

Thanks for diagnosing this.
Paul.
--

> 
> -- 
> FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
> according to speedtest.net.
Pavel Machek Sept. 18, 2014, 1:17 p.m. UTC | #14
On Wed 2014-09-17 10:57:45, Paul Gortmaker wrote:
> This reverts commit 4dfe694f616e00e6fd83e5bbcd7a3c4d7113493d.

This solves my problems, thanks.

Tested-by: Pavel Machek <pavel@denx.de>

									Pavel
Pavel Machek April 9, 2015, 9:42 a.m. UTC | #15
On Thu 2014-09-18 15:17:16, Pavel Machek wrote:
> On Wed 2014-09-17 10:57:45, Paul Gortmaker wrote:
> > This reverts commit 4dfe694f616e00e6fd83e5bbcd7a3c4d7113493d.
> 
> This solves my problems, thanks.

Weird. It seems this regression is back in 4.0-rc7?

root=0xb302 works, root=/dev/mmcblk0p2 does not. socfpga board.
									Pavel