lkml.org 
[lkml]   [2010]   [Sep]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: help with git bisecting a bug 16376: random - possibly Radeon DRM KMS related - freezes
On Sun, Sep 05, 2010 at 09:53:41AM +0200, Martin Steigerwald wrote:
>
> Quite some kernels were unbootable with an ext4 and readahead related
> backtrace[1].

Unfortunately, you don't have a full backtrace in the picture which
submitted as an attachment to the bugzilla. It shows part of the
backtrace which has an ext4 and readahead stack, yes. But we didn't
get to see the beginning of the stack trace with the IP and the reason
for the oops. If keyboard interrupts still work, you might try seing
if you can scroll upwards and see more of the backtrace. Or you might
try configuring your console to use a higher resolution display so
more lines can be displayed. Or you might try getting a serial
console.

I don't recognize the display, but the problem could just as easily be
in the block layer or in the device driver for your hard drive.
(i.e., the readahead stack calls ext4, which in turn will submit a
read request to the block device layer which then submits the request
to a device driver).

But because you keep referring it to it as an ext4/readahead related
backtrace, you may have disguised the symptom enough that people who
might recognize it as, "Oh, yeah, there was this regression in the
SATA layer", wouldn't recognize it as such from your description.
That's why it's important to be careful how you describe issues; if
you had said, I don't have a complete stack trace, and I don't have
the IP and function where the fault occurred, that might have caused
people to think a bit harder about what might be the problem, instead
of thinking to themselves, "ah, well, the ext4 and readahead parts of
the kernel aren't my problem, so I'll ignore this report".

> I am also seeking help with selecting more suitable commits to test: If
> its a Radeon KMS related freeze and everything points at it, I think the
> offending commit is in the first quarter of what git commit shows to me[2].

You do know that you can restrict a git bisect to commits that modify
a particular part of the tree, right? e.g.,

git bisect start 2.6.34 2.6.33 -- drivers/gpu/drm/radeon

- Ted


\
 
 \ /
  Last update: 2010-09-07 04:53    [W:0.422 / U:0.148 seconds]
©2003-2014 Jasper Spaans. Advertise on this site