From: Johannes Berg <johannes@sipsolutions.net>
To: Francisco Jerez <currojerez@riseup.net>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Ben Skeggs <bskeggs@redhat.com>,
dri-devel@lists.freedesktop.org
Subject: Re: nouveau X lockup on 36-rc (regression from 2.6.35)
Date: Mon, 30 Aug 2010 21:54:27 +0200 [thread overview]
Message-ID: <1283198067.3909.0.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <87d3sz50ze.fsf@riseup.net>
On Mon, 2010-08-30 at 21:55 +0200, Francisco Jerez wrote:
> Johannes Berg <johannes@sipsolutions.net> writes:
>
> > On Mon, 2010-08-30 at 21:33 +0200, Francisco Jerez wrote:
> >> Johannes Berg <johannes@sipsolutions.net> writes:
> >>
> >> > On Mon, 2010-08-30 at 21:08 +0200, Francisco Jerez wrote:
> >> >
> >> >> > This problem persists in -rc3, where I'd hoped the nouveau changes would
> >> >> > actually fix it :-( In fact, it seems I was either "lucky" or it was
> >> >> > made easier to trigger, this time it already happened during my login.
> >> >
> >> >> That's already fixed in the nouveau kernel tree.
> >> >
> >> > Can you identify a fix that I can cherry-pick until (hopefully) -rc4?
> >> >
> >> Sure, try 5a5608adff833bad37c56278b6194c5b0a5b36bf.
> >
> > An actual url would help ... What is "the nouveau kernel tree"?
> >
> Ah sorry, git://anongit.freedesktop.org/nouveau/linux-2.6.
Ah, freedesktop, was looking on git.kernel.org. Thanks, I'll install the
kernel now and let you know how it fares when I boot it in the morning.
johannes
next prev parent reply other threads:[~2010-08-30 19:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 13:55 nouveau X lockup on 36-rc (regression from 2.6.35) Johannes Berg
2010-08-30 16:30 ` Johannes Berg
2010-08-30 19:08 ` Francisco Jerez
2010-08-30 19:13 ` Johannes Berg
2010-08-30 19:33 ` Francisco Jerez
2010-08-30 19:27 ` Johannes Berg
2010-08-30 19:55 ` Francisco Jerez
2010-08-30 19:54 ` Johannes Berg [this message]
2010-08-31 9:27 ` Johannes Berg
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=1283198067.3909.0.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=bskeggs@redhat.com \
--cc=currojerez@riseup.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=rjw@sisk.pl \
/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.