[IMAGE] A13(-WIFI) Debian (now Ubuntu) + xfce flashable (Updated: 08 Mar: R18)

jwischka · July 13, 2013, 03:11:44 PM

Quote from: SlyCom on July 13, 2013, 10:50:27 AM
No error messages. I've got "usb 2-1.2.2: new full-speed USB device number 7 using sw-ehci" and no ttUSB available in /dev

Hmm... not sure what to tell you. Which version are you using?

SlyCom · July 14, 2013, 11:26:14 PM

I'm using the latest one.
The USB -> Serial FTDI converter is recognised correctly but not CP210x drivers.

jwischka · July 14, 2013, 11:26:59 PM

I'll check and see if it's enabled in the kernel.

SlyCom · July 15, 2013, 09:41:31 AM

Thank you. If its disabled, do I need to recompile the Kernel??

jwischka · July 15, 2013, 08:29:21 PM

Try this image. R19 Beta 2

SlyCom · July 23, 2013, 11:41:05 AM

It stops:
[ 2.630000] Kernel panic - not syncing: Attempted to kill init!
[ 2.630000] [<c003e204>] (unwind_backtrace+0x0/0x138) from [<c05a5c2c>] (panic+0x6c/0x18c)
[ 2.640000] [<c05a5c2c>] (panic+0x6c/0x18c) from [<c0067f14>] (do_exit+0x6ec/0x720)
[ 2.650000] [<c0067f14>] (do_exit+0x6ec/0x720) from [<c003c1a4>] (die+0x260/0x2b8)
[ 2.660000] [<c003c1a4>] (die+0x260/0x2b8) from [<c0042758>] (__do_kernel_fault+0x74/0x84)
[ 2.670000] [<c0042758>] (__do_kernel_fault+0x74/0x84) from [<c00428f4>] (do_page_fault+0x18c/0x2ec)
[ 2.680000] [<c00428f4>] (do_page_fault+0x18c/0x2ec) from [<c003121c>] (do_DataAbort+0x34/0x9c)
[ 2.680000] [<c003121c>] (do_DataAbort+0x34/0x9c) from [<c0037950>] (__dabt_svc+0x70/0xa0)
[ 2.690000] Exception stack(0xdf83bf50 to 0xdf83bf98)
[ 2.700000] bf40: ffffffed 00000001 00000000 00000000
[ 2.710000] bf60: ffffffed c002bc08 df83a000 00000000 c000e8c4 00000000 00000000 00000000
[ 2.710000] bf80: c0842354 df83bf98 c000e98c c02e9a00 a0000013 ffffffff
[ 2.720000] [<c0037950>] (__dabt_svc+0x70/0xa0) from [<c02e9a00>] (regulator_get_voltage+0x8/0x34)
[ 2.730000] [<c02e9a00>] (regulator_get_voltage+0x8/0x34) from [<c000e98c>] (sun4i_cpufreq_initcall+0xc8/0x124)
[ 2.740000] [<c000e98c>] (sun4i_cpufreq_initcall+0xc8/0x124) from [<c0031464>] (do_one_initcall+0x34/0x17c)
[ 2.750000] [<c0031464>] (do_one_initcall+0x34/0x17c) from [<c0008a18>] (kernel_init+0xc8/0x158)
[ 2.760000] [<c0008a18>] (kernel_init+0xc8/0x158) from [<c0038edc>] (kernel_thread_exit+0x0/0x8)
[ 2.780000] [mmc]: mmc 0 detect change, present 1

jwischka · July 23, 2013, 02:54:44 PM

This is going to sound silly, but pop the card, out and back in, and power cycle the board.

Quote from: SlyCom on July 23, 2013, 11:41:05 AM
It stops:
[ 2.630000] Kernel panic - not syncing: Attempted to kill init!
[ 2.630000] [<c003e204>] (unwind_backtrace+0x0/0x138) from [<c05a5c2c>] (panic+0x6c/0x18c)
[ 2.640000] [<c05a5c2c>] (panic+0x6c/0x18c) from [<c0067f14>] (do_exit+0x6ec/0x720)
[ 2.650000] [<c0067f14>] (do_exit+0x6ec/0x720) from [<c003c1a4>] (die+0x260/0x2b8)
[ 2.660000] [<c003c1a4>] (die+0x260/0x2b8) from [<c0042758>] (__do_kernel_fault+0x74/0x84)
[ 2.670000] [<c0042758>] (__do_kernel_fault+0x74/0x84) from [<c00428f4>] (do_page_fault+0x18c/0x2ec)
[ 2.680000] [<c00428f4>] (do_page_fault+0x18c/0x2ec) from [<c003121c>] (do_DataAbort+0x34/0x9c)
[ 2.680000] [<c003121c>] (do_DataAbort+0x34/0x9c) from [<c0037950>] (__dabt_svc+0x70/0xa0)
[ 2.690000] Exception stack(0xdf83bf50 to 0xdf83bf98)
[ 2.700000] bf40: ffffffed 00000001 00000000 00000000
[ 2.710000] bf60: ffffffed c002bc08 df83a000 00000000 c000e8c4 00000000 00000000 00000000
[ 2.710000] bf80: c0842354 df83bf98 c000e98c c02e9a00 a0000013 ffffffff
[ 2.720000] [<c0037950>] (__dabt_svc+0x70/0xa0) from [<c02e9a00>] (regulator_get_voltage+0x8/0x34)
[ 2.730000] [<c02e9a00>] (regulator_get_voltage+0x8/0x34) from [<c000e98c>] (sun4i_cpufreq_initcall+0xc8/0x124)
[ 2.740000] [<c000e98c>] (sun4i_cpufreq_initcall+0xc8/0x124) from [<c0031464>] (do_one_initcall+0x34/0x17c)
[ 2.750000] [<c0031464>] (do_one_initcall+0x34/0x17c) from [<c0008a18>] (kernel_init+0xc8/0x158)
[ 2.760000] [<c0008a18>] (kernel_init+0xc8/0x158) from [<c0038edc>] (kernel_thread_exit+0x0/0x8)
[ 2.780000] [mmc]: mmc 0 detect change, present 1

Ekkehard · July 26, 2013, 07:23:29 PM

This little thing is quite amazing - running apache, php, and quite a bit of my code connecting it to other machines via sockets and all (running R18). So I'm almost done

But here is something that puzzles me: Just looked at my syslog to find out why cron isn't working, and I found it is getting filled with lines of the form

Code Select


Jul 25 06:27:44 olinuxino kernel: [2205272.270000] init: openvt main process ended, respawning
Jul 25 06:28:44 olinuxino kernel: [2205332.990000] init: openvt main process ended, respawning
Jul 25 06:29:45 olinuxino kernel: [2205393.700000] init: openvt main process ended, respawning

So every minute openvt fails. Not only does that clutter syslog quite a bit, something ain't quite right. Anybody having the same issue? Anybody knows what causes it? Anybody knows how to fix it?

There is some chatter on the net regarding Linaro and this symptom, but all connected to some upstart jobs - not something that happens every minute. It being there every minute could mean it is cron-related (which runs every minute and is also in upstart).

Ekkehard · July 27, 2013, 12:10:41 AM

Now I know why cron wasn't working - not sure that this is related to the other problem though.

cron is working - kind of - but it is using GMT instead of the local time. That is definitely a bug. What goes into crontab files should be local time, not GMT. Other than using the wrong time, cron is working very reliably as usual.

Anybody knows how to fix this, i.e. where to start looking? @jwischka any ideas?

BTW, the "date" command shows the local time as expected - not GMT.

jwischka · July 27, 2013, 12:18:31 AM

Quote from: Ekkehard on July 27, 2013, 12:10:41 AM
Now I know why cron wasn't working - not sure that this is related to the other problem though.

cron is working - kind of - but it is using GMT instead of the local time. That is definitely a bug. What goes into crontab files should be local time, not GMT. Other than using the wrong time, cron is working very reliably as usual.

Anybody knows how to fix this, i.e. where to start looking? @jwischka any ideas?

BTW, the "date" command shows the local time as expected - not GMT.

Which image are you on?

Ekkehard · July 27, 2013, 12:21:06 AM

R18

jwischka · July 27, 2013, 01:14:19 AM

Quote from: Ekkehard on July 27, 2013, 12:21:06 AM
R18

Can you try with R19 beta 2 and see if it is still there?

Ekkehard · July 27, 2013, 01:49:17 AM

will do - but it will take me a little while before I have my stuff set up again

jwischka · July 27, 2013, 02:20:20 AM

Quote from: Ekkehard on July 27, 2013, 01:49:17 AM
will do - but it will take me a little while before I have my stuff set up again

Ok - The main reason I ask is because the entire rootfs has changed between the two versions, meaning that the bug may have already been fixed. Let me know if not and I'll look into it.

Ekkehard · July 27, 2013, 05:33:24 AM

OK - tried it out - same result using R19 beta...

However, I found the problem - it was mine!! I had used tzselect to select the time zone, which works fine but not system wide. So cron does not know about my local time zone changes, even though I put the setting of the TZ variable into /etc/profile. I should have used

Code Select


sudo dpkg-reconfigure tzdata

to select the correct time zone instead. Only this program modifies /etc/localtime correctly to reflect the proper local time zone. With that mod, cron works perfectly in R19. I'm going back now to R18 and my full configuration - I'm sure it will work fine there too. I will switch to R19 once I got everything working.

Thanks for your help anyways!