From: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
To: Paul Gortmaker <paul.gortmaker-CWA4WttNNZF54TAoqtyWWQ@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
James Hogan <james.hogan-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>,
linux-metag-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: metag test failure in -next due to commit 'module: relocate module_init from init.h to module.h'
Date: Fri, 5 Jun 2015 13:40:55 -0700 [thread overview]
Message-ID: <20150605204055.GA981@roeck-us.net> (raw)
Hi,
My qemu metag runtime test fails in -next due to commit 5ebbb3badaa8 ("module:
relocate module_init from init.h to module.h"). Bisect log is as follows.
A log of a failed test is available at
http://server.roeck-us.net:8010/builders/qemu-metag-next/builds/173/steps/qemubuildcommand/logs/stdio
Essentially the test just hangs in boot.
Reverting the commit fixes the problem.
Guenter
---
# bad: [94feb25d6fcd34b0d45c18cf0185d83d0c13c60a] Add linux-next specific files for 20150604
# good: [c65b99f046843d2455aa231747b5a07a999a9f3d] Linux 4.1-rc6
git bisect start 'HEAD' 'v4.1-rc6'
# good: [46cb2717b4b827977bccd276096791d0efdb4119] Merge remote-tracking branch 'drm/drm-next'
git bisect good 46cb2717b4b827977bccd276096791d0efdb4119
# good: [37104644ae9384d6fc6574f16dc9782259ab89b1] Merge remote-tracking branch 'kvms390/next'
git bisect good 37104644ae9384d6fc6574f16dc9782259ab89b1
# good: [311942c925377a65157e4b14778a22bb05808314] Merge remote-tracking branch 'staging/staging-next'
git bisect good 311942c925377a65157e4b14778a22bb05808314
# good: [4b40a87efb321750a527aea556337f24b5268783] Merge remote-tracking branch 'clk/clk-next'
git bisect good 4b40a87efb321750a527aea556337f24b5268783
# good: [0cd6ba7205ab368b324d5a5f601aa3f5f89c246f] MAINTAINERS: update sound soc intel patterns
git bisect good 0cd6ba7205ab368b324d5a5f601aa3f5f89c246f
# good: [076edbd2f016f2fb4a80b95625cd65a9aed4e06c] Merge remote-tracking branch 'rtc/rtc-next'
git bisect good 076edbd2f016f2fb4a80b95625cd65a9aed4e06c
# good: [8c169d94c31fced71d907e26b19b4f5f0bd9d7bf] scsi-resolve-sg-buffer-const-ness-issue-fix
git bisect good 8c169d94c31fced71d907e26b19b4f5f0bd9d7bf
# good: [baaf163cd06a517d85dc39a6fa00107e3620b779] Merge branch 'module_init-device_initcall-4.1-rc6' into init-v4.1-rc6
git bisect good baaf163cd06a517d85dc39a6fa00107e3620b779
# good: [8f0b9591c464a9fd783b481b2c9cddf008043ba4] Merge branch 'module-builtin_driver-4.1-rc6' into init-v4.1-rc6
git bisect good 8f0b9591c464a9fd783b481b2c9cddf008043ba4
# bad: [fc3af372b8c176c08e8921d772ca2bff5620f15b] kernel/relay.c: use kvfree() in relay_free_page_array()
git bisect bad fc3af372b8c176c08e8921d772ca2bff5620f15b
# bad: [cdcdbb925bb730624d1312620263c0cf3666da5c] Merge remote-tracking branch 'init/init-v4.1-rc6'
git bisect bad cdcdbb925bb730624d1312620263c0cf3666da5c
# good: [3a283d1794f58a054f247152fb4aa15088aad561] mips: make loongsoon serial driver explicitly modular
git bisect good 3a283d1794f58a054f247152fb4aa15088aad561
# bad: [3491bfd125cd3d2b7654e2244fb1c262c7212049] Merge branch 'module-misc-4.1-rc6' into init-v4.1-rc6
git bisect bad 3491bfd125cd3d2b7654e2244fb1c262c7212049
# bad: [5ebbb3badaa8ffc50558af88cdea27497953356a] module: relocate module_init from init.h to module.h
git bisect bad 5ebbb3badaa8ffc50558af88cdea27497953356a
# first bad commit: [5ebbb3badaa8ffc50558af88cdea27497953356a] module: relocate module_init from init.h to module.h
next reply other threads:[~2015-06-05 20:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 20:40 Guenter Roeck [this message]
[not found] ` <20150605204055.GA981-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2015-06-05 21:39 ` metag test failure in -next due to commit 'module: relocate module_init from init.h to module.h' James Hogan
[not found] ` <20150605213900.GA30510-4bYivNCBEGTR3KXKvIWQxtm+Uo4AYnCiHZ5vskTnxNA@public.gmane.org>
2015-06-06 0:39 ` Guenter Roeck
[not found] ` <55724131.9040900-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2015-06-07 22:17 ` Paul Gortmaker
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=20150605204055.GA981@roeck-us.net \
--to=linux-0h96xk9xttrk1umjsbkqmq@public.gmane.org \
--cc=james.hogan-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-metag-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=paul.gortmaker-CWA4WttNNZF54TAoqtyWWQ@public.gmane.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 read-only IMAP folder(s) and NNTP newsgroup(s).