mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Claudio Martins <ctpm@rnl.ist.utl.pt>
To: linux-kernel@vger.kernel.org
Cc: Jeff Garzik <jgarzik@pobox.com>, silverbanana@gmx.de
Subject: Re: usage of RealTek 8169 crashes my Linux system
Date: Mon, 29 Mar 2004 09:41:27 +0100	[thread overview]
Message-ID: <200403290941.27765.ctpm@rnl.ist.utl.pt> (raw)
In-Reply-To: <4067378B.7070102@pobox.com>


On Sunday 28 March 2004 21:37, Jeff Garzik wrote:
> Bernd Fuhrmann wrote:
> >
> > Any idea how to fix it? Is that driver getting stable in the next months
> > or are there obstacles that should make me buy a different NIC (like
> > missing docs for that chipset and stuff like that)?
>
> Does Andrew Morton's -mm patches fix it for you?
>
> 	Jeff


 Hi,

  I'm also seeing hard crashes when using the r8169 driver, running a 32-bit 
2.6.4-rc1 kernel on a AMD64 system with a MSI K8T motherboard (VIA KT800). It 
has an onboard Realtek 8110S chip.
  When I stopped using the r8169 module the crashes stopped. Now using a PCI 
rtl8139 nic temporarily.

  Is there any way to apply these newer -netdev patches without resorting to 
-mm tree? This is a production machine, so I'd rather stick to linus' 2.6.x, 
but if there's no choice I'll try -mm...

 Thanks in advance for your attention.

Claudio


  parent reply	other threads:[~2004-03-29  8:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-28 20:24 Bernd Fuhrmann
2004-03-28 20:37 ` Jeff Garzik
2004-03-28 21:50   ` Bernd Fuhrmann
2004-03-28 22:35     ` Jeff Garzik
2004-03-28 22:36     ` Francois Romieu
2004-03-29 19:39       ` Bernd Fuhrmann
2004-03-29 19:56         ` Francois Romieu
2004-03-30  9:08           ` Bernd Fuhrmann
2004-03-29  8:41   ` Claudio Martins [this message]
2004-03-29 16:18     ` Francois Romieu
2004-03-29  9:24 ` Daniel Egger
2004-03-29 16:13   ` Francois Romieu
2004-03-29 16:20     ` Francois Romieu

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=200403290941.27765.ctpm@rnl.ist.utl.pt \
    --to=ctpm@rnl.ist.utl.pt \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=silverbanana@gmx.de \
    /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

all inboxes | Powered by JetHome®