From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?iso-8859-2?Q?Br=FCns=2C_Stefan?= Date: Mon, 23 Jan 2017 16:38:17 +0000 Subject: [U-Boot] ext4: crash when writing a file In-Reply-To: <90bd01f1-165d-6fbb-3328-97b497c439d9@armadeus.com> References: <9c9637dd-582d-ac8a-fb71-ee5dcb8307bb@armadeus.com> <2757307.t5dS6qHjZC@sbruens-linux> <90bd01f1-165d-6fbb-3328-97b497c439d9@armadeus.com> Message-ID: <1913709.keHlVjZkVL@sbruens-linux> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Freitag, 20. Januar 2017 18:32:49 CET S?bastien Szymanski wrote: [...] > Then under the sandbox I do the following: > > U-Boot 2017.01-00002-g558e41e-dirty (Jan 20 2017 - 16:19:47 +0100) > > DRAM: 256 MiB > MMC: > Using default environment > > In: serial > Out: serial > Err: serial > SCSI: Net: No ethernet found. > IDE: Bus 0: not available > > => host bind 0 /tftproot/rootfs.raw > > => ls host 0:2 > 1024 . > 1024 .. > 16384 lost+found > 1024 var > 1024 run > 1024 root > 1024 media > 1024 mnt > 1024 tmp > 3 lib32 > 1024 usr > 1024 proc > 1024 dev > 1024 boot > 1024 sys > 3072 sbin > 3072 bin > 11 linuxrc > 1024 etc > 1024 opt > 3072 lib > > => ls host 0:2 /boot > 1024 . > 1024 .. > 26909 imx6ul-opos6uldev.dtb > 1 dtbs > 5359984 opos6ul-linux.bin > > => host load hostfs - 0 /tftproot/opos6ul-linux.bin > 5359984 bytes read in 2 ms (2.5 GiB/s) > > => printenv filesize > filesize=51c970 > > => ext4write host 0:2 0 /boot/opos6ul-linux.bin ${filesize} > File System is consistent > file found, deleting > update journal finished > File System is consistent > update journal finished > Segmentation fault As you can repeat this under sandbox, the next step would be to run sandbox under gdb, e.g.: $> gdb --args sandbox -c "host bind 0 /tftproot/rootfs.raw ; host load hostfs - 0 /tftproot/opos6ul-linux.bin ; ext4write host 0:2 0 /boot/opos6ul-linux.bin ${filesize}" Kind regards, Stefan