-include /usr/src/linux/include/linux/modversions.h
to your CFLAGS. I haven't tracked down why this makes a difference on
SMP. Anyone have any ideas?
cheers,
aaron
It would seem that WANG,YIDING (HP-SanJose,ex1) (yiding_wang@am.exch.hp.com) said:
> Many thanks for the response!
>
> I have tried 'insmod -f hpfc' and failed again with following messages:
>
> ./hpfc: unresolved symbol pci_write_config_byte
> ./hpfc: unresolved symbol request_region
> ./hpfc: unresolved symbol __udelay
> ./hpfc: unresolved symbol kmalloc
> ./hpfc: unresolved symbol release_region
> ./hpfc: unresolved symbol scsi_unregister_module
> ./hpfc: unresolved symbol pci_read_config_byte
> ./hpfc: unresolved symbol scsi_register
> ./hpfc: unresolved symbol free_irq
> ./hpfc: unresolved symbol pci_read_config_dword
> ./hpfc: unresolved symbol __ioremap
> ./hpfc: unresolved symbol pci_read_config_word
> ./hpfc: unresolved symbol io_request_lock
> ./hpfc: unresolved symbol kfree
> ./hpfc: unresolved symbol request_irq
> ./hpfc: unresolved symbol scsi_register_module
> ./hpfc: unresolved symbol pci_write_config_dword
> ./hpfc: unresolved symbol pci_find_device
> ./hpfc: unresolved symbol pci_write_config_word
> ./hpfc: unresolved symbol sprintf
> ./hpfc: unresolved symbol check_region
> ./hpfc: unresolved symbol jiffies
> ./hpfc: unresolved symbol printk
> ./hpfc: unresolved symbol add_timer
> ./hpfc: unresolved symbol scsi_unregister
> ./hpfc: unresolved symbol __const_udelay
> Warning: kernel-module version mismatch
> ./hpfc was compiled for kernel version 2.2.5-15
> while this kernel is version 2.2.5-15smp
>
> "hpfc" is driver module name. The driver is tested on UP system already.
>
> I tried again on Intel Viper (8 CPU) system again and did the following:
> 1, 'make menuconfig'
> - Only thing changed there is to support SMP.
> 2, 'make dep'
> 3, recompile the driver with -D__SMP__ define in CFLAG under new system
> configuration.
> - with new configuration, driver compiled OK (it failed before the
> reconfiguration
> due to some variables are not defined when with -D__SMP__).
> 4, 'insmod hpfc'
> - it failed with messgaes:
> ./hpfc was compiled for kernel version 2.2.5-15
> while this kernel is version 2.2.5-15smp
> 5, 'insmod -f hpfc'
> - it failed with the messages shown above.
>
> I am sure that I missed something during the process of compiling or loading
> driver but just don't know what.
>
> Adding "#include <asm/smp.h> and <asm/spinlock.h>" in driver code doesn't
> help either.
> My system related CFLAG define: CFLAGS = -O -D__SMP__ -D__KERNEL__ -DMODULE
>
> Could anyone help on this issue please!!!
>
> Many thanks!
>
>
> -eddie
>
> -----Original Message-----
> From: Richard B. Johnson [mailto:root@chaos.analogic.com]
> Sent: Monday, September 20, 1999 4:54 PM
> To: WANG,YIDING (HP-SanJose,ex1)
> Cc: 'Rui Sousa'; linux-kernel
> Subject: RE: SMP environment driver building issue ...
>
>
> On Mon, 20 Sep 1999, WANG,YIDING (HP-SanJose,ex1) wrote:
>
> > Rui,
> >
> > Folllowed your suggestion, I run 'make config' and enable SMP support with
> > all other option as default value. The I run 'make dep'.
> >
> > After system is reconfigured, compileing driver seems OK. However, when I
> > load driver "hpfc" with :
> > 'insmod hpfc',
> > system still complains:
> > ./hpfc: kernel was compiled for kernel version 2.2.5-15
> > while this kernel is version 2.2.5-15smp
> >
> > Seems like I still miss something during the driver compiling or kernel
> > reconfigure. I am using "-D__SMP__" in CFLAG during the driver compiling.
> >
> > Any suggestion from there to help driver successfully compiles and loads
> on
> > SMP environment?
> >
> > Many thanks!
> >
> > -eddie
>
> Temporary fix, use `insmod -f` to force it to load.
>
> Cheers,
> Dick Johnson
> **** FILE SYSTEM WAS MODIFIED ****
> Penguin : Linux version 2.3.13 on an i686 machine (400.59 BogoMips).
> Warning : It's hard to remain at the trailing edge of technology.
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
> Please read the FAQ at http://www.tux.org/lkml/
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/