linux-kernel - RE: 1000xf bus problem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 18 Mar 2007 22:03:21 -0500
From:	<Greg.Chandler@...lsfargo.com>
To:	<auke-jan.h.kok@...el.com>, <hancockr@...w.ca>
Cc:	<linux-kernel@...r.kernel.org>, <e1000-devel@...ts.sourceforge.net>
Subject: RE: 1000xf bus problem


If you mean dmesg it says this:
e1000: 0000:0d:02.0: e1000_probe: (PCI-X:100MHz:64-bit)  {macaddress}

That's weird... dmesg shows one thing, lspci shows another, and my data
transfers seem to point to the lspci info...

Any idea which I should trust?


-----Original Message-----
From: Kok, Auke [mailto:auke-jan.h.kok@...el.com] 
Sent: Sunday, March 18, 2007 3:52 PM
To: Robert Hancock
Cc: Chandler, Greg; linux-kernel; e1000-devel@...ts.sourceforge.net
Subject: Re: 1000xf bus problem

Robert Hancock wrote:
> Greg.Chandler@...lsfargo.com wrote:
>> I'm running a e1000xf adapter in a 64-bit/100Mhz PCI slot.  The intel

>> site shows this is a supported config for the card, but linux is 
>> pulling this info:
>>
>> ed:02.0 Ethernet controller: Intel Corporation 82544EI Gigabit 
>> Ethernet Controller (Fiber) (rev 02)
>> 	Subsystem: Intel Corporation PRO/1000 XF Server Adapter
>> 	Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 18
>> 	Memory at f7fe0000 (64-bit, non-prefetchable) [size=128K]
>>       Memory at f7fc0000 (64-bit, non-prefetchable) [size=128K]
>>       I/O ports at 7000 [size=32]
>>       [virtual] Expansion ROM at f10a0000 [disabled] [size=128K]
>>       Capabilities: [dc] Power Management version 2
>>       Capabilities: [e4] PCI-X non-bridge device
>>       Capabilities: [f0] Message Signalled Interrupts: 64bit+ 
>> Queue=0/0
>> Enable-
>>
>> My thoughput tests show it is definitely not running at the 100Mhz 
>> bus rate is should be capable of.
> 
> How are you determining this?
> 
>  > Any ideas on how to make it work at full speed?

what is the dmesh output of e1000 ? it should show you what the card
itself detects (at least the newer drivers since 7.0.x all do). This may
provide some clues as to what the card has detected.

Auke


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/