* bnx2 vlan issue
@ 2011-03-17 14:51 Seblu
2011-03-17 18:02 ` Seblu
0 siblings, 1 reply; 13+ messages in thread
From: Seblu @ 2011-03-17 14:51 UTC (permalink / raw)
To: netdev
[-- Attachment #1: Type: text/plain, Size: 6567 bytes --]
Good Afternoon Gentleman,
I've an issue with a 2.6.38 (vanilla) on a debian unstable distro. I
attached an lspci and lshw about hardware. I also attached debian
network config file.
My host is a host kvm which run vm on different networks (vlan). I
have 2 1Gbit/s card (eth0, eth1) and 1 10Gbit/s card (eth2).
I use bonding (bond0) mode 1 on the 1Gbit/s cards.
vlan 14 and 15 are only availlable trought 1G cards. Same tagging on
both cards in switch. 14 is untagged (need for pxe) and 15 is tagged.
Every network on my host is in a bridge. Eg:
vlan 15 is in br15 by bond0.15 as member,
vlan 14 is in br14 by bond0 as member,
vlan 20 is in br20 by eth2.20
The issue is simple, packets from vlan 15 which are tagged are not
visible on bond0.15 but in bond0 (see capture). Like if there is no
vlan.
we see rx packet on bond0
bond0 Link encap:Ethernet HWaddr 5c:26:0a:fc:f1:14
UP BROADCAST RUNNING PROMISC MASTER MULTICAST MTU:1500 Metric:1
RX packets:20219 errors:0 dropped:7999 overruns:0 frame:0
TX packets:2256 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3740193 (3.5 MiB) TX bytes:152212 (148.6 KiB)
we don't see rx packet (should see my ping)
bond0.15 Link encap:Ethernet HWaddr 5c:26:0a:fc:f1:14
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:2117 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:90162 (88.0 KiB)
and we see my ping in vlan 15 in bond0 (which is vlan14 untagged)
14:27:46.770375 00:1d:09:6b:45:27 > 5c:26:0a:fc:f1:14, ethertype
802.1Q (0x8100), length 102: vlan 15, p 0, ethertype IPv4, 10.15.242.1
> 10.15.0.42: ICMP echo request, id 23406, seq 1944, length 64
14:27:47.156674 00:25:64:1a:7b:13 > ff:ff:ff:ff:ff:ff, ethertype
802.1Q (0x8100), length 294: vlan 15, p 0, ethertype IPv4, 0.0.0.0.68
> 255.255.255.255.67: BOOTP/DHCP, Request from 00:25:64:1a:7b:13,
length 248
14:27:47.158508 00:16:3e:0a:a4:17 > ff:ff:ff:ff:ff:ff, ethertype
802.1Q (0x8100), length 347: vlan 15, p 0, ethertype IPv4,
10.15.255.250.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 301
14:27:47.160375 00:25:64:1a:7b:13 > ff:ff:ff:ff:ff:ff, ethertype
802.1Q (0x8100), length 294: vlan 15, p 0, ethertype IPv4, 0.0.0.0.68
> 255.255.255.255.67: BOOTP/DHCP, Request from 00:25:64:1a:7b:13,
length 248
14:27:47.161392 84:2b:2b:57:fa:61 > ff:ff:ff:ff:ff:ff, ethertype
802.1Q (0x8100), length 64: vlan 15, p 0, ethertype ARP, Request
who-has 10.15.104.31 (ff:ff:ff:ff:ff:ff) tell 10.15.104.31, length 46
14:27:47.162159 00:16:3e:0a:a4:17 > ff:ff:ff:ff:ff:ff, ethertype
802.1Q (0x8100), length 347: vlan 15, p 0, ethertype IPv4,
10.15.255.250.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 301
14:27:47.163991 00:25:64:1a:7b:13 > ff:ff:ff:ff:ff:ff, ethertype
802.1Q (0x8100), length 294: vlan 15, p 0, ethertype IPv4, 0.0.0.0.68
> 255.255.255.255.67: BOOTP/DHCP, Request from 00:25:64:1a:7b:13,
length 248
14:27:47.165625 00:16:3e:0a:a4:17 > ff:ff:ff:ff:ff:ff, ethertype
802.1Q (0x8100), length 347: vlan 15, p 0, ethertype IPv4,
10.15.255.250.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 301
14:27:47.167457 00:25:64:1a:7b:13 > ff:ff:ff:ff:ff:ff, ethertype
802.1Q (0x8100), length 294: vlan 15, p 0, ethertype IPv4, 0.0.0.0.68
> 255.255.255.255.67: BOOTP/DHCP, Request from 00:25:64:1a:7b:13,
length 248
14:27:47.169173 00:16:3e:0a:a4:17 > ff:ff:ff:ff:ff:ff, ethertype
802.1Q (0x8100), length 347: vlan 15, p 0, ethertype IPv4,
10.15.255.250.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 301
14:27:47.544048 5c:26:0a:fc:f1:14 > ff:ff:ff:ff:ff:ff, ethertype
802.1Q (0x8100), length 46: vlan 15, p 0, ethertype ARP, Request
who-has 10.15.255.42 tell 10.15.0.42, length 28
14:27:47.544238 52:54:00:5f:2b:fe > 5c:26:0a:fc:f1:14, ethertype
802.1Q (0x8100), length 64: vlan 15, p 0, ethertype ARP, Reply
10.15.255.42 is-at 52:54:00:5f:2b:fe, length 46
14:27:47.752880 00:1d:09:6b:45:27 > 5c:26:0a:fc:f1:14, ethertype
802.1Q (0x8100), length 102: vlan 15, p 0, ethertype IPv4, 10.15.242.1
> 10.15.0.42: ICMP echo request, id 23406, seq 1945, length 64
14:27:48.391137 00:26:b9:fb:f1:90 > 33:33:00:00:00:00, ethertype
802.1Q (0x8100), length 90: vlan 15, p 5, ethertype IPv6,
truncated-ip6 - 8160 bytes missing!:: > ff02::1: HBH ICMP6, multicast
listener queryv2 [gaddr ::[|icmp6], length 8184
14:27:48.431190 00:26:b9:fb:f1:90 > 01:00:5e:00:00:01, ethertype
802.1Q (0x8100), length 64: vlan 15, p 1, ethertype IPv4, 0.0.0.0 >
224.0.0.1: igmp query v2
14:27:48.544004 5c:26:0a:fc:f1:14 > ff:ff:ff:ff:ff:ff, ethertype
802.1Q (0x8100), length 46: vlan 15, p 0, ethertype ARP, Request
who-has 10.15.255.42 tell 10.15.0.42, length 28
14:27:48.544142 52:54:00:5f:2b:fe > 5c:26:0a:fc:f1:14, ethertype
802.1Q (0x8100), length 64: vlan 15, p 0, ethertype ARP, Reply
10.15.255.42 is-at 52:54:00:5f:2b:fe, length 46
14:27:48.723049 00:24:e8:7f:c4:58 > ff:ff:ff:ff:ff:ff, ethertype
802.1Q (0x8100), length 64: vlan 15, p 0, ethertype ARP, Request
who-has 10.15.102.21 (ff:ff:ff:ff:ff:ff) tell 10.15.102.21, length 46
14:27:48.752858 00:1d:09:6b:45:27 > 5c:26:0a:fc:f1:14, ethertype
802.1Q (0x8100), length 102: vlan 15, p 0, ethertype IPv4, 10.15.242.1
> 10.15.0.42: ICMP echo request, id 23406, seq 1946, length 64
14:27:48.776100 84:2b:2b:57:f6:d2 > ff:ff:ff:ff:ff:ff, ethertype
802.1Q (0x8100), length 64: vlan 15, p 0, ethertype ARP, Request
who-has 10.15.104.21 (ff:ff:ff:ff:ff:ff) tell 10.15.104.21, length 46
14:27:49.544049 5c:26:0a:fc:f1:14 > ff:ff:ff:ff:ff:ff, ethertype
802.1Q (0x8100), length 46: vlan 15, p 0, ethertype ARP, Request
who-has 10.15.255.42 tell 10.15.0.42, length 28
in dmesg in see something like : "8021q: adding VLAN 0 to HW filter on
device bond0".
Maybe there is something wrong with hardware filtering?
I don't find a way to disable hw vlan filtering.
# ethtool -K eth1 rxvlan off
Cannot set device flag settings: Invalid argument
I found a way to make thing work and don't work by one command.
# rmmod bonding
# ifdown br14
# ifdown br15
# ifup --force bond0
# ifup --force bond0.15
# ifup --force br15
=> i can ping my ip on 15 working
if i make ifup --force br14, i lost connectivity on vlan 15.
I don't have isssue when bond0 is not member of br14. So vlan on
bonding seems to be broken.
Regards,
--
Sébastien Luttringer
www.seblu.net
[-- Attachment #2: lshw --]
[-- Type: application/octet-stream, Size: 28084 bytes --]
test-hkvm-seblu
description: Multi-system
product: PowerEdge M610 ()
vendor: Winbond Electronics
version: PowerEdge M1000e
serial: 80ZTY4J
width: 64 bits
capabilities: smbios-2.6 dmi-2.6 vsyscall64 vsyscall32
configuration: boot=normal chassis=multi-system uuid=44454C4C-3000-105A-8054-B8C04F59344A
*-core
description: Motherboard
vendor: Winbond Electronics
physical id: 0
serial: .300HH4J..08.
slot: Slot 08
*-firmware
description: BIOS
vendor: Winbond Electronics
physical id: 0
version: 2.2.9
date: 10/25/2010
size: 64KiB
capacity: 4032KiB
capabilities: isa pci pnp upgrade shadowing cdboot bootselect edd int13floppytoshiba int13floppy360 int13floppy1200 int13floppy720 int9keyboard int14serial int10video acpi usb biosbootspecification netboot
*-cpu:0
description: CPU
product: Intel(R) Xeon(R) CPU L5640 @ 2.27GHz
vendor: Intel Corp.
physical id: 400
bus info: cpu@0
version: Intel(R) Xeon(R) CPU L5640 @ 2.27GHz
slot: CPU1
size: 2266MHz
capacity: 3600MHz
width: 64 bits
clock: 1565MHz
capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt aes lahf_lm ida arat tpr_shadow vnmi flexpriority ept vpid
configuration: cores=6 enabledcores=6 threads=12
*-cache:0
description: L1 cache
physical id: 700
size: 192KiB
capacity: 192KiB
capabilities: internal write-back data
*-cache:1
description: L2 cache
physical id: 701
size: 1536KiB
capacity: 2MiB
capabilities: internal write-back unified
*-cache:2
description: L3 cache
physical id: 702
size: 12MiB
capacity: 12MiB
capabilities: internal write-back unified
*-cpu:1
description: CPU
product: Intel(R) Xeon(R) CPU L5640 @ 2.27GHz
vendor: Intel Corp.
physical id: 401
bus info: cpu@1
version: Intel(R) Xeon(R) CPU L5640 @ 2.27GHz
slot: CPU2
size: 2266MHz
capacity: 3600MHz
width: 64 bits
clock: 1565MHz
capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt aes lahf_lm ida arat tpr_shadow vnmi flexpriority ept vpid
configuration: cores=6 enabledcores=6 threads=12
*-cache:0
description: L1 cache
physical id: 703
size: 192KiB
capacity: 192KiB
capabilities: internal write-back data
*-cache:1
description: L2 cache
physical id: 704
size: 1536KiB
capacity: 2MiB
capabilities: internal write-back unified
*-cache:2
description: L3 cache
physical id: 705
size: 12MiB
capacity: 12MiB
capabilities: internal write-back unified
*-memory
description: System Memory
physical id: 1000
slot: System board or motherboard
size: 48GiB
*-bank:0
description: DIMM DDR3 Synchronous 1333 MHz (0.8 ns)
product: M393B5273CH0-CH9
vendor: 00CE00B380CE
physical id: 0
serial: 87307157
slot: DIMM_A1
size: 4GiB
width: 64 bits
clock: 1333MHz (0.8ns)
*-bank:1
description: DIMM DDR3 Synchronous 1333 MHz (0.8 ns)
product: M393B5273CH0-CH9
vendor: 00CE00B380CE
physical id: 1
serial: 86ED9AD3
slot: DIMM_A2
size: 4GiB
width: 64 bits
clock: 1333MHz (0.8ns)
*-bank:2
description: DIMM DDR3 Synchronous 1333 MHz (0.8 ns)
product: M393B5273CH0-CH9
vendor: 00CE00B380CE
physical id: 2
serial: 86ED9ABF
slot: DIMM_A3
size: 4GiB
width: 64 bits
clock: 1333MHz (0.8ns)
*-bank:3
description: DIMM DDR3 Synchronous 1333 MHz (0.8 ns)
product: M393B5273CH0-CH9
vendor: 00CE00B380CE
physical id: 3
serial: 87307132
slot: DIMM_A4
size: 4GiB
width: 64 bits
clock: 1333MHz (0.8ns)
*-bank:4
description: DIMM DDR3 Synchronous 1333 MHz (0.8 ns)
product: M393B5273CH0-CH9
vendor: 00CE00B380CE
physical id: 4
serial: 87307154
slot: DIMM_A5
size: 4GiB
width: 64 bits
clock: 1333MHz (0.8ns)
*-bank:5
description: DIMM DDR3 Synchronous 1333 MHz (0.8 ns)
product: M393B5273CH0-CH9
vendor: 00CE00B380CE
physical id: 5
serial: 86ED9AC6
slot: DIMM_A6
size: 4GiB
width: 64 bits
clock: 1333MHz (0.8ns)
*-bank:6
description: DIMM DDR3 Synchronous 1333 MHz (0.8 ns)
product: M393B5273CH0-CH9
vendor: 00CE00B380CE
physical id: 6
serial: 86ED99A2
slot: DIMM_B1
size: 4GiB
width: 64 bits
clock: 1333MHz (0.8ns)
*-bank:7
description: DIMM DDR3 Synchronous 1333 MHz (0.8 ns)
product: M393B5273CH0-CH9
vendor: 00CE00B380CE
physical id: 7
serial: 873070DF
slot: DIMM_B2
size: 4GiB
width: 64 bits
clock: 1333MHz (0.8ns)
*-bank:8
description: DIMM DDR3 Synchronous 1333 MHz (0.8 ns)
product: M393B5273CH0-CH9
vendor: 00CE00B380CE
physical id: 8
serial: 873070F8
slot: DIMM_B3
size: 4GiB
width: 64 bits
clock: 1333MHz (0.8ns)
*-bank:9
description: DIMM DDR3 Synchronous 1333 MHz (0.8 ns)
product: M393B5273CH0-CH9
vendor: 00CE00B380CE
physical id: 9
serial: 87307153
slot: DIMM_B4
size: 4GiB
width: 64 bits
clock: 1333MHz (0.8ns)
*-bank:10
description: DIMM DDR3 Synchronous 1333 MHz (0.8 ns)
product: M393B5273CH0-CH9
vendor: 00CE00B380CE
physical id: a
serial: 873070F0
slot: DIMM_B5
size: 4GiB
width: 64 bits
clock: 1333MHz (0.8ns)
*-bank:11
description: DIMM DDR3 Synchronous 1333 MHz (0.8 ns)
product: M393B5273CH0-CH9
vendor: 00CE00B380CE
physical id: b
serial: 86ED9ACA
slot: DIMM_B6
size: 4GiB
width: 64 bits
clock: 1333MHz (0.8ns)
*-pci
description: Host bridge
product: 5500 I/O Hub to ESI Port
vendor: Intel Corporation
physical id: 100
bus info: pci@0000:00:00.0
version: 13
width: 32 bits
clock: 33MHz
*-pci:0
description: PCI bridge
product: 5520/5500/X58 I/O Hub PCI Express Root Port 1
vendor: Intel Corporation
physical id: 1
bus info: pci@0000:00:01.0
version: 13
width: 32 bits
clock: 33MHz
capabilities: pci msi pciexpress pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:53 memory:da000000-ddffffff
*-network:0
description: Ethernet interface
product: NetXtreme II BCM5709S Gigabit Ethernet
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:01:00.0
logical name: eth0
version: 20
serial: 5c:26:0a:fc:f1:14
size: 1Gbit/s
capacity: 1Gbit/s
width: 64 bits
clock: 33MHz
capabilities: pm vpd msi msix pciexpress bus_master cap_list ethernet physical tp fibre 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=bnx2 driverversion=2.0.21 duplex=full firmware=6.0.1 bc 5.2.3 NCSI 2.0.10 latency=0 link=yes multicast=yes port=fibre slave=yes speed=1Gbit/s
resources: irq:36 memory:da000000-dbffffff
*-network:1
description: Ethernet interface
product: NetXtreme II BCM5709S Gigabit Ethernet
vendor: Broadcom Corporation
physical id: 0.1
bus info: pci@0000:01:00.1
logical name: eth1
version: 20
serial: 5c:26:0a:fc:f1:14
size: 1Gbit/s
capacity: 1Gbit/s
width: 64 bits
clock: 33MHz
capabilities: pm vpd msi msix pciexpress bus_master cap_list ethernet physical tp fibre 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=bnx2 driverversion=2.0.21 duplex=full firmware=6.0.1 bc 5.2.3 NCSI 2.0.10 latency=0 link=yes multicast=yes port=fibre slave=yes speed=1Gbit/s
resources: irq:48 memory:dc000000-ddffffff
*-pci:1
description: PCI bridge
product: 5520/5500/X58 I/O Hub PCI Express Root Port 7
vendor: Intel Corporation
physical id: 7
bus info: pci@0000:00:07.0
version: 13
width: 32 bits
clock: 33MHz
capabilities: pci msi pciexpress pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:53 ioport:e000(size=4096) memory:df000000-df3fffff ioport:d9000000(size=12582912)
*-network:0 DISABLED
description: Ethernet interface
product: 82599EB 10 Gigabit Dual Port Backplane Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:03:00.0
logical name: eth2
version: 01
serial: 00:1b:21:87:7e:9c
size: 1Gbit/s
capacity: 1Gbit/s
width: 64 bits
clock: 33MHz
capabilities: pm msi msix pciexpress bus_master cap_list rom ethernet physical fibre 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=ixgbe driverversion=3.2.9-k2 duplex=full firmware=1.0-3 latency=0 link=no multicast=yes speed=1Gbit/s
resources: irq:45 memory:d9000000-d93fffff ioport:ecc0(size=32) memory:d9bf8000-d9bfbfff memory:df000000-df3fffff
*-network:1 DISABLED
description: Ethernet interface
product: 82599EB 10 Gigabit Dual Port Backplane Connection
vendor: Intel Corporation
physical id: 0.1
bus info: pci@0000:03:00.1
logical name: eth3
version: 01
serial: 00:1b:21:87:7e:9e
capacity: 1Gbit/s
width: 64 bits
clock: 33MHz
capabilities: pm msi msix pciexpress bus_master cap_list ethernet physical fibre 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=ixgbe driverversion=3.2.9-k2 firmware=1.0-3 latency=0 link=no multicast=yes
resources: irq:38 memory:d9400000-d97fffff ioport:ece0(size=32) memory:d9bfc000-d9bfffff
*-pci:2
description: PCI bridge
product: 5520/5500/X58 I/O Hub PCI Express Root Port 9
vendor: Intel Corporation
physical id: 9
bus info: pci@0000:00:09.0
version: 13
width: 32 bits
clock: 33MHz
capabilities: pci msi pciexpress pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:53
*-generic:0
description: PIC
product: 5520/5500/X58 I/O Hub System Management Registers
vendor: Intel Corporation
physical id: 14
bus info: pci@0000:00:14.0
version: 13
width: 32 bits
clock: 33MHz
capabilities: pciexpress 8259 cap_list
configuration: driver=i7core_edac latency=0
resources: irq:0
*-generic:1 UNCLAIMED
description: PIC
product: 5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers
vendor: Intel Corporation
physical id: 14.1
bus info: pci@0000:00:14.1
version: 13
width: 32 bits
clock: 33MHz
capabilities: pciexpress 8259 cap_list
configuration: latency=0
*-generic:2 UNCLAIMED
description: PIC
product: 5520/5500/X58 I/O Hub Control Status and RAS Registers
vendor: Intel Corporation
physical id: 14.2
bus info: pci@0000:00:14.2
version: 13
width: 32 bits
clock: 33MHz
capabilities: pciexpress 8259 cap_list
configuration: latency=0
*-usb:0
description: USB Controller
product: 82801I (ICH9 Family) USB UHCI Controller #4
vendor: Intel Corporation
physical id: 1a
bus info: pci@0000:00:1a.0
version: 02
width: 32 bits
clock: 33MHz
capabilities: uhci bus_master cap_list
configuration: driver=uhci_hcd latency=0
resources: irq:17 ioport:dc00(size=32)
*-usb:1
description: USB Controller
product: 82801I (ICH9 Family) USB UHCI Controller #5
vendor: Intel Corporation
physical id: 1a.1
bus info: pci@0000:00:1a.1
version: 02
width: 32 bits
clock: 33MHz
capabilities: uhci bus_master cap_list
configuration: driver=uhci_hcd latency=0
resources: irq:18 ioport:dc20(size=32)
*-usb:2
description: USB Controller
product: 82801I (ICH9 Family) USB2 EHCI Controller #2
vendor: Intel Corporation
physical id: 1a.7
bus info: pci@0000:00:1a.7
version: 02
width: 32 bits
clock: 33MHz
capabilities: pm debug ehci bus_master cap_list
configuration: driver=ehci_hcd latency=0
resources: irq:19 memory:df6ff800-df6ffbff
*-pci:3
description: PCI bridge
product: 82801I (ICH9 Family) PCI Express Port 1
vendor: Intel Corporation
physical id: 1c
bus info: pci@0000:00:1c.0
version: 02
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:73 ioport:f000(size=4096) memory:df400000-df5fffff
*-scsi
description: SCSI storage controller
product: SAS1068E PCI-Express Fusion-MPT SAS
vendor: LSI Logic / Symbios Logic
physical id: 0
bus info: pci@0000:02:00.0
logical name: scsi0
version: 08
width: 64 bits
clock: 33MHz
capabilities: scsi pm pciexpress msi msix bus_master cap_list rom
configuration: driver=mptsas latency=0
resources: irq:16 ioport:fc00(size=256) memory:df5fc000-df5fffff memory:df5e0000-df5effff memory:df400000-df4fffff
*-disk:0
description: SCSI Disk
physical id: 0.0.0
bus info: scsi@0:0.0.0
logical name: /dev/sda
size: 465GiB (500GB)
capabilities: gpt-1.00 partitioned partitioned:gpt
configuration: guid=32374a01-13c8-45bc-b08d-9fa7280c6bb2
*-volume:0
description: EFI partition
physical id: 1
bus info: scsi@0:0.0.0,1
logical name: /dev/sda1
serial: 5bd9901a-13e8-4a52-aeae-66256feb9e85
capacity: 3071KiB
configuration: name=primary
*-volume:1
description: EXT3 volume
vendor: Linux
physical id: 2
bus info: scsi@0:0.0.0,2
logical name: /dev/sda2
version: 1.0
serial: 8c0415d6-d0c4-4faa-b3be-aff277f0581f
size: 10239MiB
capacity: 10239MiB
capabilities: multi journaled extended_attributes large_files recover ext3 ext2 initialized
configuration: created=2011-03-16 12:22:58 filesystem=ext3 label=slash modified=2011-03-16 12:34:49 mounted=2011-03-17 13:34:24 name=primary state=clean
*-volume:2
description: Linux RAID partition
physical id: 3
bus info: scsi@0:0.0.0,3
logical name: /dev/sda3
serial: cHcSsT-kPAR-PjLu-ormw-6mhO-Rr4N-d2Loaf
size: 455GiB
capacity: 455GiB
capabilities: multi lvm2
configuration: name=primary
*-disk:1
description: SCSI Disk
physical id: 0.1.0
bus info: scsi@0:0.1.0
logical name: /dev/sdb
size: 465GiB (500GB)
capabilities: gpt-1.00 partitioned partitioned:gpt
configuration: guid=c527a7cd-0440-4734-9294-cbe631b6dd45
*-volume:0
description: EFI partition
physical id: 1
bus info: scsi@0:0.1.0,1
logical name: /dev/sdb1
serial: 92e39259-fbe5-4025-ac58-e0275a4b4f4b
capacity: 3071KiB
configuration: name=primary
*-volume:1
description: EXT3 volume
vendor: Linux
physical id: 2
bus info: scsi@0:0.1.0,2
logical name: /dev/sdb2
version: 1.0
serial: 8c0415d6-d0c4-4faa-b3be-aff277f0581f
size: 10239MiB
capacity: 10239MiB
capabilities: multi journaled extended_attributes large_files recover ext3 ext2 initialized
configuration: created=2011-03-16 12:22:58 filesystem=ext3 label=slash modified=2011-03-16 12:34:49 mounted=2011-03-17 13:34:24 name=primary state=clean
*-volume:2
description: Linux RAID partition
physical id: 3
bus info: scsi@0:0.1.0,3
logical name: /dev/sdb3
serial: cHcSsT-kPAR-PjLu-ormw-6mhO-Rr4N-d2Loaf
size: 455GiB
capacity: 455GiB
capabilities: multi lvm2
configuration: name=primary
*-usb:3
description: USB Controller
product: 82801I (ICH9 Family) USB UHCI Controller #1
vendor: Intel Corporation
physical id: 1d
bus info: pci@0000:00:1d.0
version: 02
width: 32 bits
clock: 33MHz
capabilities: uhci bus_master cap_list
configuration: driver=uhci_hcd latency=0
resources: irq:21 ioport:dc40(size=32)
*-usb:4
description: USB Controller
product: 82801I (ICH9 Family) USB UHCI Controller #2
vendor: Intel Corporation
physical id: 1d.1
bus info: pci@0000:00:1d.1
version: 02
width: 32 bits
clock: 33MHz
capabilities: uhci bus_master cap_list
configuration: driver=uhci_hcd latency=0
resources: irq:20 ioport:dc60(size=32)
*-usb:5
description: USB Controller
product: 82801I (ICH9 Family) USB UHCI Controller #3
vendor: Intel Corporation
physical id: 1d.2
bus info: pci@0000:00:1d.2
version: 02
width: 32 bits
clock: 33MHz
capabilities: uhci bus_master cap_list
configuration: driver=uhci_hcd latency=0
resources: irq:21 ioport:dc80(size=32)
*-usb:6
description: USB Controller
product: 82801I (ICH9 Family) USB2 EHCI Controller #1
vendor: Intel Corporation
physical id: 1d.7
bus info: pci@0000:00:1d.7
version: 02
width: 32 bits
clock: 33MHz
capabilities: pm debug ehci bus_master cap_list
configuration: driver=ehci_hcd latency=0
resources: irq:21 memory:df6ffc00-df6fffff
*-pci:4
description: PCI bridge
product: 82801 PCI Bridge
vendor: Intel Corporation
physical id: 1e
bus info: pci@0000:00:1e.0
version: 92
width: 32 bits
clock: 33MHz
capabilities: pci subtractive_decode bus_master cap_list
resources: memory:de000000-deffffff ioport:d8800000(size=8388608)
*-display UNCLAIMED
description: VGA compatible controller
product: MGA G200eW WPCM450
vendor: Matrox Graphics, Inc.
physical id: 3
bus info: pci@0000:05:03.0
version: 0a
width: 32 bits
clock: 33MHz
capabilities: pm vga_controller bus_master cap_list
configuration: latency=32 maxlatency=32 mingnt=16
resources: memory:d8800000-d8ffffff memory:deffc000-deffffff memory:de000000-de7fffff memory:de800000-de80ffff
*-isa
description: ISA bridge
product: 82801IB (ICH9) LPC Interface Controller
vendor: Intel Corporation
physical id: 1f
bus info: pci@0000:00:1f.0
version: 02
width: 32 bits
clock: 33MHz
capabilities: isa bus_master cap_list
configuration: latency=0
*-network:0
description: Ethernet interface
physical id: 1
logical name: bond0
serial: 5c:26:0a:fc:f1:14
capabilities: ethernet physical
configuration: broadcast=yes driver=bonding driverversion=3.7.0 firmware=2 link=yes master=yes multicast=yes promiscuous=yes
*-network:1
description: Ethernet interface
physical id: 2
logical name: bond0.15
serial: 5c:26:0a:fc:f1:14
capabilities: ethernet physical
configuration: broadcast=yes driver=802.1Q VLAN Support driverversion=1.8 firmware=N/A link=yes multicast=yes
*-network:2
description: Ethernet interface
physical id: 3
logical name: vnet0
serial: fe:54:00:b1:38:ef
size: 10Mbit/s
capabilities: ethernet physical
configuration: autonegotiation=off broadcast=yes driver=tun driverversion=1.6 duplex=full firmware=N/A link=yes multicast=yes port=twisted pair speed=10Mbit/s
*-network:3
description: Ethernet interface
physical id: 4
logical name: vnet1
serial: fe:54:00:21:25:28
size: 10Mbit/s
capabilities: ethernet physical
configuration: autonegotiation=off broadcast=yes driver=tun driverversion=1.6 duplex=full firmware=N/A link=yes multicast=yes port=twisted pair speed=10Mbit/s
*-network:4
description: Ethernet interface
physical id: 5
logical name: vnet2
serial: fe:54:00:b9:70:1a
size: 10Mbit/s
capabilities: ethernet physical
configuration: autonegotiation=off broadcast=yes driver=tun driverversion=1.6 duplex=full firmware=N/A link=yes multicast=yes port=twisted pair speed=10Mbit/s
*-network:5
description: Ethernet interface
physical id: 6
logical name: vnet3
serial: fe:54:00:96:65:09
size: 10Mbit/s
capabilities: ethernet physical
configuration: autonegotiation=off broadcast=yes driver=tun driverversion=1.6 duplex=full firmware=N/A link=yes multicast=yes port=twisted pair speed=10Mbit/s
*-network:6
description: Ethernet interface
physical id: 7
logical name: vnet4
serial: fe:54:00:61:20:db
size: 10Mbit/s
capabilities: ethernet physical
configuration: autonegotiation=off broadcast=yes driver=tun driverversion=1.6 duplex=full firmware=N/A link=yes multicast=yes port=twisted pair speed=10Mbit/s
*-network:7
description: Ethernet interface
physical id: 8
logical name: vnet5
serial: fe:54:00:c5:a4:fd
size: 10Mbit/s
capabilities: ethernet physical
configuration: autonegotiation=off broadcast=yes driver=tun driverversion=1.6 duplex=full firmware=N/A link=yes multicast=yes port=twisted pair speed=10Mbit/s
*-network:8
description: Ethernet interface
physical id: 9
logical name: vnet6
serial: fe:54:00:d5:49:27
size: 10Mbit/s
capabilities: ethernet physical
configuration: autonegotiation=off broadcast=yes driver=tun driverversion=1.6 duplex=full firmware=N/A link=yes multicast=yes port=twisted pair speed=10Mbit/s
*-network:9
description: Ethernet interface
physical id: a
logical name: vnet7
serial: fe:54:00:7a:ce:76
size: 10Mbit/s
capabilities: ethernet physical
configuration: autonegotiation=off broadcast=yes driver=tun driverversion=1.6 duplex=full firmware=N/A link=yes multicast=yes port=twisted pair speed=10Mbit/s
*-network:10
description: Ethernet interface
physical id: b
logical name: vnet8
serial: fe:54:00:df:51:95
size: 10Mbit/s
capabilities: ethernet physical
configuration: autonegotiation=off broadcast=yes driver=tun driverversion=1.6 duplex=full firmware=N/A link=yes multicast=yes port=twisted pair speed=10Mbit/s
[-- Attachment #3: lspci --]
[-- Type: application/octet-stream, Size: 1553 bytes --]
-[0000:00]-+-00.0 Intel Corporation 5500 I/O Hub to ESI Port
+-01.0-[01]--+-00.0 Broadcom Corporation NetXtreme II BCM5709S Gigabit Ethernet
| \-00.1 Broadcom Corporation NetXtreme II BCM5709S Gigabit Ethernet
+-07.0-[03]--+-00.0 Intel Corporation 82599EB 10 Gigabit Dual Port Backplane Connection
| \-00.1 Intel Corporation 82599EB 10 Gigabit Dual Port Backplane Connection
+-09.0-[04]--
+-14.0 Intel Corporation 5520/5500/X58 I/O Hub System Management Registers
+-14.1 Intel Corporation 5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers
+-14.2 Intel Corporation 5520/5500/X58 I/O Hub Control Status and RAS Registers
+-1a.0 Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4
+-1a.1 Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5
+-1a.7 Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2
+-1c.0-[02]----00.0 LSI Logic / Symbios Logic SAS1068E PCI-Express Fusion-MPT SAS
+-1d.0 Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1
+-1d.1 Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2
+-1d.2 Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3
+-1d.7 Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1
+-1e.0-[05]----03.0 Matrox Graphics, Inc. MGA G200eW WPCM450
\-1f.0 Intel Corporation 82801IB (ICH9) LPC Interface Controller
[-- Attachment #4: dmesg.out --]
[-- Type: application/octet-stream, Size: 66114 bytes --]
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.38-sj+1 (root@sluttrin) (gcc version 4.5.2 (Debian 4.5.2-6) ) #2 SMP Wed Mar 16 11:36:51 CET 2011
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.38-sj+1 root=UUID=8c0415d6-d0c4-4faa-b3be-aff277f0581f ro quiet
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
[ 0.000000] BIOS-e820: 0000000000100000 - 00000000cf379000 (usable)
[ 0.000000] BIOS-e820: 00000000cf379000 - 00000000cf38f000 (reserved)
[ 0.000000] BIOS-e820: 00000000cf38f000 - 00000000cf3ce000 (ACPI data)
[ 0.000000] BIOS-e820: 00000000cf3ce000 - 00000000d0000000 (reserved)
[ 0.000000] BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
[ 0.000000] BIOS-e820: 00000000fe000000 - 0000000100000000 (reserved)
[ 0.000000] BIOS-e820: 0000000100000000 - 0000000c30000000 (usable)
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] DMI 2.6 present.
[ 0.000000] DMI: Dell Inc. PowerEdge M610/0V56FN, BIOS 2.2.9 10/25/2010
[ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
[ 0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
[ 0.000000] No AGP bridge found
[ 0.000000] last_pfn = 0xc30000 max_arch_pfn = 0x400000000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-D3FFF write-protect
[ 0.000000] D4000-EBFFF uncachable
[ 0.000000] EC000-FFFFF write-protect
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 0000000000 mask FF80000000 write-back
[ 0.000000] 1 base 0080000000 mask FFC0000000 write-back
[ 0.000000] 2 base 00C0000000 mask FFF0000000 write-back
[ 0.000000] 3 base 0100000000 mask FF00000000 write-back
[ 0.000000] 4 base 0200000000 mask FE00000000 write-back
[ 0.000000] 5 base 0400000000 mask FC00000000 write-back
[ 0.000000] 6 base 0800000000 mask FC00000000 write-back
[ 0.000000] 7 base 0C00000000 mask FFC0000000 write-back
[ 0.000000] 8 disabled
[ 0.000000] 9 disabled
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[ 0.000000] e820 update range: 00000000d0000000 - 0000000100000000 (usable) ==> (reserved)
[ 0.000000] last_pfn = 0xcf379 max_arch_pfn = 0x400000000
[ 0.000000] found SMP MP-table at [ffff8800000fe710] fe710
[ 0.000000] initial memory mapped : 0 - 20000000
[ 0.000000] Using GB pages for direct mapping
[ 0.000000] init_memory_mapping: 0000000000000000-00000000cf379000
[ 0.000000] 0000000000 - 00c0000000 page 1G
[ 0.000000] 00c0000000 - 00cf200000 page 2M
[ 0.000000] 00cf200000 - 00cf379000 page 4k
[ 0.000000] kernel direct mapping tables up to cf379000 @ 1fffd000-20000000
[ 0.000000] init_memory_mapping: 0000000100000000-0000000c30000000
[ 0.000000] 0100000000 - 0c00000000 page 1G
[ 0.000000] 0c00000000 - 0c30000000 page 2M
[ 0.000000] kernel direct mapping tables up to c30000000 @ cf377000-cf379000
[ 0.000000] RAMDISK: 36ab4000 - 37552000
[ 0.000000] ACPI: RSDP 00000000000f1950 00024 (v02 DELL )
[ 0.000000] ACPI: XSDT 00000000000f1a54 0009C (v01 DELL PE_SC3 00000001 DELL 00000001)
[ 0.000000] ACPI: FACP 00000000cf3b3f9c 000F4 (v03 DELL PE_SC3 00000001 DELL 00000001)
[ 0.000000] ACPI: DSDT 00000000cf38f000 039D9 (v01 DELL PE_SC3 00000001 INTL 20050624)
[ 0.000000] ACPI: FACS 00000000cf3b6000 00040
[ 0.000000] ACPI: APIC 00000000cf3b3478 0015E (v01 DELL PE_SC3 00000001 DELL 00000001)
[ 0.000000] ACPI: SPCR 00000000cf3b35d8 00050 (v01 DELL PE_SC3 00000001 DELL 00000001)
[ 0.000000] ACPI: HPET 00000000cf3b362c 00038 (v01 DELL PE_SC3 00000001 DELL 00000001)
[ 0.000000] ACPI: DMAR 00000000cf3b3668 001C0 (v01 DELL PE_SC3 00000001 DELL 00000001)
[ 0.000000] ACPI: MCFG 00000000cf3b38c4 0003C (v01 DELL PE_SC3 00000001 DELL 00000001)
[ 0.000000] ACPI: WD__ 00000000cf3b3904 00134 (v01 DELL PE_SC3 00000001 DELL 00000001)
[ 0.000000] ACPI: SLIC 00000000cf3b3a3c 00024 (v01 DELL PE_SC3 00000001 DELL 00000001)
[ 0.000000] ACPI: ERST 00000000cf392b5c 00270 (v01 DELL PE_SC3 00000001 DELL 00000001)
[ 0.000000] ACPI: HEST 00000000cf392dcc 003A8 (v01 DELL PE_SC3 00000001 DELL 00000001)
[ 0.000000] ACPI: BERT 00000000cf3929dc 00030 (v01 DELL PE_SC3 00000001 DELL 00000001)
[ 0.000000] ACPI: EINJ 00000000cf392a0c 00150 (v01 DELL PE_SC3 00000001 DELL 00000001)
[ 0.000000] ACPI: SRAT 00000000cf3b3bc0 00370 (v01 DELL PE_SC3 00000001 DELL 00000001)
[ 0.000000] ACPI: TCPA 00000000cf3b3f34 00064 (v02 DELL PE_SC3 00000001 DELL 00000001)
[ 0.000000] ACPI: SSDT 00000000cf3b7000 062C4 (v01 INTEL PPM RCM 80000001 INTL 20061109)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] SRAT: PXM 1 -> APIC 0x20 -> Node 0
[ 0.000000] SRAT: PXM 2 -> APIC 0x00 -> Node 1
[ 0.000000] SRAT: PXM 1 -> APIC 0x22 -> Node 0
[ 0.000000] SRAT: PXM 2 -> APIC 0x02 -> Node 1
[ 0.000000] SRAT: PXM 1 -> APIC 0x24 -> Node 0
[ 0.000000] SRAT: PXM 2 -> APIC 0x04 -> Node 1
[ 0.000000] SRAT: PXM 1 -> APIC 0x30 -> Node 0
[ 0.000000] SRAT: PXM 2 -> APIC 0x10 -> Node 1
[ 0.000000] SRAT: PXM 1 -> APIC 0x32 -> Node 0
[ 0.000000] SRAT: PXM 2 -> APIC 0x12 -> Node 1
[ 0.000000] SRAT: PXM 1 -> APIC 0x34 -> Node 0
[ 0.000000] SRAT: PXM 2 -> APIC 0x14 -> Node 1
[ 0.000000] SRAT: PXM 1 -> APIC 0x21 -> Node 0
[ 0.000000] SRAT: PXM 2 -> APIC 0x01 -> Node 1
[ 0.000000] SRAT: PXM 1 -> APIC 0x23 -> Node 0
[ 0.000000] SRAT: PXM 2 -> APIC 0x03 -> Node 1
[ 0.000000] SRAT: PXM 1 -> APIC 0x25 -> Node 0
[ 0.000000] SRAT: PXM 2 -> APIC 0x05 -> Node 1
[ 0.000000] SRAT: PXM 1 -> APIC 0x31 -> Node 0
[ 0.000000] SRAT: PXM 2 -> APIC 0x11 -> Node 1
[ 0.000000] SRAT: PXM 1 -> APIC 0x33 -> Node 0
[ 0.000000] SRAT: PXM 2 -> APIC 0x13 -> Node 1
[ 0.000000] SRAT: PXM 1 -> APIC 0x35 -> Node 0
[ 0.000000] SRAT: PXM 2 -> APIC 0x15 -> Node 1
[ 0.000000] SRAT: Node 1 PXM 2 0-d0000000
[ 0.000000] SRAT: Node 1 PXM 2 100000000-630000000
[ 0.000000] SRAT: Node 0 PXM 1 630000000-c30000000
[ 0.000000] SRAT: Node 1 [0,d0000000) + [100000000,630000000) -> [0,630000000)
[ 0.000000] NUMA: Allocated memnodemap from c2ffffe40 - c30000000
[ 0.000000] NUMA: Using 28 for the hash shift.
[ 0.000000] Initmem setup node 0 0000000630000000-0000000c30000000
[ 0.000000] NODE_DATA [0000000c2fffae40 - 0000000c2ffffe3f]
[ 0.000000] Initmem setup node 1 0000000000000000-0000000630000000
[ 0.000000] NODE_DATA [000000062fffb000 - 000000062fffffff]
[ 0.000000] [ffffea0015a80000-ffffea0015bfffff] potential offnode page_structs
[ 0.000000] [ffffea0000000000-ffffea0015bfffff] PMD -> [ffff880617e00000-ffff88062cffffff] on node 1
[ 0.000000] [ffffea0015c00000-ffffea002abfffff] PMD -> [ffff880c17e00000-ffff880c2cdfffff] on node 0
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0x00000010 -> 0x00001000
[ 0.000000] DMA32 0x00001000 -> 0x00100000
[ 0.000000] Normal 0x00100000 -> 0x00c30000
[ 0.000000] Movable zone start PFN for each node
[ 0.000000] early_node_map[4] active PFN ranges
[ 0.000000] 1: 0x00000010 -> 0x000000a0
[ 0.000000] 1: 0x00000100 -> 0x000cf379
[ 0.000000] 1: 0x00100000 -> 0x00630000
[ 0.000000] 0: 0x00630000 -> 0x00c30000
[ 0.000000] On node 0 totalpages: 6291456
[ 0.000000] Normal zone: 86016 pages used for memmap
[ 0.000000] Normal zone: 6205440 pages, LIFO batch:31
[ 0.000000] On node 1 totalpages: 6288137
[ 0.000000] DMA zone: 56 pages used for memmap
[ 0.000000] DMA zone: 8 pages reserved
[ 0.000000] DMA zone: 3920 pages, LIFO batch:0
[ 0.000000] DMA32 zone: 14280 pages used for memmap
[ 0.000000] DMA32 zone: 830385 pages, LIFO batch:31
[ 0.000000] Normal zone: 74368 pages used for memmap
[ 0.000000] Normal zone: 5365120 pages, LIFO batch:31
[ 0.000000] ACPI: PM-Timer IO Port: 0x808
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x20] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x00] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x22] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x02] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x24] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x04] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x30] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x10] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x32] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x12] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x34] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x14] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x21] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x01] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x23] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x03] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x25] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x05] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x31] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x14] lapic_id[0x11] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x15] lapic_id[0x33] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x16] lapic_id[0x13] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x17] lapic_id[0x35] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x15] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x38] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x39] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x3a] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x1c] lapic_id[0x3b] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x1d] lapic_id[0x3c] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x1e] lapic_id[0x3d] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x1f] lapic_id[0x3e] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x20] lapic_id[0x3f] disabled)
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
[ 0.000000] ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
[ 0.000000] ACPI: IOAPIC (id[0x01] address[0xfec80000] gsi_base[32])
[ 0.000000] IOAPIC[1]: apic_id 1, version 32, address 0xfec80000, GSI 32-55
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 0.000000] ACPI: IRQ0 used by override.
[ 0.000000] ACPI: IRQ2 used by override.
[ 0.000000] ACPI: IRQ9 used by override.
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] ACPI: HPET id: 0x8086a301 base: 0xfed00000
[ 0.000000] SMP: Allowing 32 CPUs, 8 hotplug CPUs
[ 0.000000] nr_irqs_gsi: 72
[ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 0000000000100000
[ 0.000000] PM: Registered nosave memory: 00000000cf379000 - 00000000cf38f000
[ 0.000000] PM: Registered nosave memory: 00000000cf38f000 - 00000000cf3ce000
[ 0.000000] PM: Registered nosave memory: 00000000cf3ce000 - 00000000d0000000
[ 0.000000] PM: Registered nosave memory: 00000000d0000000 - 00000000e0000000
[ 0.000000] PM: Registered nosave memory: 00000000e0000000 - 00000000f0000000
[ 0.000000] PM: Registered nosave memory: 00000000f0000000 - 00000000fe000000
[ 0.000000] PM: Registered nosave memory: 00000000fe000000 - 0000000100000000
[ 0.000000] Allocating PCI resources starting at d0000000 (gap: d0000000:10000000)
[ 0.000000] setup_percpu: NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:32 nr_node_ids:2
[ 0.000000] PERCPU: Embedded 26 pages/cpu @ffff8800cf000000 s75584 r8192 d22720 u131072
[ 0.000000] pcpu-alloc: s75584 r8192 d22720 u131072 alloc=1*2097152
[ 0.000000] pcpu-alloc: [0] 00 02 04 06 08 10 12 14 16 18 20 22 24 26 28 30
[ 0.000000] pcpu-alloc: [1] 01 03 05 07 09 11 13 15 17 19 21 23 25 27 29 31
[ 0.000000] Built 2 zonelists in Zone order, mobility grouping on. Total pages: 12404865
[ 0.000000] Policy zone: Normal
[ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.38-sj+1 root=UUID=8c0415d6-d0c4-4faa-b3be-aff277f0581f ro quiet
[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.000000] Checking aperture...
[ 0.000000] No AGP bridge found
[ 0.000000] Calgary: detecting Calgary via BIOS EBDA area
[ 0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
[ 0.000000] Memory: 49539360k/51118080k available (3121k kernel code, 799708k absent, 779012k reserved, 3555k data, 600k init)
[ 0.000000] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=32, Nodes=2
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] RCU dyntick-idle grace-period acceleration is enabled.
[ 0.000000] RCU-based detection of stalled CPUs is disabled.
[ 0.000000] NR_IRQS:33024 nr_irqs:1480 16
[ 0.000000] Extended CMOS year: 2000
[ 0.000000] Console: colour VGA+ 80x25
[ 0.000000] console [tty0] enabled
[ 0.000000] hpet clockevent registered
[ 0.000000] Fast TSC calibration using PIT
[ 0.004000] Detected 2260.852 MHz processor.
[ 0.000010] Calibrating delay loop (skipped), value calculated using timer frequency.. 4521.70 BogoMIPS (lpj=9043408)
[ 0.000014] pid_max: default: 32768 minimum: 301
[ 0.000054] Security Framework initialized
[ 0.000058] SELinux: Disabled at boot.
[ 0.004692] Dentry cache hash table entries: 8388608 (order: 14, 67108864 bytes)
[ 0.019000] Inode-cache hash table entries: 4194304 (order: 13, 33554432 bytes)
[ 0.025029] Mount-cache hash table entries: 256
[ 0.025251] Initializing cgroup subsys ns
[ 0.025254] ns_cgroup deprecated: consider using the 'clone_children' flag without the ns_cgroup.
[ 0.025256] Initializing cgroup subsys cpuacct
[ 0.025263] Initializing cgroup subsys devices
[ 0.025265] Initializing cgroup subsys freezer
[ 0.025267] Initializing cgroup subsys net_cls
[ 0.025269] Initializing cgroup subsys blkio
[ 0.025307] CPU: Physical Processor ID: 1
[ 0.025308] CPU: Processor Core ID: 0
[ 0.025313] mce: CPU supports 9 MCE banks
[ 0.025323] CPU0: Thermal monitoring enabled (TM1)
[ 0.025331] using mwait in idle threads.
[ 0.025359] ACPI: Core revision 20110112
[ 0.027311] DMAR: Host address width 40
[ 0.027314] DMAR: DRHD base: 0x000000fed90000 flags: 0x1
[ 0.027322] IOMMU 0: reg_base_addr fed90000 ver 1:0 cap c90780106f0462 ecap f020fe
[ 0.027324] DMAR: RMRR base: 0x000000cf4c8000 end: 0x000000cf4dffff
[ 0.027326] DMAR: RMRR base: 0x000000cf4b1000 end: 0x000000cf4bffff
[ 0.027327] DMAR: RMRR base: 0x000000cf4a1000 end: 0x000000cf4a1fff
[ 0.027329] DMAR: RMRR base: 0x000000cf4a3000 end: 0x000000cf4a3fff
[ 0.027330] DMAR: RMRR base: 0x000000cf4a5000 end: 0x000000cf4a5fff
[ 0.027332] DMAR: RMRR base: 0x000000cf4a7000 end: 0x000000cf4a7fff
[ 0.027334] DMAR: RMRR base: 0x000000cf4a9000 end: 0x000000cf4a9fff
[ 0.027335] DMAR: RMRR base: 0x000000cf4c0000 end: 0x000000cf4c0fff
[ 0.027337] DMAR: RMRR base: 0x000000cf4c2000 end: 0x000000cf4c2fff
[ 0.027338] DMAR: ATSR flags: 0x0
[ 0.027444] IOAPIC id 0 under DRHD base 0xfed90000 IOMMU 0
[ 0.027446] IOAPIC id 1 under DRHD base 0xfed90000 IOMMU 0
[ 0.027645] Enabled Interrupt-remapping
[ 0.027649] Setting APIC routing to physical flat
[ 0.028132] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.067734] CPU0: Intel(R) Xeon(R) CPU L5640 @ 2.27GHz stepping 02
[ 0.172470] Performance Events: PEBS fmt1+, Westmere events, Intel PMU driver.
[ 0.172477] ... version: 3
[ 0.172478] ... bit width: 48
[ 0.172480] ... generic registers: 4
[ 0.172481] ... value mask: 0000ffffffffffff
[ 0.172482] ... max period: 000000007fffffff
[ 0.172483] ... fixed-purpose events: 3
[ 0.172484] ... event mask: 000000070000000f
[ 0.173130] NMI watchdog enabled, takes one hw-pmu counter.
[ 0.173222] Booting Node 1, Processors #1
[ 0.280352] NMI watchdog enabled, takes one hw-pmu counter.
[ 0.280417] Ok.
[ 0.280418] Booting Node 0, Processors #2
[ 0.388151] NMI watchdog enabled, takes one hw-pmu counter.
[ 0.388260] Ok.
[ 0.388261] Booting Node 1, Processors #3
[ 0.495921] NMI watchdog enabled, takes one hw-pmu counter.
[ 0.495988] Ok.
[ 0.495989] Booting Node 0, Processors #4
[ 0.603721] NMI watchdog enabled, takes one hw-pmu counter.
[ 0.603823] Ok.
[ 0.603825] Booting Node 1, Processors #5
[ 0.711446] NMI watchdog enabled, takes one hw-pmu counter.
[ 0.711523] Ok.
[ 0.711525] Booting Node 0, Processors #6
[ 0.819257] NMI watchdog enabled, takes one hw-pmu counter.
[ 0.819359] Ok.
[ 0.819361] Booting Node 1, Processors #7
[ 0.927052] NMI watchdog enabled, takes one hw-pmu counter.
[ 0.927122] Ok.
[ 0.927124] Booting Node 0, Processors #8
[ 1.034825] NMI watchdog enabled, takes one hw-pmu counter.
[ 1.034932] Ok.
[ 1.034933] Booting Node 1, Processors #9
[ 1.142652] NMI watchdog enabled, takes one hw-pmu counter.
[ 1.142719] Ok.
[ 1.142721] Booting Node 0, Processors #10
[ 1.250452] NMI watchdog enabled, takes one hw-pmu counter.
[ 1.250559] Ok.
[ 1.250560] Booting Node 1, Processors #11
[ 1.358183] NMI watchdog enabled, takes one hw-pmu counter.
[ 1.358248] Ok.
[ 1.358250] Booting Node 0, Processors #12
[ 1.465945] NMI watchdog enabled, takes one hw-pmu counter.
[ 1.466052] Ok.
[ 1.466054] Booting Node 1, Processors #13
[ 1.573778] NMI watchdog enabled, takes one hw-pmu counter.
[ 1.573857] Ok.
[ 1.573858] Booting Node 0, Processors #14
[ 1.681494] NMI watchdog enabled, takes one hw-pmu counter.
[ 1.681600] Ok.
[ 1.681601] Booting Node 1, Processors #15
[ 1.789327] NMI watchdog enabled, takes one hw-pmu counter.
[ 1.789394] Ok.
[ 1.789395] Booting Node 0, Processors #16
[ 1.897129] NMI watchdog enabled, takes one hw-pmu counter.
[ 1.897239] Ok.
[ 1.897240] Booting Node 1, Processors #17
[ 2.004926] NMI watchdog enabled, takes one hw-pmu counter.
[ 2.004991] Ok.
[ 2.004993] Booting Node 0, Processors #18
[ 2.112628] NMI watchdog enabled, takes one hw-pmu counter.
[ 2.112737] Ok.
[ 2.112738] Booting Node 1, Processors #19
[ 2.220464] NMI watchdog enabled, takes one hw-pmu counter.
[ 2.220534] Ok.
[ 2.220536] Booting Node 0, Processors #20
[ 2.328273] NMI watchdog enabled, takes one hw-pmu counter.
[ 2.328377] Ok.
[ 2.328379] Booting Node 1, Processors #21
[ 2.436002] NMI watchdog enabled, takes one hw-pmu counter.
[ 2.436075] Ok.
[ 2.436076] Booting Node 0, Processors #22
[ 2.543782] NMI watchdog enabled, takes one hw-pmu counter.
[ 2.543885] Ok.
[ 2.543886] Booting Node 1, Processors #23
[ 2.651612] NMI watchdog enabled, takes one hw-pmu counter.
[ 2.651632] Brought up 24 CPUs
[ 2.651636] Total of 24 processors activated (108527.39 BogoMIPS).
[ 2.671123] devtmpfs: initialized
[ 2.678297] print_constraints: dummy:
[ 2.678375] NET: Registered protocol family 16
[ 2.678479] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
[ 2.678482] ACPI: bus type pci registered
[ 2.678566] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
[ 2.678569] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820
[ 2.694503] PCI: Using configuration type 1 for base access
[ 2.696645] bio: create slab <bio-0> at 0
[ 2.697386] ACPI: EC: Look up EC in DSDT
[ 2.698289] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 2.701271] ACPI: Interpreter enabled
[ 2.701274] ACPI: (supports S0 S4 S5)
[ 2.701286] ACPI: Using IOAPIC for interrupt routing
[ 2.704780] ACPI: No dock devices found.
[ 2.704891] HEST: Table parsing has been initialized.
[ 2.704894] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[ 2.705093] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[ 2.705266] pci_root PNP0A08:00: host bridge window [io 0x0000-0x0cf7]
[ 2.705268] pci_root PNP0A08:00: host bridge window [io 0x0d00-0xffff]
[ 2.705270] pci_root PNP0A08:00: host bridge window [mem 0x000a0000-0x000bffff]
[ 2.705272] pci_root PNP0A08:00: host bridge window [mem 0xd0000000-0xfdffffff]
[ 2.705274] pci_root PNP0A08:00: host bridge window [mem 0xfed40000-0xfed44fff]
[ 2.705289] pci 0000:00:00.0: [8086:3403] type 0 class 0x000600
[ 2.705331] pci 0000:00:00.0: PME# supported from D0 D3hot D3cold
[ 2.705334] pci 0000:00:00.0: PME# disabled
[ 2.705356] pci 0000:00:01.0: [8086:3408] type 1 class 0x000604
[ 2.705396] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
[ 2.705399] pci 0000:00:01.0: PME# disabled
[ 2.705420] pci 0000:00:07.0: [8086:340e] type 1 class 0x000604
[ 2.705460] pci 0000:00:07.0: PME# supported from D0 D3hot D3cold
[ 2.705463] pci 0000:00:07.0: PME# disabled
[ 2.705482] pci 0000:00:09.0: [8086:3410] type 1 class 0x000604
[ 2.705522] pci 0000:00:09.0: PME# supported from D0 D3hot D3cold
[ 2.705525] pci 0000:00:09.0: PME# disabled
[ 2.705546] pci 0000:00:14.0: [8086:342e] type 0 class 0x000800
[ 2.705600] pci 0000:00:14.1: [8086:3422] type 0 class 0x000800
[ 2.705653] pci 0000:00:14.2: [8086:3423] type 0 class 0x000800
[ 2.705714] pci 0000:00:1a.0: [8086:2937] type 0 class 0x000c03
[ 2.705754] pci 0000:00:1a.0: reg 20: [io 0xdc00-0xdc1f]
[ 2.705794] pci 0000:00:1a.1: [8086:2938] type 0 class 0x000c03
[ 2.705833] pci 0000:00:1a.1: reg 20: [io 0xdc20-0xdc3f]
[ 2.705884] pci 0000:00:1a.7: [8086:293c] type 0 class 0x000c03
[ 2.705903] pci 0000:00:1a.7: reg 10: [mem 0xdf6ff800-0xdf6ffbff]
[ 2.705971] pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
[ 2.705974] pci 0000:00:1a.7: PME# disabled
[ 2.705993] pci 0000:00:1c.0: [8086:2940] type 1 class 0x000604
[ 2.706042] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[ 2.706045] pci 0000:00:1c.0: PME# disabled
[ 2.706071] pci 0000:00:1d.0: [8086:2934] type 0 class 0x000c03
[ 2.706110] pci 0000:00:1d.0: reg 20: [io 0xdc40-0xdc5f]
[ 2.706150] pci 0000:00:1d.1: [8086:2935] type 0 class 0x000c03
[ 2.706189] pci 0000:00:1d.1: reg 20: [io 0xdc60-0xdc7f]
[ 2.706229] pci 0000:00:1d.2: [8086:2936] type 0 class 0x000c03
[ 2.706268] pci 0000:00:1d.2: reg 20: [io 0xdc80-0xdc9f]
[ 2.706316] pci 0000:00:1d.7: [8086:293a] type 0 class 0x000c03
[ 2.706336] pci 0000:00:1d.7: reg 10: [mem 0xdf6ffc00-0xdf6fffff]
[ 2.706403] pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
[ 2.706407] pci 0000:00:1d.7: PME# disabled
[ 2.706425] pci 0000:00:1e.0: [8086:244e] type 1 class 0x000604
[ 2.706476] pci 0000:00:1f.0: [8086:2918] type 0 class 0x000601
[ 2.706547] pci 0000:00:1f.0: quirk: [io 0x0800-0x087f] claimed by ICH6 ACPI/GPIO/TCO
[ 2.706551] pci 0000:00:1f.0: quirk: [io 0x0880-0x08bf] claimed by ICH6 GPIO
[ 2.706555] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0c00 (mask 007f)
[ 2.706558] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 2 PIO at 0ca0 (mask 000f)
[ 2.706561] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 3 PIO at 00e0 (mask 000f)
[ 2.706636] pci 0000:01:00.0: [14e4:163a] type 0 class 0x000200
[ 2.706651] pci 0000:01:00.0: reg 10: [mem 0xda000000-0xdbffffff 64bit]
[ 2.706711] pci 0000:01:00.0: PME# supported from D0 D3hot D3cold
[ 2.706714] pci 0000:01:00.0: PME# disabled
[ 2.706742] pci 0000:01:00.1: [14e4:163a] type 0 class 0x000200
[ 2.706756] pci 0000:01:00.1: reg 10: [mem 0xdc000000-0xddffffff 64bit]
[ 2.706816] pci 0000:01:00.1: PME# supported from D0 D3hot D3cold
[ 2.706819] pci 0000:01:00.1: PME# disabled
[ 2.706842] pci 0000:00:01.0: PCI bridge to [bus 01-01]
[ 2.706845] pci 0000:00:01.0: bridge window [io 0xf000-0x0000] (disabled)
[ 2.706849] pci 0000:00:01.0: bridge window [mem 0xda000000-0xddffffff]
[ 2.706853] pci 0000:00:01.0: bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
[ 2.706895] pci 0000:03:00.0: [8086:10f8] type 0 class 0x000200
[ 2.706908] pci 0000:03:00.0: reg 10: [mem 0xd9000000-0xd93fffff 64bit pref]
[ 2.706915] pci 0000:03:00.0: reg 18: [io 0xecc0-0xecdf]
[ 2.706929] pci 0000:03:00.0: reg 20: [mem 0xd9bf8000-0xd9bfbfff 64bit pref]
[ 2.706936] pci 0000:03:00.0: reg 30: [mem 0xdf000000-0xdf3fffff pref]
[ 2.706957] pci 0000:03:00.0: PME# supported from D0 D3hot
[ 2.706960] pci 0000:03:00.0: PME# disabled
[ 2.706986] pci 0000:03:00.0: reg 184: [mem 0x00000000-0x00003fff 64bit]
[ 2.706998] pci 0000:03:00.0: reg 190: [mem 0x00000000-0x00003fff 64bit]
[ 2.707019] pci 0000:03:00.1: [8086:10f8] type 0 class 0x000200
[ 2.707032] pci 0000:03:00.1: reg 10: [mem 0xd9400000-0xd97fffff 64bit pref]
[ 2.707039] pci 0000:03:00.1: reg 18: [io 0xece0-0xecff]
[ 2.707053] pci 0000:03:00.1: reg 20: [mem 0xd9bfc000-0xd9bfffff 64bit pref]
[ 2.707060] pci 0000:03:00.1: reg 30: [mem 0xdf000000-0xdf3fffff pref]
[ 2.707081] pci 0000:03:00.1: PME# supported from D0 D3hot
[ 2.707084] pci 0000:03:00.1: PME# disabled
[ 2.707106] pci 0000:03:00.1: reg 184: [mem 0x00000000-0x00003fff 64bit]
[ 2.707119] pci 0000:03:00.1: reg 190: [mem 0x00000000-0x00003fff 64bit]
[ 2.707134] pci 0000:00:07.0: PCI bridge to [bus 03-03]
[ 2.707137] pci 0000:00:07.0: bridge window [io 0xe000-0xefff]
[ 2.707140] pci 0000:00:07.0: bridge window [mem 0xdf000000-0xdf3fffff]
[ 2.707144] pci 0000:00:07.0: bridge window [mem 0xd9000000-0xd9bfffff 64bit pref]
[ 2.707176] pci 0000:00:09.0: PCI bridge to [bus 04-04]
[ 2.707179] pci 0000:00:09.0: bridge window [io 0xf000-0x0000] (disabled)
[ 2.707182] pci 0000:00:09.0: bridge window [mem 0xfff00000-0x000fffff] (disabled)
[ 2.707187] pci 0000:00:09.0: bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
[ 2.707238] pci 0000:02:00.0: [1000:0058] type 0 class 0x000100
[ 2.707252] pci 0000:02:00.0: reg 10: [io 0xfc00-0xfcff]
[ 2.707267] pci 0000:02:00.0: reg 14: [mem 0xdf5fc000-0xdf5fffff 64bit]
[ 2.707282] pci 0000:02:00.0: reg 1c: [mem 0xdf5e0000-0xdf5effff 64bit]
[ 2.707301] pci 0000:02:00.0: reg 30: [mem 0xdf400000-0xdf4fffff pref]
[ 2.707328] pci 0000:02:00.0: supports D1 D2
[ 2.707350] pci 0000:00:1c.0: PCI bridge to [bus 02-02]
[ 2.707353] pci 0000:00:1c.0: bridge window [io 0xf000-0xffff]
[ 2.707357] pci 0000:00:1c.0: bridge window [mem 0xdf400000-0xdf5fffff]
[ 2.707362] pci 0000:00:1c.0: bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
[ 2.707401] pci 0000:05:03.0: [102b:0532] type 0 class 0x000300
[ 2.707416] pci 0000:05:03.0: reg 10: [mem 0xd8800000-0xd8ffffff pref]
[ 2.707425] pci 0000:05:03.0: reg 14: [mem 0xdeffc000-0xdeffffff]
[ 2.707435] pci 0000:05:03.0: reg 18: [mem 0xde000000-0xde7fffff]
[ 2.707465] pci 0000:05:03.0: reg 30: [mem 0x00000000-0x0000ffff pref]
[ 2.707519] pci 0000:00:1e.0: PCI bridge to [bus 05-05] (subtractive decode)
[ 2.707522] pci 0000:00:1e.0: bridge window [io 0xf000-0x0000] (disabled)
[ 2.707526] pci 0000:00:1e.0: bridge window [mem 0xde000000-0xdeffffff]
[ 2.707531] pci 0000:00:1e.0: bridge window [mem 0xd8800000-0xd8ffffff 64bit pref]
[ 2.707533] pci 0000:00:1e.0: bridge window [io 0x0000-0x0cf7] (subtractive decode)
[ 2.707535] pci 0000:00:1e.0: bridge window [io 0x0d00-0xffff] (subtractive decode)
[ 2.707538] pci 0000:00:1e.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
[ 2.707540] pci 0000:00:1e.0: bridge window [mem 0xd0000000-0xfdffffff] (subtractive decode)
[ 2.707542] pci 0000:00:1e.0: bridge window [mem 0xfed40000-0xfed44fff] (subtractive decode)
[ 2.707561] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[ 2.707983] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX1._PRT]
[ 2.708059] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX7._PRT]
[ 2.708131] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX9._PRT]
[ 2.708201] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.SBEX._PRT]
[ 2.708269] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.COMP._PRT]
[ 2.710865] ACPI: PCI Interrupt Link [LK00] (IRQs 3 4 5 6 7 10 11 14 *15)
[ 2.710919] ACPI: PCI Interrupt Link [LK01] (IRQs 3 4 5 6 7 10 11 *14 15)
[ 2.710970] ACPI: PCI Interrupt Link [LK02] (IRQs 3 4 5 6 7 10 *11 14 15)
[ 2.711022] ACPI: PCI Interrupt Link [LK03] (IRQs 3 4 5 6 7 *10 11 14 15)
[ 2.711073] ACPI: PCI Interrupt Link [LK04] (IRQs 3 4 *5 6 7 10 11 14 15)
[ 2.711125] ACPI: PCI Interrupt Link [LK05] (IRQs 3 4 5 *6 7 10 11 14 15)
[ 2.711175] ACPI: PCI Interrupt Link [LK06] (IRQs 3 4 5 6 7 10 11 14 15) *0, disabled.
[ 2.711227] ACPI: PCI Interrupt Link [LK07] (IRQs 3 *4 5 6 7 10 11 14 15)
[ 2.711309] vgaarb: device added: PCI:0000:05:03.0,decodes=io+mem,owns=io+mem,locks=none
[ 2.711311] vgaarb: loaded
[ 2.711344] PCI: Using ACPI for IRQ routing
[ 2.711346] PCI: pci_cache_line_size set to 64 bytes
[ 2.711414] reserve RAM buffer: 00000000cf379000 - 00000000cfffffff
[ 2.711513] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0
[ 2.711517] hpet0: 4 comparators, 64-bit 14.318180 MHz counter
[ 2.713528] Switching to clocksource hpet
[ 2.714937] pnp: PnP ACPI init
[ 2.714953] ACPI: bus type pnp registered
[ 2.715045] pnp 00:00: [bus 00-ff]
[ 2.715047] pnp 00:00: [io 0x0cf8-0x0cff]
[ 2.715049] pnp 00:00: [io 0x0000-0x0cf7 window]
[ 2.715054] pnp 00:00: [io 0x0d00-0xffff window]
[ 2.715056] pnp 00:00: [mem 0x000a0000-0x000bffff window]
[ 2.715058] pnp 00:00: [mem 0xd0000000-0xfdffffff window]
[ 2.715060] pnp 00:00: [mem 0xfed40000-0xfed44fff window]
[ 2.715095] pnp 00:00: Plug and Play ACPI device, IDs PNP0a08 PNP0a03 (active)
[ 2.715135] pnp 00:01: [io 0x0080-0x009f]
[ 2.715137] pnp 00:01: [io 0x0000-0x001f]
[ 2.715139] pnp 00:01: [io 0x00c0-0x00df]
[ 2.715141] pnp 00:01: [dma 4]
[ 2.715171] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
[ 2.715189] pnp 00:02: [io 0x00f0-0x00ff]
[ 2.715200] pnp 00:02: [irq 13]
[ 2.715227] pnp 00:02: Plug and Play ACPI device, IDs PNP0c04 (active)
[ 2.715246] pnp 00:03: [io 0x0061]
[ 2.715290] system 00:03: Plug and Play ACPI device, IDs PNP0c01 (active)
[ 2.715309] pnp 00:04: [io 0x0070-0x007f]
[ 2.715316] pnp 00:04: [irq 8]
[ 2.715344] pnp 00:04: Plug and Play ACPI device, IDs PNP0b00 (active)
[ 2.715358] Switched to NOHz mode on CPU #0
[ 2.715402] Switched to NOHz mode on CPU #14
[ 2.715406] Switched to NOHz mode on CPU #18
[ 2.715421] Switched to NOHz mode on CPU #12
[ 2.715425] Switched to NOHz mode on CPU #5
[ 2.715429] Switched to NOHz mode on CPU #22
[ 2.715432] Switched to NOHz mode on CPU #8
[ 2.715433] Switched to NOHz mode on CPU #6
[ 2.715444] Switched to NOHz mode on CPU #21
[ 2.715452] Switched to NOHz mode on CPU #1
[ 2.715457] Switched to NOHz mode on CPU #2
[ 2.715460] Switched to NOHz mode on CPU #4
[ 2.715465] Switched to NOHz mode on CPU #7
[ 2.715469] Switched to NOHz mode on CPU #11
[ 2.715473] Switched to NOHz mode on CPU #3
[ 2.715476] Switched to NOHz mode on CPU #16
[ 2.715479] Switched to NOHz mode on CPU #19
[ 2.715482] Switched to NOHz mode on CPU #15
[ 2.715487] Switched to NOHz mode on CPU #13
[ 2.715489] Switched to NOHz mode on CPU #20
[ 2.715492] Switched to NOHz mode on CPU #23
[ 2.715495] Switched to NOHz mode on CPU #10
[ 2.715498] Switched to NOHz mode on CPU #9
[ 2.715502] pnp 00:05: Plug and Play ACPI device, IDs PNP0501 (disabled)
[ 2.715505] Switched to NOHz mode on CPU #17
[ 2.716145] pnp 00:06: [io 0x0800-0x087f]
[ 2.716147] pnp 00:06: [io 0x00e0-0x00e7]
[ 2.716149] pnp 00:06: [io 0x0880-0x08ff]
[ 2.716150] pnp 00:06: [io 0x0900-0x091f]
[ 2.716151] pnp 00:06: [io 0x0920-0x0923]
[ 2.716153] pnp 00:06: [io 0x0924]
[ 2.716154] pnp 00:06: [io 0x0ca0-0x0ca7]
[ 2.716156] pnp 00:06: [io 0x0ca9-0x0cab]
[ 2.716157] pnp 00:06: [io 0x0cad-0x0caf]
[ 2.716159] pnp 00:06: [io 0x0060-0x005f disabled]
[ 2.716160] pnp 00:06: [io 0x0064-0x0063 disabled]
[ 2.716208] system 00:06: [io 0x0800-0x087f] has been reserved
[ 2.716211] system 00:06: [io 0x0880-0x08ff] could not be reserved
[ 2.716213] system 00:06: [io 0x0900-0x091f] has been reserved
[ 2.716215] system 00:06: [io 0x0920-0x0923] has been reserved
[ 2.716218] system 00:06: [io 0x0924] has been reserved
[ 2.716220] system 00:06: [io 0x0ca0-0x0ca7] has been reserved
[ 2.716222] system 00:06: [io 0x0ca9-0x0cab] has been reserved
[ 2.716224] system 00:06: [io 0x0cad-0x0caf] has been reserved
[ 2.716227] system 00:06: Plug and Play ACPI device, IDs PNP0c01 (active)
[ 2.716268] pnp 00:07: [io 0x0ca8]
[ 2.716269] pnp 00:07: [io 0x0cac]
[ 2.716271] pnp 00:07: [irq 0 disabled]
[ 2.716316] system 00:07: [io 0x0ca8] has been reserved
[ 2.716319] system 00:07: [io 0x0cac] has been reserved
[ 2.716321] system 00:07: Plug and Play ACPI device, IDs IPI0001 PNP0c01 (active)
[ 2.717306] pnp 00:08: [mem 0xe0000000-0xefffffff]
[ 2.717350] system 00:08: [mem 0xe0000000-0xefffffff] has been reserved
[ 2.717352] system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 2.717397] pnp 00:09: [mem 0xfed00000-0xfed003ff]
[ 2.717455] pnp 00:09: Plug and Play ACPI device, IDs PNP0103 (active)
[ 2.717470] pnp 00:0a: [mem 0xfed90000-0xfed91fff]
[ 2.717513] system 00:0a: [mem 0xfed90000-0xfed91fff] has been reserved
[ 2.717516] system 00:0a: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 2.717667] pnp: PnP ACPI: found 11 devices
[ 2.717669] ACPI: ACPI bus type pnp unregistered
[ 2.724012] pci 0000:03:00.1: address space collision: [mem 0xdf000000-0xdf3fffff pref] conflicts with 0000:03:00.0 [mem 0xdf000000-0xdf3fffff pref]
[ 2.724046] pci 0000:00:01.0: PCI bridge to [bus 01-01]
[ 2.724047] pci 0000:00:01.0: bridge window [io disabled]
[ 2.724051] pci 0000:00:01.0: bridge window [mem 0xda000000-0xddffffff]
[ 2.724054] pci 0000:00:01.0: bridge window [mem pref disabled]
[ 2.724066] pci 0000:03:00.0: reg 184: [mem 0x00000000-0x00003fff 64bit]
[ 2.724074] pci 0000:03:00.0: reg 190: [mem 0x00000000-0x00003fff 64bit]
[ 2.724082] pci 0000:03:00.0: reg 184: [mem 0x00000000-0x00003fff 64bit]
[ 2.724091] pci 0000:03:00.0: reg 184: [mem 0x00000000-0x00003fff 64bit]
[ 2.724099] pci 0000:03:00.1: reg 184: [mem 0x00000000-0x00003fff 64bit]
[ 2.724107] pci 0000:03:00.0: reg 184: [mem 0x00000000-0x00003fff 64bit]
[ 2.724115] pci 0000:03:00.0: reg 190: [mem 0x00000000-0x00003fff 64bit]
[ 2.724123] pci 0000:03:00.1: reg 190: [mem 0x00000000-0x00003fff 64bit]
[ 2.724132] pci 0000:03:00.0: reg 184: [mem 0x00000000-0x00003fff 64bit]
[ 2.724140] pci 0000:03:00.0: reg 190: [mem 0x00000000-0x00003fff 64bit]
[ 2.724148] pci 0000:03:00.1: reg 184: [mem 0x00000000-0x00003fff 64bit]
[ 2.724153] pci 0000:03:00.1: BAR 6: can't assign mem pref (size 0x400000)
[ 2.724161] pci 0000:03:00.0: reg 184: [mem 0x00000000-0x00003fff 64bit]
[ 2.724169] pci 0000:03:00.0: reg 184: [mem 0x00000000-0x00003fff 64bit]
[ 2.724171] pci 0000:03:00.0: BAR 7: can't assign mem (size 0x100000)
[ 2.724180] pci 0000:03:00.0: reg 190: [mem 0x00000000-0x00003fff 64bit]
[ 2.724188] pci 0000:03:00.0: reg 190: [mem 0x00000000-0x00003fff 64bit]
[ 2.724190] pci 0000:03:00.0: BAR 10: can't assign mem (size 0x100000)
[ 2.724198] pci 0000:03:00.1: reg 184: [mem 0x00000000-0x00003fff 64bit]
[ 2.724206] pci 0000:03:00.1: reg 184: [mem 0x00000000-0x00003fff 64bit]
[ 2.724208] pci 0000:03:00.1: BAR 7: can't assign mem (size 0x100000)
[ 2.724217] pci 0000:03:00.1: reg 190: [mem 0x00000000-0x00003fff 64bit]
[ 2.724225] pci 0000:03:00.1: reg 190: [mem 0x00000000-0x00003fff 64bit]
[ 2.724227] pci 0000:03:00.1: BAR 10: can't assign mem (size 0x100000)
[ 2.724229] pci 0000:00:07.0: PCI bridge to [bus 03-03]
[ 2.724231] pci 0000:00:07.0: bridge window [io 0xe000-0xefff]
[ 2.724235] pci 0000:00:07.0: bridge window [mem 0xdf000000-0xdf3fffff]
[ 2.724238] pci 0000:00:07.0: bridge window [mem 0xd9000000-0xd9bfffff 64bit pref]
[ 2.724243] pci 0000:00:09.0: PCI bridge to [bus 04-04]
[ 2.724244] pci 0000:00:09.0: bridge window [io disabled]
[ 2.724247] pci 0000:00:09.0: bridge window [mem disabled]
[ 2.724250] pci 0000:00:09.0: bridge window [mem pref disabled]
[ 2.724255] pci 0000:00:1c.0: PCI bridge to [bus 02-02]
[ 2.724257] pci 0000:00:1c.0: bridge window [io 0xf000-0xffff]
[ 2.724261] pci 0000:00:1c.0: bridge window [mem 0xdf400000-0xdf5fffff]
[ 2.724264] pci 0000:00:1c.0: bridge window [mem pref disabled]
[ 2.724270] pci 0000:05:03.0: BAR 6: assigned [mem 0xde800000-0xde80ffff pref]
[ 2.724272] pci 0000:00:1e.0: PCI bridge to [bus 05-05]
[ 2.724274] pci 0000:00:1e.0: bridge window [io disabled]
[ 2.724278] pci 0000:00:1e.0: bridge window [mem 0xde000000-0xdeffffff]
[ 2.724281] pci 0000:00:1e.0: bridge window [mem 0xd8800000-0xd8ffffff 64bit pref]
[ 2.724302] pci 0000:00:01.0: PCI INT A -> GSI 53 (level, low) -> IRQ 53
[ 2.724306] pci 0000:00:01.0: setting latency timer to 64
[ 2.724311] pci 0000:00:07.0: PCI INT A -> GSI 53 (level, low) -> IRQ 53
[ 2.724314] pci 0000:00:07.0: setting latency timer to 64
[ 2.724318] pci 0000:00:09.0: PCI INT A -> GSI 53 (level, low) -> IRQ 53
[ 2.724321] pci 0000:00:09.0: setting latency timer to 64
[ 2.724337] pci 0000:00:1c.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 2.724340] pci 0000:00:1c.0: setting latency timer to 64
[ 2.724346] pci 0000:00:1e.0: setting latency timer to 64
[ 2.724349] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
[ 2.724351] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
[ 2.724352] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
[ 2.724354] pci_bus 0000:00: resource 7 [mem 0xd0000000-0xfdffffff]
[ 2.724356] pci_bus 0000:00: resource 8 [mem 0xfed40000-0xfed44fff]
[ 2.724358] pci_bus 0000:01: resource 1 [mem 0xda000000-0xddffffff]
[ 2.724360] pci_bus 0000:03: resource 0 [io 0xe000-0xefff]
[ 2.724362] pci_bus 0000:03: resource 1 [mem 0xdf000000-0xdf3fffff]
[ 2.724364] pci_bus 0000:03: resource 2 [mem 0xd9000000-0xd9bfffff 64bit pref]
[ 2.724366] pci_bus 0000:02: resource 0 [io 0xf000-0xffff]
[ 2.724368] pci_bus 0000:02: resource 1 [mem 0xdf400000-0xdf5fffff]
[ 2.724370] pci_bus 0000:05: resource 1 [mem 0xde000000-0xdeffffff]
[ 2.724372] pci_bus 0000:05: resource 2 [mem 0xd8800000-0xd8ffffff 64bit pref]
[ 2.724374] pci_bus 0000:05: resource 4 [io 0x0000-0x0cf7]
[ 2.724376] pci_bus 0000:05: resource 5 [io 0x0d00-0xffff]
[ 2.724377] pci_bus 0000:05: resource 6 [mem 0x000a0000-0x000bffff]
[ 2.724379] pci_bus 0000:05: resource 7 [mem 0xd0000000-0xfdffffff]
[ 2.724381] pci_bus 0000:05: resource 8 [mem 0xfed40000-0xfed44fff]
[ 2.724415] NET: Registered protocol family 2
[ 2.724804] IP route cache hash table entries: 524288 (order: 10, 4194304 bytes)
[ 2.726140] TCP established hash table entries: 524288 (order: 11, 8388608 bytes)
[ 2.727705] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
[ 2.727905] TCP: Hash tables configured (established 524288 bind 65536)
[ 2.727907] TCP reno registered
[ 2.727993] UDP hash table entries: 32768 (order: 8, 1048576 bytes)
[ 2.728272] UDP-Lite hash table entries: 32768 (order: 8, 1048576 bytes)
[ 2.728731] NET: Registered protocol family 1
[ 2.741496] pci 0000:05:03.0: Boot video device
[ 2.741499] PCI: CLS 64 bytes, default 64
[ 2.741546] Unpacking initramfs...
[ 2.959935] Freeing initrd memory: 10872k freed
[ 2.962406] DMAR: Device scope device [0000:00:1a.02] not found
[ 2.962409] DMAR: Device scope device [0000:00:1a.02] not found
[ 2.962413] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[ 2.962416] Placing 64MB software IO TLB between ffff8800cb000000 - ffff8800cf000000
[ 2.962417] software IO TLB at phys 0xcb000000 - 0xcf000000
[ 2.963852] audit: initializing netlink socket (disabled)
[ 2.963864] type=2000 audit(1300368828.480:1): initialized
[ 2.975095] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[ 2.976577] VFS: Disk quotas dquot_6.5.2
[ 2.976634] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 2.976738] msgmni has been set to 32768
[ 2.977011] alg: No test for stdrng (krng)
[ 2.977060] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[ 2.977064] io scheduler noop registered
[ 2.977065] io scheduler deadline registered
[ 2.977099] io scheduler cfq registered (default)
[ 2.977257] pcieport 0000:00:1c.0: setting latency timer to 64
[ 2.977303] pcieport 0000:00:1c.0: irq 73 for MSI/MSI-X
[ 2.977481] ERST: Error Record Serialization Table (ERST) support is initialized.
[ 2.977535] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 3.076953] serial 00:05: [io 0x03f8-0x03ff]
[ 3.077000] serial 00:05: [irq 4]
[ 3.077335] serial 00:05: activated
[ 3.097674] 00:05: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 3.097908] Linux agpgart interface v0.103
[ 3.098057] i8042: PNP: No PS/2 controller found. Probing ports directly.
[ 3.098914] i8042: No controller found
[ 3.099040] mousedev: PS/2 mouse device common for all mice
[ 3.099076] rtc_cmos 00:04: RTC can wake from S4
[ 3.099174] rtc_cmos 00:04: rtc core: registered rtc_cmos as rtc0
[ 3.099199] rtc0: alarms up to one day, y3k, 242 bytes nvram, hpet irqs
[ 3.099211] cpuidle: using governor ladder
[ 3.099212] cpuidle: using governor menu
[ 3.099426] TCP cubic registered
[ 3.099535] NET: Registered protocol family 10
[ 3.100189] Mobile IPv6
[ 3.100192] NET: Registered protocol family 17
[ 3.100196] Registering the dns_resolver key type
[ 3.100315] PM: Hibernation image not present or could not be loaded.
[ 3.100321] registered taskstats version 1
[ 3.100724] rtc_cmos 00:04: setting system clock to 2011-03-17 13:33:50 UTC (1300368830)
[ 3.100742] Initalizing network drop monitor service
[ 3.101991] Freeing unused kernel memory: 600k freed
[ 3.102131] Write protecting the kernel read-only data: 6144k
[ 3.105054] Freeing unused kernel memory: 956k freed
[ 3.107742] Freeing unused kernel memory: 828k freed
[ 3.116956] udev[138]: starting version 166
[ 3.131987] dca service started, version 1.12.1
[ 3.142861] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 3.2.9-k2
[ 3.142864] ixgbe: Copyright (c) 1999-2010 Intel Corporation.
[ 3.142916] ixgbe 0000:03:00.0: PCI INT B -> GSI 45 (level, low) -> IRQ 45
[ 3.142928] ixgbe 0000:03:00.0: setting latency timer to 64
[ 3.148424] usbcore: registered new interface driver usbfs
[ 3.148447] usbcore: registered new interface driver hub
[ 3.148484] usbcore: registered new device driver usb
[ 3.152286] bnx2: Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v2.0.21 (Dec 23, 2010)
[ 3.152292] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 3.152322] ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 19 (level, low) -> IRQ 19
[ 3.152334] bnx2 0000:01:00.0: PCI INT A -> GSI 36 (level, low) -> IRQ 36
[ 3.152347] bnx2 0000:01:00.0: setting latency timer to 64
[ 3.152360] ehci_hcd 0000:00:1a.7: setting latency timer to 64
[ 3.152364] ehci_hcd 0000:00:1a.7: EHCI Host Controller
[ 3.152390] ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1
[ 3.156428] bnx2 0000:01:00.0: eth0: Broadcom NetXtreme II BCM5709 1000Base-SX (C0) PCI Express found at mem da000000, IRQ 36, node addr 5c:26:0a:fc:f1:14
[ 3.156468] bnx2 0000:01:00.1: PCI INT B -> GSI 48 (level, low) -> IRQ 48
[ 3.156475] bnx2 0000:01:00.1: setting latency timer to 64
[ 3.160436] bnx2 0000:01:00.1: eth1: Broadcom NetXtreme II BCM5709 1000Base-SX (C0) PCI Express found at mem dc000000, IRQ 48, node addr 5c:26:0a:fc:f1:16
[ 3.163840] SCSI subsystem initialized
[ 3.171257] Fusion MPT base driver 3.04.18
[ 3.171258] Copyright (c) 1999-2008 LSI Corporation
[ 3.177915] Fusion MPT SAS Host driver 3.04.18
[ 3.177933] mptsas 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 3.178025] mptbase: ioc0: Initiating bringup
[ 3.248450] ehci_hcd 0000:00:1a.7: debug port 1
[ 3.252330] ehci_hcd 0000:00:1a.7: cache line size of 64 is not supported
[ 3.252345] ehci_hcd 0000:00:1a.7: irq 19, io mem 0xdf6ff800
[ 3.264382] ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00
[ 3.264403] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 3.264406] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.264409] usb usb1: Product: EHCI Host Controller
[ 3.264412] usb usb1: Manufacturer: Linux 2.6.38-sj+1 ehci_hcd
[ 3.264417] usb usb1: SerialNumber: 0000:00:1a.7
[ 3.264538] hub 1-0:1.0: USB hub found
[ 3.264541] hub 1-0:1.0: 4 ports detected
[ 3.264613] ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 21 (level, low) -> IRQ 21
[ 3.264653] ehci_hcd 0000:00:1d.7: setting latency timer to 64
[ 3.264656] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[ 3.264663] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2
[ 3.304295] ehci_hcd 0000:00:1d.7: debug port 1
[ 3.308161] ehci_hcd 0000:00:1d.7: cache line size of 64 is not supported
[ 3.308174] ehci_hcd 0000:00:1d.7: irq 21, io mem 0xdf6ffc00
[ 3.320241] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
[ 3.320255] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[ 3.320258] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.320260] usb usb2: Product: EHCI Host Controller
[ 3.320262] usb usb2: Manufacturer: Linux 2.6.38-sj+1 ehci_hcd
[ 3.320264] usb usb2: SerialNumber: 0000:00:1d.7
[ 3.320386] hub 2-0:1.0: USB hub found
[ 3.320390] hub 2-0:1.0: 6 ports detected
[ 3.321250] ixgbe 0000:03:00.0: irq 74 for MSI/MSI-X
[ 3.321262] ixgbe 0000:03:00.0: irq 75 for MSI/MSI-X
[ 3.321272] ixgbe 0000:03:00.0: irq 76 for MSI/MSI-X
[ 3.321283] ixgbe 0000:03:00.0: irq 77 for MSI/MSI-X
[ 3.321293] ixgbe 0000:03:00.0: irq 78 for MSI/MSI-X
[ 3.321304] ixgbe 0000:03:00.0: irq 79 for MSI/MSI-X
[ 3.321314] ixgbe 0000:03:00.0: irq 80 for MSI/MSI-X
[ 3.321325] ixgbe 0000:03:00.0: irq 81 for MSI/MSI-X
[ 3.321335] ixgbe 0000:03:00.0: irq 82 for MSI/MSI-X
[ 3.321346] ixgbe 0000:03:00.0: irq 83 for MSI/MSI-X
[ 3.321356] ixgbe 0000:03:00.0: irq 84 for MSI/MSI-X
[ 3.321371] ixgbe 0000:03:00.0: irq 85 for MSI/MSI-X
[ 3.321381] ixgbe 0000:03:00.0: irq 86 for MSI/MSI-X
[ 3.321390] ixgbe 0000:03:00.0: irq 87 for MSI/MSI-X
[ 3.321399] ixgbe 0000:03:00.0: irq 88 for MSI/MSI-X
[ 3.321409] ixgbe 0000:03:00.0: irq 89 for MSI/MSI-X
[ 3.321418] ixgbe 0000:03:00.0: irq 90 for MSI/MSI-X
[ 3.321427] ixgbe 0000:03:00.0: irq 91 for MSI/MSI-X
[ 3.321437] ixgbe 0000:03:00.0: irq 92 for MSI/MSI-X
[ 3.321447] ixgbe 0000:03:00.0: irq 93 for MSI/MSI-X
[ 3.321456] ixgbe 0000:03:00.0: irq 94 for MSI/MSI-X
[ 3.321466] ixgbe 0000:03:00.0: irq 95 for MSI/MSI-X
[ 3.321475] ixgbe 0000:03:00.0: irq 96 for MSI/MSI-X
[ 3.321484] ixgbe 0000:03:00.0: irq 97 for MSI/MSI-X
[ 3.321493] ixgbe 0000:03:00.0: irq 98 for MSI/MSI-X
[ 3.321540] ixgbe 0000:03:00.0: Multiqueue Enabled: Rx Queue count = 24, Tx Queue count = 24
[ 3.321546] ixgbe 0000:03:00.0: (PCI Express:5.0Gb/s:Width x8) 00:1b:21:87:7e:9c
[ 3.321632] ixgbe 0000:03:00.0: MAC: 2, PHY: 0, PBA No: E90209-006
[ 3.322274] uhci_hcd: USB Universal Host Controller Interface driver
[ 3.322350] uhci_hcd 0000:00:1a.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 3.322356] uhci_hcd 0000:00:1a.0: setting latency timer to 64
[ 3.322359] uhci_hcd 0000:00:1a.0: UHCI Host Controller
[ 3.322369] uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3
[ 3.418733] ixgbe 0000:03:00.0: Intel(R) 10 Gigabit Network Connection
[ 3.418767] ixgbe 0000:03:00.1: PCI INT A -> GSI 38 (level, low) -> IRQ 38
[ 3.418773] ixgbe 0000:03:00.1: setting latency timer to 64
[ 3.436042] uhci_hcd 0000:00:1a.0: irq 17, io base 0x0000dc00
[ 3.436076] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
[ 3.436078] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.436081] usb usb3: Product: UHCI Host Controller
[ 3.436083] usb usb3: Manufacturer: Linux 2.6.38-sj+1 uhci_hcd
[ 3.436085] usb usb3: SerialNumber: 0000:00:1a.0
[ 3.436220] hub 3-0:1.0: USB hub found
[ 3.436223] hub 3-0:1.0: 2 ports detected
[ 3.436304] uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 18 (level, low) -> IRQ 18
[ 3.436310] uhci_hcd 0000:00:1a.1: setting latency timer to 64
[ 3.436313] uhci_hcd 0000:00:1a.1: UHCI Host Controller
[ 3.436321] uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4
[ 3.471972] uhci_hcd 0000:00:1a.1: irq 18, io base 0x0000dc20
[ 3.472010] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
[ 3.472013] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.472016] usb usb4: Product: UHCI Host Controller
[ 3.472019] usb usb4: Manufacturer: Linux 2.6.38-sj+1 uhci_hcd
[ 3.472021] usb usb4: SerialNumber: 0000:00:1a.1
[ 3.472164] hub 4-0:1.0: USB hub found
[ 3.472169] hub 4-0:1.0: 2 ports detected
[ 3.472252] uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
[ 3.472259] uhci_hcd 0000:00:1d.0: setting latency timer to 64
[ 3.472262] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[ 3.472271] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 5
[ 3.499904] uhci_hcd 0000:00:1d.0: irq 21, io base 0x0000dc40
[ 3.499943] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
[ 3.499946] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.499949] usb usb5: Product: UHCI Host Controller
[ 3.499952] usb usb5: Manufacturer: Linux 2.6.38-sj+1 uhci_hcd
[ 3.499954] usb usb5: SerialNumber: 0000:00:1d.0
[ 3.500098] hub 5-0:1.0: USB hub found
[ 3.500103] hub 5-0:1.0: 2 ports detected
[ 3.500197] uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 20 (level, low) -> IRQ 20
[ 3.500204] uhci_hcd 0000:00:1d.1: setting latency timer to 64
[ 3.500208] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[ 3.500217] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 6
[ 3.528950] ixgbe 0000:03:00.1: irq 99 for MSI/MSI-X
[ 3.528961] ixgbe 0000:03:00.1: irq 100 for MSI/MSI-X
[ 3.528971] ixgbe 0000:03:00.1: irq 101 for MSI/MSI-X
[ 3.528982] ixgbe 0000:03:00.1: irq 102 for MSI/MSI-X
[ 3.528992] ixgbe 0000:03:00.1: irq 103 for MSI/MSI-X
[ 3.529003] ixgbe 0000:03:00.1: irq 104 for MSI/MSI-X
[ 3.529014] ixgbe 0000:03:00.1: irq 105 for MSI/MSI-X
[ 3.529024] ixgbe 0000:03:00.1: irq 106 for MSI/MSI-X
[ 3.529034] ixgbe 0000:03:00.1: irq 107 for MSI/MSI-X
[ 3.529045] ixgbe 0000:03:00.1: irq 108 for MSI/MSI-X
[ 3.529055] ixgbe 0000:03:00.1: irq 109 for MSI/MSI-X
[ 3.529066] ixgbe 0000:03:00.1: irq 110 for MSI/MSI-X
[ 3.529076] ixgbe 0000:03:00.1: irq 111 for MSI/MSI-X
[ 3.529086] ixgbe 0000:03:00.1: irq 112 for MSI/MSI-X
[ 3.529097] ixgbe 0000:03:00.1: irq 113 for MSI/MSI-X
[ 3.529107] ixgbe 0000:03:00.1: irq 114 for MSI/MSI-X
[ 3.529118] ixgbe 0000:03:00.1: irq 115 for MSI/MSI-X
[ 3.529128] ixgbe 0000:03:00.1: irq 116 for MSI/MSI-X
[ 3.529138] ixgbe 0000:03:00.1: irq 117 for MSI/MSI-X
[ 3.529149] ixgbe 0000:03:00.1: irq 118 for MSI/MSI-X
[ 3.529159] ixgbe 0000:03:00.1: irq 119 for MSI/MSI-X
[ 3.529169] ixgbe 0000:03:00.1: irq 120 for MSI/MSI-X
[ 3.529181] ixgbe 0000:03:00.1: irq 121 for MSI/MSI-X
[ 3.529191] ixgbe 0000:03:00.1: irq 122 for MSI/MSI-X
[ 3.529202] ixgbe 0000:03:00.1: irq 123 for MSI/MSI-X
[ 3.529250] ixgbe 0000:03:00.1: Multiqueue Enabled: Rx Queue count = 24, Tx Queue count = 24
[ 3.529256] ixgbe 0000:03:00.1: (PCI Express:5.0Gb/s:Width x8) 00:1b:21:87:7e:9e
[ 3.529342] ixgbe 0000:03:00.1: MAC: 2, PHY: 0, PBA No: E90209-006
[ 3.555811] uhci_hcd 0000:00:1d.1: irq 20, io base 0x0000dc60
[ 3.555867] usb usb6: New USB device found, idVendor=1d6b, idProduct=0001
[ 3.555872] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.555877] usb usb6: Product: UHCI Host Controller
[ 3.555880] usb usb6: Manufacturer: Linux 2.6.38-sj+1 uhci_hcd
[ 3.555884] usb usb6: SerialNumber: 0000:00:1d.1
[ 3.556107] hub 6-0:1.0: USB hub found
[ 3.556114] hub 6-0:1.0: 2 ports detected
[ 3.556231] uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 21 (level, low) -> IRQ 21
[ 3.556241] uhci_hcd 0000:00:1d.2: setting latency timer to 64
[ 3.556246] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[ 3.556258] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 7
[ 3.558969] ixgbe 0000:03:00.1: Intel(R) 10 Gigabit Network Connection
[ 3.591738] uhci_hcd 0000:00:1d.2: irq 21, io base 0x0000dc80
[ 3.591779] usb usb7: New USB device found, idVendor=1d6b, idProduct=0001
[ 3.591783] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.591786] usb usb7: Product: UHCI Host Controller
[ 3.591788] usb usb7: Manufacturer: Linux 2.6.38-sj+1 uhci_hcd
[ 3.591791] usb usb7: SerialNumber: 0000:00:1d.2
[ 3.591945] hub 7-0:1.0: USB hub found
[ 3.591949] hub 7-0:1.0: 2 ports detected
[ 3.811256] usb 5-2: new full speed USB device using uhci_hcd and address 2
[ 3.891093] ioc0: LSISAS1068E B3: Capabilities={Initiator}
[ 3.891119] mptsas 0000:02:00.0: setting latency timer to 64
[ 3.958966] Refined TSC clocksource calibration: 2260.999 MHz.
[ 3.958971] Switching to clocksource tsc
[ 3.974003] usb 5-2: New USB device found, idVendor=046b, idProduct=ff10
[ 3.974007] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3.974010] usb 5-2: Product: Virtual Keyboard and Mouse
[ 3.974012] usb 5-2: Manufacturer: American Megatrends Inc.
[ 3.974015] usb 5-2: SerialNumber: serial
[ 4.086804] input: American Megatrends Inc. Virtual Keyboard and Mouse as /devices/pci0000:00/0000:00:1d.0/usb5/5-2/5-2:1.0/input/input0
[ 4.086887] generic-usb 0003:046B:FF10.0001: input,hidraw0: USB HID v1.10 Keyboard [American Megatrends Inc. Virtual Keyboard and Mouse] on usb-0000:00:1d.0-2/input0
[ 4.091943] input: American Megatrends Inc. Virtual Keyboard and Mouse as /devices/pci0000:00/0000:00:1d.0/usb5/5-2/5-2:1.1/input/input1
[ 4.092073] generic-usb 0003:046B:FF10.0002: input,hidraw1: USB HID v1.10 Mouse [American Megatrends Inc. Virtual Keyboard and Mouse] on usb-0000:00:1d.0-2/input1
[ 4.092097] usbcore: registered new interface driver usbhid
[ 4.092100] usbhid: USB HID core driver
[ 4.146587] usb 6-2: new low speed USB device using uhci_hcd and address 2
[ 4.323337] usb 6-2: New USB device found, idVendor=0624, idProduct=de11
[ 4.323341] usb 6-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 4.323344] usb 6-2: Product: Avocent KVM
[ 4.323347] usb 6-2: Manufacturer: Avocent
[ 4.358509] input: Avocent Avocent KVM as /devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.0/input/input2
[ 4.358591] generic-usb 0003:0624:DE11.0003: input,hidraw2: USB HID v1.10 Keyboard [Avocent Avocent KVM] on usb-0000:00:1d.1-2/input0
[ 4.389508] input: Avocent Avocent KVM as /devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.1/input/input3
[ 4.389639] generic-usb 0003:0624:DE11.0004: input,hidraw3: USB HID v1.10 Mouse [Avocent Avocent KVM] on usb-0000:00:1d.1-2/input1
[ 33.132112] scsi0 : ioc0: LSISAS1068E B3, FwRev=00192f00h, Ports=1, MaxQ=266, IRQ=16
[ 33.166984] mptsas: ioc0: attaching ssp device: fw_channel 0, fw_id 0, phy 0, sas_addr 0x5000c50025bc50b1
[ 33.168073] scsi 0:0:0:0: Direct-Access SEAGATE ST9500430SS DS64 PQ: 0 ANSI: 5
[ 33.171520] mptsas: ioc0: attaching ssp device: fw_channel 0, fw_id 1, phy 1, sas_addr 0x5000c50025bdd755
[ 33.172442] scsi 0:0:1:0: Direct-Access SEAGATE ST9500430SS DS64 PQ: 0 ANSI: 5
[ 33.183919] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB)
[ 33.183989] sd 0:0:1:0: [sdb] 976773168 512-byte logical blocks: (500 GB/465 GiB)
[ 33.185730] sd 0:0:0:0: [sda] Write Protect is off
[ 33.185734] sd 0:0:0:0: [sda] Mode Sense: d7 00 10 08
[ 33.185764] sd 0:0:1:0: [sdb] Write Protect is off
[ 33.185767] sd 0:0:1:0: [sdb] Mode Sense: d7 00 10 08
[ 33.187063] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, supports DPO and FUA
[ 33.187090] sd 0:0:1:0: [sdb] Write cache: disabled, read cache: enabled, supports DPO and FUA
[ 33.228520] sdb: sdb1 sdb2 sdb3
[ 33.233271] sd 0:0:1:0: [sdb] Attached SCSI disk
[ 33.277929] sda: sda1 sda2 sda3
[ 33.282125] sd 0:0:0:0: [sda] Attached SCSI disk
[ 33.463015] md: raid1 personality registered for level 1
[ 33.470976] md: md2 stopped.
[ 33.472191] md: bind<sdb2>
[ 33.472404] md: bind<sda2>
[ 33.473663] bio: create slab <bio-1> at 1
[ 33.473754] md/raid1:md2: active with 2 out of 2 mirrors
[ 33.473775] md2: detected capacity change from 0 to 10737352704
[ 33.505960] md2: unknown partition table
[ 33.518890] md: md3 stopped.
[ 33.526232] md: bind<sdb3>
[ 33.526437] md: bind<sda3>
[ 33.527759] md/raid1:md3: active with 2 out of 2 mirrors
[ 33.527780] md3: detected capacity change from 0 to 489366159360
[ 33.536366] device-mapper: uevent: version 1.0.3
[ 33.536501] device-mapper: ioctl: 4.19.1-ioctl (2011-01-07) initialised: dm-devel@redhat.com
[ 33.537847] md3: unknown partition table
[ 33.639684] EXT3-fs: barriers not enabled
[ 33.640251] kjournald starting. Commit interval 5 seconds
[ 33.640275] EXT3-fs (md2): mounted filesystem with ordered data mode
[ 34.766559] udev[446]: starting version 166
[ 35.372834] input: PC Speaker as /devices/platform/pcspkr/input/input4
[ 35.445611] ACPI Error: No handler for Region [IPMI] (ffff880c17051240) [IPMI] (20110112/evregion-369)
[ 35.445620] ACPI Error: Region IPMI(0x7) has no handler (20110112/exfldio-292)
[ 35.445628] ACPI Error: Method parse/execution failed [\_SB_.PMI0._GHL] (Node ffff880c17050b18), AE_NOT_EXIST (20110112/psparse-536)
[ 35.445641] ACPI Error: Method parse/execution failed [\_SB_.PMI0._PMC] (Node ffff880c17050a78), AE_NOT_EXIST (20110112/psparse-536)
[ 35.445657] ACPI Exception: AE_NOT_EXIST, Evaluating _PMC (20110112/power_meter-773)
[ 35.474435] ACPI: acpi_idle registered with cpuidle
[ 35.474738] Monitor-Mwait will be used to enter C-1 state
[ 35.474777] Monitor-Mwait will be used to enter C-3 state
[ 35.480460] dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2)
[ 35.483956] EDAC MC: Ver: 2.1.0 Mar 16 2011
[ 35.530107] EDAC i7core: Driver loaded.
[ 35.586279] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input5
[ 35.586361] ACPI: Power Button [PWRF]
[ 35.735087] Error: Driver 'pcspkr' is already registered, aborting...
[ 36.558855] EXT3-fs (md2): using internal journal
[ 36.698522] Bridge firewalling registered
[ 36.737916] 802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
[ 36.737920] All bugs added by David S. Miller <davem@redhat.com>
[ 36.775239] tun: Universal TUN/TAP device driver, 1.6
[ 36.775243] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 38.295058] bonding: Ethernet Channel Bonding Driver: v3.7.0 (June 2, 2010)
[ 38.295062] bonding: Warning: either miimon or arp_interval and arp_ip_target module parameters must be specified, otherwise bonding will not detect link failures! see bonding.txt for details.
[ 38.297721] bonding: bond0: setting mode to active-backup (1).
[ 38.297893] bonding: bond0: Setting MII monitoring interval to 100.
[ 38.332778] bonding: bond0: doing slave updates when interface is down.
[ 38.332783] bonding: bond0: Adding slave eth0.
[ 38.332786] bonding: bond0: master_dev is not up in bond_enslave
[ 38.338318] bnx2 0000:01:00.0: irq 124 for MSI/MSI-X
[ 38.338330] bnx2 0000:01:00.0: irq 125 for MSI/MSI-X
[ 38.338341] bnx2 0000:01:00.0: irq 126 for MSI/MSI-X
[ 38.338352] bnx2 0000:01:00.0: irq 127 for MSI/MSI-X
[ 38.338364] bnx2 0000:01:00.0: irq 128 for MSI/MSI-X
[ 38.338376] bnx2 0000:01:00.0: irq 129 for MSI/MSI-X
[ 38.338387] bnx2 0000:01:00.0: irq 130 for MSI/MSI-X
[ 38.338399] bnx2 0000:01:00.0: irq 131 for MSI/MSI-X
[ 38.338410] bnx2 0000:01:00.0: irq 132 for MSI/MSI-X
[ 38.414682] bnx2 0000:01:00.0: eth0: using MSIX
[ 38.418713] bonding: bond0: enslaving eth0 as a backup interface with a down link.
[ 38.460349] bonding: bond0: doing slave updates when interface is down.
[ 38.460355] bonding: bond0: Adding slave eth1.
[ 38.460357] bonding: bond0: master_dev is not up in bond_enslave
[ 38.464510] bnx2 0000:01:00.1: irq 133 for MSI/MSI-X
[ 38.464523] bnx2 0000:01:00.1: irq 134 for MSI/MSI-X
[ 38.464533] bnx2 0000:01:00.1: irq 135 for MSI/MSI-X
[ 38.464544] bnx2 0000:01:00.1: irq 136 for MSI/MSI-X
[ 38.464554] bnx2 0000:01:00.1: irq 137 for MSI/MSI-X
[ 38.464565] bnx2 0000:01:00.1: irq 138 for MSI/MSI-X
[ 38.464577] bnx2 0000:01:00.1: irq 139 for MSI/MSI-X
[ 38.464588] bnx2 0000:01:00.1: irq 140 for MSI/MSI-X
[ 38.464600] bnx2 0000:01:00.1: irq 141 for MSI/MSI-X
[ 38.542424] bnx2 0000:01:00.1: eth1: using MSIX
[ 38.546448] bonding: bond0: enslaving eth1 as a backup interface with a down link.
[ 38.548688] bonding: bond0: Setting eth0 as primary slave.
[ 38.616753] ADDRCONF(NETDEV_UP): bond0: link is not ready
[ 38.616757] 8021q: adding VLAN 0 to HW filter on device bond0
[ 38.996745] device bond0 entered promiscuous mode
[ 39.010120] bnx2 0000:01:00.0: eth0: NIC SerDes Link is Up, 1000 Mbps full duplex, receive & transmit flow control ON
[ 39.109280] bonding: bond0: link status definitely up for interface eth0, 1000 Mbps full duplex.
[ 39.109285] bonding: bond0: making interface eth0 the new active one.
[ 39.109288] device eth0 entered promiscuous mode
[ 39.109343] bonding: bond0: first active interface up!
[ 39.113302] ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
[ 39.113331] br14: port 1(bond0) entering forwarding state
[ 39.113334] br14: port 1(bond0) entering forwarding state
[ 39.137871] bnx2 0000:01:00.1: eth1: NIC SerDes Link is Up, 1000 Mbps full duplex, receive & transmit flow control ON
[ 39.209074] bonding: bond0: link status definitely up for interface eth1, 1000 Mbps full duplex.
[ 40.048040] device bond0.15 entered promiscuous mode
[ 40.056510] br15: port 1(bond0.15) entering forwarding state
[ 40.056514] br15: port 1(bond0.15) entering forwarding state
[ 41.947060] fuse init (API version 7.16)
[ 44.014843] Ebtables v2.0 registered
[ 44.108232] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 44.165016] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 45.590254] device vnet0 entered promiscuous mode
[ 45.594389] br14: port 2(vnet0) entering forwarding state
[ 45.594393] br14: port 2(vnet0) entering forwarding state
[ 46.352377] device vnet1 entered promiscuous mode
[ 46.356656] br14: port 3(vnet1) entering forwarding state
[ 46.356660] br14: port 3(vnet1) entering forwarding state
[ 46.895209] device vnet2 entered promiscuous mode
[ 46.899245] br14: port 4(vnet2) entering forwarding state
[ 46.899249] br14: port 4(vnet2) entering forwarding state
[ 47.562023] device vnet3 entered promiscuous mode
[ 47.566065] br14: port 5(vnet3) entering forwarding state
[ 47.566069] br14: port 5(vnet3) entering forwarding state
[ 48.136984] device vnet4 entered promiscuous mode
[ 48.141029] br14: port 6(vnet4) entering forwarding state
[ 48.141033] br14: port 6(vnet4) entering forwarding state
[ 48.701802] device vnet5 entered promiscuous mode
[ 48.704561] br14: port 7(vnet5) entering forwarding state
[ 48.704565] br14: port 7(vnet5) entering forwarding state
[ 49.252830] device vnet6 entered promiscuous mode
[ 49.255315] br14: port 8(vnet6) entering forwarding state
[ 49.255318] br14: port 8(vnet6) entering forwarding state
[ 49.847766] device vnet7 entered promiscuous mode
[ 49.850492] br14: port 9(vnet7) entering forwarding state
[ 49.850496] br14: port 9(vnet7) entering forwarding state
[ 50.491336] device vnet8 entered promiscuous mode
[ 50.494595] br14: port 10(vnet8) entering forwarding state
[ 50.494599] br14: port 10(vnet8) entering forwarding state
[ 126.188510] ipmi message handler version 39.2
[ 126.206076] IPMI System Interface driver.
[ 126.206115] ipmi_si: probing via SMBIOS
[ 126.206118] ipmi_si: SMBIOS: io 0xca8 regsize 1 spacing 4 irq 0
[ 126.206121] ipmi_si: Adding SMBIOS-specified kcs state machine
[ 126.206126] ipmi_si: Trying SMBIOS-specified kcs state machine at i/o address 0xca8, slave address 0x20, irq 0
[ 126.365594] ipmi_si ipmi_si.0: Found new BMC (man_id: 0x0002a2, prod_id: 0xaabb, dev_id: 0x20)
[ 126.365609] ipmi_si ipmi_si.0: IPMI kcs interface initialized
[ 126.377015] ipmi device interface
[-- Attachment #5: interfaces --]
[-- Type: application/octet-stream, Size: 795 bytes --]
# Used by ifup(8) and ifdown(8). See the interfaces(5) manpage or
# /usr/share/doc/ifupdown/examples for more information.
auto lo
iface lo inet loopback
# LACP bonding on 2 x 1G
auto bond0
iface bond0 inet manual
slaves eth0 eth1
bond_mode 1
bond_primary eth0
bond_miimon 100
# LACP bonding on 2 x 1G
auto bond0.15
iface bond0.15 inet manual
vlan-raw-device bond0
## 10GE
# reset enslaved 10G interfaces
auto eth2
iface eth2 inet manual
up ifconfig $IFACE txqueuelen 10000
up ethtool -K $IFACE lro off
## Boot network
auto br14
iface br14 inet manual
bridge_ports bond0
bridge_stp off
bridge_fd 0
## ADM network
auto br15
iface br15 inet static
bridge_ports bond0.15
bridge_stp off
bridge_fd 0
address 10.15.0.42
netmask 255.255.0.0
gateway 10.15.255.254
[-- Attachment #6: ifconfig --]
[-- Type: application/octet-stream, Size: 5785 bytes --]
bond0 Link encap:Ethernet HWaddr 5c:26:0a:fc:f1:14
UP BROADCAST RUNNING PROMISC MASTER MULTICAST MTU:1500 Metric:1
RX packets:20907 errors:0 dropped:8265 overruns:0 frame:0
TX packets:2335 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3861879 (3.6 MiB) TX bytes:157324 (153.6 KiB)
bond0.15 Link encap:Ethernet HWaddr 5c:26:0a:fc:f1:14
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:2199 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:93654 (91.4 KiB)
br14 Link encap:Ethernet HWaddr 5c:26:0a:fc:f1:14
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:11378 errors:0 dropped:112 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1759027 (1.6 MiB) TX bytes:0 (0.0 B)
br15 Link encap:Ethernet HWaddr 5c:26:0a:fc:f1:14
inet addr:10.15.0.42 Bcast:10.15.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:2145 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:90090 (87.9 KiB)
eth0 Link encap:Ethernet HWaddr 5c:26:0a:fc:f1:14
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:12642 errors:0 dropped:0 overruns:0 frame:0
TX packets:2335 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2156262 (2.0 MiB) TX bytes:157324 (153.6 KiB)
Interrupt:36 Memory:da000000-da012800
eth1 Link encap:Ethernet HWaddr 5c:26:0a:fc:f1:14
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:8265 errors:0 dropped:8265 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1705617 (1.6 MiB) TX bytes:0 (0.0 B)
Interrupt:48 Memory:dc000000-dc012800
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:953 errors:0 dropped:0 overruns:0 frame:0
TX packets:953 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:85590 (83.5 KiB) TX bytes:85590 (83.5 KiB)
vnet0 Link encap:Ethernet HWaddr fe:54:00:b1:38:ef
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10 errors:0 dropped:0 overruns:0 frame:0
TX packets:6862 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:1256 (1.2 KiB) TX bytes:1565042 (1.4 MiB)
vnet1 Link encap:Ethernet HWaddr fe:54:00:21:25:28
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:13 errors:0 dropped:0 overruns:0 frame:0
TX packets:6865 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:1682 (1.6 KiB) TX bytes:1565804 (1.4 MiB)
vnet2 Link encap:Ethernet HWaddr fe:54:00:b9:70:1a
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10 errors:0 dropped:0 overruns:0 frame:0
TX packets:6861 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:1256 (1.2 KiB) TX bytes:1564978 (1.4 MiB)
vnet3 Link encap:Ethernet HWaddr fe:54:00:96:65:09
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10 errors:0 dropped:0 overruns:0 frame:0
TX packets:6857 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:1256 (1.2 KiB) TX bytes:1563662 (1.4 MiB)
vnet4 Link encap:Ethernet HWaddr fe:54:00:61:20:db
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:31 errors:0 dropped:0 overruns:0 frame:0
TX packets:6859 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:3230 (3.1 KiB) TX bytes:1564916 (1.4 MiB)
vnet5 Link encap:Ethernet HWaddr fe:54:00:c5:a4:fd
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:13 errors:0 dropped:0 overruns:0 frame:0
TX packets:6858 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:1682 (1.6 KiB) TX bytes:1564852 (1.4 MiB)
vnet6 Link encap:Ethernet HWaddr fe:54:00:d5:49:27
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:11 errors:0 dropped:0 overruns:0 frame:0
TX packets:6851 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:1342 (1.3 KiB) TX bytes:1563278 (1.4 MiB)
vnet7 Link encap:Ethernet HWaddr fe:54:00:7a:ce:76
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10 errors:0 dropped:0 overruns:0 frame:0
TX packets:6850 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:1256 (1.2 KiB) TX bytes:1562684 (1.4 MiB)
vnet8 Link encap:Ethernet HWaddr fe:54:00:df:51:95
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:11 errors:0 dropped:0 overruns:0 frame:0
TX packets:6851 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:1298 (1.2 KiB) TX bytes:1562744 (1.4 MiB)
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: bnx2 vlan issue
2011-03-17 14:51 bnx2 vlan issue Seblu
@ 2011-03-17 18:02 ` Seblu
2011-03-17 19:16 ` Jesse Gross
0 siblings, 1 reply; 13+ messages in thread
From: Seblu @ 2011-03-17 18:02 UTC (permalink / raw)
To: netdev
On Thu, Mar 17, 2011 at 3:51 PM, Seblu <seblu@seblu.net> wrote:
> Good Afternoon Gentleman,
>
> I've an issue with a 2.6.38 (vanilla) on a debian unstable distro. I
> attached an lspci and lshw about hardware. I also attached debian
> network config file.
>
> My host is a host kvm which run vm on different networks (vlan). I
> have 2 1Gbit/s card (eth0, eth1) and 1 10Gbit/s card (eth2).
> I use bonding (bond0) mode 1 on the 1Gbit/s cards.
>
> vlan 14 and 15 are only availlable trought 1G cards. Same tagging on
> both cards in switch. 14 is untagged (need for pxe) and 15 is tagged.
>
> Every network on my host is in a bridge. Eg:
> vlan 15 is in br15 by bond0.15 as member,
> vlan 14 is in br14 by bond0 as member,
> vlan 20 is in br20 by eth2.20
>
> The issue is simple, packets from vlan 15 which are tagged are not
> visible on bond0.15 but in bond0 (see capture). Like if there is no
> vlan.
>
>
> in dmesg in see something like : "8021q: adding VLAN 0 to HW filter on
> device bond0".
> Maybe there is something wrong with hardware filtering?
>
> I don't find a way to disable hw vlan filtering.
> # ethtool -K eth1 rxvlan off
> Cannot set device flag settings: Invalid argument
>
> I found a way to make thing work and don't work by one command.
> # rmmod bonding
> # ifdown br14
> # ifdown br15
> # ifup --force bond0
> # ifup --force bond0.15
> # ifup --force br15
> => i can ping my ip on 15 working
> if i make ifup --force br14, i lost connectivity on vlan 15.
>
> I don't have isssue when bond0 is not member of br14. So vlan on
> bonding seems to be broken.
>
I done more test this afternoon.
I set an ip on bond0, ip on bond0.15 is still pingeable.
I created a bridge. Until I don't add bond0 in my bridge, bond0.15 is
still pingeable.
Now is see a relation with a similar issue come with 2.6.37. This become
eth0 => network 1
eth0.42 => network 2
br0 => eth0 + eth1 (network1)
Since 2.6.37, eth0.42 (network2) become unavailable, and it is only
possible to do something like:
br0 => eth0 + eth1 (network1)
br0.42 => network 2
To conclude:
add a bonding interface in a bridge, kill vlan setted on it.
add a real interface in a bridge, kill vlan setted on it.
So, i don't see how we can restore a per bridge vlan. Why do you
remove this possibility in 2.6.37?
--
Sébastien Luttringer
www.seblu.net
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: bnx2 vlan issue
2011-03-17 18:02 ` Seblu
@ 2011-03-17 19:16 ` Jesse Gross
2011-03-17 23:22 ` Seblu
0 siblings, 1 reply; 13+ messages in thread
From: Jesse Gross @ 2011-03-17 19:16 UTC (permalink / raw)
To: Seblu; +Cc: netdev
On Thu, Mar 17, 2011 at 11:02 AM, Seblu <seblu@seblu.net> wrote:
> On Thu, Mar 17, 2011 at 3:51 PM, Seblu <seblu@seblu.net> wrote:
>> Good Afternoon Gentleman,
>>
>> I've an issue with a 2.6.38 (vanilla) on a debian unstable distro. I
>> attached an lspci and lshw about hardware. I also attached debian
>> network config file.
>>
>> My host is a host kvm which run vm on different networks (vlan). I
>> have 2 1Gbit/s card (eth0, eth1) and 1 10Gbit/s card (eth2).
>> I use bonding (bond0) mode 1 on the 1Gbit/s cards.
>>
>> vlan 14 and 15 are only availlable trought 1G cards. Same tagging on
>> both cards in switch. 14 is untagged (need for pxe) and 15 is tagged.
>>
>> Every network on my host is in a bridge. Eg:
>> vlan 15 is in br15 by bond0.15 as member,
>> vlan 14 is in br14 by bond0 as member,
>> vlan 20 is in br20 by eth2.20
>>
>> The issue is simple, packets from vlan 15 which are tagged are not
>> visible on bond0.15 but in bond0 (see capture). Like if there is no
>> vlan.
>>
>>
>> in dmesg in see something like : "8021q: adding VLAN 0 to HW filter on
>> device bond0".
>> Maybe there is something wrong with hardware filtering?
>>
>> I don't find a way to disable hw vlan filtering.
>> # ethtool -K eth1 rxvlan off
>> Cannot set device flag settings: Invalid argument
>>
>> I found a way to make thing work and don't work by one command.
>> # rmmod bonding
>> # ifdown br14
>> # ifdown br15
>> # ifup --force bond0
>> # ifup --force bond0.15
>> # ifup --force br15
>> => i can ping my ip on 15 working
>> if i make ifup --force br14, i lost connectivity on vlan 15.
>>
>> I don't have isssue when bond0 is not member of br14. So vlan on
>> bonding seems to be broken.
>>
> I done more test this afternoon.
>
> I set an ip on bond0, ip on bond0.15 is still pingeable.
> I created a bridge. Until I don't add bond0 in my bridge, bond0.15 is
> still pingeable.
>
>
>
> Now is see a relation with a similar issue come with 2.6.37. This become
> eth0 => network 1
> eth0.42 => network 2
> br0 => eth0 + eth1 (network1)
>
> Since 2.6.37, eth0.42 (network2) become unavailable, and it is only
> possible to do something like:
> br0 => eth0 + eth1 (network1)
> br0.42 => network 2
>
> To conclude:
> add a bonding interface in a bridge, kill vlan setted on it.
> add a real interface in a bridge, kill vlan setted on it.
>
> So, i don't see how we can restore a per bridge vlan. Why do you
> remove this possibility in 2.6.37?
It was a bug that it worked at all and whether it worked depended on
the hardware/firmware/driver. If an interface is attached to a
bridge, the bridge takes all the packets received on that interface,
including vlan packets.
There are a few ways to setup vlans and bridging that work on all
kernels and with all NICs:
* vlans on interface, bridges contain vlan devices. This gives you a
bridge for each vlan.
* bridge on interface, vlans on bridge device. This gives you a
bridge with all packets and vlan devices can give you specific vlans.
* Use ebtables rules in the bridge to accept/reject certain packets as desired.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: bnx2 vlan issue
2011-03-17 19:16 ` Jesse Gross
@ 2011-03-17 23:22 ` Seblu
2011-03-22 2:05 ` Jesse Gross
0 siblings, 1 reply; 13+ messages in thread
From: Seblu @ 2011-03-17 23:22 UTC (permalink / raw)
To: Jesse Gross; +Cc: netdev
On Thu, Mar 17, 2011 at 8:16 PM, Jesse Gross <jesse@nicira.com> wrote:
> On Thu, Mar 17, 2011 at 11:02 AM, Seblu <seblu@seblu.net> wrote:
>> On Thu, Mar 17, 2011 at 3:51 PM, Seblu <seblu@seblu.net> wrote:
>
> It was a bug that it worked at all and whether it worked depended on
> the hardware/firmware/driver. If an interface is attached to a
> bridge, the bridge takes all the packets received on that interface,
> including vlan packets.
ok i see.
>
> There are a few ways to setup vlans and bridging that work on all
> kernels and with all NICs:
>
> * vlans on interface, bridges contain vlan devices. This gives you a
> bridge for each vlan.
Except for untagged isn't it? This is why i fail. I need to have a
bridge with the untagged vlan from an interface.
Before 2.6.37 (with most of drivers/firmware/hardware i use) when a
vlan is defined on an interface, for example eth0, eth0.15 show vlan15
frames and eth0 show untagged frames.
I've tryed eth0.0, expecting to have untagged vlan, but this doesnt work.
How can I create a bridge with the untagged vlan from an interface?
> * bridge on interface, vlans on bridge device. This gives you a
> bridge with all packets and vlan devices can give you specific vlans.
I cannot use this schema, i used bridge to bring together vnet
interface and vlan interface.
> * Use ebtables rules in the bridge to accept/reject certain packets as desired.
I don't see how use ebtables to push untagged frame to a dedicated
iface which can be added in a bridge.
--
Sébastien Luttringer
www.seblu.net
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: bnx2 vlan issue
2011-03-17 23:22 ` Seblu
@ 2011-03-22 2:05 ` Jesse Gross
2011-03-22 10:59 ` Seblu
0 siblings, 1 reply; 13+ messages in thread
From: Jesse Gross @ 2011-03-22 2:05 UTC (permalink / raw)
To: Seblu; +Cc: netdev
On Thu, Mar 17, 2011 at 4:22 PM, Seblu <seblu@seblu.net> wrote:
> On Thu, Mar 17, 2011 at 8:16 PM, Jesse Gross <jesse@nicira.com> wrote:
>> On Thu, Mar 17, 2011 at 11:02 AM, Seblu <seblu@seblu.net> wrote:
>>> On Thu, Mar 17, 2011 at 3:51 PM, Seblu <seblu@seblu.net> wrote:
>>
>> It was a bug that it worked at all and whether it worked depended on
>> the hardware/firmware/driver. If an interface is attached to a
>> bridge, the bridge takes all the packets received on that interface,
>> including vlan packets.
> ok i see.
>
>>
>> There are a few ways to setup vlans and bridging that work on all
>> kernels and with all NICs:
>>
>> * vlans on interface, bridges contain vlan devices. This gives you a
>> bridge for each vlan.
> Except for untagged isn't it? This is why i fail. I need to have a
> bridge with the untagged vlan from an interface.
> Before 2.6.37 (with most of drivers/firmware/hardware i use) when a
> vlan is defined on an interface, for example eth0, eth0.15 show vlan15
> frames and eth0 show untagged frames.
>
> I've tryed eth0.0, expecting to have untagged vlan, but this doesnt work.
eth0.0 will get packets that have a vlan tag with vid 0, some people
use it as just another vlan.
> How can I create a bridge with the untagged vlan from an interface?
>
>> * bridge on interface, vlans on bridge device. This gives you a
>> bridge with all packets and vlan devices can give you specific vlans.
> I cannot use this schema, i used bridge to bring together vnet
> interface and vlan interface.
I'm not sure I understand why you say you can't use this. You can
combine vlans and bridging pretty much arbitrarily, including stacking
multiple layers.
>
>> * Use ebtables rules in the bridge to accept/reject certain packets as desired.
> I don't see how use ebtables to push untagged frame to a dedicated
> iface which can be added in a bridge.
You could have a bridge on the raw interface and connect all of the
VMs that need untagged traffic. If you add an ebtables rule to reject
tagged traffic then vlan devices on the interface will continue to
work as before.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: bnx2 vlan issue
2011-03-22 2:05 ` Jesse Gross
@ 2011-03-22 10:59 ` Seblu
2011-03-22 23:19 ` Jesse Gross
0 siblings, 1 reply; 13+ messages in thread
From: Seblu @ 2011-03-22 10:59 UTC (permalink / raw)
To: Jesse Gross; +Cc: netdev
On Tue, Mar 22, 2011 at 3:05 AM, Jesse Gross <jesse@nicira.com> wrote:
> On Thu, Mar 17, 2011 at 4:22 PM, Seblu <seblu@seblu.net> wrote:
>> On Thu, Mar 17, 2011 at 8:16 PM, Jesse Gross <jesse@nicira.com> wrote:
>>> On Thu, Mar 17, 2011 at 11:02 AM, Seblu <seblu@seblu.net> wrote:
>>>> On Thu, Mar 17, 2011 at 3:51 PM, Seblu <seblu@seblu.net> wrote:
>> How can I create a bridge with the untagged vlan from an interface?
>>
>>> * bridge on interface, vlans on bridge device. This gives you a
>>> bridge with all packets and vlan devices can give you specific vlans.
>> I cannot use this schema, i used bridge to bring together vnet
>> interface and vlan interface.
>
> I'm not sure I understand why you say you can't use this. You can
> combine vlans and bridging pretty much arbitrarily, including stacking
> multiple layers.
I don't see _how I can bridge an interface with an untagged vlan from
another interface_.
I little example is maybe more clear:
My dekstop have 2 NIC (eth0, eth1). I receive from network admin 2
vlans. 20 untag and 21 tagged. My laptop is plugged to eth1.
I want "export" untagged vlan 20 to eth1.
Before 2.6.37, i do something like br0 = (eth0 + eth1). I put an ip on
br0 and on eth0.21. And br0 just have untagged frame from eth0 which
was transmitted to eth1. eth0.21 have only tagged frame from vlan 21.
eth1 did not receive tagged vlan 21.
After 2.6.37, i can do a bridge like before (br0 = eth0 + eth1) but i
must use br0.21 to have access to vlan 21 network in my desktop. But,
my laptop can also access to tagged vlan 21, and i don't want this.
A lot of old xen based setup use this behaviour.
About my kvm test, I'm looking to the pci passtrough and macvtap, but
this requires configuration that supports it.
Why cannot have a eth0.U with only untagged frames?
>
>>
>>> * Use ebtables rules in the bridge to accept/reject certain packets as desired.
>> I don't see how use ebtables to push untagged frame to a dedicated
>> iface which can be added in a bridge.
>
> You could have a bridge on the raw interface and connect all of the
> VMs that need untagged traffic. If you add an ebtables rule to reject
> tagged traffic then vlan devices on the interface will continue to
> work as before.
>
If I ignores the fact that the name of the card is not fixed, i see.
But performance will follow? I don't believe this kind of config will
allow ~7/8Gbit/s of traffic.
Traversing ebtables rules is not free. And starting filtering traffic
is a really different job than just bridge cards together.
Regards,
--
Sébastien Luttringer
www.seblu.net
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: bnx2 vlan issue
2011-03-22 10:59 ` Seblu
@ 2011-03-22 23:19 ` Jesse Gross
2011-03-24 12:58 ` Seblu
0 siblings, 1 reply; 13+ messages in thread
From: Jesse Gross @ 2011-03-22 23:19 UTC (permalink / raw)
To: Seblu; +Cc: netdev
On Tue, Mar 22, 2011 at 3:59 AM, Seblu <seblu@seblu.net> wrote:
> On Tue, Mar 22, 2011 at 3:05 AM, Jesse Gross <jesse@nicira.com> wrote:
>> On Thu, Mar 17, 2011 at 4:22 PM, Seblu <seblu@seblu.net> wrote:
>>> On Thu, Mar 17, 2011 at 8:16 PM, Jesse Gross <jesse@nicira.com> wrote:
>>>> On Thu, Mar 17, 2011 at 11:02 AM, Seblu <seblu@seblu.net> wrote:
>>>>> On Thu, Mar 17, 2011 at 3:51 PM, Seblu <seblu@seblu.net> wrote:
>>> How can I create a bridge with the untagged vlan from an interface?
>>>
>>>> * bridge on interface, vlans on bridge device. This gives you a
>>>> bridge with all packets and vlan devices can give you specific vlans.
>>> I cannot use this schema, i used bridge to bring together vnet
>>> interface and vlan interface.
>>
>> I'm not sure I understand why you say you can't use this. You can
>> combine vlans and bridging pretty much arbitrarily, including stacking
>> multiple layers.
> I don't see _how I can bridge an interface with an untagged vlan from
> another interface_.
>
> I little example is maybe more clear:
> My dekstop have 2 NIC (eth0, eth1). I receive from network admin 2
> vlans. 20 untag and 21 tagged. My laptop is plugged to eth1.
> I want "export" untagged vlan 20 to eth1.
> Before 2.6.37, i do something like br0 = (eth0 + eth1). I put an ip on
> br0 and on eth0.21. And br0 just have untagged frame from eth0 which
> was transmitted to eth1. eth0.21 have only tagged frame from vlan 21.
> eth1 did not receive tagged vlan 21.
> After 2.6.37, i can do a bridge like before (br0 = eth0 + eth1) but i
> must use br0.21 to have access to vlan 21 network in my desktop. But,
> my laptop can also access to tagged vlan 21, and i don't want this.
>
> A lot of old xen based setup use this behaviour.
> About my kvm test, I'm looking to the pci passtrough and macvtap, but
> this requires configuration that supports it.
> Why cannot have a eth0.U with only untagged frames?
>
>>
>>>
>>>> * Use ebtables rules in the bridge to accept/reject certain packets as desired.
>>> I don't see how use ebtables to push untagged frame to a dedicated
>>> iface which can be added in a bridge.
>>
>> You could have a bridge on the raw interface and connect all of the
>> VMs that need untagged traffic. If you add an ebtables rule to reject
>> tagged traffic then vlan devices on the interface will continue to
>> work as before.
>>
> If I ignores the fact that the name of the card is not fixed, i see.
> But performance will follow? I don't believe this kind of config will
> allow ~7/8Gbit/s of traffic.
> Traversing ebtables rules is not free. And starting filtering traffic
> is a really different job than just bridge cards together.
I don't necessarily disagree that there should be a better way to do
this, though as of the moment the above is probably your best bet.
To me, the most important thing is to have consistent behavior across
different cards. In 2.6.37 that behavior was standardized on the way
non-accelerated NICs used to do but the other way is more common and
perhaps better. Eric B. posted a patch yesterday that better unifies
the code paths. This would be the first step to such a change because
it would make it easier to move the handling logic for both at the
same time.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: bnx2 vlan issue
2011-03-22 23:19 ` Jesse Gross
@ 2011-03-24 12:58 ` Seblu
2011-03-24 19:55 ` Jesse Gross
0 siblings, 1 reply; 13+ messages in thread
From: Seblu @ 2011-03-24 12:58 UTC (permalink / raw)
To: Jesse Gross; +Cc: netdev
On Wed, Mar 23, 2011 at 12:19 AM, Jesse Gross <jesse@nicira.com> wrote:
> On Tue, Mar 22, 2011 at 3:59 AM, Seblu <seblu@seblu.net> wrote:
>> On Tue, Mar 22, 2011 at 3:05 AM, Jesse Gross <jesse@nicira.com> wrote:
>>> On Thu, Mar 17, 2011 at 4:22 PM, Seblu <seblu@seblu.net> wrote:
>>>> On Thu, Mar 17, 2011 at 8:16 PM, Jesse Gross <jesse@nicira.com> wrote:
>>>>> On Thu, Mar 17, 2011 at 11:02 AM, Seblu <seblu@seblu.net> wrote:
>>>>>> On Thu, Mar 17, 2011 at 3:51 PM, Seblu <seblu@seblu.net> wrote:
>>>> How can I create a bridge with the untagged vlan from an interface?
>>>>
>>>>> * bridge on interface, vlans on bridge device. This gives you a
>>>>> bridge with all packets and vlan devices can give you specific vlans.
>>>> I cannot use this schema, i used bridge to bring together vnet
>>>> interface and vlan interface.
>>>
>>> I'm not sure I understand why you say you can't use this. You can
>>> combine vlans and bridging pretty much arbitrarily, including stacking
>>> multiple layers.
>> I don't see _how I can bridge an interface with an untagged vlan from
>> another interface_.
>>
>> I little example is maybe more clear:
>> My dekstop have 2 NIC (eth0, eth1). I receive from network admin 2
>> vlans. 20 untag and 21 tagged. My laptop is plugged to eth1.
>> I want "export" untagged vlan 20 to eth1.
>> Before 2.6.37, i do something like br0 = (eth0 + eth1). I put an ip on
>> br0 and on eth0.21. And br0 just have untagged frame from eth0 which
>> was transmitted to eth1. eth0.21 have only tagged frame from vlan 21.
>> eth1 did not receive tagged vlan 21.
>> After 2.6.37, i can do a bridge like before (br0 = eth0 + eth1) but i
>> must use br0.21 to have access to vlan 21 network in my desktop. But,
>> my laptop can also access to tagged vlan 21, and i don't want this.
>>
>> A lot of old xen based setup use this behaviour.
>> About my kvm test, I'm looking to the pci passtrough and macvtap, but
>> this requires configuration that supports it.
>> Why cannot have a eth0.U with only untagged frames?
>>
>>>
>>>>
>>>>> * Use ebtables rules in the bridge to accept/reject certain packets as desired.
>>>> I don't see how use ebtables to push untagged frame to a dedicated
>>>> iface which can be added in a bridge.
>>>
>>> You could have a bridge on the raw interface and connect all of the
>>> VMs that need untagged traffic. If you add an ebtables rule to reject
>>> tagged traffic then vlan devices on the interface will continue to
>>> work as before.
>>>
>> If I ignores the fact that the name of the card is not fixed, i see.
>> But performance will follow? I don't believe this kind of config will
>> allow ~7/8Gbit/s of traffic.
>> Traversing ebtables rules is not free. And starting filtering traffic
>> is a really different job than just bridge cards together.
>
> I don't necessarily disagree that there should be a better way to do
> this, though as of the moment the above is probably your best bet.
>
> To me, the most important thing is to have consistent behavior across
> different cards.
Speaking of that, i've tryed 2.6.38 on my station (dell opitplex 980)
to use the new bridging schema and it doesn't work.
Exactly the case previously described: ip on br0 (eth0+eth1) and ip on
br0.42. eth0 driver is e1000e and eth1 is tg3. br0.42 don't receive
traffic.
I have to open a bug report?
> In 2.6.37 that behavior was standardized on the way
> non-accelerated NICs used to do but the other way is more common and
> perhaps better. Eric B. posted a patch yesterday that better unifies
> the code paths. This would be the first step to such a change because
> it would make it easier to move the handling logic for both at the
> same time.
Agree it's going in the right direction, but it's sad that breaks
basic network concept. Therefore hope in future versions.
Regards,
--
Sébastien Luttringer
www.seblu.net
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: bnx2 vlan issue
2011-03-24 12:58 ` Seblu
@ 2011-03-24 19:55 ` Jesse Gross
2011-03-25 0:26 ` Seblu
0 siblings, 1 reply; 13+ messages in thread
From: Jesse Gross @ 2011-03-24 19:55 UTC (permalink / raw)
To: Seblu; +Cc: netdev
On Thu, Mar 24, 2011 at 5:58 AM, Seblu <seblu@seblu.net> wrote:
>> I don't necessarily disagree that there should be a better way to do
>> this, though as of the moment the above is probably your best bet.
>>
>> To me, the most important thing is to have consistent behavior across
>> different cards.
>
> Speaking of that, i've tryed 2.6.38 on my station (dell opitplex 980)
> to use the new bridging schema and it doesn't work.
> Exactly the case previously described: ip on br0 (eth0+eth1) and ip on
> br0.42. eth0 driver is e1000e and eth1 is tg3. br0.42 don't receive
> traffic.
> I have to open a bug report?
The change was deliberate, not an accidental mistake, so don't expect
2.6.38 to suddenly switch back to the previous behavior. There's no
need to file a bug report - the new behavior is known (I was the one
who changed it in the first place). I will look into nicer semantics
in the future.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: bnx2 vlan issue
2011-03-24 19:55 ` Jesse Gross
@ 2011-03-25 0:26 ` Seblu
2011-04-02 2:01 ` Jesse Gross
0 siblings, 1 reply; 13+ messages in thread
From: Seblu @ 2011-03-25 0:26 UTC (permalink / raw)
To: Jesse Gross; +Cc: netdev
On Thu, Mar 24, 2011 at 8:55 PM, Jesse Gross <jesse@nicira.com> wrote:
> On Thu, Mar 24, 2011 at 5:58 AM, Seblu <seblu@seblu.net> wrote:
>>> I don't necessarily disagree that there should be a better way to do
>>> this, though as of the moment the above is probably your best bet.
>>>
>>> To me, the most important thing is to have consistent behavior across
>>> different cards.
>>
>> Speaking of that, i've tryed 2.6.38 on my station (dell opitplex 980)
>> to use the new bridging schema and it doesn't work.
>> Exactly the case previously described: ip on br0 (eth0+eth1) and ip on
>> br0.42. eth0 driver is e1000e and eth1 is tg3. br0.42 don't receive
>> traffic.
>> I have to open a bug report?
>
> The change was deliberate, not an accidental mistake, so don't expect
> 2.6.38 to suddenly switch back to the previous behavior. There's no
> need to file a bug report - the new behavior is known (I was the one
> who changed it in the first place). I will look into nicer semantics
> in the future.
>
Maybe i was not enough clear. It seems to me that new behaviour, with
vlan on top of bridge rather than above interface in bridge is not
functional.
In other words, i cannot use vlan and bridge together in 2.6.38 (with e1000e).
I understand hard works are in progress and old behaviour will maybe
disapear forever. Here i just don't use vlan and bridge like you
suggest me in your previous post.
--
Sébastien Luttringer
www.seblu.net
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: bnx2 vlan issue
2011-03-25 0:26 ` Seblu
@ 2011-04-02 2:01 ` Jesse Gross
2011-06-17 6:10 ` Dominique Martinet
0 siblings, 1 reply; 13+ messages in thread
From: Jesse Gross @ 2011-04-02 2:01 UTC (permalink / raw)
To: Seblu; +Cc: netdev
On Thu, Mar 24, 2011 at 5:26 PM, Seblu <seblu@seblu.net> wrote:
> On Thu, Mar 24, 2011 at 8:55 PM, Jesse Gross <jesse@nicira.com> wrote:
>> On Thu, Mar 24, 2011 at 5:58 AM, Seblu <seblu@seblu.net> wrote:
>>>> I don't necessarily disagree that there should be a better way to do
>>>> this, though as of the moment the above is probably your best bet.
>>>>
>>>> To me, the most important thing is to have consistent behavior across
>>>> different cards.
>>>
>>> Speaking of that, i've tryed 2.6.38 on my station (dell opitplex 980)
>>> to use the new bridging schema and it doesn't work.
>>> Exactly the case previously described: ip on br0 (eth0+eth1) and ip on
>>> br0.42. eth0 driver is e1000e and eth1 is tg3. br0.42 don't receive
>>> traffic.
>>> I have to open a bug report?
>>
>> The change was deliberate, not an accidental mistake, so don't expect
>> 2.6.38 to suddenly switch back to the previous behavior. There's no
>> need to file a bug report - the new behavior is known (I was the one
>> who changed it in the first place). I will look into nicer semantics
>> in the future.
>>
> Maybe i was not enough clear. It seems to me that new behaviour, with
> vlan on top of bridge rather than above interface in bridge is not
> functional.
> In other words, i cannot use vlan and bridge together in 2.6.38 (with e1000e).
Sorry, I misunderstood what you were saying before. Can you try and
see where the packets are getting lost or improperly handled by
running tcpdump on the various interfaces? For example, check that
packets are coming in with tags on the physical interfaces, have tags
on the bridge interface, no tag on the vlan interface, etc.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: bnx2 vlan issue
2011-04-02 2:01 ` Jesse Gross
@ 2011-06-17 6:10 ` Dominique Martinet
2011-06-17 16:47 ` Jesse Gross
0 siblings, 1 reply; 13+ messages in thread
From: Dominique Martinet @ 2011-06-17 6:10 UTC (permalink / raw)
To: netdev
Hi,
Jesse Gross <jesse <at> nicira.com> writes:
> On Thu, Mar 24, 2011 at 5:26 PM, Seblu <seblu <at> seblu.net> wrote:
> > Maybe i was not enough clear. It seems to me that new behaviour, with
> > vlan on top of bridge rather than above interface in bridge is not
> > functional.
> > In other words, i cannot use vlan and bridge together in 2.6.38 (with
> > e1000e).
>
> Sorry, I misunderstood what you were saying before. Can you try and
> see where the packets are getting lost or improperly handled by
> running tcpdump on the various interfaces? For example, check that
> packets are coming in with tags on the physical interfaces, have tags
> on the bridge interface, no tag on the vlan interface, etc.
I think I ran into the same problem, and my workaround for this was to add
a vlan do the bridge and then add the vlan'ed bridge to another bridge, i.e.
(since I can't draw, commands will be better :P)
brctl addbr br0
brctl addif br0 eth0
ip link add link br0 name br0.42 type vlan id 42
ip link set br0.42 up
brctl addbr br_42
brctl addif br_42 br0.42
and then I could put VMs in br_42 which got network "as expected"
before, I used to have br_42 with eth0.42 in it, so it is just one more
step..
What bothers me is that I also want to put VMs in br0, and it does work,
but this bridge also sees all the tagged data - isn't there a way to just
"pick" the untagged network?
My other question is that I'm not certain if that's the expected way to
use the new behaviour, if not I wouldn't mind light shining from above :)
This is enough for me, though I can't say I like the change I can't argue
that having everything behave the same way is better, but I'm still
curious...
Regards,
Dominique Martinet | Asmadeus
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: bnx2 vlan issue
2011-06-17 6:10 ` Dominique Martinet
@ 2011-06-17 16:47 ` Jesse Gross
0 siblings, 0 replies; 13+ messages in thread
From: Jesse Gross @ 2011-06-17 16:47 UTC (permalink / raw)
To: Dominique Martinet; +Cc: netdev
On Thu, Jun 16, 2011 at 11:10 PM, Dominique Martinet
<rnfhrznznaq.tf@noclue.notk.org> wrote:
> Hi,
>
> Jesse Gross <jesse <at> nicira.com> writes:
>> On Thu, Mar 24, 2011 at 5:26 PM, Seblu <seblu <at> seblu.net> wrote:
>> > Maybe i was not enough clear. It seems to me that new behaviour, with
>> > vlan on top of bridge rather than above interface in bridge is not
>> > functional.
>> > In other words, i cannot use vlan and bridge together in 2.6.38 (with
>> > e1000e).
>>
>> Sorry, I misunderstood what you were saying before. Can you try and
>> see where the packets are getting lost or improperly handled by
>> running tcpdump on the various interfaces? For example, check that
>> packets are coming in with tags on the physical interfaces, have tags
>> on the bridge interface, no tag on the vlan interface, etc.
>
> I think I ran into the same problem, and my workaround for this was to add
> a vlan do the bridge and then add the vlan'ed bridge to another bridge, i.e.
> (since I can't draw, commands will be better :P)
>
> brctl addbr br0
> brctl addif br0 eth0
> ip link add link br0 name br0.42 type vlan id 42
> ip link set br0.42 up
>
> brctl addbr br_42
> brctl addif br_42 br0.42
>
> and then I could put VMs in br_42 which got network "as expected"
> before, I used to have br_42 with eth0.42 in it, so it is just one more
> step..
> What bothers me is that I also want to put VMs in br0, and it does work,
> but this bridge also sees all the tagged data - isn't there a way to just
> "pick" the untagged network?
You are bridging the VMs to the physical network, so it is expected
that they will see all traffic. That said, you could use ebtables to
only take vlan 0, similar to if you only wanted them to see packets to
their MAC address and not flooding.
> My other question is that I'm not certain if that's the expected way to
> use the new behaviour, if not I wouldn't mind light shining from above :)
Yes, that's the intended behavior and correct usage.
^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2011-06-17 16:47 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-03-17 14:51 bnx2 vlan issue Seblu
2011-03-17 18:02 ` Seblu
2011-03-17 19:16 ` Jesse Gross
2011-03-17 23:22 ` Seblu
2011-03-22 2:05 ` Jesse Gross
2011-03-22 10:59 ` Seblu
2011-03-22 23:19 ` Jesse Gross
2011-03-24 12:58 ` Seblu
2011-03-24 19:55 ` Jesse Gross
2011-03-25 0:26 ` Seblu
2011-04-02 2:01 ` Jesse Gross
2011-06-17 6:10 ` Dominique Martinet
2011-06-17 16:47 ` Jesse Gross
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).