errors in Sandy Bridge servers

[blueice]

In beta1 and beta2 versions i have see many errors like this:

[drm:intel_panel_get_max_backlight] *ERROR* fixme: max PWM is zero

and after 2-3 days i have slow network.

I not have similar problems with the 1.X series in the same hardware.
This is happen because of the change in the kernel? (changed from debian to redhat)
The Sandy Bridge is not supported in the new version?

 

[dietmar]

That is just a harmless debug message - or do you have any problems?

 

[blueice]

the problem is that the network is slow, when i request a page sometimes need 10 seconds to complete, not only in vps but also and in proxmox interface.
some more errors is like this:

[drm:intel_panel_get_max_backlight] *ERROR* fixme: max PWM is zero.
[drm:intel_panel_get_max_backlight] *ERROR* fixme: max PWM is zero.
[drm] Initialized drm 1.1.0 20060810
i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
i915 0000:00:02.0: setting latency timer to 64
mtrr: type mismatch for d0000000,10000000 old: write-back new: write-combining
[drm] MTRR allocation failed. Graphics performance may suffer.
xhci_hcd 0000:06:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
xhci_hcd 0000:06:00.0: setting latency timer to 64
xhci_hcd 0000:06:00.0: xHCI Host Controller
xhci_hcd 0000:06:00.0: new USB bus registered, assigned bus number 3
xhci_hcd 0000:06:00.0: irq 19, io mem 0xfe400000
alloc irq_desc for 35 on node -1
alloc kstat_irqs on node -1
alloc irq_2_iommu on node -1
xhci_hcd 0000:06:00.0: irq 35 for MSI/MSI-X
alloc irq_desc for 36 on node -1
alloc kstat_irqs on node -1
alloc irq_2_iommu on node -1
xhci_hcd 0000:06:00.0: irq 36 for MSI/MSI-X
alloc irq_desc for 37 on node -1
alloc kstat_irqs on node -1
alloc irq_2_iommu on node -1
xhci_hcd 0000:06:00.0: irq 37 for MSI/MSI-X
alloc irq_desc for 38 on node -1
alloc kstat_irqs on node -1
alloc irq_2_iommu on node -1
[drm:intel_panel_get_max_backlight] *ERROR* fixme: max PWM is zero.
TCP: Peer 79.103.8.83:60284/80 unexpectedly shrunk window 1806338857:1806341761 (repaired)
TCP: Peer 79.103.8.83:60283/80 unexpectedly shrunk window 1810147258:1810153066 (repaired)
TCP: Peer 79.103.8.83:60287/80 unexpectedly shrunk window 1796175529:1796181337 (repaired)
TCP: Peer 79.103.8.83:60284/80 unexpectedly shrunk window 1806338857:1806341761 (repaired)
TCP: Peer 79.103.8.83:60287/80 unexpectedly shrunk window 1796175529:1796181337 (repaired)
TCP: Peer 79.103.8.83:60283/80 unexpectedly shrunk window 1810147258:1810153066 (repaired)
TCP: Peer 79.103.8.83:60305/80 unexpectedly shrunk window 1848160295:1848163199 (repaired)
TCP: Peer 212.54.207.198:49796/80 unexpectedly shrunk window 1581820946:1581822398 (repaired)
TCP: Peer 212.54.207.198:49791/80 unexpectedly shrunk window 1574116166:1574119070 (repaired)

 

[blueice]

and also some more logs:

tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
device tap103i0 entered promiscuous mode
u32 classifier
Performance counters on
input device check on
Actions configured
vmbr0: port 2(tap103i0) entering forwarding state
vmbr0: no IPv6 routers present
eth0: no IPv6 routers present
tap103i0: no IPv6 routers present
[drm:intel_panel_get_max_backlight] *ERROR* fixme: max PWM is zero.
[drm:intel_panel_get_max_backlight] *ERROR* fixme: max PWM is zero.
[drm:intel_panel_get_max_backlight] *ERROR* fixme: max PWM is zero.
vmbr0: port 2(tap103i0) entering disabled state
vmbr0: port 2(tap103i0) entering disabled state