linux-kernel - Re: Initialized radeon -> Oops: 0000 [#1] SMP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 7 Mar 2009 15:22:20 -0800
From:	Arjan van de Ven <arjan@...radead.org>
To:	Tomasz Chmielewski <mangoo@...g.org>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Initialized radeon -> Oops: 0000 [#1] SMP

On Fri, 06 Mar 2009 20:11:08 +0100
Tomasz Chmielewski <mangoo@...g.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.



-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/