From: "BERTRAND Joël" <joel.bertrand@systella.fr>
To: sparclinux@vger.kernel.org
Subject: Re: [2.6.29.4] Blade 2000
Date: Fri, 12 Jun 2009 07:25:09 +0000 [thread overview]
Message-ID: <4A3202D5.1090906@systella.fr> (raw)
In-Reply-To: <4A1C36B5.6040707@systella.fr>
David Miller wrote:
> From: BERTRAND Joël <joel.bertrand@systella.fr>
> Date: Thu, 11 Jun 2009 18:32:04 +0200
>
>> tchebytchev:[~/linux/sparc-2.6] > git bisect start v2.6.29 v2.6.28 --
>> drivers/scsi/qla2xxx/
>> Checking out files: 100% (10708/10708), done.
>> Switched to branch "master"
>> Bisecting: 19 revisions left to test after this
>> [8eca3f39c4b11320787f7b216f63214aee8415a9] [SCSI] qla2xxx: Always
>> serialize mailbox command execution.
>>
>> -> kernel boots
>>
>> tchebytchev:[~/linux/sparc-2.6] > git bisect good
>> Bisecting: 9 revisions left to test after this
>> [618a752319503a64d1b66615e8ea2a0e7edaf914] [SCSI] qla2xxx: Remove
>> interrupt request bit check in the response processing path in multiq
>> mode.
>>
>> -> kernel doesn't boot
>>
>> tchebytchev:[~/linux/sparc-2.6] > git bisect bad
>> Bisecting: 4 revisions left to test after this
>> [b872ca4081c480e3d76443282ffd7f206321f50f] [SCSI] qla2xxx: Correct
>> descriptions in flash manipulation routines.
>> tchebytchev:[~/linux/sparc-2.6] >
>>
>> tchebytchev:[~/linux/sparc-2.6] > git bisect log
>> # bad: [8e0ee43bc2c3e19db56a4adaa9a9b04ce885cd84] Linux 2.6.29
>> # good: [4a6908a3a050aacc9c3a2f36b276b46c0629ad91] Linux 2.6.28
>> git-bisect start 'v2.6.29' 'v2.6.28' '--' 'drivers/scsi/qla2xxx/'
>> # good: [8eca3f39c4b11320787f7b216f63214aee8415a9] [SCSI] qla2xxx:
>> # Always serialize mailbox command execution.
>> git-bisect good 8eca3f39c4b11320787f7b216f63214aee8415a9
>> # bad: [618a752319503a64d1b66615e8ea2a0e7edaf914] [SCSI] qla2xxx: Remove
>> # interrupt request bit check in the response processing path in multiq
>> # mode.
>> git-bisect bad 618a752319503a64d1b66615e8ea2a0e7edaf914
>> tchebytchev:[~/linux/sparc-2.6] >
>>
>> I'm investigating...
>
> Keep going :-)
>
> You need to keep building and going "git bisect bad" or "git bisect
> good" until it tells you the final guilty commit.
>
> I assume you understand this and are just giving a status report
> mid-way in your task, but I wanted to be sure. :-)
David, I know. But I have no time to complete this work until this
week-end (I cannot reboot workstation I use for tests).
Regards,
JKB
next prev parent reply other threads:[~2009-06-12 7:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 18:36 [2.6.29.4] Blade 2000 BERTRAND Joël
2009-05-29 9:58 ` BERTRAND Joël
2009-06-04 22:39 ` David Miller
2009-06-05 7:49 ` BERTRAND Joël
2009-06-05 7:59 ` David Miller
2009-06-11 10:38 ` David Miller
2009-06-11 10:56 ` BERTRAND Joël
2009-06-11 16:32 ` BERTRAND Joël
2009-06-12 0:06 ` David Miller
2009-06-12 7:25 ` BERTRAND Joël [this message]
2009-06-14 12:40 ` BERTRAND Joël
2009-07-17 17:23 ` David Miller
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=4A3202D5.1090906@systella.fr \
--to=joel.bertrand@systella.fr \
--cc=sparclinux@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 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.