Menu
▾
▴
Re: [E1000-devel] tx unit hang fc11
|
From: <jo...@de...> - 2010-10-26 15:00:42
|
Any ideas on this Jesse? Does anything jump out at you or am I screwed? I do have an Intel box that I could boot a FC12 64bit livecd that has the card. And send you the output of if this might help to find the issue. Jon Quoting Jesse Brandeburg <jes...@gm...>: > On Fri, Oct 22, 2010 at 6:17 PM, <jo...@de...> wrote: >> Quoting "Brandeburg, Jesse" <jes...@in...>: >> >>> >>> >>> On Thu, 21 Oct 2010, jo...@de... wrote: >>> >>>> I am still having this issue but it seems to only be on x86_64. I used >>>> a Knoppix disk to boot with and the card worked with no issues using a >>>> 32bit kernel. I downloaded the latest kernel from kernel.org and >>>> compiled it and the issue returns using a 64bit kernel. >>> >>> huh, that is pretty interesting. Does your machine have >= >>> 4GB ram? Did >>> you ever try enabling the APIC with apic=force kernel boot option? >> >> Yes it has 6GB of RAM. I have never tried apic=force as a boot option >> I will try that. I thought the default was for apic to be enabled so I >> have tried it with apic=no. >> >> I have tried ignore_64bit_dma=1 and still get the same issue. I am >> using modprobe ignore_64bit_dma=1 e1000, that is the correct way to >> load it with that option? I have also tried TXDescriptorStep=4 along > > I think the syntax is modprobe ./e1000.ko ignore_64bit_dma=1 > of course only after make install > >> with and without the ignore_64bit_dma option. >> >> I am right now trying to figure out how to get the dmesg.log from >> knoppix whch seems to truncate it. Tushar has asked me for this so I >> have been waiting to post back until I got it when I noticed your reply. > > you might be able to boot the knoppix kernel with a kernel option to > increase the dmesg log buffer size (think its called log_buf_size ?). > >> >> While I'm trying to figure out the dmesg problem what else if anything >> would you need, cat /proc/interrupts or any thing else? > > cat /proc interrupts on the 32 bit kernel and the full dmesg (i know > you're working on it) you maybe just want to do dmesg > file.txt > >> >> Just a note, I have tried the last three versions of the module all >> with the same results. >> >> I am getting close to just installing a 32bit kernel but all of my >> VM's are 64bit so it would be a huge hassle. :) > > The 64bit dma fix is precisely for the problem you're describing, also > the descriptor step workaround has been known to help in amd systems. > |