From: Pekka Paalanen <pq@iki.fi>
To: "Ozan Çağlayan" <ozan@pardus.org.tr>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
jens.axboe@oracle.com, dri-devel@lists.sf.net
Subject: Re: NULL pointer dereference at cfq_exit_single_io_context
Date: Sun, 4 Oct 2009 19:31:11 +0300 [thread overview]
Message-ID: <20091004193111.1e8e3baf@daedalus.pq.iki.fi> (raw)
In-Reply-To: <4AC85907.7080805@pardus.org.tr>
On Sun, 04 Oct 2009 11:12:55 +0300
Ozan Çağlayan <ozan@pardus.org.tr> wrote:
> Hi,
>
> The attached dmesg is obtained on a 2.6.30.8 with:
>
> - DRM patches mainly gathered from Fedora F-11 branch,
> - The following patch from mainline which addresses kernel
> bugzilla #13401:
>
> From: Jeff Moyer <jmoyer@redhat.com>
> Date: Fri, 11 Sep 2009 15:08:59 +0000 (+0200)
> Subject: cfq: choose a new next_req when a request is dispatched
> X-Git-Url:
> http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Ftorvalds%2Flinux-2.6.git;a=commitdiff_plain;h=06d2188644c85c56d243efab914f368d1d23c4a3
>
>
> The user which sent me the dmesg below tells that consecutive
> attempts to boot into X with the *nouveau* driver is generally
> not possible because of random lockups.
>
> I'll have access to the machine in this week so I can try
> anything you want me to do.
This problem should be fixed now, we debugged it for a long time. E.g.
https://bugs.freedesktop.org/show_bug.cgi?id=23847
The commit:
http://cgit.freedesktop.org/nouveau/linux-2.6/commit/?id=7798546495c04a810db86be34ba1f39e370fd325
"drm/nouveau: fix missized allocation for ttm_bo_global struct"
I hope that solves your issue.
--
Pekka Paalanen
http://www.iki.fi/pq/
next prev parent reply other threads:[~2009-10-04 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-04 8:12 Ozan Çağlayan
2009-10-04 16:31 ` Pekka Paalanen [this message]
2009-10-04 20:05 ` Ozan Çağlayan
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=20091004193111.1e8e3baf@daedalus.pq.iki.fi \
--to=pq@iki.fi \
--cc=dri-devel@lists.sf.net \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ozan@pardus.org.tr \
/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®