I'm very close to having a working sshfs setup. I've got:
working fuse.ko module
working version of openssh ssh client
working version of sshfs
I can happily mount remote file systems and use them just fine, but when I try to unmount them, my phone just locks and then reboots. I'd like to try and debug this, but I get no messages in any log that I can see.
So my question is, if I'm getting some kind of kernel panic, where can i see what's actually happening to try and debug this.
Any thoughts on what might be causing this would also be much appreciated.
I'll post full instructions once I get everything working of course.
can you not run "adb shell cat /proc/kmsg" to check for any Kernel Panic's
cat /proc/last_kmsg will get u the details of kernel panic and help u debug
if u want to save it to a file then type
cat /proc/last_kmsg > /sdcard/kmsg.txt
Okay, it's an "Alignment Trap"
Thanks for the info, now I can at least see the fault that's happening. It's an "Alignment trap". I assume this means one of the binaries I've created is messed up somehow. Any ideas on what/how to do about it much appreciated.
Note that this happens if I run 'fusermount -u mountpoint' and also if I run 'umount mountpoint'.
Relevant bits of /proc/last_kmsg:
Code:
[ 4323.039703] Alignment trap: not handling instruction e1903f9f at [<c00cc5dc>]
[ 4323.040069] Unhandled fault: alignment exception (0x011) at 0x00000001
[ 4323.040679] Internal error: : 11 [#1] PREEMPT
[ 4323.041015] last sysfs file: /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
[ 4323.041625] Modules linked in: fuse bcm4329
[ 4323.042877] CPU: 0 Tainted: G W (2.6.34-cyanogenmod #1)
[ 4323.043518] PC is at __destroy_inode+0x7c/0xa0
[ 4323.043853] LR is at __destroy_inode+0x28/0xa0
[ 4323.044494] pc : [<c00cc5e0>] lr : [<c00cc58c>] psr: 20000013
[ 4323.044525] sp : c54b5ee0 ip : 00000010 fp : 00100100
[ 4323.045440] r10: c30358f0 r9 : 00000000 r8 : 00200200
[ 4323.045776] r7 : 00000001 r6 : c54b4000 r5 : 00000000 r4 : c6b41d40
[ 4323.046417] r3 : 00000000 r2 : c54b5ec8 r1 : c54b5ec8 r0 : 00000001
[ 4323.046752] Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
[ 4323.047393] Control: 10c5787d Table: 261bc019 DAC: 00000015
[ 4323.048004]
[ 4323.048004] PC: 0xc00cc560:
----snip lots of register dumps-----
[ 4323.264343] Process fusermount (pid: 2455, stack limit = 0xc54b42f0)
[ 4323.264953] Stack: (0xc54b5ee0 to 0xc54b6000)
-----snip fusermount stack dump--
[ 4323.270294] [<c00cc5e0>] (__destroy_inode+0x7c/0xa0) from [<c00cc610>] (destroy_inode+0xc/0x44)
[ 4323.270935] [<c00cc610>] (destroy_inode+0xc/0x44) from [<c00cba80>] (iput+0x64/0x74)
[ 4323.271575] [<c00cba80>] (iput+0x64/0x74) from [<c00c9f84>] (shrink_dcache_for_umount_subtree+0x24c/0x2e4)
[ 4323.272216] [<c00c9f84>] (shrink_dcache_for_umount_subtree+0x24c/0x2e4) from [<c00ca068>] (shrink_dcache_for_umount+0x4c/0x60)
[ 4323.272888] [<c00ca068>] (shrink_dcache_for_umount+0x4c/0x60) from [<c00bab08>] (generic_shutdown_super+0x1c/0x13c)
[ 4323.273559] [<c00bab08>] (generic_shutdown_super+0x1c/0x13c) from [<c00bac64>] (kill_anon_super+0xc/0x78)
[ 4323.274230] [<c00bac64>] (kill_anon_super+0xc/0x78) from [<c00bb0ec>] (deactivate_super+0x68/0x80)
[ 4323.274597] [<c00bb0ec>] (deactivate_super+0x68/0x80) from [<c00d07dc>] (sys_umount+0x2f8/0x328)
[ 4323.275268] [<c00d07dc>] (sys_umount+0x2f8/0x328) from [<c0025f00>] (ret_fast_syscall+0x0/0x30)
[ 4323.275909] Code: 88bd8010 e3500000 08bd8010 e1903f9f (e2433001)
[ 4323.277313] ---[ end trace 1b75b31a2719ed1f ]---
[ 4323.277954] Kernel panic - not syncing: Fatal exception
[ 4323.278381] [<c002a9ac>] (unwind_backtrace+0x0/0xf0) from [<c03141f0>] (panic+0x58/0xd4)
[ 4323.279052] [<c03141f0>] (panic+0x58/0xd4) from [<c00297f8>] (die+0x2b4/0x304)
[ 4323.279693] [<c00297f8>] (die+0x2b4/0x304) from [<c0025314>] (do_DataAbort+0x80/0x94)
[ 4323.280059] [<c0025314>] (do_DataAbort+0x80/0x94) from [<c0025a2c>] (__dabt_svc+0x4c/0x60)
[ 4323.280700] Exception stack(0xc54b5e98 to 0xc54b5ee0)
[ 4323.281311] 5e80: 00000001 c54b5ec8
[ 4323.281768] 5ea0: c54b5ec8 00000000 c6b41d40 00000000 c54b4000 00000001 00200200 00000000
[ 4323.282409] 5ec0: c30358f0 00100100 00000010 c54b5ee0 c00cc58c c00cc5e0 20000013 ffffffff
[ 4323.283081] [<c0025a2c>] (__dabt_svc+0x4c/0x60) from [<c00cc5e0>] (__destroy_inode+0x7c/0xa0)
[ 4323.283447] [<c00cc5e0>] (__destroy_inode+0x7c/0xa0) from [<c00cc610>] (destroy_inode+0xc/0x44)
[ 4323.284118] [<c00cc610>] (destroy_inode+0xc/0x44) from [<c00cba80>] (iput+0x64/0x74)
[ 4323.284759] [<c00cba80>] (iput+0x64/0x74) from [<c00c9f84>] (shrink_dcache_for_umount_subtree+0x24c/0x2e4)
[ 4323.285430] [<c00c9f84>] (shrink_dcache_for_umount_subtree+0x24c/0x2e4) from [<c00ca068>] (shrink_dcache_for_umount+0x4c/0x60)
[ 4323.286102] [<c00ca068>] (shrink_dcache_for_umount+0x4c/0x60) from [<c00bab08>] (generic_shutdown_super+0x1c/0x13c)
[ 4323.286773] [<c00bab08>] (generic_shutdown_super+0x1c/0x13c) from [<c00bac64>] (kill_anon_super+0xc/0x78)
[ 4323.287414] [<c00bac64>] (kill_anon_super+0xc/0x78) from [<c00bb0ec>] (deactivate_super+0x68/0x80)
[ 4323.287780] [<c00bb0ec>] (deactivate_super+0x68/0x80) from [<c00d07dc>] (sys_umount+0x2f8/0x328)
[ 4323.288421] [<c00d07dc>] (sys_umount+0x2f8/0x328) from [<c0025f00>] (ret_fast_syscall+0x0/0x30)
[ 4323.289062] Rebooting in 5 seconds..
[ 4328.263732] Restarting Linux version 2.6.34-cyanogenmod ([email protected]) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Mon Jun 28 20:07:00 EDT 2010
hope this helps, remove spaces (since I am new user not allowed to post external links )
www rt-embedded com / blog / archives / resolving-alignment-traps /
Any news with this? I would be more than happy to have a working sshfs on my phone
Wish You best luck!
ditto, has anyone managed to get sshfs working?
waspbr said:
ditto, has anyone managed to get sshfs working?
Click to expand...
Click to collapse
I run sshfs on my Epic. I compiled the FUSE kernel module (fuse.ko) from the stock Samsung kernel sources and installed the pre-built userland dependencies (sshfs, fuse-utils, openssh-client, etc.) in a Debian chroot. I mount sshfs "volumes" in the chroot using the "allow_other" option, so that any Android uid/gid can access them.
The chroot probably isn't necessary, but I didn't want to bother compiling the userland dependencies myself. This article gives some directions on how to build a Debian chroot. I don't wase time with the unionfs stuff though, I just bind mount /dev, /dev/pts, /proc, & /sys.
thanks, gonna have a go at it once my schedule clears up
any progress? ive been thinking of using something like this on a Galaxy tab, make it a portal to my remote developer machine.
Sorry to bring up a dead thread, but it seems that there is at least a chance at sshfs. Seeing as I have a need or at least a strong desire to get this working, any chance someone figured it out?
Aaaaaaaaand, reviving this Thread again... sorry...
Anyone managed to get SSHfs properly working?
Thanks!
Hello
I'm experiencing a more/less frequent device lock ups/hangs....when only long push turn off button works to restart the system.
This happened both on Foilo Mod 1.3d and happening on latest official rooted firmware.
This can happen once/twice in 1 hour....on a random applications I use like ftp, games, web browsing, file managers....
psl advise in you have anything like it or help with possible solutions
Thanks
P.S. Always do update with factory reset before and after to gain stability, but this does not help it seems....
I does notice also it too on my folio with FolioMod v1.4, so i've installed the graphic-tweak-driver-rollback-patch now, to see if it is better now.
sader0 said:
Hello
I'm experiencing a more/less frequent device lock ups/hangs....when only long push turn off button works to restart the system.
Click to expand...
Click to collapse
Yep, I can confirm this. And it happens with no particular advice, such as slowdowns and so on... From my short experience with the Folio, it used to happen with 1.3d too. So, I'm worried that this might be a somewhat hardware-related problem.
Otherwise, with Foliomod, it would be such a great cheap device.
Anyone knows if there is a way to check logs history after a lockup/reboot just to look at what was going on right before the crash in search of possible hints???
Unfortunately issue still exists for my Folio 100
After update to Dexter Mod 1.4 became more frequent, so I rolled back to latest updated stock firmware, which still gives more rare lock ups rate....
anyone else havin such issues ? Anyone from mod developers(ofc roms testing is not the case) ?
thanks
I do noticve such locks/hang ups sometimes. but for me its mostly when the folio launches first time. just before when it has to mount the external sdcard. if i unlock the device before it sd card is mounted, it freezes and locks and either i restart it using long press power button or i just leave it and wait until it restarts by itself ( takes like 5 min or something for it to restart)
but if everytime i wait until the sd card is mounted then unlock the screen, then it works perfectly. so for me the issue comes with the sd card mounting system. either driver or something like that.
i dont think its all related to hardware issues, these locks/hang ups.
i believe it mostly has to do with the drivers being crap, resulting in unstable overall system. so unless toshiba provides with latest better drivers for the hardware present, then we will still experience these hang ups.
kaivish said:
I do noticve such locks/hang ups sometimes. but for me its mostly when the folio launches first time. just before when it has to mount the external sdcard. if i unlock the device before it sd card is mounted, it freezes and locks and either i restart it using long press power button or i just leave it and wait until it restarts by itself ( takes like 5 min or something for it to restart)
but if everytime i wait until the sd card is mounted then unlock the screen, then it works perfectly. so for me the issue comes with the sd card mounting system. either driver or something like that.
i dont think its all related to hardware issues, these locks/hang ups.
i believe it mostly has to do with the drivers being crap, resulting in unstable overall system. so unless toshiba provides with latest better drivers for the hardware present, then we will still experience these hang ups.
Click to expand...
Click to collapse
Same wif u... mine original firmware ..only facing start up hang ..sometime.. if remove the sd card before start...then is ok.
Well, I can advise that there is still a bug with system freeze/crash in case u will slide to unlock the system during mounting/preparation of the SD card.
However, after I removed SD card, problem still occurs randomly....
sader0 said:
Well, I can advise that there is still a bug with system freeze/crash in case u will slide to unlock the system during mounting/preparation of the SD card.
However, after I removed SD card, problem still occurs randomly....
Click to expand...
Click to collapse
well,, i think you should probably read the post one more time. slide to unlock while the sd card is being mounted, will definitely cause it to crash. i mentioned it earlier that this is a driver issue. try to unlock AFTER the sd card has been mounted. guess u can wait 1 second more before u unlock
if this is followed, then the issue of crashing is minimal at best. for me, i am using the folio without this issue since i managed to learn its ways. if u still have hangs, after waiting for mounting then uinlock AFTER mounting,, then i would say its something to do with apps u installed which is running the background and not compatible with the folio.
This is the /proc/kmsg (dmesg) "kernel panic" output directly before or better at a complete-freeze / lockup on my folio 100 (per "adb wait-for-device && adb shell cat /proc/kmsg" ) :
Code:
<1>[ 71.127595] Unable to handle kernel paging request at virtual address 0073008b
<1>[ 71.134890] pgd = d4858000
<1>[ 71.137668] [0073008b] *pgd=00000000
<0>[ 71.141254] Internal error: Oops: 5 [#1] PREEMPT SMP
<0>[ 71.146219] last sysfs file: /sys/devices/nvec/nvec_battery/power_supply/battery/technology
<4>[ 71.154567] Modules linked in: ar6000
<4>[ 71.158260] CPU: 1 Not tainted (2.6.32.9 #1)
<4>[ 71.162887] PC is at sem_handle_search+0xc/0x6c
<4>[ 71.167418] LR is at NvOsSemaphoreDestroy+0x18/0x7c
<4>[ 71.172295] pc : [<c0048704>] lr : [<c00488b8>] psr: 20000013
<4>[ 71.172302] sp : d485fe48 ip : d485fe60 fp : d485fe5c
<4>[ 71.183769] r10: 00000000 r9 : d485e000 r8 : c0033364
<4>[ 71.188990] r7 : 40044e21 r6 : 40044e21 r5 : d8f25004 r4 : 0073006f
<4>[ 71.195514] r3 : 00000000 r2 : 00000000 r1 : bed259e8 r0 : 0073006f
<4>[ 71.202038] Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
<4>[ 71.209169] Control: 10c5387d Table: 1485804a DAC: 00000015
<4>[ 71.214907]
<4>[ 71.214910] PC: 0xc0048684:
<4>[ 71.219179] 8684 e5982004 e2822001 e5882004 e593a010 e35a0000 0a00000a e59ac000 e30890d0
<4>[ 71.227435] 86a4 e58d9000 e1a00006 e1a01004 e3a0200c e1a03007 e12fff3c e5bac004 e35c0000
<4>[ 71.235685] 86c4 1afffff6 e5983004 e2433001 e5883004 e5983000 e3130002 0affffdc eb0e1a7d
<4>[ 71.243938] 86e4 eaffffda c05093f0 c0537080 c0509120 c0048614 e1a0c00d e92dd830 e24cb004
<4>[ 71.252190] 8704 e590301c e1a04000 e3530000 0a00000c e3730a01 8a00000a e59f003c eb0e1f40
<4>[ 71.260444] 8724 e594501c e3550000 0a000008 e595300c e1540003 3a000000 9a000004 e1a00005
<4>[ 71.268698] 8744 e89da830 e3a05000 e1a00005 e89da830 e59f0004 eb023e1e eafffff7 c050ccdc
<4>[ 71.276951] 8764 e1a0c00d e92dd830 e24cb004 e3500a01 e1a04000 3a000011 e3500000 089da830
<4>[ 71.285206]
<4>[ 71.285209] LR: 0xc0048838:
<4>[ 71.289479] 8838 e3500000 1a000001 e1a00004 eb01d0ca e3a00001 e89da830 e0855205 e0844105
<4>[ 71.297734] 8858 e5940010 ebffffc0 e3a00001 e89da830 e0855205 e0844105 e2840028 eb023f63
<4>[ 71.305988] 8878 e3a00001 e89da830 e0855205 e5940000 e0844105 e1a0e00f e594f010 e3a00001
<4>[ 71.314239] 8898 e89da830 c053acf8 e1a0c00d e92dd830 e24cb004 e2504000 089da830 ebffff8f
<4>[ 71.322492] 88b8 e2505000 089da830 f57ff05f e2843014 e1932f9f e2422001 e1831f92 e3310000
<4>[ 71.330743] 88d8 1afffffa f57ff05f e3520000 189da830 e59f0028 eb0e1ec8 e284101c e1a00005
<4>[ 71.338997] 88f8 eb071e22 e59f0014 eb023daf e1a00005 eb03e8cd e1a00004 eb03e8cb e89da830
<4>[ 71.347252] 8918 c050ccdc e1a0c00d e92dd830 e24cb004 e1a04000 ebffff71 e3500000 089da830
<4>[ 71.355506]
<4>[ 71.355509] SP: 0xd485fdc8:
<4>[ 71.359778] fdc8 00000100 c026f53c d485e000 d485fe34 00000000 00000001 ffffffff d485fe34
<4>[ 71.368033] fde8 40044e21 40044e21 d485fe5c d485fe00 c0032cec c00324f0 0073006f bed259e8
<4>[ 71.376284] fe08 00000000 00000000 0073006f d8f25004 40044e21 40044e21 c0033364 d485e000
<4>[ 71.384536] fe28 00000000 d485fe5c d485fe60 d485fe48 c00488b8 c0048704 20000013 ffffffff
<4>[ 71.392788] fe48 0073006f d8f25004 d485fe74 d485fe60 c00488b8 c0048704 00000000 d8f25004
<4>[ 71.401039] fe68 d485fedc d485fe78 c00477c4 c00488ac d485fd88 d485ff54 d485febc d485fe90
<4>[ 71.409291] fe88 c00af010 c0571338 00000000 0000ba00 00000000 d485ff7c d485ff78 d7524c40
<4>[ 71.417545] fea8 00000004 0073006f 00000100 d7c460a0 c0047428 bed259e4 40044e21 c0033364
<4>[ 71.425828]
<4>[ 71.425832] IP: 0xd485fde0:
<4>[ 71.430104] fde0 ffffffff d485fe34 40044e21 40044e21 d485fe5c d485fe00 c0032cec c00324f0
<4>[ 71.438398] fe00 0073006f bed259e8 00000000 00000000 0073006f d8f25004 40044e21 40044e21
<4>[ 71.446702] fe20 c0033364 d485e000 00000000 d485fe5c d485fe60 d485fe48 c00488b8 c0048704
<4>[ 71.454984] fe40 20000013 ffffffff 0073006f d8f25004 d485fe74 d485fe60 c00488b8 c0048704
<4>[ 71.463264] fe60 00000000 d8f25004 d485fedc d485fe78 c00477c4 c00488ac d485fd88 d485ff54
<4>[ 71.471542] fe80 d485febc d485fe90 c00af010 c0571338 00000000 0000ba00 00000000 d485ff7c
<4>[ 71.479822] fea0 d485ff78 d7524c40 00000004 0073006f 00000100 d7c460a0 c0047428 bed259e4
<4>[ 71.488099] fec0 40044e21 c0033364 d485e000 00000000 d485ff04 d485fee0 c0157258 c0047434
<4>[ 71.496380]
<4>[ 71.496385] FP: 0xd485fddc:
<4>[ 71.500658] fddc 00000001 ffffffff d485fe34 40044e21 40044e21 d485fe5c d485fe00 c0032cec
<4>[ 71.508942] fdfc c00324f0 0073006f bed259e8 00000000 00000000 0073006f d8f25004 40044e21
<4>[ 71.517223] fe1c 40044e21 c0033364 d485e000 00000000 d485fe5c d485fe60 d485fe48 c00488b8
<4>[ 71.525504] fe3c c0048704 20000013 ffffffff 0073006f d8f25004 d485fe74 d485fe60 c00488b8
<4>[ 71.533772] fe5c c0048704 00000000 d8f25004 d485fedc d485fe78 c00477c4 c00488ac d485fd88
<4>[ 71.542054] fe7c d485ff54 d485febc d485fe90 c00af010 c0571338 00000000 0000ba00 00000000
<4>[ 71.550327] fe9c d485ff7c d485ff78 d7524c40 00000004 0073006f 00000100 d7c460a0 c0047428
<4>[ 71.558597] febc bed259e4 40044e21 c0033364 d485e000 00000000 d485ff04 d485fee0 c0157258
<4>[ 71.566879]
<4>[ 71.566884] R5: 0xd8f24f84:
<4>[ 71.571158] 4f84 ******** ******** ******** ******** ******** ******** ******** ********
<4>[ 71.579440] 4fa4 ******** ******** ******** ******** ******** ******** ******** ********
<4>[ 71.587712] 4fc4 ******** ******** ******** ******** ******** ******** ******** ********
<4>[ 71.595998] 4fe4 ******** ******** ******** ******** ******** ******** ******** 00000038
<4>[ 71.604275] 5004 00000000 00000000 00000000 d8f25010 d8f25010 0000ffff 00000000 d7957480
<4>[ 71.612569] 5024 00000000 00000000 d8f2502c d8f2502c 000003bc ffffff00 ffffffff ffffffff
<4>[ 71.620843] 5044 ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
<4>[ 71.629128] 5064 ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
<4>[ 71.637406]
<4>[ 71.637411] R8: 0xc00332e4:
<4>[ 71.641683] 32e4 e92d0030 e31c0c01 1a000008 e3570e17 e24fef47 3798f107 e28d1008 e3a08000
<4>[ 71.649957] 3304 e357080f e2270000 2a0010ff ea028117 e1a02007 e28d1008 e3a00000 eb00054a
<4>[ 71.658236] 3324 e28fe014 e1a07000 e28d1008 e3570e17 3891000f 3798f107 eaffffef e5ad0008
<4>[ 71.666510] 3344 e1a02007 e1a0100d e3a00001 eb00053e eaffffb6 e320f000 e320f000 c050b54c
<4>[ 71.674793] 3364 c00c6920 c00ba5bc c003394c c0149868 c0149600 c0146cc0 c0146a38 c00d3774
<4>[ 71.683061] 3384 c0146ce8 c01557a4 c015507c c003395c c01477bc c00d3774 c01554c8 c0147690
<4>[ 71.691347] 33a4 c00e6f0c c00d3774 c00d3774 c01485c8 c00c60f0 c0163e48 c00d3774 c00e6e54
<4>[ 71.699623] 33c4 c00e6b60 c00d3774 c00c19b4 c00d3774 c00d3774 c00c6afc c00d3774 c00d3774
<4>[ 71.707920]
<4>[ 71.707924] R9: 0xd485df80:
<4>[ 71.712196] df80 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
<4>[ 71.720490] dfa0 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
<4>[ 71.728767] dfc0 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
<4>[ 71.737069] dfe0 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
<4>[ 71.745370] e000 00000002 00000002 00000000 d7957480 c05133ac 00000001 00000017 d7957480
<4>[ 71.753663] e020 c093a420 d485e000 c059ad40 d0a9c8c0 cd5f8000 00000000 d485fbe4 d485fb38
<4>[ 71.761938] e040 c03ce7dc 00000000 00000000 00000000 00000000 00000000 01010000 00000000
<4>[ 71.770225] e060 afd4a868 00000000 00000000 00000000 00000000 00000000 00000000 00000000
<0>[ 71.778513] Process mediaserver (pid: 956, stack limit = 0xd485e2f0)
<0>[ 71.784866] Stack: (0xd485fe48 to 0xd4860000)
<0>[ 71.789226] fe40: 0073006f d8f25004 d485fe74 d485fe60 c00488b8 c0048704
<0>[ 71.797411] fe60: 00000000 d8f25004 d485fedc d485fe78 c00477c4 c00488ac d485fd88 d485ff54
<0>[ 71.805595] fe80: d485febc d485fe90 c00af010 c0571338 00000000 0000ba00 00000000 d485ff7c
<0>[ 71.813773] fea0: d485ff78 d7524c40 00000004 0073006f 00000100 d7c460a0 c0047428 bed259e4
<0>[ 71.821951] fec0: 40044e21 c0033364 d485e000 00000000 d485ff04 d485fee0 c0157258 c0047434
<0>[ 71.830138] fee0: d485ff0c d485fef0 bed259e4 d7c460a0 40044e21 00000003 d485ff7c d485ff08
<0>[ 71.838324] ff00: c0157430 c015722c c00b0dec c00e5bec d485ff70 00000000 00000080 0000ba00
<0>[ 71.846509] ff20: 00000002 00000000 d485e000 00000000 d485ffa4 d485ff40 c00e4f30 c00e47f0
<0>[ 71.854695] ff40: 0000ba00 00000000 ffffffff d485ff58 c00cf70c d485fed4 d7c460a0 bed259e4
<0>[ 71.862880] ff60: 40044e21 00000003 c0033364 d485e000 d485ffa4 d485ff80 c01579f4 c01573cc
<0>[ 71.871063] ff80: 00000000 00000001 8040916c bed259fc bed25ab4 00000036 00000000 d485ffa8
<0>[ 71.879250] ffa0: c00331e0 c01579c0 8040916c bed259fc 00000003 40044e21 bed259e4 bed259dc
<0>[ 71.887431] ffc0: 8040916c bed259fc bed25ab4 00000036 00000000 00000000 00000000 00000000
<0>[ 71.895619] ffe0: 80409178 bed259c0 afd22efd afd0dbdc 80000010 00000003 00000000 00000000
<4>[ 71.903793] Backtrace:
<4>[ 71.906275] [<c00486f8>] (sem_handle_search+0x0/0x6c) from [<c00488b8>] (NvOsSemaphoreDestroy+0x18/0x7c)
<4>[ 71.915756] r5:d8f25004 r4:0073006f
<4>[ 71.919373] [<c00488a0>] (NvOsSemaphoreDestroy+0x0/0x7c) from [<c00477c4>] (nvos_ioctl+0x39c/0x6bc)
<4>[ 71.928418] r5:d8f25004 r4:00000000
<4>[ 71.932032] [<c0047428>] (nvos_ioctl+0x0/0x6bc) from [<c0157258>] (vfs_ioctl+0x38/0x98)
<4>[ 71.940042] [<c0157220>] (vfs_ioctl+0x0/0x98) from [<c0157430>] (do_vfs_ioctl+0x70/0x5f4)
<4>[ 71.948221] r7:00000003 r6:40044e21 r5:d7c460a0 r4:bed259e4
<4>[ 71.953945] [<c01573c0>] (do_vfs_ioctl+0x0/0x5f4) from [<c01579f4>] (sys_ioctl+0x40/0x68)
<4>[ 71.962126] r9:d485e000 r8:c0033364 r7:00000003 r6:40044e21 r5:bed259e4
<4>[ 71.968731] r4:d7c460a0
<4>[ 71.971383] [<c01579b4>] (sys_ioctl+0x0/0x68) from [<c00331e0>] (ret_fast_syscall+0x0/0x2c)
<4>[ 71.979739] r7:00000036 r6:bed25ab4 r5:bed259fc r4:8040916c
<0>[ 71.985456] Code: c0048614 e1a0c00d e92dd830 e24cb004 (e590301c)
<4>[ 72.026642] ---[ end trace b90de0c8fa44cdc0 ]---
<0>[ 72.031450] Kernel panic - not syncing: Fatal exception
<4>[ 72.036680] Backtrace:
<4>[ 72.039211] [<c0036fac>] (dump_backtrace+0x0/0x10c) from [<c03cdd94>] (dump_stack+0x18/0x1c)
<4>[ 72.047669] r7:d485e2f0 r6:c05398a8 r5:d7957480 r4:c054e240
<4>[ 72.053390] [<c03cdd7c>] (dump_stack+0x0/0x1c) from [<c03cddfc>] (panic+0x64/0x130)
<4>[ 72.061089] [<c03cdd98>] (panic+0x0/0x130) from [<c0037474>] (die+0x168/0x190)
<4>[ 72.068345] r3:00000001 r2:d485fcc8 r1:ceb06760 r0:c04899d0
<4>[ 72.074057] [<c003730c>] (die+0x0/0x190) from [<c0039cbc>] (__do_kernel_fault+0x6c/0x7c)
<4>[ 72.082171] [<c0039c50>] (__do_kernel_fault+0x0/0x7c) from [<c0039e24>] (do_page_fault+0x158/0x1f4)
<4>[ 72.091236] r7:00010000 r6:0073008b r5:d7957480 r4:d7c021a0
<4>[ 72.096983] [<c0039ccc>] (do_page_fault+0x0/0x1f4) from [<c0039fc0>] (do_translation_fault+0x74/0x7c)
I hope this output can help to fix the freeze/lockup issue. And i will do maybe more reseaching into that issue later.
Edit: After trying it more times to trigger this issue (simply per turning the folio complete off and again on, and then start some apps, until the issue is there), I'll get always similar kernel panics (only with different memory addresses, the rest is always almost fully identical) if my folio freezed up/lockup.
Edit: After trying it more times to trigger this issue (simply per turning the folio complete off and again on, and then start some apps, until the issue is there), I'll get always similar kernel panics (only with different memory addresses, the rest is always almost fully identical) if my folio freezed up/lockup.
Click to expand...
Click to collapse
With Topogigi we have isolated that only hangs after screen lock/sleep, then wake-up, then wifi reconnect and after a while (5/10 min) usimg net connection, folio freezes. But if you do not use net (disconnect wifi, because if wifi is connected, sync can freeze it), folio works fine all the time you want.
Of course, it's very annoying because practically all apps connect to net.
Thats the tests we've done. Perhaps that help:
I use a widget to prevent auto screen off. When active, Techvision screen off always gave me SOD.
So I removed widget preventing auto screen off. Then Techvision screen off was able to sleep and wake (it took a while to wake). But after that, Wifi wasn't able to reconnect. After Wifi off and on again, it took almost a minute and several attempts in order to have a connection. Five minutes after connecting, got a hang and needed to power off (10 secs power button press).
After a full minute insulting the tablet and Toshiba, restarted and changed advanced Wifi settings to "never" in "Screen off wifi policy".
Tested Techvisions Screen off. Tablet woke up very quickly and Wifi was already connected. But few minutes after that, Dolphin freezed and had to hardly power off (10 secs power button press).
When I've finished blasphemating, I've reached these conclusions:
- General hangs are due to Wifi/Net connections (despite hangs due to specific apps). Had tried almost all browsers (Dolphin, Opera, Android default, Miren, UC, Galapagos, Firefox, ...) and all them gave me hangs. But also BeyondPod, Newsrob, Market, Flickie Wallpapers, YouTube, Facebook, Tapatalk, XBMC Remote... that I remember. All them using net connections and at least one (XBMC) do not uses Internet (no DNS).
- When wifi is set to 'never' policy, tablet screens off but do not sleep (led is fixed orange, quickly wake up). After a long while it goes slept (led blinks orange, wake up takes a while, wifi connection has gone) and then is when you can have SOD.
- When Wifi is set to 'When screen off' policy, Techvision screen off directly goes to sleep mode (led blinks orange) and you can have SOD.
- SOD always appeared when preventing auto screen off, but only few times when not ???
- I've noticed that when Wifi level is low and it tooks several attempts to connect (my bedroom for instance, far from router), it has more hangs than when Wifi level is higher and connects almost in few seconds (sittingroom, near the router). Someone wrote in another thread that Wifi driver has a wrong level issue and connects at a wrong speed when level is low. Orders can confirm that?
Click to expand...
Click to collapse
EulerVen said:
With Topogigi we have isolated that only hangs after screen lock/sleep, then wake-up, then wifi reconnect and after a while (5/10 min) usimg net connection, folio freezes. But if you do not use net (disconnect wifi, because if wifi is connected, sync can freeze it), folio works fine all the time you want.
Of course, it's very annoying because practically all apps connect to net.
Thats the tests we've done. Perhaps that help:
Click to expand...
Click to collapse
WiFi is at me "completely" off/disabled (at the almost time), so that your here described issue is maybe a different issue than mine
And I had already two other folios (from fully different webshops), which had exactly the equal identical issue like my current third folio.
BeRo1985 said:
WiFi is at me "completely" off/disabled (at the almost time), so that your here described issue is maybe a different issue than mine
And I had already two other folios (from fully different webshops), which had exactly the equal identical issue like my current third folio.
Click to expand...
Click to collapse
Then the only answer I can manage is that different hardware versions have different issues with the same drivers (1.4 mod). Amazing!
Check your dmesg: the kernel panic is caused by ar6000 module that is wifi. It's always the same story...
EDIT: I made another test this morning. I fired up a terminal emulator, logged as root (su), then removed ar6000 module with "rmmod ar6000". Wireless connection stopped imediately and I tried to put the device to sleep. At wakeup, I started wifi (need to do it twice, the first time it gives an error), but then I could work with my tablet without hangups. Wireless network became very slow (speedtest.net takes an age to load), but the tablet was fully functional. I'm really convinced that something net related is causing all the hangups. And....I don't use SD at boot (that's another story), so no hangups with the screen lock.
In my case, I was unable to use my Folio for more than 30 min.
I can only confirm that from my observation it is related with wifi and wake up.
Its always the same, after reboot it works fine till first wifi disconnection (in sleep mode or during normal operation), and when it will connect again, after 5~10 min device freezes, always.
Besides, when I was using EZ File Explorer and I preform a search of SMB shares in network device freezes, the same was when Ive started FTP server on Folio, and I was trying upload a large file to built in SD (without earlier disconnection).
But right now Im able to work on device without hangs for few hours using following (temporary) solution:
Ive changed settings of a screen to: always on
Ive downloaded "Screen off" widget from techvision (that Topogigi mentioned in other thread) and when I want to have a brake, I use Screen off shortcut.
Ive downloaded Repgon WIFI keep alive, and configure it to always keep wifi connection on.
So with above mix of solution it works better, but still when wifi will disconnect it will hang. This temporary solution also shorten battery life.
But at least I can use it now.
Regards,
headblow
headblow said:
In my case, I was unable to use my Folio for more than 30 min.
I can only confirm that from my observation it is related with wifi and wake up.
Its always the same, after reboot it works fine till first wifi disconnection (in sleep mode or during normal operation), and when it will connect again, after 5~10 min device freezes, always.
Besides, when I was using EZ File Explorer and I preform a search of SMB shares in network device freezes, the same was when Ive started FTP server on Folio, and I was trying upload a large file to built in SD (without earlier disconnection).
But right now Im able to work on device without hangs for few hours using following (temporary) solution:
Ive changed settings of a screen to: always on
Ive downloaded "Screen off" widget from techvision (that Topogigi mentioned in other thread) and when I want to have a brake, I use Screen off shortcut.
Ive downloaded Repgon WIFI keep alive, and configure it to always keep wifi connection on.
So with above mix of solution it works better, but still when wifi will disconnect it will hang. This temporary solution also shorten battery life.
But at least I can use it now.
Regards,
headblow
Click to expand...
Click to collapse
I think we are narrowing the research: I can suspend the device now without side effects manually removing the ar6000 module with rmmod and reloading it with "insmod /system/wifi/ar6000.ko" at wakeup. With a "netcfg wlan0 up" the tablet reconnects to wifi on a regular basis, but connection is really slow after this (but no more hangups downloading a 10mb file). I'll go further with experiments.
Topogigi said:
Check your dmesg: the kernel panic is caused by ar6000 module that is wifi. It's always the same story...
Click to expand...
Click to collapse
Sorry, it's not correct. The "Modules linked in:" line shows only the "loaded" kernel modules to the kernel panic time, but not the modules, which has raised the kernel panic.
And as said I will do more researching at lowlevel debugging as far I get the time for it.
BeRo1985 said:
Sorry, it's not correct. The "Modules linked in:" line shows only the "loaded" kernel modules to the kernel panic time, but not the modules, which has raised the kernel panic.
And as said I will do more researching at lowlevel debugging as far I get the time for it.
Click to expand...
Click to collapse
Sorry, but I'm only arguing that the module is loaded, so the kernel panic (it's my theory) is due to the module. Try to unload the module and let's see if the kernel panics anymore....
My preliminary research results:
nvos_ioctl calls NvOsSemaphoreDestroy in mach-tegra/nvos/nvos.c, which calls sem_handle_search in in mach-tegra/nvos/nvos.c, and at least this sem_handle_search implementation seems to be the final trigger of the page fault (but sem_handle_search must not be the culprit of it too).
sem_handle_search does binary tree search with the semaphore handle as search key, and if a binary tree node contains a invalid node-next-left or node-next-right pointer, then it will trigger this memory access violation or better page fault kernel exception.
And since nvos_ioctl refers to the user space, because nvos_ioctl is located in the mach-tegra/nvos/nvos_user.c as link to unlocked_ioctl in the nvosfops
file_operations structure, which is used by the ioctl user space API calls and/or user space syscalls. So the real culprit must be "maybe" found from there in user space.
Hence my two suspects in addition to the kernel are now: mediaserver or nvrm_daemon maybe together with a multithreading-code-on-multiple-cores-synchronisation problem.
Unfortunately, the Folio has probably no JTAG, to debug it together with printk on kernel level over a serial console. ADB is almost sadly useless here.
So to all hardware-hackers/hardware-freaks here, get/buy a folio, open and disselect it, and search for JTAG pins on the PCB board. That would be really helpful then.
As a small note: I'm a software developer with very strong high-level and very strong low-level-coding skills
I am giving up on folio... I can't understand how someone could be happy with it. Lots of hardware and software problems and sure no great software or games anytime soon. Tegra 2 had a bad start. I really regret to say but apple had the upper hand here. Android is good but not good enough for using in a tablet. I would like to give thanks to everyone who had being working hard to improve folio.
bastospn said:
I am giving up on folio... I can't understand how someone could be happy with it. Lots of hardware and software problems and sure no great software or games anytime soon. Tegra 2 had a bad start. I really regret to say but apple had the upper hand here. Android is good but not good enough for using in a tablet. I would like to give thanks to everyone who had being working hard to improve folio.
Click to expand...
Click to collapse
@bastospn
Cheers. You're entitled to your opinion. Not that I'm defending the Folio here but I believe there are no Android tablets right now that are 'stable'. Of course, we are all constantly benchmarking tablets (Android, WebOS, et al) against the iPad. So, in that sense, Apple has it hands down over Android in this department for now. Agree! But I'd venture to say that this is because Android is a relatively new OS as compared to iOS.
Nevertheless, I guess it's just a matter of choice and preference over which OS to choose (and not so much the tablet).
Cheers~
wonger