From: Martin Steigerwald <Martin@lichtvoll.de>
To: Theodore Tso <tytso@mit.edu>
Cc: Florian Mickler <florian@mickler.org>,
linux-kernel@vger.kernel.org, Paolo Ornati <ornati@gmail.com>
Subject: Re: help with git bisecting a bug 16376: random - possibly Radeon DRM KMS related - freezes
Date: Fri, 10 Sep 2010 18:18:02 +0200 [thread overview]
Message-ID: <201009101818.03436.Martin@lichtvoll.de> (raw)
In-Reply-To: <412F0940-B810-4F19-8064-CD3E11DEE8B4@mit.edu>
[-- Attachment #1: Type: Text/Plain, Size: 1517 bytes --]
Am Freitag 10 September 2010 schrieb Theodore Tso:
> On Sep 10, 2010, at 9:49 AM, Martin Steigerwald wrote:
> > Maybe next time: "Fails to boot with partially shown backtrace, with
> > some ext4 / readahead function calls inside it"? Or even more
> > general some I/O / filesystem related functions?
> Learn how to use a serial console so you can get a full backtrace, thus
> saving yourself and folks interesting in helping you valuable time?
> :-)
I know how to use a serial console. Actually I am no freaking idiot at all
and I do not like being treated as such.
I just did a bisect, and these kernels were unbootable. I didn't think it
would have been worth the effort to put that much time in it to grab my
other notebook, remember how to set up the serial stuff and all - when all
I wanted to do was to complete the bisect.
I already told that I missed reporting that I do not need any information
relating that issue anymore cause I was able to skip the area with that
unbootable kernels at all. I am sorry for that, cause then you would have
known in advance that there is no need to do any further analysis.
Its getting a bit ridicolous now. I am done with it, since its no issue at
all anymore. My current 2.6.36-rc3 definately boots, so does 2.6.34 and
2.6.35 and thus the issue is gone and all is well. So can we be done with
that now?
Thanks,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2010-09-10 16:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 19:53 help with git bisecting a bug 16376: random - possibly Radeon DRM KMS related - freezes Martin Steigerwald
2010-08-31 22:39 ` Ken Moffat
2010-09-01 16:10 ` Martin Steigerwald
2010-09-01 18:13 ` Ken Moffat
2010-09-01 18:47 ` Paolo Ornati
2010-09-01 19:26 ` Martin Steigerwald
2010-09-05 7:53 ` Martin Steigerwald
2010-09-05 12:20 ` Paolo Ornati
2010-09-05 13:25 ` Martin Steigerwald
2010-09-07 2:51 ` Ted Ts'o
2010-09-09 14:18 ` Martin Steigerwald
2010-09-10 11:55 ` Florian Mickler
2010-09-10 13:49 ` Martin Steigerwald
2010-09-10 15:53 ` Theodore Tso
2010-09-10 16:18 ` Martin Steigerwald [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=201009101818.03436.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=florian@mickler.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ornati@gmail.com \
--cc=tytso@mit.edu \
/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