FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian User

 
 
LinkBack Thread Tools
 
Old 01-04-2008, 09:06 PM
David MAGNY
 
Default Kernel issues due to identical network cards

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 :


Linux version 2.6.18-5-686 (Debian 2.6.18.dfsg.1-17)
(dannf@debian.org) (gcc version 4.1.2 20061115
(prerelease) (Debian 4.1.1-21)) #1 SMP Mon Dec 24
16:41:07 UTC 2007
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 00000000000a0000
(usable)
BIOS-e820: 00000000000f0000 - 0000000000100000
(reserved)
BIOS-e820: 0000000000100000 - 000000001fe8cc00
(usable)
BIOS-e820: 000000001fe8cc00 - 000000001fe8ec00 (ACPI
NVS)
BIOS-e820: 000000001fe8ec00 - 000000001fe90c00 (ACPI
data)
BIOS-e820: 000000001fe90c00 - 0000000020000000
(reserved)
BIOS-e820: 00000000e0000000 - 00000000f0000000
(reserved)
BIOS-e820: 00000000fec00000 - 00000000fed00400
(reserved)
BIOS-e820: 00000000fed20000 - 00000000feda0000
(reserved)
BIOS-e820: 00000000fee00000 - 00000000fef00000
(reserved)
BIOS-e820: 00000000ffb00000 - 0000000100000000
(reserved)
0MB HIGHMEM available.
510MB LOWMEM available.
found SMP MP-table at 000fe710
On node 0 totalpages: 130700
DMA zone: 4096 pages, LIFO batch:0
Normal zone: 126604 pages, LIFO batch:31
DMI 2.3 present.
ACPI: RSDP (v000 DELL
) @ 0x000fec10
ACPI: RSDT (v001 DELL PE1420 0x00000007 ASL
0x00000061) @ 0x000fcb6c
ACPI: FADT (v001 DELL PE1420 0x00000007 ASL
0x00000061) @ 0x000fcbac
ACPI: SSDT (v001 DELL st_ex 0x00001000 MSFT
0x0100000d) @ 0xfffc4a0c
ACPI: MADT (v001 DELL PE1420 0x00000007 ASL
0x00000061) @ 0x000fcc20
ACPI: BOOT (v001 DELL PE1420 0x00000007 ASL
0x00000061) @ 0x000fccaa
ACPI: ASF! (v016 DELL PE1420 0x00000007 ASL
0x00000061) @ 0x000fccd2
ACPI: MCFG (v001 DELL PE1420 0x00000007 ASL
0x00000061) @ 0x000fcd39
ACPI: HPET (v001 DELL PE1420 0x00000007 ASL
0x00000061) @ 0x000fcd77
ACPI: DSDT (v001 DELL dt_ex 0x00001000 MSFT
0x0100000d) @ 0x00000000
ACPI: PM-Timer IO Port: 0x808
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 15:4 APIC version 20
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
Processor #1 15:4 APIC version 20
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] disabled)
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x07] disabled)
ACPI: LAPIC_NMI (acpi_id[0xff] high level lint[0x1])
ACPI: IOAPIC (id[0x08] address[0xfec00000]
gsi_base[0])
IOAPIC[0]: apic_id 8, version 32, address 0xfec00000,
GSI 0-23
ACPI: IOAPIC (id[0x09] address[0xfec80000]
gsi_base[24])
IOAPIC[1]: apic_id 9, version 32, address 0xfec80000,
GSI 24-47
ACPI: IOAPIC (id[0x0a] address[0xfec80800]
gsi_base[48])
IOAPIC[2]: apic_id 10, version 32, address 0xfec80800,
GSI 48-71
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl
dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high
level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Enabling APIC mode: Flat. Using 3 I/O APICs
ACPI: HPET id: 0x8086a201 base: 0xfed00000
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 30000000 (gap:
20000000:c0000000)
Detected 2793.335 MHz processor.
Built 1 zonelists. Total pages: 130700
Kernel command line: root=/dev/sda1 ro pci=routeirq
mapped APIC to ffffd000 (fee00000)
mapped IOAPIC to ffffc000 (fec00000)
mapped IOAPIC to ffffb000 (fec80000)
mapped IOAPIC to ffffa000 (fec80800)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 8192 bytes)
Console: colour VGA+ 80x25
Dentry cache hash table entries: 65536 (order: 6,
262144 bytes)
Inode-cache hash table entries: 32768 (order: 5,
131072 bytes)
Memory: 510652k/522800k available (1541k kernel code,
11580k reserved, 576k data, 196k init, 0k highmem)
Checking if this processor honours the WP bit even in
supervisor mode... Ok.
hpet0: at MMIO 0xfed00000 (virtual 0xe0800000), IRQs
2, 8, 0
hpet0: 3 64-bit timers, 14318180 Hz
Using HPET for base-timer
Calibrating delay using timer specific routine..
5590.14 BogoMIPS (lpj=11180287)
Security Framework v1.0.0 initialized
SELinux: Disabled at boot.
Capability LSM initialized
Mount-cache hash table entries: 512
CPU: After generic identify, caps: bfebfbff 20000000
00000000 00000000 0000641d 00000000 00000000
CPU: After vendor identify, caps: bfebfbff 20000000
00000000 00000000 0000641d 00000000 00000000
monitor/mwait feature present.
using mwait in idle threads.
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: Physical Processor ID: 0
CPU: After all inits, caps: bfebfbff 20000000 00000000
00000180 0000641d 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU0: Intel P4/Xeon Extended MCE MSRs (24) available
CPU0: Thermal monitoring enabled
Compat vDSO mapped to ffffe000.
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
ACPI: Core revision 20060707
CPU0: Intel(R) Xeon(TM) CPU 2.80GHz stepping 01
SMP alternatives: switching to SMP code
Booting processor 1/1 eip 3000
Initializing CPU#1
Calibrating delay using timer specific routine..
5586.16 BogoMIPS (lpj=11172325)
CPU: After generic identify, caps: bfebfbff 20000000
00000000 00000000 0000641d 00000000 00000000
CPU: After vendor identify, caps: bfebfbff 20000000
00000000 00000000 0000641d 00000000 00000000
monitor/mwait feature present.
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: Physical Processor ID: 0
CPU: After all inits, caps: bfebfbff 20000000 00000000
00000180 0000641d 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#1.
CPU1: Intel P4/Xeon Extended MCE MSRs (24) available
CPU1: Thermal monitoring enabled
CPU1: Intel(R) Xeon(TM) CPU 2.80GHz stepping 01
Total of 2 processors activated (11176.30 BogoMIPS).
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
checking TSC synchronization across 2 CPUs: passed.
Brought up 2 CPUs
migration_cost=13
checking if image is initramfs... it is
Freeing initrd memory: 4379k freed
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: Using MMCONFIG
Setting up standard PCI resources
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
PCI quirk: region 0800-087f claimed by ICH4
ACPI/GPIO/TCO
PCI quirk: region 0880-08bf claimed by ICH4 GPIO
PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
PCI: PXH quirk detected, disabling MSI for SHPC device
PCI: PXH quirk detected, disabling MSI for SHPC device
Boot video device is 0000:02:0c.0
PCI: Transparent bridge - 0000:00:1e.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table
[\_SB_.PCI0.PCI1._PRT]
ACPI: PCI Interrupt Routing Table
[\_SB_.PCI0.PCI1.PCI2._PRT]
ACPI: PCI Interrupt Routing Table
[\_SB_.PCI0.PCI1.PCI3._PRT]
ACPI: PCI Interrupt Routing Table
[\_SB_.PCI0.PCI4._PRT]
ACPI: PCI Interrupt Routing Table
[\_SB_.PCI0.PCI5._PRT]
ACPI: PCI Interrupt Routing Table
[\_SB_.PCI0.PCI6._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10
*11 12 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10
11 12 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 *9 10
11 12 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 *10
11 12 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10
11 12 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10
11 12 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 9 10
11 12 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 *5 6 7 9 10
11 12 15)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 12 devices
PnPBIOS: Disabled by ACPI PNP
PCI: Using ACPI for IRQ routing
PCI: Routing PCI interrupts for all devices because
"pci=routeirq" specified
ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level,
low) -> IRQ 169
ACPI: PCI Interrupt 0000:00:03.0[A] -> GSI 16 (level,
low) -> IRQ 169
ACPI: PCI Interrupt 0000:00:04.0[A] -> GSI 16 (level,
low) -> IRQ 169
ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level,
low) -> IRQ 169
ACPI: PCI Interrupt 0000:00:1d.1[b] -> GSI 19 (level,
low) -> IRQ 177
ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level,
low) -> IRQ 185
ACPI: PCI Interrupt 0000:00:1d.3[A] -> GSI 16 (level,
low) -> IRQ 169
ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 23 (level,
low) -> IRQ 193
ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level,
low) -> IRQ 185
ACPI: PCI Interrupt 0000:00:1f.2[A] -> GSI 18 (level,
low) -> IRQ 185
ACPI: PCI Interrupt 0000:00:1f.3[b] -> GSI 17 (level,
low) -> IRQ 201
ACPI: PCI Interrupt 0000:02:0c.0[A] -> GSI 26 (level,
low) -> IRQ 209
ACPI: PCI Interrupt 0000:03:0c.0[A] -> GSI 53 (level,
low) -> IRQ 217
ACPI: PCI Interrupt 0000:03:0d.0[A] -> GSI 49 (level,
low) -> IRQ 225
ACPI: PCI Interrupt 0000:03:0e.0[A] -> GSI 48 (level,
low) -> IRQ 233
pnp: 00:01: ioport range 0x800-0x85f could not be
reserved
pnp: 00:01: ioport range 0xc00-0xc7f has been reserved
pnp: 00:01: ioport range 0x860-0x8ff could not be
reserved
PCI: Bridge: 0000:01:00.0
IO window: d000-dfff
MEM window: de000000-dfefffff
PREFETCH window: disabled.
PCI: Bridge: 0000:01:00.2
IO window: c000-cfff
MEM window: dde00000-ddffffff
PREFETCH window: 30000000-300fffff
PCI: Bridge: 0000:00:02.0
IO window: c000-dfff
MEM window: dde00000-dfefffff
PREFETCH window: 30000000-300fffff
PCI: Bridge: 0000:00:03.0
IO window: disabled.
MEM window: ddd00000-dddfffff
PREFETCH window: disabled.
PCI: Bridge: 0000:00:04.0
IO window: disabled.
MEM window: ddc00000-ddcfffff
PREFETCH window: disabled.
PCI: Bridge: 0000:00:1e.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level,
low) -> IRQ 169
PCI: Setting latency timer of device 0000:00:02.0 to
64
PCI: Setting latency timer of device 0000:01:00.0 to
64
PCI: Setting latency timer of device 0000:01:00.2 to
64
ACPI: PCI Interrupt 0000:00:03.0[A] -> GSI 16 (level,
low) -> IRQ 169
PCI: Setting latency timer of device 0000:00:03.0 to
64
ACPI: PCI Interrupt 0000:00:04.0[A] -> GSI 16 (level,
low) -> IRQ 169
PCI: Setting latency timer of device 0000:00:04.0 to
64
PCI: Setting latency timer of device 0000:00:1e.0 to
64
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2,
16384 bytes)
TCP established hash table entries: 16384 (order: 5,
131072 bytes)
TCP bind hash table entries: 8192 (order: 4, 65536
bytes)
TCP: Hash tables configured (established 16384 bind
8192)
TCP reno registered
Simple Boot Flag value 0x87 read from CMOS RAM was
invalid
Simple Boot Flag at 0x7a set to 0x1
audit: initializing netlink socket (disabled)
audit(1199480879.596:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096
bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Intel E7520/7320/7525 detected.<7>PCI: Setting latency
timer of device 0000:00:02.0 to 64
Allocate Port Service[0000:00:02.0cie00]
Allocate Port Service[0000:00:02.0cie01]
PCI: Setting latency timer of device 0000:00:03.0 to
64
Allocate Port Service[0000:00:03.0cie00]
Allocate Port Service[0000:00:03.0cie01]
PCI: Setting latency timer of device 0000:00:04.0 to
64
Allocate Port Service[0000:00:04.0cie00]
Allocate Port Service[0000:00:04.0cie01]
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports,
IRQ sharing enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:0b: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 8192K size
1024 blocksize
PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at
0x60,0x64 irq 1,12
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 8
NET: Registered protocol family 20
Starting balanced_irq
Using IPI No-Shortcut mode
ACPI: (supports S0 S1 S4 S5)
Freeing unused kernel memory: 196k freed
Time: tsc clocksource has been installed.
ACPI Exception (acpi_processor-0681): AE_NOT_FOUND,
Processor Device is not present [20060707]
ACPI: Getting cpuindex for acpiid 0x3
ACPI Exception (acpi_processor-0681): AE_NOT_FOUND,
Processor Device is not present [20060707]
ACPI: Getting cpuindex for acpiid 0x4
usbcore: registered new driver usbfs
usbcore: registered new driver hub
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level,
low) -> IRQ 169
PCI: Setting latency timer of device 0000:00:1d.0 to
64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered,
assigned bus number 1
uhci_hcd 0000:00:1d.0: irq 169, io base 0x0000ff80
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
Linux Tulip driver version 1.1.13-NAPI (May 11, 2002)
Uniform Multi-Platform E-IDE driver Revision:
7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes;
override with idebus=xx
SCSI subsystem initialized
libata version 2.00 loaded.
Intel(R) PRO/1000 Network Driver - version
7.1.9-k4-NAPI
Copyright (c) 1999-2006 Intel Corporation.
ACPI: PCI Interrupt 0000:00:1d.1[b] -> GSI 19 (level,
low) -> IRQ 177
PCI: Setting latency timer of device 0000:00:1d.1 to
64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered,
assigned bus number 2
uhci_hcd 0000:00:1d.1: irq 177, io base 0x0000ff60
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level,
low) -> IRQ 185
PCI: Setting latency timer of device 0000:00:1d.2 to
64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered,
assigned bus number 3
uhci_hcd 0000:00:1d.2: irq 185, io base 0x0000ff40
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.3[A] -> GSI 16 (level,
low) -> IRQ 169
PCI: Setting latency timer of device 0000:00:1d.3 to
64
uhci_hcd 0000:00:1d.3: UHCI Host Controller
uhci_hcd 0000:00:1d.3: new USB bus registered,
assigned bus number 4
uhci_hcd 0000:00:1d.3: irq 169, io base 0x0000ff20
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
usb 1-1: new low speed USB device using uhci_hcd and
address 2
ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 23 (level,
low) -> IRQ 193
PCI: Setting latency timer of device 0000:00:1d.7 to
64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered,
assigned bus number 5
ehci_hcd 0000:00:1d.7: debug port 1
PCI: cache line size of 128 is not supported by device
0000:00:1d.7
ehci_hcd 0000:00:1d.7: irq 193, io mem 0xffa80800
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00,
driver 10 Dec 2004
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 8 ports detected
ACPI: PCI Interrupt 0000:03:0e.0[A] -> GSI 48 (level,
low) -> IRQ 233
ata_piix 0000:00:1f.2: version 2.00
ata_piix 0000:00:1f.2: MAP [ P0 -- P1 -- ]
ACPI: PCI Interrupt 0000:00:1f.2[A] -> GSI 18 (level,
low) -> IRQ 185
PCI: Setting latency timer of device 0000:00:1f.2 to
64
ata1: SATA max UDMA/133 cmd 0xFE00 ctl 0xFE12 bmdma
0xFEA0 irq 185
ata2: SATA max UDMA/133 cmd 0xFE20 ctl 0xFE32 bmdma
0xFEA8 irq 185
scsi0 : ata_piix
e1000: 0000:03:0e.0: e1000_probe: (PCI:33MHz:64-bit)
00:11:43:15:8c:34
ata1.00: ATA-7, max UDMA/133, 156250000 sectors: LBA48
NCQ (depth 0/32)
ata1.00: ata1: dev 0 multi count 8
ata1.00: configured for UDMA/133
scsi1 : ata_piix
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network
Connection
usb 1-1: device not accepting address 2, error -71
Vendor: ATA Model: WDC WD800AAJS-18 Rev: 01.0
Type: Direct-Access ANSI SCSI
revision: 05
ACPI: PCI Interrupt 0000:03:0c.0[A] -> GSI 53 (level,
low) -> IRQ 217
tulip0: MII transceiver #1 config 1000 status 786d
advertising 05e1.
ICH5: IDE controller at PCI slot 0000:00:1f.1
ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level,
low) -> IRQ 185
ICH5: chipset revision 2
ICH5: not 100% native mode: will probe irqs later
ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings:
hdcMA, hddio
Probing IDE interface ide1...
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.
usb 1-1: new low speed USB device using uhci_hcd and
address 4
usb 1-1: configuration #1 chosen from 1 choice
usbcore: registered new driver hiddev
input: DELL DELL USB Keyboard as /class/input/input0
input: USB HID v1.10 Keyboard [DELL DELL USB Keyboard]
on usb-0000:00:1d.0-1
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
hdc: SAMSUNG CD-ROM SC-148A, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
SCSI device sda: 156250000 512-byte hdwr sectors
(80000 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 156250000 512-byte hdwr sectors
(80000 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
sda:<6>hdc: ATAPI 48X CD-ROM drive, 128kB Cache,
UDMA(33)
Uniform CD-ROM driver Revision: 3.20
sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 >
sd 0:0:0:0: Attached scsi disk sda
Attempting manual resume
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
EDAC MC: Ver: 2.0.1 Dec 24 2007
EDAC e752x: tolm = 20000, remapbase = ffc000,
remaplimit = 0
EDAC MC0: Giving out device to e752x_edac E7520: DEV
0000:00:00.0
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: Standard Hot Plug PCI Controller Driver
version: 0.4
input: PC Speaker as /class/input/input1
intel_rng: FWH not detected
ACPI: PCI Interrupt 0000:00:1f.3[b] -> GSI 17 (level,
low) -> IRQ 201
Real Time Clock Driver v1.12ac
Floppy drive(s): fd0 is 1.44M
parport: PnPBIOS parport detected.
parport0: PC-style at 0x378 (0x778), irq 7, using FIFO
[PCSPP,TRISTATE,COMPAT,ECP]
FDC 0 is a post-1991 82077
Adding 1951856k swap on /dev/sda8. Priority:-1
extents:1 across:1951856k
EXT3 FS on sda1, internal journal
loop: loaded (max 8 devices)
device-mapper: ioctl: 4.7.0-ioctl (2006-06-24)
initialised: dm-devel@redhat.com
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda5, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda7, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
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



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.

Any ideas ?

Regards

David MAGNY



__________________________________________________ ___________________________
Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail http://mail.yahoo.fr


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 01-05-2008, 01:49 AM
"Douglas A. Tutty"
 
Default 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.

What exactly does this line mean? Do you mean that of the two identical
cards, only one is available?

> The used kernel is 2.6.18.
>
> Within the dmesg log file, I have the following
> information :
>

> 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.

You also have this (culled from your dmesg)

> e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network
> Connection
> usb 1-1: device not accepting address 2, error -71
> Vendor: ATA Model: WDC WD800AAJS-18 Rev: 01.0
> Type: Direct-Access ANSI SCSI
> revision: 05
> ACPI: PCI Interrupt 0000:03:0c.0[A] -> GSI 53 (level,
> low) -> IRQ 217
> tulip0: MII transceiver #1 config 1000 status 786d
> advertising 05e1.

so at least you know that the kernel is finding the card.

I don't like the 2.6 dmesg with messages from different modules being
intermixed. Since I don't know the kernel internals, its hard for me to
tell what line belongs to which device if it doesn't start with a device
node. So, in this case, I don't know if the third line (usb 1-1...)
relates to the problem or not.

This suggests that eth0 is the intel card, while eth1 and eth2 are the
two ADMtek comets.

What does your /etc/network/interfaces look like?

Doug.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 01-05-2008, 06:24 AM
Andrew Sackville-West
 
Default 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
 
Old 01-05-2008, 11:11 AM
David MAGNY
 
Default Kernel issues due to identical network cards

--- "Douglas A. Tutty" <dtutty@porchlight.ca> a écrit
:

> 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.
>
> What exactly does this line mean? Do you mean that
> of the two identical
> cards, only one is available?

Yes, only one is available
>
> > The used kernel is 2.6.18.
> >
> > Within the dmesg log file, I have the following
> > information :
> >
>
> > 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.
>
> You also have this (culled from your dmesg)
>
> > e1000: eth0: e1000_probe: Intel(R) PRO/1000
> Network
> > Connection
> > usb 1-1: device not accepting address 2, error -71
> > Vendor: ATA Model: WDC WD800AAJS-18 Rev:
> 01.0
> > Type: Direct-Access ANSI
> SCSI
> > revision: 05
> > ACPI: PCI Interrupt 0000:03:0c.0[A] -> GSI 53
> (level,
> > low) -> IRQ 217
> > tulip0: MII transceiver #1 config 1000 status
> 786d
> > advertising 05e1.
>
> so at least you know that the kernel is finding the
> card.
>
> I don't like the 2.6 dmesg with messages from
> different modules being
> intermixed. Since I don't know the kernel
> internals, its hard for me to
> tell what line belongs to which device if it doesn't
> start with a device
> node. So, in this case, I don't know if the third
> line (usb 1-1...)
> relates to the problem or not.
>
> This suggests that eth0 is the intel card, while
> eth1 and eth2 are the
> two ADMtek comets.

Yes you are right. But, I use ifrename (/etc/iftab) in
order to be sure that a network interface has always
the same name when I restart the server.

if my /etc/iftab I mention that,
ethO is one of ADMtek comet
eth1 is the intel card
eth2 is the other ADMtek card

and in fact eth2 is not available.



> What does your /etc/network/interfaces look like?
#eth0 is connected to Internet
auto eth0
iface eth0 inet static
address X.X.X.X
netmask X.X.X.X
network X.X.X.X
broadcast X.X.X.X
gateway X.X.X.X

#eth1 is connected to the private network
auto eth1
iface eth1 inet static
address 192.168.0.254
netmask 255.255.255.0
network 192.168.0.0
broadcast 192.168.0.255

#eth2 is connected to the DMZ
auto eth2
iface eth2 inet static
address 192.168.2.254
netmask 255.255.255.0
network 192.168.2.0
broadcast 192.168.2.255

>
> Doug.
>

David
>
> --
> To UNSUBSCRIBE, email to
> debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
>
>



__________________________________________________ ___________________________
Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail http://mail.yahoo.fr


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 01-05-2008, 03:26 PM
"Douglas A. Tutty"
 
Default Kernel issues due to identical network cards

On Sat, Jan 05, 2008 at 01:11:41PM +0100, David MAGNY wrote:
> --- "Douglas A. Tutty" <dtutty@porchlight.ca> a ?crit
> > 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.
> >
> > What exactly does this line mean? Do you mean that
> > of the two identical
> > cards, only one is available?
>
> Yes, only one is available

> > so at least you know that the kernel is finding the
> > card.
> >
[snip dmesg that shows all three cards]
> > This suggests that eth0 is the intel card, while
> > eth1 and eth2 are the
> > two ADMtek comets.
>
> Yes you are right. But, I use ifrename (/etc/iftab) in
> order to be sure that a network interface has always
> the same name when I restart the server.
>
> if my /etc/iftab I mention that,
> ethO is one of ADMtek comet
> eth1 is the intel card
> eth2 is the other ADMtek card
>
> and in fact eth2 is not available.
>
>

What if you don't use iftab? If, as a test, you just go ahead and set
up all three cards? Does /sbin/ifconfig then show three cards
configured? If so, then dmesg and the kernel are just fine, the problem
is in ifrename. I've never needed ifrename so I don't know about it.

>
> > What does your /etc/network/interfaces look like?
> #eth0 is connected to Internet
> auto eth0
> iface eth0 inet static
> address X.X.X.X
> netmask X.X.X.X
> network X.X.X.X
> broadcast X.X.X.X
> gateway X.X.X.X
>
> #eth1 is connected to the private network
> auto eth1
> iface eth1 inet static
> address 192.168.0.254
> netmask 255.255.255.0
> network 192.168.0.0
> broadcast 192.168.0.255
>
> #eth2 is connected to the DMZ
> auto eth2
> iface eth2 inet static
> address 192.168.2.254
> netmask 255.255.255.0
> network 192.168.2.0
> broadcast 192.168.2.255
>



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 

Thread Tools




All times are GMT. The time now is 04:57 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org