Fusermount crash?

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Fusermount crash?

Matthew Dickinson-6
Hi,

Running kernel 2.4.29, on a Debian machine with fuse-2.3.0, libusb-0.1.10a
and owfs.

When trying to mount OWFS via a USB device, it appears that fusermount broke
:-(

Am I coming to the right place? Or is this libusb/owfs related instead?

Thanks,

Matthew

Jul 24 21:01:47 localhost kernel: Unable to handle kernel paging request at
virtual address fffffffc
Jul 24 21:01:47 localhost kernel:  printing eip:
Jul 24 21:01:47 localhost kernel: c0113370
Jul 24 21:01:47 localhost kernel: *pde = 00021063
Jul 24 21:01:47 localhost kernel: *pte = 00000000
Jul 24 21:01:47 localhost kernel: Oops: 0000
Jul 24 21:01:47 localhost kernel: CPU:    0
Jul 24 21:01:47 localhost kernel: EIP:    0010:[__wake_up+32/160]    Not
tainted
Jul 24 21:01:47 localhost kernel: EFLAGS: 00010017
Jul 24 21:01:47 localhost kernel: eax: c77ac978   ebx: 00000000   ecx:
00000001   edx: 00000003
Jul 24 21:01:47 localhost kernel: esi: c5bafba0   edi: c77ac978   ebp:
c6a17db0   esp: c6a17d98
Jul 24 21:01:47 localhost kernel: ds: 0018   es: 0018   ss: 0018
Jul 24 21:01:47 localhost kernel: Process fusermount (pid: 5774,
stackpage=c6a17000)
Jul 24 21:01:47 localhost kernel: Stack: 00000001 00000286 00000003 c77ac960
c5bafba0 c7aee000 c6a17dd0 c88f8728
Jul 24 21:01:47 localhost kernel:        c5bafba0 c77ac960 c88fc150 c6a17dec
00000000 00004000 c6a17df0 c88f87a4
Jul 24 21:01:47 localhost kernel:        c77ac960 c5bafba0 c6a17e60 c88fc981
c7aee000 00000001 c6a17e20 c88f8801
Jul 24 21:01:47 localhost kernel: Call Trace:
[usbcore:usb_devfs_handle_Re9c5f87f+644472/95842749]
[usbcore:usb_devfs_handle_Re9c5f87f+659360/95827861]
[usbcore:usb_devfs_handle_Re9c5f87f+644596/95842625]
[usbcore:usb_devfs_handle_Re9c5f87f+661457/95825764]
[usbcore:usb_devfs_handle_Re9c5f87f+644689/95842532]
Jul 24 21:01:47 localhost kernel:
[usbcore:usb_devfs_handle_Re9c5f87f+644791/95842430]
[usbcore:usb_devfs_handle_Re9c5f87f+644715/95842506] [d_alloc_root+75/96]
[usbcore:usb_devfs_handle_Re9c5f87f+661682/95825539]
[usbcore:usb_devfs_handle_Re9c5f87f+661552/95825669]
[usbcore:usb_devfs_handle_Re9c5f87f+665600/95821621]
Jul 24 21:01:47 localhost kernel:   [do_page_fault+512/1287]
[__generic_copy_from_user+48/96]
[usbcore:usb_devfs_handle_Re9c5f87f+661745/95825476]
[usbcore:usb_devfs_handle_Re9c5f87f+665600/95821621]
[usbcore:usb_devfs_handle_Re9c5f87f+665600/95821621]
[usbcore:usb_devfs_handle_Re9c5f87f+665600/95821621]
Jul 24 21:01:47 localhost kernel:
[usbcore:usb_devfs_handle_Re9c5f87f+665600/95821621] [get_sb_nodev+56/128]
[usbcore:usb_devfs_handle_Re9c5f87f+665600/95821621] [do_kern_mount+217/256]
[usbcore:usb_devfs_handle_Re9c5f87f+665600/95821621] [do_add_mount+117/352]
Jul 24 21:01:47 localhost kernel:   [do_mount+307/400]
[copy_mount_options+77/160] [sys_mount+138/192] [system_call+51/64]
Jul 24 21:01:47 localhost kernel:
Jul 24 21:01:47 localhost kernel: Code: 8b 4b fc 8b 01 85 45 f0 74 26 31 c0
9c 5e fa 8b 51 3c c7 01
Jul 24 21:01:47 localhost kernel:  <1>Unable to handle kernel paging request
at virtual address fffffffc
Jul 24 21:01:47 localhost kernel:  printing eip:
Jul 24 21:01:47 localhost kernel: c0113370
Jul 24 21:01:47 localhost kernel: *pde = 00021063
Jul 24 21:01:47 localhost kernel: *pte = 00000000
Jul 24 21:01:47 localhost kernel: Oops: 0000
Jul 24 21:01:47 localhost kernel: CPU:    0
Jul 24 21:01:47 localhost kernel: EIP:    0010:[__wake_up+32/160]    Not
tainted
Jul 24 21:01:47 localhost kernel: EFLAGS: 00010003
Jul 24 21:01:47 localhost kernel: eax: c5bafc30   ebx: 00000000   ecx:
00000001   edx: 00000003
Jul 24 21:01:47 localhost kernel: esi: c77ac960   edi: c5bafc30   ebp:
c6a17ba0   esp: c6a17b88
Jul 24 21:01:47 localhost kernel: ds: 0018   es: 0018   ss: 0018
Jul 24 21:01:47 localhost kernel: Process fusermount (pid: 5774,
stackpage=c6a17000)
Jul 24 21:01:47 localhost kernel: Stack: 00000001 00000286 00000003 c77ac9b4
c77ac960 c5bafba0 c6a17bc0 c88f8406
Jul 24 21:01:47 localhost kernel:        c77ac984 c77ac960 c761de00 c6a1ddcc
00000046 00000001 c6a17bf0 c88f9352
Jul 24 21:01:47 localhost kernel:        c77ac960 c5bafba0 c6b15880 c6b151c8
c77ac960 c11653e0 c01fedc1 00000246
Jul 24 21:01:47 localhost kernel: Call Trace:
[usbcore:usb_devfs_handle_Re9c5f87f+643670/95843551]
[usbcore:usb_devfs_handle_Re9c5f87f+647586/95839635]
[unix_release_sock+449/496]
[usbcore:usb_devfs_handle_Re9c5f87f+647642/95839579] [dput+211/336]
Jul 24 21:01:47 localhost kernel:   [fput+223/256] [filp_close+55/96]
[put_files_struct+87/176] [do_exit+157/560] [die+83/96]
[do_page_fault+710/1287]
Jul 24 21:01:47 localhost kernel:
[usbcore:usb_devfs_handle_Re9c5f87f+661796/95825425]
[kmem_cache_grow+408/560]
[usbcore:usb_devfs_handle_Re9c5f87f+658640/95828581]
[usbcore:usb_devfs_handle_Re9c5f87f+642763/95844458]
[usbcore:usb_devfs_handle_Re9c5f87f+658666/95828555]
[usbcore:usb_devfs_handle_Re9c5f87f+658742/95828479]
Jul 24 21:01:47 localhost OWFS[5773]: Closed USB DS9490 adapter at (null).
Jul 24 21:01:47 localhost kernel:   [ext2_find_entry+122/432]
[do_page_fault+0/1287] [error_code+52/64] [__wake_up+32/160]
[usbcore:usb_devfs_handle_Re9c5f87f+644472/95842749]
[usbcore:usb_devfs_handle_Re9c5f87f+659360/95827861]
Jul 24 21:01:47 localhost kernel:
[usbcore:usb_devfs_handle_Re9c5f87f+644596/95842625]
[usbcore:usb_devfs_handle_Re9c5f87f+661457/95825764]
[usbcore:usb_devfs_handle_Re9c5f87f+644689/95842532]
[usbcore:usb_devfs_handle_Re9c5f87f+644791/95842430]
[usbcore:usb_devfs_handle_Re9c5f87f+644715/95842506] [d_alloc_root+75/96]
Jul 24 21:01:47 localhost kernel:
[usbcore:usb_devfs_handle_Re9c5f87f+661682/95825539]
[usbcore:usb_devfs_handle_Re9c5f87f+661552/95825669]
[usbcore:usb_devfs_handle_Re9c5f87f+665600/95821621]
[do_page_fault+512/1287] [__generic_copy_from_user+48/96]
[usbcore:usb_devfs_handle_Re9c5f87f+661745/95825476]
Jul 24 21:01:47 localhost kernel:
[usbcore:usb_devfs_handle_Re9c5f87f+665600/95821621]
[usbcore:usb_devfs_handle_Re9c5f87f+665600/95821621]
[usbcore:usb_devfs_handle_Re9c5f87f+665600/95821621]
[usbcore:usb_devfs_handle_Re9c5f87f+665600/95821621] [get_sb_nodev+56/128]
[usbcore:usb_devfs_handle_Re9c5f87f+665600/95821621]
Jul 24 21:01:47 localhost kernel:   [do_kern_mount+217/256]
[usbcore:usb_devfs_handle_Re9c5f87f+665600/95821621] [do_add_mount+117/352]
[do_mount+307/400] [copy_mount_options+77/160] [sys_mount+138/192]
Jul 24 21:01:47 localhost kernel:   [system_call+51/64]



-------------------------------------------------------
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=7477&alloc_id=16492&op=click
_______________________________________________
fuse-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fuse-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Fusermount crash?

Miklos Szeredi
> Running kernel 2.4.29, on a Debian machine with fuse-2.3.0, libusb-0.1.10a
> and owfs.
>
> When trying to mount OWFS via a USB device, it appears that fusermount broke
> :-(
>
> Am I coming to the right place?

I think you are.

Is it reproducible?  

The syslog trace you sent is slightly garbled, so it would be better
to get a clean trace with 'dmesg | ksymoops' after the mount failure.

Thanks,
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=7477&alloc_id=16492&op=click
_______________________________________________
fuse-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fuse-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: Fusermount crash?

Matthew Dickinson-6
Miklos Szeredi wrote:
> Is it reproducible?

Yeah, it happens every time I try to mount owfs - and even just running
"example/fusexmp"

>
> The syslog trace you sent is slightly garbled, so it would be better
> to get a clean trace with 'dmesg | ksymoops' after the mount failure.

Please find attached,

Thanks,

Matthew

oops.txt (6K) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Fusermount crash?

Miklos Szeredi
> >
> > The syslog trace you sent is slightly garbled, so it would be better
> > to get a clean trace with 'dmesg | ksymoops' after the mount failure.
>
> Please find attached,

Still no good.  The call trace is totally bogus.  Seems like it's been
processed by syslog.  Did you use 'dmesg' to get the raw Oops output?

Also the first Oops after a reboot would be nice.  Sometimes the later
Oopses are just secondary effects of the first.

Thanks,
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=7477&alloc_id=16492&op=click
_______________________________________________
fuse-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fuse-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Fusermount crash?

Matthew Dickinson-6
In reply to this post by Matthew Dickinson-6
> Still no good.  The call trace is totally bogus.  Seems like it's been
> processed by syslog.  Did you use 'dmesg' to get the raw Oops output?
>
> Also the first Oops after a reboot would be nice.  Sometimes the later
> Oopses are just secondary effects of the first.
>
> Thanks,
> Miklos

There's no oops in dmesg - i've manually been trying to mount the
filesystem, but i'll set it up to try at boot time.

Rather than doing it with owfs, even the unmodified fusexmp when run from
command prompt causes the oops (which is reported to syslog, nothing to
the active console).

I'll try and get a "better" oops tonight,

thanks,

Matthew


-------------------------------------------------------
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=7477&alloc_id=16492&op=click
_______________________________________________
fuse-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fuse-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Fusermount crash?

Miklos Szeredi
> There's no oops in dmesg

That's impossible.

You shouldn't be looking at /var/log/dmesg, that's something
different.  Rather the output of the 'dmesg' program.

> - i've manually been trying to mount the filesystem, but i'll set it
> up to try at boot time.

No need to mount at boot time.  You can mount by hand, just be sure to
record the dmesg output after the first attemted mount.

> Rather than doing it with owfs, even the unmodified fusexmp when run from
> command prompt causes the oops (which is reported to syslog, nothing to
> the active console).
>
> I'll try and get a "better" oops tonight,

OK, thanks for your effort.

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=7477&alloc_id=16492&op=click
_______________________________________________
fuse-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fuse-devel
Loading...