From: Danny <dannydaemonic@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: netdev@oss.sgi.com, Francois Romieu <romieu@fr.zoreil.com>
Subject: Re: mm kernel oops with r8169 & named, PREEMPT
Date: Wed, 13 Oct 2004 14:59:06 -0700 [thread overview]
Message-ID: <9625752b04101314595f72f84a@mail.gmail.com> (raw)
In-Reply-To: <20041013205433.GC30761@electric-eye.fr.zoreil.com>
On Wed, 13 Oct 2004 22:54:33 +0200, Francois Romieu wrote:
> [snip]
> Possible :o)
>
> OTOH, I do not want to miss an error report.
Well the options I tried disabling (ACPI, PREEMPT) didn't stop the oops.
> [snip]
> I am not a reiserfs addict but you can imho go for the complete serie
> of reiserfs patches once you have sucked the first one (3Mo, yuck).
>
> If you have issues with the ordering of the patches, just grep the
> patches in the 'series' file.
Ok thanks, I have work to do right now so I'll have to try this out tonight.
next prev parent reply other threads:[~2004-10-13 21:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 6:00 mm kernel oops with r8169 & named, PREEMPT Danny
2004-10-13 6:32 ` Jeff Garzik
2004-10-13 7:28 ` Francois Romieu
2004-10-13 16:05 ` Danny
2004-10-13 16:17 ` Danny
[not found] ` <9625752b04101309182a96fbd2@mail.gmail.com>
[not found] ` <200410131129.05657.jdmason@us.ltcfwd.linux.ibm.com>
2004-10-13 20:28 ` Danny
[not found] ` <200410131703.21726.jdmason@us.ltcfwd.linux.ibm.com>
2004-10-14 21:54 ` Danny
[not found] ` <20041013181840.GA30852@electric-eye.fr.zoreil.com>
2004-10-13 20:44 ` Danny
[not found] ` <9625752b04101313417be4cf90@mail.gmail.com>
[not found] ` <20041013205433.GC30761@electric-eye.fr.zoreil.com>
2004-10-13 21:59 ` Danny [this message]
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
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=9625752b04101314595f72f84a@mail.gmail.com \
--to=dannydaemonic@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=romieu@fr.zoreil.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.