[Sorry Paul, I've canceled this posting twice because of the attachment,
which is to big for the list. Hopefully this one will go through.]
Hi Paul,
On 08/26/2010 09:31 PM, Paul Alfille wrote:
> I tried to replicate tis error on Ubuntu 10.4 using a private mlocate
> database:
>
> updatedb -l 0 -o db_file -U 1wire
>
> But it completes successfully. Indeed, I've run an (older) version of
> owfs and updatedb for years at a time.
>
> There are clearly differences in our setup.
>
> For starters, can you give:
>
> owfs invocation command line
> A directory listing of your 1wire directory.
> /opt/owfs/bin/owfs -V
> updatedb -V
Actually, owfs just segfaulted while I was doing an ls -lR of the 1wire
directory. Guess this explains why updatedb is also causing an owfs
crash. The backtraces in both crashes (caused by ls or by updatedb) are
the same.
I am starting owfs as follows:
/opt/owfs/bin/owserver -d /dev/ttyUSB1 -F --error_print 0 --error_level
1 --nozero
/opt/owfs/bin/owfs --allow_other -F -s localhost:4304 /owfs --nozero
$ /opt/owfs/bin/owfs -V
/opt/owfs/bin/owfs version:
2.8p1
libow version:
2.8p1
$ updatedb -V
updatedb (mlocate) 0.22.2
although I don't think you'll be interested in updatedb anymore.
$ ls -lR /owfs/ > /tmp/owfs.txt
ls: reading directory /owfs/structure/FC/910: Software caused connection
abort
ls: cannot open directory /owfs/structure/FC/eeprom: Transport endpoint
is not connected
ls: cannot open directory /owfs/structure/FC/firmware: Transport
endpoint is not connected
ls: cannot open directory /owfs/structure/FF: Transport endpoint is not
connected
ls: cannot open directory /owfs/structure/simultaneous: Transport
endpoint is not connected
ls: cannot open directory /owfs/structure/thermostat: Transport endpoint
is not connected
ls: cannot open directory /owfs/system: Transport endpoint is not connected
ls: cannot open directory /owfs/uncached: Transport endpoint is not
connected
I have the /tmp/owfs.txt generated by the ls -lR if you want it (46k
compressed), but I can trigger the crash by just doing "ls
/owfs/structure/FC/910".
$ ls -l /owfs/structure/FC
total 0
drwxrwxrwx 1 root root 30 2010-08-26 22:43 910
-r--r--r-- 1 root root 30 2010-08-26 22:28 address
-r--r--r-- 1 root root 30 2010-08-26 22:28 alias
-r--r--r-- 1 root root 30 2010-08-26 22:28 bootstrap_version
-r--r--r-- 1 root root 30 2010-08-26 22:28 chip_type
--w--w--w- 1 root root 30 2010-08-26 22:43 command
-r--r--r-- 1 root root 30 2010-08-26 22:28 crc8
-r--r--r-- 1 root root 30 2010-08-26 22:28 device_type
-r--r--r-- 1 root root 30 2010-08-26 22:28 device_version
drwxrwxrwx 1 root root 30 2010-08-26 22:43 eeprom
-r--r--r-- 1 root root 30 2010-08-26 22:28 family
drwxrwxrwx 1 root root 30 2010-08-26 22:43 firmware
-r--r--r-- 1 root root 30 2010-08-26 22:28 id
-r--r--r-- 1 root root 30 2010-08-26 22:28 localtype
-r--r--r-- 1 root root 30 2010-08-26 22:28 locator
-rw-rw-rw- 1 root root 30 2010-08-26 22:28 memory
-r--r--r-- 1 root root 30 2010-08-26 22:28 r_address
-r--r--r-- 1 root root 30 2010-08-26 22:28 r_id
-r--r--r-- 1 root root 30 2010-08-26 22:28 r_locator
-r--r--r-- 1 root root 30 2010-08-26 22:28 type
-r--r--r-- 1 root root 30 2010-08-26 22:28 version
--w--w--w- 1 root root 30 2010-08-26 22:28 writebyte
There's something about that "910" directory that is causing problems. I
can ls the "eeprom" and "firmware" directories just fine.
I am running Ubuntu 10.04, although my kernel (2.6.35.3) is custom-built.
I ran owfs' configure script like this:
./configure --disable-owperl --disable-zero --enable-debian
Let me know if you'd like to know anything else.
Cheers,
Eloy Paris.-
> On Thu, Aug 26, 2010 at 10:03 AM, Eloy Paris <[email protected]
> <mailto:[email protected]>> wrote:
>
> Hello,
>
> The owfs process is crashing for me everyday at 6:25 AM. Turns out that
> the crash is triggered by updatedb, which gets kicked off daily around
> 6:25 AM by cron to update the locate database.
>
> I've worked around the problem by telling updatedb not to go into the
> owfs-mounted directory but I thought I'd report the problem in case
> someone wants to tackle the root cause to prevent the crash in the first
> place.
>
> I am including below a backtrace, and I am happy to run further tests or
> try any possible fixes. This is completely reproducible for me, though.
>
> Cheers,
>
> Eloy Paris.-
>
> ------------------------------------------------------
>
> (gdb) where
> #0 0x00000000 in ?? ()
> #1 0xb76af543 in BUS_reset (pn=0xb5a12098) at ow_reset.c:23
> #2 0xb76b3b90 in BUS_select_closing (pn=<value optimized out>) at
> ow_select.c:154
> #3 0xb76b3f7f in BUS_select (pn=0xb5a12098) at ow_select.c:78
> #4 0xb76b7b98 in BUS_transaction_single (t=<value optimized out>,
> pn=0x0) at ow_transaction.c:83
> #5 0xb76b827c in BUS_transaction_nolock (tl=0xb6c21938, pn=0xb5a12098)
> at ow_transaction.c:68
> #6 0xb76b84b0 in BUS_transaction (tl=0xb6c21938, pn=0xb5a12098) at
> ow_transaction.c:51
> #7 0xb768902d in OW_type (owq=0xb5a12080) at ow_bae.c:769
> #8 FS_type_state (owq=0xb5a12080) at ow_bae.c:524
> #9 0xb76acc71 in FS_read_lump (owq=0xb5a12080) at ow_read.c:512
> #10 0xb76ad34d in FS_r_local (owq=0xb5a12080) at ow_read.c:460
> #11 0xb76b4b4a in FS_r_sibling_U (U=0xb6c21c5c, sibling=0xb76c32c6
> "typestate", owq=0xb5a12008)
> at ow_sibling_uint.c:54
> #12 0xb7689cca in FS_type_device (owq=0xb5a12008) at ow_bae.c:548
> #13 0xb76acc71 in FS_read_lump (owq=0xb5a12008) at ow_read.c:512
> #14 0xb76ad34d in FS_r_local (owq=0xb5a12008) at ow_read.c:460
> #15 0xb76b4b4a in FS_r_sibling_U (U=0xb6c21f28, sibling=0xb76c32dd
> "device_type", owq=0xb5a11f18)
> at ow_sibling_uint.c:54
> #16 0xb7689e11 in VISIBLE_BAE (pn=0xb6c220c0) at ow_bae.c:296
> #17 VISIBLE_910 (pn=0xb6c220c0) at ow_bae.c:318
> #18 0xb7692c30 in FS_devdir (dirfunc=<value optimized out>, v=<value
> optimized out>, pn_raw_directory=0xb6c220c0,
> flags=0xb6c2206c) at ow_dir.c:376
> #19 FS_dir_both (dirfunc=<value optimized out>, v=<value optimized out>,
> pn_raw_directory=0xb6c220c0,
> flags=0xb6c2206c) at ow_dir.c:124
> #20 0xb769368f in FS_dir (dirfunc=0x80496d0 <FS_getdir_callback>,
> v=0xb6c220b8, pn_directory=0xb6c220c0)
> at ow_dir.c:65
> #21 0x0804966b in FS_getdir (path=0xb5a14138 "/structure/FC/910",
> h=0xb6c22168, filler=0xb762f6d0)
> at owfs_callback.c:186
> #22 0xb762c3d0 in fuse_fs_readdir () from /lib/libfuse.so.2
> #23 0xb7632d26 in ?? () from /lib/libfuse.so.2
> #24 0xb7638e67 in ?? () from /lib/libfuse.so.2
> #25 0xb76377ba in ?? () from /lib/libfuse.so.2
> ---Type <return> to continue, or q <return> to quit---
> #26 0xb763a976 in fuse_session_process () from /lib/libfuse.so.2
> #27 0xb7635dd3 in ?? () from /lib/libfuse.so.2
> #28 0xb75d596e in start_thread () from
> /lib/tls/i686/cmov/libpthread.so.0
> #29 0xb7542a4e in clone () from /lib/tls/i686/cmov/libc.so.6
------------------------------------------------------------------------------
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users
worldwide. Take advantage of special opportunities to increase revenue and
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
