On Sat, May 30, 2009 at 10:42, Matthias Urlichs <[email protected]> wrote: > Hi, > > Rob Fugina: >> one can see that the 1-wire bus master is being repeatedly >> reset for some reason. > > The master itself, or just the bus? > > Bus resets are a normal part of the protocol.
If I had only seen a couple, I wouldn't have brought it up. The fact that hundreds were happening over and over during the period that the client request seemed to be hanging... Here's what I saw, cut from the log file I included in a previous message to the list. I've removed the DEBUG lines to make it easier to find for the moment: Writev byte buffer ionr=2/2 length=38 --000: 2F 31 46 2E 39 34 45 36 30 33 30 30 30 30 30 30 --016: 2F 6D 61 69 6E 2F 31 30 2E 32 35 42 36 30 41 30 --032: 30 30 30 30 30 00 </1F.94E603000000/main/10.25B60A000000.> DATA: ow_ds9490.c:DS9490_reset(855) start DATA: ow_ds9490.c:DS9490_reset(909) ok CALL: ow_parsename.c:FS_ParsedName_anywhere(115) path=[/1F.94E603000000/main/10.55B30A000000] Writev byte buffer ionr=1/2 length=24 --000: 00 00 00 00 00 00 00 26 00 00 00 00 00 01 01 05 --016: 00 00 00 25 00 00 00 00 <.......&...........%....> Writev byte buffer ionr=2/2 length=38 --000: 2F 31 46 2E 39 34 45 36 30 33 30 30 30 30 30 30 --016: 2F 6D 61 69 6E 2F 31 30 2E 35 35 42 33 30 41 30 --032: 30 30 30 30 30 00 </1F.94E603000000/main/10.55B30A000000.> DATA: ow_ds9490.c:DS9490_reset(855) start DATA: ow_ds9490.c:DS9490_reset(909) ok CALL: ow_parsename.c:FS_ParsedName_anywhere(115) path=[/1F.94E603000000/main/10.47B10A000000] Writev byte buffer ionr=1/2 length=24 --000: 00 00 00 00 00 00 00 26 00 00 00 00 00 01 01 05 --016: 00 00 00 25 00 00 00 00 <.......&...........%....> Writev byte buffer ionr=2/2 length=38 --000: 2F 31 46 2E 39 34 45 36 30 33 30 30 30 30 30 30 --016: 2F 6D 61 69 6E 2F 31 30 2E 34 37 42 31 30 41 30 --032: 30 30 30 30 30 00 </1F.94E603000000/main/10.47B10A000000.> DATA: ow_ds9490.c:DS9490_reset(855) start DATA: ow_ds9490.c:DS9490_reset(909) ok CALL: ow_parsename.c:FS_ParsedName_anywhere(115) path=[/1F.94E603000000/main/26.B4A1BC000000] Writev byte buffer ionr=1/2 length=24 --000: 00 00 00 00 00 00 00 26 00 00 00 00 00 01 01 05 --016: 00 00 00 25 00 00 00 00 <.......&...........%....> Writev byte buffer ionr=2/2 length=38 --000: 2F 31 46 2E 39 34 45 36 30 33 30 30 30 30 30 30 --016: 2F 6D 61 69 6E 2F 32 36 2E 42 34 41 31 42 43 30 --032: 30 30 30 30 30 00 </1F.94E603000000/main/26.B4A1BC000000.> DATA: ow_ds9490.c:DS9490_reset(855) start DATA: ow_ds9490.c:DS9490_reset(909) ok CALL: ow_parsename.c:FS_ParsedName_anywhere(115) path=[/1F.94E603000000/main/26.B253B6000000] Writev byte buffer ionr=1/2 length=24 --000: 00 00 00 00 00 00 00 26 00 00 00 00 00 01 01 05 --016: 00 00 00 25 00 00 00 00 <.......&...........%....> I said it's the bus master being reset because I see "DS9490_reset", but since I don't know the code, I could be interpreting it wrong. During this "hang" period, these blocks go by very fast, repeating over the same 6 or so 1-wire devices (all on the same slave bus) over and over and over. Rob ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com _______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
