[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Kernel issues due to identical network cards



On Fri, Jan 04, 2008 at 11:06:31PM +0100, David MAGNY wrote:
> Hello,
> 
> I am upgrading a firewall from Sarge to Etch.
> 
> On this machine, I have 3 network cards.
> 
> 2 networks cards are identical. It is PCI network
> cards and it is SMC1233A-TX.
> 
> On Sarge, everything worked well.
> 
> The issue is that only one card of both is available.
> The used kernel is  2.6.18.
> 
> Within the dmesg log file, I have the following
> information :
...
> e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network
> Connection

found 1 card, though it's not very helpful info.

...
> eth1: ADMtek Comet rev 17 at 0001c800,
> 00:50:BF:B0:CB:4B, IRQ 217.
...

found another card, with MAC and irq.

> eth2: ADMtek Comet rev 17 at 0001cc00,
> 00:50:BF:B7:F2:79, IRQ 225.

ditto.

...
> ADDRCONF(NETDEV_UP): eth2: link is not ready
> e1000: eth2: e1000_watchdog: NIC Link is Up 100 Mbps
> Full Duplex
> ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready

hmmm... do the ADMtek cards use e1000 driver or did eth0 get moved to
eth2, thus bumping eth2 elsewhere? 

> 
> 
> 
> I noticed that the two identical network cards are
> detected  :
> 
> eth1: ADMtek Comet rev 17 at 0001c800,
> 00:50:BF:B0:CB:4B, IRQ 217.
> ACPI: PCI Interrupt 0000:03:0d.0[A] -> GSI 49 (level,
> low) -> IRQ 225
> tulip1:  MII transceiver #1 config 1000 status 786d
> advertising 05e1.
> eth2: ADMtek Comet rev 17 at 0001cc00,
> 00:50:BF:B7:F2:79, IRQ 225.
> 
> I added the following parameters to the kernel
> pci=irprouting, and I always have the same issue.

why did you do this? is that a typo? irqrouting maybe?

what output from 

lspci -v

what output from 

ls /sys/bus/pci/drivers/

and 

ls /sys/bus/pci/drivers/e1000

A

Attachment: signature.asc
Description: Digital signature


Reply to: