Active Topics

 



Notices


Reply
Thread Tools
filip.pz's Avatar
Posts: 108 | Thanked: 578 times | Joined on Feb 2013 @ Požega, Croatia
#21
Originally Posted by wicket View Post
It looks like switch_root is being called with incompatible arguments, probably due to the previous mount errors.

Make sure you have CONFIG_BLK_DEV_LOOP enabled. That should hopefully fix the /dev/loop0 errors.
CONFIG_BLK_DEV_LOOP is set to y.

Here's boot with 4.3.0-rc1: http://pastie.org/pastes/10433203
Seems that mmc driver is having some DMA trouble:
omap_hsmmc 480b4000.mmc: unable to obtain RX DMA engine channel 3230369304

I'm guessing that needs to be taken care of first of all.

Last edited by filip.pz; 2015-09-20 at 10:50.
 

The Following 2 Users Say Thank You to filip.pz For This Useful Post:
filip.pz's Avatar
Posts: 108 | Thanked: 578 times | Joined on Feb 2013 @ Požega, Croatia
#22
OK, mmc issue sorted out by adding
CONFIG_DMADEVICES=y
CONFIG_DMA_OMAP=y

This time Nemo does get started, but dies soon after (http://pastie.org/10433263). I guess watchdog shuts it off before DSME is able to start and prevent that.

Anyway - I now have a working serial console cable, and we have kernel that kinda boots. I hope to make some more progress in the following days (time permitting).
 

The Following 4 Users Say Thank You to filip.pz For This Useful Post:
Posts: 3,296 | Thanked: 4,325 times | Joined on May 2011 @ Poland
#23
The first error I noticed was

Code:
mount: mounting /dev/mmcblk0p1 on /mnt/base failed: No such file or directory
It seems as though the kernel didn't find the right partition.
Would it be possible to dump the partition table before booting? I can't really do it myself now, but you may post a question on unix.stackexchange.com
__________________
If you want to support my work, you can donate by PayPal or Flattr

Projects no longer actively developed: here
 

The Following User Says Thank You to marmistrz For This Useful Post:
filip.pz's Avatar
Posts: 108 | Thanked: 578 times | Joined on Feb 2013 @ Požega, Croatia
#24
Originally Posted by marmistrz View Post
The first error I noticed was

Code:
mount: mounting /dev/mmcblk0p1 on /mnt/base failed: No such file or directory
It seems as though the kernel didn't find the right partition.
That problem has been solved, as described in my last post:

Originally Posted by filip.pz View Post
OK, mmc issue sorted out by adding
CONFIG_DMADEVICES=y
CONFIG_DMA_OMAP=y
Seems that MMC driver works only with DMA enabled.

I've also captured boot of 3.5.3 kernel for reference (http://pastie.org/10433952).

I think that this is the one to solve next:
Code:
watchdog watchdog0: watchdog did not stop!
 

The Following 2 Users Say Thank You to filip.pz For This Useful Post:
Posts: 1,189 | Thanked: 4,019 times | Joined on Oct 2014
#25
Originally Posted by filip.pz View Post
I think that this is the one to solve next:
Code:
watchdog watchdog0: watchdog did not stop!
This is just a warning, that some service didn't stop within a given timeout. You will find that even in normal log iam sure.
__________________
You can still support my work by donation - click here

ETH: 0xFcD031609DB739C62730589361940C68ceEbC913
 

The Following User Says Thank You to nieldk For This Useful Post:
filip.pz's Avatar
Posts: 108 | Thanked: 578 times | Joined on Feb 2013 @ Požega, Croatia
#26
Originally Posted by nieldk View Post
This is just a warning, that some service didn't stop within a given timeout. You will find that even in normal log iam sure.
It's not present when booting 3.5.3. I'd expect for kernel to kick the watchdog just before init, so it doesn't time out. Seems to me that's just the case here.

Last edited by filip.pz; 2015-09-20 at 17:36.
 

The Following User Says Thank You to filip.pz For This Useful Post:
Posts: 1,189 | Thanked: 4,019 times | Joined on Oct 2014
#27
Originally Posted by filip.pz View Post
It's not present when booting 3.5.3. I'd expect for kernel to kick the watchdog just before init, so it doesn't time out. Seems to me that just the case here.
Possibly its related to the systemd errors. While annoying, I don't think its a stopper.

But, what about the unknown partition table listed?

Code:
 213   2.520324  mmcblk0boot1: unknown partition table
__________________
You can still support my work by donation - click here

ETH: 0xFcD031609DB739C62730589361940C68ceEbC913
 

The Following User Says Thank You to nieldk For This Useful Post:
filip.pz's Avatar
Posts: 108 | Thanked: 578 times | Joined on Feb 2013 @ Požega, Croatia
#28
Originally Posted by nieldk View Post
Possibly its related to the systemd errors. While annoying, I don't think its a stopper.
This seems to be related:
https://github.com/filippz/kernel-ad...030_wdt.c#L235
I'll try to implement this into new kernel and see
 

The Following 2 Users Say Thank You to filip.pz For This Useful Post:
wicket's Avatar
Posts: 576 | Thanked: 2,888 times | Joined on May 2010 @ Colombia
#29
The N900 which also uses twl4030_wdt, doesn't need that hack. Check that you are not doing anything differently. Here's the latest N900 config file which you might find useful for reference given the hardware similarities:

https://github.com/pali/linux-n900/b...rx51_defconfig
__________________
DebiaN900 - Native Debian on the N900. Deprecated in favour of Maemo Leste.

Mobile devices with mainline Linux support - Help needed with documentation.

"Those who do not understand Unix are condemned to reinvent it, poorly." - Henry Spencer
 

The Following User Says Thank You to wicket For This Useful Post:
filip.pz's Avatar
Posts: 108 | Thanked: 578 times | Joined on Feb 2013 @ Požega, Croatia
#30
Originally Posted by wicket View Post
The N900 which also uses twl4030_wdt, doesn't need that hack. Check that you are not doing anything differently.
In fact N9 uses TWL5031, but the driver is the same. Both 2.6 and 3.5 had some kind of WD hacks:
https://github.com/filippz/kernel-ad...030_wdt_hack.c
https://github.com/filippz/kernel-ad...514acf4db038b0

The one from 3.5.3 seem to help a bit, ie boots a bit further.

Originally Posted by wicket View Post
Here's the latest N900 config file which you might find useful for reference given the hardware similarities:

https://github.com/pali/linux-n900/b...rx51_defconfig
Only difference I see is that CONFIG_OMAP_WATCHDOG and CONFIG_TWL4030_WATCHDOG are set to m whereas I used y. I'll retest with that, but not until tomorrow.
 

The Following 3 Users Say Thank You to filip.pz For This Useful Post:
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 03:52.