From: Arjan van de Ven <arjan@infradead.org>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Initialized radeon -> Oops: 0000 [#1] SMP
Date: Sat, 7 Mar 2009 15:41:16 -0800 [thread overview]
Message-ID: <20090307154116.470b2883@infradead.org> (raw)
In-Reply-To: <49B3027D.60400@wpkg.org>
On Sun, 08 Mar 2009 00:25:49 +0100
Tomasz Chmielewski <mangoo@wpkg.org> wrote:
> Arjan van de Ven schrieb:
> > On Fri, 06 Mar 2009 20:11:08 +0100
> > Tomasz Chmielewski <mangoo@wpkg.org> wrote:
> >
> >> Don't really know where one should send Oops... Is there a better
> >> place than linux-kernel?
> >>
> >>
> >> First time I see such an oops on this multiseat system. Everything
> >> still works fine though.
> >>
> >
> > Hi,
> >
> > if you run the oops through "markup_oops.pl" (and assuming you have
> > CONFIG_DEBUG_INFO set) the oops gets part transformed into a
> > sourcecode dump of where the oops is happening..... that sometimes
> > helps in nailing it down.
>
> Hmmm, no luck here, or...?
>
> # zgrep CONFIG_DEBUG_INFO /proc/config.gz
> # CONFIG_DEBUG_INFO is not set
yeah you might want to flip that for next time ;-)
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2009-03-07 23:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 19:11 Initialized radeon -> Oops: 0000 [#1] SMP Tomasz Chmielewski
2009-03-07 21:16 ` Rafael J. Wysocki
2009-03-07 23:13 ` Tomasz Chmielewski
2009-03-08 22:47 ` Tomasz Chmielewski
2009-03-07 23:22 ` Arjan van de Ven
2009-03-07 23:25 ` Tomasz Chmielewski
2009-03-07 23:41 ` Arjan van de Ven [this message]
2009-03-07 23:43 ` Dave Airlie
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=20090307154116.470b2883@infradead.org \
--to=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mangoo@wpkg.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