From: Alistair John Strachan <alistair@devzero.co.uk>
To: "Roman Medina-Heigl Hernandez" <roman@rs-labs.com>
Cc: Frans Pop <elendil@planet.nl>, linux-kernel@vger.kernel.org
Subject: Re: Oops with Gigabyte motherboard "GA-X48-DQ6" and r8168 Realtek driver
Date: Sat, 10 Jan 2009 12:55:07 +0000 [thread overview]
Message-ID: <200901101255.07611.alistair@devzero.co.uk> (raw)
In-Reply-To: <4967DE52.3040709@rs-labs.com>
On Friday 09 January 2009 23:31:30 Roman Medina-Heigl Hernandez wrote:
> Frans Pop escribió:
> > Roman Medina-Heigl Hernandez wrote:
> >> 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.
> >
> > Have you tried the 2.6.24 kernel that is available for Debian Etch? That
> > seems to me the most logical thing to try first as a possible solution.
>
> I didn't (although I thought of it). It seems to me like a blind attempt
> and the problem is that I cannot afford to waste another "production
> attempt" and that I cannot reproduce the crash whenever I want, so if I
> upgrade I'll not be able to know whether the problem is fixed or not until
> I got a new crash (or not). Moreover, if the root cause of the problem is
> r8168 driver, it will crash in both cases (the driver doesn't change, it's
> compiled from source by me).
One thing to bear in mind is that if you're using a CPU which goes via swiotlb
(such as a pre-nehalem Intel Quad) 2.6.24 won't be new enough. The r8169
driver until recently had a grave bug on >=4GB RAM systems where the kernel
would crash after some amount of transfer.
My advice to you is to install the very latest Debian kernel (2.6.27) in which
this bug has been fixed. That said, I think if you do this, you won't have any
further problems. Using the vendor driver instead of the one in mainline
probably isn't a good idea.
--
Cheers,
Alistair.
next prev parent reply other threads:[~2009-01-10 12:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 9:40 Oops with Gigabyte motherboard "GA-X48-DQ6" and r8168 Realtek driver Roman Medina-Heigl Hernandez
2009-01-09 21:52 ` Frans Pop
2009-01-09 23:31 ` Roman Medina-Heigl Hernandez
2009-01-10 12:55 ` Alistair John Strachan [this message]
2009-01-10 18:47 ` Roman Medina-Heigl Hernandez
2009-01-10 20:35 ` Alistair John Strachan
2009-01-11 18:06 ` Roman Medina-Heigl Hernandez
2009-01-15 8:00 ` Roman Medina-Heigl Hernandez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200901101255.07611.alistair@devzero.co.uk \
--to=alistair@devzero.co.uk \
--cc=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=roman@rs-labs.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox