IRC log of #maemo-ssu for Monday, 2013-01-14

freemangordonso (again a wild guess), the interrupt line is enabled when it should not (a) or luf's device/cable is screwed00:00
freemangordonluf: did you try with different cable00:00
freemangordon?00:00
lufNo because it happens only 4 times.00:00
lufI'm using the cable with the dev phone very often.00:00
luf* I use ...00:02
freemangordonPali: http://logs.nslu2-linux.org/livelogs/maemo/maemo.20101013.txt00:02
freemangordonsearch for bug00:02
luffreemangordon: I'm not alone :D00:03
luffreemangordon: did you see that after osso-gnomevfs-extra cleanup the browserd core dump doesn't arrive?00:04
freemangordonluf: yes00:04
freemangordonthough I wonder what cleanup you are talking about00:05
freemangordon:)00:05
lufI'll upload to git when I finish. After that I'll add posibility to recreate bda -> path hash (in case of gnomevfs daemon failure).00:06
freemangordonluf: did you get such oopses with KP51r1?00:07
lufI find that there is dbus_message_unref prior working with the message data (gchar *). So maybe it was this.00:07
luffreemangordon: It's the only 4 oopses I have ever seen with N900.00:07
freemangordonaah, for sure00:07
freemangordonluf: all of them with KP52, ain't?00:08
lufShit now I'm checking prod N900 and the error is there also.00:10
freemangordonluf: what kernel?00:10
lufKP5000:11
freemangordonluf: what machine/os do you connect to?00:11
lufIt' not HW problem with N900.00:11
freemangordonsure00:11
luffreemangordon: FC16 (my desktop).00:11
lufBut I have no idea if I used the same or different cable :(00:12
freemangordonluf: however the kernel should deal with broken cabling :)00:13
freemangordonluf: do you have some reliable way of reproducing that?00:13
luffreemangordon: no :(00:14
lufThe first time on dev N900 I saw when I was very low on battery. But last time N900 has nearly full battery.00:14
lufI'm using dev N900 several month (nearly day to day) and only 4 oopses.00:15
freemangordonhmm, BUG_ON is missing from the upstream code00:20
freemangordonPali: ^^^ http://lxr.free-electrons.com/source/drivers/usb/musb/musb_gadget.c#L90800:20
freemangordonneither there is such a loop00:21
*** NIN101 has quit IRC00:25
lufAnother question. I have a lot ot useless d(x) calls and I want to remove it using #define d(x) ... What is the right construct for it?00:27
freemangordonluf: I am not sure I get your question00:28
luf#define d(x)00:28
lufIs it correct?00:29
freemangordonyep00:29
lufI see recomendation to use it this (safer way): #define d(x) {}00:30
freemangordonshould not matter00:31
lufRight. I'll try :)00:31
freemangordonluf: unfortunately I don;t think we'll be able to fix that bug without having a way to reproduce it :(. anyway, lets see if Pali will come up with something00:39
luffreemangordon: I understand.00:40
*** Guest25139 has quit IRC00:40
freemangordonuploading microb-engine in cssu-devel00:41
luffreemangordon: I pushed the cleanup into git.00:47
freemangordondo you mind to upluad to -devel too?00:47
freemangordon*upload00:47
lufNot now. I'll finish one task first.00:48
freemangordon luf: microb-engine is in the repo00:55
luffreemangordon: gread job. Thanks.00:55
freemangordonthe fuck, I had forgotten how slow is microb ARM build :)01:00
luf:D01:00
*** arcean has quit IRC01:04
luffreemangordon: tell us how long it takes.01:04
freemangordonwhich one?01:04
luffreemangordon: microb ARM build01:04
*** arcean has joined #maemo-ssu01:05
freemangordonoh, you got me wrong, I mean - how slow is microb when microb-engine is build with gcc 4.2.101:05
freemangordonotherwise the build takes ~40 minutes01:06
luffreemangordon: What's the difference (%) ?01:06
DocScrutinizer05did *anything* regarding internet connection and particularly DHCP change in CSSU (lately)?01:06
freemangordonNFC, it is just rendering much slower than -thumb build01:06
freemangordonDocScrutinizer05: afaik Pali has changed something, though not sure if it is in -testing01:07
luffreemangordon, DocScrutinizer05: it's disabled by default.01:07
DocScrutinizer05I had more issues with broken connectivity during last 2 weeks orso than the 4 years before01:07
PaliDocScrutinizer05, changes are only in usb001:08
Paliand everything is disabled by default01:08
*** arcean has quit IRC01:08
DocScrutinizer05given the low frequency I leave home, I could almost claim it's 100% reproducible01:09
DocScrutinizer05I'll keep an eye on it01:09
* DocScrutinizer05 frowns01:09
keriodon't frown! you'll get wrinkles!01:15
DocScrutinizer05leaving WLAN area, 2.5G doesn't connect. Switching to "dual", takes 20s to crank up 3G, still no connect. "No Internet". Connecting to GPRS, switching back to 2.5G, works.01:27
DocScrutinizer05Feels like ICD2 or whomever doesn't connect to GPRS anymore, though I got setting "connect to any internet available"01:28
DocScrutinizer05rather "automatic connect: Any connection"01:30
* ShadowJK would blame operator01:41
* ShadowJK left home today, N900 connected to 2.5g01:42
luffreemangordon: ping01:47
*** wmarone has quit IRC01:47
*** wmarone has joined #maemo-ssu01:48
luffreemangordon: libnspr4 libnss3 libnss3-certs - these packages were uploaded with microb-engine?01:51
DocScrutinizer05ShadowJK: hard to blame those 0.5th level help desk robots02:00
DocScrutinizer05ShadowJK: unless I have some hard facts to slap them with02:00
ShadowJKBasically the modem hides their buggy network config02:02
DocScrutinizer05ShadowJK: but yeah, it kinda explains the behavior when I assume >>DHCP doesn't work for new lease on 2G, while handing over an existing lease from 3G works"02:02
ShadowJKI suspect dhcp isn't really relevant02:04
ShadowJKlike, I've never seen a dhcp request or refresh in 3g-2g-3g transitions02:04
DocScrutinizer05who however is the culprit for DHCP not working on 2G, that's still up to anybody's guess. Particularly since during last years I found 2G recovering from such lockup when I reboot the device02:04
DocScrutinizer05and yes, it could as well be something around APN sign-in02:05
ShadowJKdhclient or dhcp overall is probably not at all involved at any stage of a cellular connection02:05
DocScrutinizer05errr, how would ICD2 resp dnsmasq know about the device's IP then?02:06
ShadowJK"dhcp not working" is hard to tell apart from "connection is not working at all" unless you've got access to both ends02:06
DocScrutinizer05after all I config my GPRS DHCP in connections-advanced02:07
DocScrutinizer05I *could*02:08
DocScrutinizer05"get IP automatically" and "get DNS automatically"02:09
ShadowJKIt's not dhcp02:10
DocScrutinizer05o.O02:10
ShadowJKSince when has gsm/3g ever reused an existing protocol when they could invent a new protocol :P02:11
ShadowJKdhcp needs an existing IP connection, I suspect the addresses get negotiated before IP packets start flowing02:12
ShadowJKthere's also no dhcp on dialup internet, PPPoE and PPPoA +dsl either02:13
luffreemangordon: I announced also your upload of microb-engine to cssu-devel on TMO.02:32
*** luf has quit IRC02:33
DocScrutinizer05ShadowJK: I'd say you got a point there03:01
*** arcean has joined #maemo-ssu03:52
*** arcean has quit IRC03:56
*** kolp_ has joined #maemo-ssu04:14
*** kolp has quit IRC04:17
*** kolp_ has quit IRC04:44
*** nox- has quit IRC05:02
*** snx has joined #maemo-ssu05:16
*** Jaded has joined #maemo-ssu05:21
*** Jaded has quit IRC05:21
*** Jaded has joined #maemo-ssu05:21
*** Jade has quit IRC05:24
*** amiconn_ has joined #maemo-ssu05:36
*** amiconn has quit IRC05:36
*** amiconn_ is now known as amiconn05:36
*** DocScrutinizer05 has quit IRC06:03
*** DocScrutinizer05 has joined #maemo-ssu06:03
*** snx has quit IRC06:05
*** Pali has quit IRC06:34
*** snx has joined #maemo-ssu07:24
*** Jaded is now known as jade07:26
*** snx has quit IRC07:37
*** luf has joined #maemo-ssu08:02
*** Martix has quit IRC08:17
freemangordonluf: can we do anything about the missing thumbnails? to stop trying to get them for example?09:14
freemangordonluf: this is for obexftp09:16
luffreemangordon: I understand. I also have it in my todo.09:22
freemangordonluf: another inconvenience (though I think nothing can be done) - the connection to the devices is tried in order BT returns them09:24
freemangordonthis leads that 5th device in the list (which is available) to be hardly accessible, because the 4 previous are not available09:25
freemangordonI hope you get what I mean09:25
freemangordonI wonder if async dbus calls with callbacks could help here09:26
luffreemangordon: we talked about it last week. You said it's async ...09:26
freemangordonluf: BT as a whole is async related to the other fs09:27
freemangordonbut device enumeration/browsing in BT is not AIUI09:28
luffreemangordon: enumeration is fast enough. The problem is that it tries to preload the content one level down ...09:28
freemangordoni.e. until there is no answer from device A (evenv if it is "device not found"), device B is not enumerated09:28
freemangordonluf: exactly. however, it is not a major problem, so I think we could live with it09:29
freemangordonif there is no some easy solution09:29
luffreemangordon: I can add it to the todo however I have no idea how to do it.09:30
freemangordonluf: I guess it is something in gw_... calls09:30
freemangordonluf: it is up to you09:30
luffreemangordon: Hmmm maybe some monitor ... (the problem is on FS side)09:31
freemangordonyes09:31
lufI have no problem with BLUEZ/DBUS but right now it's just function call from gnome-vfs-daemon and response (sync).09:31
freemangordoncould it be that the "serial.connect" call is causing it to stall?09:32
luffreemangordon: however it'll have downside in periodical (?) checking of device status (online/offline).09:32
freemangordonhmm, yep, afaik it blocks in "serial.connect" for the devices not in the range09:33
luffreemangordon: you said that it's not a problem. However only adding some g_warning and checking logs can gives you the answer.09:33
freemangordonluf: :nod:09:33
freemangordonok, i'll do it when have some time09:34
* freemangordon heads for the office09:34
lufI'll add todos: 1) try to change connecting in parallel; 2) try to handle BT devices using some monitor (but how to check availability periodically).09:36
luf1) just inside the one sync call from gnome-vfs-daemon 2) it'll be fully async09:36
luffreemangordon: how long "freeze" do you see because of not reachable 4 devices?09:37
keriohm, is there an obexfs fuse file system?10:07
kerioit would be neat10:07
lufkerio: no idea10:09
*** Martix has joined #maemo-ssu10:18
*** jade has quit IRC11:25
*** jade has joined #maemo-ssu11:25
*** jade has quit IRC11:25
*** jade has joined #maemo-ssu11:25
*** Martix has quit IRC11:42
*** Martix has joined #maemo-ssu11:42
*** Martix has quit IRC11:49
*** andre__ has joined #maemo-ssu12:04
*** andre__ has joined #maemo-ssu12:04
luffreemangordon: ping12:28
luffreemangordon: never mind I had wrong idea12:31
*** gregoa has quit IRC12:37
*** kolp has joined #maemo-ssu12:37
*** gregoa has joined #maemo-ssu12:37
*** Pali has joined #maemo-ssu12:52
*** M4rtinK has joined #maemo-ssu13:08
*** amiconn has quit IRC13:20
*** amiconn has joined #maemo-ssu13:21
*** arcean has joined #maemo-ssu13:21
*** lizardo has joined #maemo-ssu13:40
freemangordonluf: I misexplained it - there is no "freeze", but a device in range which is 5th in the list, gives "unable to connect" error. I guess it is because something times out while bluez(or whoever) tries to connect to the 4 devices not in range13:45
freemangordonotherwise UI is fully responsible all the time13:45
luffreemangordon: can you post me what's in syslog?13:56
luffreemangordon: I think this should be logged (the error why it's unable to connect).13:57
*** BCMM has joined #maemo-ssu13:59
freemangordoncan't do it now, my second device is not with me here in the office14:05
freemangordonwill do later, when back home14:05
freemangordonluf: ^^^14:05
luffreemangordon: ok14:16
*** joshgillies has quit IRC14:34
*** arcean has quit IRC14:53
*** wirr has joined #maemo-ssu15:02
*** xmlich02 has joined #maemo-ssu15:08
*** BCMM has quit IRC15:12
*** luf has quit IRC16:00
*** arcean has joined #maemo-ssu16:48
*** MrPingu has joined #maemo-ssu16:59
*** chainsawbike has quit IRC17:03
*** chainsawbike has joined #maemo-ssu17:04
*** chainsawbike has quit IRC17:16
*** chainsawbike has joined #maemo-ssu17:18
*** amiconn_ has joined #maemo-ssu18:05
*** amiconn has quit IRC18:05
*** amiconn_ is now known as amiconn18:05
freemangordonluf: http://pastebin.com/jUckH5qD18:05
*** toxaris has joined #maemo-ssu18:06
*** toxaris has quit IRC18:28
freemangordonwhy Qt refuses to build?18:33
freemangordonnice, if you have some escaped char in the build path ('+' for example) you can't build Qt :D18:48
*** MrPingu has quit IRC18:53
*** NIN101 has joined #maemo-ssu18:55
*** wumpwoast has joined #maemo-ssu19:02
*** arcean has quit IRC19:47
*** freemangordon has quit IRC19:51
*** freemangordon has joined #maemo-ssu19:51
*** arcean has joined #maemo-ssu20:08
*** arcean_ has joined #maemo-ssu20:14
*** arcean has quit IRC20:14
*** MadeAllUp has joined #maemo-ssu20:19
*** arcean_ is now known as arcean20:42
*** MrPingu has joined #maemo-ssu21:03
*** NIN101 has quit IRC21:04
*** NIN102 has joined #maemo-ssu21:05
*** Martix has joined #maemo-ssu21:20
*** grummund has joined #maemo-ssu21:50
*** dafox has joined #maemo-ssu22:14
*** lizardo has quit IRC22:57
*** LinuxCode has joined #maemo-ssu23:00
*** wirr has left #maemo-ssu23:11
*** MrPingu has quit IRC23:22
*** NIN102 has quit IRC23:43
*** xes has joined #maemo-ssu23:59

Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!