From: Danny <dannydaemonic@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: netdev@oss.sgi.com
Subject: Re: mm kernel oops with r8169 & named, PREEMPT
Date: Wed, 13 Oct 2004 13:44:02 -0700 [thread overview]
Message-ID: <9625752b04101313445a67923@mail.gmail.com> (raw)
In-Reply-To: <20041013181840.GA30852@electric-eye.fr.zoreil.com>
On Wed, 13 Oct 2004 20:18:40 +0200, Francois Romieu wrote:
> Danny, can your drop the r8169 driver from 2.6.9-rc4-mm1 into vanilla
> 2.6.9-rc4 and confirm that it works (preempt should not matter) ?
I see how the timing on the installation of the r8169 could have just
been bad. Since preempt shouldn't matter, I'm going to test that
and acpi etc first (because it's easier to test heh).
See, well, I'm going to need reiser4 for the vanilla. I found patches here:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.9-rc4/2.6.9-rc4-mm1/broken-out/
But can someone point out which patches I will need? Do I only need
reiser4-only.patch or is it safer for my fs if I have all the other
reiser4 patches?
next prev parent reply other threads:[~2004-10-13 20:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9625752b041012230068619e68@mail.gmail.com>
[not found] ` <20041013072814.GA24066@electric-eye.fr.zoreil.com>
2004-10-13 16:05 ` mm kernel oops with r8169 & named, PREEMPT Danny
[not found] ` <9625752b041013091772e26739@mail.gmail.com>
2004-10-13 16:18 ` Danny
2004-10-13 16:29 ` Jon Mason
2004-10-13 18:18 ` Francois Romieu
2004-10-13 20:44 ` Danny [this message]
[not found] ` <9625752b04101313417be4cf90@mail.gmail.com>
[not found] ` <20041013205433.GC30761@electric-eye.fr.zoreil.com>
2004-10-13 21:59 ` Danny
2004-10-14 22:04 ` Danny
2004-10-15 16:18 ` Francois Romieu
2004-10-15 21:07 ` Danny
2004-10-16 10:01 ` profile path bug again (was Re: mm kernel oops with r8169 & named, PREEMPT) Francois Romieu
2004-10-16 15:52 ` Danny
2004-10-13 20:28 ` mm kernel oops with r8169 & named, PREEMPT Danny
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=9625752b04101313445a67923@mail.gmail.com \
--to=dannydaemonic@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).