Re: [Owfs-developers] Problems in owfs2.p14 DS9490
On Fri, Apr 27, 2012 at 03:53, Michael Markstaller m...@elabnet.de wrote: owfs 2.8p14 is fully unusable/broken with DS9490, maybe I'm just the only one with this constellation (please dissent!) Oh no, I fully agree! The only way working with OWFS and DS9490 are hacks: fall back to older versions improves a litle bit, or regulary restart the owserver process Achim -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Problems in owfs2.p14 DS9490
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 25.04.2012 13:36, schrieb Ivan Lisenkov: Is this patch is in CVS already or I should to patch it by myself? No it isnt and I also would clearly flag it as a hack, I'm no C-programmer and I probably only understand 50% of the code.. But OTOH it fixes at least two essential problems and all of the problems here. And there are real problems, DS9490 gets used wrong, thats for sure, so it cannot work.. Though I dont know why this is disregarded, sorry to say but this is present for many months now, owfs 2.8p14 is fully unusable/broken with DS9490, maybe I'm just the only one with this constellation (please dissent!) Michael -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+Z/CYACgkQaWRHV2kMuALFTwCg+iYq9OnCy6OXtXOxFoKnOO/h VpkAnjaDRcyzeK/tjObvs3MgDJQINwYO =kBTW -END PGP SIGNATURE- -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Problems in owfs2.p14 DS9490
Is this patch is in CVS already or I should to patch it by myself? Best Regards, Ivan, PhD On Sun, Apr 22, 2012 at 9:55 PM, Michael Markstaller m...@elabnet.de wrote: Thanks, I already thought I'm the only one using (several hundred btw) DS9490 in real life ;) Though, I have no single 1w-hub here and maybe I can't explain it good enough but the problem is mainly about (re)initialisation and the reset-stuff, pretty sure in this now.. best regards Michael Am 20.04.2012 23:25, schrieb Mark Richards: THANK YOU THANK YOU THANK YOU! I've been plagued by this issue and was about to give up using some old boards with 2490's. The issue seems to happen when discovering devices behind a switch. Instead of crashing totally, we get a bunch of delays and retries and finally get the data. Nice work! /m -- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Problems in owfs2.p14 DS9490
Thanks, I already thought I'm the only one using (several hundred btw) DS9490 in real life ;) Though, I have no single 1w-hub here and maybe I can't explain it good enough but the problem is mainly about (re)initialisation and the reset-stuff, pretty sure in this now.. best regards Michael Am 20.04.2012 23:25, schrieb Mark Richards: THANK YOU THANK YOU THANK YOU! I've been plagued by this issue and was about to give up using some old boards with 2490's. The issue seems to happen when discovering devices behind a switch. Instead of crashing totally, we get a bunch of delays and retries and finally get the data. Nice work! /m -- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Problems in owfs2.p14 DS9490
THANK YOU THANK YOU THANK YOU! I've been plagued by this issue and was about to give up using some old boards with 2490's. The issue seems to happen when discovering devices behind a switch. Instead of crashing totally, we get a bunch of delays and retries and finally get the data. Nice work! /m On 4/3/2012 7:09 AM, Michael Markstaller wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Getting back on this, attached two patches.. This is definitely no fix but more a works-for-me-HACK! though it might outline where trouble starts.. At least in two of my testbeds it improves owserver running reliable with multiple DS9490 and long networks for days, instead of minutes. Though it still doesn't resolve the problem, that when it hits a reset-error on a null bus without id (which couldn't be), no real action besides a NOOP-loop is IMHO taken. (as comment in patch) The stuff in ow_usb_msg.c is only for debugging. Just adding this, it's easy to see that after an usb-reset the adaptors go on unitialized with wrong settings. best regards, Michael -- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Problems in owfs2.p14 DS9490
Something like: http://owfs.cvs.sourceforge.net/owfs/owfs/module/owlib/src/c/ow_opt.c?r1=1.155r2=1.156 ;) Getting back on the subject: Would be good if someone with a real installation, longmany BM would also test, it improved reliability here by many 100%.. Also compared with 2.8p2 Never had a runtime of owserve 2d since 2.7p34 ;) One of the main reasons might also be the changed PARMSET_Slew1p10Vus I guess (I'll cross-verify this again if it runs fine for some days, never had it running for 6hrs before!) - on a known broken installation, but now: that happens in life.. Michael Am 04.04.2012 04:36, schrieb Roberto Spadim: sorry i wrote wrong... could you make a patch that put ow version at debug output? :) Em 3 de abril de 2012 23:18, Michael Markstaller m...@elabnet.de mailto:m...@elabnet.de escreveu: Am 03.04.2012 16:48, schrieb Roberto Spadim: hi, could you add a version information at debug output too? maybe at the start of ow program, just to us know what's the version... this could be easier to know what we are debugging There was no Debug-output in my post, the version is in the subject, but this feature is already in CVS AFAIK ;) I'd be happy to use it, but owfs is - sorry for direct speech - really very broken regarding the stock USB-adaptors for quite a while now, thats my issue, not in which version,, Michael -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net mailto:Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Roberto Spadim Spadim Technology / SPAEmpresarial -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Michael Markstaller Elaborated Networks GmbH www.elabnet.de - www.wiregate.de Lise-Meitner-Str. 1, D-85662 Hohenbrunn, Germany fon: +49-8102-8951-60, fax: +49-8102-8951-80 Geschäftsführer: Stefan Werner, Michael Markstaller Amtsgericht München HRB 125120, Ust-ID: DE201281054 -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Problems in owfs2.p14 DS9490
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Getting back on this, attached two patches..
This is definitely no fix but more a works-for-me-HACK! though it
might outline where trouble starts..
At least in two of my testbeds it improves owserver running reliable
with multiple DS9490 and long networks for days, instead of minutes.
Though it still doesn't resolve the problem, that when it hits a
reset-error on a null bus without id (which couldn't be), no real
action besides a NOOP-loop is IMHO taken. (as comment in patch)
The stuff in ow_usb_msg.c is only for debugging. Just adding this,
it's easy to see that after an usb-reset the adaptors go on
unitialized with wrong settings.
best regards,
Michael
Am 17.03.2012 17:23, schrieb Michael Markstaller:
I changed the subject..
Am 16.03.2012 14:49, schrieb Paul Alfille:
To hunt this down, you find that heavy USB activity causes
communication failures and puts owfs is an unusable state?
No, I don't think thats a root cause. My last tests where done with
only 1-4 DS9490R on a powered hub without any other USB-devices
active. Maybe heavy USB-traffic or long-lines intensify the problem
but it also happens in simle setups.
Referring to my post:
http://article.gmane.org/gmane.comp.file-systems.owfs.devel/9120
#1) is pretty reproduceable, just a matter of time (minutes to
hours), regardless wether there is one DS9490 and one sensor or 6
and 50.. (leads to #2): the mode-register isn't set after a
subsequent PoR of the DS2490 IMHO, only initially, so it's set to
standard instead of flexible speed which doesn't work
reliable. #3 (long lines): I *think* its mostly #1+#2: reset_errors
occur faster on long lines and after the reset the BM is running at
standard vs. flexible speed which then worses the problem until all
sensors (including the 81.xx id-chip!) is lost.
As fas as I understand the code, what happens then is trying to
reset/reconnect the lost BM resulting in a noop: DEBUG:
ow_ds9490.c:(513) Attempting RESET on null bus DEBUG:
ow_reset.c:(48) Reset error. Reconnection 4/2
until a restart of owserver the whole bus is lost
I experienced the problems with openwrt (current trunk)
owfs2.8p8/p14 and was able to reproduce them easily with 2.8p14 on
ubuntu 11.10
(#4 this might be related or not) - under openwrt I get masses of
usb 1-1.1: usbfs: usb_submit_urb returned -28 in dmesg
I need to create a test bed to mimic and correct this.
Would be no issue to setup some systems for testing!
best regards
Michael
--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
___ Owfs-developers
mailing list Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk962lsACgkQaWRHV2kMuAL5oACeKI6g7RXbpcEjuSzmdmiGNUl5
46YAn1wGNog/F24zMGXKjUABMOuM0pt2
=DetY
-END PGP SIGNATURE-
--- owfs-2.8p14/module/owlib/src/c/ow_ds9490.c 2011-12-11 03:29:48.0 +0100
+++ module/owlib/src/c/ow_ds9490.c 2012-04-03 12:39:47.419243139 +0200
@@ -506,8 +506,10 @@
struct connection_in * in = pn-selected_connection ;
int readlen = 0 ;
+ LEVEL_DEBUG(DS9490 RESET. changed %d, flex: %d, in-changed_bus_settings, in-flex) ;
+
if (in-master.usb.usb == NULL || in-master.usb.dev == NULL) {
- LEVEL_DEBUG(Attempting RESET on null bus) ;
+ LEVEL_DEBUG(Attempting RESET on null bus %d/%d, in-master.usb.usb, in-master.usb.dev) ; //FIXME! what doees it mean? no action/reconnect is even tried- shouldn't we just drop this BM and let uscan rediscover it? DS9490 must always have an ID chip..
return BUS_RESET_ERROR;
}
@@ -530,7 +532,8 @@
}
// Send reset
- if ( BAD( USB_Control_Msg(COMM_CMD, COMM_1_WIRE_RESET | COMM_F | COMM_IM | COMM_SE, USpeed, pn)) ) {
+ //FIXME: MM/ changed hard to flexible speed as it gets wrong somewhere, only want flexible
+ if ( BAD( USB_Control_Msg(COMM_CMD, COMM_1_WIRE_RESET | COMM_F | COMM_IM | COMM_SE, ONEWIREBUSSPEED_FLEXIBLE, pn)) ) {
LEVEL_DATA(Reset command rejected);
return BUS_RESET_ERROR; // fatal error... probably closed usb-handle
}
@@ -545,18 +548,41 @@
switch( DS9490_getstatus(buffer, readlen, pn) ) {
case BUS_RESET_SHORT:
/* Short detected, but otherwise no bigger problem */
+ LEVEL_DEBUG(DS9490_Reset: SHORT);
return BUS_RESET_SHORT ;
case BUS_RESET_OK:
+ LEVEL_DEBUG(DS9490_Reset: OK);
break ;
case BUS_RESET_ERROR:
default:
- return BUS_RESET_ERROR;
+ LEVEL_DEBUG(DS9490_Reset: ERROR);
+ /* FIXME: FIXED. In ow_usb_msg.c an USB-reset was was issued:
+ * USB_Control_Msg(CONTROL_CMD, CTL_RESET_DEVICE, 0x, pn) ;
+ * So we need to setup the Adapter again
+ *
Re: [Owfs-developers] Problems in owfs2.p14 DS9490
hi, could you add a version information at debug output too? maybe at the start of ow program, just to us know what's the version... this could be easier to know what we are debugging Em 3 de abril de 2012 08:09, Michael Markstaller m...@elabnet.de escreveu: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Getting back on this, attached two patches.. This is definitely no fix but more a works-for-me-HACK! though it might outline where trouble starts.. At least in two of my testbeds it improves owserver running reliable with multiple DS9490 and long networks for days, instead of minutes. Though it still doesn't resolve the problem, that when it hits a reset-error on a null bus without id (which couldn't be), no real action besides a NOOP-loop is IMHO taken. (as comment in patch) The stuff in ow_usb_msg.c is only for debugging. Just adding this, it's easy to see that after an usb-reset the adaptors go on unitialized with wrong settings. best regards, Michael Am 17.03.2012 17:23, schrieb Michael Markstaller: I changed the subject.. Am 16.03.2012 14:49, schrieb Paul Alfille: To hunt this down, you find that heavy USB activity causes communication failures and puts owfs is an unusable state? No, I don't think thats a root cause. My last tests where done with only 1-4 DS9490R on a powered hub without any other USB-devices active. Maybe heavy USB-traffic or long-lines intensify the problem but it also happens in simle setups. Referring to my post: http://article.gmane.org/gmane.comp.file-systems.owfs.devel/9120 #1) is pretty reproduceable, just a matter of time (minutes to hours), regardless wether there is one DS9490 and one sensor or 6 and 50.. (leads to #2): the mode-register isn't set after a subsequent PoR of the DS2490 IMHO, only initially, so it's set to standard instead of flexible speed which doesn't work reliable. #3 (long lines): I *think* its mostly #1+#2: reset_errors occur faster on long lines and after the reset the BM is running at standard vs. flexible speed which then worses the problem until all sensors (including the 81.xx id-chip!) is lost. As fas as I understand the code, what happens then is trying to reset/reconnect the lost BM resulting in a noop: DEBUG: ow_ds9490.c:(513) Attempting RESET on null bus DEBUG: ow_reset.c:(48) Reset error. Reconnection 4/2 until a restart of owserver the whole bus is lost I experienced the problems with openwrt (current trunk) owfs2.8p8/p14 and was able to reproduce them easily with 2.8p14 on ubuntu 11.10 (#4 this might be related or not) - under openwrt I get masses of usb 1-1.1: usbfs: usb_submit_urb returned -28 in dmesg I need to create a test bed to mimic and correct this. Would be no issue to setup some systems for testing! best regards Michael -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk962lsACgkQaWRHV2kMuAL5oACeKI6g7RXbpcEjuSzmdmiGNUl5 46YAn1wGNog/F24zMGXKjUABMOuM0pt2 =DetY -END PGP SIGNATURE- -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Roberto Spadim Spadim Technology / SPAEmpresarial -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Problems in owfs2.p14 DS9490
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 03.04.2012 16:48, schrieb Roberto Spadim: hi, could you add a version information at debug output too? maybe at the start of ow program, just to us know what's the version... this could be easier to know what we are debugging There was no Debug-output in my post, the version is in the subject, but this feature is already in CVS AFAIK ;) I'd be happy to use it, but owfs is - sorry for direct speech - really very broken regarding the stock USB-adaptors for quite a while now, thats my issue, not in which version,, Michael -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk97r14ACgkQaWRHV2kMuAJ9AgCgx+YQtaxL9y2dkKPpqYarIdfG b+UAoIIdB3utAPa3gLGM1TMEAZiXgUFI =mpVS -END PGP SIGNATURE- -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Problems in owfs2.p14 DS9490
sorry i wrote wrong... could you make a patch that put ow version at debug output? :) Em 3 de abril de 2012 23:18, Michael Markstaller m...@elabnet.de escreveu: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 03.04.2012 16:48, schrieb Roberto Spadim: hi, could you add a version information at debug output too? maybe at the start of ow program, just to us know what's the version... this could be easier to know what we are debugging There was no Debug-output in my post, the version is in the subject, but this feature is already in CVS AFAIK ;) I'd be happy to use it, but owfs is - sorry for direct speech - really very broken regarding the stock USB-adaptors for quite a while now, thats my issue, not in which version,, Michael -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk97r14ACgkQaWRHV2kMuAJ9AgCgx+YQtaxL9y2dkKPpqYarIdfG b+UAoIIdB3utAPa3gLGM1TMEAZiXgUFI =mpVS -END PGP SIGNATURE- -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Roberto Spadim Spadim Technology / SPAEmpresarial -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Problems in owfs2.p14 DS9490
I changed the subject.. Am 16.03.2012 14:49, schrieb Paul Alfille: To hunt this down, you find that heavy USB activity causes communication failures and puts owfs is an unusable state? No, I don't think thats a root cause. My last tests where done with only 1-4 DS9490R on a powered hub without any other USB-devices active. Maybe heavy USB-traffic or long-lines intensify the problem but it also happens in simle setups. Referring to my post: http://article.gmane.org/gmane.comp.file-systems.owfs.devel/9120 #1) is pretty reproduceable, just a matter of time (minutes to hours), regardless wether there is one DS9490 and one sensor or 6 and 50.. (leads to #2): the mode-register isn't set after a subsequent PoR of the DS2490 IMHO, only initially, so it's set to standard instead of flexible speed which doesn't work reliable. #3 (long lines): I *think* its mostly #1+#2: reset_errors occur faster on long lines and after the reset the BM is running at standard vs. flexible speed which then worses the problem until all sensors (including the 81.xx id-chip!) is lost. As fas as I understand the code, what happens then is trying to reset/reconnect the lost BM resulting in a noop: DEBUG: ow_ds9490.c:(513) Attempting RESET on null bus DEBUG: ow_reset.c:(48) Reset error. Reconnection 4/2 until a restart of owserver the whole bus is lost I experienced the problems with openwrt (current trunk) owfs2.8p8/p14 and was able to reproduce them easily with 2.8p14 on ubuntu 11.10 (#4 this might be related or not) - under openwrt I get masses of usb 1-1.1: usbfs: usb_submit_urb returned -28 in dmesg I need to create a test bed to mimic and correct this. Would be no issue to setup some systems for testing! best regards Michael -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
