From: Marcin Slusarz <marcin.slusarz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "Sune Mølgaard" <sune-6pRy+okvdpRg9hUCZPvPmw@public.gmane.org>
Cc: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: Fwd: [bisected] nouveau failure with 3.9-rc1 and ongoing
Date: Thu, 14 Mar 2013 20:09:19 +0100 [thread overview]
Message-ID: <20130314190919.GA3092@joi.lan> (raw)
In-Reply-To: <51421D43.7030909-6pRy+okvdpRg9hUCZPvPmw@public.gmane.org>
On Thu, Mar 14, 2013 at 07:56:03PM +0100, Sune Mølgaard wrote:
> Marcin Slusarz wrote:
> > I think it may be already fixed by commit 94f54f5336aac6801f2a14dcb12467e41b35456a
> > "drm/nv50: encoder creation failure doesn't mean full init failure" (post 3.9-rc2)
>
> With the latest 3.9-rc2+ git, I got past the KMS init blackout and into
> X, but I got a panic shortly after.
>
> Unfortunately, the trace was too lengthy to see in which module, and
> since it wasn't captured /var/log/syslog, I have no idea whether it has
> anything to do with nouveau or something else.
>
> tl;dr: It would seem that the commit fixes the specific bug I reported,
> but my system isn't functional.
If you have another machine in the same network, you could try to catch this
panic with netconsole. See
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/networking/netconsole.txt
Marcin
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
prev parent reply other threads:[~2013-03-14 19:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 18:57 [bisected] nouveau failure with 3.9-rc1 and ongoing Sune Mølgaard
[not found] ` <513F7AB3.3-6pRy+okvdpRg9hUCZPvPmw@public.gmane.org>
2013-03-13 17:22 ` Fwd: " Sune Mølgaard
[not found] ` <5140B5DE.4070800-6pRy+okvdpRg9hUCZPvPmw@public.gmane.org>
2013-03-13 19:57 ` Marcin Slusarz
[not found] ` <20130313195700.GA10649-OI9uyE9O0yo@public.gmane.org>
2013-03-14 18:56 ` Sune Mølgaard
[not found] ` <51421D43.7030909-6pRy+okvdpRg9hUCZPvPmw@public.gmane.org>
2013-03-14 19:09 ` Marcin Slusarz [this message]
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=20130314190919.GA3092@joi.lan \
--to=marcin.slusarz-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=sune-6pRy+okvdpRg9hUCZPvPmw@public.gmane.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 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.