Subject: How to debug linux-next? (was: Re: xorg problems with v2.6.27-rc1-2457-gdcb80fd)

From: Nico -telmich- Schottelius <[email-masked]>
Date: Thu, 31 Jul 2008 15:23:44 +0200

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