|
From: Frank M. H. <fm...@us...> - 2003-05-20 22:11:06
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 20 May 2003 01:54 pm, Neil Phipps wrote: > Hi Frank, > > Here's the lspci output ... it seems to make sense, it shows the two > computer boards I have in the system, one is the 96 bit DIO card and th= e > other is the GPIB card ... it should be the 1 MHz versioon, that's why = I > used cbi_pci_accel, but I did try it with the regular cbi_pci and got > the same result ... using gdb it seems the segfault occurs almost befor= e > anything else happens ... I'll put in some breakpoints and send you mor= e > detailed info shortly, but for now, at least here's the lspci -v output > ... > It's unfortunate that Measurement Computing has assigned the same pci=20 device id to the 300k and 1M versions of their board, and they don't even= =20 appear to be compatible. During 'make config', you should turn on=20 debugging symbols in the library (which should help gdb), and debugging=20 output for the kernel modules (which will produce a lot of spam in your=20 kernel logs). Also, have you checked your kernel logs for a ksymoops=20 message when the segfault occurs?=20 - --=20 Frank -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE+yqdD5vihyNWuA4URAlVcAJ9eDRCtZWjaCMMwnfrtYWy0qtc6BwCfd/iz dlZBn73BdO9qQqrykEgwX5g=3D =3D5DnE -----END PGP SIGNATURE----- |