**** BEGIN LOGGING AT Sun Feb 17 02:59:57 2019 Feb 17 06:18:08 https://k2.okccdn.com/php/load_okc_image.php/images/36x37/683x684/0/14973695938364948173.webp?v=2 Feb 17 06:19:20 why the heck would you remove the cellular antenna? Feb 17 06:30:10 Vajb: your problem is actually (SSI interface to) modem: Feb 17 06:30:11 Feb 16 15:14:29 Nokia-N900 kernel: [ 7934.904876] McSAAB: ------- TX WATCHDOG TIMER trigerred ----- Feb 17 06:30:13 Feb 16 15:14:29 Nokia-N900 kernel: [ 7934.904968] McSAAB: ACWake line 00000001 Feb 17 06:36:02 this either means the interface got disconnected (nroken solder joint), or - more likely -the modem went into shut down state for whatever reason, in an unexpected way that the fremantle "drivers" didn't notice Feb 17 06:36:32 one such trigger could be undervoltage from battery Feb 17 06:40:41 DocScrutinizer05: I suspect solder join. Because I have noticed that temperature affects it. Feb 17 06:43:41 and I was planning to remove cellular antenna just to rule out possibility of weak connection there. Feb 17 16:38:27 Vajb: yes yours is clearly now not antenna related - those were possibilities to explore earlier. Feb 17 16:39:30 incidentally, for the last few days, i am using a different operaor - thoe one which my No00 doesn't "like" Feb 17 16:40:28 i have also got a couple of modem resets, and Internet connectivity is really bd. Feb 17 16:40:58 i am just waiting to depelte the data plan on it, and switch bad. i cleaned the SIM card Feb 17 16:41:37 so you may also, just for the fun of it at least, test a different operator Feb 17 16:41:49 s/depelte/deplete/ Feb 17 16:46:37 paste.debian.net/1068431/ Feb 17 16:49:05 this does not happen with the other operator ... dunno if this would be a plausible theory: the 'bad' operator has some instability on their network, and N900 modem keeps trying to keep up/adapt, until it gives up and restarts (buggy?) Feb 17 16:49:32 in my case, it is not a SIM issue, as i have also tried a brand new SIM Feb 17 16:50:07 i've also had this problem for at least 2 years, but usage is perfect with the 2nd operator Feb 17 17:14:21 yeah I got new sim as well. I could purchase prepaid sim I thing to test. Feb 17 17:15:33 but I think I'll make backup first and try with other device. Feb 17 17:20:35 other device? Feb 17 17:46:52 what other device you mean Vajb? Feb 17 17:48:03 other n900 Feb 17 17:48:17 I have three ;) Feb 17 17:48:45 but Im lazy and stubborn and don't wanna give up with this one Feb 17 18:08:54 lol. you're unfair to us :D Feb 17 18:09:20 you mean you haven't even tested this 'problem' on one of the other N900 at all up to now? Feb 17 18:15:46 What can cause huge mem usage by 'hald' after some time? Stop & start 'hal' frees mem but it reboots also. Feb 17 18:15:48 https://transfer.sh/ThiCQ/Screenshot-20190216-222336.png Feb 17 18:15:57 https://transfer.sh/HkNDL/Screenshot-20190216-224937.png Feb 17 18:17:05 no I haven't. Other is having devuan so would need flashing and another is untouched by me so would require flashing too Feb 17 18:22:57 devuan? you didn't install devuan on a uSD card? Feb 17 18:36:55 hmm now that you mentioned I am not sure. It's been awhile. I followed Enrico_Menotti's instructions. Feb 17 18:39:45 i don't think anyone is installing to eMMC yet. Feb 17 18:42:44 well if nothing else I've created some conversation :) Feb 17 18:44:26 ontime: no idea. you don't have something nstalled which might 'confuse' hald? such as battery managers perhaps? Feb 17 18:45:57 i2cget and i2cset are most use Feb 17 18:46:09 is sd card only one option? I want to test devuan and internal eMMC would be best option Feb 17 18:46:37 Vajb: I've fixed gsm failure by adding spongy thing between metal can and gsm chip Feb 17 18:47:02 but after several months when I've disassembled device this fixed occured temporary Feb 17 18:56:18 dbus-monitor shows a lot constantly: signal sender=org.freedesktop.DBus -> dest=(null destination) serial=71943 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged Feb 17 18:56:35 probably because of gsm chip failure? Feb 17 18:59:58 I'll turn off script with i2cset, use it for setting battery voltage to 3.85 when device is on charger Feb 17 19:07:38 yes, do that. Feb 17 19:07:57 you're using bme-replacment? Feb 17 19:11:53 didn't touch bme, only i2cset Feb 17 19:18:03 turns it off, seems help, because that above 'dbus member=NameOwnerChanged' disappear Feb 17 19:18:38 might be that Feb 17 20:17:50 ~+uptime Feb 17 20:17:51 - Uptime for purl - Feb 17 20:17:51 Now: 1h 20m 54s running infobot 1.5.4 (SVN) -- linux Feb 17 20:17:51 1: 59d 8h 41m 19s running infobot 1.5.4 (SVN) -- linux, ended Sun Nov 14 18:39:57 2010 Feb 17 20:17:51 2: 57d 3h 9m 23s running infobot 1.5.4 (SVN) -- linux, ended Fri Jun 26 20:39:27 2009 Feb 17 20:17:52 3: 53d 8h 24m 4s running infobot 1.5.4 (SVN) -- linux, ended Tue Nov 7 05:34:20 2017 Feb 17 20:22:58 DocScrutinizer05: any ideas with my modem issues? http://paste.debian.net/1068431/ Feb 17 20:23:33 Feb 17 16:44:44 Nokia-N900 kernel: [ 239.880493] * CMT rst line change detected (0) Feb 17 20:23:44 the modem triggered a restart Feb 17 20:23:59 AIUI Feb 17 20:26:58 it only seems to happen with this one operator, where i have flaky Internet connection. with the other operator, connection is always good, and i don't recall having these restarts there Feb 17 20:26:58 maybe the fremantle driver (icd, ssc, csd, whatever) is supposed to send keep-alive pings via SSI aka McSAAB and didn't do, so the modem decided to assert the reset line to make fremantle reset the modem and drivers? Feb 17 20:28:07 I have no really good idea of what's going on in context of this SSI iterface between modem and OMAP Feb 17 20:28:46 I just know SSI/HSI is a PITA since it's IRQ driven and one lost IRQ will make the whole interface stall Feb 17 20:29:51 you'd hope they use level IRQ detection, not edge Feb 17 20:31:05 keeping a constant ping helps a lot in my case - the restarts don't happen (at least not frequently) Feb 17 20:45:31 ooh **** ENDING LOGGING AT Mon Feb 18 02:59:56 2019