Re: [Owfs-developers] More on Hanging Problems
Am Dienstag, 21. Juni 2005 13:18 schrieb Alfille, Paul H.,M.D.:
DS2480_reset_errors
DS9097_reset_errors
DS9490_reset_errors
(and perhaps if DS2480_read_timeout is large I think...)
if(DS2480_reset_errors || DS9097_reset_errors || DS9490_reset_errors) {
COM_close(in);
usleep(10);
COM_open(in);
if ( DS2480_detect(in) ) {
if ( DS9097_detect(in) ) {
ret = -ENODEV;
}
}
}
Something like this would probably be enough to make a reset of the
adapter when the 1-wire bus fails.
--
This would work, but there may be a more efficient DS9490_detect, I made
room for the USB device handle in connection_in
in-connin.usb.dev so we can break out the internal part of DS9490_detect
and save re-enumerating the entire USB bus.
Perhaps a fallback of re-enumerating if the simpler routine fails.
Paul
In the meanwhile, I made some logs of the statistics/errors directory:
init.log: Directly after owfs -u1 mnt/1wire
ok1.log: After starting and stopping test.sh
ok2.log: After starting and stopping test.sh again.
So far, no errors. Now the critical ones:
on1.log: After switching the mains transformer ON (blinking stopped before)
on2.log: After starting and stopping test.sh again.
Then I did killall owfs and restarted owfs -u1 mnt/1wire, start test.sh.
off1.log: After switching the mains transformer OFF (blinking stopped
before)
off2.log: After starting and stopping test.sh again.
off3.log is just a repetition of off2.log after killall owfs and restarting
all again.
I hope you now can find a way to detect this kind of error and automatically
re-initialize.
Kind regards
Jan
logs.tar.bz2
Description: application/tbz
Re: [Owfs-developers] More on Hanging Problems
Your logs show mainly BUS_select_low_errors increasing.
Unfortunately there are 5 places in file ow_bus.c function BUS_select_low
where that variable is incremented. I've added some (temporary) printf's to
run the program in foreground and flip the garbalizer.
Can you pull from the latest CVS and try it out?
Once we know which point fails, we can further select that best place to test
for garbage and fix the problem.
Paul
On Friday 24 June 2005 10:01 am, Jan Kandziora wrote:
Am Dienstag, 21. Juni 2005 13:18 schrieb Alfille, Paul H.,M.D.:
DS2480_reset_errors
DS9097_reset_errors
DS9490_reset_errors
(and perhaps if DS2480_read_timeout is large I think...)
if(DS2480_reset_errors || DS9097_reset_errors || DS9490_reset_errors) {
COM_close(in);
usleep(10);
COM_open(in);
if ( DS2480_detect(in) ) {
if ( DS9097_detect(in) ) {
ret = -ENODEV;
}
}
}
Something like this would probably be enough to make a reset of the
adapter when the 1-wire bus fails.
--
This would work, but there may be a more efficient DS9490_detect, I made
room for the USB device handle in connection_in
in-connin.usb.dev so we can break out the internal part of DS9490_detect
and save re-enumerating the entire USB bus.
Perhaps a fallback of re-enumerating if the simpler routine fails.
Paul
In the meanwhile, I made some logs of the statistics/errors directory:
init.log: Directly after owfs -u1 mnt/1wire
ok1.log: After starting and stopping test.sh
ok2.log: After starting and stopping test.sh again.
So far, no errors. Now the critical ones:
on1.log: After switching the mains transformer ON (blinking stopped
before) on2.log: After starting and stopping test.sh again.
Then I did killall owfs and restarted owfs -u1 mnt/1wire, start
test.sh.
off1.log: After switching the mains transformer OFF (blinking stopped
before)
off2.log: After starting and stopping test.sh again.
off3.log is just a repetition of off2.log after killall owfs and restarting
all again.
I hope you now can find a way to detect this kind of error and
automatically re-initialize.
Kind regards
Jan
---
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
[Owfs-developers] Fwd: Re: [fuse-devel] Getting fuse fs type from userspace
I think we should set the filetype to owfs#/dev/ttyS0 or owfs#10.1.2.3:3001 although using multiple buses would be a problem. Perhaps only owfs Paul -- Forwarded Message -- Subject: Re: [fuse-devel] Getting fuse fs type from userspace Date: Thursday 23 June 2005 01:13 pm From: Miklos Szeredi [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED], [EMAIL PROTECTED] However, df and mount just indicate that we're on a fuse fs, which is clearly not enough. Is there a way to get that information? Otherwise, would you be interested in a patch exporting to, lets say, /proc/fuse/ the mounted fs and their types? For my 'fuse' file-system: /proc/mounts shows: muirfs /muirfs fuse rw,user_id=0,group_id=0,default_permissions,allow_other 0 0 Clearly it is showing the correct file-system type. Perhaps this is because in the mount options for my file-system, I use 'fsname=muirfs'. Yes, setting fsname to the filesystem type is a nice way to differentiate different FUSE based filesystems. When you want to use fsname for other information you can set it to type#otherinfo. For example sshfs sets it to sshfs#host:path. Miklos --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ fuse-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fuse-devel --- --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
