From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Nico -telmich- Schottelius <nico-linux-next@schottelius•org>
Cc: linux-next@vger•kernel.org
Subject: Re: How to debug linux-next? (was: Re: xorg problems with v2.6.27-rc1-2457-gdcb80fd)
Date: Thu, 31 Jul 2008 23:35:58 +1000 [thread overview]
Message-ID: <20080731233558.ba613f33.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20080731132344.GC4201@denkbrett.schottelius.org>
[-- Attachment #1: Type: text/plain, Size: 1752 bytes --]
On Thu, 31 Jul 2008 15:23:44 +0200 Nico -telmich- Schottelius <nico-linux-next@schottelius•org> wrote:
>
> Some questions about using and debugging linux-next:
>
> - Where to report errors? to this ml? cc-ing the related subsystem
> maintainer(s)?
Yes.
> - What's the normal way of finding out the source for a problem, if you know
> a good commit (9bead9ae16728973cd31d9fd60c496e0e2fabbd1) and a
> bad commit (dcb80fdb8cffd3fa06cd322b3e8227632ec23597)?
It is much easier to use "git bisect" within a single linux-next release
than between releases. The latter should work some of the time but is
complicated by the fact that linux-next is effectively rebased every
day. So it is sensible to see if the "stable" branch of linux-next works
(as that is just Linus' tree) and use that as a "good" starting point if
so. If that doesn't work, then the problem is in Linus' tree already.
> - As far as I can see, you are doing rebase on linux-next. Why don't you
> continue to do git-merge?
Because some of the trees that are merged into linux-next are rebased
fairly often as well.
> - And would a non-rebased tree not make life much easier for debugging
> purposes?
I don't know. What it would do is produce a lot more merge conflicts as
patches are moved around, changed, removed etc on a daily basis.
> My motivation is to find out the reason why xorg crashes now together
> with the xorg guys. But currently it seems to be impossible for me to
> detect which commits have been between to snapshots of the master
> branch of linux-next.
Yeah, that is a pain. Does Linus' tree work?
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-07-31 13:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 12:56 xorg problems with v2.6.27-rc1-2457-gdcb80fd Nico -telmich- Schottelius
2008-07-31 13:23 ` How to debug linux-next? (was: Re: xorg problems with v2.6.27-rc1-2457-gdcb80fd) Nico -telmich- Schottelius
2008-07-31 13:35 ` Stephen Rothwell [this message]
2008-07-31 14:41 ` How to debug linux-next? Nico -telmich- Schottelius
2008-07-31 15:58 ` Takashi Iwai
2008-07-31 16:09 ` Nico -telmich- Schottelius
2008-07-31 16:36 ` Takashi Iwai
2008-07-31 16:54 ` Nico -telmich- Schottelius
2008-07-31 16:59 ` Takashi Iwai
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=20080731233558.ba613f33.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=nico-linux-next@schottelius$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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