From: Nico -telmich- Schottelius <nico-linux-next@schottelius•org>
To: linux-next@vger•kernel.org
Subject: How to debug linux-next? (was: Re: xorg problems with v2.6.27-rc1-2457-gdcb80fd)
Date: Thu, 31 Jul 2008 15:23:44 +0200 [thread overview]
Message-ID: <20080731132344.GC4201@denkbrett.schottelius.org> (raw)
In-Reply-To: <20080731125630.GB4201@denkbrett.schottelius.org>
[-- Attachment #1: Type: text/plain, Size: 1542 bytes --]
Hello again!
Some questions about using and debugging linux-next:
- Where to report errors? to this ml? cc-ing the related subsystem
maintainer(s)?
- 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)?
- As far as I can see, you are doing rebase on linux-next. Why don't you
continue to do git-merge?
- And would a non-rebased tree not make life much easier for debugging
purposes?
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.
Sincerly,
Nico
Nico -telmich- Schottelius [Thu, Jul 31, 2008 at 02:56:30PM +0200]:
> Hello!
>
> When booting this kernel, xorg crashes. Details can be found on
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=493101.
>
> Possibly more an xorg issue, just wanted to report that xorg still works
> with 2.6.26-next-20080725.
>
> Sincerly,
>
> Nico
>
> --
> Think about Free and Open Source Software (FOSS).
> http://nico.schottelius.org/documentations/foss/the-term-foss/
>
> PGP: BFE4 C736 ABE5 406F 8F42 F7CF B8BE F92A 9885 188C
--
Think about Free and Open Source Software (FOSS).
http://nico.schottelius.org/documentations/foss/the-term-foss/
PGP: BFE4 C736 ABE5 406F 8F42 F7CF B8BE F92A 9885 188C
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-07-31 13:23 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 ` Nico -telmich- Schottelius [this message]
2008-07-31 13:35 ` How to debug linux-next? (was: Re: xorg problems with v2.6.27-rc1-2457-gdcb80fd) Stephen Rothwell
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=20080731132344.GC4201@denkbrett.schottelius.org \
--to=nico-linux-next@schottelius$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.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