Oops with Gigabyte motherboard "GA-X48-DQ6" and r8168 Realtek driver

[Roman Medina-Heigl Hernandez <roman@rs-labs.com>]

Hello kernel-hackers,

I bought a PC intended to be used as a server with the recent Gigabyte
motherboard "GA-X48-DQ6":
http://www.giga-byte.es/products/mb/specs/ga_x48_dq6.html

It includes two RTL8111/8168B NICs, which seem the cause of the kernel
crashes (*but I'm not sure*)..., a Quad core, 4GB RAM and two 500GB HDs.

I installed Debian Linux (4.0) on it and I'm getting *kernel panic*
errors (r8168 module) when set to production state. I couldn't get any
kernel debug messages since I'm using Debian stock kernel
(2.6.18-6-686-bigmem) and I'm not a kernel hacker either. It happens from
time to time so it is not easily reproduceable, or at least I couldn't find
the way to reproduce it on purpose (I stressed the server forcing huge sftp
transfers and/or using iperf tool, without success). But the problem is
there and it seems a NIC driver problem.

Moreover, the machine is located at a remote location so I have to trust
other people reading screen messages for me, etc. It's not easy to debug in
this situation. I've been told that the oops were produced in r8168 module,
from time to time, and that they saw also one only crash while booting the
server "due to SATA" (???). The server uses software-raid and was
re-syncing to a second disk since the second disk was new (so expect high
disk load). I'm a bit confused, it seems that the problem could be the
r8168 driver but I cannot be sure at all.

Could you help me? Do you have reports of similar problems with similar NIC
/ motherboard? How to solve it? I'm sorry for not providing more info
(lspci, etc) but as I previously said the server is in a remote location
and it's currently powered-off. Any hints?

I'm using latest Realtek driver for RTL8111/8168B at:
ftp://202.65.194.212/cn/nic/r8168-8.010.00.tar.bz2
(I have r8169 driver *not* loaded and blacklisted in
/etc/modprobe.d/blacklist -since it didn't work for my 8111B-, and initrd
was rebuilt with new r8168 driver; so the only NIC driver loaded is r8168,
compiled from the former .tar.bz2 (8.010 version).

As a quick workaround (since I need to put that server on production state
*ASAP*), would you recommend to boot with safer options (noacpi, etc)?
Which ones exactly? (no problem if they degrade performance a bit or if
they cause less power-saving; in this case, stability and uptime is preferred).

Thank you from your comprehension and cooperation.
-Roman