From: ebiederm@xmission.com (Eric W. Biederman)
To: g3vbv@blueyonder.co.uk
Cc: Adrian Bunk <bunk@stusta.de>,
Randy Dunlap <randy.dunlap@oracle.com>,
linux-kernel@vger.kernel.org, auxsvr@gmail.com
Subject: Re: 2.6.21-rc1 and 2.6.21-rc2 kwin dies silently
Date: Tue, 27 Mar 2007 07:48:42 -0600 [thread overview]
Message-ID: <m1y7liyeyt.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <4608919C.4050007@blueyonder.co.uk> (Sid Boyce's message of "Tue, 27 Mar 2007 04:38:04 +0100")
Sid Boyce <g3vbv@blueyonder.co.uk> writes:
> This is what I've got so far on the first boot, I shall have to check the
> manpage for git-bisect again to see if there is anything else to be added,
> nothing enlightening seen so far - further reboots to be done.
I'm a little confused at what I am seeing below.
Normally what happens is that after a kernel compile and test. You call
"git-bisect bad" or "git-bisect good" and then git-bisect picks the next
kernel to test. Then you compile and test that one. It looks like
you called git-bisect bad several times in a row without testing....
Eric
> barrabas:/usr/src/GIT/linux-2.6 # git bisect bad
> Bisecting: 22 revisions left to test after this
> [3fc605a2aa38899c12180ca311f1eeb61a6d867e] knfsd: allow the server to provide a
> gid list when using AUTH_UNIX authentication
> rrabas:/usr/src/GIT/linux-2.6 # git bisect bad
> Bisecting: 11 revisions left to test after this
> [ed8b4d4d7a31923db32f4684535944d69eb43677] qconf: hide empty list items
> barrabas:/usr/src/GIT/linux-2.6 #
> rrabas:/usr/src/GIT/linux-2.6 # git bisect bad
> Bisecting: 6 revisions left to test after this
> [66e7c7230fed159e138fc1292ee662b8bbdb74d6] qconf: relocate Search Command
> barrabas:/usr/src/GIT/linux-2.6 #
>
> barrabas:/usr/src/GIT/linux-2.6 # git bisect bad
> Bisecting: 3 revisions left to test after this
> [895a39a084e5478121a74752a291165c4502378f] Make mkcompile_h use LANG=C and
> LC_ALL=C for $CC -v
>
> barrabas:/usr/src/GIT/linux-2.6 # git bisect bad
> Bisecting: 2 revisions left to test after this
> [8c7e4498adfdb4aea5a0d056590ec18d099ba062] search a little harder for mkimage
>
> barrabas:/usr/src/GIT/linux-2.6 # git bisect bad
> Bisecting: 1 revisions left to test after this
> [b7de8e7e3c7b79a72c20c7fd58bd65df3d146b13] ia64: fix noncoherent DMA API so
> devres builds
>
> # git bisect bad
> b7de8e7e3c7b79a72c20c7fd58bd65df3d146b13 is first bad commit
> commit b7de8e7e3c7b79a72c20c7fd58bd65df3d146b13
> Author: Roland Dreier <rdreier@cisco.com>
> Date: Wed Feb 14 00:32:53 2007 -0800
>
> [PATCH] ia64: fix noncoherent DMA API so devres builds
>
> On ia64, drivers/base/dma-mapping.c doesn't build because it calls
> dma_alloc_noncoherent() and dma_free_noncoherent(), which appear to be
> terminally broken; the calls end up generating errors like
>
> drivers/base/dma-mapping.c: In function 'dmam_noncoherent_release':
> drivers/base/dma-mapping.c:32: error: 'struct ia64_machine_vector' has no
> member named 'platform_dma_free_coherent'
>
> because the multiple levels of macro expansion in <asm/dma-mapping.h> and
> <asm/machvec.h> end up turning a call to dma_free_noncoherent() into
> ia64_mv.platform_dma_free_coherent (instead of the intended
> ia64_mv.dma_free_coherent).
>
> This patch fixes this by converting dma_{alloc,free}_noncoherent() into
> inline functions that call the corresponding coherent functions, instead of
> trying to do this with macros.
>
> Signed-off-by: Roland Dreier <rolandd@cisco.com>
> Acked-by: Tony Luck <tony.luck@intel.com>
> Cc: Al Viro <viro@zeniv.linux.org.uk>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
> :040000 040000 ac36019577dc1846a5655918cf9d6b2541c398cf
> ba536f54303cc9495b7839763ed1121d3a22154c M include
>
> barrabas:/usr/src/GIT/linux-2.6 # git bisect bad
> 86a71dbd3e81e8870d0f0e56b87875f57e58222b
> Bisecting: 44 revisions left to test after this
> [208367eeec8d6f6fcee1a0672af2149aeee7b658] sysctl: cdrom: remove unnecessary
> insert_at_head flag
>
> barrabas:/usr/src/GIT/linux-2.6 # git bisect good
> ac98695d6c1508b724f246f38ce57fb4e3cec356
> Bisecting: 44 revisions left to test after this
> [208367eeec8d6f6fcee1a0672af2149aeee7b658] sysctl: cdrom: remove unnecessary
> insert_at_head flag
>
> Regards
> Sid.
>
> --
> Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
> Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist,
> Cricket Coach
> Microsoft Windows Free Zone - Linux used for all Computing Tasks
next prev parent reply other threads:[~2007-03-27 13:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-28 15:19 Sid Boyce
2007-02-28 16:05 ` auxsvr
2007-03-08 5:47 ` Andrew Morton
2007-03-08 7:34 ` Sid Boyce
2007-03-21 17:43 ` Sid Boyce
2007-03-21 19:34 ` Adrian Bunk
2007-03-21 20:17 ` Eric W. Biederman
2007-03-22 1:32 ` Sid Boyce
2007-03-22 1:42 ` Randy Dunlap
2007-03-22 10:59 ` Adrian Bunk
2007-03-22 19:49 ` Sid Boyce
2007-03-26 12:02 ` boris
2007-03-27 3:38 ` Sid Boyce
2007-03-27 13:48 ` Eric W. Biederman [this message]
2007-03-28 3:26 ` Sid Boyce
2007-03-28 4:14 ` Adrian Bunk
2007-03-28 13:17 ` Eric W. Biederman
2007-03-29 11:35 ` Sid Boyce
2007-03-30 18:00 ` Adrian Bunk
2007-03-29 4:04 ` Eric W. Biederman
2007-03-29 11:37 ` Sid Boyce
2007-03-29 16:16 ` Sid Boyce
2007-02-28 16:24 Sid Boyce
[not found] <45E5DE32.2070902@argo.co.il>
2007-03-01 13:52 ` Sid Boyce
2007-03-01 15:11 ` Avi Kivity
2007-03-02 4:22 ` Sid Boyce
[not found] <45E939E1.8050501@argo.co.il>
2007-03-03 20:30 ` Sid Boyce
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=m1y7liyeyt.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=auxsvr@gmail.com \
--cc=bunk@stusta.de \
--cc=g3vbv@blueyonder.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/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
all inboxes | Powered by JetHome®