bug#34162: linux-libre 4.20+ fails to mount ext4 on aarch64

2019-01-25 Thread Ludovic Courtès
Hi, Vagrant Cascadian skribis: > On 2019-01-23, Ludovic Courtès wrote: >> Vagrant Cascadian skribis: >>> After upgrading to linux-libre 4.20, and again tested with 4.20.3, an >>> aarch64 system failed to boot (using 4.19.10 worked fine): >>> >>> [3.692351] device-mapper: ioctl: 4.39.0-ioctl

bug#34162: linux-libre 4.20+ fails to mount ext4 on aarch64

2019-01-25 Thread Ludovic Courtès
Hello! Efraim Flashner skribis: > Checked the others right after I sent the previous email: > $ grep _CRC32C gnu/packages/aux-files/linux-libre/4.20-*.conf > gnu/packages/aux-files/linux-libre/4.20-arm.conf:CONFIG_CRYPTO_CRC32C=y > gnu/packages/aux-files/linux-libre/4.20-arm64.conf:CONFIG_CRYPTO

bug#34162: linux-libre 4.20+ fails to mount ext4 on aarch64

2019-01-23 Thread Mark H Weaver
Vagrant Cascadian writes: > On 2019-01-23, Mark H Weaver wrote: >> Here's a proposed (untested) patch. Would you like to test it and see >> if it eliminates the need for this workaround? > > It did, thanks! Okay, I pushed it to master, commit ff0b73028c0bbbcbf352989ed3863947357c3bce. I'm closi

bug#34162: linux-libre 4.20+ fails to mount ext4 on aarch64

2019-01-23 Thread Vagrant Cascadian
On 2019-01-23, Mark H Weaver wrote: > Vagrant Cascadian writes: > >> After upgrading to linux-libre 4.20, and again tested with 4.20.3, an >> aarch64 system failed to boot (using 4.19.10 worked fine): > > [...] > >> Workaround or fix was to add to config.scm: >> >> (initrd (append (list "crc32c_ge

bug#34162: linux-libre 4.20+ fails to mount ext4 on aarch64

2019-01-23 Thread Mark H Weaver
Hi, Vagrant Cascadian writes: > After upgrading to linux-libre 4.20, and again tested with 4.20.3, an > aarch64 system failed to boot (using 4.19.10 worked fine): [...] > Workaround or fix was to add to config.scm: > > (initrd (append (list "crc32c_generic" ... ) %base-initrd-modules)) Here's

bug#34162: linux-libre 4.20+ fails to mount ext4 on aarch64

2019-01-23 Thread Efraim Flashner
On Wed, Jan 23, 2019 at 07:54:24PM +0200, Efraim Flashner wrote: > On Wed, Jan 23, 2019 at 11:54:31AM +0100, Ludovic Courtès wrote: > > Hi Vagrant, > > > > Vagrant Cascadian skribis: > > > > > After upgrading to linux-libre 4.20, and again tested with 4.20.3, an > > > aarch64 system failed to bo

bug#34162: linux-libre 4.20+ fails to mount ext4 on aarch64

2019-01-23 Thread Efraim Flashner
On Wed, Jan 23, 2019 at 11:54:31AM +0100, Ludovic Courtès wrote: > Hi Vagrant, > > Vagrant Cascadian skribis: > > > After upgrading to linux-libre 4.20, and again tested with 4.20.3, an > > aarch64 system failed to boot (using 4.19.10 worked fine): > > > > [3.692351] device-mapper: ioctl: 4.

bug#34162: linux-libre 4.20+ fails to mount ext4 on aarch64

2019-01-23 Thread Vagrant Cascadian
On 2019-01-23, Ludovic Courtès wrote: > Vagrant Cascadian skribis: >> After upgrading to linux-libre 4.20, and again tested with 4.20.3, an >> aarch64 system failed to boot (using 4.19.10 worked fine): >> >> [3.692351] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: >> dm-de...@r

bug#34162: linux-libre 4.20+ fails to mount ext4 on aarch64

2019-01-23 Thread Ludovic Courtès
Hi Vagrant, Vagrant Cascadian skribis: > After upgrading to linux-libre 4.20, and again tested with 4.20.3, an > aarch64 system failed to boot (using 4.19.10 worked fine): > > [3.692351] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: > dm-de...@redhat.com > ext2fs_check_if_mou

bug#34162: linux-libre 4.20+ fails to mount ext4 on aarch64

2019-01-21 Thread Vagrant Cascadian
After upgrading to linux-libre 4.20, and again tested with 4.20.3, an aarch64 system failed to boot (using 4.19.10 worked fine): [3.692351] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: dm-de...@redhat.com ext2fs_check_if_mount: Can't check if filesystem is mounted due to missi