Bug#607114: Same error on second server
I got similar messages some days ago on different hardware (see attached
file).
Both servers are
- running the same version of kernel and Debian
- inter-connected with two Ethernet cross-cables in bond
(balance-rr) with bridge and two vlans with MTU 9000 on top of it
- totally different on hardware
- server1 is Xeon 3210 based with all Intel Ethernet cards
- server2 is Opteron 2431 based with Broadcom Ethernet cards
--
Peter Viskup
Dec 5 23:10:31 server1 kernel: [350429.816318] BUG: unable to handle kernel paging request at 00000000004817f0
Dec 5 23:10:31 server1 kernel: [350429.816356] IP: [<ffffffffa01e5101>] :8021q:__vlan_find_group+0x25/0x36
Dec 5 23:10:31 server1 kernel: [350429.816390] PGD 11cbf067 PUD 1ebb5067 PMD 11cfc067 PTE 0
Dec 5 23:10:31 server1 kernel: [350429.816429] Oops: 0000 [1] SMP
Dec 5 23:10:31 server1 kernel: [350429.816479] CPU 0
Dec 5 23:10:31 server1 kernel: [350429.816522] Modules linked in: xt_physdev ipt_MASQUERADE ipt_LOG xt_state iptable_mangle xt_tcpudp iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack iptable_filter ip_tables x_tables bridge ipv6 dm_crypt crypto_blkcipher 8021q coretemp ipmi_poweroff ipmi_watchdog ipmi_si ipmi_devintf ipmi_msghandler bonding loop serio_raw psmouse i2c_i801 pcspkr i2c_core button shpchp pci_hotplug evdev ext3 jbd mbcache dm_mirror dm_log dm_snapshot dm_mod raid1 md_mod sd_mod floppy ahci libata scsi_mod dock e1000 ehci_hcd uhci_hcd e1000e thermal processor fan thermal_sys [last unloaded: scsi_wait_scan]
Dec 5 23:10:31 server1 kernel: [350429.817142] Pid: 7066, comm: vconfig Not tainted 2.6.26-2-xen-amd64 #1
Dec 5 23:10:31 server1 kernel: [350429.817197] RIP: e030:[<ffffffffa01e5101>] [<ffffffffa01e5101>] :8021q:__vlan_find_group+0x25/0x36
Dec 5 23:10:31 server1 kernel: [350429.817292] RSP: e02b:ffff880011de3e10 EFLAGS: 00010206
Dec 5 23:10:31 server1 kernel: [350429.817343] RAX: ffff88001ed4c4c0 RBX: 000000000000000a RCX: 000000000000000a
Dec 5 23:10:31 server1 kernel: [350429.817427] RDX: 0000000000481800 RSI: 000000000000000a RDI: ffff88001d896000
Dec 5 23:10:31 server1 kernel: [350429.817510] RBP: 00000000ffffffde R08: 00007f31b6a02440 R09: 0000000000000000
Dec 5 23:10:31 server1 kernel: [350429.817594] R10: 0000000000000000 R11: ffffffff802e3c42 R12: ffff88001ded76a0
Dec 5 23:10:31 server1 kernel: [350429.817677] R13: ffff88001d896000 R14: 000000000000000a R15: 00007fffffffeec1
Dec 5 23:10:31 server1 kernel: [350429.817762] FS: 00007f31b6e5d6e0(0000) GS:ffffffff8053a000(0000) knlGS:0000000000000000
Dec 5 23:10:31 server1 kernel: [350429.817849] CS: e033 DS: 0000 ES: 0000
Dec 5 23:10:31 server1 kernel: [350429.817895] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Dec 5 23:10:31 server1 kernel: [350429.817979] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Dec 5 23:10:31 server1 kernel: [350429.818063] Process vconfig (pid: 7066, threadinfo ffff880011de2000, task ffff88001da65100)
Dec 5 23:10:31 server1 kernel: [350429.818150] Stack: ffffffffa01e511a 000000000000000a ffffffffa01e51c9 00000000ffffffbf
Dec 5 23:10:31 server1 kernel: [350429.818253] ffffffffa01e5a36 646e6f6200000000 0000000000000031 0000000000000000
Dec 5 23:10:31 server1 kernel: [350429.818351] 0000000a00000000 0000000000000000 0000000000000000 0000000000000000
Dec 5 23:10:31 server1 kernel: [350429.818418] Call Trace:
Dec 5 23:10:31 server1 kernel: [350429.818493] [<ffffffffa01e511a>] ? :8021q:__find_vlan_dev+0x8/0x36
Dec 5 23:10:31 server1 kernel: [350429.818550] [<ffffffffa01e51c9>] ? :8021q:vlan_check_real_dev+0x81/0x8e
Dec 5 23:10:31 server1 kernel: [350429.818608] [<ffffffffa01e5a36>] ? :8021q:vlan_ioctl_handler+0x1c9/0x363
Dec 5 23:10:31 server1 kernel: [350429.818669] [<ffffffff80276818>] ? handle_mm_fault+0x5f8/0xc46
Dec 5 23:10:31 server1 kernel: [350429.818724] [<ffffffff803bde80>] ? sk_prot_alloc+0x46/0xa4
Dec 5 23:10:31 server1 kernel: [350429.818778] [<ffffffff803baef5>] ? sock_ioctl+0x171/0x1f8
Dec 5 23:10:31 server1 kernel: [350429.818831] [<ffffffff802968b5>] ? vfs_ioctl+0x21/0x6b
Dec 5 23:10:31 server1 kernel: [350429.818883] [<ffffffff80296b47>] ? do_vfs_ioctl+0x248/0x261
Dec 5 23:10:31 server1 kernel: [350429.818937] [<ffffffff80296bb1>] ? sys_ioctl+0x51/0x70
Dec 5 23:10:31 server1 kernel: [350429.818990] [<ffffffff8020b528>] ? system_call+0x68/0x6d
Dec 5 23:10:31 server1 kernel: [350429.819043] [<ffffffff8020b4c0>] ? system_call+0x0/0x6d
Dec 5 23:10:31 server1 kernel: [350429.819095]
Dec 5 23:10:31 server1 kernel: [350429.819132]
Dec 5 23:10:31 server1 kernel: [350429.819169] Code: 89 e8 5d 41 5c c3 8b 97 80 00 00 00 89 d0 c1 e8 05 31 d0 83 e0 1f 48 8b 14 c5 a0 aa 1e a0 eb 03 48 8b 12 48 85 d2 75 03 31 c0 c3 <48> 39 7a f0 48 8b 02 0f 18 08 48 8d 42 f0 75 e5 c3 53 89 f3 e8
Dec 5 23:10:31 server1 kernel: [350429.819220] RIP [<ffffffffa01e5101>] :8021q:__vlan_find_group+0x25/0x36
Dec 5 23:10:31 server1 kernel: [350429.819220] RSP <ffff880011de3e10>
Dec 5 23:10:31 server1 kernel: [350429.819220] CR2: 00000000004817f0
Dec 5 23:10:31 server1 kernel: [350429.820373] ---[ end trace 2455feeb7fc5a643 ]---
Reply to: