From mboxrd@z Thu Jan  1 00:00:00 1970
From: U.Mutlu <for-gmane@mutluit.com>
Date: Wed, 10 Apr 2019 00:54:22 +0200
Subject: [U-Boot] Possible bug in release: fdisk in linux cannot read
 /dev/mmcblk0 anymore
In-Reply-To: <5CAD1E9A.6020200@mutluit.com>
References: <5CAD1E9A.6020200@mutluit.com>
Message-ID: <5CAD229E.2060801@mutluit.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Sorry, seems to be a false alert.

After rebuilding u-boot it works fine again.


U.Mutlu wrote on 04/10/2019 12:37 AM:
> Hi folks,
>
> # U-Boot 2019.04 Configuration
>
> I just updated to the latest version via git.
> My previous version was the recent 2019.04-rc4.
>
> Now in this latest version I think a bug shows up:
>
> Inside Linux on the device, suddenly the following command no longer works:
>
> # fdisk -l /dev/mmcblk0
> fdisk: cannot open /dev/mmcblk0: Input/output error
>
> # ls -l /dev/mmcblk0
> brw-rw---- 1 root disk 179, 0 Jan  1  1970 /dev/mmcblk0
>
> The device is present, but fdisk cannot read the partitions,
> although u-boot has successfully used the boot partition
> of this SD card to boot Linux.
> IMHO a funny situation, isn't it? :-)
>
> This always had worked for me, up until now.
> Is this more a linux issue or a u-boot issue?
>
> Let me know if you need specific data.
>
> Thx