eth1 - SIOCSIFFLAGS Device or resource busy

[foxco]

Bonjour a vous tous,

Heureux utilisateur de la version .16,
j'ai eu la mauvaise idee de mettre a jour vers .17 et .18

depuis je n'ai plus de zone bleue active...

Je vous explique ma config :

Serveur 1U - 3.00Ghz - 1Gb
Carte quad port Gigabit Intel

zone rouge : MODEM IP fixe
zone orange (serveurs) IP's Fixes (192.168.100.xx)
zone verte (stations travail) DHCP 192.168.1.2 - 192.168.1.254
zone bleue (laptop) DHCP 192.168.2.100 - 192.168.2.254

Suite a la mise a jour, les machines se trouvant dans le zone bleue n'ont plus eu de connection (connection limitée ou inexistante), j'ai tenté de forcer l'attribution des IP (ipconfig /renew), en vain.

J'ai donc redemarré l'ipcop et j'ai pu lire

rules firewall
siocsifflags : device or resouce busy

j'ai donc cherché sur google, et je trouve que cela pourrait venir d'un soucis d'IRQ

Aurais je foiré qqchose dans la mise a jour ?

Voila le log complet, la partie qui me semble interessante est reprise plus bas en rouge.
Je suis pas du tout Linux Guy, mais je suis pret a apprendre.

Merci à vous tous.

Code: Tout sélectionner

Feb 22 21:53:23 fw syslogd 1.4.1: restart.
Feb 22 21:53:23 fw kernel: klogd 1.4.1, log source = /proc/kmsg started.
Feb 22 21:53:23 fw kernel: Inspecting /boot/System.map-2.4.34-smp
Feb 22 21:53:23 fw kernel: Loaded 12453 symbols from /boot/System.map-2.4.34-smp.
Feb 22 21:53:23 fw kernel: Symbols match kernel version 2.4.34.
Feb 22 21:53:23 fw kernel: Loaded 200 symbols from 8 modules.
Feb 22 21:53:23 fw kernel: Linux version 2.4.34-smp (root@barton) (gcc version 3.3.3) #1 SMP Mon Jul 16 23:04:20 GMT 2007
Feb 22 21:53:23 fw kernel: BIOS-provided physical RAM map:
Feb 22 21:53:23 fw kernel:  BIOS-e820: 0000000000000000 - 000000000009f400 (usable)
Feb 22 21:53:23 fw kernel:  BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved)
Feb 22 21:53:23 fw kernel:  BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
Feb 22 21:53:23 fw kernel:  BIOS-e820: 0000000000100000 - 000000001f6e0000 (usable)
Feb 22 21:53:23 fw kernel:  BIOS-e820: 000000001f6e0000 - 000000001f6e3000 (ACPI NVS)
Feb 22 21:53:23 fw kernel:  BIOS-e820: 000000001f6e3000 - 000000001f6f0000 (ACPI data)
Feb 22 21:53:23 fw kernel:  BIOS-e820: 000000001f6f0000 - 000000001f700000 (reserved)
Feb 22 21:53:23 fw kernel:  BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
Feb 22 21:53:23 fw kernel:  BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
Feb 22 21:53:23 fw kernel: 0MB HIGHMEM available.
Feb 22 21:53:23 fw kernel: 502MB LOWMEM available.
Feb 22 21:53:23 fw kernel: found SMP MP-table at 000f3580
Feb 22 21:53:23 fw kernel: hm, page 000f3000 reserved twice.
Feb 22 21:53:23 fw kernel: hm, page 000f4000 reserved twice.
Feb 22 21:53:23 fw kernel: hm, page 000f1000 reserved twice.
Feb 22 21:53:23 fw kernel: hm, page 000f2000 reserved twice.
Feb 22 21:53:23 fw kernel: On node 0 totalpages: 128736
Feb 22 21:53:23 fw kernel: zone(0): 4096 pages.
Feb 22 21:53:23 fw kernel: zone(1): 124640 pages.
Feb 22 21:53:23 fw kernel: zone(2): 0 pages.
Feb 22 21:53:23 fw kernel: ACPI: RSDP (v000 IntelR                                    ) @ 0x000f7780
Feb 22 21:53:23 fw kernel: ACPI: RSDT (v001 IntelR AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1f6e3040
Feb 22 21:53:23 fw kernel: ACPI: FADT (v001 IntelR AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1f6e30c0
Feb 22 21:53:23 fw kernel: ACPI: MCFG (v001 IntelR AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1f6e7540
Feb 22 21:53:23 fw kernel: ACPI: MADT (v001 IntelR AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1f6e7440
Feb 22 21:53:23 fw kernel: ACPI: SSDT (v001  PmRef  Cpu0Ist 0x00003000 INTL 0x20041203) @ 0x1f6e75c0
Feb 22 21:53:23 fw kernel: ACPI: SSDT (v001  PmRef    CpuPm 0x00003000 INTL 0x20041203) @ 0x1f6e7a50
Feb 22 21:53:23 fw kernel: ACPI: DSDT (v001 INTELR AWRDACPI 0x00001000 MSFT 0x03000000) @ 0x00000000
Feb 22 21:53:23 fw kernel: ACPI: Local APIC address 0xfee00000
Feb 22 21:53:23 fw kernel: ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Feb 22 21:53:24 fw kernel: Processor #0 Unknown CPU [15:6] APIC version 20
Feb 22 21:53:24 fw kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Feb 22 21:53:24 fw kernel: Processor #1 Unknown CPU [15:6] APIC version 20
Feb 22 21:53:24 fw kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] disabled)
Feb 22 21:53:24 fw kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] disabled)
Feb 22 21:53:24 fw kernel: ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Feb 22 21:53:24 fw kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Feb 22 21:53:24 fw kernel: ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Feb 22 21:53:24 fw kernel: ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Feb 22 21:53:24 fw kernel: Using ACPI for processor (LAPIC) configuration information
Feb 22 21:53:24 fw kernel: Intel MultiProcessor Specification v1.4
Feb 22 21:53:24 fw kernel:     Virtual Wire compatibility mode.
Feb 22 21:53:24 fw kernel: OEM ID: OEM00000 Product ID: PROD00000000 APIC at: 0xFEE00000
Feb 22 21:53:24 fw kernel: I/O APIC #4 Version 17 at 0xFEC00000.
Feb 22 21:53:24 fw kernel: Enabling APIC mode: Flat.^IUsing 1 I/O APICs
Feb 22 21:53:24 fw kernel: Processors: 2
Feb 22 21:53:24 fw kernel: Kernel command line: root=/dev/hda4 panic=10 acpi=ht ro
Feb 22 21:53:24 fw kernel: Initializing CPU#0
Feb 22 21:53:24 fw kernel: Detected 2992.631 MHz processor.
Feb 22 21:53:24 fw kernel: Console: colour VGA+ 80x25
Feb 22 21:53:24 fw kernel: Calibrating delay loop... 5976.88 BogoMIPS
Feb 22 21:53:24 fw kernel: Memory: 506216k/514944k available (1340k kernel code, 8340k reserved, 374k data, 116k init, 0k highmem)
Feb 22 21:53:24 fw kernel: Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Feb 22 21:53:24 fw kernel: Inode cache hash table entries: 32768 (order: 6, 262144 bytes)
Feb 22 21:53:24 fw kernel: Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Feb 22 21:53:24 fw kernel: Buffer cache hash table entries: 32768 (order: 5, 131072 bytes)
Feb 22 21:53:24 fw kernel: Page-cache hash table entries: 131072 (order: 7, 524288 bytes)
Feb 22 21:53:24 fw kernel: CPU: Trace cache: 12K uops, L1 D cache: 16K
Feb 22 21:53:24 fw kernel: CPU: Physical Processor ID: 0
Feb 22 21:53:24 fw kernel: Intel machine check architecture supported.
Feb 22 21:53:24 fw kernel: Intel machine check reporting enabled on CPU#0.
Feb 22 21:53:24 fw kernel: Enabling fast FPU save and restore... done.
Feb 22 21:53:24 fw kernel: Enabling unmasked SIMD FPU exception support... done.
Feb 22 21:53:24 fw kernel: Checking 'hlt' instruction... OK.
Feb 22 21:53:24 fw kernel: Checking for popad bug... OK.
Feb 22 21:53:24 fw kernel: POSIX conformance testing by UNIFIX
Feb 22 21:53:24 fw kernel: CPU: Trace cache: 12K uops, L1 D cache: 16K
Feb 22 21:53:24 fw kernel: CPU: Physical Processor ID: 0
Feb 22 21:53:24 fw kernel: Intel machine check reporting enabled on CPU#0.
Feb 22 21:53:24 fw kernel: CPU0: Intel(R) Pentium(R) 4 CPU 3.00GHz stepping 05
Feb 22 21:53:24 fw kernel: per-CPU timeslice cutoff: 45.71 usecs.
Feb 22 21:53:24 fw kernel: enabled ExtINT on CPU#0
Feb 22 21:53:24 fw kernel: ESR value before enabling vector: 00000000
Feb 22 21:53:24 fw kernel: ESR value after enabling vector: 00000000
Feb 22 21:53:24 fw kernel: Booting processor 1/1 eip 3000
Feb 22 21:53:24 fw kernel: Initializing CPU#1
Feb 22 21:53:25 fw kernel: masked ExtINT on CPU#1
Feb 22 21:53:25 fw kernel: ESR value before enabling vector: 00000000
Feb 22 21:53:25 fw kernel: ESR value after enabling vector: 00000000
Feb 22 21:53:25 fw kernel: Calibrating delay loop... 5976.88 BogoMIPS
Feb 22 21:53:25 fw kernel: CPU: Trace cache: 12K uops, L1 D cache: 16K
Feb 22 21:53:25 fw kernel: CPU: Physical Processor ID: 0
Feb 22 21:53:25 fw kernel: Intel machine check reporting enabled on CPU#1.
Feb 22 21:53:25 fw kernel: CPU1: Intel(R) Pentium(R) 4 CPU 3.00GHz stepping 05
Feb 22 21:53:25 fw kernel: Total of 2 processors activated (11953.76 BogoMIPS).
Feb 22 21:53:25 fw kernel: cpu_sibling_map[0] = 1
Feb 22 21:53:25 fw kernel: cpu_sibling_map[1] = 0
Feb 22 21:53:25 fw kernel: ENABLING IO-APIC IRQs
Feb 22 21:53:25 fw kernel: Setting 4 in the phys_id_present_map
Feb 22 21:53:25 fw kernel: ...changing IO-APIC physical APIC ID to 4 ... ok.
Feb 22 21:53:25 fw kernel: ..TIMER: vector=0x31 pin1=2 pin2=0
Feb 22 21:53:25 fw kernel: testing the IO APIC.......................
Feb 22 21:53:25 fw kernel:
Feb 22 21:53:25 fw kernel: .................................... done.
Feb 22 21:53:25 fw kernel: Using local APIC timer interrupts.
Feb 22 21:53:25 fw kernel: calibrating APIC timer ...
Feb 22 21:53:25 fw kernel: ..... CPU clock speed is 2992.6840 MHz.
Feb 22 21:53:25 fw kernel: ..... host bus clock speed is 199.5121 MHz.
Feb 22 21:53:25 fw kernel: cpu: 0, clocks: 1995121, slice: 665040
Feb 22 21:53:25 fw kernel: CPU0<T0:1995120,T1:1330080,D:0,S:665040,C:1995121>
Feb 22 21:53:25 fw kernel: cpu: 1, clocks: 1995121, slice: 665040
Feb 22 21:53:25 fw kernel: CPU1<T0:1995120,T1:665040,D:0,S:665040,C:1995121>
Feb 22 21:53:25 fw kernel: checking TSC synchronization across CPUs: passed.
Feb 22 21:53:25 fw kernel: Waiting on wait_init_idle (map = 0x2)
Feb 22 21:53:25 fw kernel: All processors have done init_idle
Feb 22 21:53:25 fw kernel: ACPI: Subsystem revision 20040326
Feb 22 21:53:26 fw kernel: ACPI: Interpreter disabled.
Feb 22 21:53:26 fw kernel: PCI: PCI BIOS revision 3.00 entry at 0xf9420, last bus=8
Feb 22 21:53:26 fw kernel: PCI: Using configuration type 1
Feb 22 21:53:26 fw kernel: PCI: Probing PCI hardware
Feb 22 21:53:26 fw kernel: PCI: Probing PCI hardware (bus 00)
Feb 22 21:53:26 fw kernel: PCI: Ignoring BAR0-3 of IDE controller 00:1f.2
Feb 22 21:53:26 fw kernel: Transparent bridge - PCI device 8086:244e
Feb 22 21:53:26 fw kernel: PCI->APIC IRQ transform: (B0,I1,P0) -> 16
Feb 22 21:53:26 fw kernel: PCI->APIC IRQ transform: (B0,I2,P0) -> 16
Feb 22 21:53:26 fw kernel: PCI->APIC IRQ transform: (B0,I28,P0) -> 16
Feb 22 21:53:26 fw kernel: PCI->APIC IRQ transform: (B0,I28,P0) -> 16
Feb 22 21:53:26 fw kernel: PCI->APIC IRQ transform: (B0,I28,P1) -> 17
Feb 22 21:53:26 fw kernel: PCI->APIC IRQ transform: (B0,I31,P1) -> 19
Feb 22 21:53:26 fw last message repeated 2 times
Feb 22 21:53:26 fw kernel: PCI->APIC IRQ transform: (B3,I0,P0) -> 16
Feb 22 21:53:26 fw kernel: PCI->APIC IRQ transform: (B3,I0,P1) -> 17
Feb 22 21:53:26 fw kernel: PCI->APIC IRQ transform: (B4,I0,P0) -> 17
Feb 22 21:53:26 fw kernel: PCI->APIC IRQ transform: (B4,I0,P1) -> 18
Feb 22 21:53:27 fw kernel: Linux NET4.0 for Linux 2.4
Feb 22 21:53:27 fw kernel: Based upon Swansea University Computer Society NET3.039
Feb 22 21:53:27 fw kernel: Initializing RT netlink socket
Feb 22 21:53:27 fw kernel: Starting kswapd
Feb 22 21:53:27 fw kernel: Journalled Block Device driver loaded
Feb 22 21:53:27 fw kernel: pty: 256 Unix98 ptys configured
Feb 22 21:53:27 fw kernel: Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled
Feb 22 21:53:27 fw kernel: ttyS01 at 0x02f8 (irq = 3) is a 16550A
Feb 22 21:53:27 fw kernel: Real Time Clock Driver v1.10f
Feb 22 21:53:27 fw kernel: Floppy drive(s): fd0 is unknown type 15 (usb?), fd1 is unknown type 15 (usb?)
Feb 22 21:53:27 fw kernel: floppy0: no floppy controllers found
Feb 22 21:53:27 fw kernel: RAMDISK driver initialized: 16 RAM disks of 5120K size 1024 blocksize
Feb 22 21:53:27 fw kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
Feb 22 21:53:27 fw kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Feb 22 21:53:27 fw kernel: hda: WDC WD800JD-00LSA5, ATA DISK drive
Feb 22 21:53:27 fw kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Feb 22 21:53:27 fw kernel: hda: attached ide-disk driver.
Feb 22 21:53:27 fw kernel: hda: host protected area => 1
Feb 22 21:53:27 fw kernel: hda: 156301488 sectors (80026 MB) w/8192KiB Cache, CHS=9729/255/63
Feb 22 21:53:27 fw kernel: Partition check:
Feb 22 21:53:27 fw kernel:  hda: hda1 hda2 hda4
Feb 22 21:53:27 fw kernel: Initializing Cryptographic API
Feb 22 21:53:27 fw kernel: NET4: Linux TCP/IP 1.0 for NET4.0
Feb 22 21:53:27 fw kernel: IP Protocols: ICMP, UDP, TCP
Feb 22 21:53:28 fw kernel: IP: routing cache hash table of 4096 buckets, 32Kbytes
Feb 22 21:53:28 fw kernel: TCP: Hash tables configured (established 32768 bind 32768)
Feb 22 21:53:28 fw kernel: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Feb 22 21:53:28 fw kernel: EXT3-fs: INFO: recovery required on readonly filesystem.
Feb 22 21:53:28 fw kernel: EXT3-fs: write access will be enabled during recovery.
Feb 22 21:53:28 fw kernel: kjournald starting.  Commit interval 5 seconds
Feb 22 21:53:28 fw kernel: EXT3-fs: recovery complete.
Feb 22 21:53:28 fw kernel: EXT3-fs: mounted filesystem with ordered data mode.
Feb 22 21:53:28 fw kernel: VFS: Mounted root (ext3 filesystem) readonly.
Feb 22 21:53:28 fw kernel: Freeing unused kernel memory: 116k freed
Feb 22 21:53:28 fw kernel: frandom: Seeded global generator now (used by erandom)
Feb 22 21:53:28 fw kernel: apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16)
Feb 22 21:53:28 fw kernel: apm: disabled - APM is not SMP safe.
Feb 22 21:53:28 fw kernel: usb.c: registered new driver usbdevfs
Feb 22 21:53:28 fw kernel: usb.c: registered new driver hub
Feb 22 21:53:28 fw kernel: usb-uhci.c: $Revision: 1.275
Feb 22 21:53:28 fw kernel: usb-uhci.c: High bandwidth mode enabled
Feb 22 21:53:28 fw kernel: usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
Feb 22 21:53:28 fw kernel: SCSI subsystem driver Revision: 1.00
Feb 22 21:53:28 fw kernel: Initializing USB Mass Storage driver...
Feb 22 21:53:28 fw kernel: usb.c: registered new driver usb-storage
Feb 22 21:53:28 fw kernel: USB Mass Storage support registered.
Feb 22 21:53:28 fw kernel: usb.c: registered new driver hiddev
Feb 22 21:53:28 fw kernel: usb.c: registered new driver hid
Feb 22 21:53:28 fw kernel: hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vojtech@suse.cz>
Feb 22 21:53:28 fw kernel: hid-core.c: USB HID support drivers
Feb 22 21:53:28 fw kernel: usb.c: registered new driver acm
Feb 22 21:53:28 fw kernel: acm.c: v0.21:USB Abstract Control Model driver for USB modems and ISDN adapters
Feb 22 21:53:28 fw kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,4), internal journal
Feb 22 21:53:28 fw kernel: kjournald starting.  Commit interval 5 seconds
Feb 22 21:53:28 fw kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,1), internal journal
Feb 22 21:53:28 fw kernel: EXT3-fs: mounted filesystem with ordered data mode.
Feb 22 21:53:29 fw kernel: kjournald starting.  Commit interval 5 seconds
Feb 22 21:53:29 fw kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,2), internal journal
Feb 22 21:53:29 fw kernel: EXT3-fs: mounted filesystem with ordered data mode.
Feb 22 21:53:29 fw kernel: Adding Swap: 32764k swap-space (priority -1)
Feb 22 21:53:29 fw kernel: ip_tables: (C) 2000-2002 Netfilter core team
Feb 22 21:53:29 fw kernel: ip_conntrack version 2.1 (4023 buckets, 32184 max) - 308 bytes per conntrack
Feb 22 21:53:29 fw kernel: ip_conntrack_pptp version 1.9 loaded
Feb 22 21:53:29 fw kernel: ip_nat_pptp version 1.5 loaded
Feb 22 21:53:29 fw kernel: usb-uhci.c: $Revision: 1.275
Feb 22 21:53:29 fw kernel: usb-uhci.c: High bandwidth mode enabled
Feb 22 21:53:29 fw kernel: usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
Feb 22 21:53:29 fw kernel: Intel(R) PRO/1000 Network Driver - version 7.6.12
Feb 22 21:53:29 fw kernel: Copyright (c) 1999-2007 Intel Corporation.
Feb 22 21:53:29 fw kernel: e1000: 03:00.0: e1000_probe: (PCI Express:2.5Gb/s:Width x4) 00:15:17:44:bd:3c
Feb 22 21:53:29 fw kernel: e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
Feb 22 21:53:29 fw kernel: e1000: 03:00.1: e1000_probe: (PCI Express:2.5Gb/s:Width x4) 00:15:17:44:bd:3d
Feb 22 21:53:29 fw kernel: e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection
Feb 22 21:53:29 fw kernel: e1000: 04:00.0: e1000_probe: (PCI Express:2.5Gb/s:Width x4) 00:15:17:44:bd:3e
Feb 22 21:53:29 fw kernel: e1000: eth2: e1000_probe: Intel(R) PRO/1000 Network Connection
Feb 22 21:53:29 fw kernel: e1000: 04:00.1: e1000_probe: (PCI Express:2.5Gb/s:Width x4) 00:15:17:44:bd:3f
Feb 22 21:53:29 fw kernel: e1000: eth3: e1000_probe: Intel(R) PRO/1000 Network Connection
Feb 22 21:53:29 fw kernel: e1000: eth1: e1000_request_irq: Unable to allocate interrupt Error: -16
Feb 22 21:53:29 fw kernel: e1000: eth1: e1000_request_irq: Unable to allocate interrupt Error: -16
Feb 22 21:53:30 fw kernel: e1000: eth0: e1000_watchdog_task: NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX
Feb 22 21:53:31 fw dnsmasq[429]: started, version 2.38 cachesize 150
Feb 22 21:53:31 fw dnsmasq[429]: compile time options: no-IPv6 GNU-getopt ISC-leasefile no-DBus no-I18N TFTP
Feb 22 21:53:31 fw dnsmasq[429]: reading /var/state/dhcp/dhcpd.leases
Feb 22 21:53:31 fw dnsmasq[429]: reading /etc/resolv.conf
Feb 22 21:53:31 fw dnsmasq[429]: ignoring nameserver 127.0.0.1 - local interface
Feb 22 21:53:31 fw dnsmasq[429]: read /etc/hosts - 7 addresses
Feb 22 21:53:31 fw ipcop: Starting RED device eth3.
Feb 22 21:53:32 fw dnsmasq[474]: started, version 2.38 cachesize 150
Feb 22 21:53:32 fw dnsmasq[474]: compile time options: no-IPv6 GNU-getopt ISC-leasefile no-DBus no-I18N TFTP
Feb 22 21:53:32 fw dnsmasq[474]: reading /var/state/dhcp/dhcpd.leases
Feb 22 21:53:32 fw dnsmasq[474]: reading /var/ipcop/red/resolv.conf
Feb 22 21:53:32 fw dnsmasq[474]: using nameserver 195.238.2.22#53
Feb 22 21:53:32 fw dnsmasq[474]: using nameserver 195.238.2.21#53
Feb 22 21:53:32 fw dnsmasq[474]: read /etc/hosts - 7 addresses
Feb 22 21:53:33 fw rc.updatered: pid 442 end
Feb 22 21:53:34 fw fcron[551]: fcron[551] 3.0.1 started
Feb 22 21:53:34 fw fcron[551]: updating configuration from /var/spool/cron
Feb 22 21:53:34 fw fcron[551]: adding file root
Feb 22 21:53:35 fw dhcpd: Wrote 54 leases to leases file.
Feb 22 21:53:35 fw dhcpd:
Feb 22 21:53:35 fw dhcpd: No subnet declaration for eth1 (0.0.0.0).
Feb 22 21:53:35 fw dhcpd: ** Ignoring requests on eth1.  If this is not what
Feb 22 21:53:35 fw dhcpd:    you want, please write a subnet declaration
Feb 22 21:53:35 fw dhcpd:    in your dhcpd.conf file for the network segment
Feb 22 21:53:35 fw dhcpd:    to which interface eth1 is attached. **
Feb 22 21:53:35 fw dhcpd:
Feb 22 21:53:36 fw sshd[576]: Server listening on 0.0.0.0 port 222.
Feb 22 21:53:37 fw dhcpd: DHCPDISCOVER from 00:0e:a6:8e:88:aa via eth0
Feb 22 21:53:38 fw dhcpd: DHCPOFFER on 192.168.1.254 to 00:0e:a6:8e:88:aa (laptop) via eth0
Feb 22 21:53:38 fw dhcpd: DHCPREQUEST for 192.168.1.254 (192.168.1.1) from 00:0e:a6:8e:88:aa (laptop) via eth0
Feb 22 21:53:38 fw dhcpd: DHCPACK on 192.168.1.254 to 00:0e:a6:8e:88:aa (laptop) via eth0
Feb 22 21:53:39 fw dnsmasq[474]: reading /var/state/dhcp/dhcpd.leases
Feb 22 21:53:50 fw squid[589]: Squid Parent: child process 591 started
Feb 22 21:53:50 fw dhcpd: DHCPINFORM from 192.168.1.254 via eth0
Feb 22 21:53:50 fw dhcpd: DHCPACK to 192.168.1.254 (00:0e:a6:8e:88:aa) via eth0
Feb 22 21:53:50 fw ipcop: IPCop started.
Feb 22 21:53:50 fw init: Entering runlevel: 3
Feb 22 21:53:53 fw dhcpd: DHCPINFORM from 192.168.1.254 via eth0
Feb 22 21:53:53 fw dhcpd: DHCPACK to 192.168.1.254 (00:0e:a6:8e:88:aa) via eth0
Feb 22 21:55:00 fw fcron[627]: Job [ -f "/var/ipcop/red/active" ] && /usr/local/bin/setddns.pl started for user root (pid 628)
Feb 22 21:55:00 fw fcron[629]: Job /usr/local/bin/makegraphs >/dev/null started for user root (pid 630)
Feb 22 21:55:00 fw fcron[632]: Job /usr/local/bin/timecheck > /dev/null 2>&1 started for user root (pid 634)
Feb 22 21:55:02 fw fcron[627]: Job [ -f "/var/ipcop/red/active" ] && /usr/local/bin/setddns.pl completed
Feb 22 21:55:02 fw fcron[632]: Job /usr/local/bin/timecheck > /dev/null 2>&1 completed
Feb 22 21:55:29 fw fcron[629]: Job /usr/local/bin/makegraphs >/dev/null completed
Feb 22 21:55:31 fw dhcpd: DHCPINFORM from 192.168.1.254 via eth0
Feb 22 21:55:31 fw dhcpd: DHCPACK to 192.168.1.254 (00:0e:a6:8e:88:aa) via eth0
Feb 22 21:55:34 fw dhcpd: DHCPINFORM from 192.168.1.254 via eth0
Feb 22 21:55:34 fw dhcpd: DHCPACK to 192.168.1.254 (00:0e:a6:8e:88:aa) via eth0
Feb 22 21:55:52 fw sshd[649]: Accepted password for root from 192.168.1.254 port 2640 ssh2
Feb 22 21:55:52 fw sshd[649]: subsystem request for sftp
Feb 22 21:57:13 fw dhcpd: DHCPINFORM from 192.168.1.254 via eth0
Feb 22 21:57:13 fw dhcpd: DHCPACK to 192.168.1.254 (00:0e:a6:8e:88:aa) via eth0
Feb 22 21:57:17 fw dhcpd: DHCPINFORM from 192.168.1.254 via eth0
Feb 22 21:57:17 fw dhcpd: DHCPACK to 192.168.1.254 (00:0e:a6:8e:88:aa) via eth0
Feb 22 21:58:57 fw dhcpd: DHCPINFORM from 192.168.1.254 via eth0
Feb 22 21:58:57 fw dhcpd: DHCPACK to 192.168.1.254 (00:0e:a6:8e:88:aa) via eth0
Feb 22 21:59:00 fw dhcpd: DHCPINFORM from 192.168.1.254 via eth0
Feb 22 21:59:00 fw dhcpd: DHCPACK to 192.168.1.254 (00:0e:a6:8e:88:aa) via eth0
Feb 22 22:00:00 fw fcron[652]: Job [ -f "/var/ipcop/red/active" ] && /usr/local/bin/setddns.pl started for user root (pid 653)
Feb 22 22:00:00 fw fcron[654]: Job /usr/local/bin/makegraphs >/dev/null started for user root (pid 655)
Feb 22 22:00:00 fw fcron[657]: Job /usr/local/bin/timecheck > /dev/null 2>&1 started for user root (pid 659)
Feb 22 22:00:02 fw fcron[652]: Job [ -f "/var/ipcop/red/active" ] && /usr/local/bin/setddns.pl completed
Feb 22 22:00:02 fw fcron[657]: Job /usr/local/bin/timecheck > /dev/null 2>&1 completed
Feb 22 22:00:12 fw fcron[654]: Job /usr/local/bin/makegraphs >/dev/null completed
Feb 22 22:00:28 fw dhcpd: DHCPINFORM from 192.168.1.254 via eth0
Feb 22 22:00:28 fw dhcpd: DHCPACK to 192.168.1.254 (00:0e:a6:8e:88:aa) via eth0
Feb 22 22:00:31 fw dhcpd: DHCPINFORM from 192.168.1.254 via eth0
Feb 22 22:00:31 fw dhcpd: DHCPACK to 192.168.1.254 (00:0e:a6:8e:88:aa) via eth0
Feb 22 22:02:18 fw dhcpd: DHCPINFORM from 192.168.1.254 via eth0
Feb 22 22:02:18 fw dhcpd: DHCPACK to 192.168.1.254 (00:0e:a6:8e:88:aa) via eth0
Feb 22 22:02:22 fw dhcpd: DHCPINFORM from 192.168.1.254 via eth0
Feb 22 22:02:22 fw dhcpd: DHCPACK to 192.168.1.254 (00:0e:a6:8e:88:aa) via eth0
Feb 22 22:03:44 fw dhcpd: DHCPINFORM from 192.168.1.254 via eth0
Feb 22 22:03:44 fw dhcpd: DHCPACK to 192.168.1.254 (00:0e:a6:8e:88:aa) via eth0
Feb 22 22:03:47 fw dhcpd: DHCPINFORM from 192.168.1.254 via eth0
Feb 22 22:03:47 fw dhcpd: DHCPACK to 192.168.1.254 (00:0e:a6:8e:88:aa) via eth0
Feb 22 22:05:00 fw fcron[674]: Job [ -f "/var/ipcop/red/active" ] && /usr/local/bin/setddns.pl started for user root (pid 675)
Feb 22 22:05:00 fw fcron[676]: Job /usr/local/bin/makegraphs >/dev/null started for user root (pid 677)
Feb 22 22:05:00 fw fcron[680]: Job /usr/local/bin/timecheck > /dev/null 2>&1 started for user root (pid 681)
Feb 22 22:05:02 fw fcron[674]: Job [ -f "/var/ipcop/red/active" ] && /usr/local/bin/setddns.pl completed
Feb 22 22:05:02 fw fcron[680]: Job /usr/local/bin/timecheck > /dev/null 2>&1 completed
Feb 22 22:05:12 fw fcron[676]: Job /usr/local/bin/makegraphs >/dev/null completed
Feb 22 22:05:32 fw dhcpd: DHCPINFORM from 192.168.1.254 via eth0
Feb 22 22:05:32 fw dhcpd: DHCPACK to 192.168.1.254 (00:0e:a6:8e:88:aa) via eth0
Feb 22 22:05:36 fw dhcpd: DHCPINFORM from 192.168.1.254 via eth0
Feb 22 22:05:36 fw dhcpd: DHCPACK to 192.168.1.254 (00:0e:a6:8e:88:aa) via eth0
Feb 22 22:06:09 fw kernel: e1000: eth0: e1000_watchdog_task: NIC Link is Down
Feb 22 22:09:23 fw kernel: e1000: eth0: e1000_watchdog_task: NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX
Feb 22 22:09:28 fw dhcpd: DHCPREQUEST for 192.168.1.254 from 00:0e:a6:8e:88:aa (laptop) via eth0
Feb 22 22:09:28 fw dhcpd: DHCPACK on 192.168.1.254 to 00:0e:a6:8e:88:aa (laptop) via eth0
Feb 22 22:09:31 fw dnsmasq[474]: reading /var/state/dhcp/dhcpd.leases
Feb 22 22:09:31 fw sshd[696]: Accepted password for root from 192.168.1.254 port 3141 ssh2
Feb 22 22:09:31 fw sshd[696]: subsystem request for sftp


Feb 22 21:53:35 fw dhcpd:
Feb 22 21:53:35 fw dhcpd: No subnet declaration for eth1 (0.0.0.0).
Feb 22 21:53:35 fw dhcpd: ** Ignoring requests on eth1. If this is not what
Feb 22 21:53:35 fw dhcpd: you want, please write a subnet declaration
Feb 22 21:53:35 fw dhcpd: in your dhcpd.conf file for the network segment
Feb 22 21:53:35 fw dhcpd: to which interface eth1 is attached. **
Feb 22 21:53:35 fw dhcpd:

donc par acquis de conscience, j'ai été voir le contenu du fichier dhcpd.conf

Code: Tout sélectionner

ddns-update-style none;
deny bootp;   #default
authoritative;

subnet 192.168.1.0 netmask 255.255.255.0 #GREEN
{
   range 192.168.1.2 192.168.1.254;
   option subnet-mask 255.255.255.0;
   option domain-name "reseau.xxxxx.be";
   option routers 192.168.1.1;
   option domain-name-servers 192.168.100.10;
   option netbios-name-servers 192.168.100.10;
   default-lease-time 3600;
   max-lease-time 7200;
} #GREEN

subnet 192.168.2.0 netmask 255.255.255.0 #BLUE
{
   range 192.168.2.100 192.168.2.254;
   option subnet-mask 255.255.255.0;
   option domain-name "habitantes.xxxxx.be";
   option routers 192.168.2.1;
   option domain-name-servers 192.168.2.1;
   option netbios-name-servers 192.168.100.10;
   default-lease-time 3600;
   max-lease-time 7200;
} #BLUE


En esperant que vous puissiez m'aider.

[foxco]

Toujours en quête de solution,
je fait un ifconfig eth1 up
et j'obtiens le message :

siocsifflags : device or resouce busy

[Gesp]

tu utilises quel noyau au démarrage?

Je pense que tu as sélectionné le 4ème choix acpi+ht.

Il faudrait que l'on change dans /boot/grub/grub.conf la partie acpi=ht en pci=acpi (ou voir ne rien mettre).
acpi=ht désactive une partie de l'acpi et les bios des machines modernes ne sont plus testé sans acpi et comportent des bugs de ce coté. Donc autant utiliser acpi totalement et le mieux est de tester sans acpi=ht

Voir sur http://en.opensuse.org/SDB:Kernel_Param ... _ACPI/APIC pour plus de détails

[foxco]

Je te remercie pour l'interet que tu portes a mon soucis.

Malheureusement, cela ne résoud pas mon probleme.
En ayant supprimé acpi=ht
ou en l'ayant remplacé par pci=acpi la problématique reste la meme.

Je dois malheureusement remettre cela sur pied pour ce soir, le temps m'est donc compté.

Je me demande si quelque chose n'a pas foiré dans les mises a jour car je peux lire 2x la .18

Ne serait il pas plus sage de recuperer certains fichiers de config et de refaire une install a partir de rien ?
Cela ne me plait pas plus que cela car je devrai reconfigurer squid, la zone bleue, ...

Dans l'attente de vous lire.

[Gesp]

Je me demande si quelque chose n'a pas foiré dans les mises a jour car je peux lire 2x la .18

J'ai retiré le blocage sur l'application d'une même mise à jour.
On peut maintenant appliquer une même mise à jour plusieurs fois, c'est testé comme cela.

Je pense que le problème vient de la mise à jour du driver e1000 en 7.6.12 en 1.4.17.
Mais cela n'apparait pas très clairement dans le changelog du 7.6.12

FIXES
compile fixes for newer kernels.
ethtool fix for flow control settings when resetting auto-negotiation.
avoid excessive ethtool or mii-tool generated PHY reads while autonegotiating, could cause no-link condition.

FEATURES
copy netdev feature flags to vlan devices to enable TSO or TCP checksum offload on vlan transmits.

Mise à jour 7.6.15:

- new 2.6.24 compatibility
- [FIX] use return values directly from pci_resource*
from Ben Herrenschmidt, he noticed on ppc64 kernels running on 32
bit userspace, that some of the values returned here are
truncated by the size of our variables.
- fix 2.4 kernel build error
- [FEATURE] update some stats in real time
- various flag cleanups
- [FEATURE] user can now modify InterruptThrottleRate settings using ethtool -C rx-usecs N
- [FIX] reduce binary size by making register test a function
- [FIX] disabling TSO while vlans are enabled causes a panic
- [FIX] semaphore fixes for ES2LAN (ESB2) phy access
- [FEATURE] alternate MAC address support for ES2LAN(ESB2)
- [FIX] resolve MDIC timeouts when resetting ESB2 parts if the internal BMC is enabled
- [FIX] serdes link issues

Mise à jour 7.6.15.4

il n'y a rien de marqué

Il faudrait revenir dans la version précédente contenu dans la mise à jour 1.4.13.
Voici ce que tu peux faire pour juste revenir à la version précéente de e1000

Copie la mise à jour 1.4.13 dans /var/patches sous le nom patch.gpg (peu importe le nom mais il faut être cohérent dans les commandes après)

Code: Tout sélectionner

/usr/bin/gpg --batch  --homedir /root/.gnupg -o /var/patches/patch-1.tgz --decrypt /var/patches/patch.gpg
# ls /var/patches doit montrer patch-1.tgz et patch.gpg
rm /var/patches/patch.gpg;# faire de la place

cd /var/patches; tar zxf patch-1.tgz
# ls /var/patches doit montrer setup,information et patch.tar.gz
rm /var/patches/patch-1.tgz;# faire encore de la place

cd /var/patches; tar zvxf patch.tar.gz -C / lib/modules/2.4.34*/kernel/drivers/net/e1000/e1000.o.gz

# normalement tu as eu les 2 modules (normal et smp) extraits

# redémarrer le réseau en rechargeant le module restauré
/usr/local/bin/restartnetwork


et puis surtout reporte si cela a changé quelquechose.

[foxco]

Ca fonctionne -> Patte bleue a nouveau fonctionnelle

Merci infiniment.

1. Dois je remodifier les parametres du boot ?
pour le moment j'utilise le choix #4
kernet /vmlinuz-smp root=/dev/hda4 panic=10 pci=acpi ro

2. Dois je éviter les futures mises a jour ?

[Gesp]

1. Dois je remodifier les parametres du boot ?

Si cela fonctionne, ne casse rien

Dois je éviter les futures mises a jour ?

I faudrait que je te fasse essayer la dernière version e1000 pour savoir si c'est réparé ou s'il faut reporter le bug.

[foxco]

Très bien, souhaites tu faire cela aujourd'hui tant que la machine est au bureau ?

idéalement, je dois la ramener dans son environnement de production en fin d'après midi.

[Gesp]

Pas dans l'après-midi.

Parce que la prochaine version aura le noyau 2.4.36, il faut que je compile la version 1.4.18 avec le noyau 2.4.34 puis que je compile la nouvelle version e1000. Il me faudra bien 2 h pour être arrivé au bout de tout cela (je viens de lancer la compilation et j'ai aussi d'autres choses à faire)

[foxco]

Te tracasses pas,
Je me bats avec l'install de BOT.
Donc ce firewall ne sera pas en place ce soir ...


deplus, je me rends compte que je ne peux plus acceder a l'onglet blue access ...
[edit] -> j'ai supprimé le contenu du fichier /var/ipcop/wireless/config et tout est en ordre


Question subsidiaire :
Pourquoi l'insertion d'ip dans acces blue prends elle tant de temps ?

[Gesp]

Pourquoi l'insertion d'ip dans acces blue prends elle tant de temps ?

Je ne sais pas.
Qu'est-ce qu'il se passe exactement?

Le driver e1000-7.6.15.4 est disponible à cette adresse
http://g.esp.free.fr/download/e1000-7.6 ... 2.4.34.tgz

Sauvegarde avant les anciens drivers qui fonctionnent

Code: Tout sélectionner

cd /tmp
tar cvzf e1000-7.6.12.tgz lib/modules/2.4.34*/kernel/drivers/net/e1000/e1000.o.gz

copie les drivers dans /tmp puis

Code: Tout sélectionner

cd /tmp
tar zvxf e1000-7.6.15.4-linux-2.4.34.tgz -C /
/usr/local/bin/restartnetwork

[foxco]

j'ai fait cela, maintenant je n'ai plus de carte reseau reconnue,
je boot et me logue en tant que root, je lance un setup, la recherche de pilotes auto ne traouve rien
et quand je choisis moi meme la carte, il m'indique impossible de trouver les pilotes ...

comment puis je revenir a la situation precedente ?

Merci.

Pour la lenteur 'zone bleue' après avoir introduit une ip, je dois attendre 45 secondes avant que la page ne se recharge ...

je n'ai pas essayé de joindre cette page avant de passer a l'instal de BOT

Je suis a deux doigts de desinstaller BOT,
BOT que j'ai installé uniquement pour pouvoir utiliser un serveur dans la zone orange pour servir de print server pour blue et green.

Ne serais ce pas plus sage de définir une regle dans iptables pour cet usage uniquement au lieu d''encombrer' mon firewall avec cela ?

Quoi qu'il en soit, je suis très embeté par la situation actuelle.

Merci pour ton feedback.

[Gesp]

Cela veut-il dire que e1000-7.6.15.4 est pire encore?
Tu n'as que e1000 comme driver?

Quand tu fais ifconfig, est-ce que les interfaces s'affichent (sont up)?

Si oui, met les toutes down et regarde le message quand tu tapes

Code: Tout sélectionner

modprobe -r e1000
modprobe e1000

Reboote après pour repartir d'un état connu.

[foxco]

non, un ifconfig ne me donne plus de ethx.
Je n'ai plus que lo

si je tape modprobe -r e1000
aucun resultat

si je tape modprobe e1000
j'obtiens un ecran complet me donnant le chemin du pilote et ensuite une mention :
unresolved symbol request_irq_T0c60f2e0

(plusieurs fois)

pour ensuite se terminer par insmod e1000 failed

J'ai donc repris ton precedent post :

cd /var/patches; tar zvxf patch.tar.gz -C / lib/modules/2.4.34*/kernel/drivers/net/e1000/e1000.o.gz

/usr/local/bin/restartnetwork

et c'est reparti

[Gesp]

Ok restaure la connexion pour pouvoir charger un nouveau paquet:

Code: Tout sélectionner

cd /tmp; tar xvzf e1000-7.6.12.tgz -C /
restartnetwork

Là le réseau doit fonctionner à nouveau.
Recharge le paquet à la même adresse, cette fois ci il inclut le vmlinuz et System.map donc tu n'auras plus de unresolved symbols
http://g.esp.free.fr/download/e1000-7.6 ... 2.4.34.tgz

Code: Tout sélectionner

cd /tmp
tar zvxf e1000-7.6.15.4-linux-2.4.34.tgz -C /
restartnetwork
reboot #parce que le noyau a été changé