Hi Jim, I'm glad you found the problem. Here Emil (I cc'd him above) tried playing around with the RHEL5.[4|5] xen kernels but wasn't able to recreate your issue, now at least we know why. :)
As for building a driver against a kernel you don't have installed, I don't believe you can do it. At the least I think you would need the kernel source and then I believe you would make using the BUILD_KERNEL option in our makefile. That said it's been a long time since I've done that but I believe that's how you do it. Best of luck, -Don >-----Original Message----- >From: Guo, Weiping (Jim) [mailto:w...@avaya.com] >Sent: Thursday, July 15, 2010 2:23 PM >To: Skidmore, Donald C >Subject: RE: Kernel panic ixgbe-2.0.72.4 against 164.15.1 > >Hi Don, > >I played around the build more, and found out everything is OK if I >build the driver against the current running kernel. > >However, if I want to build driver against a kernel which is not >installed, I got the "Unknown symbol error". I have been trying to >modify the spec file, but not sure how can I force pointing to the >correct path. Any tips? > >Thanks. > >Jim > > >make -C >/opt/ws/vsst/trunk/drivers/../os/target/rpmbuild/dist//lib/modules/2.6.1 >8-164.15.1.AV.1.el5xen/build/ >O=/lib/modules/2.6.18-164.15.1.AV.1.el5xen/build >SUBDIRS=/opt/ws/vsst/trunk/drivers/target/rpmbuild/BUILD/ixgbe-2.0.84.9/ >src modules > > > >Weiping (Jim) Guo | Avaya | 233 Mt. Airy Road| Rm. 2D31 | Basking Ridge, >NJ 07920-2311 | Voice/Fax: 908-696-5161 908-696-5402 | w...@avaya.com > >-----Original Message----- >From: Guo, Weiping (Jim) >Sent: Thursday, July 15, 2010 9:46 AM >To: 'Skidmore, Donald C' >Subject: RE: Kernel panic ixgbe-2.0.72.4 against 164.15.1 > >I just built the 2.0.84.9, and but got error when insmod: > >ixgbe: Unknown symbol dma_set_mask > >For the kernel configuration, should I disable DMA? > ># ># DMA Engine support ># >CONFIG_DMA_ENGINE=m > ># ># DMA Devices ># >CONFIG_INTEL_IOATDMA=m >CONFIG_DCA=m > ># ># DMA Engine support version 3 ># >CONFIG_DMA_ENGINE_V3=y > ># ># DMA Clients V3 ># >CONFIG_NET_DMA=y > ># ># DMA Devices ># >CONFIG_INTEL_IOATDMA_V3=m >CONFIG_UIO=m > > >-----Original Message----- >From: Guo, Weiping (Jim) >Sent: Wednesday, July 14, 2010 9:47 PM >To: Skidmore, Donald C >Subject: RE: Kernel panic ixgbe-2.0.72.4 against 164.15.1 > >Hi Don, > >Thanks for getting me back so quickly. I tried 2.0.75.1, but not the >latest one. Will try out. > >I am suspecting something goes wrong with my build process. > >Thank you. > >Jim > > >-----Original Message----- >From: Skidmore, Donald C [mailto:donald.c.skidm...@intel.com] >Sent: Wed 7/14/2010 7:38 PM >To: Guo, Weiping (Jim); e1000-devel@lists.sourceforge.net >Subject: RE: Kernel panic ixgbe-2.0.72.4 against 164.15.1 > >Hi Jim, > >Sorry you're having problems building ixgbe. This failure doesn't look >familiar to me and I don't currently have the kernel you were working on >handy. However the first question that comes to mind: did you try >building the latest ixgbe on source forge (2.0.84.9) and if so did it >also fail? > >Thanks, >-Don Skidmore <donald.c.skidm...@intel.com> > >>-----Original Message----- >>From: Guo, Weiping (Jim) [mailto:w...@avaya.com] >>Sent: Wednesday, July 14, 2010 2:47 PM >>To: e1000-devel@lists.sourceforge.net >>Subject: [E1000-devel] Kernel panic ixgbe-2.0.72.4 against 164.15.1 >> >>Hi All, >> >> >> >>I build the ixgbe-2.0.72.4 against the kernel 2.6.18-164.15.1.el5xen >>(using default configuration). However, when I tried to configure the >>card, the kernel panic right away. If I use the driver built-in 5.4, it >>works OK (at least no oops). >> >> >> >>The issue is that I could not use built-in version because of some of >>the hardware version is AT2. >> >> >> >>I finally caught the stack trace like the following: >> >> >> >>Call Trace: >> >>[<ffffffff882a1086>]:ixgbe:ixgbe_alloc_rx_buffers+0x1f6/0x2f0 >> >>[<ffffffff882a1d16>]:ixgbe:ixgbe_configure+0xb96/0xbb0 >> >>[<ffffffff882a1e34>]:ixgbe:ixgbe_open+0x104/0x6f0 >> >>[<ffffffff8041c40b>]dev_open+0x2f/0x6e >> >>[<ffffffff8041a399>]dev_change_flags+0x5a/0x11a >> >>[<ffffffff8044ece7>]devinit_ioctl+0x235/0x59c >> >>[<ffffffff80411c79>]sock_ioctl+0x1c1/0x1e5 >> >>[<ffffffff80243f88>]do_ioctl+0x21/0x6b >> >>[<ffffffff80231715>]vfs_ioctl+0x457/0x4b9 >> >>[<ffffffff8020b424>]kmem_cache_alloc+0x62/0x6d >> >>[<ffffffff8024e6f1>]sys_ioctl+0x59/0x78 >> >>[<ffffffff80260106>]system_call+0x86/0x8b >> >>[<ffffffff80260080>]system_call+0x0/ox8b >> >> >> >>Any helps would be appreciated! >> >> >> >>Thank you! >> >> >> >>Jim >> >> > ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
