From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
To: Hermann Himmelbauer <dusty@violin.dyndns.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: rtl8139 Problem/kernel panic (probably unrelated)
Date: Thu, 10 Apr 2003 22:31:04 +0200 [thread overview]
Message-ID: <3E95D488.60806@gmx.net> (raw)
In-Reply-To: <200304102118.24350.dusty@violin.dyndns.org>
Hermann Himmelbauer wrote:
> Hi,
> I have problems with my Ovis Link 10/100 PCI Network adapter (based on
> RTL8139too)
>
> Until yesterday the NIC worked flawlessly with Linux-2.4.19-SuSE (from SuSE
> 8.1) and rtl8139too (driver version 0.9.26).
Have you tried upgrading your kernel to the current version from SuSE?
The version number should be like k_deflt-2.4.19-274, which also would
fix the ptrace problem.
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
next prev parent reply other threads:[~2003-04-10 20:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-10 19:18 rtl8139 Problem/kernel panic (probably unrelated) Hermann Himmelbauer
2003-04-10 20:31 ` Carl-Daniel Hailfinger [this message]
2003-04-11 8:15 ` Hermann Himmelbauer
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=3E95D488.60806@gmx.net \
--to=c-d.hailfinger.kernel.2003@gmx.net \
--cc=dusty@violin.dyndns.org \
--cc=linux-kernel@vger.kernel.org \
/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