public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Dave Airlie <airlied@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: vanilla kernels hang randomly under Fedora 10 on system with Radeon card
Date: Mon, 1 Dec 2008 23:42:32 +0100	[thread overview]
Message-ID: <200812012342.32575.bzolnier@gmail.com> (raw)


Hi,

After Fedora 9 -> Fedora 10 upgrade vanilla kernels which previously
worked fine (next-20081128 and next-20081121) started to hang randomly
on my Pentium M / 855PM / RV350 laptop.  Since (surprisingly) stock
Fedora kernel (2.6.27.5-117.fc10.i686) was not affected I got the idea
that either userspace changes uncovered some kernel regression or some
Fedora specific patch must be fixing the issue.  Unfortunately vanilla
2.6.27 also freezed so after the usual pain caused by hitting bunch of
unrelated problems [1] it turned out that drm-modesetting-radeon.patch
is the magic patch and CONFIG_DRM_RADEON_KMS is the magic change.  With
the patch and enabling the option next-20081128 works stable again...

Since the following error gets logged by kernel:

[drm:drm_buffer_object_validate] *ERROR* Failed moving buffer. cef578c0 1444 4000027 10000a0
[drm:drm_buffer_object_validate] *ERROR* Out of aperture space or DRM memory quota.

and it also seems that system is more responsive now (it was kind of
sluggish previously) my draft theory is that F9 -> F10 triggered some
AGP memory management bug and CONFIG_DRM_RADEON_KMS happens to fix it
but I'll leave figuring this up to the more knowledgeable people... ;)

Thanks,
Bart

PS1 full dmesg, config and lspci outputs are here:
http://www.kernel.org/pub/linux/kernel/people/bart/f9_to_f10_grind/

PS2 drm set mode reporting looks quite weird sometimes, i.e.:

...
[drm] LVDS-8: set mode �Տ�� d                                                   
[drm] bios LVDS_GEN_CNTL: 0x30ff24                                              
...

[1] some Fedora patches make quilt trip (quilt push applies whole patch
but quilt pop only removes a part of it) since they aggregate multiple
changes to a single file, execshield patch causes oops with my kernel
config and depmod run for a Fedora kernel config's build triggered OOM
kill (512M on this machine and yes, I was happily running without swap)

             reply	other threads:[~2008-12-01 22:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-01 22:42 Bartlomiej Zolnierkiewicz [this message]
2008-12-02  5:18 ` vanilla kernels hang randomly under Fedora 10 on system with Radeon card Dave Airlie
2008-12-03 14:10   ` Bartlomiej Zolnierkiewicz
2008-12-04  0:07     ` Bartlomiej Zolnierkiewicz
2008-12-04 19:55       ` Bartlomiej Zolnierkiewicz
2008-12-04 20:18         ` Bartlomiej Zolnierkiewicz
2008-12-07 19:21           ` Bartlomiej Zolnierkiewicz
2008-12-13 14:12             ` Bartlomiej Zolnierkiewicz
2008-12-05 18:50         ` next-2008120[3,4] drm oops (was Re: vanilla kernels hang randomly under Fedora 10 on system with Radeon card) Bartlomiej Zolnierkiewicz
2008-12-08  0:17           ` Dave Airlie
2008-12-09 23:09             ` Bartlomiej Zolnierkiewicz
2008-12-13 13:57               ` Bartlomiej Zolnierkiewicz
2008-12-04 19:32   ` vanilla kernels hang randomly under Fedora 10 on system with Radeon card Jack Tanner
2008-12-02  9:37 ` Benny Amorsen

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=200812012342.32575.bzolnier@gmail.com \
    --to=bzolnier@gmail.com \
    --cc=airlied@redhat.com \
    --cc=linux-kernel@vger.kernel.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