Re: HELP! iSCSI qla4010 HBA driver problems.

From: Jimmy McMillan (jimmy_at_freshstation.org)
Date: 05/31/05

  • Next message: Les Mikesell: "Re: General routing question?" 
    Date: Tue, 31 May 2005 12:10:41 -0400
To: For users of Fedora Core releases <fedora-list@redhat.com>

    Awesome, got it compiled, and probed. So far so good. I got a few
    warnings included at compile time, but all in all it's working. I'm
    gonna setup random writes to the device for a day to see if it
    eventually fails. It's so random. Thanks alot Andy!

    qla4xxx -- Building the qla4xxx driver...
    make: Entering directory `/lib/modules/2.6.11-1.27_FC3smp/build'
      CC [M] /usr/src/qlogic/v5.00.02-1/5.00.02/ql4_os.o
      CC [M] /usr/src/qlogic/v5.00.02-1/5.00.02/ql4_init.o
      CC [M] /usr/src/qlogic/v5.00.02-1/5.00.02/ql4_mbx.o
      CC [M] /usr/src/qlogic/v5.00.02-1/5.00.02/ql4_iocb.o
      CC [M] /usr/src/qlogic/v5.00.02-1/5.00.02/ql4_isr.o
    /usr/src/qlogic/v5.00.02-1/5.00.02/ql4_isr.c: In function
    `qla4xxx_check_and_copy_sense':
    /usr/src/qlogic/v5.00.02-1/5.00.02/ql4_isr.c:161: warning: ISO C90
    forbids mixed declarations and code
    /usr/src/qlogic/v5.00.02-1/5.00.02/ql4_os.c: In function
    `qla4xxx_config_dma_addressing':
    /usr/src/qlogic/v5.00.02-1/5.00.02/ql4_os.c:876: warning: ignoring
    return value of `pci_set_consistent_dma_mask', declared with attribute
    warn_unused_result
    /usr/src/qlogic/v5.00.02-1/5.00.02/ql4_os.c:884: warning: ignoring
    return value of `pci_set_dma_mask', declared with attribute
    warn_unused_result
      CC [M] /usr/src/qlogic/v5.00.02-1/5.00.02/ql4_isns.o
      CC [M] /usr/src/qlogic/v5.00.02-1/5.00.02/ql4_nvram.o
      CC [M] /usr/src/qlogic/v5.00.02-1/5.00.02/ql4_dbg.o
      CC [M] /usr/src/qlogic/v5.00.02-1/5.00.02/ql4_cfg.o
      CC [M] /usr/src/qlogic/v5.00.02-1/5.00.02/ql4_cfgln.o
      CC [M] /usr/src/qlogic/v5.00.02-1/5.00.02/ql4_fo.o
      CC [M] /usr/src/qlogic/v5.00.02-1/5.00.02/ql4_foio.o
      CC [M] /usr/src/qlogic/v5.00.02-1/5.00.02/ql4_foioctl.o
      CC [M] /usr/src/qlogic/v5.00.02-1/5.00.02/ql4_foln.o
      CC [M] /usr/src/qlogic/v5.00.02-1/5.00.02/ql4_xioct.o
      CC [M] /usr/src/qlogic/v5.00.02-1/5.00.02/ql4_inioct.o
      CC [M] /usr/src/qlogic/v5.00.02-1/5.00.02/ql4_32ioctl.o
      LD [M] /usr/src/qlogic/v5.00.02-1/5.00.02/qla4xxx.o
      Building modules, stage 2.
      MODPOST
      CC /usr/src/qlogic/v5.00.02-1/5.00.02/qla4xxx.mod.o
      LD [M] /usr/src/qlogic/v5.00.02-1/5.00.02/qla4xxx.ko
    make: Leaving directory `/lib/modules/2.6.11-1.27_FC3smp/build'

    Andy Green wrote:

    > -----BEGIN PGP SIGNED MESSAGE-----
    > Hash: SHA1
    >
    > Jimmy McMillan wrote:
    > | Also here's a build error I get when compiling the module.
    >
    > | /usr/src/qlogic/v5.00.02-1/5.00.02/ql4_os.c: In function
    > | `qla4xxx_probe_adapter':
    > | /usr/src/qlogic/v5.00.02-1/5.00.02/ql4_os.c:195: sorry, unimplemented:
    > | inlining failed in call to 'qla4xxx_config_dma_addressing': function
    > | body not available
    >
    > These are likely genuine problems with the source which the later
    > version of the compiler you have now is detecting and complaining about,
    > whereas previous versions of the compiler silently accepted the error.
    >
    > Remove the "inline" token at the function declarations and it should
    > continue.
    >
    > - -Andy
    > -----BEGIN PGP SIGNATURE-----
    > Version: GnuPG v1.4.1 (GNU/Linux)
    > Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
    >
    > iD8DBQFCnHs8jKeDCxMJCTIRAhFzAJ9EDEffZ3ihzpaFkitYpzMxMDX0FQCfaviy
    > NfsjZg1If4j35NU7qm1Buw0=
    > =XJN4
    > -----END PGP SIGNATURE-----
    > 

    -- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
  • Next message: Les Mikesell: "Re: General routing question?"

    Relevant Pages

    • Re: Ommiting void
      ... easily avoid the issue by always declarating "int main". ... I do, however, also drop K&R style declarations, along with implicit ... If you don't want to support them in your compiler, that's fine, ... actually, in my case I seem not to mix well with moderators, as moderators necessarily reject my posts, and English teachers necessarily give me very low grades, even when my grammar and spelling is correct. ...
      (comp.std.c)
    • Re: Prototype or not prototype?
      ... in PDP-11 environments as well as Standard C environments, ... The code used a lot of function pointers and enum parameters ... K&R-style declarations or the C compiler had been able to root them out, ...
      (comp.std.c)
    • managing header files
      ... while in the .h files the external declarations showed no arguments. ... Apparently that was the reason the compiler wasn't catching errors of the ... wrong number of arguments when routines were called from other files. ... Then I went through the all the header files ...
      (comp.lang.c.moderated)
    • declarations summary
      ... generate executable bytecode but merely affects the compiler". ... don't fit comfortably into Python syntax and 2) they at least ... execute. ... for me to call them both "declarations" was incorrect. ...
      (comp.lang.python)
    • Re: namespaces and main()
      ... > You're not writing code twice, just declarations. ... information for the linker to check if any exported type information ... again lack of adequate information passed from the compiler to ...
      (comp.lang.cpp)