kernel panic with latest kirkwood 3.9 update

[replabrobin]

Moonman, I will try a full boot of the two kernels and their associated modules this evening; it's a bit hard while I am at work. I will need to try and figure out exactly what I need to change in my boot code to make the different images work.

[moonman]

If it works, it will boot after you upgrade from 3.8.x to the patched 3.9.x. I already committed all the changes.
If mmc shows up in dev it should work. The new 3.9.3 will have the patch included (probably tomorrow when its built).

[replabrobin]

Moonman, I managed to get some time before leaving and did a test of the third case ie the kernel with one patch applied. So far as I can tell that one worked fine and booted as 3.9.2-1 with my SD card as /boot and /.

I will test the other around 8pm tonight (BST).

[replabrobin]

Moonman, I have just booted the second of your kernels ie 1 patch revrted + 1 applied and that also boots fine with its modules and sees my SD card fine.

[moonman]

seems they merged the wrong patch into mainline. They were deciding between the two. It was supposed to fix this exact problem, and it doesn't obviously.

3.9.3 is in the repo now. Thanks for testing!

[replabrobin]

Moonman, kudos for the fast resolution & fix. I upgraded today to 3.9.3-1 and all is well. Thanks.

[ThisIsAandomString]

Weirdly, from 3.9 on, on eSata Sheevaplug the kernel doesn't work properly, as it detects the SD card as read only.

$this->bbcode_second_pass_code('', '[ 0.000000] Kernel command line: console=ttyS0,115200 ro root=/dev/mmcblk0p3 rootdelay=1 init=/bin/systemd
[ 15.269103] mmc0: mvsdio driver initialized, using GPIO 47 for card detection
[ 15.310960] mmc0: new high speed SDHC card at address b368
[ 15.311273] mmcblk0: mmc0:b368 SDC 30.2 GiB (ro)
[ 15.313291] mmcblk0: p1 p2 p3
[ 16.280391] EXT3-fs (mmcblk0p3): error: couldn't mount because of unsupported optional features (40)
[ 16.290533] EXT2-fs (mmcblk0p3): error: couldn't mount because of unsupported optional features (40)
[ 16.314464] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null)
[ 17.951579] systemd[1]: Expecting device dev-mmcblk0p1.device...
')

If I fall back to 3.7.3 it's detected as rw as it should (can test other kernels, my cache is plenty).

Best regards.

[pepedog]

I bet the ro comes from uboot bootargs. Can you not put a remount in fstab?

[ThisIsAandomString]

No, remount complains about device being write protected. If I pass rw instead of ro as bootargs it panics as root cannot be mounted.

[moonman]

Can you try "1 patch revrted + 1 applied" on the previous page?