From: Francois Romieu <romieu@fr.zoreil.com>
To: Danny <dannydaemonic@gmail.com>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: profile path bug again (was Re: mm kernel oops with r8169 & named, PREEMPT)
Date: Sat, 16 Oct 2004 12:01:26 +0200 [thread overview]
Message-ID: <20041016100125.GA15833@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <9625752b04101514073f6dab24@mail.gmail.com>
Danny <dannydaemonic@gmail.com> :
[profile path bug hits hard]
> Also posting the oops directly instead of linking to it probably
> allows people passing by to look at the oops, increasing the total
> number of eyes.
Yes.
Oops posting is still on-topic in l-k.
> I have a quick question though, if I'm using the kernel with all the
> debug features turned on, should I still run it through ksymoops?
Your file named "oops-raw" contained the relevant information.
--
Ueimor
next prev parent reply other threads:[~2004-10-16 10:01 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
2004-10-14 22:04 ` Danny
2004-10-15 16:18 ` Francois Romieu
2004-10-15 21:07 ` Danny
2004-10-16 10:01 ` Francois Romieu [this message]
2004-10-16 15:52 ` profile path bug again (was Re: 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=20041016100125.GA15833@electric-eye.fr.zoreil.com \
--to=romieu@fr.zoreil.com \
--cc=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
all inboxes | Powered by JetHome®