All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Christian Kujau <evil@g-house.de>
Cc: linux-kernel@vger.kernel.org, alsa-devel@lists.sourceforge.net,
	perex@suse.cz
Subject: Re: Oops in 2.6.10-rc1
Date: Sun, 7 Nov 2004 10:44:19 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0411071040440.2223@ppc970.osdl.org> (raw)
In-Reply-To: <20041107182155.M43317@g-house.de>



On Sun, 7 Nov 2004, Christian Kujau wrote:

> On Sun, 7 Nov 2004 08:57:40 -0800 (PST), Linus Torvalds wrote
> > 
> > You can check the ALSA tree _before_ the merge, by doing (in 
> > the current tree):
> > 
> > 	bk undo -a1.2000.7.2
> > 
> > which should give you a tree without any of "my" stuff, ie it 
> > was what Jaroslav was working on before he merged it into the 
> > standard tree.
> 
> yes, i already did so, i think:
> 
> http://marc.theaimsgroup.com/?l=linux-kernel&m=109979092216919&w=2
> 
> but i did it this way:
>  bk clone -r1.2000.7.1 linux-2.6-BK linux-2.6-BK-test
>  bk undo -a1.2010

Hmm.. That may well have worked fine, but it sounds in that post like you
tried to undo the ALSA stuff, and what I suggested was really to do the
reverse: take _only_ the ALSA changes, and then if it still fails, at
least you have now pinpointed it a bit more (admittedly to the _likely_
source, but that's as it should be: you narrow down the "known bad" source
base until you've narrowed it down to the smallest change you can find
that causes the problem).

> > Yes, that makes me suspicious, and is one reason why I wonder 
> > if it's just your tree not being built right.
> 
> i'll build a -bk snapshot from a tar.bz2 later on and see what it gives.

Sounds like you're doing everything right, but hey, it can't hurt to 
double-check.

		Linus

  reply	other threads:[~2004-11-07 18:44 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-28 13:12 Oops in 2.6.10-rc1 Christian
2004-10-28 13:29 ` [Alsa-devel] " Jaroslav Kysela
2004-10-28 14:09   ` Christian
2004-11-04 15:16     ` Christian Kujau
2004-11-05  2:35       ` Christian Kujau
2004-11-05 11:40         ` holborn
2004-11-07  1:24       ` Christian Kujau
2004-11-07  7:02         ` Linus Torvalds
2004-11-07 13:10           ` Christian Kujau
2004-11-07 16:02             ` Christian Kujau
2004-11-07 16:57               ` Linus Torvalds
2004-11-07 18:31                 ` Christian Kujau
2004-11-07 18:44                   ` Linus Torvalds [this message]
2004-11-07 23:45                   ` Christian Kujau
2004-11-07 23:45                     ` Christian Kujau
2004-11-08  1:16                     ` Linus Torvalds
2004-11-08  1:16                       ` Linus Torvalds
2004-11-08 13:01                       ` Christian Kujau
2004-11-08 13:01                         ` Christian Kujau
2004-11-08 18:13                         ` Linus Torvalds
2004-11-08 18:13                           ` Linus Torvalds
2004-11-08 20:59                           ` Christian Kujau
2004-11-08 20:59                             ` Christian Kujau
2004-11-08 23:49                             ` Christian Kujau
2004-11-09  1:05                               ` Linus Torvalds
2004-11-09  1:41                                 ` Christian Kujau
2004-11-09  1:31                               ` Christian Kujau
2004-11-09  7:40                                 ` Pekka Enberg
2004-11-09 12:33                                   ` Christian Kujau
2004-11-09 17:26                                     ` Oops in 2.6.10-rc1 (almost solved) Christian Kujau
2004-11-09 18:53                                       ` Linus Torvalds
2004-11-09 19:04                                         ` [PATCH] kobject: fix double kobject_put() in error path of kobject_add() Greg KH
2004-11-09 19:08                                           ` Greg KH
2004-11-09 20:19                                             ` Pekka Enberg
2004-11-09 21:21                                             ` Christian Kujau
2004-11-09 21:31                                             ` Christian Kujau
2004-11-09 19:09                                           ` Linus Torvalds
2004-11-09 22:06                                             ` Christian Kujau
2004-11-09 23:30                                         ` Oops in 2.6.10-rc1 (almost solved) Christian Kujau
2004-11-09 23:40                                           ` Matt Domsch
2004-11-10  0:21                                             ` Christian Kujau
2004-11-10  1:01                                               ` Linus Torvalds
2004-11-11 22:43                                             ` Matt Domsch
2004-11-11 22:53                                               ` Linus Torvalds
2004-11-11 22:55                                                 ` Matt Domsch
2004-11-12  0:27                                               ` Christian Kujau
2004-11-12  0:49                                                 ` Linus Torvalds
2004-11-12  1:27                                                   ` Christian Kujau
2004-11-10  0:12                           ` Oops in 2.6.10-rc1 Christian Kujau
2004-11-10  0:23                             ` Linus Torvalds
2004-11-08 18:44                         ` Pekka Enberg
2004-11-08 18:44                           ` Pekka Enberg
2004-11-08 19:00                           ` Greg KH
2004-11-08 19:00                             ` Greg KH
2004-11-08 19:18                             ` Pekka Enberg
2004-11-08 19:18                               ` Pekka Enberg
2004-11-08 19:30                               ` Pekka Enberg
2004-11-08 19:30                                 ` Pekka Enberg
2004-11-08 20:31                               ` Christian Kujau
2004-11-08 20:31                                 ` Christian Kujau
2004-11-07 13:05         ` Pekka Enberg
2004-11-07 13:43           ` Christian Kujau

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=Pine.LNX.4.58.0411071040440.2223@ppc970.osdl.org \
    --to=torvalds@osdl.org \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=evil@g-house.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@suse.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.