From: Jiang Liu <jiang.liu@linux.intel.com>
To: Guenter Roeck <linux@roeck-us.net>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: linux-next: Tree for Nov 14
Date: Sun, 16 Nov 2014 10:33:46 +0800 [thread overview]
Message-ID: <54680D0A.7070900@linux.intel.com> (raw)
In-Reply-To: <20141115211922.GA2347@roeck-us.net>
Hi Guenter,
Could you please help to provide the config file and
error messages?
Thanks!
Gerry
On 2014/11/16 5:19, Guenter Roeck wrote:
> On Fri, Nov 14, 2014 at 07:27:38PM +1100, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20141113:
>>
>> New tree: overlayfs
>>
>> The idle tree gained a conflict against Linus' tree.
>>
>> The scsi tree gained a conflict against the usb tree.
>>
>> Non-merge commits (relative to Linus' tree): 6264
>> 6509 files changed, 209171 insertions(+), 167101 deletions(-)
>>
>
> I bisected the x86-nosmp qemu runtime failure I have seen for
> the last few days. Here is the result:
>
> bb46613f7099f70bc68c1c684cfa22d6863cd8eb is the first bad commit
> commit bb46613f7099f70bc68c1c684cfa22d6863cd8eb
> Author: Jiang Liu <jiang.liu@linux.intel.com>
> Date: Mon Oct 27 16:12:06 2014 +0800
>
> x86, irq: Make MSI and HT_IRQ indepenent of X86_IO_APIC
>
> Detailed log:
>
> git bisect start 'HEAD' 'v3.18-rc4'
> # good: [97bf3e2baed8f45432933bf15535061fb5acda44] Merge remote-tracking branch 'sound-asoc/for-next'
> git bisect good 97bf3e2baed8f45432933bf15535061fb5acda44
> # bad: [d23dcf93e7ad8004ef80726717f700316e53f44d] Merge remote-tracking branch 'usb-serial/usb-next'
> git bisect bad d23dcf93e7ad8004ef80726717f700316e53f44d
> # bad: [cff78d32f4c15b7b2cb173c8e6097c513f406da0] Merge remote-tracking branch 'kvm/linux-next'
> git bisect bad cff78d32f4c15b7b2cb173c8e6097c513f406da0
> # good: [09dc3f20206821e06b1b281b1ae4451777f707c4] Merge remote-tracking branch 'audit/next'
> git bisect good 09dc3f20206821e06b1b281b1ae4451777f707c4
> # bad: [caf0fea9e728916a92c508988fd2ae84a08c280b] Merge branch 'x86/vdso'
> git bisect bad caf0fea9e728916a92c508988fd2ae84a08c280b
> # good: [9aa5f98820067b00456c42347fc0ff48d2d2474f] Merge branch 'sched/urgent'
> git bisect good 9aa5f98820067b00456c42347fc0ff48d2d2474f
> # bad: [46fe562d914fde0a43ee339a0fcfd4af829cb8f7] Merge branch 'x86/boot'
> git bisect bad 46fe562d914fde0a43ee339a0fcfd4af829cb8f7
> # good: [b26ea43d0bb1539ce047206a57c7fd8d636e7f22] x86, irq: Protect __clear_irq_vector() with vector_lock
> git bisect good b26ea43d0bb1539ce047206a57c7fd8d636e7f22
> # bad: [e1d8f79a27a41493c8f1ad0bde440048e17f9494] iommu/amd: Use helpers to access irq_cfg data structure associated with IRQ
> git bisect bad e1d8f79a27a41493c8f1ad0bde440048e17f9494
> # good: [051825cab15c8180f2f0dbc3a9de5a3db7476065] x86, irq: Move HT IRQ related code from io_apic.c into htirq.c
> git bisect good 051825cab15c8180f2f0dbc3a9de5a3db7476065
> # bad: [bb46613f7099f70bc68c1c684cfa22d6863cd8eb] x86, irq: Make MSI and HT_IRQ indepenent of X86_IO_APIC
> git bisect bad bb46613f7099f70bc68c1c684cfa22d6863cd8eb
> # good: [b09198f7b59101e52bcf238ed3b7bfc64de055ef] x86, irq: Move IRQ initialization routines from io_apic.c into vector.c
> git bisect good b09198f7b59101e52bcf238ed3b7bfc64de055ef
> # first bad commit: [bb46613f7099f70bc68c1c684cfa22d6863cd8eb] x86, irq: Make MSI and HT_IRQ indepenent of X86_IO_APIC
>
> I'll be happy to provide the configuration if needed.
>
> Guenter
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2014-11-16 2:33 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 8:27 linux-next: Tree for Nov 14 Stephen Rothwell
2014-11-15 21:19 ` Guenter Roeck
2014-11-16 2:33 ` Jiang Liu [this message]
2014-11-16 3:22 ` Guenter Roeck
2014-11-16 4:20 ` Jiang Liu
2014-11-16 6:56 ` Guenter Roeck
2014-11-16 8:24 ` Jiang Liu
2014-11-16 8:37 ` Jiang Liu
2014-11-16 15:42 ` Guenter Roeck
2014-11-16 16:01 ` Guenter Roeck
2014-11-16 16:11 ` Guenter Roeck
2014-11-17 5:12 ` Jiang Liu
2014-11-17 17:02 ` Guenter Roeck
-- strict thread matches above, loose matches on Subject: below --
2023-11-14 3:19 Stephen Rothwell
2022-11-14 7:49 Stephen Rothwell
2019-11-14 8:31 Stephen Rothwell
2019-11-14 18:38 ` Naresh Kamboju
2019-11-14 20:11 ` Jan Stancek
2019-11-14 21:19 ` Arnd Bergmann
2018-11-14 5:26 Stephen Rothwell
2017-11-14 6:20 Stephen Rothwell
2016-11-14 7:23 Stephen Rothwell
2013-11-14 4:22 Stephen Rothwell
2012-11-14 5:30 Stephen Rothwell
2012-11-14 5:37 ` Andrew Morton
2012-11-14 5:53 ` Andrew Morton
2012-11-14 6:47 ` Ingo Molnar
2012-11-14 6:56 ` Andrew Morton
2012-11-14 7:15 ` Stephen Rothwell
2012-11-14 7:24 ` Andrew Morton
2012-11-14 7:39 ` Ingo Molnar
2012-11-14 8:13 ` Hugh Dickins
2012-11-14 17:05 ` Rik van Riel
2012-11-15 12:10 ` Mel Gorman
2012-11-14 17:19 ` Linus Torvalds
2012-11-14 6:55 ` Stephen Rothwell
2012-11-14 7:03 ` Stephen Rothwell
2011-11-14 3:43 Stephen Rothwell
2019-11-14 16:43 ` Christian Brauner
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=54680D0A.7070900@linux.intel.com \
--to=jiang.liu@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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).