Quesion about pve-kernel-2.6.32-18-pve

nx650

Member
Dec 9, 2012
3
0
21
Hallo,

after upgrading to pve-kernel-2.6.32-18-pve i have
a warning in syslog. Now, i need some help.
Should i ignore this warning and use kernel 18-pve ?
At the moment i decide to use the pve-kernel-2.6.32-17-pve without this
warning.

Best regards
Ralf

Code:
pve-manager: 2.3-7 (pve-manager/2.3/1fe64d18)
running kernel: 2.6.32-17-pve
proxmox-ve-2.6.32: 2.3-88
pve-kernel-2.6.32-16-pve: 2.6.32-82
pve-kernel-2.6.32-18-pve: 2.6.32-88
pve-kernel-2.6.32-17-pve: 2.6.32-83
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-36
qemu-server: 2.3-8
pve-firmware: 1.0-21
libpve-common-perl: 1.0-44
libpve-access-control: 1.0-25
libpve-storage-perl: 2.3-2
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.3-18
ksm-control-daemon: 1.1-1
Code:
syslog
Feb  4 19:26:32 proxmox kernel: ------------[ cut here ]------------
Feb  4 19:26:32 proxmox kernel: WARNING: at drivers/pci/intel-iommu.c:2775 intel_unmap_page+0x15f/0x180() (Not tainted)
Feb  4 19:26:32 proxmox kernel: Hardware name: MS-7750
Feb  4 19:26:32 proxmox kernel: Driver unmaps unmatched page at PFN 0
Feb  4 19:26:32 proxmox kernel: Modules linked in: bonding ipv6 8021q garp xhci_hcd shpchp tpm_tis tpm i2c_i801 i2c_core video output serio_raw wmi tpm_bios snd_pcsp snd_pcm snd_timer snd soundcore snd_page_alloc ext4 mbcache jbd2 ata_generic pata_acpi r8169 mii ata_piix bnx2 ahci [last unloaded: scsi_wait_scan]
Feb  4 19:26:32 proxmox kernel: Pid: 0, comm: swapper veid: 0 Not tainted 2.6.32-18-pve #1
Feb  4 19:26:32 proxmox kernel: Call Trace:
Feb  4 19:26:32 proxmox kernel: <IRQ>  [<ffffffff8106d228>] ? warn_slowpath_common+0x88/0xc0
Feb  4 19:26:32 proxmox kernel: [<ffffffff8106d316>] ? warn_slowpath_fmt+0x46/0x50
Feb  4 19:26:32 proxmox kernel: [<ffffffff812a6cdb>] ? find_iova+0x5b/0x90
Feb  4 19:26:32 proxmox kernel: [<ffffffff812aaf1f>] ? intel_unmap_page+0x15f/0x180
Feb  4 19:26:32 proxmox kernel: [<ffffffffa001ea65>] ? bnx2_poll_work+0x155/0x11d0 [bnx2]
Feb  4 19:26:32 proxmox kernel: [<ffffffff8101c54a>] ? intel_pmu_enable_all+0xba/0x160
Feb  4 19:26:32 proxmox kernel: [<ffffffff810efcbe>] ? rcu_start_gp+0x1be/0x230
Feb  4 19:26:32 proxmox kernel: [<ffffffff810efdf1>] ? cpu_quiet_msk+0xc1/0x130
Feb  4 19:26:32 proxmox kernel: [<ffffffff81012a49>] ? read_tsc+0x9/0x20
Feb  4 19:26:32 proxmox kernel: [<ffffffff8102b32d>] ? lapic_next_event+0x1d/0x30
Feb  4 19:26:32 proxmox kernel: [<ffffffffa001fc24>] ? bnx2_poll+0x74/0x310 [bnx2]
Feb  4 19:26:32 proxmox kernel: [<ffffffff810308a7>] ? native_apic_msr_write+0x37/0x40
Feb  4 19:26:32 proxmox kernel: [<ffffffff810a5314>] ? clockevents_program_event+0x54/0xa0
Feb  4 19:26:32 proxmox kernel: [<ffffffff81457aa3>] ? net_rx_action+0x103/0x2e0
Feb  4 19:26:32 proxmox kernel: [<ffffffff8109bae5>] ? __hrtimer_start_range_ns+0x1a5/0x480
Feb  4 19:26:32 proxmox kernel: [<ffffffff81076063>] ? __do_softirq+0x103/0x260
Feb  4 19:26:32 proxmox kernel: [<ffffffff8100c2ac>] ? call_softirq+0x1c/0x30
Feb  4 19:26:32 proxmox kernel: [<ffffffff8100def5>] ? do_softirq+0x65/0xa0
Feb  4 19:26:32 proxmox kernel: [<ffffffff81075e8d>] ? irq_exit+0xcd/0xd0
Feb  4 19:26:32 proxmox kernel: [<ffffffff81524935>] ? do_IRQ+0x75/0xf0
Feb  4 19:26:32 proxmox kernel: [<ffffffff8100ba93>] ? ret_from_intr+0x0/0x11
Feb  4 19:26:32 proxmox kernel: <EOI>  [<ffffffff812fa7b0>] ? acpi_idle_enter_bm+0x29c/0x2d0
Feb  4 19:26:32 proxmox kernel: [<ffffffff812fa7a9>] ? acpi_idle_enter_bm+0x295/0x2d0
Feb  4 19:26:32 proxmox kernel: [<ffffffff81420387>] ? cpuidle_idle_call+0xa7/0x140
Feb  4 19:26:32 proxmox kernel: [<ffffffff8100a023>] ? cpu_idle+0xb3/0x110
Feb  4 19:26:32 proxmox kernel: [<ffffffff81503e35>] ? rest_init+0x85/0x90
Feb  4 19:26:32 proxmox kernel: [<ffffffff81c2ef6e>] ? start_kernel+0x412/0x41e
Feb  4 19:26:32 proxmox kernel: [<ffffffff81c2e33a>] ? x86_64_start_reservations+0x125/0x129
Feb  4 19:26:32 proxmox kernel: [<ffffffff81c2e438>] ? x86_64_start_kernel+0xfa/0x109
Feb  4 19:26:32 proxmox kernel: ---[ end trace 94a5e86350ca9e02 ]---
 
pls add detailed info about your hardware.
 
Hallo,

thanks for your reply.Here is the list of the used hardware
CPU i5-3350p
Board MSI MSI Z68A-G43 (G3)
RAM 4 x DELL SNPP382HC/4G
NIC NC380T
DVB-s2 Cine S2 V6
Matrox G450

Best regards,
Ralf
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!