linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olh@suse.de>
To: linux-scsi@vger.kernel.org
Subject: Re: 2.6.16-rc1 crash in scsi_target_reap_work
Date: Mon, 6 Feb 2006 23:26:22 +0100	[thread overview]
Message-ID: <20060206222622.GA13062@suse.de> (raw)
In-Reply-To: <20060206220434.GA11732@suse.de>

 On Mon, Feb 06, Olaf Hering wrote:

> I started with:
>  git-bisect bad 7a0268fa1a3613f2c526a9b3058701b277f6abe1
>  git-bisect good a020ff412f0ecbb1e4aae1681b287e5785dd77b5

I just learned there is a log:

.git/BISECT_LOG
git-bisect start
# bad: [7a0268fa1a3613f2c526a9b3058701b277f6abe1] powerpc/64: per cpu data optimisations
git-bisect bad 7a0268fa1a3613f2c526a9b3058701b277f6abe1
# good: [a020ff412f0ecbb1e4aae1681b287e5785dd77b5] Fix pragma packing in ip2 driver
git-bisect good a020ff412f0ecbb1e4aae1681b287e5785dd77b5
# bad: [864472e9b8fa76ffaad17dfcb84d79e16df6828c] NFSv4: Make open recovery track O_RDWR, O_RDONLY and O_WRONLY correctly
git-bisect bad 864472e9b8fa76ffaad17dfcb84d79e16df6828c
# bad: [25c862cc9ea9b312c25a9f577f91b973131f1261] Merge git://git.kernel.org/pub/scm/linux/kernel/git/sam/kbuild
git-bisect bad 25c862cc9ea9b312c25a9f577f91b973131f1261
# good: [f61ea1b0c825a20a1826bb43a226387091934586] Merge git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi-misc-2.6
git-bisect good f61ea1b0c825a20a1826bb43a226387091934586
# good: [f2e46561cc1afa82b18b2fc6efc8510ec57c7d7d] sky2: no irq disable needed during tx
git-bisect good f2e46561cc1afa82b18b2fc6efc8510ec57c7d7d
# good: [d779188d2baf436e67fe8816fca2ef53d246900f] Merge branch 'upstream-linus' of master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/netdev-2.6
git-bisect good d779188d2baf436e67fe8816fca2ef53d246900f
# good: [1cb9e8e01d2c73184e2074f37cd155b3c4fdaae6] Merge branch 'upstream' of master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/libata-dev
git-bisect good 1cb9e8e01d2c73184e2074f37cd155b3c4fdaae6
# good: [54e08a2392e99ba9e48ce1060e0b52a39118419c] kbuild: tags file generation fixup
git-bisect good 54e08a2392e99ba9e48ce1060e0b52a39118419c
# bad: [52347f4e810ba323d02cd2c26b5d738f4a2c3d5e] Merge git://git.kernel.org/pub/scm/linux/kernel/git/bunk/trivial
git-bisect bad 52347f4e810ba323d02cd2c26b5d738f4a2c3d5e
# bad: [f62870db3c73683fe566a05efa2a05f3faeb44f5] Documentation/SubmittingPatches: update Trivial Patch Monkey information
git-bisect bad f62870db3c73683fe566a05efa2a05f3faeb44f5
# good: [4a4efbdee278b2f4ed91aad2db5c006ff754276e] s/retreiv/retriev/g
git-bisect good 4a4efbdee278b2f4ed91aad2db5c006ff754276e

Guess I need to let the good ones run much longer now.


-- 
short story of a lazy sysadmin:
 alias appserv=wotan

  reply	other threads:[~2006-02-06 22:26 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-17  0:05 2.6.15-git12, slab corruption in ipr Olaf Hering
2006-01-18 18:42 ` Brian King
2006-01-19 21:05   ` Olaf Hering
2006-01-30 10:46     ` Olaf Hering
2006-01-30 16:49       ` Olaf Hering
2006-02-06 22:04         ` 2.6.16-rc1 crash in scsi_target_reap_work Olaf Hering
2006-02-06 22:26           ` Olaf Hering [this message]
2006-02-06 22:44           ` James Bottomley
2006-02-09 20:05             ` Olaf Hering
2006-02-10 10:11               ` Olaf Hering
2006-02-10 14:04                 ` James Bottomley
2006-02-10 14:10                   ` Olaf Hering
2006-02-10 23:01                     ` Olaf Hering
2006-02-10 23:21                       ` Brian King
2006-02-10 23:29                         ` Olaf Hering
2006-02-11 10:34                           ` Olaf Hering
2006-02-20 23:00                           ` Brian King
2006-02-22  8:36                             ` Olaf Hering
2006-02-22 14:38                               ` Brian King
2006-02-22 15:53                                 ` Olaf Hering
2006-02-22 16:47                                 ` Mike Anderson
2006-02-22 17:05                                   ` James Bottomley
2006-02-10 21:28                   ` Brian King
2006-01-30 18:07 ` 2.6.15-git12, slab corruption in ipr Olaf Hering

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=20060206222622.GA13062@suse.de \
    --to=olh@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).