thr3ads.net - CentOS - [CentOS] latest kernel [Sep 2006]

If this information is useful, please help other people find it:
Share via:

David Hrbáč

2006-Sep-01 19:12 UTC

[CentOS] latest kernel

Micha Silver napsal(a):> Today I updated several servers running CentOS 4.3, and got the new
> 2.6.9-42 kernel. One of the machines serves as our firewall. After
> rebooting I lost all forwarding thru the machine. I reverted back to the
> 2.6.9-34 kernel and connectivity returned. During the few minutes that
> the new kernel was running I checked that the routing table looked OK,
> and with tcpdump I saw that indeed no traffic was going thru from the
> externel interface to any of the internal interfaces.
> 
> Has anyone seen similar behavior??
> 
Had no time to update all routers I have, but two were updated. Both
work smoothly (except shaping, which is resolved by update iproute package).
David

Marko A. Jennings

2006-Sep-01 19:13 UTC

head link

[CentOS] latest kernel

On Fri, September 1, 2006 4:04 pm, Micha Silver wrote:> Today I updated several servers running CentOS 4.3, and got the new
> 2.6.9-42 kernel. One of the machines serves as our firewall. After
> rebooting I lost all forwarding thru the machine. I reverted back to the
> 2.6.9-34 kernel and connectivity returned. During the few minutes that
> the new kernel was running I checked that the routing table looked OK,
> and with tcpdump I saw that indeed no traffic was going thru from the
> externel interface to any of the internal interfaces.
>
> Has anyone seen similar behavior??
>
The two firewalls I upgraded to 2.6.9-42 have been working just fine.

Micha Silver

2006-Sep-01 20:04 UTC

head link

[CentOS] latest kernel

Today I updated several servers running CentOS 4.3, and got the new 
2.6.9-42 kernel. One of the machines serves as our firewall. After 
rebooting I lost all forwarding thru the machine. I reverted back to the 
2.6.9-34 kernel and connectivity returned. During the few minutes that 
the new kernel was running I checked that the routing table looked OK, 
and with tcpdump I saw that indeed no traffic was going thru from the 
externel interface to any of the internal interfaces.

Has anyone seen similar behavior??

Clive Gould

2006-Sep-02 19:37 UTC

head link

[CentOS] latest kernel

Marko

I have 5 servers running CentOS.

Four of them work fine with the 42 kernel.

The fifth I use as a yum respository and when I try to use the 42 kernel I
lose all network connectivity.

Reverting to the earlier kernel on this box restores connectivity.

I append some dmesg excerpts which suggest that the new kernel handles PCI
(GSI) differently, but have not had the time to investigate further.

Please let me know if you find a solution.

Best wishes

Clive


dmesg excerpt for 42 kernel:

PCI: Probing PCI hardware (bus 00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 10 11 12 14 15) *9
ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [ALKA] (IRQs 16 17 18 19 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [ALKB] (IRQs 16 17 18 19 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [ALKC] (IRQs 22) *0, disabled.
ACPI: PCI Interrupt Link [ALKD] (IRQs 21) *0, disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: Using ACPI for IRQ routing
ACPI: PCI interrupt 0000:00:05.0[A]: no GSI - using IRQ 11
ACPI: PCI interrupt 0000:00:06.0[A]: no GSI - using IRQ 5
ACPI: PCI interrupt 0000:00:0e.0[A]: no GSI - using IRQ 5
ACPI: PCI interrupt 0000:00:11.1[A]: no GSI
ACPI: PCI interrupt 0000:00:11.2[D]: no GSI - using IRQ 11
ACPI: PCI interrupt 0000:00:11.3[D]: no GSI - using IRQ 11
ACPI: PCI interrupt 0000:00:11.5[C]: no GSI - using IRQ 9
ACPI: PCI interrupt 0000:01:00.0[A]: no GSI - using IRQ 11
apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
apm: overridden by ACPI.

8139cp: 10/100 PCI Ethernet driver v1.2 (Mar 22, 2004)
8139cp: pci dev 0000:00:0e.0 (id 10ec:8139 rev 10) is not an 8139C+
compatible chip
8139cp: Try the "8139too" driver instead.
ACPI: PCI interrupt 0000:00:06.0[A]: no GSI - using IRQ 5
3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
0000:00:06.0: 3Com PCI 3c905B Cyclone 100baseTx at 0xa400. Vers LK1.1.19
divert: allocating divert_blk for eth0
via-rhine.c:v1.10-LK1.2.0-2.6 June-10-2004 Written by Donald Becker
ACPI: PCI interrupt 0000:00:05.0[A]: no GSI - using IRQ 11
divert: allocating divert_blk for eth1
eth1: VIA Rhine at 0xe3000000, 00:50:ba:a1:86:44, IRQ 11.
eth1: MII PHY found at address 8, status 0x7809 advertising 05e1 Link 0000.
8139too Fast Ethernet driver 0.9.27
ACPI: PCI interrupt 0000:00:0e.0[A]: no GSI - using IRQ 5
divert: allocating divert_blk for eth2
eth2: RealTek RTL8139 at 0xa800, 00:10:dc:59:bd:dc, IRQ 5
eth2:  Identified 8139 chip type 'RTL-8101'
ACPI: PCI interrupt 0000:00:11.5[C]: no GSI - using IRQ 9
PCI: Setting latency timer of device 0000:00:11.5 to 64
pciehp: acpi_pciehprm:\_SB_.PCI0 evaluate _BBN fail=0x5
pciehp: acpi_pciehprm:get_device PCI ROOT HID fail=0x5
USB Universal Host Controller Interface driver v2.2
ACPI: PCI interrupt 0000:00:11.2[D]: no GSI - using IRQ 11

dmesg excerpt for 34 kernel:

PCI: Probing PCI hardware (bus 00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 10 11 12 14 15) *9
ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [ALKA] (IRQs 16 17 18 19 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [ALKB] (IRQs 16 17 18 19 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [ALKC] (IRQs 22) *0, disabled.
ACPI: PCI Interrupt Link [ALKD] (IRQs 21) *0, disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: Using ACPI for IRQ routing
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
ACPI: PCI interrupt 0000:00:05.0[A] -> GSI 11 (level, low) -> IRQ 11
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 5
ACPI: PCI interrupt 0000:00:06.0[A] -> GSI 5 (level, low) -> IRQ 5
ACPI: PCI interrupt 0000:00:0e.0[A] -> GSI 5 (level, low) -> IRQ 5
ACPI: PCI interrupt 0000:00:11.1[A] -> GSI 11 (level, low) -> IRQ 11
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
ACPI: PCI interrupt 0000:00:11.2[D] -> GSI 11 (level, low) -> IRQ 11
ACPI: PCI interrupt 0000:00:11.3[D] -> GSI 11 (level, low) -> IRQ 11
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10
ACPI: PCI interrupt 0000:00:11.5[C] -> GSI 10 (level, low) -> IRQ 10
ACPI: PCI interrupt 0000:01:00.0[A] -> GSI 11 (level, low) -> IRQ 11

8139too Fast Ethernet driver 0.9.27
ACPI: PCI interrupt 0000:00:0e.0[A] -> GSI 5 (level, low) -> IRQ 5
divert: allocating divert_blk for eth0
eth0: RealTek RTL8139 at 0xa800, 00:10:dc:59:bd:dc, IRQ 5
eth0:  Identified 8139 chip type 'RTL-8101'
ACPI: PCI interrupt 0000:00:06.0[A] -> GSI 5 (level, low) -> IRQ 5
3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
0000:00:06.0: 3Com PCI 3c905B Cyclone 100baseTx at 0xa400. Vers LK1.1.19
divert: allocating divert_blk for eth1
via-rhine.c:v1.10-LK1.2.0-2.6 June-10-2004 Written by Donald Becker
ACPI: PCI interrupt 0000:00:05.0[A] -> GSI 11 (level, low) -> IRQ 11
divert: allocating divert_blk for eth2
eth2: VIA Rhine at 0xe3000000, 00:50:ba:a1:86:44, IRQ 11.
eth2: MII PHY found at address 8, status 0x7809 advertising 05e1 Link 0000.
ACPI: PCI interrupt 0000:00:11.5[C] -> GSI 10 (level, low) -> IRQ 10
PCI: Setting latency timer of device 0000:00:11.5 to 64
pciehp: acpi_pciehprm:\_SB_.PCI0 evaluate _BBN fail=0x5
pciehp: acpi_pciehprm:get_device PCI ROOT HID fail=0x5
USB Universal Host Controller Interface driver v2.2
ACPI: PCI interrupt 0000:00:11.2[D] -> GSI 11 (level, low) -> IRQ 11
uhci_hcd 0000:00:11.2: UHCI Host Controller
uhci_hcd 0000:00:11.2: irq 11, io base 0000b000
uhci_hcd 0000:00:11.2: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ACPI: PCI interrupt 0000:00:11.3[D] -> GSI 11 (level, low) -> IRQ 11


Message: 34
Date: Fri, 1 Sep 2006 15:13:02 -0400 (EDT)
From: "Marko A. Jennings" <markobiz at bluegargoyle.com>
Subject: Re: [CentOS] latest kernel
To: centos at centos.org
Message-ID: <48730.192.168.77.10.1157137982.squirrel at bluegargoyle.com>
Content-Type: text/plain;charset=iso-8859-1

On Fri, September 1, 2006 4:04 pm, Micha Silver wrote:> Today I updated several servers running CentOS 4.3, and got the new
> 2.6.9-42 kernel. One of the machines serves as our firewall. After
> rebooting I lost all forwarding thru the machine. I reverted back to the
> 2.6.9-34 kernel and connectivity returned. During the few minutes that
> the new kernel was running I checked that the routing table looked OK,
> and with tcpdump I saw that indeed no traffic was going thru from the
> externel interface to any of the internal interfaces.
>
> Has anyone seen similar behavior??
>

Apparently Analagous Threads

Search for more reasonably related threads

CentOS - Sep 2006 - latest kernel

[CentOS] latest kernel

[CentOS] latest kernel

[CentOS] latest kernel

[CentOS] latest kernel

Apparently Analagous Threads