Starting program: /opt/owfs/bin/owfs --foreground --error_level=9 -u /mnt/1wire/
[Thread debugging using libthread_db enabled]
[New Thread -1208842560 (LWP 5372)]
Detaching after fork from child process 5373.
INFO: PARSENAME path=
ERR: Failed to set configuration on USB DS9490 adapter at 003/002.
: Operation not permitted
[New Thread 26201008 (LWP 5374)]
INFO: PARSENAME path=/
INFO: PARSENAME path=/
INFO: ATTRIBUTES path=/
INFO: PARSENAME path=/
INFO: ATTRIBUTES path=/
INFO: PARSENAME path=/
INFO: ATTRIBUTES path=/
INFO: PARSENAME path=/
INFO: DIRECTORY path=/
INFO: PARSENAME path=/
INFO: ATTRIBUTES path=/
INFO: PARSENAME path=/
INFO: ATTRIBUTES path=/
INFO: PARSENAME path=/
INFO: ATTRIBUTES path=/
INFO: PARSENAME path=/
INFO: DIRECTORY path=/
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1208842560 (LWP 5372)]
0x0085d76a in FS_dir (dirfunc=0xbff5fd20, pn=0xbff5fd50) at ow_dir.c:108
108 dirfunc( &pn2 ) ;
(gdb)
Any ideas?
On 9/8/05, Christian Magnusson <[EMAIL PROTECTED]> wrote:
I guess you have to debug this with gdb. Could you try to turn
on the core dumps in your shell:
tcsh: limit coredumpsize unlimited
bash: ulimit -c unlimited
Start owfs and do you crashing ls.
> /opt/owfs/bin/owfs --error_level=9 -u /mnt/1wire/
> ls /mnt/1wire/
Check if any core-file is generated
> ls -l core*
If not, do your ls again.
> ls /mnt/1wire/
Check if any core-file is generated
> ls -l core*
Read the generated core-file with:
> gdb /opt/owfs/bin/owfs core.12345
Show the backtrace.
(gdb) bt
Show all threads backtrace.
(gdb) thread apply all bt
This will give you some information about where the crash occurred .
-------------------------------
You could of course also start owfs from gdb like this:
> gdb /opt/owfs/bin/owfs
(gdb) run --foreground --error_level=9 -u /mnt/1wire/
[do you crashing ls from another shell.]
(gdb) bt
(gdb) thread apply all bt
--------------------------
Does this tell you where owfs (or fuse) crashed?
/Christian
On Wed, 2005-09-07 at 11:45 -0400, Phil Strong wrote:
> Ok with new unit and after I reinstalled both fuse (tested) and owfs
> (newest cvs) I get the following
>
> [EMAIL PROTECTED] /]# /opt/owfs/bin/owfs --error_level=9 -u /mnt/1wire/
> INFO: PARSENAME path=
>
> ERR: Opened USB DS9490 adapter at 002/002.
> : No data available
> INFO: DS9490_setup_adapter: done
>
> INFO: DS9490_overdrive()
>
> INFO: DS9490_reset: ok
>
> INFO: Found device [125494360000009A] on adapter [002/002]
>
> INFO: DS9490_reset: ok
>
> INFO: Found a DS1420 device [817FCD24000000A6]
>
> INFO: Found device [817FCD24000000A6] on adapter [002/002]
>
> INFO: Set DS9490 [817FCD24000000A6] unique id to adapter [002/002]
> [EMAIL PROTECTED] /]# ls /mnt/1wire/
> 12.549436000000 81.7FCD24000000 alarm bus.0 settings statistics
> structure system uncached
> [EMAIL PROTECTED] /]# ls /mnt/1wire/
> ls: reading directory /mnt/1wire/: Software caused connection abort
> [EMAIL PROTECTED] /]# ls /mnt/1wire/
> ls: /mnt/1wire/: Transport endpoint is not connected
>
> When I try it with a different device (thermometer) attached I get
> similar results.
> ___
> [EMAIL PROTECTED] /]# umount /mnt/1wire
> [EMAIL PROTECTED] /]# /opt/owfs/bin/owfs --error_level=9 -u /mnt/1wire/
> INFO: PARSENAME path=
>
> ERR: Opened USB DS9490 adapter at 002/002.
> : No data available
> INFO: DS9490_setup_adapter: done
>
> INFO: DS9490_overdrive()
>
> INFO: DS9490_reset: ok
>
> INFO: Found device [100B3540000000B5] on adapter [002/002]
>
> INFO: DS9490_reset: ok
>
> INFO: Found a DS1420 device [817FCD24000000A6]
>
> INFO: Found device [817FCD24000000A6] on adapter [002/002]
>
> INFO: Set DS9490 [817FCD24000000A6] unique id to adapter [002/002]
> [EMAIL PROTECTED] /]# ls /mnt/1wire/
> 10.0B3540000000 81.7FCD24000000 alarm bus.0 settings simultaneous
> statistics structure system uncached
> [EMAIL PROTECTED] /]# ls /mnt/1wire/
> ls: reading directory /mnt/1wire/: Software caused connection abort
> [EMAIL PROTECTED] /]# ls /mnt/1wire/
> ls: /mnt/1wire/: Transport endpoint is not connected
> ________________________________________________
>
> On 8/31/05, Phil Strong < [EMAIL PROTECTED]> wrote:
> Awesome I will try it when I get home Paul thanks so far for
> all your help.
>
>
> On 8/30/05, Alfille, Paul H.,M.D. < [EMAIL PROTECTED]>
> wrote:
> Hmm... I think both would work well, as well as the
> DS9490 (USB) and the LINK
> adapters.
>
> Before you do that, try something I'm uploading now:
> OWFS-DSL
>
> I mentioned it in another post, but now the unified CD
> image is available.
>
> It is a bootable live-CD distribution with owfs
> already configured.
>
> Download mydsl.iso and burn it to a CD, then boot off
> it. If everything works,
> the problem isn't hardware.
>
> Paul
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED] on
> behalf of Phil Strong
> Sent: Tue 8/30/2005 2:26 PM
> To: [email protected]
> Subject: [Owfs-developers] Which part to buy
>
> I have been having trouble with owfs and my machine
> and want to rule out the
> idea that the serial to 1wire device I have now isn't
> faulty. Currently I
> have a DS9097U-S09 should I buy another one of those
> or something different.
>
> - DS9097U-S09
> - 9-Pin RS-232-C port
> - Communicates with all *i*Buttons, can read but
> not write to
> DS198x EPROM *i*Buttons
> - DS9097U-009
> - 9-Pin RS-232-C port
> - Has internal 64-bit address
> - Communicates with all *i*Buttons, can read but
> not write to
> DS198x EPROM *i*Buttons
>
> get the DS9097U-009? Basically the most trustworthy
> device possible with
> owfs!
>
> --
> Phil Strong
> Synergetic Data Systems
> (w) 240 793 6565
> [EMAIL PROTECTED]
>
>
>
>
>
> --
> Phil Strong
> Synergetic Data Systems
> (w) 240 793 6565
> [EMAIL PROTECTED]
>
>
>
> --
> Phil Strong
> Synergetic Data Systems
> (w) 240 793 6565
> [EMAIL PROTECTED]
--
Phil Strong
Synergetic Data Systems
(w) 240 793 6565
[EMAIL PROTECTED]
