ANN: 1.17.900 released (unstable)

Tang Nguyen tang_nguyen at yahoo.com
Wed Jan 25 21:23:56 UTC 2017


Hi Alek,

Here are backtrace from gdb.  Your hints are greatly appreciated .. :)


(gdb) run -w /dev/cdc-wdm0 -u SWI9X15C_05.05.58.01.cwe SWI9X15C_05.05.58.01_Verizon_005.029_001.nvu
Starting program: /usr/bin/qmi-firmware-update -w /dev/cdc-wdm0 -u SWI9X15C_05.05.58.01.cwe SWI9X15C_05.05.58.01_Verizon_005.029_001.nvu
warning: Could not load shared library symbols for linux-vdso32.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/powerpc-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x69636570 in ?? ()
(gdb) backtrace 
#0  0x69636570 in ?? ()
#1  0x0f826284 in ?? () from /lib/powerpc-linux-gnu/libudev.so.1
#2  0x0f828f84 in udev_device_new_from_syspath () from /lib/powerpc-linux-gnu/libudev.so.1
#3  0x0f82a400 in ?? () from /lib/powerpc-linux-gnu/libudev.so.1
#4  0x0f828264 in udev_device_get_parent () from /lib/powerpc-linux-gnu/libudev.so.1
#5  0x0ffdb5dc in g_udev_device_get_parent () from /usr/lib/powerpc-linux-gnu/libgudev-1.0.so.0
#6  0x10009294 in udev_helper_get_udev_device_details (device=device at entry=0x10035450, out_sysfs_path=0x1003acc8, out_sysfs_path at entry=0xbffff978, out_vid=out_vid at entry=0x0, 
    out_pid=out_pid at entry=0x0, out_busnum=0xbffff4ed, out_busnum at entry=0x0, out_devnum=out_devnum at entry=0x0, error=error at entry=0xbffffa38) at qfu-udev-helpers.c:126
#7  0x10009db8 in qfu_udev_helper_find_by_file (file=file at entry=0x10034b30, error=0xbffffa38) at qfu-udev-helpers.c:213
#8  0x10009ee8 in qfu_udev_helper_find_by_file_path (path=<optimized out>, error=error at entry=0xbffffa38) at qfu-udev-helpers.c:229
#9  0x10004ca8 in qfu_device_selection_new (preferred_cdc_wdm=0x10034f78 "/dev/cdc-wdm0", preferred_tty=0x0, preferred_vid=<optimized out>, preferred_pid=<optimized out>, 
    preferred_busnum=0, preferred_devnum=0, error=error at entry=0xbffffa38) at qfu-device-selection.c:266
#10 0x10003b30 in main (argc=1, argv=0xbffffcc4) at qfu-main.c:550
(gdb) 


--------------------------------------------
On Wed, 1/25/17, Tang Nguyen <tang_nguyen at yahoo.com> wrote:

 Subject: Re: ANN: 1.17.900 released (unstable)
 To: "Tang Nguyen" <tang_nguyen at yahoo.com>, "Aleksander Morgado" <aleksander at aleksander.es>
 Cc: "libqmi (development)" <libqmi-devel at lists.freedesktop.org>
 Date: Wednesday, January 25, 2017, 4:00 PM
 
 
 --------------------------------------------
 On Wed, 1/25/17, Aleksander Morgado <aleksander at aleksander.es>
 wrote:
 
  Subject: Re: ANN: 1.17.900 released (unstable)
  To: "Tang Nguyen" <tang_nguyen at yahoo.com>
  Cc: "libqmi (development)" <libqmi-devel at lists.freedesktop.org>
  Date: Wednesday, January 25, 2017, 2:27 PM
  
  On Tue, Jan 24, 2017 at
  11:13 PM, Tang Nguyen <tang_nguyen at yahoo.com>
  wrote:
  > On Tue, Jan 24, 2017 at
  >  9:56 PM, Tang Nguyen <tang_nguyen at yahoo.com>
  >  wrote:
  >  > I got
  Segment fault when i tried
  >  to update
  the firmware on MC7350.  syslog just shows me
  >  this:
  >  >
  >  > Jan 24
  > 
  15:36:23 ruggedcom kernel: [  290.007349]
  >  qmi-firmware-up[6487]: unhandled signal
  11 at 69636570 nip
  >  69636570 lr
  0f826284 code 30001
  >  >
  >  > dmesg showed the same thing - no
  more
  >  further information.
  >  >
  >  > My
  kernel is 3.14, plus 3 patches to
  > 
  support raw-ip mode.  Should I need to apply any patch
  to
  >  support qmi-firmware-update tool
  ?
  >
  >  No patches
  needed I think.
  >
  > 
  Is it reproducible? If so, can you run it under
  >
  > Tang: yes, 100%
  happend, Alek
  >
  > 
  gdb and get a
  >  backtrace, maybe also
  using -L
  >  /tmp/qfu.log?
  >
  > Tang: OKay, I'll
  try to set up the gdb debugger
  >
  >  Which image
  >  files
  were you using?
  >
  >
  Tang: I tried both image file: *.SPK and *CWE, *NVU file
 as
  shown from  "--help-examples "
  >
  >  Which
  >  was the full list of command line
  options used?
  >
  >
  Tang: my full command;
  >
  >  qmi-firmware-update -w /dev/cdc-wdm0 -u
  SWI9X15C_05.05.58.01.cwe
  SWI9X15C_05.05.58.01_Verizon_005.029_001.nvu
  
  Ok thanks. Please try to get a
  backtrace with gdb.
  
  Which
  system is this, btw?
  
 Tang: I am testing on PowerPC embedded system, running
 Debian Linux.
 
  -- 
  Aleksander
  https://aleksander.es
  _______________________________________________
  libqmi-devel mailing list
  libqmi-devel at lists.freedesktop.org
  https://lists.freedesktop.org/mailman/listinfo/libqmi-devel
  


More information about the libqmi-devel mailing list